You have been subscribed to a public bug: Environment: Ubuntu 15.10 Linux cluster-02.home.arswiki.org 4.2.0-25-generic #30-Ubuntu SMP Mon Jan 18 12:31:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Objective: Configure host using lacp (bonded) interface with access to multiple vlans with 1 vlan configured for jumbo frames (mtu=9000); all other vlans are configured for standard mtu (1500). Issues: I am unable to define a configuration in /etc/network/interfaces that works as desired on boot. I can create a configuration that works after boot (systemctl stop networking && systemctl start networking). The interfaces will show up (ip) but the mtu will be 1500 instead of the desired 9000. References: 1. I tried the workaround in this but, but it doesn't work in the latest version of Ubuntu server: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007 Details: Given this /etc/network/interfaces: - 4 physical interfaces (mtu=9000) - 1 bond interfage (mtu=9000) - a series of vlan interfaces, bond0.x (bond0.80 mtu=9000, all others mtu=1500) - a series of bridge interfaces, brxx, bridge with the vlan interface root@cluster-02:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback auto enp0s20f0 iface enp0s20f0 inet manual bond-master bond0 mtu 9000 auto enp0s20f1 iface enp0s20f1 inet manual bond-master bond0 mtu 9000 auto enp0s20f2 iface enp0s20f2 inet manual bond-master bond0 mtu 9000 auto enp0s20f3 iface enp0s20f3 inet manual bond-master bond0 mtu 9000 auto bond0 iface bond0 inet manual bond-mode 802.3ad bond-miimon 100 bond-lacp-rate 1 bond-slaves none bond-xmit-hash-policy layer3+4 mtu 9000 auto bond0.5 iface bond0.5 inet manual vlan_raw_device bond0 mtu 1500 auto bond0.10 iface bond0.10 inet manual vlan_raw_device bond0 mtu 1500 auto bond0.20 iface bond0.20 inet manual vlan_raw_device bond0 mtu 1500 auto bond0.30 iface bond0.30 inet manual vlan_raw_device bond0 mtu 1500 auto bond0.40 iface bond0.40 inet manual vlan_raw_device bond0 mtu 1500 auto bond0.70 iface bond0.70 inet manual vlan_raw_device bond0 mtu 1500 auto bond0.80 iface bond0.80 inet manual vlan_raw_device bond0 mtu 9000 auto br5 iface br5 inet manual bridge_ports bond0.5 mtu 1500 auto br10 iface br10 inet manual bridge_ports bond0.10 mtu 1500 auto br20 iface br20 inet manual bridge_ports bond0.20 mtu 1500 auto br30 iface br30 inet manual bridge_ports bond0.30 mtu 1500 auto br40 iface br40 inet static address 10.0.20.58 netmask 255.255.252.0 broadcast 10.0.23.255 gateway 10.0.20.1 bridge_ports bond0.40 mtu 1500 dns-nameservers 10.0.20.250 dns-nameservers 10.0.20.252 auto br70 iface br70 inet manual bridge_ports bond0.70 mtu 1500 auto br80 iface br80 inet manual bridge_ports bond0.80 mtu 9000 Now, the configuration looks correct, but it does not work as intended. The mtu is set as follows, per interface, after boot: root@cluster-02:~# ip l |grep mtu 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 2: enp0s20f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 3: enp0s20f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 4: enp0s20f2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 5: enp0s20f3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default 7: bond0.5@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br5 state UP mode DEFAULT group default 8: bond0.10@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br10 state UP mode DEFAULT group default 9: bond0.20@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br20 state UP mode DEFAULT group default 10: bond0.30@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br30 state UP mode DEFAULT group default 11: bond0.40@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br40 state UP mode DEFAULT group default 12: bond0.70@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br70 state UP mode DEFAULT group default 13: bond0.80@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br80 state UP mode DEFAULT group default 14: br5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 15: br10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 16: br40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 17: br20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 18: br70: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 19: br30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 20: br80: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default /var/log/syslog shows the following: Jan 31 21:43:30 cluster-02 systemd-udevd[487]: Could not generate persistent MAC address for bond0.80: No such file or directory Jan 31 21:43:30 cluster-02 systemd-udevd[486]: Could not generate persistent MAC address for br80: No such file or directory Jan 31 21:43:30 cluster-02 systemd[1]: Found device /sys/subsystem/net/devices/bond0.80. Jan 31 21:43:30 cluster-02 systemd[1]: Found device /sys/subsystem/net/devices/br80. Jan 31 21:43:30 cluster-02 systemd[1]: Started ifup for bond0.80. Jan 31 21:43:30 cluster-02 sh[4934]: Failed to bring up bond0.80. Jan 31 21:43:30 cluster-02 systemd[1]: Started ifup for br80. Jan 31 21:43:30 cluster-02 networking[5234]: * Configuring network interfaces... Jan 31 21:43:30 cluster-02 sh[5114]: Waiting for br80 to get ready (MAXWAIT is 32 seconds). Jan 31 21:43:30 cluster-02 systemd[1]: ifup@bond0.80.service: Main process exited, code=exited, status=1/FAILURE Jan 31 21:43:30 cluster-02 networking[5234]: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Jan 31 21:43:30 cluster-02 networking[5234]: RTNETLINK answers: Numerical result out of range Jan 31 21:43:30 cluster-02 networking[5234]: Failed to bring up bond0.80. Jan 31 21:43:30 cluster-02 sh[4818]: device bond0.80 is already a member of a bridge; can't enslave it to bridge br80. Jan 31 21:43:30 cluster-02 networking[5234]: ...done. Jan 31 21:43:30 cluster-02 kernel: [ 13.893031] device bond0.80 entered promiscuous mode Jan 31 21:43:31 cluster-02 kernel: [ 21.782774] br80: port 1(bond0.80) entered forwarding state Jan 31 21:43:31 cluster-02 kernel: [ 21.782782] br80: port 1(bond0.80) entered forwarding state Jan 31 21:43:31 cluster-02 sh[5114]: RTNETLINK answers: Invalid argument Jan 31 21:43:31 cluster-02 sh[5114]: Failed to bring up br80. Jan 31 21:43:31 cluster-02 systemd[1]: ifup@br80.service: Main process exited, code=exited, status=1/FAILURE Jan 31 21:43:46 cluster-02 kernel: [ 36.825980] br80: port 1(bond0.80) entered forwarding state If I restart networking on the console (systemctl restart networking), everything comes up configured as expected without any errors in /var/log/syslog. This is how the mtu is configured for each interface after restarted networking: root@cluster-02:~# ip l |grep mtu 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 2: enp0s20f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 3: enp0s20f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 4: enp0s20f2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 5: enp0s20f3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 20: br80: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default 21: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default 22: bond0.5@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br5 state UP mode DEFAULT group default 23: br5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 24: bond0.10@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br10 state UP mode DEFAULT group default 25: br10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 26: bond0.20@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br20 state UP mode DEFAULT group default 27: br20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 28: bond0.30@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br30 state UP mode DEFAULT group default 29: br30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 30: bond0.40@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br40 state UP mode DEFAULT group default 31: br40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 32: bond0.70@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br70 state UP mode DEFAULT group default 33: br70: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default 34: bond0.80@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue master br80 state UP mode DEFAULT group default So... what is different when networking is started at boot versus after boot? ** Affects: ubuntu Importance: Undecided Status: New -- Unable to set mtu when using bonding (802.3ad), vlan, and bridge https://bugs.launchpad.net/bugs/1540213 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
