search

deadash / droidwall

Automatically exported from code.google.com/p/droidwall
0 stars 0 forks source link

blocking tethering apps when enabled in DroidWall #124

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install a tethering application.
2. Enable iptables via DroidWall and allow said application.  Apply rules via 
whitelist.
3. Start the tethering Rudi app.

What is the expected output? 
You should see a broadcasted ad-hoc ssid and when you connect to the network 
you should get an ip address and browse the internet.

What do you see instead?
You see a broadcasted ssid and can connect to the network.  Your device can't 
obtain an IP or browse the internet because of no ip.

What version of the product are you using? On what operating system?
DroidWall 1.5.0
Android 2.2.1 rooted.
Motorolla Droid X

Please provide any additional information below.
Affected applications are:
Barnacle Wifi Tether
Wireless Tether for Root Users

The applications work when you disable firewall or allow all applications. The 
apps run dhcpd so it is likely being blocked.

Possible solution is to allow ports via DroidWall and open port 67.  Another 
solution would be to allow a user to add a custom binary path for a firewall 
exception.

Sam Gleske

Original issue reported on code.google.com by sam.mxra...@gmail.com on 29 Mar 2011 at 1:17

GoogleCodeExporter commented 8 years ago 
Can you please check what app ID is blocked on DroidWall logs?

Thanks!

Original comment by rodrigo...@gmail.com on 30 Mar 2011 at 8:52

GoogleCodeExporter commented 8 years ago 
Hey, sorry it took me a while to get back to you.  Here's what the log shows.

App ID 0 ((root) - Applications running as root) - Blocked 85 packets (83 
packets for 192.168.2.103, 2 packets for 255.255.255.255)

App ID (kernel) - Blocked 11 packets (3 for 66.174.92.14, 4 packets for 
72.14.204.82, 4 packets for 12.234.113.120)

End of log.

So my guess is it is the applications running as root rule which is blocking 
dhcpd.  I would like to be able to open up the firewall just to dhcpd.  Because 
I don't want other root running applications to get Internet access without my 
permission.

Sam Gleske

Original comment by sam.mxra...@gmail.com on 2 Apr 2011 at 4:02

GoogleCodeExporter commented 8 years ago 
Well the root rule appears to be what is blocking it because I enabled that 
rule in the whitelist and then the application started working.  Though, as I 
stated before this is not a desirable solution due to the security risk of any 
root application having internet access.

Sam Gleske

Original comment by sam.mxra...@gmail.com on 2 Apr 2011 at 4:23

GoogleCodeExporter commented 8 years ago 
That is definitely not a "security risk" since the applications are already 
running as root. Any malicious app running as root will be able to bypass any 
firewall it wants to.

Sorry, but it is not possible to allow only dhcp since iptables works by 
matching against USER IDs (not processes).

Original comment by rodrigo...@gmail.com on 4 Apr 2011 at 12:21