iptables: Protocol wrong type for socket

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open DW
2. press menu
3. press "Firewall Disable" to enable DW

What is the expected output?
for rules to be applied

What do you see instead?
a popup saying iptables: Protocol wrong type for socket

What version of the product are you using? On what operating system?
HTC Desire HD
CyanogenMod 7 (android 2.3.2) nightly 20110128
DroidWall 1.4.6

Please provide any additional information below.
D/WifiService( 1301): acquireWifiLockLocked: WifiLock{NetworkLocationProvider 
type=2 binder=android.os.BinderProxy@40893898}
D/DroidWall( 3600): Changing enabled status to: true
D/DroidWall( 3600): Applying rules.
D/su      ( 3613): 10029 com.googlecode.droidwall.free executing 0 
/data/data/com.googlecode.droidwall.free/cache/droidwall.sh using shell 
/system/bin/sh : sh
I/ActivityManager( 1301): Start proc com.noshufou.android.su for broadcast 
com.noshufou.android.su/.SuNotificationReceiver: pid=3615 uid=10023 gids={1015, 
3003}
D/szipinf ( 3615): Initializing inflate state
D/su      ( 3622): 10029 com.googlecode.droidwall.free executing 0 
/data/data/com.googlecode.droidwall.free/cache/droidwall.sh using shell 
/system/bin/sh : sh
E/DroidWall( 3600): iptables v1.3.7
E/DroidWall( 3600): iptables: Protocol wrong type for socket
D/DroidWall( 3600): Failed - Disabling firewall.

Original issue reported on code.google.com by BUGabu...@gmail.com on 28 Jan 2011 at 4:02

[GoogleCodeExporter]

I strongly believe that this ticket should be opened on CyanogenMod... not here.
The kernel on CM7 was probably not configured correctly for iptables to work.

Since those are nightly CM7 builds we probably should just wait for a 
stable/beta one before complaining to Mr. Cyanogen ;)

PS: I'm running stock Android 2.3.2 on my Nexus S and DroidWall works just 
fine, so it is not any kind of incompatibility with GingerBread.

Original comment by rodrigo...@gmail.com on 28 Jan 2011 at 4:52

• Changed state: WontFix

[GoogleCodeExporter]

thanks for the fast reply.
I'm part of the development of CM.
I'll let kali (mantainer of DHD) know.

Original comment by ferna...@bugabundo.net on 28 Jan 2011 at 5:02

[GoogleCodeExporter]

FYI, this is reproducible on cyanogenmod 7-rc2 (vision)

http://code.google.com/p/cyanogenmod/issues/detail?id=2925

===
Error applying iptables rules.
Exit code: 1

iptables v1.3.7
FIX ME! implement getprotobyname() bionic/libc/bionic/stubs.c:378
iptables: Protocol wrong type for socket

Original comment by chris.ku...@gmail.com on 10 Mar 2011 at 8:04

[GoogleCodeExporter]

yeah i've been having this alot.
usually i clear Data for droidwall and it gets fixed for a while, and then 
returns

Original comment by ferna...@bugabundo.net on 10 Mar 2011 at 11:58

[GoogleCodeExporter]

thanks ferna... your hint helped me. I had the same problem and clearing cache 
and data of droidwall made it work again on cm7. so i think the problem is in 
droidwall not in cm. 
PS: i love droidwall & cm7!

Original comment by bernd.bu...@gmail.com on 21 Apr 2011 at 6:48

[GoogleCodeExporter]

This seems to be a mix of DroidWall + CM7 problem.

DroidWall problem: Binary files are installed in the "cache" folder, and 
running any kind of "fix permissions" script will mess the permission of the 
files. This has been fixed already (for the next version)

CM7 problem: For some unknown reason, CM7 is shipping with a VERY outdated 
iptables binaries. So when DroidWall fails to use the one in the "cache" 
folder, it attempts to use the system one (and fails because it is too old).

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