[Touch-packages] [Bug 1577382] Re: Network fails to start if VLAN have bigger MTU than default
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577382 Title: Network fails to start if VLAN have bigger MTU than default Status in network-manager package in Ubuntu: Expired Bug description: Hello, Looks like a bug for me. If I configure interface VLAN with bigger MTU than 1500, which is default, interface with VLAN fail to start. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009. May 2 14:40:16 demo-host sh[2184]: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config May 2 14:40:16 demo-host sh[2184]: RTNETLINK answers: Numerical result out of range May 2 14:40:16 demo-host sh[2184]: Failed to bring up eno3.1009. auto eno3 iface eno3 inet manual mtu 1550 auto eno3.805 iface eno3.805 inet manual vlan-raw-device eno3 mtu 1500 auto eno3.1009 iface eno3.1009 inet static vlan-raw-device eno3 address 10.20.30.7 netmask 255.255.255.0 mtu 1550 eno3 and eno3.805 starts successfully, but eno3.1009 not. If I look at syslog, I can see, that interface boot order goes from last interface in config to first: ~# cat /var/log/syslog|grep -i "Started ifup for eno3" May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.805. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3. This is really strange, I suppose it should have some kind of order in such cases. If I change configuration, e.g., eno3.1009 configure before eno3, host boots successfully with configured VLAN, but I suppose it could fail in some cases anyway. So looks like we need some kind of "order" configuration in which we can setup after what cases we can take up interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577382] Re: Network fails to start if VLAN have bigger MTU than default
@Martins, I want to know what's the MTU configured on eno3 interface, that one should be >= mtu of vlan interface. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577382 Title: Network fails to start if VLAN have bigger MTU than default Status in network-manager package in Ubuntu: Incomplete Bug description: Hello, Looks like a bug for me. If I configure interface VLAN with bigger MTU than 1500, which is default, interface with VLAN fail to start. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009. May 2 14:40:16 demo-host sh[2184]: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config May 2 14:40:16 demo-host sh[2184]: RTNETLINK answers: Numerical result out of range May 2 14:40:16 demo-host sh[2184]: Failed to bring up eno3.1009. auto eno3 iface eno3 inet manual mtu 1550 auto eno3.805 iface eno3.805 inet manual vlan-raw-device eno3 mtu 1500 auto eno3.1009 iface eno3.1009 inet static vlan-raw-device eno3 address 10.20.30.7 netmask 255.255.255.0 mtu 1550 eno3 and eno3.805 starts successfully, but eno3.1009 not. If I look at syslog, I can see, that interface boot order goes from last interface in config to first: ~# cat /var/log/syslog|grep -i "Started ifup for eno3" May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.805. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3. This is really strange, I suppose it should have some kind of order in such cases. If I change configuration, e.g., eno3.1009 configure before eno3, host boots successfully with configured VLAN, but I suppose it could fail in some cases anyway. So looks like we need some kind of "order" configuration in which we can setup after what cases we can take up interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577382] Re: Network fails to start if VLAN have bigger MTU than default
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577382 Title: Network fails to start if VLAN have bigger MTU than default Status in network-manager package in Ubuntu: New Bug description: Hello, Looks like a bug for me. If I configure interface VLAN with bigger MTU than 1500, which is default, interface with VLAN fail to start. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009. May 2 14:40:16 demo-host sh[2184]: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config May 2 14:40:16 demo-host sh[2184]: RTNETLINK answers: Numerical result out of range May 2 14:40:16 demo-host sh[2184]: Failed to bring up eno3.1009. auto eno3 iface eno3 inet manual mtu 1550 auto eno3.805 iface eno3.805 inet manual vlan-raw-device eno3 mtu 1500 auto eno3.1009 iface eno3.1009 inet static vlan-raw-device eno3 address 10.20.30.7 netmask 255.255.255.0 mtu 1550 eno3 and eno3.805 starts successfully, but eno3.1009 not. If I look at syslog, I can see, that interface boot order goes from last interface in config to first: ~# cat /var/log/syslog|grep -i "Started ifup for eno3" May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.805. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3. This is really strange, I suppose it should have some kind of order in such cases. If I change configuration, e.g., eno3.1009 configure before eno3, host boots successfully with configured VLAN, but I suppose it could fail in some cases anyway. So looks like we need some kind of "order" configuration in which we can setup after what cases we can take up interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577382] Re: Network fails to start if VLAN have bigger MTU than default
** Tags added: xenial ** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1577382 Title: Network fails to start if VLAN have bigger MTU than default Status in network-manager package in Ubuntu: New Bug description: Hello, Looks like a bug for me. If I configure interface VLAN with bigger MTU than 1500, which is default, interface with VLAN fail to start. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009. May 2 14:40:16 demo-host sh[2184]: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config May 2 14:40:16 demo-host sh[2184]: RTNETLINK answers: Numerical result out of range May 2 14:40:16 demo-host sh[2184]: Failed to bring up eno3.1009. auto eno3 iface eno3 inet manual mtu 1550 auto eno3.805 iface eno3.805 inet manual vlan-raw-device eno3 mtu 1500 auto eno3.1009 iface eno3.1009 inet static vlan-raw-device eno3 address 10.20.30.7 netmask 255.255.255.0 mtu 1550 eno3 and eno3.805 starts successfully, but eno3.1009 not. If I look at syslog, I can see, that interface boot order goes from last interface in config to first: ~# cat /var/log/syslog|grep -i "Started ifup for eno3" May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.1009. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3.805. May 2 14:40:16 demo-host systemd[1]: Started ifup for eno3. This is really strange, I suppose it should have some kind of order in such cases. If I change configuration, e.g., eno3.1009 configure before eno3, host boots successfully with configured VLAN, but I suppose it could fail in some cases anyway. So looks like we need some kind of "order" configuration in which we can setup after what cases we can take up interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1577382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
