Re: rlm_ippool and tcp TIME_WAIT state

Sebastien Cantos wrote:

I’ve noticed that rlm_ippool is nearly always reassigning an IP address that has just been releasing for a new connexion. This cause some TCP connexion problems because of the TIME_WAIT state.

Interesting. The IPs are allocated by a GDBM walk of the database, and use of the first free or expired IP. This will always tend to be the same one hence the repeat allocations. It would in theory be possible to save the key from the last walk, and next time we allocate an IP start from that key and wrap back around, which would allocate IPs in a more round-robin fashion.