On Thu, 24 Feb 2000, tom minchin wrote:
> On Wed, Feb 23, 2000 at 12:17:44PM -0600, David Lloyd wrote:
> > On Wed, 23 Feb 2000, Mike McCauley wrote:
> >
> > > Hi David,
> > >
> > > Radiator only ever contacts the NAS when it has to: when a user logs in, and
> > > the session database thinks they are at their sim-use limit already. That means
> > > that Radiator only checks the NAS occasionally.
> > >
> > > At DEBUG (level 4), Radiator prints a message when it checks the NAS:
> > > "Checking if user is still online: ....."
> > > If it turns out that Radiator conludes the user was not really online when in
> > > fact the session database said they were, it prints out another message at
> > > NOTICE (level 3):
> > > "Session for $name at $nas_id:$nas_port has gone away"
> >
> > Does it do anything if the SNMP query failed?
> >
>
> Yeah, you get an error (at level 4). Basically just the error from snmpget -
> ie wrong community, can't lookup that particular port (eg ISDN on Cisco).
> The user is allowed to continue past the simuse limitation if there's an error.
Oh, okay... so if I'm geting a lot of incorrect 'Simultaneous use'
violations, then it's likely I'm getting misinformation from my NAS?
I think I'll mod the source so that those messages show up on tracelevel
3. :-) I don't like all those packet dumps and stuff....
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
