LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [lvs-users] Reg Tunneling IPV6 VS to IPv4 RS

To: SankaraNarayanan S <sankaranarayanan.s@xxxxxxxxxxxx>
Subject: Re: [lvs-users] Reg Tunneling IPV6 VS to IPv4 RS
Cc: lvs-users <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: Julian Anastasov <ja@xxxxxx>
Date: Tue, 12 Jun 2018 21:55:18 +0300 (EEST)
        Hello,

On Tue, 12 Jun 2018, SankaraNarayanan S wrote:

> Hello,
> 
>  Am trying to create a Tunneling IPV6 VS to IPv4 RS.below are the commands i 
> used .
> 
> ipvsadm -A -t [fd21:d1aa:194a:3515:0:1:0:0]:80 -s rr
> 
> ipvsadm -a -t [fd21:d1aa:194a:3515:0:1:0:0]:80 -r 172.20.22.229:80 -i
> 
> root@172.20.28.92~#ipvsadm -Ln
> 
> IP Virtual Server version 1.2.1 (size=4096)
> 
> Prot LocalAddress:Port Scheduler Flags
> 
>   -&gt; RemoteAddress:Port           Forward Weight ActiveConn InActConn
> 
> TCP  [fd21:d1aa:194a:3515:0:1::]:80 rr
> 
>   -&gt; 172.20.22.229:80             Tunnel  1      2          0        

        2 Active connections? From previous test?

> root@172.20.28.92~#
> 
> 
> 
> 
> 
> While connecting the Virtual server, the request is not passing to the 
> tunneled IPV4 real server. 
> 
> 
> 
> root@172.20.28.92~#tcpdump -i bond0 -vvAzzxxxX ip6 | grep http

        On the wire you should expect IPIP (IPv4) packet,
not IPv6 one. So, we are not sure if packet is correctly
sent. If yes, problem can be in real server.

> 
> tcpdump: listening on bond0, link-type EN10MB (Ethernet), capture size 262144 
> bytes
> 
> 
> 
> 17:41:28.802885 IP6 (hlim 64, next-header TCP (6) payload length: 40) 
> fe80::5054:ff:feb8:d153.53343 &gt; fd21:d1aa:194a:3515:0:1::.http: Flags [S], 
> cksum 0x8d28 (correct), seq 616138939, win 14400, options [mss 1440,sackOK,TS 
> val 2619026270 ecr 0,nop,wscale 7], length 0
> 
> 17:41:35.376335 IP6 (hlim 64, next-header TCP (6) payload length: 40) 
> fe80::5054:ff:feb8:d153.53344 &gt; fd21:d1aa:194a:3515:0:1::.http: Flags [S], 
> cksum 0x870f (correct), seq 693727359, win 14400, options [mss 1440,sackOK,TS 
> val 2619032850 ecr 0,nop,wscale 7], length 0
> 
> 17:41:36.376316 IP6 (hlim 64, next-header TCP (6) payload length: 40) 
> fe80::5054:ff:feb8:d153.53344 &gt; fd21:d1aa:194a:3515:0:1::.http: Flags [S], 
> cksum 0x8327 (correct), seq 693727359, win 14400, options [mss 1440,sackOK,TS 
> val 2619033850 ecr 0,nop,wscale 7], length 0
> 
> 17:41:38.376295 IP6 (hlim 64, next-header TCP (6) payload length: 40) 
> fe80::5054:ff:feb8:d153.53344 &gt; fd21:d1aa:194a:3515:0:1::.http: Flags [S], 
> cksum 0x7b57 (correct), seq 693727359, win 14400, options [mss 1440,sackOK,TS 
> val 2619035850 ecr 0,nop,wscale 7], length 0
> 
> 17:41:42.376307 IP6 (hlim 64, next-header TCP (6) payload length: 40) 
> fe80::5054:ff:feb8:d153.53344 &gt; fd21:d1aa:194a:3515:0:1::.http: Flags [S], 
> cksum 0x6bb7 (correct), seq 693727359, win 14400, options [mss 1440,sackOK,TS 
> val 2619039850 ecr 0,nop,wscale 7], length 0

        You can enable IPVS debugging while sending the SYN packet:

echo 20 > /proc/sys/net/ipv4/vs/debug_level

        It should give more information what happens.

> root@172.20.28.92~#uname -a
> 
> Linux 172.20.28.92 4.16.11-1.el7.elrepo.x86_64 #1 SMP Tue May 22 15:34:16 EDT 
> 2018 x86_64 x86_64 x86_64 GNU/Linux
> 
> root@172.20.28.92~#ipvsadm -v
> 
> ipvsadm v1.29 2016/12/23 (compiled with popt and IPVS v1.2.1)
> 
> 
> 
> is there anything need to done to achieve this. 

Regards

--
Julian Anastasov <ja@xxxxxx>

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

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