ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ifupdown (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
/e/n/i:
auto lo
iface lo inet loopback
dns-nameservers 10.245.168.2
dns-search dellstack
auto eth0
iface eth0 inet static
gateway 10.245.168.1
address 10.245.168.17/21
dns-nameservers 10.245.168.2
mtu 1500
auto eth1
iface eth1 inet manual
mtu 1500
auto eth1.2667
iface eth1.2667 inet static
address 10.245.184.20/24
vlan-raw-device eth1
mtu 9000
vlan_id 2667
output from networking startup:
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/
Drop-In: /run/systemd/
Active: failed (Result: exit-code) since Mon 2016-04-04 12:14:26 UTC; 1h 33min ago
Docs: man:interfaces(5)
Process: 1255 ExecStart=
Process: 868 ExecStartPre=
Main PID: 1255 (code=exited, status=1/FAILURE)
Apr 04 12:14:25 reflecting-
Apr 04 12:14:26 reflecting-
Apr 04 12:14:26 reflecting-
Apr 04 12:14:26 reflecting-
Apr 04 12:14:26 reflecting-
Apr 04 12:14:26 reflecting-
Apr 04 12:14:26 reflecting-
Apr 04 12:14:26 reflecting-
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ifupdown 0.8.10ubuntu1
ProcVersionSign
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Mon Apr 4 13:42:48 2016
SourcePackage: ifupdown
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in ifupdown (Ubuntu): | |
importance: | Undecided → High |
Turned out it was the mtu setting directly on the vlan interface that causes the problem:
auto eth1.2667
iface eth1.2667 inet static
address 10.245.184.20/24
vlan-raw-device eth1
mtu 9000
vlan_id 2667
mtu needs to be set on the underlying network device (eth1 in this case).