Wicd: "Connection failed: Unable to get IP Address"

w1ntermute · 2010-09-14 04:45:26

Hi,

Wicd has suddenly stopped working for me. The only recent change I can think of is updating virtualbox_bin (from AUR). I can successfully connect to my wireless network from an Ubuntu 10.04 machine, so the problem is on my Arch laptop. Here's my /var/log/everything.log from a fresh boot immediately followed by an attempt to connect to my wireless network:

Sep 13 23:35:18 archtop polkitd[2252]: started daemon version 0.96 using authority implementation `local' version `0.96'
Sep 13 23:35:18 archtop pulseaudio[2244]: module-alsa-card.c: Failed to find a working profile.
Sep 13 23:35:18 archtop pulseaudio[2244]: module.c: Failed to load  module "module-alsa-card" (argument: "device_id="29" name="platform-thinkpad_acpi" card_name="alsa_card.platform-thinkpad_acpi" tsched=yes ignore_dB=no card_properties="module-udev-detect.discovered=1""): initialization failed.
Sep 13 23:35:19 archtop kernel: fuse init (API version 7.14)
Sep 13 23:35:30 archtop dhcpcd[2627]: dhcpcd not running
Sep 13 23:35:30 archtop kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 13 23:35:30 archtop dhcpcd[2650]: dhcpcd not running
Sep 13 23:35:31 archtop kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Sep 13 23:35:31 archtop kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Sep 13 23:35:31 archtop kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 13 23:35:31 archtop dhcpcd[2678]: dhcpcd not running
Sep 13 23:35:31 archtop kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 13 23:35:36 archtop kernel: wlan0: authenticate with ${MAC_ADDRESS} (try 1)
Sep 13 23:35:36 archtop kernel: wlan0: authenticated
Sep 13 23:35:36 archtop kernel: wlan0: associate with ${MAC_ADDRESS} (try 1)
Sep 13 23:35:36 archtop kernel: wlan0: RX AssocResp from ${MAC_ADDRESS} (capab=0x431 status=0 aid=3)
Sep 13 23:35:36 archtop kernel: wlan0: associated
Sep 13 23:35:36 archtop kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep 13 23:35:36 archtop kernel: cfg80211: Calling CRDA for country: US
Sep 13 23:35:36 archtop kernel: Intel AES-NI instructions are not detected.
Sep 13 23:35:36 archtop kernel: padlock: VIA PadLock not detected.
Sep 13 23:35:36 archtop kernel: /dev/vmnet: open called by PID 2103 (vmnet-bridge)
Sep 13 23:35:36 archtop kernel: /dev/vmnet: hub 0 does not exist, allocating memory.
Sep 13 23:35:36 archtop kernel: /dev/vmnet: port on hub 0 successfully opened
Sep 13 23:35:36 archtop kernel: bridge-wlan0: up
Sep 13 23:35:36 archtop vmnetBridge: Adding interface wlan0 index:4
Sep 13 23:35:36 archtop vmnetBridge: Started bridge wlan0 to virtual network 0.
Sep 13 23:35:36 archtop kernel: bridge-wlan0: attached
Sep 13 23:35:37 archtop dhcpcd[3483]: version 5.2.7 starting
Sep 13 23:35:37 archtop dhcpcd[3483]: wlan0: broadcasting for a lease
Sep 13 23:35:47 archtop kernel: wlan0: no IPv6 routers present
Sep 13 23:36:07 archtop dhcpcd[3483]: timed out
Sep 13 23:36:07 archtop dhcpcd[3648]: dhcpcd not running
Sep 13 23:36:07 archtop kernel: wlan0: deauthenticating from ${MAC_ADDRESS} by local choice (reason=3)
Sep 13 23:36:07 archtop vmnetBridge: Removing interface wlan0 index:4
Sep 13 23:36:07 archtop kernel: bridge-wlan0: disabling the bridge on dev down
Sep 13 23:36:07 archtop kernel: bridge-wlan0: down
Sep 13 23:36:07 archtop kernel: cfg80211: Calling CRDA to update world regulatory domain
Sep 13 23:36:07 archtop kernel: bridge-wlan0: detached
Sep 13 23:36:07 archtop kernel: /dev/vmnet: open called by PID 2103 (vmnet-bridge)
Sep 13 23:36:07 archtop kernel: /dev/vmnet: hub 0 does not exist, allocating memory.
Sep 13 23:36:07 archtop kernel: /dev/vmnet: port on hub 0 successfully opened
Sep 13 23:36:07 archtop kernel: bridge-wlan0: attached
Sep 13 23:36:07 archtop vmnetBridge: Stopped bridge wlan0 to virtual network 0.
Sep 13 23:36:07 archtop vmnetBridge: Adding interface wlan0 index:4
Sep 13 23:36:07 archtop vmnetBridge: Started bridge wlan0 to virtual network 0.
Sep 13 23:36:07 archtop vmnetBridge: Removing interface wlan0 index:4
Sep 13 23:36:07 archtop kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 13 23:36:07 archtop kernel: bridge-wlan0: enabling the bridge on dev up
Sep 13 23:36:07 archtop kernel: bridge-wlan0: up
Sep 13 23:36:07 archtop kernel: bridge-wlan0: disabling the bridge
Sep 13 23:36:07 archtop dhcpcd[3657]: dhcpcd not running
Sep 13 23:36:07 archtop kernel: bridge-wlan0: down
Sep 13 23:36:07 archtop kernel: bridge-wlan0: detached
Sep 13 23:36:07 archtop vmnetBridge: Stopped bridge wlan0 to virtual network 0.
Sep 13 23:36:08 archtop kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Sep 13 23:36:08 archtop kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Sep 13 23:36:08 archtop kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready

Any ideas?

Thanks!

Last edited by w1ntermute (2010-09-14 04:47:21)

warenoso · 2010-09-14 05:03:08

what wireless card do you have?

w1ntermute · 2010-09-14 05:10:59

Woops, forgot to include hardware specs:

ThinkPad T400 with an Intel 4965AGN.

Last edited by w1ntermute (2010-09-14 05:11:09)

warenoso · 2010-09-14 05:18:34

could you paste iwconfig output

w1ntermute · 2010-09-14 05:39:47

lo        no wireless extensions.

eth0      no wireless extensions.

vboxnet0  no wireless extensions.

wmx0      no wireless extensions.

wwan0     no wireless extensions.

vmnet1    no wireless extensions.

vmnet8    no wireless extensions.

wlan0     IEEE 802.11abgn  Mode:Managed  Frequency:2.417 GHz  
          Access Point: Not-Associated   Tx-Power=14 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

ewaller · 2010-09-14 06:36:04

I'm just guessing here. I have not set one up in years since I did it with physical NIC cards; but...

Is it possible you have constructed a bridge interface (TAP) and then added one of the VmWare virtual interfaces and wlan0 to that bridge?

Sep 13 23:36:07 archtop vmnetBridge: Adding interface wlan0 index:4
Sep 13 23:36:07 archtop vmnetBridge: Started bridge wlan0 to virtual network 0.

That looks ominous.

IIRC, dhcpcd needs to be applied to the bridge, not the NIC. Whats worse, the wlan0 is not associated according to iwconfig, Now my head hurts :-/

Did you intend to set up a bridge? I find that NAT works much better (unless you need to use the virtual machine as a network server)

w1ntermute · 2010-09-14 23:48:19

ewaller wrote:

Is it possible you have constructed a bridge interface (TAP) and then added one of the VmWare virtual interfaces and wlan0 to that bridge?

I haven't manually set up any interfaces, that's for sure. In VirtualBox my network adapter is set to "Attached to: NAT", not "Attached to: Bridged Adapter".

Did you intend to set up a bridge? I find that NAT works much better (unless you need to use the virtual machine as a network server)

No, I didn't intend to set up anything. I just want wireless and wired to work on my laptop and on my virtual machine, and I want to be able to access shared folders from my host OS in my Windows XP guest OS (which happens via the network sharing functionality in Windows).

Also, today I tried connecting to another wireless network, and I was successful, so maybe it's something about the way that my home wireless settings are configured. I tried rebooting several times yesterday when I couldn't connect at home, so I don't think it was something fixed by me rebooting before I tried connecting to the other wireless network. I'll try again to connect to my home network in a bit, just in case it was.

Last edited by w1ntermute (2010-09-14 23:50:51)

kcirick · 2010-09-15 01:01:43

I had the same issue using BCM4328 wireless card. I couldn't figure out the problem, but network manager had no problem whatsoever, so I'm using that instead.

1LordAnubis · 2010-09-15 20:58:30

Same thing happened here on my iwl3945 thinkpad... seems to do it at random times; I switched from fam to gamin not that long ago, perhaps that or my daemons array affect it, idk. Restarting hal, wicd seemed to get it working, but idk why there is a problem all of a sudden; I have @gamin early in daemons array in rc.conf and @wicd about last and it still seems to do it.
That being said, my laptop with a nearly identical setup with ath5k has had no issue.

Edit: Confused what gamin substituted (fam)

Also: I first noticed this happening only when I was running on battery power, increasing in probability as the battery discharged.

Last edited by 1LordAnubis (2010-09-16 01:00:43)

kcirick · 2010-09-15 23:59:54

1LordAnubis wrote:

Same thing happened here on my iwl3945 thinkpad... seems to do it at random times; I switched from hal to gamin not that long ago, perhaps that or my daemons array affect it, idk. Restarting gamin, wicd seemed to get it working, but idk why there is a problem all of a sudden; I have @gamin early in daemons array in rc.conf and @wicd about last and it still seems to do it.
That being said, my laptop with a nearly identical setup with ath5k has had no issue.

I don't think gamin has a daemon? check your /etc/rc.d. there's not gamin daemon in there

1LordAnubis · 2010-09-16 01:02:35

kcirick wrote:

1LordAnubis wrote:
Same thing happened here on my iwl3945 thinkpad... seems to do it at random times; I switched from hal to gamin not that long ago, perhaps that or my daemons array affect it, idk. Restarting gamin, wicd seemed to get it working, but idk why there is a problem all of a sudden; I have @gamin early in daemons array in rc.conf and @wicd about last and it still seems to do it.
That being said, my laptop with a nearly identical setup with ath5k has had no issue.
I don't think gamin has a daemon? check your /etc/rc.d. there's not gamin daemon in there

Thanks for clearing that up

aboutblank · 2010-09-19 16:23:57

On my Thinkpad with Intel 4965 wireless, I'm having many issues one of which being that dhcpd times out when trying to connect to wireless network. I've determined that I'm getting massive packet loss (on the order of 40%) regardless of the AP, which may be the cause of the issues. After connecting to an access point, trying pinging google.com for a while.

Last edited by aboutblank (2010-09-19 16:25:05)

w1ntermute · 2010-09-19 16:27:11

aboutblank wrote:

On my Thinkpad with Intel 4965 wireless, I'm having many issues one of which being that dhcpd times out when trying to connect to wireless network. I've determined that I'm getting massive packet loss (on the order of 40%) regardless of the AP, which may be the cause of the issues. After connecting to an access point, trying pinging google.com for a while.

OK, I'll give that a shot.

Is this an issue with the 4965 driver, or is it something Arch-specific? Have you used any other distros on your ThinkPad?

aboutblank · 2010-09-19 16:37:18

w1ntermute wrote:

Is this an issue with the 4965 driver, or is it something Arch-specific? Have you used any other distros on your ThinkPad?

Virtually nothing is specific to Arch itself, but rather specific to a particular package.

It's quite possible this is a bug in the iwlagn/iwlcore modules in the 2.6.35 kernel. If that's the case, you might also see this issue with the Ubuntu 10.10 beta, which also has that kernel. But no, I have not tried any other distros.

w1ntermute · 2010-09-19 16:42:15

Alright, I guess I'll download Ubuntu 10.04 and the 10.10 beta and compare their behavior.

Svenstaro · 2010-09-19 16:49:20

I had this a few times. I then switched to dhclient instead of dhcpcd and my issues went away. Try dhclient.

aboutblank · 2010-09-19 17:00:55

w1ntermute wrote:

Alright, I guess I'll download Ubuntu 10.04 and the 10.10 beta and compare their behavior.

What was the result of the packet loss test?

w1ntermute · 2010-09-19 17:05:36

aboutblank wrote:

w1ntermute wrote:
Alright, I guess I'll download Ubuntu 10.04 and the 10.10 beta and compare their behavior.
What was the result of the packet loss test?

I can't test it now because I'm at home, and I can't connect to my home wireless network. I'll test it on a wireless network that I can connect to tomorrow.

aboutblank · 2010-09-19 17:08:41

w1ntermute wrote:

aboutblank wrote:
w1ntermute wrote:
Alright, I guess I'll download Ubuntu 10.04 and the 10.10 beta and compare their behavior.
What was the result of the packet loss test?
I can't test it now because I'm at home, and I can't connect to my home wireless network. I'll test it on a wireless network that I can connect to tomorrow.

If it's packet loss that is preventing you from connecting to the home wireless, having it try and try again will hopefully eventually get you connected. This happened at campus a couple times and I couldn't connect until I'd rebooted 3 times (dunno if rebooting actually changed anything).

w1ntermute · 2010-09-19 18:01:33

aboutblank wrote:

If it's packet loss that is preventing you from connecting to the home wireless, having it try and try again will hopefully eventually get you connected.

That's what happened the day I started the thread. I kept trying to connect and rebooted a few times, but it didn't help.

Last edited by w1ntermute (2010-09-19 18:01:56)

adamlogan · 2010-09-19 20:24:24

Svenstaro wrote:

I had this a few times. I then switched to dhclient instead of dhcpcd and my issues went away. Try dhclient.

Out of curiosity I tried this out. Installed dhclient (sudo pacman -Sy dhclient) with success, but then removing dhcpcd (sudo pacman -Rs dhcpcd) fails not because of an error, but that wicd requires the dhcpcd package... Did you just leave dhcpcd installed along with dhclient? I don't get how that would help.

Also out of curiosity, what is the benefit of replacing hal with garmin?

I appear to be getting the dbus errors only when I try to use the experimental python backends. If I use the default "external" it works fine.

Last edited by adamlogan (2010-09-24 01:07:35)

Svenstaro · 2010-09-19 21:57:16

I just have dhcpcd still on still since I don't really care. Wicd now uses dhclient and I am happy.

1LordAnubis · 2010-09-23 20:51:11

adamlogan wrote:

Also out of curiosity, what is the benefit of replacing hal with garmin?

Sorry, I meant to say to replace *fam* with gamin; http://wiki.archlinux.org/index.php/Gamin

Last edited by 1LordAnubis (2010-09-23 20:52:10)

Arch Linux

#1 2010-09-14 04:45:26

Wicd: "Connection failed: Unable to get IP Address"

#2 2010-09-14 05:03:08

Re: Wicd: "Connection failed: Unable to get IP Address"

#3 2010-09-14 05:10:59

Re: Wicd: "Connection failed: Unable to get IP Address"

#4 2010-09-14 05:18:34

Re: Wicd: "Connection failed: Unable to get IP Address"

#5 2010-09-14 05:39:47

Re: Wicd: "Connection failed: Unable to get IP Address"

#6 2010-09-14 06:36:04

Re: Wicd: "Connection failed: Unable to get IP Address"

#7 2010-09-14 23:48:19

Re: Wicd: "Connection failed: Unable to get IP Address"

#8 2010-09-15 01:01:43

Re: Wicd: "Connection failed: Unable to get IP Address"

#9 2010-09-15 20:58:30

Re: Wicd: "Connection failed: Unable to get IP Address"

#10 2010-09-15 23:59:54

Re: Wicd: "Connection failed: Unable to get IP Address"

#11 2010-09-16 01:02:35

Re: Wicd: "Connection failed: Unable to get IP Address"

#12 2010-09-19 16:23:57

Re: Wicd: "Connection failed: Unable to get IP Address"

#13 2010-09-19 16:27:11

Re: Wicd: "Connection failed: Unable to get IP Address"

#14 2010-09-19 16:37:18

Re: Wicd: "Connection failed: Unable to get IP Address"

#15 2010-09-19 16:42:15

Re: Wicd: "Connection failed: Unable to get IP Address"

#16 2010-09-19 16:49:20

Re: Wicd: "Connection failed: Unable to get IP Address"

#17 2010-09-19 17:00:55

Re: Wicd: "Connection failed: Unable to get IP Address"

#18 2010-09-19 17:05:36

Re: Wicd: "Connection failed: Unable to get IP Address"

#19 2010-09-19 17:08:41

Re: Wicd: "Connection failed: Unable to get IP Address"

#20 2010-09-19 18:01:33

Re: Wicd: "Connection failed: Unable to get IP Address"

#21 2010-09-19 20:24:24

Re: Wicd: "Connection failed: Unable to get IP Address"

#22 2010-09-19 21:57:16

Re: Wicd: "Connection failed: Unable to get IP Address"

#23 2010-09-23 20:51:11

Re: Wicd: "Connection failed: Unable to get IP Address"

Board footer