Change Details

Based on the bridge(4) feature, this change allows updating the MTU of an existing lagg interface. Previously, changing the MTU would require destroying the lagg and creating a new one. Now it is allowed to change the MTU of the lagg ports and then update the MTU of the lagg itself if all the ports match the new MTU. While this does open the possibility of misconfiguration by incorrectly changing the MTU of a port after lagg creation, this is consistent with the behavior of bridge(4), and the benefit of not having to completely destroy and recreate the interface to change MTU seems greater than the risk of accidentally configuring a port wrong.

Previously, changing the MTU would require destroying the lagg and creating a new one. Now it is allowed to change the MTU of the lagg interface. The MTU of the ports will be set to match. If any port cannot set the new MTU, all ports are reverted to the original MTU of the lagg.

Based on the bridge(4) feature, this change allows updating the MTU of an existing lagg interface. Previously, changing the MTU would require destroying the lagg and creating a new one. Now it is allowed to change the MTU of the lagg ports and then update the MTU of the lagg itself if all the ports match the new MTU. While this does open the possibility of misconfiguration by incorrectly changing the MTU of a port after lagg creation,interface. The MTU of the ports will be set to match. this is consistent withIf any port cannot set the behavior of bridge(4)new MTU, and the benefit of not having to completely destroy and recreate the interface to change MTU seems greater than the risk of accidentally configuring a port wronll ports are reverted to the original MTU of the lagg.