|
On Thu, 20 Apr 2000, Donald Ball wrote:
> Hi guys. I'm having trouble getting my direct routing LVS cluster up and
> running. Per the instructions on
>
> http://linuxvirtualserver.org/arp.html
>
> and this message
>
> http://marc.theaimsgroup.com/?l=linux-virtual-server&m=95533730908496&w=2
>
> I issued the following commands on one of my real servers:
>
> echo "1" >/proc/sys/net/ipv4/conf/all/hidden
> echo "1" >/proc/sys/net/ipv4/conf/lo/hidden
> ifconfig lo:0 206.66.49.220 mtu 150
>
Please use
ifconfig lo:0 206.66.49.220 netmask 255.255.255.255 broadcast \
206.66.49.220 up
I used the command like this in my tests.
Wensong
> where 206.66.49.220 is one of the public ip addresses that the cluster is
> serving. Sadly, now the real server cannot communicate with the
> 206.66.49.0 network anymore. Actually, that's a lie - ICMP pings work
> great, UDP name services don't work at all, telnet closes immediately.
> Tcpdump seems to indicate that the real server is attempting to use the lo
> interface to communicate with the 206.66.49.0 network, even though the
> route command clearly shows that it should go over eth0:
>
> [root@johnny /root]# route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> johnny-internal * 255.255.255.255 UH 0 0 0 eth1
> 206.66.49.219 * 255.255.255.255 UH 0 0 0 eth0
> 206.66.49.0 * 255.255.255.0 U 0 0 0 eth0
> 192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
> default 206.66.49.1 0.0.0.0 UG 0 0 0 eth0
>
> I'm confused. Can someone point me in the right direction here? Thanks.
>
> - donald
>
>
>
|
