Droidwall doesn't work correctly on Jelly Bean with data connection

[GoogleCodeExporter]

What steps will reproduce the problem?
1. On a Galaxy Nexus (VZW Version) install Jelly BAMF.
2. Enable Droidwall.
3. Disable WiFi if on WiFi.
4. Apps that connect to the Internet like Browser/Chrome/Tweetcaster will take 
a long time to connect, if they connect at all.  WiFi does not exhibit the 
problem.  Droidwall functions correctly.

What is the expected output? What do you see instead?
Regardless of data connection or wifi apps should be able to access the 
Internet.

What version of the product are you using? On what operating system?
Latest version.  1.5.7.  Android 4.1. 

Please provide any additional information below.
Yes, I understand that I'm on a port from the GSM Nexus image but this is still 
worth noting since 4.1 code hits mid-July.  AOSP ROM's will follow shortly 
there after and I would very much prefer to keep using Droidwall instead of 
having to find a substitute.

Original issue reported on code.google.com by jtsch...@gmail.com on 2 Jul 2012 at 10:03

[GoogleCodeExporter]

Yeah I have the same problem on my Galaxy S2 running Resurrection Remix v2.5.3 
with newly imported Jelly beans animations and features. 

Just as a side note this happens to all firewall apps such as Root Firewall and 
Avast's in built firewall, and they all have the same error code too!

Hopefully a fix soon!! 

Original comment by Troy.Mc...@gmail.com on 8 Jul 2012 at 10:25

[GoogleCodeExporter]

Same problem on jakeday's 4.1.1 build from AOSP

http://rootzwiki.com/topic/28677-rom-jelly-belly-v63-08152012-jellybean-411-pure
-aosp-its-all-about-the-butter/

Original comment by korth.l...@gmail.com on 16 Aug 2012 at 8:28

[GoogleCodeExporter]

Seeing the same issue affect both data and wifi connections, though it seems 
more severe in the case of data. Galaxy S2 with latest CM 10 nightly.

Original comment by j.in.ja...@gmail.com on 21 Aug 2012 at 4:03

[GoogleCodeExporter]

Workaround: activate the logging function in DroidWall.

For my configuration (Galaxy S, CM10) this seems to work :) 
Don't know why but tested it a few times with and without - and it was always 
the same effect. When "Log" was deactivated - establishing of a network 
connection was delayed again. 

Original comment by sendm...@gmail.com on 22 Aug 2012 at 1:52

[GoogleCodeExporter]

Confirming with S2 CM10 build 20120904 and it's default kernel. Log activation 
solves the problem.

Original comment by saulius....@gmail.com on 10 Sep 2012 at 8:49

[GoogleCodeExporter]

Same issue using Android 4.1.2 (unofficial CM10 on Samsung Infuse I997). This 
particular problem isn't exclusive for Droidwall but another firewall apps like 
Root Firewall are affected. May be an iptables related issue.

Original comment by jmlvar...@gmail.com on 18 Oct 2012 at 2:15

[GoogleCodeExporter]

Ok, no comments from developer... We can try this: 
http://forum.xda-developers.com/showthread.php?t=541380&page=64

Original comment by jmlvar...@gmail.com on 25 Oct 2012 at 2:18

[GoogleCodeExporter]

FYI: The original owner and creator Rodrigo Rosauro sold droidwall to AVAST in 
December 2011. A fork of the latest GPL version of droidwall (v1.5.7) can be 
found here: https://github.com/kechagia/droidwall

I've starting working on a fork of this.

Original comment by korth.l...@gmail.com on 25 Oct 2012 at 2:22

[GoogleCodeExporter]

Same on Nexus S 4G with CM10 M2 snapshot. Droidwall v1.5.7.

Enabling the log in Droidwall works as a workaround.

Original comment by mast...@gmail.com on 8 Nov 2012 at 2:06