From: "Jonathan De Graeve" <Jonathan dot De dot Graeve at imelda dot be>

> I was thinking about a nicer solution where the DB is first looked after
> which rules are in use before actually assigning them. But this needs a
> bigger change which I can't do in figurely speaking 5minutes.

> Another solution would be actually writing the FW rules assigned to
> Allowed-IP-address into a db. This would be a very safe solution not
> requiring reboot and allowing proper wrapping.

>ATM a reboot isn't required, it is a recommendation until it is properly
> fixed ;)

Two questions...
First, what "bad thing" can happen when I don't reboot?  I can't think how 
many times I do this quick during the day to solve a problem (usually an AOL 
browser) and could not reboot.
Second, what is the symptom of a wrap?  I think I actually had one in the 
wield the other day.  It was a hotel I have behind m0n0wall running 1.21 
since the day of release without a reboot.  Between 10 - 50 users a day. 
Suddenly no one could log in to the CP but the old allowed IPs were fine. 
It was a busy time, so I had to reboot after very little troubleshooting, 
and it worked fine.

One comment...
If there was some way to reorder the table without login off everyone, that 
would be good.  I can not log people off in production, and often need to 
add ip addresses.

                        Lee