|
Hey all, hope you can help I'm going crazy here.
I've had LVS_NAT working on 2.2 kernel environment with no problems for
awhile.
I've recently upgrade to a 2.4.7 kernel and had LVS_NAT working on it for
awhile on my development environment. At that time I just had one director
box, and one realserver. I decided to add another realserver, while doing
so I gave the new realserver the IP address of the old one, and the old one
new IP addresses. I also restarted the director after the upgrades. Now
when trying to connect from a client it just hangs.
My setup:
Client: 216.163.XXX.2 Box 1
VIP: 216.163.XXX.4 eth0 Box2
DIP: 10.75.0.1 eth1
RIP 10.75.0.11 and 10.75.32.11 Box 3
10.75.0.1 is the gateway for the realservers, I can ping the VIP from the
realservers.
I've tried masquerading with iptables:
/usr/local/sbin/iptables -t nat -A POSTROUTING -s 10.75.0.0/16 -d 0.0.0.0/0
-o eth0 -j MASQUERADE
With this setup I can ping the world on my realservers.
I've also tried it without seting up the masquerading.
LVS is set up as:
/sbin/modprobe ip_vs_rr
ipvsadm -C
ipvsadm -A -t 216.163.XXX.4:25 -s rr
ipvsadm -a -t 216.163.XXX.4:25 -R 10.75.0.11:25 -m
ipvsadm -a -t 216.163.XXX.4:25 -R 10.75.32.11:25 -m
On the director when doing a ipvsadm -l -c
# ipvsadm -l -c
IPVS connection entries
pro expire state source virtual destination
TCP 00:58.17 SYN_RECV 216.163.XXX.2:3713 216.163.XXX.4:smtp
10.75.0.11:smtp
Which I think means that it's not getting any response from the realservers.
I've done tcpdumps on the realservers and I'm not getting any traffic from
the director, but from the director I can talk to the RIP's service and it
works like expected.
I've gone back and removed the new realserver and re-IPed back to the way
things were and I'm still having the same problem.
HELP!
|
