LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: simple problem with direct routing LVS

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: simple problem with direct routing LVS
From: Malcolm Turnbull <Malcolm.Turnbull@xxxxxxxxxxxx>
Date: Wed, 05 Mar 2003 13:28:36 +0000
John P. Looney wrote:
 Hi, I've done a good bit of LVS stuff before, but never direct routing,
which is why I'm a little confused.

 I've setup a director with:

echo 1 > /proc/sys/net/ipv4/ip_forward
ipvsadm -A -t XXX.168.225.3:17 -s wlc
ipvsadm -a -t XXX.168.225.3:17 -r XXX.168.225.1 -g
ipvsadm -a -t XXX.168.225.3:17 -r XXX.168.225.2 -g
ifconfig dummy0 0.0.0.0 up
echo 1 > /proc/sys/net/ipv4/conf/all/hidden
echo 1 > /proc/sys/net/ipv4/conf/dummy0/hidden
ifconfig dummy0:0 XXX.168.225.3 up

 So, it should just be setup to forward 17 to XXX.168.225.1 and
XXX.168.225.2. On both clients, I have:

echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/all/hidden
echo 1 > /proc/sys/net/ipv4/conf/lo/hidden
ifconfig lo:0 XXX.168.225.3 netmask 255.255.255.255 broadcast \
XXX.168.225.3 up

 I can ping XXX.168.225.3 fine. However, when I nmap that address, I'm
told that port 17 is "filtered". Telnetting to that port results in a
"no route to host". Is there something silly I've not done ?

John



John,

Um why have you set up a dummy VIP on the director ?
This is the one you WANT the network to see.

i.e.
 ifconfig eth0:1 XXX.168.225.3 up





Regards,

Malcolm Turnbull.

Crocus.co.uk Ltd
01344 629629
http://www.crocus.co.uk/





<Prev in Thread] Current Thread [Next in Thread>