Reviewed: https://review.opendev.org/c/openstack/neutron/+/796637 Committed: https://opendev.org/openstack/neutron/commit/c7e1de09e1fd221ab9d5880165baaa3f34678c35 Submitter: "Zuul (22348)" Branch: master
commit c7e1de09e1fd221ab9d5880165baaa3f34678c35 Author: Slawek Kaplonski <[email protected]> Date: Wed Jun 16 14:03:33 2021 +0200 [Docs] Add info about vlan transparent networks' MTU MTU configured inside instances which are connected to the networks with enabled transparent vlan needs to have MTU set to 4 bytes less than it is provided by DHCP to make space for additional vlan header. This is required only if instance will have some vlan tagged interfaces configured. Closes-bug: #1906318 Change-Id: Ia6691cbe35a1e874857ec94660ac4b1850586305 ** Changed in: neutron Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1906318 Title: MTU for networks with enabled vlan transparency should be 4 bytes lower Status in neutron: Fix Released Bug description: For networks when VLAN transparency is enabled, mtu value returned by get_mtu should be lower by 4 bytes to make space for that additional vlan tag which is added by the VM. The problem here is that get_mtu() method in the type drivers currently only gets physical_network as parameter so there is no way to check if network has or hasn't got vlan_transparency enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1906318/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
