From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: hide devices starting with period by default
Date: Thu, 23 Feb 2017 17:31:14 -0800 [thread overview]
Message-ID: <20170223173114.621cb747@xeon-e3> (raw)
In-Reply-To: <13cec1c2-88f4-e61d-02ee-dc01ccee7281@cumulusnetworks.com>
On Thu, 23 Feb 2017 18:07:07 -0700
David Ahern <dsa@cumulusnetworks.com> wrote:
> On 2/23/17 5:30 PM, Stephen Hemminger wrote:
> > On Thu, 23 Feb 2017 16:39:52 -0700
> > David Ahern <dsa@cumulusnetworks.com> wrote:
> >
> >> On 2/23/17 12:50 PM, Stephen Hemminger wrote:
> >>> Some use cases create Linux networking devices which are not intended for use
> >>> by normal networking. This is an enhancement to ip command to hide network
> >>> devices starting with period (like files in normal directory). Interfaces whose
> >>> name start with "." are not shown by default, and the -a (or -all) flag must
> >>> be used to show these devices.
> >>
> >> Agree that some devices need to be hidden by default -- not just from
> >> users but also other processes.
> >>
> >> This solution is very narrow, only affecting iproute2 users. Any other
> >> programs that use netlink or /proc files will continue to see those devices.
> >
> > I want solution that works broadly. And this works for sysfs already.
>
> for 'ls' maybe, but not general walking of /sys. It does not hide
> devices from snmpd, from ifconfig, etc., etc.
>
>
> >> I started a patch a year ago that allows devices to marked as invisible
> >> (attribute can be toggled at any time). Invisible devices do not show up
> >> in netlink dumps, proc files or notifications. Netlink dumps can request
> >> invisible devices to be included in a link dump. While it is more
> >> intrusive, it is also more complete covering all of the paths in which
> >> the device is shows up.
> >>
> >> Also, changing the default behavior for iproute2 could break existing
> >> users that have such device names.
> >
> > I am less worried about this. The only people using . in name already
> > are probably Brocade, and they have similar thing in CLI to hide these
> > devices.
>
>
> seems like a big assumption.
Need a solution now, not something that requires kernel and command changes.
next prev parent reply other threads:[~2017-02-24 1:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 19:50 [PATCH] iproute2: hide devices starting with period by default Stephen Hemminger
2017-02-23 23:39 ` David Ahern
2017-02-24 0:30 ` Stephen Hemminger
2017-02-24 1:07 ` David Ahern
2017-02-24 1:31 ` Stephen Hemminger [this message]
2017-02-24 15:38 ` Phil Sutter
2017-02-24 3:12 ` David Miller
2017-02-24 15:52 ` David Ahern
2017-05-04 15:15 ` Nicolas Dichtel
2017-05-04 16:37 ` David Ahern
2017-05-04 19:10 ` Florian Fainelli
2017-05-04 19:47 ` David Ahern
2017-05-05 6:47 ` Jiri Benc
2017-05-05 7:42 ` Nicolas Dichtel
2017-02-24 17:06 ` Andy Gospodarek
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=20170223173114.621cb747@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsa@cumulusnetworks.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).