Hugh,
Should this be done in conjunction with AccountingHandled (section
6.16.10) ?
Also, our setup is such that we have two AuthBy's per proxy realm
looking something like this:
authby group
AuthByPolicy ContinueAlways
authby sql
IgnoreAuthentication
Hello Peter -
I haven't actually tested this myself (although I will a bit later), so you
should try it as you show below to see if it works. If it doesn't, you should
use the new HostColumnDef with a HostSelect in Radiator 3.1.
regards
Hugh
On Fri, 24 May 2002 03:56, peter moody wrote:
Hello Peter -
The simplest way to do what you describe is this:
# define Realm(s) or Handler(s) with AccountingHandled
Realm ...
AccountingHandled
# define AuthBy RADIUS with IgnoreAccountingResponse
AuthBy RADIUS
IgnoreAccountingResponse
Hello,
I've got a radiator (2.19) running on a linux box with about 20 proxy
realms. When one of our proxy users disconnects, Qwests seems to send
about 6 Stop packets all at once. It's almost round-robin, except that
radiator notes that all the packets arrive within a second or two.
Radiator
Poor form to reply to my own email, but there appears to be more
information.
Qwest is actually sending the stop/start packets at 5 second intervals,
and radiator is forwarding them on the the proxy radius server. Qwest
is, I guess, waiting for some sort of acknowledgement and when one isn't
I've started seeing this too, extremely intermittently (though not from
Qwest). I'd be interested in knowing how people clean RADIUS accounting
logs to remove stuff like this to avoid coloring results. Sure, we'd want
to find and fix the problem if possible as to why those are getting in
) qwest and stop packets
I've started seeing this too, extremely intermittently
(though not from
Qwest). I'd be interested in knowing how people clean
RADIUS accounting
logs to remove stuff like this to avoid coloring results.
Sure, we'd want
to find and fix the problem
