LinuxQuestions.org - Atheros ath9k and wicd in Slackware64...can not connect

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Atheros ath9k and wicd in Slackware64...can not connect (https://www.linuxquestions.org/questions/slackware-14/atheros-ath9k-and-wicd-in-slackware64-can-not-connect-748281/)

Atheros ath9k and wicd in Slackware64...can not connect

My HP fried the north bridge so I have a brand spanking new Asus K50. Being a dedicated Slacker I promptly pulled the Vista HD and replaced it with a shiny new Slackware64 HD. It has an atheros AR9285 wireless card. I have tried using wpa_supplicant as I have done in the past with no luck. I installed wicd from /extra and restarted. I can connect to my network with the wired card with no problem, and I can see all the nearby networks in the list including my own. When I try to connect it spends a while at "Validation Authentication" then finally makes it to "Obtaining IP address". It finally ends up with "Unable to Get IP Address"

/var/log/wicd/wicd.log "cleansed"

Code:

2009/08/18 00:06:34 :: iwconfig wlan0

2009/08/18 00:06:36 :: Connecting to wireless network SSID

2009/08/18 00:06:36 :: /sbin/dhcpcd -k eth0

2009/08/18 00:06:36 :: ifconfig eth0 0.0.0.0 

2009/08/18 00:06:36 :: /sbin/ip route flush dev eth0

2009/08/18 00:06:36 :: ifconfig eth0 down

2009/08/18 00:06:36 :: ifconfig eth0 up

2009/08/18 00:06:36 :: Putting interface down

2009/08/18 00:06:36 :: ifconfig wlan0 down

2009/08/18 00:06:36 :: iwconfig wlan0

2009/08/18 00:06:36 :: Releasing DHCP leases...

2009/08/18 00:06:36 :: /sbin/dhcpcd -k wlan0

2009/08/18 00:06:36 :: Setting false IP...

2009/08/18 00:06:36 :: ifconfig wlan0 0.0.0.0 

2009/08/18 00:06:36 :: Stopping wpa_supplicant

2009/08/18 00:06:36 :: wpa_cli -i wlan0 terminate

2009/08/18 00:06:36 :: Flushing the routing table...

2009/08/18 00:06:36 :: /sbin/ip route flush dev wlan0

2009/08/18 00:06:36 :: iwconfig wlan0 mode managed

2009/08/18 00:06:36 :: Putting interface up...

2009/08/18 00:06:36 :: ifconfig wlan0 up

2009/08/18 00:06:36 :: enctype is wpa

2009/08/18 00:06:36 :: Generating psk...

2009/08/18 00:06:36 :: ['/usr/sbin/wpa_passphrase', 'SSID', 'PW']

2009/08/18 00:06:36 :: Attempting to authenticate...

2009/08/18 00:06:36 :: ['wpa_supplicant', '-B', '-i', 'wlan0', '-c', '/var/lib/wicd/configurations/0018f8bdef84', '-D', 'wext']

2009/08/18 00:06:36 :: ['iwconfig', 'wlan0', 'essid', 'SSID']

2009/08/18 00:06:36 :: iwconfig wlan0 channel 9

2009/08/18 00:06:36 :: iwconfig wlan0 ap 00:18:F8:BD:EF:84

2009/08/18 00:06:36 :: WPA_CLI RESULT IS DISCONNECTED

2009/08/18 00:06:37 :: WPA_CLI RESULT IS ASSOCIATED

2009/08/18 00:06:38 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:39 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:40 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:41 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:42 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:44 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:45 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:46 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:47 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:48 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:49 :: WPA_CLI RESULT IS ASSOCIATING

2009/08/18 00:06:50 :: WPA_CLI RESULT IS ASSOCIATED

2009/08/18 00:06:51 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:52 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:53 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:54 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:55 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:56 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:57 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:58 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:06:59 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:00 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:01 :: WPA_CLI RESULT IS DISCONNECTED

2009/08/18 00:07:02 :: WPA_CLI RESULT IS ASSOCIATING

2009/08/18 00:07:03 :: WPA_CLI RESULT IS ASSOCIATED

2009/08/18 00:07:04 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:05 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:06 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:07 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:08 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:09 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:10 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:11 :: WPA_CLI RESULT IS 4WAY_HANDSHAKE

2009/08/18 00:07:12 :: wpa_supplicant authentication may have failed.

2009/08/18 00:07:12 :: Running DHCP

2009/08/18 00:07:12 :: /sbin/dhcpcd wlan0

2009/08/18 00:07:32 :: err, wlan0: timed out

2009/08/18 00:07:32 :: 

2009/08/18 00:07:32 :: DHCP connection failed

2009/08/18 00:07:32 :: exiting connection thread

2009/08/18 00:07:32 :: Sending connection attempt result dhcp_failed

2009/08/18 00:07:32 :: ifconfig eth0

2009/08/18 00:07:32 :: ifconfig wlan0

...

2009/08/18 00:09:25 :: iwconfig wlan0

2009/08/18 00:09:27 :: ifconfig eth0

2009/08/18 00:09:27 :: ifconfig wlan0

2009/08/18 00:09:27 :: iwconfig wlan0

lspci | grep Wireless

Code:

02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

iwconfig

Code:

wlan0    IEEE 802.11bgn  Mode:Managed  Frequency:2.452 GHz  

          Access Point: Not-Associated  Tx-Power=27 dBm    

          Retry min limit:7  RTS thr:off  Fragment thr=2352 B  

          Encryption key:off                                      

          Power Management:off                                    

          Link Quality:0  Signal level:0  Noise level:0

          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:0  Missed beacon:0

I've googled my fingers off and I am still tethered to the wall. Please point me in the right direction.

Thanks,
Eric

oh yea,
lsmod | grep ath

Code:

ath9k                328688  0

mac80211              171288  1 ath9k

rfkill                11316  2 ath9k

led_class              4360  2 ath9k,asus_laptop

I haven't tried wicd, but I might be able to help you with wpa_supplicant. Judging from your output, it looks like you can't authenticate with the password you gave. I know that seems obvious, but I didn't see the line I always get: wlan0 authenticated. I always use wpa_passphrase <ssid> <password>, then take that hex output and put it in my wpa_supplicant.conf file.

If that doesn't work, I have an ASUS motherboard with an ethernet controller and a wifi card. For Slackware 12.2, my problem was that Slackware was trying to use the ethernet card even without a cable plugged in. My solution in /etc/rc.d/inetd.conf was to comment out the wired controller so that Slackware would use the wireless controller. Might work for you.

I haven't had to do do that in the past, but I'll certainly give it a try. I have always used wpa_gui to fire up which ever network I was on, from there I could re-connect from the CLI. I'll see what happens.

Thanks,
Eric

Looking at your output from wicd, it looks like it's doing wpa_passphrase already.

Quote:

'/usr/sbin/wpa_passphrase', 'SSID', 'PW'

Do you have mac filtering setup on your wireless router? Did you add the new card to your list?

This might help you too:
http://alien.slackbook.org/dokuwiki/...ckware:network

I do not have mac filtering on my router. I get the same result trying to connect to the wireless network here at work. I did re-read the log as you did and noticed that wicd was also handling the wpa_passphrase. I have read through the wireless section of slackbook, but I'm going to re-read it and look for something I missed.

Thanks again,
Eric

Or maybe wicd is failing in detecting the encryption algorithm; wicd successfully detects that you're using WPA, but maybe it doesn't know if you're using TKIP or AES.

Also, you might want to try using a fixed IP in wicd (if possible), so you have less variables that can go wrong.

Saw another thread that mentions there might be a conflict between inetd.conf and wicd...he just used the default inetd.conf and things worked fine.

If you're not broadcasting the SSID, this can make things a little more tricky as well...

I may have narrowed it down to dhclient

dhclient wlan0

Code:



wmaster0: unknown hardware address type 801

wmaster0: unknown hardware address type 801

Listening on LPF/wlan0/00:24:23:0a:2b:1b

Sending on  LPF/wlan0/00:24:23:0a:2b:1b

Sending on  Socket/fallback

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4

No DHCPOFFERS received.

No working leases in persistent database - sleeping.

wmaster0 is unknown to me. I don't know why it would get polled when I told it to broadcast on wlan0

My ssid is broadcast and shows up readily in wicd.

A quick search on wmaster0 revealed this: http://ubuntuforums.org/showthread.php?t=697807. Anyway, dhclient will probably ignore it since it doesn't know what it is. Those DHCPDISCOVER lines look strange--hopefully you just sanitized the output or do they point to your router (x.x.x.1)?

After looking at wicd posts, can you post the output (sanitized) of /var/lib/wicd/configurations/0018f8bdef84 (or whatever the filename is when you run wicd)?

This post gave me the idea: http://wicd.net/punbb/viewtopic.php?pid=1545

My router happily gives my wifes machine an IP address so I know the router is working fine. The more I read the less I am convinced that ath9k is ready to handle my wireless card. This being an N card, it's pretty new. I have seen many questions similar to mine all with no resolution at this time. I have 2 broadcom cards at home that I am strongly considering swapping in. I have successfully setup b43 in the past, so I'm sure I can do it again.

DHCPDISCOVER is always broadcast to 255.255.255.255 as the card does not yet know the ip address of the router to which it is trying to connect.

http://support.microsoft.com/kb/169289

Per the article, it appears that all negotiation is at this address and at 0.0.0.0.

After looking at wicd posts, can you post the output (sanitized) of /var/lib/wicd/configurations/0018f8bdef84 (or whatever the filename is when you run wicd)? This post gave me the idea: http://wicd.net/punbb/viewtopic.php?pid=1545.

I put my known good broadcom b/g card in and setup the firmware, I now have wireless! I won't mark this thread as solved since I still didn't get the athreos card working. A bonus though, wicd works which was not true with my old machine.

Thanks vik for all your help.

Eric

No problem. Sorry I couldn't be of more assistance...

I had the exact same error, however the wlan works like a charm with the latest compat drivers