Closed GoogleCodeExporter closed 8 years ago
That is very interesting :|
Could you please try to manually run this command:
/data/data/com.googlecode.droidwall.free/cache/iptables_n1 -L -v
Please post the results here.
Thanks
Original comment by rodrigo...@gmail.com
on 25 Apr 2011 at 7:37
Oh, forgot to say that this command should be executed with the iptables binary
shipped with DroidWall (not the synlink you did) :)
Original comment by rodrigo...@gmail.com
on 25 Apr 2011 at 7:38
I tried that before. It's the same output as in screenshot1, except it first
output the default chains and then for some reason the process gets stopped.
When I press ENTER again, the rest of the output (of the stopped process) gets
flushed:
/data/data/com.googlecode.droidwall.free/cache # ./iptables_n1 -L -v
Chain INPUT (policy ACCEPT 22379 packets, 16M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 19528 packets, 2096K bytes)
pkts bytes target prot opt in out source destination
[1]+ Stopped (signal) ./iptables_n1 -L -v
/data/data/com.googlecode.droidwall.free/cache # <JUST PRESSING ENTER HERE>
[1]+ Illegal instruction ./iptables_n1 -L -v
Original comment by dominik....@gmail.com
on 25 Apr 2011 at 9:06
Could you please try the iptables binary that I attached on issue 139 ?
I compiled that one myself, hope it works :)
If that one does not work, please post your /proc/cpuinfo
Thanks
Original comment by rodrigo...@gmail.com
on 27 Apr 2011 at 9:48
I tried your iptables_armv5 and it works like a charm. Thank you!
Anyway, here's my /proc/cpuinfo of my LG-P990 (Optimus 2X):
/ $ cat /proc/cpuinfo
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 1998.84
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 0
Hardware : Tegra 2 Development System
Revision : 0000
Serial : 0000000000000000
Original comment by dominik....@gmail.com
on 28 Apr 2011 at 4:21
Merging this into issue 139 then ;) will be fixed on the next version
(DroidWall 1.5.1)
Original comment by rodrigo...@gmail.com
on 28 Apr 2011 at 4:46
Original issue reported on code.google.com by
dominik....@gmail.com
on 23 Apr 2011 at 10:41Attachments: