From 79926486a01fdd8fc55432200886c83a1622875f Mon Sep 17 00:00:00 2001 From: Imran Haider Date: Sat, 2 Sep 2017 23:25:21 -0400 Subject: [PATCH] Set MTU on bond master as opposed to a bond slave Prior to this commit, the MTU setting was applied to a bond slave interface. In older versions of the Linux kernel, this setting propagated to the bond master and the other bond slaves associated with the master. In recent versions of the kernel (observed in Linux 4.12), increasing the MTU of a slave does not automatically increase the MTU of the master. This allows for more flexibility but requires the MTU of the master to be changed manually. Ideally, the MTU setting should be applied to the bond master and the setting will propagate to the bond slaves, since the slaves are required to have a MTU that is greater than or equal to the bond master. --- modules.d/40network/ifup.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules.d/40network/ifup.sh b/modules.d/40network/ifup.sh index 687b5707f..0db3c0213 100755 --- a/modules.d/40network/ifup.sh +++ b/modules.d/40network/ifup.sh @@ -257,7 +257,7 @@ if [ -z "$NO_BOND_MASTER" ]; then done # Set mtu on bond master - [ -n "$bondmtu" ] && ip link set mtu $bondmtu dev $netif + [ -n "$bondmtu" ] && ip link set mtu $bondmtu dev $bondname # add the bits to setup the needed post enslavement parameters for arg in $bondoptions ; do -- 2.47.2