[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180129.123625.749874592074031868.davem@davemloft.net>
Date: Mon, 29 Jan 2018 12:36:25 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: nicolas.dichtel@...nd.com
Cc: netdev@...r.kernel.org, jbenc@...hat.com,
christian.brauner@...ntu.com
Subject: Re: [PATCH net-next 0/2] Ease to follow an interface that moves to
another netns
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
Date: Thu, 25 Jan 2018 15:01:37 +0100
> The goal of this series is to ease the user to follow an interface that
> moves to another netns.
>
> After this series, with a patched iproute2:
>
> $ ip netns
> bar
> foo
> $ ip monitor link &
> $ ip link set dummy0 netns foo
> Deleted 5: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
> link/ether 6e:a7:82:35:96:46 brd ff:ff:ff:ff:ff:ff new-nsid 0 new-ifindex 6
>
> => new nsid: 0, new ifindex: 6 (was 5 in the previous netns)
>
> $ ip link set eth1 netns bar
> Deleted 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
> link/ether 52:54:01:12:34:57 brd ff:ff:ff:ff:ff:ff new-nsid 1 new-ifindex 3
>
> => new nsid: 1, new ifindex: 3 (same ifindex)
>
> $ ip netns
> bar (id: 1)
> foo (id: 0)
Series applied, thanks Nicolas.
Powered by blists - more mailing lists