Hello Valentin -
On Thursday 08 March 2001 07:05, Valentin Tumarkin wrote:
> Hi,
>
> Will Radiator 2.18 include update to the AddressAllocatorSQL.pm module so
> that 'confirm' function actually confirms IP allocation (in
> Radiator 2.17.1 it just returns 'ACCEPT') ?
>
> My worry is that in case of some NAS/network/Server performance problem a
> sitiation can occur, where multiple, duplicate Access-Request packets will
> be sent to the Radius server, which Radiator will not be able to
> De-Duplicate. That will result in AddressAllocatorSQL allocating a number
> of IP Addresses for a single user.
>
> The full solution to the above problem would probably also include puting
> NAS-IP-Address:NAS-Port pairs in the RADPOOL table, and checking for
> existing leases for a NAS-IP-Address:NAS-Port pair before giving out a
> new lease (simular to Session Database).
>
Mike and I discussed this at great length and there was much subsequent
discussion on the mailing list.
The reason the code does what it does currently is because it is the lesser
of two evils. This is because if you miss an accounting start, and reallocate
an address that is already in use, very bad things happen. This to us seems
worse that having a few IP addresses marked as used until the lease period
expires.
Note that there is a very good way to deal with the duplicate problem, and
that is simply by specifying an appropriate DupInterval in the Client clause.
I have used this approach very successfully in the past.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.
