From: John Fastabend <john.r.fastabend@intel•com>
To: "Fabien C." <kczy1jafrl3jpq1@jetable•org>
Cc: netdev@vger•kernel.org
Subject: Re: [iproute2] display vlan configuration
Date: Thu, 05 Jul 2012 16:20:38 -0700 [thread overview]
Message-ID: <4FF62146.9070702@intel.com> (raw)
In-Reply-To: <4FF61DE9.7000507@jetable.org>
On 7/5/2012 4:06 PM, Fabien C. wrote:
> Hello,
>
> it looks like there is no way to show the vlan configuration with iproute (nor with any other tool apparently).
>
> This can lead to trouble since :
> # ip link add link eth0 name eth2.333 type vlan id 444
>
> will create an interface that will show up like this with "ip link show" :
> 51: eth2.333@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
>
> The only hint we have is the interface name, which may not be related to the vlan id we set earlier.
Here you need to show the details,
#ip -d link show dev eth2.333
From my current setup,
# ip -d link show dev vlan0
33: vlan0@eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 00:1b:21:55:23:59 brd ff:ff:ff:ff:ff:ff
vlan id 101 <REORDER_HDR>
next prev parent reply other threads:[~2012-07-05 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 23:06 [iproute2] display vlan configuration Fabien C.
2012-07-05 23:20 ` John Fastabend [this message]
2012-07-07 16:03 ` Fabien C.
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=4FF62146.9070702@intel.com \
--to=john.r.fastabend@intel$(echo .)com \
--cc=kczy1jafrl3jpq1@jetable$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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