[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180125140139.18106-1-nicolas.dichtel@6wind.com>
Date: Thu, 25 Jan 2018 15:01:37 +0100
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: davem@...emloft.net
Cc: netdev@...r.kernel.org, jbenc@...hat.com,
christian.brauner@...ntu.com
Subject: [PATCH net-next 0/2] Ease to follow an interface that moves to another netns
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)
include/linux/rtnetlink.h | 5 +++--
include/uapi/linux/if_link.h | 1 +
net/core/dev.c | 22 ++++++++++++----------
net/core/rtnetlink.c | 31 ++++++++++++++++++++-----------
4 files changed, 36 insertions(+), 23 deletions(-)
Comments are welcomed,
Regards,
Nicolas
Powered by blists - more mailing lists