I will test with WPA2, but I don’t use multi password anyway. So this issue is also there without multi password
Okay team I have confirmed for sure… that at least in my particular case, switching back to WPA2 completely resolved the weird VLAN problem.
I want to note something important though… I only ever had one password on the SSID. I bring it up because you mentioned a few times just to create a separate SSID for it to work. Does that mean creating a separate SSID and setting WPA3 to required, rather than “on”? Is that where the problem lies? If not, perhaps more investigation is necessary. Let me know what further tests I can do for you!
1 Like
There are many older devices that don’t support WPA3, so it could be a case that if you set it to required, it may not work with older devices, so we don’t really recommend enabling that unless it’s required in special circumstances.
It happens even if there is a single password and the VLAN is set in advanced rather than against the password.
Just had it happen here, Did have WPA3 enabled. It was just after I changed the Vlan to test something (One of my Vlans uses a different router for LAN > LAN traffic i wanted to put my wireless devices on that vlan for a mo as I suspected my other router is bottlenecking inter VLAN traffic)
Edit:
Getting vlan weridness even with WPA3 Off including some devices getting addresses from 10.88.233.x which isn’t a subnet I’d expect to find on my network.
Edit2: Looks like it’s trying to hotspot the iphone which is werid because hotspot isn’t enabled on any of the interfaces.
Hi @Alta-MattH is there any roadmap(not looking for specific time frames, just that its on the radar, which I could not determine by reading this thread) for getting support of dynamic vlan assignments on a per device basis working with WPA3?