Hello Clement -
On Wed, 14 Jun 2000, Clement wrote:
> Hi Mike and Hugh,
>
> Thank you very much for the new feature. Most of the time, it works
> well. However, we just come into a situation when the old IP was
> reallocated and the PING test just failed to tell.
>
> I think the solution is simple. Before writing a new session record,
> remove any existing one with the same IP address. This should be true
> in all situations. An IP address just cannot be used by 2 or more
> connections at the same time. For session data base using SQL, which we
> are, it may need only one SQL statement like this to do the job.
>
> delete * from RADONLINE where FRAMEDIPADDRESS = 'new.ip.addr';
>
> Can you gentlemen make the change? I think it can be a 2 minute job for
> you experts.
This is exactly what one of our other customers has done - he added a
"DeleteIPQuery" to the session database. We haven't yet included this in
Radiator because we are concerned about the potential for the session database
to become corrupted in some circumstances.
I've forwarded your thoughts to Mike.
many thanks for your contributions
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
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.
