[NETVIRT-145] push vlan rules in table=220 are creating a different vlan header than the incoming one Created: 14/Sep/16 Updated: 07/Dec/16 Resolved: 07/Dec/16 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Koby Aizer | Assignee: | Koby Aizer |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6723 |
| Description |
|
When working with a vlan provider external network, those are the rules which are created In table 0, we pop the vlan=805: In table 220, when we output to the external gateway, we set the same VID but with an extra DEI/CFI bit (bit 13): Seems to be originated in the openflowplugin code which is used in netvirt: pushVlanActionBuilder.setCfi(new VlanCfi(1)) |
| Comments |
| Comment by Alon Kochba [ 29/Nov/16 ] |
|
(In reply to Koby Aizer from comment #0) Though very annoying, it seems this is according to the standard.. See OF_VLAN_VID in p56 - https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.3.3.pdf OXM_OF_VLAN_VID 12+1 2 Yes None VLAN-ID from 802.1Q header. The CFI bit indicate |