Boot-time vlan network setup fails

[DimanNe]

It seems that vlan network setup fails at boot-time (but all works well after boot).

This regression was introduced several (2-3) day ago.

My /etc/network/interfaces
$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto eth0.10
        iface eth0.10 inet dhcp

auto eth0.20
        iface eth0.20 inet manual

auto dsl-provider
iface dsl-provider inet ppp
pre-up /sbin/ifconfig eth0.20 up # line maintained by pppoeconf
provider dsl-provider

During boot I see "Waiting for network configuration...", after boot in ifconfig -a output I does NOT see eht0.10 and eth0.20 interfaces.

But, if I run manually these commands AFTER boot
ip link add link eth0 name eth0.10 type vlan id 10
ip link add link eth0 name eth0.20 type vlan id 20
pon dsl-provider

all works perfectly.

Also I tried to add "8021q" in /etc/modules but it did not help.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-19-generic 3.13.0-19.39
ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dimanne 2784 F.... pulseaudio
 /dev/snd/controlC0: dimanne 2784 F.... pulseaudio
CurrentDesktop: KDE
Date: Mon Mar 24 22:29:13 2014
HibernationDevice: RESUME=UUID=e70873bf-d62f-4b4c-9f3c-823f35acb596
InstallationDate: Installed on 2013-11-11 (133 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: System manufacturer System Product Name
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=b5fff7d9-81c4-43c5-94b6-902286582c80 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-19-generic N/A
 linux-backports-modules-3.13.0-19-generic N/A
 linux-firmware 1.126
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-02-21 (31 days ago)
dmi.bios.date: 12/04/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0202
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0202:bd12/04/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Alberto Salvia Novella (es20490446e)]

It affects an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse).

[Joseph Salisbury (jsalisbury)]

Does this issue go away if you boot back into the previous kernel version?

[DimanNe (dimanne)]

I tried first available 3.13.* kernel (in my case it was 3.13.0-11-generic) and issue did NOT go away. Network configuration does not work.

[Joseph Salisbury (jsalisbury)]

That may indicate this is not a kernel bug. Can you test the upstream 3.11 final kernel to see if it has the bug or not? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/

[DimanNe (dimanne)]

I tried (already installed) 3.11.0-17-generic kernel (I thought it is not so important to test exactly the kernel version you pointed out), and issue also did NOT go away. It is still here. So it really seems that it is not kernel bug. But it is apparently bug.

[DimanNe (dimanne)]

Ping

But still here

[Joseph Salisbury (jsalisbury)]

Adding network-manager for review.

[Mathieu Trudel-Lapierre (cyphermox)]

NetworkManager is unrelated here; since this happens based on config in /etc/network/interfaces. There are also no logs from NetworkManager in the attached syslog; marking as Invalid for network-manager.

Could this be an issue because the 'vlan' package is not installed? (I could not see it in Dependencies, I can only assume it's not installed)

[DimanNe (dimanne)]

Thank you very much.

Of course, it is very interesting why (and by what system update) it was removed, or how it was working before (in case if vlan package was not installed at all). But, after installing all start working! Thanks!

[Tom (tomhek)]

Problem was solved over here by installing vlan_1.9-3ubuntu10, which got removed by the upgrade from 13.10 to 14.04.

[Sune Bredahl (sune-bredahl-deactivatedaccount)]

Installing vlan_1.9-3ubuntu10 solved my vlan interface issues too (introduced by upgrading from Xubuntu 13.10 to 14.04), thanks Tom!