|
Hi,
Local Director: (kernel-2.4.18-27.8.0,ipvsadm-1.21-4)
ipvsadm -A -t 6x.1x.1x.101:80 -s rr
ipvsadm -a -t 6x.1x.1x.101:80 -r 192.168.0.2:80 -w 10 -m
ip 192.168.0.1
ip 6x.1x.1x.101
/etc/sysctl.conf
----------------------------
net.ipv4.ip_forward = 1
net.ipv4.conf.default.rp_filter = 1
You do not need this and it will not work anyway as long as you do not
set the net.ipv4.conf.all.rp_filter=1. The all enables it, the default
is needed for flag inheritance on newly instantiated physical devices.
Real Server: (kernel-2.4.18-27.8.0)
apache is bound to 192.168.0.2:80 (tcp connection tested from Local
Director)
Ok.
ip: 192.168.0.2
gw: 192.168.0.1
Is this your default gateway?
Client (Windows 2000)
ip: 6x.1x.1x.103
Ok.
It is not working. I am tcpdumping port 80 on real-server. It doesn't
send the ack package back to the client. However when i initiate a
connection from local director, it does send the ack package back.
As Horms suggested it definitely sounds like either a routing problem on
the RS or maybe you've enabled some filter rules on the RS for packets
destined to the DGW.
Could we possibly see such a connection request tcpdump? It would help
us identify the problem further. And could you check
/var/log/{messages,kernlog} for routing anomalies printk()'d? Also make
sure you do the filter for tcpdump with ICMP too.
Thanks,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
| 