Phil Mayers wrote:
Running redundant servers doesn't help much in this case for 2 reasons: first, we've found that Cisco APs are very, very poor at detecting dead radius servers and moving to the backup; second, it seems to be malformed data coming from a certain client so if the APs do failover, the 2nd server hangs up in short order.
That's not nice...
Additionally there are certain configurations that are easy to do individually, but very difficult to combine; though the config unlang in 2.0 should resolve most of the cases I have in mind
Another thing for 2.0.0 (maybe) is to have per-socket configuration. i.e. socket X can have authorization section X, and socket Y can have authorization section Y. It may not be too hard to add, in fact. And it would be extremely useful. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog