getsockopt for multiport failed strangely: Not such file or directory

[GoogleCodeExporter]

I have install droidwall on Android 2.2, it starts normally, shows me the 
software list. But when I click "Apply rules", it shows the error:
----------------
Error applying iptables rules. Exit code: 1
getsockopt for multiport failed strangely: Not such file or directory
getsockopt for multiport failed strangely: Not such file or directory
getsockopt for multiport failed strangely: Not such file or directory
getsockopt for multiport failed strangely: Not such file or directory
iptables: Protocol wrong type for socket
----------------
And "OK" button

After that in "Show rules" I see in OUTPUT:
getsockopt for multiport failed strangely: Not such file or directory
getsockopt for multiport failed strangely: Not such file or directory
getsockopt for multiport failed strangely: Not such file or directory

Where is the problem and how I can fix it?

Original issue reported on code.google.com by Mur...@gmail.com on 15 Jun 2010 at 5:37

[GoogleCodeExporter]

Device is HTC Desire.

Original comment by Mur...@gmail.com on 15 Jun 2010 at 5:42

[GoogleCodeExporter]

Device is rooted, other rooted soft works perfectly.

Original comment by Mur...@gmail.com on 15 Jun 2010 at 5:45

[GoogleCodeExporter]

Me too, rooted Nexus One running Froyo FRF50.

Original comment by tdh...@gmail.com on 25 Jun 2010 at 5:07

[GoogleCodeExporter]

me too, acer liquid... running eclair lcr 1.7

Original comment by zachmil...@gmail.com on 7 Jul 2010 at 9:20

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I had a chance to test a rooted Nexus One running Froyo - unfortunately this 
seems to be a kernel problem (most likely compilation options)  and there is 
not much we can do to make Droid Wall work on it right now.
Droid Wall is merely an iptables front-end - if iptables is not working on the 
device, Droid Wall won't work either.

Original comment by rodrigo...@gmail.com on 7 Jul 2010 at 12:46

[GoogleCodeExporter]

This is a duplicate of issue 27 - please use that issue from now on.

Original comment by rodrigo...@gmail.com on 7 Jul 2010 at 12:49

• Changed state: Duplicate

[GoogleCodeExporter]

Ok but this bug has the actual error messages. The other report is less 
informative/google-friendly.

Anyway, I think the problem is that the newest kernel doesn't have 
CONFIG_NETFILTER_XT_MATCH_MULTIPORT. That can be compiled as a module so it may 
not be too hard to get to work.

Original comment by tdh...@gmail.com on 7 Jul 2010 at 1:20

[GoogleCodeExporter]

I think there is android kernel bug, if it works in 2.1 version and stops 
working in 2.2, and I post issue in android project: 
http://code.google.com/p/android/issues/detail?id=9586
Let's go to vote for it :)

Original comment by Mur...@gmail.com on 7 Jul 2010 at 2:01

[GoogleCodeExporter]

In ROM OpenDesire 1.6b version (for HTC Desire) author add support for 
multiport.
And after upgrade to this version multiport error go away:
[CODE]getsockopt for multiport failed strangely: Not such file or 
directory[/CODE]
But this error is still here:
[CODE]iptables: Protocol wrong type for socket[/CODE]
What does it mean and how I can fix it?

P.S. As I see, firewall goes to works, in many apps I got errors when 
connecting to internet which I don't check in DroidWall.

Original comment by Mur...@gmail.com on 14 Jul 2010 at 3:44

[GoogleCodeExporter]

At least on my HTC Desire (which I upgraded to Android 2.2 manually)
the problem apparently was not the kernel (nor a kernel module) but an outdated 
iptables version. See https://code.google.com/p/droidwall/issues/detail?id=27

Original comment by DvO...@gmail.com on 13 Aug 2010 at 6:00

[GoogleCodeExporter]

Fixed on opendesire 2.2 version, all works successfully for me.

Original comment by Mur...@gmail.com on 15 Aug 2010 at 5:27