LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

RE: Documentation of arp problem in 2.4.18 kernel

To: "'lvs-users@xxxxxxxxxxxxxxxxxxxxxx'" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Documentation of arp problem in 2.4.18 kernel
From: Arisi Pablo <arisi@xxxxxxxxxxx>
Date: Fri, 1 Mar 2002 15:15:20 -0300

Hi,

I have a small LVS-DR environment and realize the same arp problem.(as Paul Dixon).

I read the howto and put a second interface(offline, not conected to the switch) in all Linux Real Servers(RH 7.2), and configure the VIP on that int. as loopback.

The problem I have is very strange, because the linux servers still broadcast ARP from VIP Int. through the connected int. ! (I did not patch kernel)

Actually the LVS is working great, but sometimes the linux boxes send his own arp..,so I must to force the arp broadcast from the Director(Ultramonkey) to renew the arp table in Firewall.

I will apreciate any help or tip!

Pablo Arisi.


-----Mensaje original-----
De: Paul Dixon [mailto:paul@xxxxxxxxxx]
Enviado el: Viernes 1 de Marzo de 2002 14:30
Para: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Asunto: Documentation of arp problem in 2.4.18 kernel


I'm just beginning with getting an LVS-Tun system up and running. My
director is running 2.4.18 kernel with the v1.0.0. ipvs patch. The
realservers are currently stock installations of RedHat 7.2 (kernel version
2.4.9-7). Before I can progress any further I need to prevent my realservers
from responding to arp requests on the VIP.

I've read the document at http://www.linuxvirtualserver.org/docs/arp.html,
but this doesn't go into a lot of detail on the pros and cons of each
approach. I was wondering what the current best practice would be for
dealing with the arp issue in a 2.4 kernel. If at all possible, I'd prefer a
solution that didn't involve a kernel rebuild, since one of my realservers
is already racked up on the other side the Atlantic :-)

Any tips or pointers welcomed.

Paul Dixon
paul@xxxxxxxxxx



****************************************************************************
El contenido del presente mensaje es privado, estrictamente confidencial
y exclusivo para sus destinatarios, pudiendo contener informacion
protegida por normas legales y de secreto profesional. Bajo ninguna
circunstancia su contenido puede ser transmitido o revelado a terceros
ni divulgado en forma alguna. En consecuencia de haberlo recibido por
error, solicitamos contactar al remitente y eliminarlo de su sistema.
Muchas Gracias.

Visite http://www.visa.com.ar
****************************************************************************
<Prev in Thread] Current Thread [Next in Thread>