Public bug reported:
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.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: 16.04 bot-comment interfaces network ubuntu
** Description changed:
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
+ mtu 1550
auto eno3.805
iface eno3.805 inet manual
- vlan-raw-device eno3
- mtu 1500
+ 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
+ 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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577382
Title:
Network fails to start if VLAN have bigger MTU than default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1577382/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
