Hello Ray -
I have already replied to this mail, however here it is again.
You will need to check a trace 4 debug from Radiator to see what is
happening - perhaps in conjunction with a debug output from your NAS
equipment.
The most usual causes for duplicate accounting records are congested
Hello Martin -
What you show below looks alright - you should set up a test machine and
test it thoroughly to verify that it is correct.
regards
Hugh
On Monday, May 20, 2002, at 02:16 PM, Martin Edge wrote:
Er, that wasn't meant to send yet.
I have finished what I was saying, below..
Hello,
I've got a radiator (2.19) running on a linux box with about 20 proxy
realms. When one of our proxy users disconnects, Qwests seems to send
about 6 Stop packets all at once. It's almost round-robin, except that
radiator notes that all the packets arrive within a second or two.
Radiator
Poor form to reply to my own email, but there appears to be more
information.
Qwest is actually sending the stop/start packets at 5 second intervals,
and radiator is forwarding them on the the proxy radius server. Qwest
is, I guess, waiting for some sort of acknowledgement and when one isn't
I've started seeing this too, extremely intermittently (though not from
Qwest). I'd be interested in knowing how people clean RADIUS accounting
logs to remove stuff like this to avoid coloring results. Sure, we'd want
to find and fix the problem if possible as to why those are getting in
We have our own NAS units and altough we see duplicates they are not as
excessive as you describe. We eliminate the dupes by placing a UNIQUE-Key on
the Sessionid-NASID-Username fields. This prevents more than one entry for
the same user on the same NAS with the same SessionID. (**extremely**
