If I understand it correctly what you are tying to is:
SYN -> director eth1 -> director eth0 -> real eth0
(This is also what you see)
The result should be:
real eth1 -> ACK
What tells 'sysctl net/ipv4/ip_forward' ('cat
/proc/sys/net/ipv4/ip_forward')?
(on the real)
BTW. I think that I would put the vip on the real on lo:1 and the
real checking on 10.2.84.158 (eth1)
Riccardo Vestrini <mailto:riccardov@xxxxxxxx> wrote:
> Kees Bos wrote:
> > On your real servers, what tells ifconfig -a?
> > In other words, did you configure 20.1vip on the
> > real servers? (If the SYN packet is the right packet,
> > the problem is on your real servers).
>
>
> in words, there is a private network used by realservers and director,
> VIP is on the nic of the director on the public network, ipvs sends
> packets to realservers using private network, realservers send
> directly
> to client
>
> I choose this topology because those machines are already a working
> NFS-NIS cluster
>
> VIP is 10.2.84.224 and is assigned to realserver on private network
>
> the director (eth0 is private network, eth1 public):
> eth0 Link encap:Ethernet HWaddr 00:00:F8:76:45:24
> inet addr:10.0.80.8 Bcast:10.0.80.100
> Mask:255.255.255.0 inet6 addr:
> fe80::200:f8ff:fe76:4524/64 Scope:Link UP BROADCAST
> RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6462952
> errors:1 dropped:0 overruns:0 frame:0 TX packets:935017
> errors:0 dropped:0 overruns:0 carrier:0 collisions:0
> txqueuelen:1000 RX bytes:8672970196 (8.0 GiB) TX
> bytes:151125557 (144.1 MiB) Interrupt:24 Base
> address:0x9000
>
> eth1 Link encap:Ethernet HWaddr 00:02:A5:43:C3:22
> inet addr:10.2.84.156 Bcast:10.2.84.255
> Mask:255.255.255.0 inet6 addr:
> fe80::202:a5ff:fe43:c322/64 Scope:Link UP BROADCAST
> RUNNING MULTICAST MTU:1500 Metric:1 RX
> packets:12464186 errors:0 dropped:0 overruns:0 frame:0
> TX packets:6102094 errors:0 dropped:0 overruns:0
> carrier:0 collisions:0 txqueuelen:1000 RX
> bytes:1681434377 (1.5 GiB) TX bytes:8660237931 (8.0 GiB)
>
> eth1:0 Link encap:Ethernet HWaddr 00:02:A5:43:C3:22
> inet addr:10.2.84.224 Bcast:10.2.84.224
> Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST
> MTU:1500 Metric:1
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:281 errors:0 dropped:0 overruns:0 frame:0
> TX packets:281 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:27912 (27.2 KiB) TX bytes:27912 (27.2 KiB)
>
> sit0 Link encap:IPv6-in-IPv4
> NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 10.2.84.0 * 255.255.255.0 U 0 0 0 eth1
> 10.0.80.0 * 255.255.255.0 U 0 0 0 eth0
> default 10.2.84.1 0.0.0.0 UG 0 0 0 eth1
>
>
> one of the realservers (eth0 is private network, eth1 public):
> eth0 Link encap:Ethernet HWaddr 00:00:F8:76:46:B0
> inet addr:10.0.80.12 Bcast:10.0.80.255
> Mask:255.255.255.0 inet6 addr:
> fe80::200:f8ff:fe76:46b0/64 Scope:Link UP BROADCAST
> RUNNING MULTICAST MTU:1500 Metric:1 RX packets:139836
> errors:2 dropped:0 overruns:0 frame:0 TX packets:135147
> errors:3 dropped:0 overruns:0 carrier:3 collisions:0
> txqueuelen:1000 RX bytes:12031981 (11.4 MiB) TX
> bytes:10957920 (10.4 MiB) Interrupt:24 Base
> address:0x9000
>
> eth0:0 Link encap:Ethernet HWaddr 00:00:F8:76:46:B0
> inet addr:10.2.84.224 Bcast:10.2.84.224
> Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST
> MTU:1500 Metric:1 Interrupt:24 Base address:0x9000
>
> eth1 Link encap:Ethernet HWaddr 00:02:A5:43:C3:10
> inet addr:10.2.84.158 Bcast:10.2.84.255
> Mask:255.255.255.0 inet6 addr:
> fe80::202:a5ff:fe43:c310/64 Scope:Link UP BROADCAST
> RUNNING MULTICAST MTU:1500 Metric:1 RX
> packets:11160177 errors:0 dropped:0 overruns:2 frame:0
> TX packets:88551 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000 RX bytes:1659143906 (1.5
> GiB) TX bytes:8594105 (8.1 MiB)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:505 errors:0 dropped:0 overruns:0 frame:0
> TX packets:505 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:56174 (54.8 KiB) TX bytes:56174 (54.8 KiB)
>
> sit0 Link encap:IPv6-in-IPv4
> NOARP MTU:1480 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 10.2.84.0 * 255.255.255.0 U 0 0 0
> eth1
> 10.0.80.0 * 255.255.255.0 U 0 0 0
> eth0 default 10.2.84.1 0.0.0.0 UG 0 0
> 0 eth1
>
>
> as i said earlier, syn packet arrives to director on eth1, is passed
> to realserver on eth0, arrives to realserver on eth0 and vanish,
> client do not receive anything
>
> i checked with
> tethereal -i any -f "port 80"
> running wget on client and apache2 on realservers (apache correctly
> worked, with binding to every interface)
>
>
> i do not know what the kernel does with that packet, probably it
> discards it without answer
>
>
> is there any way to trace the track of packet after it arrives on eth0
> nic of the realserver?
>
>
>
> thank you
|