I was quite puzzled why it does not work for you. I bet you have
something like this in your log:
ERR: Unknown keyword 'AcctLogFilename' in file.cfg line 38
So use AcctLogFileName in your Handlers and it should work. Notice the
spelling (f vs F). That's where the problem is.
Thanks!
Hi,
We'd like to load balance RADIUS requests over several RADIATOR servers.
Therefor we will use an external hardware load balancer: a Cisco ACE (service
module).
Is there anyone who has experience with this kind of combination, i.e RADIATOR
Cisco ACE.
Any (white) papers on this subject are
Yes...ppm install did give me version 0.44 however, upon futher investigation, we have a hook that calls "use Net::LDAP qw(:all)" . The qw(:all) is what is causing the issue with this version of NET::LDAP. There are several threads regarding this particular issue. One workaround is to import only
I've done it -- currently in production serving an environment with
over 80,000 users. No issues.
If you're load balancing TACACS+ you should enable stickiness so that
the session remains pinned to one Radiator server. If load balancing
simple RADIUS, just do a simple serverfarm and load balance
EAP and OTP also requires pinning which I personally would always use.
Am 2012-05-10 16:56, schrieb James:
I've done it -- currently in production serving an environment with
over 80,000 users. No issues.
If you're load balancing TACACS+ you should enable stickiness so that
the session
