Bug 96471
| Summary: | Intel 7265 can't connect to AP of the phone and link is unstable | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | onorua (onorua) |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | ilan.peer, ilw |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://www.dropbox.com/s/uccte1ag1ohl8hh/trace.dat?dl=0 | ||
| Kernel Version: | 4.0.0-rc7 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg after fresh reboot with new kernel with enabled traces
wpa supplicant log with -dd startup argument X220 dmesg output X220 wpa_supplicant with -dd flags WPA wussplicant log disabled (hopefully) p2p WPA supplicant log without P2P old config with "new" device Connect to BB Classic All needed info with and without P2P Fix association to non P2P manager legacy AP With patch analysis |
||
can you please run the supplicant with -dd and provide its log? Clearly, the supplicant is disassociating, but I can't know why... thanks. Created attachment 173781 [details]
wpa supplicant log with -dd startup argument
Here is the requested wpa_supplicant output. Access point name of my phone is BlackBerry AP.
Hi, thanks for that. So your AP seems not to accept Intel device. Is it configured as 11n only? Your AP is buggy in a way that forces us (Intel device) to disable WMM which in turn will disable 11n. You seem not to have problems with Molochko, right? The logs seem fine when you associate to Molochko Indeed I don't have any problem with Molochko (TP-Link with 11n standard), and I do have problems with my mobile devices. The problem is that my X220 with WiFi card: 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 has connection to both of my phones without any problem. It might be possible that device request you to switch off the 11n mode for power saving reasons, it's mobile phone, and it almost impossible to get more than 56Mb/s over the air. Any way, do you mean that if access point doesn't support 11n starndard you will not connect at all? Aren't they backword compatible? (In reply to onorua from comment #4) > Indeed I don't have any problem with Molochko (TP-Link with 11n standard), > and I do have problems with my mobile devices. The problem is that my X220 > with WiFi card: > 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 > has connection to both of my phones without any problem. That's interesting. Please share the dmesg output of that. > It might be possible that device request you to switch off the 11n mode for > power saving reasons, it's mobile phone, and it almost impossible to get > more than 56Mb/s over the air. No - the AP is just buggy. > Any way, do you mean that if access point doesn't support 11n starndard you > will not connect at all? Aren't they backword compatible? We should be able to connect, but there are APs that have a setting to disallow association to stations that don't support certain features. So in order to cope with the buggy AP, we switch off many features. Note that 7265 can't associate because the AP refuses the association. Created attachment 173831 [details]
X220 dmesg output
Here is the dmesg output for x220
Created attachment 173841 [details]
X220 wpa_supplicant with -dd flags
Just to prove that my X220 has connection to AP from my BlackBerry phone.
I can't parse the frames from the log :( Can you add a monitor interface and capture the association? thanks. Sorry, I'm afraid I did not understand you. I can redo association if you need it, could you please let me know what monitor interface are you talking about? forget it. My colleague helped me and I could parse your frames :) can you please disable P2P in the supplicant? Either in the configuration file, or in the compilation. Thanks. Created attachment 174341 [details]
WPA wussplicant log disabled (hopefully) p2p
So, I've searched how to disable p2p, found some misleading information, mostly on how to enable it :) Finally I came up with following wpa.conf:
---------------------
p2p_listen_channel=0
p2p_oper_channel=0
p2p_go_intent=0
p2p_no_group_iface=0
I've executed:
sudo /sbin/wpa_supplicant -dd -f wpa_supplicant_withoutp2p.log -u -c wpa.conf -O /run/wpa_supplicant
and tried to connect to my BlackBerry AP, without success.
If I've disabled p2p incorrectly, let me know how to do it properly or if you don't know as well I'll recompile the kernel, I just have important work to do and don't want to reboot now, but if it's needed - I'll do.
Created attachment 174351 [details]
WPA supplicant log without P2P
Please ignore my previous comment, as obviously I haven't disabled P2P.
I had a time to compile wpa_supplicant version 2.4 with following config:
=======
CONFIG_BACKEND=file
CONFIG_CTRL_IFACE=y
CONFIG_DEBUG_FILE=y
CONFIG_DEBUG_SYSLOG=y
CONFIG_DEBUG_SYSLOG_FACILITY=LOG_DAEMON
CONFIG_DRIVER_NL80211=y
CONFIG_DRIVER_WEXT=y
CONFIG_DRIVER_WIRED=y
CONFIG_EAP_GTC=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_OTP=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TLS=y
CONFIG_EAP_TTLS=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_IPV6=y
CONFIG_LIBNL32=y
CONFIG_PEERKEY=y
CONFIG_PKCS12=y
CONFIG_WPS=y
CFLAGS += -I/usr/include/libnl3
CONFIG_CTRL_IFACE_DBUS=y
CONFIG_CTRL_IFACE_DBUS_NEW=y
CONFIG_CTRL_IFACE_DBUS_INTRO=y
========
and it's working now. wpa_supplicant log in debug mode is in attachment.
I think that you have disabled too much :) Can you please go back to the original configuration file that u used, and only disable CONFIG_HT_OVERRIDES and CONFIG_VHT_OVERRIDES? FWIW, in order to disable p2p, you only need to remove CONFIG_P2P, or set p2p_disabled=1 in the wlan0 configuration file. Also if possible please run trace-cmd as follows: sudo trace-cmd record -e cfg80211 -e mac80211 -e iwlwifi -e iwlwifi_data -e iwlwifi_msg I've taken apt-source wpasupplicant config, and compiled it with version 2.4 (my debian version is 2.3). Here is the config: ================== CONFIG_DRIVER_WEXT=y CONFIG_DRIVER_NL80211=y CONFIG_LIBNL32=y CONFIG_DRIVER_WIRED=y CONFIG_DRIVER_NONE=y CONFIG_IEEE8021X_EAPOL=y CONFIG_EAP_MD5=y CONFIG_EAP_MSCHAPV2=y CONFIG_EAP_TLS=y CONFIG_EAP_PEAP=y CONFIG_EAP_TTLS=y CONFIG_EAP_FAST=y CONFIG_EAP_GTC=y CONFIG_EAP_OTP=y CONFIG_EAP_SIM=y CONFIG_EAP_PSK=y CONFIG_EAP_PWD=y CONFIG_EAP_PAX=y CONFIG_EAP_LEAP=y CONFIG_EAP_AKA=y CONFIG_EAP_AKA_PRIME=y CONFIG_EAP_SAKE=y CONFIG_EAP_GPSK=y CONFIG_EAP_GPSK_SHA256=y CONFIG_EAP_TNC=y CONFIG_WPS=y CONFIG_WPS_ER=y CONFIG_WPS_REG_DISABLE_OPEN=y CONFIG_WPS_NFC=y CONFIG_EAP_IKEV2=y CONFIG_EAP_EKE=y CONFIG_PKCS12=y CONFIG_SMARTCARD=y CONFIG_PCSC=y CONFIG_HT_OVERRIDES=n CONFIG_VHT_OVERRIDES=n CONFIG_CTRL_IFACE=y CONFIG_READLINE=y CONFIG_BACKEND=file CONFIG_MAIN=main CONFIG_OS=unix CONFIG_ELOOP=eloop CONFIG_L2_PACKET=linux CONFIG_PEERKEY=y CONFIG_IEEE80211W=y CONFIG_TLS=openssl CONFIG_TLSV11=y CONFIG_TLSV12=y CONFIG_CTRL_IFACE_DBUS=y CONFIG_CTRL_IFACE_DBUS_NEW=y CONFIG_CTRL_IFACE_DBUS_INTRO=y CONFIG_IEEE80211R=y CONFIG_DEBUG_FILE=y CONFIG_DEBUG_SYSLOG=y CONFIG_DEBUG_SYSLOG_FACILITY=LOG_DAEMON CONFIG_DEBUG_LINUX_TRACING=y CONFIG_DELAYED_MIC_ERROR_REPORT=y CONFIG_IEEE80211N=y CONFIG_IEEE80211AC=y CONFIG_WNM=y CONFIG_AP=y CONFIG_P2P=y CONFIG_TDLS=y CONFIG_WIFI_DISPLAY=y CONFIG_AUTOSCAN_EXPONENTIAL=y CONFIG_AUTOSCAN_PERIODIC=y CONFIG_BGSCAN_SIMPLE=y CONFIG_IBSS_RSN=y ================== I was able to connect to my phone, please download the trace-cmd from following link (it's 8MB attachment doesn't accept it). https://www.dropbox.com/s/uccte1ag1ohl8hh/trace.dat?dl=0 Then I was curious and enabled all the options you asked me to disable, and I can connect again: https://www.dropbox.com/s/gxindon4szbrfqk/trace_with_all_enabled.dat?dl=0 Then I did recompilation of "debian" source package wpa version 2.3 and with default config I could connect as well.. I run out of ideas... maybe you can see something strange? Looking at this now. Can you go back to the original failed configuration and re-test. If it fails, send me the trace.dat + wpa_supplicant log + wpa_supplicant build configuration file. 10x :) In the first trace all seems ok. As far as I understand you device disconnected from one AP (84:db:ac:a8:e7:4a) on channel 9 and switched to another one (94:eb:cd:bf:62:d9) on channel 11. This is also the case in the 2nd trace file. I also examined the traffic captured in the 2nd trace and everything looks ok, other than the fact the the association request going out from the device does not include HT although the AP DOES indicate support for it in the beacons. This is a bit strange ... Johannes and Emmanuel pointed that the AP is publishing bad WMM parameters, and thus mac80211 disable WMM, which implies that HT is disabled as well. So this clarifies that non HT association. Created attachment 174761 [details] old config with "new" device So, it's weird because previously I could not connect to neither of my devices, and now the one which was connected already with that "limited" compilation config is able to connect, but the other one, which was never connected - still can't connect: https://www.dropbox.com/s/43w734vtzakjk3l/old_config.dat?dl=0 So it's some problem with initial connection setup, after this phase devices can connect with any of the mentioned configs. The trace file shows a successful connection to 'Putin Huilo' (with valid HT association). Same is also see in the wpa_supplicant log. FWIW, the "Blackberry AP" is not see during scan. Yes, because it's BlackBerry Classic to be connected to, my Q10 has AP name Blackberry AP, but Classic has BlackBerry Classic AP. I've tried to connect but it could not, it just "stuck" It does not seem that this ssid was configured for connection. Have a look at the wpa_supplicant log: the AP is found when scanning, but it is not selected for connection attempt as there is no matching network block. Created attachment 174771 [details] Connect to BB Classic I'm really sorry for your time, I've tried to connect, it "stuck" for some reason for minute or so without any reply and I restarted connman. Now I got error message and pressed retry several times. https://www.dropbox.com/s/di80vreuj5f3cmd/2bbclassic.dat?dl=0 AP point name you look for is: BlackBerryClassic no problem .. I'm glad to help. The log file you attached does not contain much other than scan results. From the trace file you attached I was not able to find what was wrong in the association flow. Just to be clear, this is the case where the original configuration is used. right? If so, can you please try again, but this time remove P2P_CONFIG from the wpa_supplicant configuration. Couple of notes: 1. For some reason no beacons are seen from this AP/P2P GO, only probe responses, which is strange. 2. As before, the P2P GO is publishing bad WMM parameters. 3. When you post again, please also attached dmesg and the config file that you used. Thanks. Yes, that was original config. According to wpa source package from debian repository it's: ================== CONFIG_DRIVER_WEXT=y CONFIG_DRIVER_NL80211=y CONFIG_LIBNL32=y CONFIG_DRIVER_WIRED=y CONFIG_DRIVER_NONE=y CONFIG_IEEE8021X_EAPOL=y CONFIG_EAP_MD5=y CONFIG_EAP_MSCHAPV2=y CONFIG_EAP_TLS=y CONFIG_EAP_PEAP=y CONFIG_EAP_TTLS=y CONFIG_EAP_FAST=y CONFIG_EAP_GTC=y CONFIG_EAP_OTP=y CONFIG_EAP_SIM=y CONFIG_EAP_PSK=y CONFIG_EAP_PWD=y CONFIG_EAP_PAX=y CONFIG_EAP_LEAP=y CONFIG_EAP_AKA=y CONFIG_EAP_AKA_PRIME=y CONFIG_EAP_SAKE=y CONFIG_EAP_GPSK=y CONFIG_EAP_GPSK_SHA256=y CONFIG_EAP_TNC=y CONFIG_WPS=y CONFIG_WPS_ER=y CONFIG_WPS_REG_DISABLE_OPEN=y CONFIG_WPS_NFC=y CONFIG_EAP_IKEV2=y CONFIG_EAP_EKE=y CONFIG_PKCS12=y CONFIG_SMARTCARD=y CONFIG_PCSC=y CONFIG_HT_OVERRIDES=y CONFIG_VHT_OVERRIDES=y CONFIG_CTRL_IFACE=y CONFIG_READLINE=y CONFIG_BACKEND=file CONFIG_MAIN=main CONFIG_OS=unix CONFIG_ELOOP=eloop CONFIG_L2_PACKET=linux CONFIG_PEERKEY=y CONFIG_IEEE80211W=y CONFIG_TLS=openssl CONFIG_TLSV11=y CONFIG_TLSV12=y CONFIG_CTRL_IFACE_DBUS=y CONFIG_CTRL_IFACE_DBUS_NEW=y CONFIG_CTRL_IFACE_DBUS_INTRO=y CONFIG_IEEE80211R=y CONFIG_DEBUG_FILE=y CONFIG_DEBUG_SYSLOG=y CONFIG_DEBUG_SYSLOG_FACILITY=LOG_DAEMON CONFIG_DEBUG_LINUX_TRACING=y CONFIG_DELAYED_MIC_ERROR_REPORT=y CONFIG_IEEE80211N=y CONFIG_IEEE80211AC=y CONFIG_WNM=y CONFIG_AP=y CONFIG_P2P=y CONFIG_TDLS=y CONFIG_WIFI_DISPLAY=y CONFIG_AUTOSCAN_EXPONENTIAL=y CONFIG_AUTOSCAN_PERIODIC=y CONFIG_BGSCAN_SIMPLE=y CONFIG_IBSS_RSN=y ==== Is there any wpa_supplicant debug option I can use to show you more valuable info? Can't say I understand why they chose to enable all these options, as some are clearly meant for testing. Can you retest with CONFIG_P2P=N (or just remove the line)? When running the wpa_supplicant please add the following options: -ddT (this way I could also get the wpa_supplicant logs in the trace file), and send the files I requested previously. Created attachment 174971 [details]
All needed info with and without P2P
I've executed tests with P2P enabled and without it, and created archive with 2 sets of data:
trace, wpa_supplicant.log and dmesg for you.
In short, I do have connection without P2P.
Sorry for not replying earlier .. we were on a long holiday weekend :) It is still difficult to understand why the AP in rejecting the association request, but this might due with the fact the the association request includes and P2P IE which incomplete. I'm attaching a patch to hostap (on top of the latest tip on the community hostap, but should also cleanly apply on 2.3 or 2.4). Can you please give it a try (with P2P enabled)? If this till does not work, can you try getting some logs from the blackberry phone? Created attachment 175111 [details]
Fix association to non P2P manager legacy AP
Created attachment 175541 [details]
With patch analysis
Sorry for the delayed reply, had really busy week and I needed to have my mobile hotspot working :)
So, I've compiled 2.3 version after applied your patch, and I was able to connect to my mobile phone AP. Here is the data I could gather for you for analysis.
Good - I am closing the bug. Thanks. Great. Thanks for all your support and help with this bug. BTW, the patch was also sent to the hostap mainling list: http://patchwork.ozlabs.org/patch/465485/ Thank you for the help, I don't know what would I do without your help and my mobile hotspot ;) FWIW, after the patch was reviewed by hostap maintainer .. the final version for this fix is merged to hostap repository. See http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=commit;h=9b05135aa477f2c64d08bdb99062907cf767c1ea |
Created attachment 173731 [details] dmesg after fresh reboot with new kernel with enabled traces I have just received Lenovo ThinkPad X1 3 gen with network card: 04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) Currently I have kernel 4.0.0-rc7 and firmware iwlwifi-7265-12, I can't connect to any of access points provided by smartphones and I have periodic link drops on Ubnt Unify APs and TP-Link, maybe on others too, but I have these available only. What bothers me a lot is that I can't use my mobile phone (Blackberry q10 and Blackberry Classic) as access point for my new laptop. I've made trace, in accordance to wiki: trace-cmd record -e iwlwifi -e mac80211 -e cfg80211 -e iwlwifi_msg Link has been posted to "URL" field of the bug. Please let me know if you need anything else or how can I debug more.