Re: Problems connecting using ahteros based wireless card
On Thu, 2005-01-27 at 21:28 +0100, Stefan Zechmeister wrote: NetworkManager: Activation (ath0) started... NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): access point 'ESSID' is encrypted, and a key exists. No new key needed. NetworkManager: Activation (ath0/wireless): using essid 'ESSID', with Open System authentication. NetworkManager: Activation (ath0/wireless): no hardware link to 'ESSID' in Open System mode, trying Shared Key. NetworkManager: Activation (ath0/wireless): using essid 'ESSID', with Shared Key authentication. NetworkManager: Activation (ath0/wireless): no hardware link to 'ESSID' in Shared Key mode, trying another access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Caught SIGINT/SIGTERM NetworkManager: Caught terminiation signal NetworkManager: nm_device_activation_cancel(ath0): cancelling... NetworkManager: nm_device_activation_worker(ath0): activation canceled. NetworkManager: nm_device_activation_worker(ath0): activation canceled. NetworkManager: Activation (ath0) ended. NetworkManager: nm_device_activation_cancel(ath0): cancelled. Hi, What you need to do to debug this is the following... In a separate window, run the command watch -n 1 iwconfig ath0 and let that run while NM is trying to associate with the AP. Look at the MAC address that the card reports, and if it changes to FF:FF:FF:FF:FF:FF too often during the link check, then we need to figure out what to do. What NM currently does for a link-check is to wait around 6 or 8 seconds, I think, and for every half-second during that time it wakes up, checks the MAC address the card reports, and if its a valid MAC address (ie not all 0s, all 4s, or all Fs) it increments a counter. If by the end of that full 6 or 8 seconds, the counter is above a certain value, then we decided that we have a link. This particular song dance is necessary for a couple reasons. Some cards need to load firmware into the card whenever you set the ESSID on the card, and that takes a round-trip to user-space hotplug scripts, then back into the kernel to upload the firmware to the card. Then, the card has to boot the firmware, and try to associate. This takes time. Second, some cards have more channels that others, specifically a/b/g cards. They need more time to scan all channels for the access point we're trying to find, and to associate with it. Third, some cards are just plain flaky and will take a while to stabilize the MAC address of the associated AP (they scan around and evidentally pick up the MAC addresses of other APs before they settle on the correct one, I think the problem child here is Orinoco w/ HermesI chipset). So, if you could do the watch thing, that would be great, and report teh results, ie do you see the MAC address be FF:FF:FF... for most of the period when NetworkManager tries to connect to it? Dos it usually stay at the access points MAC? Second, what is the output of lspci, and what brand/model is your Atheros card? I personally use a Netgear WG511T to test out the madwifi drivers and haven't noticed any problems, but that's because the card is b/g only most likely, and doesn't do 802.11a. Thanks! Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems connecting using ahteros based wireless card
Dan Williams wrote: What you need to do to debug this is the following... In a separate window, run the command watch -n 1 iwconfig ath0 and let that run while NM is trying to associate with the AP. Look at the MAC address that the card reports, and if it changes to FF:FF:FF:FF:FF:FF too often during the link check, then we need to figure out what to do. Also do watch -n 1 iwpriv ath0 get_mode in another window to see what mode the Atheros card is being put into. I expect you will see it get stuck in mode 1, which is 802.11a on the Atheros. I experience the same problem with my T41 but have not had time to track down what is pushing the card into 802.11a mode. --[Lance] -- Celebrate The Circle: http://www.celebratethecircle.org/ Carolina Spirit Quest: http://www.carolinaspiritquest.org/ My LiveJournal: http://www.livejournal.com/users/labrown/ GPG Fingerprint: 409B A409 A38D 92BF 15D9 6EEE 9A82 F2AC 69AC 07B9 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems connecting using ahteros based wireless card
Hi, On Thu, 27 Jan 2005 15:46:49 -0500, Dan Williams wrote: On Thu, 2005-01-27 at 21:28 +0100, Stefan Zechmeister wrote: NetworkManager: Activation (ath0) started... NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): access point 'ESSID' is encrypted, and a key exists. No new key needed. NetworkManager: Activation (ath0/wireless): using essid 'ESSID', with Open System authentication. NetworkManager: Activation (ath0/wireless): no hardware link to 'ESSID' in Open System mode, trying Shared Key. NetworkManager: Activation (ath0/wireless): using essid 'ESSID', with Shared Key authentication. NetworkManager: Activation (ath0/wireless): no hardware link to 'ESSID' in Shared Key mode, trying another access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Activation (ath0/wireless): waiting for an access point. NetworkManager: Caught SIGINT/SIGTERM NetworkManager: Caught terminiation signal NetworkManager: nm_device_activation_cancel(ath0): cancelling... NetworkManager: nm_device_activation_worker(ath0): activation canceled. NetworkManager: nm_device_activation_worker(ath0): activation canceled. NetworkManager: Activation (ath0) ended. NetworkManager: nm_device_activation_cancel(ath0): cancelled. Hi, What you need to do to debug this is the following... In a separate window, run the command watch -n 1 iwconfig ath0 and let that run while NM is trying to associate with the AP. Look at the MAC address that the card reports, and if it changes to FF:FF:FF:FF:FF:FF too often during the link check, then we need to figure out what to do. So, if you could do the watch thing, that would be great, and report teh results, ie do you see the MAC address be FF:FF:FF... for most of the period when NetworkManager tries to connect to it? Dos it usually stay at the access points MAC? Second, what is the output of lspci, and what brand/model is your Atheros card? I personally use a Netgear WG511T to test out the madwifi drivers and haven't noticed any problems, but that's because the card is b/g only most likely, and doesn't do 802.11a. Mine is a/b/g. 02:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01) Thanks! Dan I also have this problem with an atheros card, FC3, kernel 2.6.10. Manually configured works OK, and I have a stable ath0 IEEE 802.11a ESSID:home Mode:Managed Frequency:5.17GHz Access Point: 00:05:4E:45:DC:D5 Bit Rate:54Mb/s Tx-Power:50 dBm Sensitivity=0/3 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=60/94 Signal level=-35 dBm Noise level=-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 when I run NM, I found out in the watch -n 1 iwconfig ath0, that it stays few seconds associated this ap, then it starts to change frequencies/channels and of course looses the connection (the ap MAC changes to FF.FF.FF.FF.FF.FF and no essid). The AP is another linux with the same model atheros card as master, and as I said before it is working fine. I tested it in all a/b/g modes (set the ap in mode 1/2/3 manually with iwpriv) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
