Ubuntu
network-manager package

both wireless and wired connections are up after boot

Bug #94760 reported by Charles Perreault
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: network-manager

I use feisty fawn, latest updates. My wireless card use the bcm43xx driver, and my wired card 8139too (realtek).

When I'm at work and use ethernet, after booting in my gnome session, both the wired and the wireless connections are up and configured using dhcp. The wireless network automatically chosen is unencrypted. Now that's a problem since the wireless network then requires an http login in order to work, and then nothing work since the routes are badly configured. I think the normal behaviour would be to deactivate the wireless card when a wired connection is available. If I manually choose the wireless network using nm-applet, and then switch back to the wired network, the wireless interface is deactivated as it should in the first place. The problem is only at boot time.

The correct behaviour was present in dapper, although I was using ndiswrapper.

Here I paste the booting part of daemon.log. eth0 is the wired interface, eth1 the wireless. 132.210.48.0/24 is the wired network, and 132.210.56/23 is the wireless one.

Mar 22 09:07:43 port-perreaul dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
Mar 22 09:07:45 port-perreaul NetworkManager: <information>^Istarting...
Mar 22 09:07:45 port-perreaul NetworkManager: <information>^Ieth1: Device is fully-supported using driver 'bcm43xx'.
Mar 22 09:07:45 port-perreaul NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Mar 22 09:07:45 port-perreaul NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Mar 22 09:07:45 port-perreaul NetworkManager: <information>^INow managing wireless (802.11) device 'eth1'.
Mar 22 09:07:45 port-perreaul NetworkManager: <information>^IDeactivating device eth1.
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: Found user 'avahi' (UID 105) and group 'avahi' (GID 109).
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: Successfully dropped root privileges.
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: avahi-daemon 0.6.17 starting up.
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: Successfully called chroot().
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: Successfully dropped remaining capabilities.
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: No service found in /etc/avahi/services.
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: Network interface enumeration completed.
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: Registering HINFO record with values 'I686'/'LINUX'.
Mar 22 09:07:45 port-perreaul avahi-daemon[4708]: Server startup complete. Host name is port-perreaul.local. Local service cookie is 1512549232.
Mar 22 09:07:45 port-perreaul NetworkManager: <information>^Ieth0: Device is fully-supported using driver '8139too'.
Mar 22 09:07:45 port-perreaul NetworkManager: <information>^Inm_device_init(): waiting for device's worker thread to start
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^Inm_device_init(): device's worker thread started, continuing.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^INow managing wired Ethernet (802.3) device 'eth0'.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IDeactivating device eth0.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IWill activate wired connection 'eth0' because it now has a link.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^ISWITCH: no current connection, found better connection 'eth0'.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IWill activate connection 'eth0'.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IDevice eth0 activation scheduled...
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) started...
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) started...
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 1 of 5 (Device Prepare) complete.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) starting...
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) successful.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 2 of 5 (Device Configure) complete.
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) started...
Mar 22 09:07:46 port-perreaul NetworkManager: <information>^IOld device 'eth0' activating, won't change.
Mar 22 09:07:47 port-perreaul dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
Mar 22 09:07:47 port-perreaul NetworkManager: <information>^IActivation (eth0) Beginning DHCP transaction.
Mar 22 09:07:47 port-perreaul NetworkManager: <information>^IDHCP daemon state is now 12 (successfully started) for interface eth0
Mar 22 09:07:47 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Mar 22 09:07:48 port-perreaul NetworkManager: <information>^IDHCP daemon state is now 1 (starting) for interface eth0
Mar 22 09:07:52 port-perreaul dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Mar 22 09:07:52 port-perreaul dhclient: DHCPOFFER from 132.210.48.210
Mar 22 09:07:52 port-perreaul dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Mar 22 09:07:52 port-perreaul dhclient: DHCPACK from 132.210.48.210
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Joining mDNS multicast group on interface eth0.IPv4 with address 132.210.48.198.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: New relevant interface eth0.IPv4 for mDNS.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Registering new address record for 132.210.48.198 on eth0.IPv4.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Withdrawing address record for 132.210.48.198 on eth0.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Leaving mDNS multicast group on interface eth0.IPv4 with address 132.210.48.198.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Interface eth0.IPv4 no longer relevant for mDNS.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Joining mDNS multicast group on interface eth0.IPv4 with address 132.210.48.198.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: New relevant interface eth0.IPv4 for mDNS.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Registering new address record for 132.210.48.198 on eth0.IPv4.
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^IDHCP daemon state is now 2 (bound) for interface eth0
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) started...
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^IRetrieved the following IP4 configuration from the DHCP daemon:
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^I address 132.210.48.198
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^I netmask 255.255.255.0
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^I broadcast 132.210.48.255
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^I gateway 132.210.48.250
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^I nameserver 132.210.40.13
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^I nameserver 132.210.40.10
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^I hostname 'port-perreaul'
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^I domain name 'dmi.usherb.ca'
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Mar 22 09:07:52 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Withdrawing address record for 132.210.48.198 on eth0.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Leaving mDNS multicast group on interface eth0.IPv4 with address 132.210.48.198.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Interface eth0.IPv4 no longer relevant for mDNS.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Joining mDNS multicast group on interface eth0.IPv4 with address 132.210.48.198.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: New relevant interface eth0.IPv4 for mDNS.
Mar 22 09:07:52 port-perreaul avahi-daemon[4708]: Registering new address record for 132.210.48.198 on eth0.IPv4.
Mar 22 09:07:52 port-perreaul dhclient: bound to 132.210.48.198 -- renewal in 972914775 seconds.
Mar 22 09:07:53 port-perreaul dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
Mar 22 09:07:53 port-perreaul hcid[5039]: Bluetooth HCI daemon
Mar 22 09:07:53 port-perreaul NetworkManager: <debug info>^I[1174568873.475739] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/platform_bluetooth').
Mar 22 09:07:53 port-perreaul hcid[5039]: Starting SDP server
Mar 22 09:07:53 port-perreaul NetworkManager: <information>^IClearing nscd hosts cache.
Mar 22 09:07:53 port-perreaul NetworkManager: <WARNING>^I nm_spawn_process (): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
Mar 22 09:07:53 port-perreaul NetworkManager: <information>^IActivation (eth0) successful, device activated.
Mar 22 09:07:53 port-perreaul NetworkManager: <information>^IActivation (eth0) Finish handler scheduled.
Mar 22 09:07:53 port-perreaul NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Mar 22 09:07:54 port-perreaul dhclient: DHCPOFFER from 132.210.57.250
Mar 22 09:07:54 port-perreaul dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
Mar 22 09:07:54 port-perreaul dhclient: DHCPACK from 132.210.57.250
Mar 22 09:07:54 port-perreaul dhclient: bound to 132.210.56.72 -- renewal in 131 seconds.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Joining mDNS multicast group on interface eth1.IPv4 with address 132.210.56.72.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: New relevant interface eth1.IPv4 for mDNS.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Registering new address record for 132.210.56.72 on eth1.IPv4.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Withdrawing address record for 132.210.56.72 on eth1.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Leaving mDNS multicast group on interface eth1.IPv4 with address 132.210.56.72.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Interface eth1.IPv4 no longer relevant for mDNS.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Joining mDNS multicast group on interface eth1.IPv4 with address 132.210.56.72.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: New relevant interface eth1.IPv4 for mDNS.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Registering new address record for 132.210.56.72 on eth1.IPv4.
Mar 22 09:07:53 port-perreaul ntpdate[5157]: step time server 82.211.81.145 offset -0.609967 sec
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Registering new address record for fe80::2c0:9fff:feb2:f58d on eth0.*.
Mar 22 09:07:54 port-perreaul avahi-daemon[4708]: Registering new address record for fe80::290:4bff:fef7:ff91 on eth1.*.
Mar 22 09:08:04 port-perreaul avahi-daemon[4708]: Joining mDNS multicast group on interface vmnet8.IPv4 with address 192.168.100.1.
Mar 22 09:08:04 port-perreaul avahi-daemon[4708]: New relevant interface vmnet8.IPv4 for mDNS.
Mar 22 09:08:04 port-perreaul avahi-daemon[4708]: Registering new address record for 192.168.100.1 on vmnet8.IPv4.
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: Internet Software Consortium DHCP Server 2.0
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: All rights reserved.
Mar 22 09:08:04 port-perreaul vmnet-dhcpd:
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: Please contribute if you find this software useful.
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: For info, please visit http://www.isc.org/dhcp-contrib.html
Mar 22 09:08:04 port-perreaul vmnet-dhcpd:
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: Configured subnet: 192.168.100.0
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: Setting vmnet-dhcp IP address: 192.168.100.254
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: Recving on VNet/vmnet8/192.168.100.0
Mar 22 09:08:04 port-perreaul vmnet-dhcpd: Sending on VNet/vmnet8/192.168.100.0
Mar 22 09:08:05 port-perreaul avahi-daemon[4708]: Registering new address record for fe80::250:56ff:fec0:8 on vmnet8.*.
Mar 22 09:08:18 port-perreaul NetworkManager: <information>^IUpdating allowed wireless network lists.
Mar 22 09:08:40 port-perreaul ntpdate[5384]: no server suitable for synchronization found

Revision history for this message
Thomas Novin (thomasn80) wrote :

I disagree. If you have both interfaces enabled, both should be active after a reboot. It is not up to the OS to decide which connection you want to use. You can however set the metric of your interfaces to decide which one should be your first choice.

This bug should be close AFAIK.

Revision history for this message
Charles Perreault (muganor) wrote : Re: [Bug 94760] Re: both wireless and wired connections are up after boot

I also disagree because having both interfaces enabled is the opposite
of the network manager primary goal, which was to manage wired /
wireless connections for mobile desktop users (laptop) and assure
everything would work plug'n'play. It's the opposite of
"configurations", "metric" and whatsoever human manipulation. Of course
it's not the choice of the OS to decide which connection you want to
use, but network-manager isn't part of the OS. Many in the OS Science
community argue wheter file systems should be part of the OS or not
(think of micro-kernels), so network-manager is still far from there.
It's a utility package one can use or not, install or disinstall.

However there was a set of rules (it's not available on the web page
anymore, but it was when the project started to explain how to users how
network-manager would work) :

1- By default, wired will always be prefered over wireless
2- If no wire is present, choose wireless, and vice-versa
3- If both are available and a wireless network was EXPLICITELY chosen
last time both were present, choose that wireless network (kind of
"remember my preference" rule) else choose wired mode (default)

The rules enumerated back then only stated 1 of the devices would be
active at a time, depending on the situation. It would avoid having to
manipulate the route table, or manually disable the wrong interface.
I'm sure of it, that's why I was compiling/using network-manager since
it's start, before I switch to Ubuntu(breezy) and before it was included
in the default Ubuntu setup. If 2 or more devices should be configured
(bridge, gateway, etc), then it's probably not a mobile/laptop user and
it should be done outside of network-manager (by disabling the roaming
mode in the network configuration for instance). Anyway such user would
have plenty of network configuration knowledge to not need network-manager.

This bug will be close because the behaviour stated originally seemed to
have disappared with the recent updates to the kernel and probably of
the bcm43xx driver, but not because this wasn't a bug in the first place.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi, could you please test this in Gutsy (perhaps with a Live CD)? We'll only be able to address most network-manager bugs in the latest release. FWIW, I don't see this problem on my gutsy system.

Thanks.

Changed in network-manager:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Charles Perreault (muganor) wrote :

I'll try it whenever I get a chance, the environment where I found the
bug uses Wireless Distribution on multiple access points and I must go
back there to see if the bug is solved or not. Will take a few days.

Henrik Nilsen Omma wrote:
> Hi, could you please test this in Gutsy (perhaps with a Live CD)? We'll
> only be able to address most network-manager bugs in the latest release.
> FWIW, I don't see this problem on my gutsy system.
>
> Thanks.
>
> ** Changed in: network-manager (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Incomplete
>
>

Revision history for this message
Alexander Sack (asac) wrote :

this should be fixed since network-manager 0.6.5-0ubuntu12 which stopped to manage interfaces managed by ifupdown.

Changed in network-manager:
status: Incomplete → Fix Released
Revision history for this message
Charles Perreault (muganor) wrote :

Even if the interfaces are in roaming mode in gnome-network-manager ?

Alexander Sack wrote:
> this should be fixed since network-manager 0.6.5-0ubuntu12 which stopped
> to manage interfaces managed by ifupdown.
>
>
> ** Changed in: network-manager (Ubuntu)
> Status: Incomplete => Fix Released
>
>

Revision history for this message
Charles Perreault (muganor) wrote :

I cannot test the new network-manager with a Live CD : it doesn't boot
on my laptop. I used Ubuntu Gutsy Tribe 5 Live CD. GDM comes up, I can
see the background with the mouse cursor then all freeze. No tty, no
ctrl+alt+backspace to reset X, even the power button (acpi shutdown)
don't work. The CD was tested and is correct. I tried booting 3 times
and gutsy freezed everytime when loading GDM. I don't have time to find
out what goes wrong, anyway it's a tribe cd. I'll try again with
another Live CD from the official release.

Alexander Sack wrote:
> this should be fixed since network-manager 0.6.5-0ubuntu12 which stopped
> to manage interfaces managed by ifupdown.
>
>
> ** Changed in: network-manager (Ubuntu)
> Status: Incomplete => Fix Released
>
>

Revision history for this message
Alexander Sack (asac) wrote : Re: [Bug 94760] Re: both wireless and wired connections are up after boot

On Wed, Oct 03, 2007 at 02:53:03PM -0000, Charles Perreault wrote:
> I cannot test the new network-manager with a Live CD : it doesn't boot
> on my laptop. I used Ubuntu Gutsy Tribe 5 Live CD. GDM comes up, I can
> see the background with the mouse cursor then all freeze. No tty, no
> ctrl+alt+backspace to reset X, even the power button (acpi shutdown)
> don't work. The CD was tested and is correct. I tried booting 3 times
> and gutsy freezed everytime when loading GDM. I don't have time to find
> out what goes wrong, anyway it's a tribe cd. I'll try again with
> another Live CD from the official release.

Please try latest again.

 - Alexander

Revision history for this message
Charles Perreault (muganor) wrote :

I installed gutsy on my laptop and the bug seems to be solved. I'll open a new bug if it ever reappears.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.