(RADIATOR) Stuck in RADONLINE

[Mike Gomez]

Hugh,

Thank you so much!  I've implemented this today and I believe it's doing what 
I need from my tests.  Now to just wait until peak time and see if we get 
anyone stuck in RADONLINE.

Thanks again,
Mike

On Friday 11 August 2006 18:57, Hugh Irvine wrote:
> Hello Mike -
>
> You can alter the DeleteQuery in your session database to use the
> calling station id instead of the NAS and NAS-Port.
>
> See section 5.8.4 in the Radiator 3.15 reference manual ("doc/
> ref.html").
>
> regards
>
> Hugh
>
> On 11 Aug 2006, at 23:39, Mike Gomez wrote:
> > Hiya,
> >
> > I've got a bit of an issue, and I'm hoping that Radiator's wonderful
> > configurability can help me out. :)  The situation I'm in is that
> > we buy
> > dialup modem ports from a company that gets them through Level3.
> > Radius
> > requests for our users go from Level3's modem pools to a radius
> > server at the
> > company we purchase them from and then get forwarded to our
> > Radiator server.
> > The problem that I run into is that we don't always get stop
> > records for our
> > users that come in via this route (I've done a Trace 4 and see
> > nothing come
> > through in the logs for a stop record), and since we have
> > Simultaneous-Use=1
> > in their records, they can't authenticate next time because they're
> > still in
> > the RADONLINE table.
> >
> > We *do* get callerid info when users get connected, so what I
> > wanted to try
> > figuring out is this. Is there some way to tell Radiator that if a
> > user tries
> > to authenticate, and the callerid info that is passed matches the
> > callerid
> > info in the RADONLINE table for that user, to delete the old entry
> > from
> > RADONLINE and allow them access?  Or is there a better way, like
> > passing the
> > info to a script?
> >
> > Thanks!
> > --
> > Mike Gomez
> >
> > --
> > 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.
>
> NB:
>
> Have you read the reference manual ("doc/ref.html")?
> Have you searched the mailing list archive (www.open.com.au/archives/
> radiator)?
> Have you had a quick look on Google (www.google.com)?
> Have you included a copy of your configuration file (no secrets),
> together with a trace 4 debug showing what is happening?

--
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.