Comment 4 for bug 1804861
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Looks like I couldn't reproduce because I have been setting a custom MAC on the bond interface rather than using the MAC from one of the underlying devices.
If an existing physical MAC is used for the bond, then the matching in systemd/udev works such that MTU will be applied to all the interfaces with that MAC. If not all of them get the right MTU, it's because this may end up being racy.
There are two solutions to this:
- match on macaddress *and* driver (or name, but driver should be more solid) on the physical interfaces, such that the MTU is only applied to the devices that match both the MAC address and driver tuple exactly.
- set a custom MAC that isn't the MAC address from one of the underlying interfaces on the bond
I don't think we can address this in netplan programmatically, since that would break the matching story if we were to implicitly add matching rules without them appearing in the configuration file.