From: Joe Perches <joe@perches.com>
To: Christian Franke <christian.franke@adytonsystems.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] net/ipv4/ipip: add support to move between network namespaces
Date: Mon, 09 Jul 2012 09:00:54 -0700 [thread overview]
Message-ID: <1341849654.6118.5.camel@joe2Laptop> (raw)
In-Reply-To: <1341848473-2666-1-git-send-email-christian.franke@adytonsystems.com>
On Mon, 2012-07-09 at 17:41 +0200, Christian Franke wrote:
> Below there is a first attempt at adding support for IPIP tunnels to be moved
> across network namespaces. This allows e.g. for tunnel setups where the inner
> network is completely isolated from the outer transport network.
trivia:
> diff --git a/net/ipv4/ipip.c b/net/ipv4/ipip.c
[]
> @@ -652,6 +660,9 @@ ipip_tunnel_ioctl (struct net_device *dev, struct ifreq *ifr, int cmd)
> break;
>
> case SIOCADDTUNNEL:
> + /* New Tunnels will be created in the current namespace */
New tunnels
> @@ -701,6 +712,15 @@ ipip_tunnel_ioctl (struct net_device *dev, struct ifreq *ifr, int cmd)
> t->parms.iph.tos = p.iph.tos;
> t->parms.iph.frag_off = p.iph.frag_off;
> if (t->parms.link != p.link) {
> + if (!net_eq(dev_net(dev),
> + target_net(dev))) {
> + pr_info_once("%s: rebinding "
> + "cross ns device "
> + "is not supported\n",
> + __func__);
Please coalesce format strings.
pr_info_once("%s: rebinding cross ns device is not supported\n",
__func__);
shouldn't "cross ns device" be "different ns devices"?
next prev parent reply other threads:[~2012-07-09 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 15:41 [RFC PATCH] net/ipv4/ipip: add support to move between network namespaces Christian Franke
2012-07-09 16:00 ` Joe Perches [this message]
2012-07-09 21:19 ` David Miller
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=1341849654.6118.5.camel@joe2Laptop \
--to=joe@perches.com \
--cc=christian.franke@adytonsystems.com \
--cc=netdev@vger.kernel.org \
/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).