[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <563334a2-8b5d-a80b-30ef-085fdaa2d1a8@6wind.com>
Date: Wed, 5 Feb 2020 16:04:55 +0100
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: William Dauchy <w.dauchy@...teo.com>, netdev@...r.kernel.org
Subject: Re: [PATCH] net, ip6_tunnel: enhance tunnel locate with link/type
check
Le 05/02/2020 à 15:57, William Dauchy a écrit :
> With ipip, it is possible to create an extra interface explicitly
> attached to a given physical interface:
>
> # ip link show tunl0
> 4: tunl0@...E: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000
> link/ipip 0.0.0.0 brd 0.0.0.0
> # ip link add tunl1 type ipip dev eth0
> # ip link show tunl1
> 6: tunl1@...0: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000
> link/ipip 0.0.0.0 brd 0.0.0.0
>
> But it is not possible with ip6tnl:
>
> # ip link show ip6tnl0
> 5: ip6tnl0@...E: <NOARP> mtu 1452 qdisc noop state DOWN mode DEFAULT group default qlen 1000
> link/tunnel6 :: brd ::
> # ip link add ip6tnl1 type ip6tnl dev eth0
> RTNETLINK answers: File exists
>
> This patch aims to make it possible by adding the comparaison of the
> link device while trying to locate an existing tunnel.
> This later permits to make use of x-netns communication by moving the
> newly created tunnel in a given netns.
>
> Take this opportunity to also compare dev->type value as it is done in
Please, don't mix patches and problems.
You will have to split this.
Thank you,
Nicolas
Powered by blists - more mailing lists