[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200116142839.98b04af5d16f8ec3ed209288@uniroma2.it>
Date: Thu, 16 Jan 2020 14:28:39 +0100
From: Andrea Mayer <andrea.mayer@...roma2.it>
To: Sabrina Dubroca <sd@...asysnail.net>
Cc: "David S. Miller" <davem@...emloft.net>,
Petr Machata <petrm@...lanox.com>,
Stefano Brivio <sbrivio@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Taehee Yoo <ap420073@...il.com>,
Litao jiao <jiaolitao@...secom.com>,
Roopa Prabhu <roopa@...ulusnetworks.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Paolo Lungaroni <paolo.lungaroni@...t.it>
Subject: Re: [net] vxlan: fix vxlan6_get_route() adding a call to
xfrm_lookup_route()
On Wed, 15 Jan 2020 22:16:21 +0100
Sabrina Dubroca <sd@...asysnail.net> wrote:
> 2020-01-15, 20:22:31 +0100, Andrea Mayer wrote:
> > currently IPSEC cannot be used to encrypt/decrypt IPv6 vxlan traffic.
> > The problem is that the vxlan module uses the vxlan6_get_route()
> > function to find out the route for transmitting an IPv6 packet, which in
> > turn uses ip6_dst_lookup() available in ip6_output.c.
> > Unfortunately ip6_dst_lookup() does not perform any xfrm route lookup,
> > so the xfrm framework cannot be used with vxlan6.
>
> That's not the case anymore, since commit 6c8991f41546 ("net:
> ipv6_stub: use ip6_dst_lookup_flow instead of ip6_dst_lookup").
>
> Can you retest on the latest net tree?
>
> Thanks.
>
> --
> Sabrina
>
Hi Sabrina,
thanks for sharing the fix.
Sorry, my net tree was a bit outdated. I will retest with the fix and let you know.
--
Andrea Mayer <andrea.mayer@...roma2.it>
Powered by blists - more mailing lists