Rules do not get applied reliably on startup

[GoogleCodeExporter]

1. Boot the phone
2. DroidWall -> Show rules (empty/stock chains)

It's a 50/50 chance the rules will be applied by droidwall at system startup. 
Sometimes they are applied, sometimes not. 
I've found at least one more user in market comments that described exactly the 
same issue.

If i'll find something useful in logcat i will add it.

Droidwall v1.5.7
Android 2.3.7 CM7.2 (final)
Huawei U8510 (ARMv6/MSM7227/MDPI/HVGA)

Original issue reported on code.google.com by Ris...@gmail.com on 1 Jul 2012 at 6:08

[GoogleCodeExporter]

I've rebooted and logged three times now but droidwall worked properly so far. 
The bug may depend on installed apps that get loaded during bootup (kicking 
droidwall too fast). I get some logcat 'infos' due to low memory even though 
droidwall set the rules properly in that boot run.

07-01 21:31:50.720: I/ActivityManager(370): Process 
com.googlecode.droidwall.free (pid 692) has died.
07-01 21:31:50.720: I/ActivityManager(370): Low Memory: No more background 
processes.

Original comment by Ris...@gmail.com on 1 Jul 2012 at 8:02

[GoogleCodeExporter]

Issue confirmed on Galaxy W with DroidWall 1.5.7.
Sina News app should be blocked, but able to download news on startup. Later 
it's blocked alright.

Original comment by gbos...@gmail.com on 20 Jul 2012 at 4:33

[GoogleCodeExporter]

A fix for this (on cyanogen and most custom roms at least) is to put the 
following in /system/init.d/20firewall
## snip
if [ -e "/data/data/com.googlecode.droidwall.free/app_bin/droidwall.sh" ]; then
  . /data/data/com.googlecode.droidwall.free/app_bin/droidwall.sh
fi
## snip

This will -always- execute as it does so via init, not zygote and all the 
OOM/intent cruft. YMMV; I've written my own firewall script (no gui, it takes 
app.package.names from /data/fw.allow), and am not sure how droidwall.sh will 
handle $PATH, etc.

Original comment by atomicdryad on 22 Jul 2012 at 10:36

[GoogleCodeExporter]

'Droidwall.sh' may be started always during startup this way but it doesn't 
change the iptables in any way. It doesn't help.

Original comment by Ris...@gmail.com on 22 Jul 2012 at 11:26