WPA3 & DPSK

[richardcorso]

I have a set up of R750 running in unleashed mode on software 200.13.6.1.319.

But the moment i enable WPA3, the DPSK tab vanishes.

However, 6E APs R560 & R760 have been marketed with WPA3 & DPSK support:

Adds the power of DPSK to WPA3/SAE combining enhanced security with the flexibility and ease of use of dynamic passphrase to secure network access.

https://www.commscope.com/product-type/enterprise-networking/wireless-access-points/indoor/r560/

RUCKUS Networks is also adding support for the WPA3 security framework to RUCKUS Dynamic PSKTM (DPSK) technology, combining ease of deployment with advanced user security and control.

https://www.businesswire.com/news/home/20230119005140/en/RUCKUS-Networks-Enables-Multi-Dwelling-Unit...

Will the support extend to older AP model R750 as well, which does not have a 6GHz radio?

Will it be available in the unleashed variants or i need to invest in new management platform?

Thanks in advance.

[Ayush_Tripathi]

Hello @richardcorso 

In unleashed 200.13 firmware version WPA3+DPSK is not supported.

R760 and R560 are the new model APs and as of now there is no any unleashed firmware version for these APs.

Also checked in the new SmartZone firmware version 6.1.1 and 6.1.0.9204 and it is also not supported WPA3 with DPSK.

We will check and let you know in which release this feature is supported.

[Rucky860]

Any update here? Specifically, for Ruckus One? 

[srichards0101]

HOW in the world are you doing this? The VERY NATURE of WPA3-PSK prevents multiple keys. How are you hacking this and I would imagine clients will not all ubiquitously support it??  More info is needed and honestly, Ruckus needs to explain themselves if they are BREAKING SECURITY protocols!!!!

[srichards0101]

OK. I found this online - https://www.youtube.com/watch?v=d4C-Sf9PoBw

1. looks like you're using an onboarding app of some kind here. This is really coy from Ruckus...not mentioning that in the press release trying to advance some revenue sales. Not a fan of withholding this important bit of info
2. Looks like you initially joining the client as a WPA2 client...then moving into this app...then re-associating as a WPA3 client probably getting around the first and only SAE PW attempt. 

You call this "canadian patented magic"...I call it pulling the wool over customer's eyes!