dynip/statip IP overflow

[Gunther Mayer]

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.
That makes no sense. According to the above 192.168.174.128 is neither 
in the dynip range nor the last one. .129 would be the very first one 
and .254 the last. Could you please give us a real example of "wrong" ip 
address assignment?

I'm operating a large network on v0.9.11 with almost identical setups 
(also a statip .0/25 subnet with dynip .128/25), have experienced no 
issues to date and in fact have just verified with one of the logfiles 
of a busy site that indeed chilli wraps around correctly.

Gunther