wicd can not get ip address for wired connections

Bug #728749 reported by LeeG
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
New
Undecided
Unassigned

Bug Description

With Xubuntu 10.10 for my wired connection (wireless connects OK) wicd attempt to connect stalls when it tries to get an ip address. Older versions of wicd work, network-manager works, XP works, but the repository version (1.7.0+ds1-5) for Xubuntu 10.10 does not work. I cite log below, thanks:

2011/03/03 15:32:45 :: ---------------------------
2011/03/03 15:32:45 :: wicd initializing...
2011/03/03 15:32:45 :: ---------------------------
2011/03/03 15:32:45 :: wicd is version 1.7.0 552
2011/03/03 15:32:45 :: setting backend to external
2011/03/03 15:32:45 :: trying to load backend external
2011/03/03 15:32:45 :: successfully loaded backend external
2011/03/03 15:32:45 :: trying to load backend external
2011/03/03 15:32:45 :: successfully loaded backend external
2011/03/03 15:32:45 :: Automatically detected wireless interface wlan0
2011/03/03 15:32:45 :: setting wireless interface wlan0
2011/03/03 15:32:45 :: automatically detected wired interface eth0
2011/03/03 15:32:45 :: setting wired interface eth0
2011/03/03 15:32:45 :: setting wpa driver wext
2011/03/03 15:32:45 :: setting use global dns to False
2011/03/03 15:32:45 :: setting global dns
2011/03/03 15:32:45 :: global dns servers are None None None
2011/03/03 15:32:45 :: domain is None
2011/03/03 15:32:45 :: search domain is None
2011/03/03 15:32:45 :: setting automatically reconnect when connection drops True
2011/03/03 15:32:45 :: Setting dhcp client to 0
2011/03/03 15:32:45 :: Wireless configuration file found...
2011/03/03 15:32:45 :: Wired configuration file found...
2011/03/03 15:32:45 :: chmoding configuration files 0600...
2011/03/03 15:32:45 :: chowning configuration files root:root...
2011/03/03 15:32:45 :: Using wireless interface...wlan0
2011/03/03 15:32:45 :: Using wired interface...eth0
2011/03/03 15:32:52 :: attempting to set hostname with dhclient
2011/03/03 15:32:52 :: using dhcpcd or another supported client may work better
2011/03/03 15:32:52 :: attempting to set hostname with dhclient
2011/03/03 15:32:52 :: using dhcpcd or another supported client may work better
2011/03/03 15:32:53 :: Putting interface down
2011/03/03 15:32:53 :: Releasing DHCP leases...
2011/03/03 15:32:53 :: attempting to set hostname with dhclient
2011/03/03 15:32:53 :: using dhcpcd or another supported client may work better
2011/03/03 15:32:54 :: Setting false IP...
2011/03/03 15:32:54 :: Flushing the routing table...
2011/03/03 15:32:54 :: Putting interface up...
2011/03/03 15:32:56 :: Running DHCP with hostname giga1
2011/03/03 15:32:56 :: attempting to set hostname with dhclient
2011/03/03 15:32:56 :: using dhcpcd or another supported client may work better
2011/03/03 15:32:56 :: Internet Systems Consortium DHCP Client V3.1.3
2011/03/03 15:32:56 :: Copyright 2004-2009 Internet Systems Consortium.
2011/03/03 15:32:56 :: All rights reserved.
2011/03/03 15:32:56 :: For info, please visit https://www.isc.org/software/dhcp/
2011/03/03 15:32:56 ::
2011/03/03 15:32:56 :: Listening on LPF/eth0/00:1e:ec:19:d0:84
2011/03/03 15:32:56 :: Sending on LPF/eth0/00:1e:ec:19:d0:84
2011/03/03 15:32:56 :: Sending on Socket/fallback
2011/03/03 15:32:56 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
2011/03/03 15:32:59 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
2011/03/03 15:33:06 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
2011/03/03 15:33:17 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
2011/03/03 15:33:36 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
2011/03/03 15:33:47 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
2011/03/03 15:33:55 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2
2011/03/03 15:33:57 :: No DHCPOFFERS received.
2011/03/03 15:33:57 :: No working leases in persistent database - sleeping.
2011/03/03 15:34:06 :: DHCP connection failed
2011/03/03 15:34:06 :: exiting connection thread
2011/03/03 15:34:06 :: Sending connection attempt result dhcp_failed
2011/03/03 15:34:06 :: attempting to set hostname with dhclient
2011/03/03 15:34:06 :: using dhcpcd or another supported client may work better
2011/03/03 15:34:07 :: attempting to set hostname with dhclient
2011/03/03 15:34:07 :: using dhcpcd or another supported client may work better
2011/03/03 15:34:20 :: Autoconnecting...
2011/03/03 15:34:20 :: No wired connection present, attempting to autoconnect to wireless network
2011/03/03 15:34:21 :: Unable to autoconnect, you'll have to manually connect
2011/03/03 15:34:25 :: Autoconnecting...
2011/03/03 15:34:25 :: No wired connection present, attempting to autoconnect to wireless network
2011/03/03 15:34:26 :: Unable to autoconnect, you'll have to manually connect
2011/03/03 15:34:30 :: Autoconnecting...
2011/03/03 15:34:30 :: No wired connection present, attempting to autoconnect to wireless network
2011/03/03 15:34:31 :: Unable to autoconnect, you'll have to manually connect
2011/03/03 15:34:35 :: Autoconnecting...
2011/03/03 15:34:35 :: No wired connection present, attempting to autoconnect to wireless network
2011/03/03 15:34:36 :: Unable to autoconnect, you'll have to manually connect

-- end --

Revision history for this message
Joseph J. Gunn (armadefuego) wrote :

Please provide information on the hardware you are using.

And a copy of your system log.

Thanks
Joe

Revision history for this message
LeeG (leegold) wrote : Re: [Bug 728749] Re: wicd can not get ip address for wired connections
Download full text (32.7 KiB)

Hi,

I tried to get syslog for the time period in question, please let me know if it's what's needed (I have hardware info below the syslog), let me know if you need more:

Mar 3 15:32:45 giga1 dhclient: isc-dhclient-V3.1.3
Mar 3 15:32:45 giga1 dhclient: isc-dhclient-V3.1.3
Mar 3 15:32:52 giga1 dhclient: There is already a pid file /var/run/dhclient.pid with pid 3922
Mar 3 15:32:52 giga1 dhclient: killed old client process, removed PID file
Mar 3 15:32:52 giga1 dhclient: Internet Systems Consortium DHCP Client V3.1.3
Mar 3 15:32:52 giga1 dhclient: Copyright 2004-2009 Internet Systems Consortium.
Mar 3 15:32:52 giga1 dhclient: All rights reserved.
Mar 3 15:32:52 giga1 dhclient: For info, please visit https://www.isc.org/software/dhcp/
Mar 3 15:32:52 giga1 dhclient:
Mar 3 15:32:52 giga1 dhclient: Listening on LPF/wlan0/00:xx:xx:xx:11:3b
Mar 3 15:32:52 giga1 dhclient: Sending on LPF/wlan0/00:xx:xx:xx:11:3b
Mar 3 15:32:52 giga1 dhclient: Sending on Socket/fallback
Mar 3 15:32:52 giga1 dhclient: DHCPRELEASE on wlan0 to 10.0.0.1 port 67
Mar 3 15:32:52 giga1 avahi-daemon[1064]: Withdrawing address record for 10.0.0.3 on wlan0.
Mar 3 15:32:52 giga1 avahi-daemon[1064]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.0.0.3.
Mar 3 15:32:52 giga1 avahi-daemon[1064]: Interface wlan0.IPv4 no longer relevant for mDNS.
Mar 3 15:32:52 giga1 kernel: [17092.191175] iwlagn 0000:10:00.0: ACTIVATE a non DRIVER active station id 0 addr 00:xx:xx:xx:34:90
Mar 3 15:32:52 giga1 kernel: [17092.204169] wlan0: deauthenticating from 00:xx:xx:xx:34:90 by local choice (reason=3)
Mar 3 15:32:52 giga1 avahi-daemon[1064]: Interface wlan0.IPv6 no longer relevant for mDNS.
Mar 3 15:32:52 giga1 avahi-daemon[1064]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80:xxx:xxxx:xxxx113b.
Mar 3 15:32:52 giga1 avahi-daemon[1064]: Withdrawing address record for fe80:xxx:xxxx:xxxx113b on wlan0.
Mar 3 15:32:52 giga1 kernel: [17092.252549] cfg80211: All devices are disconnected, going to restore regulatory settings
Mar 3 15:32:52 giga1 kernel: [17092.252560] cfg80211: Restoring regulatory settings
Mar 3 15:32:52 giga1 kernel: [17092.252568] cfg80211: Calling CRDA to update world regulatory domain
Mar 3 15:32:52 giga1 kernel: [17092.262293] cfg80211: World regulatory domain updated:
Mar 3 15:32:52 giga1 kernel: [17092.262301] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Mar 3 15:32:52 giga1 kernel: [17092.262309] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mar 3 15:32:52 giga1 kernel: [17092.262317] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mar 3 15:32:52 giga1 kernel: [17092.262325] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Mar 3 15:32:52 giga1 kernel: [17092.262332] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mar 3 15:32:52 giga1 kernel: [17092.262340] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Mar 3 15:32:52 giga1 kernel: [17092.501599] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Mar 3 15:32:52 giga1 dhclient: Internet Systems Consortium DHCP Client V3.1.3
Mar 3 15:32:52 gig...

Revision history for this message
LeeG (leegold) wrote :
Download full text (41.1 KiB)

I installed older wicd 1.60 from Karmic packages onto my Xubuntu 10.10 and bug or problem is non-existent - rock solid - works great. As I previously said, older versions of wicd do not have to bug or problem...

> ----- Original Message -----
> From: LeeG <email address hidden>
> To: <email address hidden>
> Subject: Re: [Bug 728749] Re: wicd can not get ip address for wired connections
> Date: Fri, 04 Mar 2011 05:01:06 -0000
>
>
> Hi,
>
> I tried to get syslog for the time period in question, please let me
> know if it's what's needed (I have hardware info below the syslog), let
> me know if you need more:
>
>
> Mar 3 15:32:45 giga1 dhclient: isc-dhclient-V3.1.3
> Mar 3 15:32:45 giga1 dhclient: isc-dhclient-V3.1.3
> Mar 3 15:32:52 giga1 dhclient: There is already a pid file
> /var/run/dhclient.pid with pid 3922
> Mar 3 15:32:52 giga1 dhclient: killed old client process, removed PID file
> Mar 3 15:32:52 giga1 dhclient: Internet Systems Consortium DHCP Client V3.1.3
> Mar 3 15:32:52 giga1 dhclient: Copyright 2004-2009 Internet
> Systems Consortium.
> Mar 3 15:32:52 giga1 dhclient: All rights reserved.
> Mar 3 15:32:52 giga1 dhclient: For info, please visit
> https://www.isc.org/software/dhcp/
> Mar 3 15:32:52 giga1 dhclient:
> Mar 3 15:32:52 giga1 dhclient: Listening on LPF/wlan0/00:xx:xx:xx:11:3b
> Mar 3 15:32:52 giga1 dhclient: Sending on LPF/wlan0/00:xx:xx:xx:11:3b
> Mar 3 15:32:52 giga1 dhclient: Sending on Socket/fallback
> Mar 3 15:32:52 giga1 dhclient: DHCPRELEASE on wlan0 to 10.0.0.1 port 67
> Mar 3 15:32:52 giga1 avahi-daemon[1064]: Withdrawing address
> record for 10.0.0.3 on wlan0.
> Mar 3 15:32:52 giga1 avahi-daemon[1064]: Leaving mDNS multicast
> group on interface wlan0.IPv4 with address 10.0.0.3.
> Mar 3 15:32:52 giga1 avahi-daemon[1064]: Interface wlan0.IPv4 no
> longer relevant for mDNS.
> Mar 3 15:32:52 giga1 kernel: [17092.191175] iwlagn 0000:10:00.0:
> ACTIVATE a non DRIVER active station id 0 addr 00:xx:xx:xx:34:90
> Mar 3 15:32:52 giga1 kernel: [17092.204169] wlan0:
> deauthenticating from 00:xx:xx:xx:34:90 by local choice (reason=3)
> Mar 3 15:32:52 giga1 avahi-daemon[1064]: Interface wlan0.IPv6 no
> longer relevant for mDNS.
> Mar 3 15:32:52 giga1 avahi-daemon[1064]: Leaving mDNS multicast
> group on interface wlan0.IPv6 with address fe80:xxx:xxxx:xxxx113b.
> Mar 3 15:32:52 giga1 avahi-daemon[1064]: Withdrawing address
> record for fe80:xxx:xxxx:xxxx113b on wlan0.
> Mar 3 15:32:52 giga1 kernel: [17092.252549] cfg80211: All devices
> are disconnected, going to restore regulatory settings
> Mar 3 15:32:52 giga1 kernel: [17092.252560] cfg80211: Restoring
> regulatory settings
> Mar 3 15:32:52 giga1 kernel: [17092.252568] cfg80211: Calling CRDA
> to update world regulatory domain
> Mar 3 15:32:52 giga1 kernel: [17092.262293] cfg80211: World
> regulatory domain updated:
> Mar 3 15:32:52 giga1 kernel: [17092.262301] (start_freq -
> end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Mar 3 15:32:52 giga1 kernel: [17092.262309] (2402000 KHz -
> 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> Mar 3 15:32:52 giga1 kernel: [17092.262317] (2457000 KHz -
> ...

Revision history for this message
Harald Barth (haba+launchpad) wrote :

This might be the same bug as I encountered on Ubuntu 10.04 LTS. The prblem seems to be that right after the authenticate step the associate step somehow destroys the connection again which makes the dhcp step fail.
The following patch which comments out the associate step makes wicd work. I do not understand why this step is neccessary at all, at least not for all types of wireless connections.

------------------

--- networking.py.orig 2010-01-15 05:49:11.000000000 +0100
+++ networking.py 2011-03-14 23:09:01.063528703 +0100
@@ -866,8 +866,8 @@
             self.generate_psk_and_authenticate(wiface)

         # Associate.
- wiface.Associate(self.network['essid'], self.network['channel'],
- self.network['bssid'])
+# wiface.Associate(self.network['essid'], self.network['channel'],
+# self.network['bssid'])

         # Authenticate after association for Ralink legacy cards.
         if self.wpa_driver == 'ralink legacy':

------------------

This is my kernel log without the patch and after that dhcp fails:

Mar 14 22:02:36 habanero kernel: [14077.209605] wlan0: direct probe to AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.211864] wlan0: direct probe responded
Mar 14 22:02:36 habanero kernel: [14077.211873] wlan0: authenticate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.214671] wlan0: authenticated
Mar 14 22:02:36 habanero kernel: [14077.214709] wlan0: associate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.217792] wlan0: RX AssocResp from 00:15:f2:6a:d6:bb (capab=0x411 status=0 aid=2)
Mar 14 22:02:36 habanero kernel: [14077.217800] wlan0: associated
Mar 14 22:02:36 habanero kernel: [14077.272656] wlan0: deauthenticating from 00:15:f2:6a:d6:bb by local choice (reason=3)
Mar 14 22:02:36 habanero kernel: [14077.279944] wlan0: direct probe to AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.282191] wlan0: direct probe responded
Mar 14 22:02:36 habanero kernel: [14077.282199] wlan0: authenticate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.284156] wlan0: authenticated
Mar 14 22:02:36 habanero kernel: [14077.300771] wlan0: associate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 14 22:02:36 habanero kernel: [14077.302953] wlan0: RX AssocResp from 00:15:f2:6a:d6:bb (capab=0x411 status=0 aid=2)
Mar 14 22:02:36 habanero kernel: [14077.302960] wlan0: associated

This is my kernel log with the patch and after that DHCP works:

Mar 15 10:00:27 habanero kernel: [21361.792281] wlan0: authenticate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 15 10:00:27 habanero kernel: [21361.794210] wlan0: authenticated
Mar 15 10:00:27 habanero kernel: [21361.794250] wlan0: associate with AP 00:15:f2:6a:d6:bb (try 1)
Mar 15 10:00:27 habanero kernel: [21361.797709] wlan0: RX AssocResp from 00:15:f2:6a:d6:bb (capab=0x411 status=0 aid=2)
Mar 15 10:00:27 habanero kernel: [21361.797717] wlan0: associated
Mar 15 10:00:27 habanero kernel: [21361.816592] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Hope this helps you, I needed serveral hours to find this.
Harald.

Revision history for this message
Harald Barth (haba+launchpad) wrote :

Well, as I had problems with wireless and the original post is about wired, so I don't know if that was relevant at all for _this_ bug, however noone seems to care anyway.

Harald.

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

Other bug subscribers

Remote bug watches

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