From: Patrick McHardy <kaber@trash.net>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Milan Kocian <milon@wq.cz>, Ben Greear <greearb@candelatech.com>,
Stephen Hemminger <shemminger@vyatta.com>,
netdev@vger.kernel.org
Subject: Re: Could you make vconfig less stupid?
Date: Tue, 07 Oct 2008 14:56:03 +0200 [thread overview]
Message-ID: <48EB5C63.60501@trash.net> (raw)
In-Reply-To: <200810071549.16647.denys@visp.net.lb>
Denys Fedoryshchenko wrote:
> On Tuesday 07 October 2008, Milan Kocian wrote:
>> hello,
>>
>> btw. How can I see vlan id on device ?
>> After:
>> # ip l a l eth0 type vlan id 100
>> # ip a
>> I see:
>>
>> 64: vlan0@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
>> link/ether 00:16:d3:3e:4e:b9 brd ff:ff:ff:ff:ff:ff
>>
>> No vlan id in interface name ?
>>
>> # ip -V
>> ip utility, iproute2-ss080725
>>
>> regards,
> Use flag -d
> rich ip # ./ip -d l show dev vlan0
> 31: vlan0@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
> link/ether 00:1e:8c:89:78:af brd ff:ff:ff:ff:ff:ff
> vlan id 100 <REORDER_HDR>
It would be better to have -d as a default, I was afraid of breaking
scripts of people sedding and awking around with the iproute output.
Stephen should make this call, I'm not sure what guarantees he wants
to provide. I just remembered one of my previous jobs where a large
number of scripts had to be changed because iproute started using
lower case letters in some spots, and I had to do it :)
next prev parent reply other threads:[~2008-10-07 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 18:24 Could you make vconfig less stupid? Stephen Hemminger
2008-10-06 22:26 ` Patrick McHardy
2008-10-07 2:32 ` Ben Greear
2008-10-07 11:31 ` Patrick McHardy
2008-10-07 12:20 ` Denys Fedoryshchenko
2008-10-07 12:24 ` Patrick McHardy
2008-10-07 12:48 ` Milan Kocian
2008-10-07 12:49 ` Denys Fedoryshchenko
2008-10-07 12:56 ` Patrick McHardy [this message]
2008-10-07 13:16 ` Martin Josefsson
2008-10-07 13:54 ` Patrick McHardy
2008-10-07 13:57 ` Patrick McHardy
2008-10-07 13:28 ` Milan Kocian
2008-10-07 13:29 ` Patrick McHardy
2008-10-07 14:06 ` Stephen Hemminger
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=48EB5C63.60501@trash.net \
--to=kaber@trash.net \
--cc=denys@visp.net.lb \
--cc=greearb@candelatech.com \
--cc=milon@wq.cz \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).