Incorrect MTU problem description
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Low
|
Deepti Navale |
Bug Description
Jiri Benc from Red Hat raised a bug (RH bug: 1148011) against the Configuration Reference Guide, section http://
=======
----
MTU bug with VXLAN tunnelling
Due to a bug in Linux Bridge software maximum transmission unit (MTU) handling, using VXLAN tunnels does not work by default.
----
This is incorrect and misleading. Bridging happens at layer 2 (Ethernet) and there's no concept of fragmentation at that layer. When a frame with a size exceeding target port MTU is to be transmitted, there's nothing the bridge can do other than dropping the frame. If an incoming frame is encapsulated into a tunnel header, its size is inevitably increased. If the frame was 1500 bytes long, it's over 1500 bytes after encapsulation.
I don't think there's a bug anywhere, this is just the behavior of networking (irritating behavior, granted). The documentation should be changed to not give the customers impression that there's a bug in our product that we're not fixing for some reason.
If you rather think this is indeed a bug in the Linux bridge, please explain how else should the bridge handle oversized frames.
=======
Raising this bug to fix this issue in the upstream Config reference guide.
Changed in openstack-manuals: | |
assignee: | nobody → Deepti Navale (dnavale) |
The discussion that led to this note can be found at https:/ /bugs.launchpad .net/openstack- manuals/ +bug/1242534 - any change should ensure that the original reports intent to help users in this case is preserved.