(RADIATOR) Lease expiry and NAS reboots

[Andrew]

Hi again,

For AuthBy DYNADDRESS with AddressAllocator SQL, is it necessary for any
given dynamic IP pool to be double the size of its userbase? Reason I ask
is that if pool usage was at 95%, then the NAS was reset, there doesn't
appear to be any mechanism for reclaiming the unexpired leased addresses.
In this example only 5% of the users can reauthenticate immediately after
the reboot, which is obviously a problem.

It seems doubling the size of the IP pool to ensure it rarely or never
exceeds 50% utilised would be one way of working around this.  However it
isn't always an option.

Radiator seems to do a good job of detecting NAS reboots. If I'm not
missing something then it would be very useful to have a ClearNasQuery for
AddressAllocator SQL. Combine this with a custom nasidentifier column in
the pool table and a matching AllocateQuery and there could be efficient
deallocation on NAS reboot, even in a multi-NAS environment.

TIA,
Andrew


--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.