Hello,
I have the AR9285 wireless adaptor on an HP DV6-2128ca notebook. I can see it. it comes up in NetworkManager but never gets an IP. the router is a linksys using WPA/PSK security. Would/could someone please help me out trying to get this to work? Output of several commands follows:
dmesg:
ath: EEPROM regdomain: 0x69 ath: EEPROM indicates we should expect a direct regpair map ath: Country alpha2 being used: 00 ath: Regpair used: 0x69 phy0: Selected rate control algorithm 'ath9k_rate_control' Registered led device: ath9k-phy0::radio Registered led device: ath9k-phy0::assoc Registered led device: ath9k-phy0::tx Registered led device: ath9k-phy0::rx phy0: Atheros AR9285 MAC/BB Rev:2 AR5133 RF Rev:e0: mem=0xf8bc0000, irq=185
cat /etc/modprobe.conf:
alias wlan0 ath9k
tail /var/log/messages:
Jul 27 19:31:02 smurf3 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete. Jul 27 19:31:02 smurf3 NetworkManager: <info> (wlan0): device state change: 9 -> 3 Jul 27 19:31:02 smurf3 NetworkManager: <info> (wlan0): deactivating device (reason: 0). Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) starting connection 'Auto pszone' Jul 27 19:31:24 smurf3 NetworkManager: <info> (wlan0): device state change: 3 -> 4 Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jul 27 19:31:24 smurf3 NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0/wireless): access point 'Auto pszone' has security, but secrets are required. Jul 27 19:31:24 smurf3 NetworkManager: <info> (wlan0): device state change: 5 -> 6 Jul 27 19:31:24 smurf3 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jul 27 19:31:31 smurf3 NetworkManager: <info> (wlan0): device state change: 6 -> 4 Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jul 27 19:31:31 smurf3 NetworkManager: <info> (wlan0): device state change: 4 -> 5 Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto pszone' has security, and secrets exist. No new secrets needed. Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: added 'ssid' value 'pszone' Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: added 'scan_ssid' value '1' Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: added 'psk' value '<omitted>' Jul 27 19:31:31 smurf3 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jul 27 19:31:31 smurf3 NetworkManager: <info> Config: set interface ap_scan to 1 Jul 27 19:31:31 smurf3 NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant connection state: associated -> 4-way handshake Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant connection state: 4-way handshake -> group handshake Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'pszone'. Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Jul 27 19:31:38 smurf3 NetworkManager: <info> (wlan0): device state change: 5 -> 7 Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction. Jul 27 19:31:38 smurf3 dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat Jul 27 19:31:38 smurf3 dhclient: Copyright 2004-2006 Internet Systems Consortium. Jul 27 19:31:38 smurf3 dhclient: All rights reserved. Jul 27 19:31:38 smurf3 dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Jul 27 19:31:38 smurf3 dhclient: Jul 27 19:31:38 smurf3 NetworkManager: <info> dhclient started with pid 30770 Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Jul 27 19:31:38 smurf3 NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit Jul 27 19:31:38 smurf3 dhclient: Listening on LPF/wlan0/c4:17:fe:bb:6a:df Jul 27 19:31:38 smurf3 dhclient: Sending on LPF/wlan0/c4:17:fe:bb:6a:df Jul 27 19:31:38 smurf3 dhclient: Sending on Socket/fallback Jul 27 19:31:38 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Jul 27 19:31:42 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 Jul 27 19:31:53 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 Jul 27 19:32:07 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20 Jul 27 19:32:23 smurf3 NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it. Jul 27 19:32:23 smurf3 NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 30770 Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled... Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started... Jul 27 19:32:23 smurf3 NetworkManager: <info> (wlan0): device state change: 7 -> 9 Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) failed for access point (pszone) Jul 27 19:32:23 smurf3 NetworkManager: <info> Marking connection 'Auto pszone' invalid. Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) failed. Jul 27 19:32:23 smurf3 NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete. Jul 27 19:32:23 smurf3 NetworkManager: <info> (wlan0): device state change: 9 -> 3 Jul 27 19:32:23 smurf3 NetworkManager: <info> (wlan0): deactivating device (reason: 0)
Thank you,
Phil
On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie psavoie1783@rogers.com wrote:
Beginning DHCP transaction. Jul 27 19:31:38 smurf3 dhclient: Internet Systems Consortium DHCP Client V3.0.5-RedHat Jul 27 19:31:38 smurf3 dhclient: Copyright 2004-2006 Internet Systems Consortium. Jul 27 19:31:38 smurf3 dhclient: All rights reserved. Jul 27 19:31:38 smurf3 dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Jul 27 19:31:38 smurf3 dhclient: Jul 27 19:31:38 smurf3 NetworkManager: <info> dhclient started with pid 30770 Jul 27 19:31:38 smurf3 NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Jul 27 19:31:38 smurf3 NetworkManager: <info> DHCP: device wlan0 state changed normal exit -> preinit Jul 27 19:31:38 smurf3 dhclient: Listening on LPF/wlan0/c4:17:fe:bb:6a:df Jul 27 19:31:38 smurf3 dhclient: Sending on LPF/wlan0/c4:17:fe:bb:6a:df Jul 27 19:31:38 smurf3 dhclient: Sending on Socket/fallback Jul 27 19:31:38 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Jul 27 19:31:42 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 Jul 27 19:31:53 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 Jul 27 19:32:07 smurf3 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20 Jul 27 19:32:23 smurf3 NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it. Jul 27 19:32:23 smurf3 NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 30770
It would seem that one possibility is that the AP is not running a DHCP server.
Another is that if the AP is running a DHCP server, it is restricting IP addresses to known clients.
kind regards/ldv
Larry Vaden wrote:
It would seem that one possibility is that the AP is not running a DHCP server.
Another is that if the AP is running a DHCP server, it is restricting IP addresses to known clients.
kind regards/ldv
Hi Larry,
Thanks for your reply. This wifi card is a known host with win 7 (the other half of the dual boot) running fine.
BTW, I forgot to mention that I am running Centos 5.5.
Regards,
Phil
Larry Vaden <vaden@...> writes:
On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie <psavoie1783 <at>
rogers.com> wrote:
Beginning DHCP transaction. TRIMMED<< Jul 27 19:32:23 smurf3 NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it. Jul 27 19:32:23 smurf3 NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 30770
It would seem that one possibility is that the AP is not running a DHCP server.
Another is that if the AP is running a DHCP server, it is restricting IP addresses to known clients.
kind regards/ldv _______________________________________________ CentOS mailing list CentOS <at> centos.org http://lists.centos.org/mailman/listinfo/centos
A couple of suggestions:
1) I had very similar problems with some of the Broadcom drivers for my laptop ("transaction took too long"). An easy test is to *BRIEFLY* disable security on the AP and see if your system connects. If the two systems connect then there is a problem syncing with WPA security. A possible alternative is to use ndiswrapper and the Windows driver instead of the native Linux driver. I've been really happy with ndiswrapper even if it means I'm "impure" for using a Windows driver.
2) The actual key exchange is handled by a daemon called wpa_supplicant. It can be finicky. The config files are /etc/sysconfig/wpa_supplicant and /etc/wpa_supplicant/wpa_supplicant.cnf You may have better luck fiddling with some of the settings in the configuration files. As an example, ndiswrapper works better for me with -D wext instead of -D ndiswrapper.
I've also seen restating wpa_supplicant (as root, "service wpa_supplicant restart) fix things. Also, I've had better luck just getting the wpa_supplicant configuration right and not using NetworkManager (service NetworkManager stop). I just do a "ifup wlan0" from the command line.
Cheers, Dave
On Wed, Jul 28, 2010 at 10:49 AM, Dave Miller dave@davenjudy.org wrote:
I've also seen restating wpa_supplicant (as root, "service wpa_supplicant restart) fix things. Also, I've had better luck just getting the wpa_supplicant configuration right and not using NetworkManager (service NetworkManager stop). I just do a "ifup wlan0" from the command line.
For, anyone who'd rather go for a non-NetworkManager route, this article may help:
http://home.roadrunner.com/~computertaijutsu/wireless.html (maintained by Scott Robbins)
Akemi
From: Dave Miller dave@davenjudy.org
Larry Vaden <vaden@...> writes:
On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie <psavoie1783 <at>
rogers.com> wrote:
Beginning DHCP transaction. TRIMMED<< Jul 27 19:32:23 smurf3 NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it. Jul 27 19:32:23 smurf3 NetworkManager: <info> wlan0: canceled DHCP transaction, dhcp client pid 30770
It would seem that one possibility is that the AP is not running a DHCP server.
Another is that if the AP is running a DHCP server, it is restricting IP addresses to known clients.
kind regards/ldv _______________________________________________ CentOS mailing list CentOS <at> centos.org http://lists.centos.org/mailman/listinfo/centos
A couple of suggestions:
- I had very similar problems with some of the Broadcom drivers for my
laptop ("transaction took too long"). An easy test is to *BRIEFLY* disable security on the AP and see if your system connects. If the two systems connect then there is a problem syncing with WPA security. A possible alternative is to use ndiswrapper and the Windows driver instead of the native Linux driver. I've been really happy with ndiswrapper even if it means I'm "impure" for using a Windows driver.
- The actual key exchange is handled by a daemon called wpa_supplicant.
It can be finicky. The config files are /etc/sysconfig/wpa_supplicant and /etc/wpa_supplicant/wpa_supplicant.cnf You may have better luck fiddling with some of the settings in the configuration files. As an example, ndiswrapper works better for me with -D wext instead of -D ndiswrapper.
I've also seen restating wpa_supplicant (as root, "service wpa_supplicant restart) fix things. Also, I've had better luck just getting the wpa_supplicant configuration right and not using NetworkManager (service NetworkManager stop). I just do a "ifup wlan0" from the command line.
Doesn't it look like the wpa connection is successful? It says: " Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'pszone'." Only stages 3/4 (the DHCP part) seems to fail... The DHCPDISCOVER times out. Google says that some people with linksys DHCP problems in linux rebooted it or flashed it...
JD
Doesn't it look like the wpa connection is successful? It says: " Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'pszone'." Only stages 3/4 (the DHCP part) seems to fail... The DHCPDISCOVER times out. Google says that some people with linksys DHCP problems in linux rebooted it or flashed it...
JD
Thanks for you reply. On further googling, I found that similar cards had the same problem. It seems that if one does a tcpdump in another terminal while using NM it works. I even got the latest firmware on the router.
what works:
tcpdump -i wlan0 host <hostname>
Then run NM and voila! I was able to connect. I wonder why the card has to be in promiscuous mode to work?
Anyone have any thoughts?
Phil
On Jul 29, 2010, at 5:57 PM, Phil Savoie psavoie1783@rogers.com wrote:
Doesn't it look like the wpa connection is successful? It says: " Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'pszone'." Only stages 3/4 (the DHCP part) seems to fail... The DHCPDISCOVER times out. Google says that some people with linksys DHCP problems in linux rebooted it or flashed it...
JD
Thanks for you reply. On further googling, I found that similar cards had the same problem. It seems that if one does a tcpdump in another terminal while using NM it works. I even got the latest firmware on the router.
what works:
tcpdump -i wlan0 host <hostname>
Then run NM and voila! I was able to connect. I wonder why the card has to be in promiscuous mode to work?
Anyone have any thoughts?
Don't know, but I think there is an option you can put in your interface file to bring it up in promiscuous mode. Try that and see if NM can grab it on boot.
-Ross
Ross Walker wrote:
On Jul 29, 2010, at 5:57 PM, Phil Savoie psavoie1783@rogers.com wrote:
Doesn't it look like the wpa connection is successful? It says: " Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'pszone'." Only stages 3/4 (the DHCP part) seems to fail... The DHCPDISCOVER times out. Google says that some people with linksys DHCP problems in linux rebooted it or flashed it...
JD
Thanks for you reply. On further googling, I found that similar cards had the same problem. It seems that if one does a tcpdump in another terminal while using NM it works. I even got the latest firmware on the router.
what works:
tcpdump -i wlan0 host <hostname>
Then run NM and voila! I was able to connect. I wonder why the card has to be in promiscuous mode to work?
Anyone have any thoughts?
Don't know, but I think there is an option you can put in your interface file to bring it up in promiscuous mode. Try that and see if NM can grab it on boot.
-Ross
There used to be a PROMISC=yes setting I could have used int the ifcfg-wlan0 file but is now unsupported according to /usr/share/doc/initscripts-8.45.30/sysconfig.txt.
Thanks for trying though as it is appreciated.
Phil
On Thu, Jul 29, 2010 at 10:04:56PM -0400, Phil Savoie wrote:
Ross Walker wrote:
Don't know, but I think there is an option you can put in your interface file to bring it up in promiscuous mode. Try that and see if NM can grab it on boot.
There used to be a PROMISC=yes setting I could have used int the ifcfg-wlan0 file but is now unsupported according to /usr/share/doc/initscripts-8.45.30/sysconfig.txt.
Thanks for trying though as it is appreciated.
Create a simple S09 script (eg S09PROMISC) which basically just does "/sbin/ifconfig wlan0 promisc up"
eg create this as /etc/init.d/PROMISC and then do "chkconfig PROMISC on"
#!/bin/sh
# PROMISC puts wlan0 in promisc mode # # chkconfig: 2345 09 91 # description: puts wlan0 in promisc mode
case "$1" in start) touch /var/lock/subsys/PROMISC
/sbin/ifconfig wlan0 0.0.0.0 promisc up
;; stop) # Do nothing rm -f /var/lock/subsys/PROMISC ;; status|restart|reload) # Do nothing ;; *) echo $"Usage: $0 {start|stop|restart|reload|status}" exit 1 esac
exit 0
It might work... who knows :-)
Stephen Harris wrote:
Create a simple S09 script (eg S09PROMISC) which basically just does "/sbin/ifconfig wlan0 promisc up"
eg create this as /etc/init.d/PROMISC and then do "chkconfig PROMISC on"
#!/bin/sh
# PROMISC puts wlan0 in promisc mode # # chkconfig: 2345 09 91 # description: puts wlan0 in promisc mode
case "$1" in start) touch /var/lock/subsys/PROMISC
/sbin/ifconfig wlan0 0.0.0.0 promisc up ;;stop) # Do nothing rm -f /var/lock/subsys/PROMISC ;; status|restart|reload) # Do nothing ;; *) echo $"Usage: $0 {start|stop|restart|reload|status}" exit 1 esac
exit 0
It might work... who knows :-)
Great suggestion Stephen! Thanks very much! Just tried it out and it works fine. Just have one question... any reason not to leave the interface in promiscuous mode?
Thanks,
Phil
From: Phil Savoie psavoie1783@rogers.com
I have the AR9285 wireless adaptor on an HP DV6-2128ca notebook. I can see it. it comes up in NetworkManager but never gets an IP. the router is a linksys using WPA/PSK security. Would/could someone please help me out trying to get this to work? Output of several commands follows:
Could it be IPv6?
JD
-
Akemi Yagi -
Dave Miller -
John Doe -
Larry Vaden -
Phil Savoie -
Ross Walker -
Stephen Harris