You have been subscribed to a public bug: Binary package hint: vlan
After rebooting my system yesterday, my vlan interface did not come up. I know that update-manager had been upgrading packages several times since the last reboot before that, but I don't know which ones were updated. I have this in /etc/network/interfaces: auto lo iface lo inet loopback auto eth0.20 iface eth0.20 inet dhcp this configuration had been working fine for several months before the problem started. I see the following in syslog: Feb 11 10:35:00 alexeyt dhclient: Internet Systems Consortium DHCP Client V3.1.3 Feb 11 10:35:00 alexeyt dhclient: Copyright 2004-2009 Internet Systems Consortium. Feb 11 10:35:00 alexeyt dhclient: All rights reserved. Feb 11 10:35:00 alexeyt dhclient: For info, please visit https://www.isc.org/software/dhcp/ Feb 11 10:35:00 alexeyt dhclient: Feb 11 10:35:00 alexeyt modem-manager: (net/eth0.20): could not get port's parent device Feb 11 10:35:00 alexeyt NetworkManager[884]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 11 10:35:00 alexeyt NetworkManager[884]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Feb 11 10:35:00 alexeyt NetworkManager[884]: <warn> /sys/devices/virtual/net/eth0.20: couldn't determine device driver; ignoring... Feb 11 10:35:00 alexeyt dhclient: Listening on LPF/eth0.20/00:1e:4f:b3:18:db Feb 11 10:35:00 alexeyt dhclient: Sending on LPF/eth0.20/00:1e:4f:b3:18:db Feb 11 10:35:00 alexeyt dhclient: Sending on Socket/fallback Feb 11 10:35:00 alexeyt dhclient: DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 3 Feb 11 10:35:00 alexeyt dhclient: send_packet: Network is down Feb 11 10:35:00 alexeyt dhclient: receive_packet failed on eth0.20: Network is down Feb 11 10:35:03 alexeyt dhclient: DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 4 Feb 11 10:35:03 alexeyt dhclient: send_packet: Network is down Feb 11 10:35:07 alexeyt dhclient: DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 11 Feb 11 10:35:07 alexeyt dhclient: send_packet: Network is down Feb 11 10:35:18 alexeyt dhclient: DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 18 Feb 11 10:35:18 alexeyt dhclient: send_packet: Network is down Feb 11 10:35:36 alexeyt dhclient: DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 21 Feb 11 10:35:36 alexeyt dhclient: send_packet: Network is down Feb 11 10:35:57 alexeyt dhclient: DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 4 Feb 11 10:35:57 alexeyt dhclient: send_packet: Network is down Feb 11 10:36:01 alexeyt dhclient: No DHCPOFFERS received. Feb 11 10:36:01 alexeyt dhclient: No working leases in persistent database - sleeping. And indeed, if I do an 'ip link ls' in the time frame that dhclient3 is trying to get a lease, I see that the interfaces are down: $ ip link ls 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 00:1e:4f:b3:18:db brd ff:ff:ff:ff:ff:ff 3: eth0.20@eth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN link/ether 00:1e:4f:b3:18:db brd ff:ff:ff:ff:ff:ff However, if I manually do: sudo ifdown eth0.20 sudo ip link add link eth0 eth0.20 type vlan id 20 sudo ip link set eth0.20 up sudo dhclient3 eth0.20 Then the interface comes up fine (I'm submitting this bug report through it :-) Some package versions that might be interesting: $ dpkg-query -l *linux-image* vlan ifupdown dhcp3-client |cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-====================================-=================================================-========================================================================== ii dhcp3-client 3.1.3-2ubuntu6 DHCP client ii ifupdown 0.6.10ubuntu3.1 high level tools to configure network interfaces un linux-image <none> (no description available) un linux-image-2.6 <none> (no description available) ii linux-image-2.6.35-22-generic 2.6.35-22.35 Linux kernel image for version 2.6.35 on x86/x86_64 ii linux-image-2.6.35-23-generic 2.6.35-23.41 Linux kernel image for version 2.6.35 on x86/x86_64 ii linux-image-2.6.35-24-generic 2.6.35-24.42 Linux kernel image for version 2.6.35 on x86/x86_64 ii linux-image-2.6.35-25-generic 2.6.35-25.44 Linux kernel image for version 2.6.35 on x86/x86_64 ii linux-image-generic 2.6.35.25.32 Generic Linux kernel image ii vlan 1.9-3ubuntu3 user mode programs to enable VLANs on your ethernet devices I'm running under 2.6.35-25-generic right now, but I tried rebooting with 2.6.35-24-generic and it made no difference. Please let me know if you need more info or you'd like me to do some troubleshooting, I'd be glad to help track down the issue. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: vlan 1.9-3ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 Date: Fri Feb 11 11:01:23 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: vlan ** Affects: vlan (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug maverick -- vlan interface won't start with ifup, can be started manually https://bugs.edge.launchpad.net/bugs/717243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
