dynip/statip IP overflow

[wlan at mac.com]

Hi Oliver,

Are you by chance using either dhcpstart or dhcpend options? What  
version of chilli are you using? Check "chilli --help" to see if  
dhcpstart/dhcpend have default values (in the current svn, they  
default to '0' for disabled). If you are indeed using dhcpstart/ 
dhcpstop, make sure the range does NOT include the uamlisten IP...  
(so, if that is .1, use dhcpstart=2 and dhcpend=127).

David

On Jun 1, 2008, at 12:10 AM, Oliver Hinckel wrote:

> Hello,
>
> we're using dynip and statip in our chilli setup and noticed a  
> strange behaviour. When clients connect to our access point they'll  
> get a dynip from chilli. When another client connects to the access  
> point he'll get the next free IP address from the dynip network.  
> That all is OK.
>
> The problem is, that in case a client get's the last free dynip  
> from the dynip network and another client connects to the access  
> point, he'll get an IP address out of the dynip range.
>
> E.g. we have the following setup
> dynip 192.168.174.128/25
> statip 192.168.174.0/25
>
> In case a client will get the dynip address 192.168.174.128, the  
> next client will get 192.168.175.1. It seems that the IP address is  
> just increased by one without checking against the dynip network  
> mask. This seems like an "overflow" too me.
>
> Anyone noticed this already? Is there a fix for it?
>
> Thanks for feedback.
>
> Greetings
> Oliver Hinckel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
> For additional commands, e-mail: chilli-help at coova.org
> Wiki: http://coova.org/wiki/index.php/CoovaChilli
> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>