Hello,
I am wondering what's the best design for a high volume radius system. We are
looking at on the order of 100-150 requests/second (auth+acct) on average.
Does anyone here have a load balancing system setup? If so, I'd appreciate any
tips on how you set this up.
After using Radiator for
Hello Tim -
For this type of problem you are better off writing a PreClientHook that
walks the attribute list looking for whatever and sets a pseudo-attribute in
the request that you can then process with a Handler.
regards
Hugh
On Sat, 27 Apr 2002 21:53, Timothy G. Wells wrote:
Hi Hugh,
Hello Dan -
The AuthBy SQL clause is designed to do both authentication and accounting
(which is how most people use it), however it is flexible enough to be
configured in a number of ways including authentication only and accounting
only.
regards
Hugh
On Sun, 28 Apr 2002 04:50, Dan
Hi All,
I've just upgraded from Radiator 2.17.1 to Radiator 3.0.
I am trying to log different parts of the config to different log files,
and am having no luck at all - everything just ends up in the global
logfile. Attached is my config file - this isn't actually my main config
file, but a
Hello Viraj -
On Sun, 28 Apr 2002 23:06, Viraj Alankar wrote:
Hello,
I am wondering what's the best design for a high volume radius system. We
are looking at on the order of 100-150 requests/second (auth+acct) on
average. Does anyone here have a load balancing system setup? If so, I'd
