DroidWall doesn't work after rebooting

[GoogleCodeExporter]

What steps will reproduce the problem?
1.get Temporary root permission with z4root (it will back to normal state after 
rebooting as it says) ;
2.run droidwall and set rules on apps;
3.it works well, apps can not access network if I have blocked it in droidwall;
4.reboot;
5.rules I've set are lost (get temporary root again and More->Show Rules 
again), although check status of all apps are correctly shown there. Apps can 
still access network.
6.I need get root permission and apply rules again each time.

What is the expected output? What do you see instead?
Rules should still work after rebooting.
Rules get lost and doesn't work automatically.
(Does droidwall need the system always in rooted status? But I don't want my 
phone always work in root mode.)

What version of the product are you using? On what operating system?
Droidwall 1.5.0. Samsung Galaxy S (GT-I9000) with 2.2 Froyo.XXJPO.

Please provide any additional information below.
Check the auto-start status, droidwall auto-starts after booting.

Original issue reported on code.google.com by waynesh...@gmail.com on 20 Mar 2011 at 4:54

[GoogleCodeExporter]

iptables rules are not persistent and must be applied every time the system 
reboots.

Applying iptables rules require root access, so you need root access on boot in 
order to keep rules on reboot.

Sorry.

Original comment by rodrigo...@gmail.com on 21 Mar 2011 at 11:56

• Changed state: Invalid