(RADIATOR) AddressAllocator SQL - "confirm" appears disabled

[Orcon Network Coordinator, Mark Mackay]

Was having a look through the code after having some 'out of IP Addresses'
problems -- and noticed that the "confirmed" state doesn't seem to be
implemented.  Is there any ETA on this?

It would be great when "No free IP addresses" occurs, it works through the
'unconfirmed' RADPOOL entries (STATE=1), and uses them in oldest-issued
order, and then the Allocator code only reports an error when all the
available ip addresses are "confirmed" (STATE=2).


Obviously there may be a few problems that occur under that scenario -- so
maybe a 5-minute threshold need to be provided for so cascade doesn't occur
when approaching 'all in use'.

Also - another item to consider (a wish list I guess) -- when two users get
assigned the same IP address on our USR chassis, we get a "Stop" packet with
"NAS-Error" being the Terminate-Cause for the session getting bounced.
Under the Allocator code - this would 'free-up' an IP address I guess,
meaning it would be reused again (causing the same error again). Don't know
if 'NAS-Error' is common to all NAS equipment -- but maybe there's a way to
not free up an IP address if this response occurs.


.........................................................................

Mark Mackay,
Network Coordinator,
Orcon Internet.


===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.