search

deadash / droidwall

Automatically exported from code.google.com/p/droidwall
0 stars 0 forks source link

IPTables: Protocol wrong type for socket after upgrade to 1.5.1 #142

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Update to latest droidwall 1.5.1
2. Attempt to turn on Firewall
3. Receive this error:
Error applying IPTables rules. Exit code: 1
IpTables v1.3.7
IPTables: Protocol wrong type for socket

What is the expected output? What do you see instead?
I expected it to work as it did in 1.5.0.
I tested this regression by downgraded, and indeed it works fine.

What version of the product are you using? On what operating system?
Samsung Intercept - Froyo 2.2

Please provide any additional information below.

It's simply a regression, works in previous versions. I found out about the bug 
when I updated a few hours ago.

Original issue reported on code.google.com by gaming...@gmail.com on 28 Apr 2011 at 8:57

GoogleCodeExporter commented 8 years ago 
I expected that the new iptables binary would work on all devices :(
could you please post your /proc/cpuinfo here?
Thanks!

Original comment by rodrigo...@gmail.com on 28 Apr 2011 at 10:52

GoogleCodeExporter commented 8 years ago 
Here you are:
http://pastebin.com/C0wuUhyC

Original comment by gaming...@gmail.com on 30 Apr 2011 at 3:20

GoogleCodeExporter commented 8 years ago 
Can you please test with the attached development version of DroidWall? This 
one has a difference iptables version, compiled using the Android NDK.
Thanks!

Original comment by rodrigo...@gmail.com on 14 Jul 2011 at 7:49

Attachments:

GoogleCodeExporter commented 8 years ago 
Hmm, afraid not it's still giving the error. :/

Error: applying Iptables rules.
Exit Code: 1

Iptables v.1.3.7
Iptables: protocol wrong type for socket.

Original comment by gaming...@gmail.com on 14 Jul 2011 at 10:43

GoogleCodeExporter commented 8 years ago 
Thanks for testing it for me. I really don't know why it does not work on your 
phone!
Would you mind posting the output of "show rules" with this dev version?
Screen-shots/photos are fine if you don't wanna type that much of text ;)

Thanks again

Original comment by rodrigo...@gmail.com on 15 Jul 2011 at 12:13

GoogleCodeExporter commented 8 years ago 
I did a bit more testing, and I think I've found a resolve in this latest 
version. :D
If you "Clear Cache" on the old version, before uninstalling the old and 
installing the new "dev" version, it does not suffer the wrong protocol bug. 
Now that I've cleared this cache it seems to be working perfectly. 

If you still need me to duplicate the bug I can test installing old version, 
applying rules, uninstalling, installing new (without cache clear) and I'm 
pretty sure it will do it again. At the moment I'm just enjoying the working 
latest version. :P

Original comment by gaming...@gmail.com on 17 Jul 2011 at 2:44

GoogleCodeExporter commented 8 years ago 
Those are good news! :D
That quite of makes sense... If the app data was not removed with the 
uninstall, the new "dev" version was actually using an old iptables binary ;)

I'm glad that it works now!
I will keep this opened just to track it for the next release.

Original comment by rodrigo...@gmail.com on 17 Jul 2011 at 2:18

GoogleCodeExporter commented 8 years ago 
Hello, would you mind testing the attached version before I publish an official 
update on the Market?
You don't need to "clear data" with this one ;)

This one has iptables 1.4.10, but it was compiled using the same procedure than 
the other one.
Thank you very much in advance.

Original comment by rodrigo...@gmail.com on 20 Jul 2011 at 6:03

Attachments:

GoogleCodeExporter commented 8 years ago 
Nah, nevermind. I just published DroidWall 1.5.2 on the Market.
I am confident that it will work :) but in case it does not, please feel free 
to reopen this issue.

Thanks!

Original comment by rodrigo...@gmail.com on 20 Jul 2011 at 7:25