On Sat, 23 Feb 2002, Alan DeKok wrote: > Igor Chen <[EMAIL PROTECTED]> wrote: > > I have a problem with radius accounting, seems like other proxy radius > > (old cistron) sends duplicate Stop queries, and sometimes even Stop > > queries with equal acctsessionid,username,nasipaddress but wrong time (set > > to now(). > > Then the server should probably ignore the duplicate STOP packets. They are not always actually duplicate as i wrote above
> > Can anyone tell me, is any workaround for that situation? How can i > > recieve (or write to sql) only first Stop for that session? > > Maybe i can use acct_unique but i do not know what can be unique key :-\ > > Use the attributes which don't change between accounting packets. > You listed them above: acctsessionid,username,nasipaddress The problem is that cisco nas sometimes reloads and starts counting acctsessionid from 0 again. Really unique should be any datetime attribute... > Get the SQL module to do an 'insert' of the stop record if it isn't > there, and NOT to do an 'update' if the record already exists. If it inserts record, it iserts it without knowing Acct-Start-Time. So we get absolutely useless record in database :-\ > Alan DeKok. > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > -- cron-ripe - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
