LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: lvs setup via tunelling problem

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: lvs setup via tunelling problem
From: djamil <djamil@xxxxxxxxxxxxxxxx>
Date: Thu, 11 Oct 2001 00:08:21 +0000
oh ! thank you for replaying !
 well you must be right, altho i followed some of the examples at the site 
[about the netmask and broadcast addresses].... because when i run ssh in debug 
mode it finally got me an error message : no route to host !

and mozilla finally got me an connection refused ....
for hiding it i will try it tomorow [it's 00:00 here hehe !] 

but even after reading the docs i thaught i wouldn have because "UP RUNNING 
NOARP" in the ifconfig ...

also there is a firewall altho i double checked the trafic needed does go thru, 
unless u tell me there must be a special "opening" which would be surprizing 
'cause ipip should be just another packet like another .... just a little bit 
longer ...

i hope you have noticed the two machines are in two different dataceters ...

also:   .200 pings .146 and vice-vers-ca

        .200 pings .77 internally
        .146 pings .77 internally

                i hope this is normal !
snap-snap

> >
> > eth0:0    Link encap:Ethernet  HWaddr 00:D0:B7:00:B1:DC
> >           inet addr:212.43.221.77  Bcast:212.43.221.77  Mask:255.255.255.255
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           Interrupt:10
> 
>       Are you sure that you can talk with 221.77? I don't see valid
> network for it, it is not from the 221.146/27 network.

what do u mean ? is the Bcast/Mask wrong ?
i wish it is so i can move on !


snap-snap

> 


On Thu, 11 Oct 2001 00:38:20 +0000 (GMT)
Julian Anastasov <ja@xxxxxx> wrote:

> 
>       Hello,
> 
> On Wed, 10 Oct 2001, Djamil ESSAISSI wrote:
> 
> > the realserver is 2.2.19
> > the Director is 2.4.9 ..
> >
> > the config on the realserver:
> >
> > [root@ns0 (13:46:01) linux]# ifconfig
> > eth0      Link encap:Ethernet  HWaddr 00:D0:B7:11:5C:36
> >           inet addr:212.73.232.200  Bcast:212.73.232.255  
> > Mask:255.255.255.192
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:402808 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:407783 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:10301 txqueuelen:100
> >           Interrupt:10
> >
> > lo        Link encap:Local Loopback
> >           inet addr:127.0.0.1  Mask:255.0.0.0
> >           UP LOOPBACK RUNNING  MTU:3924  Metric:1
> >           RX packets:12795 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:12795 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >
> > tunl0     Link encap:IPIP Tunnel  HWaddr
> >           inet addr:212.43.221.77  Mask:255.255.255.255
> >           UP RUNNING 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
> 
>       I don't see any counters moving here (tunl0). OTOH, may be
> you can hide this 221.77 IP on tunl0:
> 
> echo 1 > /proc/sys/net/ipv4/conf/all/hidden
> echo 1 > /proc/sys/net/ipv4/conf/tunl0/hidden
> 
>       By this way this VIP will not be used in the ARP probes.
> 
> > [root@ns0 (13:57:27) linux]#route -n
> >  Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use 
> > Iface
> > 212.43.221.77   *               255.255.255.255 UH    0      0        0 
> > tunl0
> > 212.73.232.192  *               255.255.255.192 U     0      0        0 eth0
> > loopback        *               255.0.0.0       U     0      0        0 lo
> > default         212.73.232.193  0.0.0.0         UG    1      0        0 eth0
> > [root@ns0 (13:58:48) linux]#
> >
> >
> > config on the Director
> >
> > [root@demo (13:58:15) LVS]# ifconfig
> > eth0      Link encap:Ethernet  HWaddr 00:D0:B7:00:B1:DC
> >           inet addr:212.43.221.146  Bcast:212.43.221.159  
> > Mask:255.255.255.224
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:21928 errors:0 dropped:0 overruns:0 frame:125
> >           TX packets:4279 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           Interrupt:10

snip-snip

> > lo        Link encap:Local Loopback
> >           inet addr:127.0.0.1  Mask:255.0.0.0
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:20 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >
> > [root@demo (13:58:17) LVS]# route
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use 
> > Iface
> > 212.43.221.77   *               255.255.255.255 UH    0      0        0 eth0
> > 212.43.221.128  *               255.255.255.224 U     0      0        0 eth0
> > loopback        *               255.0.0.0       U     0      0        0 lo
> > default         212.43.221.129  0.0.0.0         UG    1      0        0 eth0
> >
> >
> > [root@demo (13:58:40) LVS]# ipvsadm
> > IP Virtual Server version 0.9.4 (size=4096)
> > Prot LocalAddress:Port Scheduler Flags
> >   -> RemoteAddress:Port             Forward Weight ActiveConn InActConn
> > TCP  212.43.221.77:www wlc
> >   -> ns0.tgv.net:www                Tunnel  1      0          0
> 
>       I assume ns0 is 232.200
> 
>       You have to check your routes and then to test with
> tcpdump at each point. The LVS-TUN traffic can be:
> 
> client:
> eth: OUT CIP -> VIP
> 
> director:
> eth: IN CIP -> VIP
> eth: OUT DIP -> RIP
> 
> real server:
> eth: IN DIP -> RIP
> tunl0: IN CIP -> VIP
> eth: ARP probe who-has GW tell VIP            <- VIP should not be
>                                               announced if GW is not
>                                               ready for this
> eth: OUT VIP -> CIP through GW
> 
> You have to find at which step the traffic stops.
> 
> Regards
> 
> --
> Julian Anastasov <ja@xxxxxx>
> 
> 
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> 


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