Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a very simple problem: when I run Wifi Tether on my Galaxy S3 the computer won't get the IP address unless I disable DroidWall firewall.

DW runs in whitelist mode, but I ran across its menu to enable all wireless related applications it found. Nothing. I have to stop it at all to make DHCP server work.

What application in Android 4.1, or at least in the stock GS3 ROM, governs DHCP in wireless tethering and should be enabled with DroidWall?

Or else, how do I find it out without try-and-fail across a large number of applications.

share|improve this question
up vote 3 down vote accepted

As of version 1.2.5, tethering has been included in AFWall+, you should only need to enable

  • (Tethering) - DHCP+DNS services
share|improve this answer

It is normal to disable Droidwall, for the reason that it blocks any incoming packets for port 67, to allow Wifi Tethering to work. Or quite simply, allow a custom script that matches the port number 67 which is dhcp to pass through.

FYI about Droidwall - the functionality and development efforts have been discontinued and the author sold it off to Avast.

The fork of Droidwall is called AFWall+ which can be found here and found on Google Play which is apparently better than the old Droidwall.


Since Wifi-Tether operates on both TCP/UDP's port number 67 (for dhcp to work), here's the rules necessary:

$IPTABLES -A "droidwall-wifi" -p TCP --destination-port 67 -j RETURN
$IPTABLES -A "droidwall-wifi" -p UDP --destination-port 67 -j RETURN

This rule here enables adbWireless to work with DroidWall enabled.

$IPTABLES -A "droidwall-wifi" --destination "" --destination-port 5555 -j RETURN

You also have to enable Wi-Fi access for "Apps running as root" for this to work.

share|improve this answer
Thanks for the 'bought by avast' info. Missed that, although it's already a year... – ce4 Jan 12 '13 at 19:32
Since I'm currently fine with DW, the question comes quickly: does AFWall+ allow DHCP without hacky scripts? By the way, since I'm not familiar with iptables scripting may I have the code for the port-67-allowing script? – usr-local-ΕΨΗΕΛΩΝ Jan 13 '13 at 12:24
Trying to guess: "$IPTABLES -A "droidwall" --destination-port 67 -j RETURN". Is it correct? – usr-local-ΕΨΗΕΛΩΝ Jan 13 '13 at 12:27
@djechelon: I will try out that shortly, am not 100% sure, but it does seem to be legit to me... :) – t0mm13b Jan 13 '13 at 14:39
Both script and flagging applications running as root fixed. I'm pretty unsure because AFAIK system apps are all root apps and Samsung preloads lots of unwanted bloatware on device, software that I wouldn't want to "phone home" often. These include Game Hub and Samsung Apps – usr-local-ΕΨΗΕΛΩΝ Jan 13 '13 at 19:49

I had the same problem with wifi tethering after I installed Droidwall. Though the wifi connection was successful but I got no internet access.

I got it working simply by adding the DNS in my laptop. Hope, it works for you or anyone facing the same problem.

Change/Add DNS and in your PC/Laptop. That's it.

share|improve this answer
This worked for me too, using NoRoot Firewall. Thanks :-) – Just Plain High Mar 30 at 5:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.