[Bug 717243] Re: vlan interface won't start with ifup, can be started manually
I have lost access to the hardware that this problem was happening on (I no longer work at the company that owns the hardware), so I will not be able to troubleshoot this further. You may want to close this bug as not reproducible. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in Ubuntu. https://bugs.launchpad.net/bugs/717243 Title: vlan interface won't start with ifup, can be started manually -- 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
[Bug 717243] Re: vlan interface won't start with ifup, can be started manually
I have lost access to the hardware that this problem was happening on (I no longer work at the company that owns the hardware), so I will not be able to troubleshoot this further. You may want to close this bug as not reproducible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717243 Title: vlan interface won't start with ifup, can be started manually -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717243] Re: vlan interface won't start with ifup, can be started manually
When I try your suggestion, I get: $ sudo ifdown eth0.20 [sudo] password for alexeyt: RTNETLINK answers: No such process Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0.20/00:1e:4f:b3:18:db Sending on LPF/eth0.20/00:1e:4f:b3:18:db Sending on Socket/fallback DHCPRELEASE on eth0.20 to 10.10.20.1 port 67 send_packet: Network is unreachable send_packet: please consult README file regarding broadcast address. SIOCSIFFLAGS: Network is down Removed VLAN -:eth0.20:- $ sudo ifup eth0.20 Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Added VLAN with VID == 20 to IF -:eth0:- Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ SIOCSIFFLAGS: Network is down SIOCSIFFLAGS: Network is down Listening on LPF/eth0.20/00:1e:4f:b3:18:db Sending on LPF/eth0.20/00:1e:4f:b3:18:db Sending on Socket/fallback DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 3 send_packet: Network is down receive_packet failed on eth0.20: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 8 send_packet: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 12 send_packet: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 13 send_packet: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 8 send_packet: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 17 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. RTNETLINK answers: Network is down run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2 ssh stop/waiting ssh start/running, process 2076 I have 2 more data points: First, since I haven't removed any old kernels since the problem began; I wanted to make sure that it's not a kernel issue, so I rebooted with each of: linux-image-2.6.35-23-generic linux-image-2.6.35-24-generic linux-image-2.6.35-25-generic linux-image-2.6.35-27-generic linux-image-2.6.35-28-generic and I see the same symptoms under all of them. Second, on one of the ~20 reboots since the problem started, the interface came up OK and did not need to be started manually, so it seems that the problem is intermittent. Please let me know if I can do any more troubleshooting. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in ubuntu. https://bugs.launchpad.net/bugs/717243 Title: vlan interface won't start with ifup, can be started manually -- 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
[Bug 717243] Re: vlan interface won't start with ifup, can be started manually
When I try your suggestion, I get: $ sudo ifdown eth0.20 [sudo] password for alexeyt: RTNETLINK answers: No such process Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0.20/00:1e:4f:b3:18:db Sending on LPF/eth0.20/00:1e:4f:b3:18:db Sending on Socket/fallback DHCPRELEASE on eth0.20 to 10.10.20.1 port 67 send_packet: Network is unreachable send_packet: please consult README file regarding broadcast address. SIOCSIFFLAGS: Network is down Removed VLAN -:eth0.20:- $ sudo ifup eth0.20 Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Added VLAN with VID == 20 to IF -:eth0:- Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ SIOCSIFFLAGS: Network is down SIOCSIFFLAGS: Network is down Listening on LPF/eth0.20/00:1e:4f:b3:18:db Sending on LPF/eth0.20/00:1e:4f:b3:18:db Sending on Socket/fallback DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 3 send_packet: Network is down receive_packet failed on eth0.20: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 8 send_packet: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 12 send_packet: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 13 send_packet: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 8 send_packet: Network is down DHCPDISCOVER on eth0.20 to 255.255.255.255 port 67 interval 17 send_packet: Network is down No DHCPOFFERS received. No working leases in persistent database - sleeping. RTNETLINK answers: Network is down run-parts: /etc/network/if-up.d/avahi-autoipd exited with return code 2 ssh stop/waiting ssh start/running, process 2076 I have 2 more data points: First, since I haven't removed any old kernels since the problem began; I wanted to make sure that it's not a kernel issue, so I rebooted with each of: linux-image-2.6.35-23-generic linux-image-2.6.35-24-generic linux-image-2.6.35-25-generic linux-image-2.6.35-27-generic linux-image-2.6.35-28-generic and I see the same symptoms under all of them. Second, on one of the ~20 reboots since the problem started, the interface came up OK and did not need to be started manually, so it seems that the problem is intermittent. Please let me know if I can do any more troubleshooting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717243 Title: vlan interface won't start with ifup, can be started manually -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717243] Re: vlan interface won't start with ifup, can be started manually
I'm sorry, but why did you change the bug from affecting vlan to affecting network-manager? The interface that the problem is on is not under network-manager control, it is configured via /etc/network/interfaces, using the extensions provided by the vlan package in /etc/network/if-pre-up.d/vlan and /etc/network/if-post- down.d/vlan... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717243 Title: vlan interface won't start with ifup, can be started manually -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 717243] [NEW] vlan interface won't start with ifup, can be started manually
Public bug reported: 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-generic2.6.35-22.35 Linux kernel image for version 2.6.35 on x86/x86_64 ii linux-image-2.6.35-23-generic2.6.35-23.41 Linux kernel image for version 2.6.35 on x86/x86_64 ii linux-image-2.6.35-24-generic2.6.35-24.42 Linux kernel image for version 2.6.35 on x86/x86_64 ii
[Bug 717243] Re: vlan interface won't start with ifup, can be started manually
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in ubuntu. https://bugs.launchpad.net/bugs/717243 Title: vlan interface won't start with ifup, can be started manually -- 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
[Bug 717243] [NEW] vlan interface won't start with ifup, can be started manually
Public bug reported: 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-generic2.6.35-22.35 Linux kernel image for version 2.6.35 on x86/x86_64 ii linux-image-2.6.35-23-generic2.6.35-23.41 Linux kernel image for version 2.6.35 on x86/x86_64 ii linux-image-2.6.35-24-generic2.6.35-24.42 Linux kernel image for version 2.6.35 on x86/x86_64 ii
[Bug 717243] Re: vlan interface won't start with ifup, can be started manually
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/717243 Title: vlan interface won't start with ifup, can be started manually -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
