Hello Mark -
On Tue, 14 Nov 2000, Mark - Orcon Support wrote:
> Thanks Hugh -
>
> We're not enforcing any simultaneous use limits -- I couldn't think of a
> better word to describe sessions for 'packets'. The following seemed to
> happen:
>
> 16:37:13 -> Auth-request (Identifier 225)
> 16:37:13 <- Access-Accept (Identifier 225)
>
> 16:37:13 -> Accounting-Request [start] (Identifier 218)
> LOG ENTRY: "INFO: Duplicate request id 218 received from xx.xxx.xxx.xx:
> ignored
>
> .............
>
> Only entry in the log prior to this was at 16:01:23 - an Accounting Request
> (Identifier 218) for a stop packet for a different user.
>
Thanks for the clarification - makes much more sense now!!
Well, in this case what is the DupInterval for the Client set to? It should be
set to a reasonable (smallish) number of seconds (defaults to 2). Note - this
should *not* be set to 0, which may be the source of your problem.
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.
