On Thu, 15 Jun 2000, Mike McCauley wrote:
> On Jun 15, 8:33am, Hugh Irvine wrote:
> > Subject: Re: (RADIATOR) Sim. use control by Ping
> >
> > Hello Clement -
> >
> > This is exactly what one of our other customers has done - he added a
> > "DeleteIPQuery" to the session database. We haven't yet included this in
> > Radiator because we are concerned about the potential for the session
> > database
> > to become corrupted in some circumstances.
> >
> > I've forwarded your thoughts to Mike.
>
> The DeleteQuery gets run just before adding a new session. I wonder if
> the right thing is to alter the DeleteQuery so it deletes the IP
> address too:
>
> DeleteQuery delete from RADONLINE where (NASIDENTIFIER='%N' and
> NASPORT=0%{NAS-Port}) or FRAMEDIPADDRESS = '%{Framed-IP-Address}'
>
> Thoughts?
Hmm, this may not be a good solution for everyone. On my NASes, if I have
a customer who is connected via multilink or ISDN, their IP may be listed
more than once. Maybe modify the statment like this:
DeleteQuery delete from RADONLINE where (NASIDENTIFIER='%N' and \
NASPORT=%{NAS-Port}) or (USERNAME <> '%n' and FRAMEDIPADDRESS = \
'%{Framed-IP-Address}')
This will cover a few more cases... the one notable exception, is where
you have a customer who has a static IP address, who is allowed to
multilink (using Simultaneous-Usage limits), but who instead dials in
using two seperate systems. I don't think there's much one can do about
that case...
- D
===
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.
