Bug 1025188

Summary: bridge vlan doesn't show vlan ids
Product: Red Hat Enterprise Linux 7 Reporter: David Spurek <dspurek>
Component: iprouteAssignee: Pavel Šimerda (pavlix) <psimerda>
Status: CLOSED NOTABUG QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: ebenes, jaster, swadeley, vyasevic
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-23 09:42:02 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:
Bug Depends On:    
Bug Blocks: 1110700, 1191021    

Description David Spurek 2013-10-31 08:14:03 UTC 
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
Comment 1 Petr Šabata 2013-11-19 09:45:38 UTC 
'bridge' is a new tool.  This will be fixed in the next release.
Comment 3 Vlad Yasevich 2014-09-10 15:56:14 UTC 
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 7 Pavel Š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