Hello Mark -
On Mon, 13 Nov 2000, Mark - Orcon Support wrote:
> Had a problem where a start session of a customer was ignored because a stop
> packet using the same identifier 25 minutes earlier.
>
> Thus I was wondering what time has to elapse between session packets before
> it's classed as a new session? And is there any way to control this?
>
Could you give me a bit more detail please?
A new session should never be ignored - the only thing that can happen is a
rejection due to simultaneous use limits being incorrectly enforced because a
stop record was missed.
The way to control this is with the NasType parameter in the Client clause to
have Radiator query the NAS to verify the existence of suspect sessions.
hth
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.
