* pci-half-mini 7260 Wireless AC support 3.13 @ 2014-02-27 15:14 Tim Nelson 2014-02-27 16:04 ` Johannes Berg 0 siblings, 1 reply; 16+ messages in thread From: Tim Nelson @ 2014-02-27 15:14 UTC (permalink / raw) To: linux-wireless I am currently running a mainline ubuntu 3.13.5 lowlatency kernel with the lastest intel firmware: iwlwifi-7260-ucode-22.15.8.0.tgz Linux nix-tn 3.13.5-031305-lowlatency #201402221823 SMP PREEMPT Sat Feb 22 23:51:31 UTC 2014 i686 i686 i686 GNU/Linux I am unable to connect to the wireless AC radios on my 3702 Lightweight AP that is connected to a Cisco 5508 controller. On the controller, I do see clients hitting the AC radios on the SSID. I am only connecting to the A/N radio however at 5ghz. Is AC truly supported currently? I heard the patches for it would be applied in 3.13 but when I do a iwconfig wlan0 I only see: wlan0 IEEE 802.11abgn This leads me to believe that it's not actually supported yet. However, this could be something aesthetic with iwconfig. ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 15:14 pci-half-mini 7260 Wireless AC support 3.13 Tim Nelson @ 2014-02-27 16:04 ` Johannes Berg 2014-02-27 16:10 ` Tim Nelson 0 siblings, 1 reply; 16+ messages in thread From: Johannes Berg @ 2014-02-27 16:04 UTC (permalink / raw) To: Tim Nelson; +Cc: linux-wireless On Thu, 2014-02-27 at 10:14 -0500, Tim Nelson wrote: > I am currently running a mainline ubuntu 3.13.5 lowlatency kernel with > the lastest intel firmware: > > iwlwifi-7260-ucode-22.15.8.0.tgz > > Linux nix-tn 3.13.5-031305-lowlatency #201402221823 SMP PREEMPT Sat > Feb 22 23:51:31 UTC 2014 i686 i686 i686 GNU/Linux > > I am unable to connect to the wireless AC radios on my 3702 > Lightweight AP that is connected to a Cisco 5508 controller. On the > controller, I do see clients hitting the AC radios on the SSID. I am > only connecting to the A/N radio however at 5ghz. > > Is AC truly supported currently? I heard the patches for it would be > applied in 3.13 but when I do a iwconfig wlan0 I only see: > wlan0 IEEE 802.11abgn > > This leads me to believe that it's not actually supported yet. 11ac is definitely supported, since long before 3.13 in fact, though 11ac TX rates were only added later. > However, this could be something aesthetic with iwconfig. It's just the thing iwconfig reads not having been updated in forever... What kind of problem did you run into? We recently saw this bug pop up which might be what you're seeing: https://bugzilla.kernel.org/show_bug.cgi?id=70881 There's a fix for that on the way. johannes ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:04 ` Johannes Berg @ 2014-02-27 16:10 ` Tim Nelson 2014-02-27 16:13 ` Johannes Berg 0 siblings, 1 reply; 16+ messages in thread From: Tim Nelson @ 2014-02-27 16:10 UTC (permalink / raw) To: Johannes Berg; +Cc: linux-wireless Although it is a similar setup, no. I am able to connect on ALL radios but the AC radio's on the 3702's. I encounter no bugs, no loss of connection. However, I NEVER connect to the AC radio on the AP. I know it works due to my Nexus 5 connecting to the AC radio immediately. If the 3702 saw that my adapter was AC capable, it would use the AC radio and not the A/N. Also, every other device with wireless AC connects fine without issue, even the same laptop on it's Windows 8 partition. If it is AC capable, how do I get it to connect to the AC radio's on the AP? It is entirely possible it is something Cisco/Linux related with how they communicate as well. On Thu, Feb 27, 2014 at 11:04 AM, Johannes Berg <johannes@sipsolutions.net> wrote: > On Thu, 2014-02-27 at 10:14 -0500, Tim Nelson wrote: >> I am currently running a mainline ubuntu 3.13.5 lowlatency kernel with >> the lastest intel firmware: >> >> iwlwifi-7260-ucode-22.15.8.0.tgz >> >> Linux nix-tn 3.13.5-031305-lowlatency #201402221823 SMP PREEMPT Sat >> Feb 22 23:51:31 UTC 2014 i686 i686 i686 GNU/Linux >> >> I am unable to connect to the wireless AC radios on my 3702 >> Lightweight AP that is connected to a Cisco 5508 controller. On the >> controller, I do see clients hitting the AC radios on the SSID. I am >> only connecting to the A/N radio however at 5ghz. >> >> Is AC truly supported currently? I heard the patches for it would be >> applied in 3.13 but when I do a iwconfig wlan0 I only see: >> wlan0 IEEE 802.11abgn >> >> This leads me to believe that it's not actually supported yet. > > 11ac is definitely supported, since long before 3.13 in fact, though > 11ac TX rates were only added later. > >> However, this could be something aesthetic with iwconfig. > > It's just the thing iwconfig reads not having been updated in forever... > > What kind of problem did you run into? We recently saw this bug pop up > which might be what you're seeing: > https://bugzilla.kernel.org/show_bug.cgi?id=70881 > There's a fix for that on the way. > > johannes > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:10 ` Tim Nelson @ 2014-02-27 16:13 ` Johannes Berg 2014-02-27 16:27 ` Tim Nelson 0 siblings, 1 reply; 16+ messages in thread From: Johannes Berg @ 2014-02-27 16:13 UTC (permalink / raw) To: Tim Nelson; +Cc: linux-wireless On Thu, 2014-02-27 at 11:10 -0500, Tim Nelson wrote: > Although it is a similar setup, no. I am able to connect on ALL > radios but the AC radio's on the 3702's. I encounter no bugs, no loss > of connection. However, I NEVER connect to the AC radio on the AP. I > know it works due to my Nexus 5 connecting to the AC radio > immediately. If the 3702 saw that my adapter was AC capable, it would > use the AC radio and not the A/N. Also, every other device with > wireless AC connects fine without issue, even the same laptop on it's > Windows 8 partition. All of this doesn't make a lot of sense to me. What do you even mean by "AC radio" in this context? Is there a separate SSID? BSSID? something else? > If it is AC capable, how do I get it to connect to the AC radio's on > the AP? It is entirely possible it is something Cisco/Linux related > with how they communicate as well. I don't see how the AP would be able to choose where the client connects, without maybe some CCX stuff that Linux doesn't have. johannes ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:13 ` Johannes Berg @ 2014-02-27 16:27 ` Tim Nelson 2014-02-27 16:29 ` Tim Nelson 0 siblings, 1 reply; 16+ messages in thread From: Tim Nelson @ 2014-02-27 16:27 UTC (permalink / raw) To: Johannes Berg; +Cc: linux-wireless On a Cisco 5508 controller with a lightweight AP, you can see the protocol the radio the client connects to. If they are in fact AC capable, you will see them connect to the AC radio inside the AP through the controller. While I see this with many devices, it never happens under linux. The AP has multiple radios in it. On Thu, Feb 27, 2014 at 11:13 AM, Johannes Berg <johannes@sipsolutions.net> wrote: > On Thu, 2014-02-27 at 11:10 -0500, Tim Nelson wrote: >> Although it is a similar setup, no. I am able to connect on ALL >> radios but the AC radio's on the 3702's. I encounter no bugs, no loss >> of connection. However, I NEVER connect to the AC radio on the AP. I >> know it works due to my Nexus 5 connecting to the AC radio >> immediately. If the 3702 saw that my adapter was AC capable, it would >> use the AC radio and not the A/N. Also, every other device with >> wireless AC connects fine without issue, even the same laptop on it's >> Windows 8 partition. > > All of this doesn't make a lot of sense to me. What do you even mean by > "AC radio" in this context? Is there a separate SSID? BSSID? something > else? > >> If it is AC capable, how do I get it to connect to the AC radio's on >> the AP? It is entirely possible it is something Cisco/Linux related >> with how they communicate as well. > > I don't see how the AP would be able to choose where the client > connects, without maybe some CCX stuff that Linux doesn't have. > > johannes > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:27 ` Tim Nelson @ 2014-02-27 16:29 ` Tim Nelson 2014-02-27 16:38 ` Johannes Berg 0 siblings, 1 reply; 16+ messages in thread From: Tim Nelson @ 2014-02-27 16:29 UTC (permalink / raw) To: Johannes Berg; +Cc: linux-wireless As an example, I have screenshot what you see from the controller: http://i.imgur.com/tEd701u.jpg These are clients actually associating with the AC radio inside the AP. On Thu, Feb 27, 2014 at 11:27 AM, Tim Nelson <tim.l.nelson@gmail.com> wrote: > On a Cisco 5508 controller with a lightweight AP, you can see the > protocol the radio the client connects to. If they are in fact AC > capable, you will see them connect to the AC radio inside the AP > through the controller. While I see this with many devices, it never > happens under linux. The AP has multiple radios in it. > > On Thu, Feb 27, 2014 at 11:13 AM, Johannes Berg > <johannes@sipsolutions.net> wrote: >> On Thu, 2014-02-27 at 11:10 -0500, Tim Nelson wrote: >>> Although it is a similar setup, no. I am able to connect on ALL >>> radios but the AC radio's on the 3702's. I encounter no bugs, no loss >>> of connection. However, I NEVER connect to the AC radio on the AP. I >>> know it works due to my Nexus 5 connecting to the AC radio >>> immediately. If the 3702 saw that my adapter was AC capable, it would >>> use the AC radio and not the A/N. Also, every other device with >>> wireless AC connects fine without issue, even the same laptop on it's >>> Windows 8 partition. >> >> All of this doesn't make a lot of sense to me. What do you even mean by >> "AC radio" in this context? Is there a separate SSID? BSSID? something >> else? >> >>> If it is AC capable, how do I get it to connect to the AC radio's on >>> the AP? It is entirely possible it is something Cisco/Linux related >>> with how they communicate as well. >> >> I don't see how the AP would be able to choose where the client >> connects, without maybe some CCX stuff that Linux doesn't have. >> >> johannes >> ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:29 ` Tim Nelson @ 2014-02-27 16:38 ` Johannes Berg 2014-02-27 16:41 ` Tim Nelson 0 siblings, 1 reply; 16+ messages in thread From: Johannes Berg @ 2014-02-27 16:38 UTC (permalink / raw) To: Tim Nelson; +Cc: linux-wireless On Thu, 2014-02-27 at 11:29 -0500, Tim Nelson wrote: > As an example, I have screenshot what you see from the controller: > > http://i.imgur.com/tEd701u.jpg > > These are clients actually associating with the AC radio inside the AP. So that doesn't really mean anything about the *radio* you're connecting to. The (probably single!) radio in the AP is simply capable of 11ac, which means it can also deal with 11n. There aren't two radios for that. What 7260 device do you have, btw? There are 11n-only versions of it, can you give me the PCI ID and/or check kernel messages (dmesg)? Or just paste the "iw list" output somewhere. johannes ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:38 ` Johannes Berg @ 2014-02-27 16:41 ` Tim Nelson 2014-02-27 16:42 ` Tim Nelson 2014-02-27 16:45 ` Johannes Berg 0 siblings, 2 replies; 16+ messages in thread From: Tim Nelson @ 2014-02-27 16:41 UTC (permalink / raw) To: Johannes Berg; +Cc: linux-wireless [ 9.299536] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 On Thu, Feb 27, 2014 at 11:38 AM, Johannes Berg <johannes@sipsolutions.net> wrote: > On Thu, 2014-02-27 at 11:29 -0500, Tim Nelson wrote: >> As an example, I have screenshot what you see from the controller: >> >> http://i.imgur.com/tEd701u.jpg >> >> These are clients actually associating with the AC radio inside the AP. > > So that doesn't really mean anything about the *radio* you're connecting > to. The (probably single!) radio in the AP is simply capable of 11ac, > which means it can also deal with 11n. There aren't two radios for that. > > What 7260 device do you have, btw? There are 11n-only versions of it, > can you give me the PCI ID and/or check kernel messages (dmesg)? Or just > paste the "iw list" output somewhere. > > johannes > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:41 ` Tim Nelson @ 2014-02-27 16:42 ` Tim Nelson 2014-02-27 16:44 ` Johannes Berg 2014-02-27 16:45 ` Johannes Berg 1 sibling, 1 reply; 16+ messages in thread From: Tim Nelson @ 2014-02-27 16:42 UTC (permalink / raw) To: Johannes Berg; +Cc: linux-wireless two 2.4-GHz/5-GHz dual-band radios, with integrated dual-band inverted-F antennas It has 2! btw ;) On Thu, Feb 27, 2014 at 11:41 AM, Tim Nelson <tim.l.nelson@gmail.com> wrote: > [ 9.299536] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band > Wireless AC 7260, REV=0x144 > > On Thu, Feb 27, 2014 at 11:38 AM, Johannes Berg > <johannes@sipsolutions.net> wrote: >> On Thu, 2014-02-27 at 11:29 -0500, Tim Nelson wrote: >>> As an example, I have screenshot what you see from the controller: >>> >>> http://i.imgur.com/tEd701u.jpg >>> >>> These are clients actually associating with the AC radio inside the AP. >> >> So that doesn't really mean anything about the *radio* you're connecting >> to. The (probably single!) radio in the AP is simply capable of 11ac, >> which means it can also deal with 11n. There aren't two radios for that. >> >> What 7260 device do you have, btw? There are 11n-only versions of it, >> can you give me the PCI ID and/or check kernel messages (dmesg)? Or just >> paste the "iw list" output somewhere. >> >> johannes >> ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:42 ` Tim Nelson @ 2014-02-27 16:44 ` Johannes Berg 0 siblings, 0 replies; 16+ messages in thread From: Johannes Berg @ 2014-02-27 16:44 UTC (permalink / raw) To: Tim Nelson; +Cc: linux-wireless On Thu, 2014-02-27 at 11:42 -0500, Tim Nelson wrote: > two 2.4-GHz/5-GHz dual-band radios, with integrated dual-band > inverted-F antennas > > It has 2! btw ;) Yeah but one is 2.4 GHz and one is 5 GHz, that doesn't mean much about the standard used (although 11ac doesn't support 2.4 GHz) johannes ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:41 ` Tim Nelson 2014-02-27 16:42 ` Tim Nelson @ 2014-02-27 16:45 ` Johannes Berg 2014-02-27 17:21 ` Tim Nelson 1 sibling, 1 reply; 16+ messages in thread From: Johannes Berg @ 2014-02-27 16:45 UTC (permalink / raw) To: Tim Nelson; +Cc: linux-wireless On Thu, 2014-02-27 at 11:41 -0500, Tim Nelson wrote: > [ 9.299536] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band > Wireless AC 7260, REV=0x144 Hm ok that should support it. Maybe it's always connecting to the 2.4 GHz one for some reason? That seems unlikely but still possible... Maybe you could get more dmesg data about the AP it selected, and the wpa_supplicant log. johannes ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 16:45 ` Johannes Berg @ 2014-02-27 17:21 ` Tim Nelson 2014-02-27 17:49 ` Tim Nelson 0 siblings, 1 reply; 16+ messages in thread From: Tim Nelson @ 2014-02-27 17:21 UTC (permalink / raw) To: Johannes Berg; +Cc: linux-wireless I see nothing at all in my dmesg when I connect to it. As well, running Ubuntu, I do not have a wpa_supplicant.log. It's not that it errors at all, in fact it works quite well. The problem lies with the fact it's not actually doing AC. Although it is doing very well with N. On Thu, Feb 27, 2014 at 11:45 AM, Johannes Berg <johannes@sipsolutions.net> wrote: > On Thu, 2014-02-27 at 11:41 -0500, Tim Nelson wrote: >> [ 9.299536] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band >> Wireless AC 7260, REV=0x144 > > Hm ok that should support it. Maybe it's always connecting to the 2.4 > GHz one for some reason? That seems unlikely but still possible... > > Maybe you could get more dmesg data about the AP it selected, and the > wpa_supplicant log. > > johannes > ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 17:21 ` Tim Nelson @ 2014-02-27 17:49 ` Tim Nelson 2014-02-27 17:54 ` Johannes Berg 0 siblings, 1 reply; 16+ messages in thread From: Tim Nelson @ 2014-02-27 17:49 UTC (permalink / raw) To: Johannes Berg; +Cc: linux-wireless Here are the logs when i set logging to informational for network-manager: Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) starting connection 'corp-public' Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> NetworkManager state is now CONNECTING Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> (wlan0): supplicant interface state: completed -> disconnected Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0/wireless): access point 'corp-public' has security, but secrets are required. Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Feb 27 12:44:38 nix-tn dbus[571]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0/wireless): connection 'corp-public' has security, and secrets exist. No new secrets needed. Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Config: added 'ssid' value 'corp-public' Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Config: added 'scan_ssid' value '1' Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Config: added 'auth_alg' value 'OPEN' Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Config: added 'psk' value '<omitted>' Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Feb 27 12:44:38 nix-tn NetworkManager[1040]: <info> Config: set interface ap_scan to 1 Feb 27 12:44:39 nix-tn wpa_supplicant[1326]: wlan0: Failed to initiate AP scan Feb 27 12:44:41 nix-tn wpa_supplicant[1326]: message repeated 2 times: [ wlan0: Failed to initiate AP scan] Feb 27 12:44:41 nix-tn wpa_supplicant[1326]: wlan0: SME: Trying to authenticate with 08:cc:68:cc:df:ab (SSID='corp-public' freq=5180 MHz) Feb 27 12:44:41 nix-tn kernel: [ 1733.272381] wlan0: authenticate with 08:cc:68:cc:df:ab Feb 27 12:44:41 nix-tn kernel: [ 1733.272390] wlan0: AP VHT information is invalid, disable VHT Feb 27 12:44:41 nix-tn kernel: [ 1733.274110] wlan0: send auth to 08:cc:68:cc:df:ab (try 1/3) Feb 27 12:44:41 nix-tn kernel: [ 1733.274997] wlan0: authenticated Feb 27 12:44:41 nix-tn wpa_supplicant[1326]: wlan0: Trying to associate with 08:cc:68:cc:df:ab (SSID='corp-public' freq=5180 MHz) Feb 27 12:44:41 nix-tn kernel: [ 1733.277165] wlan0: associate with 08:cc:68:cc:df:ab (try 1/3) Feb 27 12:44:41 nix-tn kernel: [ 1733.280564] wlan0: RX AssocResp from 08:cc:68:cc:df:ab (capab=0x11 status=0 aid=60) Feb 27 12:44:41 nix-tn wpa_supplicant[1326]: wlan0: Associated with 08:cc:68:cc:df:ab Feb 27 12:44:41 nix-tn kernel: [ 1733.281381] wlan0: associated Feb 27 12:44:41 nix-tn kernel: [ 1733.281446] cfg80211: Calling CRDA for country: US Feb 27 12:44:41 nix-tn kernel: [ 1733.286106] cfg80211: Regulatory domain changed to country: US Feb 27 12:44:41 nix-tn kernel: [ 1733.286110] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Feb 27 12:44:41 nix-tn kernel: [ 1733.286113] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) Feb 27 12:44:41 nix-tn kernel: [ 1733.286116] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) Feb 27 12:44:41 nix-tn kernel: [ 1733.286119] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Feb 27 12:44:41 nix-tn kernel: [ 1733.286121] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Feb 27 12:44:41 nix-tn kernel: [ 1733.286124] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) Feb 27 12:44:41 nix-tn kernel: [ 1733.286126] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) Feb 27 12:44:41 nix-tn kernel: [ 1733.286139] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm) Feb 27 12:44:41 nix-tn wpa_supplicant[1326]: wlan0: WPA: Key negotiation completed with 08:cc:68:cc:df:ab [PTK=CCMP GTK=CCMP] Feb 27 12:44:41 nix-tn wpa_supplicant[1326]: wlan0: CTRL-EVENT-CONNECTED - Connection to 08:cc:68:cc:df:ab completed (reauth) [id=0 id_str=] Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> (wlan0): supplicant interface state: disconnected -> associating Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'corp-public'. Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0] Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> dhclient started with pid 5596 Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Beginning IP6 addrconf. Feb 27 12:44:41 nix-tn avahi-daemon[657]: Withdrawing address record for fe80::e8b:fdff:fe32:dec6 on wlan0. Feb 27 12:44:41 nix-tn avahi-daemon[657]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::e8b:fdff:fe32:dec6. Feb 27 12:44:41 nix-tn avahi-daemon[657]: Interface wlan0.IPv6 no longer relevant for mDNS. Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Feb 27 12:44:41 nix-tn dhclient: Internet Systems Consortium DHCP Client 4.2.4 Feb 27 12:44:41 nix-tn dhclient: Copyright 2004-2012 Internet Systems Consortium. Feb 27 12:44:41 nix-tn dhclient: All rights reserved. Feb 27 12:44:41 nix-tn dhclient: For info, please visit https://www.isc.org/software/dhcp/ Feb 27 12:44:41 nix-tn dhclient: Feb 27 12:44:41 nix-tn dhclient: /var/lib/NetworkManager/dhclient-wlan0.conf line 21: semicolon expected. Feb 27 12:44:41 nix-tn dhclient: prepend domain-name-servers 8.8.8.8 172. Feb 27 12:44:41 nix-tn dhclient: ^ Feb 27 12:44:41 nix-tn dhclient: /var/lib/NetworkManager/dhclient-wlan0.conf line 21: expecting a statement. Feb 27 12:44:41 nix-tn dhclient: prepend domain-name-servers 8.8.8.8 172.22.227.70; Feb 27 12:44:41 nix-tn dhclient: ^ Feb 27 12:44:41 nix-tn dhclient: /var/lib/NetworkManager/dhclient-wlan0.conf line 55: semicolon expected. Feb 27 12:44:41 nix-tn dhclient: send Feb 27 12:44:41 nix-tn dhclient: ^ Feb 27 12:44:41 nix-tn dhclient: Listening on LPF/wlan0/0c:8b:fd:32:de:c6 Feb 27 12:44:41 nix-tn dhclient: Sending on LPF/wlan0/0c:8b:fd:32:de:c6 Feb 27 12:44:41 nix-tn dhclient: Sending on Socket/fallback Feb 27 12:44:41 nix-tn dhclient: DHCPREQUEST of 192.168.67.41 on wlan0 to 255.255.255.255 port 67 (xid=0x4bc14984) Feb 27 12:44:41 nix-tn NetworkManager[1040]: <info> (wlan0): DHCPv4 state changed nbi -> preinit Feb 27 12:44:43 nix-tn avahi-daemon[657]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::e8b:fdff:fe32:dec6. Feb 27 12:44:43 nix-tn avahi-daemon[657]: New relevant interface wlan0.IPv6 for mDNS. Feb 27 12:44:43 nix-tn avahi-daemon[657]: Registering new address record for fe80::e8b:fdff:fe32:dec6 on wlan0.*. Feb 27 12:44:44 nix-tn dhclient: DHCPREQUEST of 192.168.67.41 on wlan0 to 255.255.255.255 port 67 (xid=0x4bc14984) Feb 27 12:44:44 nix-tn dhclient: DHCPACK of 192.168.67.41 from 1.1.1.1 Feb 27 12:44:44 nix-tn dhclient: bound to 192.168.67.41 -- renewal in 6110 seconds. Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> (wlan0): DHCPv4 state changed preinit -> reboot Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> address 192.168.67.41 Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> prefix 22 (255.255.252.0) Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> gateway 192.168.64.1 Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> nameserver '8.8.8.8' Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> nameserver '8.8.4.4' Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> nameserver '4.2.2.2' Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Feb 27 12:44:44 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started... Feb 27 12:44:44 nix-tn avahi-daemon[657]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.67.41. Feb 27 12:44:44 nix-tn avahi-daemon[657]: New relevant interface wlan0.IPv4 for mDNS. Feb 27 12:44:44 nix-tn avahi-daemon[657]: Registering new address record for 192.168.67.41 on wlan0.IPv4. Feb 27 12:44:45 nix-tn NetworkManager[1040]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0] Feb 27 12:44:45 nix-tn NetworkManager[1040]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete. Feb 27 12:44:45 nix-tn NetworkManager[1040]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0] Feb 27 12:44:45 nix-tn NetworkManager[1040]: <info> NetworkManager state is now CONNECTED_GLOBAL Feb 27 12:44:45 nix-tn NetworkManager[1040]: <info> Policy set 'corp-public' (wlan0) as default for IPv4 routing and DNS. Feb 27 12:44:45 nix-tn NetworkManager[1040]: <info> Writing DNS information to /sbin/resolvconf Feb 27 12:44:45 nix-tn dnsmasq[1819]: setting upstream servers from DBus Feb 27 12:44:45 nix-tn dnsmasq[1819]: using nameserver 4.2.2.2#53 Feb 27 12:44:45 nix-tn dnsmasq[1819]: using nameserver 8.8.4.4#53 Feb 27 12:44:45 nix-tn dnsmasq[1819]: using nameserver 8.8.8.8#53 Feb 27 12:44:45 nix-tn NetworkManager[1040]: <info> (wlan0): roamed from BSSID 08:CC:68:CC:DF:A4 (corp-public) to 08:CC:68:CC:DF:AB (corp-public) On Thu, Feb 27, 2014 at 12:21 PM, Tim Nelson <tim.l.nelson@gmail.com> wrote: > I see nothing at all in my dmesg when I connect to it. As well, > running Ubuntu, I do not have a wpa_supplicant.log. > > It's not that it errors at all, in fact it works quite well. The > problem lies with the fact it's not actually doing AC. Although it is > doing very well with N. > > On Thu, Feb 27, 2014 at 11:45 AM, Johannes Berg > <johannes@sipsolutions.net> wrote: >> On Thu, 2014-02-27 at 11:41 -0500, Tim Nelson wrote: >>> [ 9.299536] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band >>> Wireless AC 7260, REV=0x144 >> >> Hm ok that should support it. Maybe it's always connecting to the 2.4 >> GHz one for some reason? That seems unlikely but still possible... >> >> Maybe you could get more dmesg data about the AP it selected, and the >> wpa_supplicant log. >> >> johannes >> ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 17:49 ` Tim Nelson @ 2014-02-27 17:54 ` Johannes Berg 2014-02-27 17:58 ` Johannes Berg 0 siblings, 1 reply; 16+ messages in thread From: Johannes Berg @ 2014-02-27 17:54 UTC (permalink / raw) To: Tim Nelson; +Cc: linux-wireless On Thu, 2014-02-27 at 12:49 -0500, Tim Nelson wrote: > Feb 27 12:44:41 nix-tn kernel: [ 1733.272390] wlan0: AP VHT > information is invalid, disable VHT That's a clue :) johannes ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 17:54 ` Johannes Berg @ 2014-02-27 17:58 ` Johannes Berg 2014-02-27 18:31 ` Johannes Berg 0 siblings, 1 reply; 16+ messages in thread From: Johannes Berg @ 2014-02-27 17:58 UTC (permalink / raw) To: Tim Nelson; +Cc: linux-wireless On Thu, 2014-02-27 at 18:54 +0100, Johannes Berg wrote: > On Thu, 2014-02-27 at 12:49 -0500, Tim Nelson wrote: > > Feb 27 12:44:41 nix-tn kernel: [ 1733.272390] wlan0: AP VHT > > information is invalid, disable VHT > > That's a clue :) iw event -t -f would help easier for me would be iw wlan0 interface add moni0 type monitor flags none ip link set moni0 up tcpdump -i moni0 -s 0 -w /tmp/assoc.pcap and then compress/send me that file after such a failed 11ac association. If you want send it privately. johannes ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: pci-half-mini 7260 Wireless AC support 3.13 2014-02-27 17:58 ` Johannes Berg @ 2014-02-27 18:31 ` Johannes Berg 0 siblings, 0 replies; 16+ messages in thread From: Johannes Berg @ 2014-02-27 18:31 UTC (permalink / raw) To: Tim Nelson; +Cc: linux-wireless (replying to myself, Tim responded off-list) On Thu, 2014-02-27 at 18:58 +0100, Johannes Berg wrote: > iw wlan0 interface add moni0 type monitor flags none > ip link set moni0 up > tcpdump -i moni0 -s 0 -w /tmp/assoc.pcap Turns out I missed a quirk in the 11ac spec when implementing this - the channel center frequency segment 0 is reserved when the channel width is 0 (use HT). Try this change maybe: diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c index 46b62bb3677c..ca1f74bb5d50 100644 --- a/net/mac80211/mlme.c +++ b/net/mac80211/mlme.c @@ -222,6 +222,7 @@ ieee80211_determine_chantype(struct ieee80211_sub_if_data *sdata, switch (vht_oper->chan_width) { case IEEE80211_VHT_CHANWIDTH_USE_HT: vht_chandef.width = chandef->width; + vht_chandef.center_freq1 = chandef->center_freq1; break; case IEEE80211_VHT_CHANWIDTH_80MHZ: vht_chandef.width = NL80211_CHAN_WIDTH_80; johannes ^ permalink raw reply related [flat|nested] 16+ messages in thread
end of thread, other threads:[~2014-02-27 18:31 UTC | newest] Thread overview: 16+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-02-27 15:14 pci-half-mini 7260 Wireless AC support 3.13 Tim Nelson 2014-02-27 16:04 ` Johannes Berg 2014-02-27 16:10 ` Tim Nelson 2014-02-27 16:13 ` Johannes Berg 2014-02-27 16:27 ` Tim Nelson 2014-02-27 16:29 ` Tim Nelson 2014-02-27 16:38 ` Johannes Berg 2014-02-27 16:41 ` Tim Nelson 2014-02-27 16:42 ` Tim Nelson 2014-02-27 16:44 ` Johannes Berg 2014-02-27 16:45 ` Johannes Berg 2014-02-27 17:21 ` Tim Nelson 2014-02-27 17:49 ` Tim Nelson 2014-02-27 17:54 ` Johannes Berg 2014-02-27 17:58 ` Johannes Berg 2014-02-27 18:31 ` Johannes Berg
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).
