This was while I had configured connection with DHCP. Once I have set it up using static IP everything started to work as expected, but I would still like to hear an explanation if somebody knows why does it behave like that.
Now I have another problem.
I'm using custom scripts in order to apply rules with more detail than just completely allow or disallow an application access through a selected interface. The problem I'm facing (and doesn't occur with DroidWall) is that when creating a rule specifying a hostname instead of an IP address, such rule doesn't get applied. However, if I execute the same command in the shell after AFWall+ finishes doing its job (i.e. applying rules), the rule is configured as expected.
e.g.: iptables -I afwall-wifi-wan 14 -m owner --uid-owner 10185 -d hostname -j RETURN
What concerns AFWall+ binaries used they are configured by default (auto/built-in). Also... IPv6 functionality is not enabled.
BTW: I noticed that before global rejection rule there is a general DNS allow for root rule set up that I haven't configured. Why?
38 RETURN udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53 owner UID match 0
Why I should buy AFWall+ Unlocker compare to AFWall+ Donate ?
1. Test AFWall+ Beta versions (usually updated first in AFWall+ Free version)
|block internet, droidwall, firewall, iptables, security|
|Thread Tools||Search this Thread|