neutron creates wrong vlan_tci filter in flow for gateway on flat external network and drops all PCP / QOS frames
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Medium
|
Slawek Kaplonski |
Bug Description
neutron creates wrong vlan_tci filter in flow for gateway on flat external network
How reproducible:
Before:
~~~
[root@overcloud
cookie=
cookie=
cookie=
cookie=
cookie=
cookie=
~~~
Create router on flat network:
~~~
openstack network create provider2 --provider-
openstack subnet create --network provider2 --subnet-range 10.1.0.0/24 provider2-subnet
openstack router create router2
openstack router set --external-gateway provider2 router2
~~~
After:
~~~
[root@overcloud
cookie=
cookie=
cookie=
cookie=
cookie=
cookie=
cookie=
[root@overcloud
~~~
The problematic rule is:
~~~
cookie=
~~~
This filter here:
vlan_tci=
Needs to be:
vlan_tci=
The existing filter works fine for frames without a dot1q tag. The filter does not work for dot1q tagged frames on VLAN 0. E.g., it COP is modified, frames with VLAN 0 and a COP value will be dropped.
~~~
man ovs-ofctl
(...)
The value that vlan_tci matches against is 0 for a packet that has no 802.1Q header. Otherwise, it is the TCI value from the 802.1Q header with the CFI bit (with value 0x1000) forced to 1.
~~~
We should not be filtering on the DCI bit, as it can be 0 or 1.
Additional info:
See https:/
Changed in neutron: | |
assignee: | nobody → Slawek Kaplonski (slaweq) |
status: | New → Confirmed |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/613239
Review: https:/