Hello Carlos -
On Fri, 24 Nov 2000, Carlos Canau wrote:
>
> The diff between the packets is two to three seconds. I think
> that the problem isn't on the NAS... maybe something on the NAS config
> can be tuned somehow... but,...
> I've seen also sessions of two seconds getting START, STOP,
> and again a START... maybe a re-transmit... it block the port on the
> table.
>
> >
> > > The NAS are c5300 and the NASPORT can't be trivially used to
> > > do a snmpget into a variable (I'm using 'radius-server attribute
> > > nas-port format c', but the others are the same with respect to
> > > NASPORT on RADONLINE...).
> > >
> >
> > In any case, Radiator already does sanity checking by removing stale records
> > when the next access request arrives for that NAS/NASPORT pair.
>
> I'm not yet using 2.17.x ...
>
The Radiator code has always done the above.
> Thu Nov 23 17:27:03 2000: ERR: do failed for 'insert into RADONLINE (USERNAME,
>NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE,
>SERVICETYPE) values ('[EMAIL PROTECTED]', '10.10.10.19', 6, '6D000C19', 975000423,
>'10.10.10.134', 'Async', 'Framed-User')': Duplicate entry '10.10.10.19-6' for key 1
> Thu Nov 23 17:27:03 2000: ERR: do failed for 'insert into RADONLINE (USERNAME,
>NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE,
>SERVICETYPE) values ('[EMAIL PROTECTED]', '10.10.10.19', 6, '6D000C19', 975000423,
>'10.10.10.134', 'Async', 'Framed-User')': Duplicate entry '10.10.10.19-6' for key 1
> Thu Nov 23 18:06:16 2000: ERR: do failed for 'insert into RADONLINE (USERNAME,
>NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE,
>SERVICETYPE) values ('[EMAIL PROTECTED]', '10.10.10.19', 6, '6D000C24', 975002776,
>'10.10.10.135', 'Async', 'Framed-User')': Duplicate entry '10.10.10.19-6' for key 1
> Thu Nov 23 18:06:16 2000: ERR: do failed for 'insert into RADONLINE (USERNAME,
>NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE,
>SERVICETYPE) values ('[EMAIL PROTECTED]', '10.10.10.19', 6, '6D000C24', 975002776,
>'10.10.10.135', 'Async', 'Framed-User')': Duplicate entry '10.10.10.19-6' for key 1
> Thu Nov 23 20:18:50 2000: ERR: do failed for 'insert into RADONLINE (USERNAME,
>NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE,
>SERVICETYPE) values ('[EMAIL PROTECTED]', '10.10.10.1', 45, '00000414', 975010730,
>'10.10.140.233', 'Async', 'Framed-User')': Duplicate entry '10.10.140.1-45' for key 1
> Thu Nov 23 20:18:50 2000: ERR: do failed for 'insert into RADONLINE (USERNAME,
>NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE,
>SERVICETYPE) values ('[EMAIL PROTECTED]', '10.10.10.1', 45, '00000414', 975010730,
>'10.10.140.233', 'Async', 'Framed-User')': Duplicate entry '10.10.140.1-45' for key 1
>
> I have to remove those by hand from the table...
>
The above look like accounting records with no access request prior to them
arriving.
> >
> > If you want to manually remove records from the session database, you can
> > simply use radpwtst to send the corresponding Stop record to flush the entry.
>
> I got several of them daily... from different NAS's. I'm
> thinking of doing a replace into or in doing some crontab script to
> periodically clean the table... or something that tails forever the
> logfile looking for entries to clean ... :-/////
>
I will need to see a trace 4 showing enough information to see what is going on.
It is possible that these accounting records are for failed access attempts and
perhaps you can set up a special Handler to trap them before they cause a
problem.
hth
Hugh
--
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.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
