From: Jiri Benc <jbenc@redhat.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next] net: do not create fallback tunnels for non-default namespaces
Date: Fri, 9 Mar 2018 12:06:36 +0100 [thread overview]
Message-ID: <20180309120636.429d8796@redhat.com> (raw)
In-Reply-To: <20180308205141.77868-1-edumazet@google.com>
On Thu, 8 Mar 2018 12:51:41 -0800, Eric Dumazet wrote:
> Note that these tunnels are still created for the initial namespace,
> to be the least intrusive for typical setups.
Since this is a knob and must be turned on explicitly, why we don't get
rid of the automatic interfaces even for the initial name space? It
causes only problems nowadays, such as
ip link add name gre0 type gre <tunnel_options...>
failing with "File exists" even if there was no gre0 interface before.
And of course, even with the error, the interface with the name "gre0"
appears in the system. And of course, it does not have any of the
options specified. This is highly confusing. Not to mention the
autocreated gre0 interface is basically useless.
I'd like to switch the knob on by default on my systems and have the
kernel behave sane, finally, even without name spaces.
Thanks!
Jiri
next prev parent reply other threads:[~2018-03-09 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 20:51 [PATCH net-next] net: do not create fallback tunnels for non-default namespaces Eric Dumazet
2018-03-09 11:06 ` Jiri Benc [this message]
2018-03-09 12:53 ` Eric Dumazet
2018-03-09 13:08 ` Jiri Benc
2018-03-09 13:18 ` Eric Dumazet
2018-03-09 16:23 ` 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=20180309120636.429d8796@redhat.com \
--to=jbenc@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.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).