I have merged the netplan code to that effect in netplan master now - i.e. generate reloads udevadm rules.
However, I have now realised something. MTUBytes can be set in two places: NetDev.MTUBytes key in the .link file and in Link.MTUBytes key in the .network file. The .link setting is applied by udev, whereas the .network setting is applied by networkd on link up. I guess it matters if the link is managed by networkd subsequently or not. I wonder if we want to set mtu in .link file, .network, or both. Such that mtu is correct if networkd doesn't manage the interface (.link file alone), and the mtu is corrected upon link up too (.network setting) if it is changed, given that .link files are not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
