Commit 499add9c authored by Beniamino Galvani's avatar Beniamino Galvani Committed by Lubomir Rintel
Browse files

device: fix reapply of MTU

When we set the MTU on the link we remember its previous source
(ip-config, parent-device or connection profile) and don't change it
again afterwards to avoid interfering with user's manual changes. The
only exceptions when we change it again are (1) if the parent device
MTU changes and (2) if the new MTU has higher priority than the one
previously set.

To allow a live reapply of the MTU property we also need to clear the
saved source, or the checks described above will prevent setting the
new value.

Fixes: 2f891723 ('device: rework mtu priority handling')
(cherry picked from commit 4ed72fa6)
(cherry picked from commit e738479b)
parent 1ef8bcc3
...@@ -11312,6 +11312,9 @@ check_and_reapply_connection (NMDevice *self, ...@@ -11312,6 +11312,9 @@ check_and_reapply_connection (NMDevice *self,
s_ip6_old = nm_connection_get_setting_ip6_config (con_old); s_ip6_old = nm_connection_get_setting_ip6_config (con_old);
s_ip6_new = nm_connection_get_setting_ip6_config (con_new); s_ip6_new = nm_connection_get_setting_ip6_config (con_new);
/* Allow reapply of MTU */
priv->mtu_source = NM_DEVICE_MTU_SOURCE_NONE;
nm_device_reactivate_ip4_config (self, s_ip4_old, s_ip4_new); nm_device_reactivate_ip4_config (self, s_ip4_old, s_ip4_new);
nm_device_reactivate_ip6_config (self, s_ip6_old, s_ip6_new); nm_device_reactivate_ip6_config (self, s_ip6_old, s_ip6_new);
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment