As far as I can tell, there's no way within "attached devices" (the panel that shows all clients) to see in a mixed WPA3 + WPA2 setup which clients are connected to which -- is this correct? I'd like to separate my primary network to only WPA3 and move all legacy WPA2-only capable clients to the IoT network, but I'd like to do this logically first by seeing which are latching onto only WPA2 (needing to go onto the WPA-2 only IoT SSID), and which are on WPA-3 and can go onto the default SSID. I'm aware that I can do this by just changing my default network to WPA3 only and see which device "fall off" and won't connect... but I have >50 devices, and this would be a very rudimentary way of doing things. I read one post that talks about Netgear Insight -- but non-Pro Orbi's / devices from netgear are ineligible to use this, including my AX6000 series.
Correct. The Orbi system does not provide information about which authentication method was used for each WiFi device. The solution described will provide the desired information in a relatively short time.
It is not clear (to me) what benefit will be derived from restricting the primary WiFi connection to WPA3 while allowing the IoT network to accept WPA2. The Orbi system places devices in the primary network (wired and WiFi) and the IoT network (WiFi only) into the same IP subnet. Devices gain no additional capabilities by joining the primary network over the capabilities they have when joining the IoT network.
I would expect that nearly all of the devices connecting at 2.4G will not support WPA3.
My goal was to designate the iot network as strictly wpa2 at 2.4ghz and normal one at 5ghz only wpa3. Hoping this might resolve issues I have with traversing the house and getting stuck off WiFi for far too long before handing off and sitting in some spots where it just cycles on and off WiFi on my iphone despite being 30 feet from a satellite . I’ve tried every other option like reduced power, changing channels, moving satellites, 20/40 coexistence, rts threshold, etc.
"Desperate times call for desperate measures". No harm in trying things to see what works. I have a sense that the form of authentication has no bearing on this specific problem. Some things to consider:
The primary WiFi network always has both 2.4G and 5G active. Neither can be disabled.
IoT devices are nearly always in fixed locations (not mobile).
One key to addressing issues is to be able to reproduce them. Can you identify which specific mobile devices exhibit this frustrating behavior? Are there mobile devices which do not behave the same way? And, can you reproduce this "lack of network" behavior over and over by doing exactly the same thing?
