(RADIATOR) Duplicate request id: ignored

[Hugh Irvine]

Hello Dave -

You normally configure the timeout and retransmit values in your NAS(s) so 
there will only ever be a small number of retransmissions. If your NAS sends 
more requests than you tell it to, it is an issue that must be addressed by 
your supplier.

BTW - the DupInterval configured in the Client clauses defines the number of 
seconds in the sliding window during which a retransmission is considered a 
duplicate.

I suggest you read the RFC's for further information (included in the 
Radiator distribution in the "doc" directory).

regards

Hugh


On Thu, 27 Jun 2002 07:04, Dave Kitabjian wrote:
> "Wed Jun 26 16:03:16 2002: INFO: Duplicate request id 87
> received from 10.52.0.1(1026): ignored"
>
> This message was logged for an Accounting request that was clearly
> retransmitted since it had a large Acct-Delay-Time value.
>
> But if Radiator keeps ignoring the request, the NAS will keep
> retransmitting, and the circle of life will go on and on and on...
>
> Does the RFC say to ignore dups? Wouldn't it make more sense to Reject
> them somehow? Or, if the original one was already processed
> successfully, it could simply send back an Accept and then discard it as
> a dup?
>
> Dave
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.

-- 
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.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.