Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1042799

Summary: Inconsistent detailed link information between "ip link" and "ip monitor link"
Product: Red Hat Enterprise Linux 6 Reporter: Antoni Segura Puimedon <asegurap>
Component: iprouteAssignee: Phil Sutter <psutter>
Status: CLOSED ERRATA QA Contact: Jaroslav Aster <jaster>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5CC: bazulay, danken, jaster, kzhang, mmarusic, ppisar, rkhan, tlavigne
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: iproute-2.6.32-46.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1042802 1042804 (view as bug list) Environment:
Last Closed: 2016-05-11 00:18:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1172231, 1275424    

Description Antoni Segura Puimedon 2013-12-13 12:17:57 UTC 
Description of problem:
In the output of "ip -d -o link show" and "ip -d -o monitor link" vlan and
macvlan devices are reported with the following form:
"device name" + "@" + "device name of the underlying device".

Since it is perfectly legal for another device to include symbols in their
names, e.g., "@", it is perfectly possible to have a dummy device called:
p1p3.13@p1p3

and a vlan device called p1p3.13 that is being reported as
p1p3.13@p1p3

In the output of "ip -d -o link show" this is disambiguable thanks to the fact
that dummies, vlans and macvlans have their type shown in the final segment:

    21: p1p3.13@p1p3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN \    link/ether 00:10:18:e1:6c:f4 brd ff:ff:ff:ff:ff:ff\    vlan id 13 <REORDER_HDR>
    23: p1p3.13@p1p3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN \    link/ether 82:17:ed:f9:e8:f3 brd ff:ff:ff:ff:ff:ff\    dummy 

However, the output of "ip -d -o monitor link" doesn't include the type
information for any device (not even for just vlanned and dummy types like
"ip -d -o link show" does). E.g.:
    23: p1p3.13@p1p3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN \    link/ether c2:01:5c:db:bd:39 brd ff:ff:ff:ff:ff:ff
    21: p1p3.13@p1p3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN \    link/ether 00:10:18:e1:6c:f4 brd ff:ff:ff:ff:ff:ff

Without a priori knowledge (having executed before a detailed link show and
keeping a database by interface index) there is no way to tell that the former
is a dummy and the latter is the vlan.

Version-Release number of selected component (if applicable): all


How reproducible: 100%


Steps to Reproduce:
1. start the monitor "ip -d -o monitor link"
2. Create vlan 13 over a nic (for example named p1p3)
3. Create a dummy called "p1p3.13@p1p3"
4. Check the detailed link monitor output

Actual results:
    23: p1p3.13@p1p3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN \    link/ether c2:01:5c:db:bd:39 brd ff:ff:ff:ff:ff:ff
    21: p1p3.13@p1p3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN \    link/ether 00:10:18:e1:6c:f4 brd ff:ff:ff:ff:ff:ff


Expected results:
    23: p1p3.13@p1p3: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN \    link/ether c2:01:5c:db:bd:39 brd ff:ff:ff:ff:ff:ff\    dummy 
    21: p1p3.13@p1p3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN \    link/ether 00:10:18:e1:6c:f4 brd ff:ff:ff:ff:ff:ff\    vlan id 13 <REORDER_HDR>
Comment 2 Pavel Šimerda (pavlix) 2014-09-11 09:47:55 UTC 
(In reply to Antoni Segura Puimedon from comment #0)
> Steps to Reproduce:
> 1. start the monitor "ip -d -o monitor link"
> 2. Create vlan 13 over a nic (for example named p1p3)
> 3. Create a dummy called "p1p3.13@p1p3"
> 4. Check the detailed link monitor output

0. on separate terminal: ip -d -o monitor link
1. ip link add name d type dummy
2. ip link add name v link d type vlan id 1
3. ip link add name v@d type dummy
Comment 12 errata-xmlrpc 2016-05-11 00:18:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0895.html