On Motorola Milestone rules are not applied after startup/reboot!

[GoogleCodeExporter]

> What steps will reproduce the problem?
1. Apply rules
2. Restart Milestone
3. Try if rules do work

> What is the expected output?

Permitted apps shoulde be able to connect as defined

> What do you see instead?

No network-access (either WLAN or mobile) does work for any app.

> What version of the product are you using?

v1.3.8-dev (latest from market)

> On what operating system?

Android 2.0.1 and 2.1!

I saw this probnlem already with 2.0.1 but was not sure if it is just a
problem of too much playing in the OS... ;) But now I installed 2.1 from
scratch but still the same problem.

As soon as my Milestone has booted completley and I apply the rules
manually, al is working as expected.

Best regards,
Robert

Please provide any additional information below.

Original issue reported on code.google.com by rhc...@gmail.com on 5 May 2010 at 9:47

[GoogleCodeExporter]

I could not reproduce this on a device with android 2.1 - could you please 
paste here
the output of the following command after rebooting?

iptables -L

Thanks in advance

Original comment by rodrigo...@gmail.com on 13 May 2010 at 4:51

[GoogleCodeExporter]

Closing due to inactivity

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

• Changed state: Invalid

[GoogleCodeExporter]

I'm reporting the same issues mentioned by rhcnbg...

after rebooting the rules are not applied. When I click on "show rules" there 
is nothing configured (see picture attached)

where to enter: iptables -L ?
sry but i'm not that familiar with console...

Original comment by hello.ti...@googlemail.com on 1 Aug 2010 at 10:35

Attachments:

• snap20100802_003244.png

[GoogleCodeExporter]

I basically have the same problem with HTC Desire running Android 2.2:
The iptable rules are not automatically restored on reboot.
This might be due to Driodwall not gaining root privilege on reboot, as 
indicated at
http://android.modaco.com/content/htc-hero-hero-modaco-com/299310/problem-with-d
roidwall-solved-solution-inside/#entry0
but the workaround given there using Autostarts did not work for me (at least 
when using Startup Manager instead of Autostarts).

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