Hello Chris -
> >
> >On Fri, 21 Jul 2000, David Lloyd wrote:
> > > On Thu, 20 Jul 2000, Hugh Irvine wrote:
> > >
> > > > A better approach to maintaining session database coherency is to use
> > > > strict checking of the NAS. This is what the NasType parameter is used
> > > > for in the Client clauses (see section 6.4.5 in the Radiator 2.16.1
> > > > reference manual). Note that there is a new NasType of "Ping" in
> > > > 2.16.1 that doesn't actually query the NAS (via finger, who, snmp or
> > > > whatever), but simply pings the IP address (Framed-IP-Address) to see
> > > > if it is still there. An additional trick that is useful is to have a
> > > > special Handler(s) to catch bogus accounting records, and use a
> > > > SessionDatabase INTERNAL in that Handler(s) to keep the bogus records
> > > > away from the SQL session database.
> > > >
> > > > This subject was discussed on the list fairly comprehensively a couple
> > > > of months ago, and several customers have reported very good success
> > > > with an SQL session database (with a custom DeleteQuery to delete a
> > > > record with an IP address and/or a NAS-IP-Address/NAS-Port) and a
> > > > NasType of Ping.
> > >
> > > I agree absolutely... I would not even *consider* using Simultaneous-Use
> > > without setting NASType in the Client clause. Radius accounting is not
> > > exactly the kind of thing that I would call 'reliable'... and it's easy
> > > for the database to get out of sync.
> > >
> > > One feature I think would be neat in Radiator, would be to send it a
> > > signal and have it 'sync-up' the database automatically. That would be
> > > pretty handy...
> > >
> >
> >Hmmmm - how would we do it though? We have enough trouble already....
> >
> >anyway, thanks for the suggestion
> >
> >Hugh
>
>
> Maybe as a timer-based callback, or something that happens periodically...
>
> <SessionDatabase SQL>
> # sync the database to the ports every 360 seconds
> SyncInterval 360
> ...
> <</SessionDatabase SQL>
>
This should be something that is implemented outside Radiator, as the
performance hit due to the overhead will be very significant. If you would like
to write a "periodic session database synchroniser" and contribute the code, we
will be happy to have a look at it and possibly include it in the "goodies".
thanks
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
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.
