Trouble connecting to WEP AP

Hamsterkill · 2010-06-30 13:56:56

I've been having issues connecting to the WEP network where I work. My laptop can connect to it fine in Windows(dual boot), and I can connect to my home WPA network in Linux and Windows fine. I can't seem to figure it out. I can scan the network okay (though it doesn't show in iwlist every time -- usually only half the time for whatever reason). The signal strength is more than adequate.

I don't know whether this started happening from an update in Arch or because my workplace replaced the main wireless router (but not the AP I connect to).

I just can't seem to get associated with the access point anymore on this network. I know it tries, because if I enter a bad key it rejects it immediately in Wicd. When I use the proper key, it tries validate authentication for a several seconds before failing with a 'bad password'. I've tried using the console to connect as well, specifying the MAC of the AP I connect to even, but iwconfig never shows it as associated and dhcpcd produces no output before timing out.

dmesg output:

# dmesg | grep 'wlan\|iwl'
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
iwlagn: Copyright(c) 2003-2010 Intel Corporation
iwlagn 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
iwlagn 0000:02:00.0: setting latency timer to 64
iwlagn 0000:02:00.0: Detected Intel Wireless WiFi Link 6000 Series 2x2 AGN REV=0x74
iwlagn 0000:02:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
iwlagn 0000:02:00.0: irq 30 for MSI/MSI-X
iwlagn 0000:02:00.0: firmware: requesting iwlwifi-6000-4.ucode
iwlagn 0000:02:00.0: loaded firmware version 9.193.4.1
phy0: Selected rate control algorithm 'iwl-agn-rs'
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: direct probe to 00:1a:70:ee:9e:9c (try 1)
wlan0: direct probe to 00:1a:70:ee:9e:9c (try 2)
wlan0: direct probe to 00:1a:70:ee:9e:9c (try 3)
wlan0: direct probe to 00:1a:70:ee:9e:9c timed out
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready

# uname -r
2.6.34-ARCH

Last edited by Hamsterkill (2010-06-30 13:58:08)

Sin.citadel · 2010-07-01 12:19:25

from the log, it looks like that your machine is unable to associate with the AP, could be that the AP has MAC filtering enabled or the AP has changed some channels or settings on it, if you have any other linux livecd available, put it in and then see, since it could also be a driver problem (not likely) or an arch problem

Hamsterkill · 2010-07-01 13:23:43

Sin.citadel wrote:

from the log, it looks like that your machine is unable to associate with the AP, could be that the AP has MAC filtering enabled or the AP has changed some channels or settings on it, if you have any other linux livecd available, put it in and then see, since it could also be a driver problem (not likely) or an arch problem

I'll give the Livecd idea a try. I know it's not MAC filtered, since I can connect fine in Windows on the same laptop, which would use the same MAC. I don't know why changing the channels would throw the ability to connect just by ESSID off, though according to IT, the new router should be configured the same way the old one was.

crankyadmin · 2010-07-01 15:11:56

The change of channels to a more 'crowded' some can cause serious issue connecting to some wireless networks. But in this case I don't think this is your problem.

When you try and connect is there anything interesting when you run dmesg?

Hamsterkill · 2010-07-02 13:28:16

crankyadmin wrote:

The change of channels to a more 'crowded' some can cause serious issue connecting to some wireless networks. But in this case I don't think this is your problem.
When you try and connect is there anything interesting when you run dmesg?

The dmesg log I posted in the OP includes a connection attempt.

Hamsterkill · 2010-07-06 14:04:46

Tried again in Puppy Linux LiveCD. Same results as in Arch. Kernel 2.6.33 on Puppy.

I'm starting to wonder if it has something to do with the network only appearing in scans about half the time.

rednano12 · 2010-07-06 20:33:44

I'm having a near identical problem to yours. The only difference is, I can connect manually. However, this manual connection lasts 30 seconds and goes away if I start X. It would be interesting to hear if others have the same problem.

ewaller · 2010-07-07 01:49:06

I had an identical problem a while back. If I remember correctly, I had a case sensitivity problem with WEP ESSIDs, but not with WPA ESSIDs. I was using wicd at the time and it seemed to want to change the case of the ESSID to all caps (I think). Regardless, I found network manager did not alter the ESSID from what I specified, it got me on the air when I was pressed for time, and I never saw fit to go back. YMMV.

Hamsterkill · 2010-07-08 13:32:30

ewaller wrote:

I had an identical problem a while back. If I remember correctly, I had a case sensitivity problem with WEP ESSIDs, but not with WPA ESSIDs. I was using wicd at the time and it seemed to want to change the case of the ESSID to all caps (I think). Regardless, I found network manager did not alter the ESSID from what I specified, it got me on the air when I was pressed for time, and I never saw fit to go back. YMMV.

My first thought was that it was a bug in Wicd. The thing is, I can't even seem to connect using iwconfig and a call to dhcpcd.

Arch Linux

#1 2010-06-30 13:56:56

Trouble connecting to WEP AP

#2 2010-07-01 12:19:25

Re: Trouble connecting to WEP AP

#3 2010-07-01 13:23:43

Re: Trouble connecting to WEP AP

#4 2010-07-01 15:11:56

Re: Trouble connecting to WEP AP

#5 2010-07-02 13:28:16

Re: Trouble connecting to WEP AP

#6 2010-07-06 14:04:46

Re: Trouble connecting to WEP AP

#7 2010-07-06 20:33:44

Re: Trouble connecting to WEP AP

#8 2010-07-07 01:49:06

Re: Trouble connecting to WEP AP

#9 2010-07-08 13:32:30

Re: Trouble connecting to WEP AP

Board footer