netdev - Re: [PATCH net] mpls: Fix 6PE forwarding

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20190319.160055.790659055193828894.davem@davemloft.net>
Date:   Tue, 19 Mar 2019 16:00:55 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     nvinay@...iper.net
Cc:     netdev@...r.kernel.org, ar977m@....com, aprabh@...iper.net
Subject: Re: [PATCH net] mpls: Fix 6PE forwarding

From: Vinay K Nallamothu <nvinay@...iper.net>
Date: Tue, 19 Mar 2019 22:41:18 +0000

> This patch adds support for 6PE (RFC 4798) which uses IPv4-mapped IPv6
> nexthop to connect IPv6 islands over IPv4 only MPLS network core.
> 
> Prior to this fix, to find the link-layer destination mac address, 6PE
> enabled host/router was sending IPv6 ND requests for IPv4-mapped IPv6
> nexthop address over the interface facing the IPv4 only core which
> wouldn't success as the core is IPv6 free.
> 
> This fix changes that behavior on 6PE host to treat the nexthop as IPv4
> address and send ARP requests whenever the next-hop address is an
> IPv4-mapped IPv6 address.
> 
> Below topology illustrates the issue and how the patch addresses it.
 ...
> With the change, when R0 sends an IPv6 packet over MPLS tunnel to abcd::2.2.2.2,
> using ::ffff:172.18.0.11 as the nexthop, it does neighbor discovery for
> 172.18.18.0.11.
> 
> Signed-off-by: Vinay K Nallamothu <nvinay@...iper.net>
> Tested-by: Avinash Lingala <ar977m@....com>
> Tested-by: Aravind Srinivas Srinivasa Prabhakar <aprabh@...iper.net>

Applied.