Public bug reported:
Networks with enabled vlan_transparency can be any of any type available in
Neutron (vxlan, vlan, flat in case of Linuxbridge, etc.). In most cases it is
fine when packets in such case have ethertype 0x8100 (802.1q).
The same ethertype is configured always for vlan network with
vlan_transparent=True. But in such case as we have 2 vlans already (S-Tag and
C-Tag) it is really QinQ. Neutron still configures ethertype to be 0x8100 in
such case and it works for most of the cases.
But in case of some hardware it needs to be 0x8a88 (802.1ad) which is real QinQ
type.
So I think that it would be good to add operators possibility to configure what
ethertype will be used in such case.
It could be simple config option and all vlan networks with enabled vlan
transparency would use it.
Default value of that option would be 0x8100 to be compatible with what we have
now.
** Affects: neutron
Importance: Wishlist
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: linuxbridge ml2 ovn rfe-triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1915151
Title:
[RFE] There should be a way to set ethertype for the vlan_transparent
networks
Status in neutron:
New
Bug description:
Networks with enabled vlan_transparency can be any of any type available in
Neutron (vxlan, vlan, flat in case of Linuxbridge, etc.). In most cases it is
fine when packets in such case have ethertype 0x8100 (802.1q).
The same ethertype is configured always for vlan network with
vlan_transparent=True. But in such case as we have 2 vlans already (S-Tag and
C-Tag) it is really QinQ. Neutron still configures ethertype to be 0x8100 in
such case and it works for most of the cases.
But in case of some hardware it needs to be 0x8a88 (802.1ad) which is real
QinQ type.
So I think that it would be good to add operators possibility to configure
what ethertype will be used in such case.
It could be simple config option and all vlan networks with enabled vlan
transparency would use it.
Default value of that option would be 0x8100 to be compatible with what we
have now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1915151/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
