topic Re: wireless security question in Wireless

wireless security question

Bekzod — Thu, 09 May 2024 22:49:25 GMT

Hi, SSID has wpa2+wpa3 security, when pc connects which one will be used first and then if it doesnt work fails to second?

Re: wireless security question

Leo Laohoo — Fri, 10 May 2024 00:02:22 GMT

Theoretically, WPA3 will take precedence and then WPA2.

In reality, it is dependent on the wireless NIC and wireless NIC driver.

Re: wireless security question

Bekzod — Fri, 10 May 2024 15:45:41 GMT

we have macbook its failing 802.1x and then passing MAB , we checked certificates are good, and he can connect to meraki which only difference is using wpa 2 while cisco ap using wpa2+wpa3 . then i saw many users were complaining with macbook to wpa 3 and thinking maybe this is the problem

Re: wireless security question

Rich R — Fri, 10 May 2024 16:11:26 GMT

- What model of WLC?
- What version of software?
Note:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvv35000
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs75741 (marked as duplicate but no reference to what bug it's a duplicate of - you'd have to ask TAC).

Also make sure device OS and drivers are fully up to date.

Re: wireless security question

Bekzod — Fri, 10 May 2024 16:27:44 GMT

wlc- 9800, version 17.9.4 , logs in ISE shows that endpoint is starting new session AAA without finishing the previous one and then fails.

Re: wireless security question

Rich R — Fri, 10 May 2024 17:10:24 GMT

Then you definitely need debugs on WLC and client at the same time and ideally OTA packet capture to understand why/where it's going wrong. Then you know whether it's an Apple or Cisco problem and raise it with the respective vendor. Do you have APSP installed on 17.9.4? (refer TAC recommended link below)

Re: wireless security question

Bekzod — Fri, 10 May 2024 17:42:05 GMT

yes, apsp was installed . will try get debugs, its not easy , he is big executive ))

thank you

Re: wireless security question

Leo Laohoo — Sat, 11 May 2024 03:31:09 GMT

Please upgrade to 17.12.3 and try again.