Hi, Af far as I see when a client gets an IP from pool an entry is created in radippool table: mysql> select * from radippool where expiry_time>now() ; +-----+------------+-----------------+---------------+-----------------+------------------+---------------------+----------+-----------+ | id | pool_name | FramedIPAddress | NASIPAddress | CalledStationId | CallingStationID | expiry_time | username | pool_key | +-----+------------+-----------------+---------------+-----------------+------------------+---------------------+----------+-----------+ | 60 | pool | 1.2.3.4 | 10.0.0.1 | | aadadasdadadaa | 2009-07-10 18:57:52 | user1 | 13242346536 In sqlippool.conf we define lease_time as 3600 seconds. I want to ask what happens after 3600 seconds. I can see that the ip is still in radippool table but date is earlier from now. Does radiusd sends a packet back to NAS so client re-requests a new IP without a traffic disruption ? Or what happens? Regards.
In sqlippool.conf we define lease_time as 3600 seconds. I want to ask what happens after 3600 seconds.
Lease is released (ie. removed from the radippool table).
I can see that the ip is still in radippool table but date is earlier from now. Does radiusd sends a packet back to NAS so client re-requests a new IP without a traffic disruption ?
No. This is not DHCP. Client doesn't need to renew the adress.
Or what happens?
Nothing. If the address is issued to another user while the first one is still conected NAS will not build the connection with the duplicate IP - connection will be refused and second user will have to try again. Lease duration in ippool is a trade-off: short eough not to block IPs in case accounting Stop packets get lost; long enough not to expire during the usual session. On a reliable network you can change it to a day if you are bothered. Ivan Kalik Kalik Informatika ISP
participants (2)
-
Ivan Kalik -
Martin Badie