Re: (RADIATOR) AddressAllocator SQL - "confirm" appears disabled

[Orcon Network Coordinator, Mark Mackay]

Thanks for the reply Hugh. I'll describe a bit more what I envisage (and see
if that is where the Radiator code is heading - or if I can nudge it in that
direction):


For the AddressAllocator code:

1) Access-Request comes in
    - standard auth/etc methods
    
    - AddressAllocator code called:
        - sets STATE=1 (allocated) for the relevant RADPOOL YIADDR entry

    - Access-Accept returned (with IP-YIADDR added to the reply)


2) Accounting-START-Request comes in
    - standard accounting code called

    - AddressAllocator code called
        - sets STATE=2 (confirmed) for the relevant RADPOOL YIADDR entry

    - Accounting-Accepted returned

3) Accounting-STOP-Request comes in
    - standard accoutning code called

    - AddressAllocator code called

       - if Terminate-Cause = NAS-Error (or similar hint for double-
            assigned connection), code is Ignored (and IP left to expire)
        - else, set STATE=0 (free) for the relevant YIADDR

-------------------------

Global notes about the AddressAllocator code:

- first: YIADDR is chosen from STATE=0 in oldest-date order
- second: (if no STATE=0), oldest-date STATE=1 is used (ie. address
allocated, but Start packet not received)
- third: no addresses (STATE=0 or 1) -- thus return error. As a side note,
would be good to have a Hook available here to mail the administrator, set
an SNMP error or something.

- other parameters (such as Lease/Expire after 24 hours/etc to still apply)
- also, might be good to catch a 'Framed-IP-Address-xx.xx.xx.xx' in a reply
packet and to set the YIADDR=1/2 for that ip. (so that a static IP
assignment leases a 'RADPOOL' address if it doubles up.  [not necessary with
structured ip address pools, but a good addition perhaps].


Hope this explains it a bit more, and I don't see the code to be too hard to
implement.  I'd be happy to take a bash at it if there's not any changes
planned to the code in the near future from your end -- but I'll confess I'm
not that up to the play on object-perl programming]

Appreciate your feedback either way (ie. not likely or is likely to be
implemented), as I'll probably need to put some of this functionality into
my config soon - and may need to right to the RADPOOL database through
existing  hooks.

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

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.