* wifi card disconnected right after assoicated with AP @ 2014-04-07 21:27 Shu, Nick 2014-04-08 13:44 ` Kalle Valo 0 siblings, 1 reply; 5+ messages in thread From: Shu, Nick @ 2014-04-07 21:27 UTC (permalink / raw) To: ath10k@lists.infradead.org Hi, All: I'm trying to use a wifi card to associate to a access point, but got a strange thing here. Right after associated with AP, it disconnected from AP, the pattern repeated for: Scan Authentication Association De-authenticated Dis-associated I captured the frames as below, saw a "wlan0 del station <AP's MAC>", why wlan0 do this local request? 0.096321: wlan0 (phy #0): scan started 2.802464: wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5660 5680 5700 5745 5765 5785 5805 5825, "" 0.008130: wlan0: new station c4:04:15:29:cd:2e 0.000462: wlan0 (phy #0): auth c4:04:15:29:cd:2e -> 00:03:07:12:34:56 status: 0: Successful [frame: b0 00 3c 00 00 03 07 12 34 56 c4 04 15 29 cd 2e c4 04 15 29 cd 2e b0 11 00 00 02 00 00 00 dd 09 00 10 18 02 00 00 1c 00 00] 0.004211: wlan0 (phy #0): assoc c4:04:15:29:cd:2e -> 00:03:07:12:34:56 status: 0: Successful [frame: 30 00 3c 00 00 03 0 7 12 34 56 c4 04 15 29 cd 2e c4 04 15 29 cd 2e c0 11 11 10 00 00 01 c0 01 08 8c 12 98 24 b0 48 60 6c 35 01 00 41 01 00 4 6 05 72 00 01 00 00 2d 1a ef 09 17 ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3d 16 99 0f 15 0 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7f 08 04 00 08 00 00 00 00 40 dd 09 00 10 18 02 00 00 1c 00 00 d d 18 00 50 f2 02 01 01 88 00 03 a4 00 00 27 a4 00 00 42 43 bc 00 62 32 66 00] 0.000099: wlan0 (phy #0): connected to c4:04:15:29:cd:2e 0.000858: wlan0: del station c4:04:15:29:cd:2e 0.000508: wlan0 (phy #0): disassoc 00:03:07:12:34:56 -> c4:04:15:29:cd:2e reason 3: Deauthenticated because sending stat ion is leaving (or has left) the IBSS or ESS [frame: a0 00 00 00 c4 04 15 29 cd 2e 00 03 07 12 34 56 c4 04 15 29 cd 2e 0 0 00 03 00] 0.000044: wlan0 (phy #0): disconnected (local request) 0.003030: phy #0: regulatory domain change: set to world roaming by the wireless core upon initialization request Thank you! Nick Shu E-mail confidentiality. -------------------------------- This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. Spirent Communications plc Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Tel No. +44 (0) 1293 767676 Fax No. +44 (0) 1293 767677 Registered in England Number 470893 Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Or if within the US, Spirent Communications, 26750 Agoura Road, Calabasas, CA, 91302, USA. Tel No. 1-818-676- 2300 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: wifi card disconnected right after assoicated with AP 2014-04-07 21:27 wifi card disconnected right after assoicated with AP Shu, Nick @ 2014-04-08 13:44 ` Kalle Valo 2014-04-08 14:20 ` Shu, Nick 0 siblings, 1 reply; 5+ messages in thread From: Kalle Valo @ 2014-04-08 13:44 UTC (permalink / raw) To: Shu, Nick; +Cc: ath10k@lists.infradead.org "Shu, Nick" <Nick.Shu@spirent.com> writes: > I'm trying to use a wifi card to associate to a access point, but got > a strange thing here. What card exactly? And what version of ath10k and the firmware? > Right after associated with AP, it disconnected from AP, the pattern repeated for: > Scan > Authentication > Association > De-authenticated > Dis-associated > I captured the frames as below, saw a "wlan0 del station <AP's MAC>", > why wlan0 do this local request? Very difficult to say based on the information you provided. How do you exactly control the STA? Using iw, wpa_supplicant, network-manager or something else? > 0.096321: wlan0 (phy #0): scan started > 2.802464: wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 > 5280 5300 5320 5500 5520 5540 5560 5580 5660 5680 5700 5745 5765 5785 5805 5825, "" > 0.008130: wlan0: new station c4:04:15:29:cd:2e > 0.000462: wlan0 (phy #0): auth c4:04:15:29:cd:2e -> 00:03:07:12:34:56 > status: 0: Successful [frame: b0 00 3c 00 00 03 07 00:03:07:12:34:56 (the default MAC address) implies that there's a problem with the calibration data. Please try with firmware 10.1.467.2-1. Do you get a proper MAC address then? Also It would be good to see both kernel logs as well as wpasupplicant debug logs. And a sniffer capture would be preferably as well. -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: wifi card disconnected right after assoicated with AP 2014-04-08 13:44 ` Kalle Valo @ 2014-04-08 14:20 ` Shu, Nick 2014-04-08 15:23 ` Kalle Valo 0 siblings, 1 reply; 5+ messages in thread From: Shu, Nick @ 2014-04-08 14:20 UTC (permalink / raw) To: Kalle Valo; +Cc: ath10k@lists.infradead.org Thanks, Kalle: I installed Ubuntu 13.10 server that has the Linux kernel 3.11 (this is what I read from the info) on my test server, it should have all driver and firmware to support the card. Card is a mini PCIe that has a QCA 9880 chip in it with 3x3 antenna configuration, made by Embedded Works. Access Point side is a Netgear AC1900 NightHawk. I set it up and using Ch153, WPA-PSK, with DHCP enabled. I'm new in Linux (worked on Windows for most time), so I'm still learning. I used "iw" and "wpa_supplicant" to control the card. I failed for scan command at the beginning (posted a message last week for help) and fixed by bring up the wlan0 interface (ip link set woan0 up). Then set net key "wpa_passphrase SSID KEY" Start wpa with command: "wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf". I actually got the card associated with the AP but couldn't get a valid IP address last Friday, so I was working on getting IP address issue. Then on Monday, I logged in to server and found the card wlan0 is up without command "ip link set ...", also the net key was remembered and auto associate to AP. So something is taking over and doing association automatically for me ( I installed metwork-manager, but never use it yet). You mentioned the card MAC is not a valid one? I though the vender should programmed a valid MAC to chip, right? I used "iw event -r -f" to monitor the debug message, do I have to enable something to get the kernel and supplicant log? Thanks! Nick -----Original Message----- From: Kalle Valo [mailto:kvalo@qca.qualcomm.com] Sent: Tuesday, April 08, 2014 8:44 AM To: Shu, Nick Cc: ath10k@lists.infradead.org Subject: Re: wifi card disconnected right after assoicated with AP "Shu, Nick" <Nick.Shu@spirent.com> writes: > I'm trying to use a wifi card to associate to a access point, but got > a strange thing here. What card exactly? And what version of ath10k and the firmware? > Right after associated with AP, it disconnected from AP, the pattern repeated for: > Scan > Authentication > Association > De-authenticated > Dis-associated > I captured the frames as below, saw a "wlan0 del station <AP's MAC>", > why wlan0 do this local request? Very difficult to say based on the information you provided. How do you exactly control the STA? Using iw, wpa_supplicant, network-manager or something else? > 0.096321: wlan0 (phy #0): scan started > 2.802464: wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 > 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 > 5280 5300 5320 5500 5520 5540 5560 5580 5660 5680 5700 5745 5765 5785 5805 5825, "" > 0.008130: wlan0: new station c4:04:15:29:cd:2e > 0.000462: wlan0 (phy #0): auth c4:04:15:29:cd:2e -> 00:03:07:12:34:56 > status: 0: Successful [frame: b0 00 3c 00 00 03 07 00:03:07:12:34:56 (the default MAC address) implies that there's a problem with the calibration data. Please try with firmware 10.1.467.2-1. Do you get a proper MAC address then? Also It would be good to see both kernel logs as well as wpasupplicant debug logs. And a sniffer capture would be preferably as well. -- Kalle Valo E-mail confidentiality. -------------------------------- This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. Spirent Communications plc Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Tel No. +44 (0) 1293 767676 Fax No. +44 (0) 1293 767677 Registered in England Number 470893 Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Or if within the US, Spirent Communications, 26750 Agoura Road, Calabasas, CA, 91302, USA. Tel No. 1-818-676- 2300 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: wifi card disconnected right after assoicated with AP 2014-04-08 14:20 ` Shu, Nick @ 2014-04-08 15:23 ` Kalle Valo 2014-04-08 16:05 ` Shu, Nick 0 siblings, 1 reply; 5+ messages in thread From: Kalle Valo @ 2014-04-08 15:23 UTC (permalink / raw) To: Shu, Nick; +Cc: ath10k@lists.infradead.org Hi Nick, "Shu, Nick" <Nick.Shu@spirent.com> writes: > I installed Ubuntu 13.10 server that has the Linux kernel 3.11 (this > is what I read from the info) on my test server, it should have all > driver and firmware to support the card. In ath10k's lifetime that's ancient. I recommend using backports to get a more recent version of ath10k: https://backports.wiki.kernel.org/index.php/Main_Page I would not even bother try debugging the issue until you have updated ath10k and the firmware. > Card is a mini PCIe that has a QCA 9880 chip in it with 3x3 antenna > configuration, made by Embedded Works. > Access Point side is a Netgear AC1900 NightHawk. I set it up and using > Ch153, WPA-PSK, with DHCP enabled. > > I'm new in Linux (worked on Windows for most time), so I'm still > learning. Unfortunately I can only help with ath10k specific issues, I do not have time to give general Linux support. But I can give you pointers and there are other forums which can help you better with those. > I used "iw" and "wpa_supplicant" to control the card. > I failed for scan command at the beginning (posted a message last week > for help) and fixed by bring up the wlan0 interface (ip link set woan0 > up). > Then set net key "wpa_passphrase SSID KEY" > Start wpa with command: "wpa_supplicant -B -D nl80211 -i wlan0 -c > /etc/wpa_supplicant.conf". > > I actually got the card associated with the AP but couldn't get a > valid IP address last Friday, so I was working on getting IP address > issue. > Then on Monday, I logged in to server and found the card wlan0 is up > without command "ip link set ...", also the net key was remembered and > auto associate to AP. > So something is taking over and doing association automatically for me > ( I installed metwork-manager, but never use it yet). If you run wpasupplicant manually you should disable network-manager, otherwise there will be problems. IIRC one issue might be that network-manager automatically disconnects you, which might be the issue you are having. > You mentioned the card MAC is not a valid one? I though the vender > should programmed a valid MAC to chip, right? Yes, the MAC address is stored in EEPROM and the firmware reads it. But older firmwares might not support newer boards and then there will be problems in reading the EEPROM. That's why I recommend using firmware 10.1.467.2-1. > I used "iw event -r -f" to monitor the debug message, do I have to > enable something to get the kernel and supplicant log? wpasupplicant has it's own debug log (-dddt) and kernel log can be read with dmesg. I recommend starting from here: http://wireless.kernel.org/en/users/Drivers/ath10k/debug http://wireless.kernel.org/en/users/Documentation/wpa_supplicant -- Kalle Valo _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: wifi card disconnected right after assoicated with AP 2014-04-08 15:23 ` Kalle Valo @ 2014-04-08 16:05 ` Shu, Nick 0 siblings, 0 replies; 5+ messages in thread From: Shu, Nick @ 2014-04-08 16:05 UTC (permalink / raw) To: Kalle Valo; +Cc: ath10k@lists.infradead.org Thanks, Kalle: Yeah, I uninstalled "network-manager" and problem solved. Now, card can associate to AP without dropping. Now problem moved to firmware related issue, I had a valid MAC from chip vendor but it appeared as a default MAC from event message and AP's connected device field. It couldn't get a valid IP address from AP's DHCP. Now, I need to work on getting new driver and firmware from backports . Thanks again Nick -----Original Message----- From: Kalle Valo [mailto:kvalo@qca.qualcomm.com] Sent: Tuesday, April 08, 2014 10:24 AM To: Shu, Nick Cc: ath10k@lists.infradead.org Subject: Re: wifi card disconnected right after assoicated with AP Hi Nick, "Shu, Nick" <Nick.Shu@spirent.com> writes: > I installed Ubuntu 13.10 server that has the Linux kernel 3.11 (this > is what I read from the info) on my test server, it should have all > driver and firmware to support the card. In ath10k's lifetime that's ancient. I recommend using backports to get a more recent version of ath10k: https://backports.wiki.kernel.org/index.php/Main_Page I would not even bother try debugging the issue until you have updated ath10k and the firmware. > Card is a mini PCIe that has a QCA 9880 chip in it with 3x3 antenna > configuration, made by Embedded Works. > Access Point side is a Netgear AC1900 NightHawk. I set it up and using > Ch153, WPA-PSK, with DHCP enabled. > > I'm new in Linux (worked on Windows for most time), so I'm still > learning. Unfortunately I can only help with ath10k specific issues, I do not have time to give general Linux support. But I can give you pointers and there are other forums which can help you better with those. > I used "iw" and "wpa_supplicant" to control the card. > I failed for scan command at the beginning (posted a message last week > for help) and fixed by bring up the wlan0 interface (ip link set woan0 > up). > Then set net key "wpa_passphrase SSID KEY" > Start wpa with command: "wpa_supplicant -B -D nl80211 -i wlan0 -c > /etc/wpa_supplicant.conf". > > I actually got the card associated with the AP but couldn't get a > valid IP address last Friday, so I was working on getting IP address > issue. > Then on Monday, I logged in to server and found the card wlan0 is up > without command "ip link set ...", also the net key was remembered and > auto associate to AP. > So something is taking over and doing association automatically for me > ( I installed metwork-manager, but never use it yet). If you run wpasupplicant manually you should disable network-manager, otherwise there will be problems. IIRC one issue might be that network-manager automatically disconnects you, which might be the issue you are having. > You mentioned the card MAC is not a valid one? I though the vender > should programmed a valid MAC to chip, right? Yes, the MAC address is stored in EEPROM and the firmware reads it. But older firmwares might not support newer boards and then there will be problems in reading the EEPROM. That's why I recommend using firmware 10.1.467.2-1. > I used "iw event -r -f" to monitor the debug message, do I have to > enable something to get the kernel and supplicant log? wpasupplicant has it's own debug log (-dddt) and kernel log can be read with dmesg. I recommend starting from here: http://wireless.kernel.org/en/users/Drivers/ath10k/debug http://wireless.kernel.org/en/users/Documentation/wpa_supplicant -- Kalle Valo E-mail confidentiality. -------------------------------- This e-mail contains confidential and / or privileged information belonging to Spirent Communications plc, its affiliates and / or subsidiaries. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution and / or the taking of any action based upon reliance on the contents of this transmission is strictly forbidden. If you have received this message in error please notify the sender by return e-mail and delete it from your system. Spirent Communications plc Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Tel No. +44 (0) 1293 767676 Fax No. +44 (0) 1293 767677 Registered in England Number 470893 Registered at Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, United Kingdom. Or if within the US, Spirent Communications, 26750 Agoura Road, Calabasas, CA, 91302, USA. Tel No. 1-818-676- 2300 _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-04-08 16:06 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-04-07 21:27 wifi card disconnected right after assoicated with AP Shu, Nick 2014-04-08 13:44 ` Kalle Valo 2014-04-08 14:20 ` Shu, Nick 2014-04-08 15:23 ` Kalle Valo 2014-04-08 16:05 ` Shu, Nick
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox