|
Why does not pass GRE traffic in persistent mode? Any ideas?
lndirector:~# tcpdump -ni eth0 proto gre
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
18:17:13.314946 IP 192.168.18.247 > 192.168.18.77: call 49152 seq 0
gre-ppp-payload
18:17:13.325301 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 0
gre-ppp-payload
18:17:15.333255 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 1
gre-ppp-payload
18:17:17.252509 IP 192.168.18.247 > 192.168.18.77: call 49152 seq 1
gre-ppp-payload
18:17:17.253758 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 2 ack 1
gre-ppp-payload
18:17:18.336196 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 3
gre-ppp-payload
18:17:21.171713 IP 192.168.18.247 > 192.168.18.77: call 49152 seq 2
gre-ppp-payload
18:17:21.173576 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 4 ack 2
gre-ppp-payload
18:17:22.330462 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 5
gre-ppp-payload
18:17:25.111635 IP 192.168.18.247 > 192.168.18.77: call 49152 seq 3
gre-ppp-payload
18:17:25.113143 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 6 ack 3
gre-ppp-payload
18:17:26.335599 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 7
gre-ppp-payload
18:17:29.057091 IP 192.168.18.247 > 192.168.18.77: call 49152 seq 4
gre-ppp-payload
18:17:29.058706 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 8 ack 4
gre-ppp-payload
18:17:30.340574 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 9
gre-ppp-payload
18:17:32.960037 IP 192.168.18.247 > 192.168.18.77: call 49152 seq 5
gre-ppp-payload
18:17:32.961531 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 10 ack 5
gre-ppp-payload
18:17:34.350148 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 11
gre-ppp-payload
18:17:36.874293 IP 192.168.18.247 > 192.168.18.77: call 49152 seq 6
gre-ppp-payload
18:17:36.877840 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 12 ack 6
gre-ppp-payload
18:17:40.351390 IP 192.168.18.77 > 192.168.18.247: call 56952 seq 13
gre-ppp-payload
21 packets captured
21 packets received by filter
0 packets dropped by kernel
lndirector:~# tcpdump -ni eth1 proto gre
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
18:18:00.644133 IP 192.168.18.247 > 192.168.18.77: call 0 seq 0
gre-ppp-payload
18:18:04.577462 IP 192.168.18.247 > 192.168.18.77: call 0 seq 1
gre-ppp-payload
18:18:08.541568 IP 192.168.18.247 > 192.168.18.77: call 0 seq 2
gre-ppp-payload
18:18:12.479802 IP 192.168.18.247 > 192.168.18.77: call 0 seq 3
gre-ppp-payload
18:18:16.446896 IP 192.168.18.247 > 192.168.18.77: call 0 seq 4
gre-ppp-payload
18:18:20.366643 IP 192.168.18.247 > 192.168.18.77: call 0 seq 5
gre-ppp-payload
18:18:24.195004 IP 192.168.18.247 > 192.168.18.77: call 0 seq 6
gre-ppp-payload
VIP - 192.168.18.247
Client - 192.168.18.77
As you can see ipvs doesn't forward ALL traffic from host 192.168.18.77 to
192.168.18.247!
--
Russia, St. Petersburg
Valeriy V. Peshkov | peshkoff@xxxxxxxxx
|
