I have two Ap6-Pros set up in my house. I have a very minimal setup so far. I have two SSIDs, each with a single password.
One is Rutledge-WiFi, which has a single password set to VLAN10.
One is Rutledge-IoT, which has a single password set to VLAN20.
My iPhone 14 pro max is set to use Rutledge-Wifi, along with my Apple Watch (series 6). However, they keep getting assigned an IP from my management VLAN, not VLAN10. I have attached screenshots for reference. You can see from the screenshot my phone gets a 192.168.5.XXX address, when it should be getting a 192.168.10.XXX address. These are the only two devices on Rutledge-WiFi that having this strange problem. What is even stranger, is if I disable and re-enable WiFi on the phone, I get the correct VLAN assigned to me. That is, until DHCP renews, or I leave home for a while and come back. These are not the only Apple devices… just about everything in my house is Apple. They are just the only ones having this issue…
It is worth noting that my phone is running iOS 17 Developer Preview… perhaps it is something goofy going on there?
Seems like I’m having the same issues… It’s weird that it’s NOT all my devices… but only a few of them. Especially Apple products. If I run the SSIDs flat without VLANs, it all works… but add vlan in, the devices connect sporadically.
A quick update on my own experimentation. Last night I disabled “Private Wi-Fi Address” on my iPhone. This morning, my IP address is still correct. I will update this thread again this afternoon when I get home from work and let you know if the IP is still correct or not. Maybe this will help?
Another quick update… my wife’s iPhone 14 pro running non iOS beta is getting the wrong IP address this morning. She still has the “Private Wi-Fi Address” set to on, as this is the default in iOS now. Definitely something interesting going on!
@rutman286 This is very interesting. I’ll take this back to the team and see if we can replicate the issue. Thank you for bringing this to our attention!
@rutman286 We will let you know if we need anything else from you. In the meantime, just letting us know if disabling the “Private WiFi Address” helped the issue at all is more than enough. According to Apple, that setting should only change/affect the MAC address of your device. So far, we have not been able to replicate the issue but we are still doing some tests.
Sounds good Stephen. I thought initially it was probably an iOS 17 beta bug… but my wife’s phone is not on iOS 17 beta… it is on the latest iOS 16 GA.
Good morning team! I am not closer to an answer, but I am closer to giving you more exact setting to replicate the problem. It is possibly WPA3 related. Here is what I have found so far:
@rutman286 we discussed, and WPA3 is rather new, and doesn’t support Multi-Password SSIDs. If you need to use WPA3, you’ll have to create a new/separate SSID in order for it to work. Can you let us know if it continues to work with WPA2?
Excellent, we’re getting somewhere! I will keep testing with the WPA2 SSID I have set up, and let you know if it remains stable with the correct VLAN.
Just installed the AP6-Pro and I’m impressed! Just hitting the same issue, no iOS here. It seems that untagged network blends in the VLANs. I run my WiFi network on seperate VLAN and it configured as untagged to the APs. My regular LAN is VLAN 10. When changing some settings clients get IPs from the untagged network. Also saw a few times that IPv6 Router Advertisements of the untagged network gets to the clients. So having from IPv6 configured. Best fix is to restart the AP. The SSID is WPA3 if that does matter.
Welcome to the forum @OXAR! I will say for me going back to WPA2 for now seems to have solved the issue. Alta team confirmed that WPA3 does not yet support Multi-Password SSIDs, so it can be causing problems.
