[pve-devel] Process to submit patches

[Dietmar Maurer]

> We have been running this successfully for a few weeks now on the default PVE
> kernel with no issues.
> 
> I searched the list archives, and the issues I could see looked like they were
> related to the MTU on the parent physical interface being too small.
> 
> Linux does not clearly differentiate between L2 (interface) and L3 (IP) MTU, and
> also has a hidden 4 byte allowance on the interface MTU, making it confusing.
> When running QinQ the parent physical interface needs a MTU of at least 1504
> bytes (allows a 1508 byte frame), any sub vlan's and bridges will then inherit this
> MTU allowing for the "inner" tag to pass externally correctly.
> 
> Obviously if the users are not doing QinQ the parent physical interface can be
> the default 1500byte MTU and will work perfectly.

@Alexandre: Do you have some spare time to test that again using MTU 1504?