Iam testing the new WPA3 feauture that recently comes out in ArubaOS 126.96.36.199. I have a IAP-325 in CAP mode managed by a MM. Far as i know is WPA3 backwards compatible with WPA2 devices.
I create a "next-next-finisch" SSID with WPA3-Personal.
Somebody got a idea why apple product seems to be not fall back to wpa2?
Is your Windows 10 machine an Intel Wireless Adapter?
I found that the windows 10 client is also unstable, high ping rate of 300ms and higer when connect to the HomeLab-WPA3 ssid.
When i connect back to HomeLab-WPA2 ssid, all pings are back to normal at 8ms.
Even the windows 10 Client (build 1709) WPA3 PSK is not connecting anytime in the correct way, sometimes it connects, othertime the PSK is timed-out.
Maybe iam to fast with testing this brand new feature, or maybe i missed something . But based on my first experience is that itsnt really backwards compatible to wpa2 right now.
Any body some tips or equivalent experience?
Did you ever find some resolution to the issue?
I am trying to connect my win7 laptop with the same wifi card running the latest intel drivers and cannot get connected. My iphone & adroid can both connect to the new WPA3 SSID without issue.
I am running an Ap515 v188.8.131.52 in IAP mode
I also have WPA3 backward compatibility issues:
Aruba AP-303 Firmware 184.108.40.206Client: OnePlus51. Client tries to connect to a new WPA3-Personal protected Wi-Fi network (network is shown unprotected in client);2. Client cannot connect. No probes, associations, no wireless traffic from client is available in Wi-Fi trace;3. Change network protection from WPA3-Personal to WPA2-Personal;4. Client can connect immediately (network is shown protected in client);5. Change network protection from WPA2-Personal to WPA3-Personal;6. Client stays connected. When disconnected, it can reconnect without any problems;7. Remove the known network in the client;8. Client cannot connect. No probes, associations, no wireless traffic from client is available in Wi-Fi trace;
Same issue on Canon wireless printer (MG5650)
Windows client can connect without any issues, even when its a 'new' network.
Can be a client issue, but has anybody found a solution?
I haven't seen the problems you are facing, but have had a couple of TAC cases lately, and they started by asking me if the customer was running WPA3.
This might just be a coincident, but it got me thinking at least.
If i'm informed, Aruba should post a new patch for both 8.6 and 8.5 today i was told. Remains to see if there are any changes towards WPA3.
Just tested with firmware 220.127.116.11_74786. Exactly the same behaviour.
Made a WLAN trace from the AP: not a single frame (for example probe) is seen from the client when WPA3 protection is enabled. Strange.
Will make a new trace with seperate WLAN dongles. I should see probe frames from the client, if not is should be a client issue. Will take some days, currently the needed hardware is not available.
Today made an airtrace of the authentication proces.
- Auth Key Management: PSK
- OnePlus 5 starts association and connection is succesful.
WPA3-SAE with WPA3 transition mode:
- Auth Key Management: PSK & SAE
- OnePlus 5 does not start association after probe response. Although PSK is avaible, association is not started.
WPA3 is not backwards compatible on all Wi-Fi clients!
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.