|
On Tue, 2010-05-04 at 20:30 +0200, mve@xxxxxxxxxxxxxxxxx wrote:
> > Please post the bash script you're using to setup the loopback device
> > etc. so i can take a look and maybe adjust it.
>
> echo "0" >/proc/sys/net/ipv4/ip_forward
> cat /proc/sys/net/ipv4/ip_forward
> echo 1 > /proc/sys/net/ipv4/conf/eth0/arp_ignore
> echo 2 > /proc/sys/net/ipv4/conf/eth0/arp_announce
> echo 1 > /proc/sys/net/ipv4/conf/all/arp_ignore
> echo 2 > /proc/sys/net/ipv4/conf/all/arp_announce
> /sbin/ifconfig lo:110 194.145.200.87 broadcast 194.145.200.87 netmask
> 0xffffffff up
> /sbin/ifconfig lo:110
> /sbin/route add -host 194.145.200.87 dev lo:110
>
> I also run this script on server2 in exact the same way.
Looks okay to me.
> When I stop Iptables orflush them the reaction from the client is
> different(as stated before).
>
> With iptables on:
> [root@knox01 ~]# telnet 194.145.200.87 25
> Trying 194.145.200.87...
> telnet: connect to address 194.145.200.87: No route to host
> telnet: Unable to connect to remote host: No route to host
> [root@knox01 ~]# telnet 194.145.200.87 25
>
> With iptables off (service iptables stop) on server1:
> (takes a long time)
> Nothing happens:
> root@knox01 ~]# telnet 194.145.200.87 25
> Trying 194.145.200.87...
Just realising something. Have you configured the mailserver service on
the failing realserver to listen on _all_ interfaces? To be sure,
compare the output of:
$ netstat -tulpen | grep 25
on both realservers.
> Could I run some tcpdumps on real servers and LVS dr to check what is
> going wrong?
Running tcpdump never hurt anyone :)
Léon
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
