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@xxxxxxxxxxxxxxxx> 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 > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
