From: David Miller <davem@davemloft.net>
To: nicolas.dichtel@6wind.com
Cc: netdev@vger.kernel.org, jbenc@redhat.com, christian.brauner@ubuntu.com
Subject: Re: [PATCH net-next 0/2] Ease to follow an interface that moves to another netns
Date: Mon, 29 Jan 2018 12:36:25 -0500 (EST) [thread overview]
Message-ID: <20180129.123625.749874592074031868.davem@davemloft.net> (raw)
In-Reply-To: <20180125140139.18106-1-nicolas.dichtel@6wind.com>
From: Nicolas Dichtel <nicolas.dichtel@6wind.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.
prev parent reply other threads:[~2018-01-29 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 14:01 [PATCH net-next 0/2] Ease to follow an interface that moves to another netns Nicolas Dichtel
2018-01-25 14:01 ` [PATCH net-next 1/2] dev: always advertise the new nsid when the netns iface changes Nicolas Dichtel
2018-01-25 22:32 ` Jiri Benc
2018-01-25 14:01 ` [PATCH net-next 2/2] dev: advertise the new ifindex " Nicolas Dichtel
2018-01-25 22:33 ` Jiri Benc
2018-01-29 17:36 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180129.123625.749874592074031868.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=christian.brauner@ubuntu.com \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).