wicd 1.7.0a2 gets confused when there are both wired and wireless networks are available on startup

Bug #492833 reported by Piotr M on 2009-12-05
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wicd
Medium
Unassigned

Bug Description

I have a wireless network marked for connecting automatically, and in the preferences I have checked the option to switch to wired connection when available. When the computer is in range of the network and connected by the cable during boot-up, wicd first connects to the wireless network, then disconnects and only then connects using the wired connection. Instead it should first check if the wired is available and if it is, it shouldn't try connecting to the wireless.
(it actually does this, but it doesn't work, as it turns out after looking through the log)

The system is Gentoo Linux with kernel 2.6.32.

system log: http://pastebin.com/fcfc1a2

wicd log:

2009/12/05 13:49:22 :: ---------------------------
2009/12/05 13:49:22 :: wicd initializing...
2009/12/05 13:49:22 :: ---------------------------
2009/12/05 13:49:22 :: wicd is version 1.7.0a2 482
2009/12/05 13:49:22 :: setting backend to external
2009/12/05 13:49:22 :: trying to load backend external
2009/12/05 13:49:22 :: successfully loaded backend external
2009/12/05 13:49:22 :: trying to load backend external
2009/12/05 13:49:22 :: successfully loaded backend external
2009/12/05 13:49:22 :: Automatically detected wireless interface wlan0
2009/12/05 13:49:22 :: setting wireless interface wlan0
2009/12/05 13:49:22 :: automatically detected wired interface eth0
2009/12/05 13:49:22 :: setting wired interface eth0
2009/12/05 13:49:22 :: setting wpa driver wext
2009/12/05 13:49:22 :: setting use global dns to False
2009/12/05 13:49:22 :: setting global dns
2009/12/05 13:49:22 :: global dns servers are None None None
2009/12/05 13:49:22 :: domain is None
2009/12/05 13:49:22 :: search domain is None
2009/12/05 13:49:22 :: setting automatically reconnect when connection drops True
2009/12/05 13:49:22 :: Setting dhcp client to 0
2009/12/05 13:49:22 :: Wireless configuration file found...
2009/12/05 13:49:22 :: Wired configuration file found...
2009/12/05 13:49:22 :: chmoding configuration files 0600...
2009/12/05 13:49:22 :: chowning configuration files root:root...
2009/12/05 13:49:22 :: Using wireless interface...wlan0
2009/12/05 13:49:22 :: Using wired interface...eth0
2009/12/05 13:49:30 :: Autoconnecting...
2009/12/05 13:49:30 :: No wired connection present, attempting to autoconnect to wireless network
2009/12/05 13:49:31 :: trying to automatically connect to...nowy lepszy szatan
2009/12/05 13:49:31 :: Connecting to wireless network nowy lepszy szatan
2009/12/05 13:49:31 :: Putting interface down
2009/12/05 13:49:31 :: Releasing DHCP leases...
2009/12/05 13:49:31 :: Setting false IP...
2009/12/05 13:49:31 :: Stopping wpa_supplicant
2009/12/05 13:49:31 :: Flushing the routing table...
2009/12/05 13:49:31 :: Putting interface up...
2009/12/05 13:49:33 :: Generating psk...
2009/12/05 13:49:34 :: Attempting to authenticate...
2009/12/05 13:49:39 :: Running DHCP with hostname laptop
2009/12/05 13:49:39 :: dhcpcd: version 5.1.3 starting
2009/12/05 13:49:39 ::
2009/12/05 13:49:39 :: dhcpcd: wlan0: broadcasting for a lease
2009/12/05 13:49:39 ::
2009/12/05 13:49:39 :: dhcpcd: wlan0: offered 192.168.1.102 from 192.168.1.1
2009/12/05 13:49:39 ::
2009/12/05 13:49:39 :: dhcpcd: wlan0: acknowledged 192.168.1.102 from 192.168.1.1
2009/12/05 13:49:39 ::
2009/12/05 13:49:39 :: dhcpcd: wlan0: checking for 192.168.1.102
2009/12/05 13:49:39 ::
2009/12/05 13:49:44 :: dhcpcd: wlan0: leased 192.168.1.102 for 86400 seconds
2009/12/05 13:49:44 ::
2009/12/05 13:49:44 :: dhcpcd: forking to background
2009/12/05 13:49:44 ::
2009/12/05 13:49:44 ::
2009/12/05 13:49:44 :: DHCP connection successful
2009/12/05 13:49:44 :: not verifying
2009/12/05 13:49:44 :: Executing post-connection script
2009/12/05 13:49:44 :: Expanded 'ntpdate pool.ntp.org' to 'ntpdate pool.ntp.org'
2009/12/05 13:49:44 :: Connecting thread exiting.
2009/12/05 13:49:48 :: Sending connection attempt result Success
2009/12/05 13:49:48 :: Autoconnecting...
2009/12/05 13:49:48 :: Attempting to autoconnect with wired interface...
2009/12/05 13:49:48 :: Putting interface down
2009/12/05 13:49:48 :: Releasing DHCP leases...
2009/12/05 13:49:48 :: Setting false IP...
2009/12/05 13:49:48 :: Flushing the routing table...
2009/12/05 13:49:48 :: Putting interface up...
2009/12/05 13:49:50 :: Running DHCP with hostname laptop
2009/12/05 13:49:50 :: dhcpcd: version 5.1.3 starting
2009/12/05 13:49:50 ::
2009/12/05 13:49:50 :: dhcpcd: eth0: waiting for carrier
2009/12/05 13:49:50 ::
2009/12/05 13:49:52 :: dhcpcd: eth0: carrier acquired
2009/12/05 13:49:52 ::
2009/12/05 13:49:52 :: dhcpcd: eth0: rebinding lease of 192.168.1.105
2009/12/05 13:49:52 ::
2009/12/05 13:49:57 :: dhcpcd: eth0: acknowledged 192.168.1.105 from 192.168.1.1
2009/12/05 13:49:57 ::
2009/12/05 13:49:57 :: dhcpcd: eth0: checking for 192.168.1.105
2009/12/05 13:49:57 ::
2009/12/05 13:50:02 :: dhcpcd: eth0: leased 192.168.1.105 for 86400 seconds
2009/12/05 13:50:02 ::
2009/12/05 13:50:02 :: dhcpcd: forking to background
2009/12/05 13:50:02 ::
2009/12/05 13:50:02 ::
2009/12/05 13:50:02 :: DHCP connection successful
2009/12/05 13:50:02 :: Connecting thread exiting.
2009/12/05 13:50:05 :: Sending connection attempt result Success

Piotr M (yabolus) on 2009-12-05
description: updated
David Paleino (dpaleino) on 2011-09-18
Changed in wicd:
status: New → Triaged
importance: Undecided → Medium
Lithopsian (x-uzuntu-c) wrote :

Wired networks cannot always be detected instantly when Wicd starts, and this can mean passing them by to a wireless network. A few seconds later the wired network shows as available and gets connected. See 533045 for more details.

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

Other bug subscribers