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 ;)
 
 
J.


________________________________

Van: Dinesh Nair [mailto:dinesh at alphaque dot com]
Verzonden: di 28/03/2006 15:10
Aan: Jonathan De Graeve
CC: MonoWall-Developers List
Onderwerp: Re: [m0n0wall-dev] Captive Portal - Allowed Ip Addresses





On 03/28/06 17:27 Jonathan De Graeve said the following:
> allowed-ip-addresses should be rebuilded starting from 10000. ATM this
> isn't done, new rules will be added with a later rule (coming from the
> nextrule file)

right, so eventually the rules will wrap around. however, forcing a
sysreboot.reqd for each addition/modification to Allowed IP would be a
little less user friendly. howabout keeping track of this wrap around
counter limit in code and only forcing a reboot (createding of
sysreboot.reqd in /var/run) when the limit is reached. otherwise, dont need
a reboot.

--
Regards,                           /\_/\   "All dogs go to heaven."
dinesh at alphaque dot com                (0 0)    http://www.alphaque.com/
+==========================----oOO--(_)--OOo----==========================+
| for a in past present future; do                                        |
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo "The opinions here in no way reflect the opinions of my $a $b."  |
| done; done                                                              |
+=========================================================================+