Applying iptables rules - Galaxy S/JVB 2.3

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Try to enable firewal

What is the expected output? What do you see instead?
The output should be something as "firewall enabled" but instead an error is 
shown:
"
Error applying iptables rules. exit code: 1
iptables v1.3.7
[1] Sementation fault / data/data/com.g..
modprobe: chdir(/system/lib/modules):No Such file or directory
getsockopt for multiport failed strangely:Nu such file or directory
getsockopt for multiport failed strangely:Nu such file or directory
getsockopt for multiport failed strangely:Nu such file or directory
getsockopt for multiport failed strangely:Nu such file or directory
"

What version of the product are you using? On what operating system?
Galaxy S, Symply Honey rom, standard kernel, based on JVB 2.3 STOCK

Please provide any additional information below.

Original issue reported on code.google.com by gide...@gmail.com on 21 Apr 2011 at 7:32

[GoogleCodeExporter]

I can confirm this... Stock samsung 2.3.3 with CF-root.... 

Original comment by g30ffmci...@gmail.com on 25 Apr 2011 at 8:20

[GoogleCodeExporter]

It seems that the iptables binary shipped with DroidWall is crashing on this 
device. DroidWall then falls-back to the system iptables, which is too old 
(v1.3.7) so it doesn't work either

Can you please post your "/proc/cpuinfo" here? Thanks

Original comment by rodrigo...@gmail.com on 25 Apr 2011 at 7:40

[GoogleCodeExporter]

I already switched back to 2.2.1 because 2.3 had too much issues.
not sure if the cpuinfo changes but here is it:

Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 786.20
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2

Hardware : SMDKC110
Revision : 0030
Serial : 30310f81a0a300ec

Original comment by gide...@gmail.com on 25 Apr 2011 at 7:48

[GoogleCodeExporter]

I also updated to 2.3 jvb today on galaxy s and got this same error.
hope will get fixed soon as this is one of the most important tool on phone..
thnks.

Original comment by shi...@gmail.com on 27 Apr 2011 at 2:28

[GoogleCodeExporter]

Can someone having the problem please test with the attached iptables binary? I 
compiled iptables 1.4.10 myself - hopefully this one will work :)

Just copy this file to 
/data/data/com.googlecode.droidwall.free/cache/iptables_n1 and make sure the 
permissions are good (must be able to execute)

I tested it on my Nexus S and it worked fine

Thanks!

Original comment by rodrigo...@gmail.com on 27 Apr 2011 at 6:46

Attachments:

• iptables

[GoogleCodeExporter]

I have the same issue on my SGS running CM7.  The above iptables binary didn't 
fix it.

Original comment by syl...@gmail.com on 28 Apr 2011 at 12:10

[GoogleCodeExporter]

strangely enough on JVB using supercurio's kernel it was working. but not so 
much with other kernels.
Whene ever in droidwall the apply rules doesn't work. The supplied iptables 
binary crashes  and I guess if falls back to the system one, it ends up with an 
error, and the firewall is disabled. at that exact moment using the widget the 
it works ... the firewall is enabled (but i'm not sure it's actually working, 
as i noticed this morning that app that aren't supposed to access the internet 
are in fact accessing)

Original comment by foufo...@gmail.com on 28 Apr 2011 at 5:27

[GoogleCodeExporter]

I can't understand why this binary crashes on the Galaxy S. It worked fine on 
all devices I tested. Unfortunately I don't have a SGS for testing but I use a 
Nexus S myself, which has a very similar hardware.

I just compiled another iptables binary, this time for ARMv5 architecture 
without any processor-specific optimizations. Can you please test with the 
attached iptables_armv5?

This binary should work on absolutely all ARM-based Android devices. If it 
still crashes I will need to get my hands on a SGS, lol

Thanks

Original comment by rodrigo...@gmail.com on 28 Apr 2011 at 12:27

Attachments:

• iptables_armv5

[GoogleCodeExporter]

great.. the latest iptables seem to do the trick.. its working perfect now on 
my sgs with 2.3.
thanks a lot for the quick fix. I'll post if any trouble.

Original comment by shi...@gmail.com on 28 Apr 2011 at 1:45

[GoogleCodeExporter]

Those are good news

I will change the iptables binary shipped with DroidWall for the next version. 
And will finally get rid of having two binaries for different ARM architectures 
:)

I appreciate if the others could also test and confirm if it works.

Original comment by rodrigo...@gmail.com on 28 Apr 2011 at 2:14

[GoogleCodeExporter]

Issue 140 has been merged into this issue.

Original comment by rodrigo...@gmail.com on 28 Apr 2011 at 4:46

[GoogleCodeExporter]

DroidWall 1.5.1 released! Go get it while it is fresh ;)

Original comment by rodrigo...@gmail.com on 28 Apr 2011 at 6:35

• Changed state: Fixed

[GoogleCodeExporter]

Thanks very much to rodrigo...@gmail.com for building iptables_armv5. Excellent 
work!

If you post another version of iptables_armv5 that supports the MARK target, 
it'd very much appreciated!

Thank you in advance

Original comment by salkint...@gmail.com on 22 May 2011 at 6:41

[GoogleCodeExporter]

@salkint, I don't know when/if I will have some spare time to do that, so you 
might want to try to compile one based on my iptables:
http://code.google.com/p/droidwall/source/browse/#svn%2Ftrunk%2Fexternal%2Fiptab
les

;) cheers

Original comment by rodrigo...@gmail.com on 22 May 2011 at 10:10

[GoogleCodeExporter]

@salkint...@gmail.com, yesterday I compiled iptables 1.4.7 will ALL supported 
features/targets ;)
Just in case you still need it... there you go

Original comment by rodrigo...@gmail.com on 15 Jul 2011 at 1:35

Attachments:

• iptables_armv5

[GoogleCodeExporter]

I had this problem on rooted xperia mini pro sk17i, android 2.3.4
Simply changing the permissions for 
/data/data/com.googlecode.droidwall/app_bin/iptables.armv5 did solve the problem

just added execute permission

Original comment by anas....@gmail.com on 27 Dec 2011 at 12:51