From: Nicolas Dichtel <nicolas.dichtel@6wind•com>
To: Saurabh Mohan <saurabh@cplanenetworks•com>,
netdev@vger•kernel.org, stephen@networkplumber•org,
davem@davemloft•net, pshelar@nicira•com, tgraf@suug•ch
Subject: Re: [PATCH net-next 1/2] Support outside netns for tunnels.
Date: Tue, 5 Jan 2016 17:47:09 +0100 [thread overview]
Message-ID: <568BF38D.4060803@6wind.com> (raw)
In-Reply-To: <1451933147-17266-1-git-send-email-saurabh@cplanenetworks.com>
Le 04/01/2016 19:45, Saurabh Mohan a écrit :
>
> This patch enchances a tunnel interface, like gre, to have the tunnel
> encap/decap be in the context of a network namespace that is different from
> the namespace of the tunnel interface.
>
> From userspace this feature may be configured using the new 'onetns' keyword:
> ip netns exec custa ip link add dev tun1 type gre local 10.0.0.1 \
> remote 10.0.0.2 onetns outside
>
> In the above example the tunnel would be in the 'custa' namespace and the
> tunnel endpoints would be in the 'outside' namespace.
What is the difference with the following commands?
ip netns exec outside ip link add dev tun1 type gre local 10.0.0.1 \
remote 10.0.0.2
ip netns exec outside ip link set tun1 netns custa
or
ip exec custa ip netns set outside 1234
ip exec custa ip link add tun1 link-netnsid 1234 type gre local 10.0.0.1 \
remote 10.0.0.2
Regards,
Nicolas
next prev parent reply other threads:[~2016-01-05 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 18:45 [PATCH net-next 1/2] Support outside netns for tunnels Saurabh Mohan
2016-01-04 18:45 ` [PATCH net-next 2/2] Support outside netns for gre & vti tunnels Saurabh Mohan
2016-01-04 19:47 ` [PATCH net-next 1/2] Support outside netns for tunnels Tom Herbert
2016-01-04 19:54 ` Joe Perches
2016-01-05 16:47 ` Nicolas Dichtel [this message]
2016-01-07 18:59 ` Saurabh Mohan
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=568BF38D.4060803@6wind.com \
--to=nicolas.dichtel@6wind$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pshelar@nicira$(echo .)com \
--cc=saurabh@cplanenetworks$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=tgraf@suug$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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