getsockopt for multiport failed strangely: Not such file or directory about droidwall HOT 13 CLOSED

Device is HTC Desire.

Device is rooted, other rooted soft works perfectly.

Me too, rooted Nexus One running Froyo FRF50.

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

[deleted comment]

[deleted comment]

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.

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

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.

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 :)

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.

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

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