On the active server (the one that have 192.168.1.1) you have to delete the route that route packets through 192.168.1.2 for subnet 192.168.1.1/24 and make sure there's a route through 192.168.1.1 for subnet 192.168.1.1/24. This way, all connexion initiate from this box will have source address 192.168.1.1. When the Ip is switched to 192.168.1.3 you have to do the same route operation, delete the route through 192.168.1.3 for subnet 192.168.1.0/24 and add a route 192.168.1.1 for subnet 192.168.1.1/24. -----Message d'origine----- De : freeradius-users-bounces+s.cantos=neopost.com@lists.freeradius.org [mailto:freeradius-users-bounces+s.cantos=neopost.com@lists.freeradius.org] De la part de Angel L. Mateo Envoyé : lundi 25 septembre 2006 14:01 À : FreeRadius users mailing list Objet : Source IP address for proxy requests Hello, I have a cluster of two servers running freeradius (the cluster is monitored by heartbeat). Each of the two members of the cluster has its own IP address (192.168.1.2 and 192.168.1.3) and one of the (the active member) has the IP address in which it runs freeradius (192.168.1.1), so freeradius only listen in this address, not in the owned by the server. Freeradius is working fine with this configuration, except the proxy module. The problema I have is that proxy requests are originated with the IP address of the member, not the IP of the cluster. And I haven't found any configuration option to configure this. Is there any way to do it? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 968367590 Fax: 968398337 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html