Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't work with rooted Epic 4G (Samsung Galaxy S) -- old shell version & no 4G interface support #43

Closed
GoogleCodeExporter opened this issue Oct 23, 2015 · 11 comments

Comments

@GoogleCodeExporter
Copy link

Droidwall does not work with a rooted Epic 4G (Samsung Galaxy S)

There are several problems:

1) the stock /system/bin/sh shell does not support shell scripting! 
droidwall.sh fails on the first 'if' statement:
# sh droidwall.sh
[: not found
[: not found
[: not found
[: not found
--version: not found


2) droidwall does not generate rules for the 4G WiMax interface ("uwbr0" on 
this phone). A simple solution would be to apply the same rules to this 
interface as to the wifi interface, since sprint plans come with real unlimited 
4G (unlike the "unlimited" 3G that is really capped at 10GB/month). Or 
alternatively, apply the same rules to the 4G interface as to the 3G interface.

You can detect the existence of the WiMax interface when it's not loaded by 
grep'ing one of the following files:
/system/etc/dhcpcd/dhcpcd.conf:interface uwbr0
/system/bin/dhcpcd:uwbr0
/system/app/MobileAP.odex:dhcp.uwbr0.result
/system/etc/enable_uwbr.sh:iptables -t nat -D POSTROUTING -o uwbr0 -j MASQUERADE
/system/etc/initialize_nat.sh:iptables -t nat -D POSTROUTING -o uwbr0 -j 
MASQUERADE
/system/framework/framework.odex: /sys/class/net/uwbr0/statistics/

Original issue reported on code.google.com by sli...@gmail.com on 17 Sep 2010 at 12:16

@GoogleCodeExporter
Copy link
Author

Could you please test the development version from the following location:
http://droidwall.googlecode.com/issues/attachment?aid=-6202447490991805206&name=
droidwall-dev.apk&token=88552b563fb4b3f59a222d7589743619

Let me know the results. Thanks

Original comment by rodrigo...@gmail.com on 17 Sep 2010 at 8:05

@GoogleCodeExporter
Copy link
Author

have same issio on Samsung Galaxy S (international), wanted to test it, but the 
link does not work.

Original comment by samichl...@gmail.com on 19 Sep 2010 at 6:58

@GoogleCodeExporter
Copy link
Author

Okay, so please test the attached version:

Original comment by rodrigo...@gmail.com on 20 Sep 2010 at 2:29

Attachments:

@GoogleCodeExporter
Copy link
Author

Works for me!

Thank you for your hard work Rodrigo! I couldn't stand having an Android 
without your awesome app

By the way -- I noticed droidwall itself doesn't show up on the applicatons 
list in droidwall. Is that only the case on my phone? Or is that intentional?

Original comment by sli...@gmail.com on 21 Sep 2010 at 3:41

@GoogleCodeExporter
Copy link
Author

Great that it works now :)

Droid Wall only displays applications that are capable of accessing the 
network, that is why many applications are filtered from the list. See issue 3 
for more details.

Original comment by rodrigo...@gmail.com on 21 Sep 2010 at 4:46

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

the issue is now fixed, but now i get  " Grep command is required, grep: not 
found" Any ideas?

Original comment by samichl...@gmail.com on 22 Sep 2010 at 8:50

@GoogleCodeExporter
Copy link
Author

samichlaus:

Probably it's because the scripts that install busybox when you root the phone 
don't properly link all of busybox's functions.

-- Do the following as root, in Terminal --

You can fix this by doing the following:
  mount -o=remount,rw -t rfs /dev/block/stl9 /system
  ln -s /system/bin/busybox /system/bin/grep

You should probably fix all the possibly busybox functions, so you don't have 
to worry about it again:
http://pastebin.com/syEvZ1Y0

Once you're done, you probably should remount read-only again: either reboot or 
run the following:
  mount -o=remount,ro -t rfs /dev/block/stl9 /system


Original comment by sli...@gmail.com on 22 Sep 2010 at 9:52

@GoogleCodeExporter
Copy link
Author

Busybox is not always located /system/bin/ - on my phone it is on 
/system/xbin/, for example.

I changed Droid Wall to try to find where "grep" is. Could you try the attached 
development version? Thanks

Original comment by rodrigo...@gmail.com on 23 Sep 2010 at 12:25

@GoogleCodeExporter
Copy link
Author

Attached the wrong one :| this is the correct one:

Original comment by rodrigo...@gmail.com on 23 Sep 2010 at 12:31

Attachments:

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

hi, sorry for the long time, i can now apply the rules, it sais that it worked, 
but it doesn't apply them, after the reboot all connections wlan/gprs are 
locked. anything else I can do for testing? (samsung galaxy i9000)

Original comment by samichl...@gmail.com on 2 Oct 2010 at 12:53

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant