public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Octavian Purdila <opurdila@ixiacom.com>,
	netdev@vger.kernel.org,
	Lucian Adrian Grijincu <lucian.grijincu@gmail.com>,
	Vlad Dogaru <ddvlad@rosedu.org>
Subject: Re: [PATCH] iproute2: ip: add wilcard support for device matching
Date: Fri, 10 Dec 2010 17:32:20 +0100	[thread overview]
Message-ID: <1291998740.3580.162.camel@edumazet-laptop> (raw)
In-Reply-To: <20101210081846.58b67f09@nehalam>

Le vendredi 10 décembre 2010 à 08:18 -0800, Stephen Hemminger a écrit :
> On Fri, 10 Dec 2010 16:58:12 +0200
> Octavian Purdila <opurdila@ixiacom.com> wrote:
> 
> > Allow the users to specify a wildcard when selecting a device:
> > 
> > $ ip set link dev dummy* up
> > 
> > We do this by expanding the original command line in multiple lines
> > which we then feed via a pipe to a forked ip processed run in batch
> > mode.
> > 
> 
> 
> Seems like feature creep. Can't you do this with bash completion
> script instead.
> -

furthermore, "*" is allowed in a device name

ip link add link bond0 "vlan*" txqueuelen 100 type vlan id 999

$ ifconfig "vlan*"
vlan*     Link encap:Ethernet  HWaddr 00:1E:0B:EC:D3:D2  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)




  reply	other threads:[~2010-12-10 16:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 14:58 [PATCH] iproute2: ip: add wilcard support for device matching Octavian Purdila
2010-12-10 16:18 ` Stephen Hemminger
2010-12-10 16:32   ` Eric Dumazet [this message]
2010-12-10 17:32     ` Octavian Purdila
2010-12-10 17:42       ` Eric Dumazet
2010-12-10 18:06         ` Octavian Purdila
2010-12-17 13:38           ` jamal
2010-12-19  9:32             ` Vlad Dogaru
2010-12-21 13:14               ` jamal
2011-01-08 21:10                 ` Philip Prindeville

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=1291998740.3580.162.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=ddvlad@rosedu.org \
    --cc=lucian.grijincu@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=opurdila@ixiacom.com \
    --cc=shemminger@vyatta.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