Strange problems in large proxy setup

Kostas Zorbadelos kzorba at otenet.gr
Sat Feb 24 13:00:27 CET 2007


On Fri, Feb 23, 2007 at 10:23:50AM -0500, Dennis Skinner wrote:
> Kostas Zorbadelos wrote:
> > radiusd -X confirms that the configuration is correct, however I have
> > this problem behaviour in large scale. My initial suspitions go to the
> > proxying code to be honest, but I need to take a good look to grasp
> > it.  
>
Hi Dennis,
 
> I would try running the production radius in debugging mode and send the
> output to a file that you can review for anomalies.  If it is happening
> often enough and you don't want to run the primary radius in debug mode,
> you could do it on the secondary and force a failover for a short time
> and try to catch it.
> 

By 'debugging mode' I guess you are referring to radiusd -xxx or
something is that correct? Could this affect the authentication
service for our customers? 

I was thinking 
something in the lines of changing the freeradius config to log the
packets going to the home server and their replies (detail_log module
in pre_proxy and post_proxy stages).

Has anyone else noticed this behaviour in a large load proxy setup?

> -- 
> Dennis Skinner
> Systems Administrator
> BlueFrog Internet
> http://www.bluefrog.com

-- 
  Kostas Zorbadelos
  Systems Designer/Developer, Otenet SA 
  m at il contact: kzorba (at) otenet.gr



More information about the Freeradius-Users mailing list