Re: [openstack-dev] [Neutron] Linux Bridge MTU bug when the VXLAN tunneling is used

2013-10-20 Thread Édouard Thuleau
I had a look for fix that and I don't found a simple way. The minimal MTU can be deducted by the LB agent with the value found on the bridge and the LB agent can set it on veth interface connect to that bridge. But there no easy way to set it on the other side of the veth in the namespace. LB agen

Re: [openstack-dev] [Neutron] Linux Bridge MTU bug when the VXLAN tunneling is used

2013-10-20 Thread Salvatore Orlando
It might be worth both documenting this limitation on the admin guide and provide a fix which we should backport to havana too. It sounds like the fix should not be too extensive, so the backport should be easily feasible. Regards, Salvatore On 18 October 2013 21:50, Édouard Thuleau wrote: > H

[openstack-dev] [Neutron] Linux Bridge MTU bug when the VXLAN tunneling is used

2013-10-18 Thread Édouard Thuleau
Hi all, I made some tests with the ML2 plugin and the Linux Bridge agent with VXLAN tunneling. By default, physical interface (used for VXLAN tunneling) has an MTU of 1500 octets. And when LB agent creates a VXLAN interface, the MTU is automatically 50 octets less than the physical interface (so