On Fri, 17 Mar 2000, Hugh Irvine wrote:
> > I was wondering if there is a way to make radiator send accounting info to
> > two different dbs. I'm using AuthBy Rodopi and the accounting attributes
> > recorded are minimal. I'd like to be able to log more information to
> > another sql db at the same time. Is this possible?
> >
>
> Sure - chain two AuthBy's like this:
This just gave me an idea. First, what happens if a single request is
handled by more than 1 <AuthBy ...>'s resulting in some mix of accepts and
rejects? Would the first returned result win and be the only one returned
to the client?
We have problems on our Cisco access servers when an <AuthBy RADIUS>
request times out because the radius server it was proxied to is
unreachable or not responding. We thought about trying to hack radiator
to return a reject in these cases...but what happens with AuthByPolicy
ContinueWhileIgnore if multipel <AuthBy ...>'s fork, and one returns a non
Ignore result while the other is still running? Is the remaining <AuthBy
...> killed? I was thinking "what if we did an <AuthBy External> that
just slept for X seconds and returned a reject?" Doing this for every
login would result in too many radiusd processes sitting around unless
they were killed off when the first <AuthBy RADIUS> returned a non-ignore
result.
I think it's getting too late at night for rational thought though.
Can timeout() in AuthRADIUS.pm return ($main::REJECT) to fake a reject
packet?
----------------------------------------------------------------------
Jon Lewis *[EMAIL PROTECTED]*| Spammers will be winnuked or
System Administrator | nestea'd...whatever it takes
Atlantic Net | to get the job done.
_________http://www.lewis.org/~jlewis/pgp for PGP public key__________
===
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.
