LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [lvs-users] ipvsadm and packets leaving a gre tunnel

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [lvs-users] ipvsadm and packets leaving a gre tunnel
From: "Marco Lorig" <MLORIG@xxxxxxx>
Date: Wed, 30 Jul 2008 14:39:28 +0200
I found out something interesting:

The Realserver is responding and transferring data correctly if the transfer is 
initiated by the client:
"Client ->scp put file -> Server"   works perfectly.
"Client -> scp get file -> Server"  still hangs.

Client at location 1 and server at location 2 are interconnected by gre over 
both directors. (as described in earlier mails).
I couldn't sniff any ICMP Packet relating to mtu mismatch.

Confusing.


Setup for directors:

Location 1
Network 10.131.0.0/24
Defaultrouter 10.131.0.1 (CISCO)
Director 1 10.131.0.250
Client 1 10.131.0.100


1. Director
ip link set eth0 up
vconfig add eth0 20
ip addr add 10.131.0.250/24 dev eth0.20
ip link set eth0.20 up
echo "1" >/proc/sys/net/ipv4/ip_forward
ip route add 10.135.28.250 via 10.131.0.1  # Route to second director for 
tunneling
ip tunnel add tunloc2 mode gre local 10.131.0.250 remote 10.135.28.250 
nopmtudisc
ip link set tunloc2 up
ip addr add 192.168.0.10/18 dev tunloc2
ip route add 192.168.64.10/18 dev tunloc2 # Route to tun-interface on second 
director
ip route add 10.135.67.100/32 dev tunloc2 # Route to ipvsadm instance on second 
director

Client: 
ip route add default via 10.131.0.250

----------------------------

Location 2
Network 10.135.28.0/24
Defaultrouter 10.135.28.1 (CISCO)
Director 1 10.135.28.100
Realserver  10.135.28.100


2. Director
ip link set eth0 up
vconfig add eth0 74
ip addr add 10.135.28.250/24 dev eth0.74
ip addr add 10.135.67.100/32 dev eth0.74 # IPVSADM instance

ip link set eth0.74 up
echo "1" >/proc/sys/net/ipv4/ip_forward
ip route add 10.131.0.250 via 10.135.28.1  # Route to first director for 
tunneling
ip tunnel add tunloc1 mode gre local 10.135.28.250 remote 10.131.0.250 
nopmtudisc
ip link set tunloc1 up
ip addr add 192.168.64.10/18 dev tunloc1
ip route add 192.168.0.10/18 dev tunloc1 # Route to tun-interface on first 
director
ip route add 10.131.0.0/24 dev tunloc1 # Route to client-network at location 1
ipvsadm -A -t 10.135.67.100:22 -s lc -p 360
ipvsadm -a -t 10.135.67.100:22 -r 10.135.28.100 -m


Server:
ip route add default 10.135.28.250


Here's about 34C° without any airconditioning so feel free to ask if I forgot 
anything. 

cheers

Marco






<Prev in Thread] Current Thread [Next in Thread>