(RADIATOR) qwest and stop packets

[Leon Oosterwijk]

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** rare
occurance within one month). Because we rotate out the accounting records
each month we minimize the possibility of this happening. You would be wise
to eliminate the duplicates in your network, but because of the nature of
UDP you will never be able to fully rule out the possilibity of dupes. You
will need some kind of unique-fier to get rid of your dupes. 


Sincerely, 

Leon Oosterwijk
ISDN-NET Inc. 
(615) 221-4200
http://www.isdn.net
 

> -----Original Message-----
> From: Chris M [mailto:chrism at peakpeak.com] 
> Sent: Monday, May 20, 2002 2:10 PM
> To: radiator at open.com.au
> Subject: Re: (RADIATOR) qwest and stop packets
> 
> 
> 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 
> there, but it seems like preemptively trying to be defensive 
> and detecting 
> or cleaning those out of the ACCOUNTING table would be a good 
> idea and a 
> best practice.
> 
> As in, what do you do, some kind of DISTINCT statement in 
> your  accounting 
> queries to select a bunch of records and INSERT them into a 
> new "scratch" 
> table, then DELETE all the original records and move the 
> records from the 
> "scratch" table back into the regular table?  In other words, 
> how would you 
> go about doing this maintenance of cleaning the table to remove the 
> spurious entries?
> 
> Chris
> 
> At 09:57 AM 5/20/2002 -0700, you wrote:
> >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 logs each of these packets in sequence and as a result our 
> >proxy users appear to have been online anywhere from 2 to 6 
> more than 
> >they really have.
> >
> >What I'm trying to figure out is, is radiator doing what 
> it's supposed 
> >to do (ie. forwarding every stop packet it gets even if 6 in 
> a row are 
> >for the same session id)?  Or more specifically, is the problem with 
> >qwest's borked nas's sending 6 stop packets at once?
> >
> >I can send trace4 log exerpts as well as sql logs if you want.
> >
> >Thanks for your help.
> >
> >-Peter
> >
> >--
> >Peter Moody             Systems Administrator
> >peter at enabledsites.com
> >:wq
> >
> >===
> >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.
> 
> 
> 
> ===
> 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.
> 
===
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.