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.
Description of problem:
bridge vlan doesn't show vlan ids
Version-Release number of selected component (if applicable):
iproute-3.10.0-5.el7
kernel-3.10.0-37.el7
How reproducible:
always
Steps to Reproduce:
1.ip link add testbridge type bridge
2.ip link add dummy0 type dummy
3.ip link add link dummy0 name dummy0.10 type vlan id 10
4.ip link set dummy0.10 master testbridge
5.bridge vlan
Actual results:
[test]bridge vlan
port vlan ids
dummy0.10 None
Expected results:
[test]bridge vlan
port vlan ids
dummy0.10 10
Additional info:
results with ip link add link dummy0 name dummy0.10 type vlan id 10 reorder_hdr off|on are the same
Not sure this is a valid bug.
'bridge vlan show' will show the vlan information that the bridge will
see comming from each port.
In the configuration from Comment 0, port dummy0.10 will not pass any vlan
information to the bridge and the port is a vlan and by the type the
packet gets to the bridge it contains no vlan information.
And, no you can't work around this by doing
# ip l a testbridge type bridge
# ip l a dummy0 type dummy
# ip l s dummy0 master testbridge
# ip l a link dummy0 type vlan id 10
In this configuration, the bridge will not see any vlan tagged traffic
at all, as vlan processing takes priority over the bridge and the packets
will be handed to the vlan device for processesing.
Now what can be done is something like
# ip l a testbridge type bridge
# ip l a dummy0 type dummy
# ip l s dummy0 master testbridge
# ip l a link testbridge type vlan id 10
# bridge vlan show
port vlan ids
testbridge 10
This would require a kernel change.
-vlad
Comment 7Pavel Šimerda (pavlix)
2015-04-23 09:42:02 UTC
(In reply to Vlad Yasevich from comment #3)
> Not sure this is a valid bug.
>
> 'bridge vlan show' will show the vlan information that the bridge will
> see comming from each port.
>
> In the configuration from Comment 0, port dummy0.10 will not pass any vlan
> information to the bridge and the port is a vlan and by the type the
> packet gets to the bridge it contains no vlan information.
>
> And, no you can't work around this by doing
>
> # ip l a testbridge type bridge
> # ip l a dummy0 type dummy
> # ip l s dummy0 master testbridge
> # ip l a link dummy0 type vlan id 10
>
> In this configuration, the bridge will not see any vlan tagged traffic
> at all, as vlan processing takes priority over the bridge and the packets
> will be handed to the vlan device for processesing.
>
> Now what can be done is something like
>
> # ip l a testbridge type bridge
> # ip l a dummy0 type dummy
> # ip l s dummy0 master testbridge
> # ip l a link testbridge type vlan id 10
>
> # bridge vlan show
> port vlan ids
> testbridge 10
>
> This would require a kernel change.
>
> -vlad
Thanks for information. We discussed it and agreed that the reported issue is not a bug.
Cheers,
Pavel