Sometimes the UniFi network app gets confused about the actual VLAN of a client when it's on a PPSK SSID. This is the trick where the AP assigns the VLAN of the client based on the password used by the client. I use it to allow a single SSID to host IoT devices on multiple VLANs.
Here is an example:
UniFi network is reporting these devices on the default VLAN (10.1.0.0/16) - but they are not. The Network app shows their correct IP, but shows the network field as empty when this occurs.
Proof - they are on VLAN 12 (10.12.1.84/16):
root@pve03:~# ping -c 2 Game-Room-Window-1
PING Game-Room-Window-1.home.kobres.net (10.12.1.84) 56(84) bytes of data.
64 bytes from game-room-window-1.home.kobres.net (10.12.1.84): icmp_seq=1 ttl=254 time=3.76 ms
64 bytes from game-room-window-1.home.kobres.net (10.12.1.84): icmp_seq=2 ttl=254 time=6.20 ms
--- Game-Room-Window-1.home.kobres.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 3.759/4.979/6.199/1.220 ms
root@pve03:~# ping -c 2 Game-Room-Window-2
PING Game-Room-Window-2.home.kobres.net (10.12.1.92) 56(84) bytes of data.
64 bytes from game-room-window-2.home.kobres.net (10.12.1.92): icmp_seq=1 ttl=254 time=3.01 ms
64 bytes from game-room-window-2.home.kobres.net (10.12.1.92): icmp_seq=2 ttl=254 time=3.14 ms
--- Game-Room-Window-2.home.kobres.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 3.013/3.077/3.141/0.064 ms
root@pve03:~# ping -c 2 Game-Room-Window-3
PING Game-Room-Window-3.home.kobres.net (10.12.1.122) 56(84) bytes of data.
64 bytes from game-room-window-3.home.kobres.net (10.12.1.122): icmp_seq=1 ttl=254 time=3.12 ms
64 bytes from game-room-window-3.home.kobres.net (10.12.1.122): icmp_seq=2 ttl=254 time=2.96 ms
--- Game-Room-Window-3.home.kobres.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 2.962/3.041/3.121/0.079 ms
root@pve03:~# ping -c 2 Game-Room-Window-4
PING Game-Room-Window-4.home.kobres.net (10.12.1.146) 56(84) bytes of data.
64 bytes from game-room-window-4.home.kobres.net (10.12.1.146): icmp_seq=1 ttl=254 time=10.4 ms
64 bytes from game-room-window-4.home.kobres.net (10.12.1.146): icmp_seq=2 ttl=254 time=8.92 ms
--- Game-Room-Window-4.home.kobres.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 8.916/9.645/10.375/0.729 ms
If I disconnect/reconnect these clients via the Network App, the information is eventually refreshed and the warning goes away in Network Optimizer.
This is clearly a Ubiquiti bug. The consistent thing I see is that it only happens with certain PPSK hosts. It appears to be a cosmetic-only issue, as there is never any interruption to the hosts when it happens - just new recommendations popping up in NetWork optimizer.
Sometimes the UniFi network app gets confused about the actual VLAN of a client when it's on a PPSK SSID. This is the trick where the AP assigns the VLAN of the client based on the password used by the client. I use it to allow a single SSID to host IoT devices on multiple VLANs.
Here is an example:
UniFi network is reporting these devices on the default VLAN (10.1.0.0/16) - but they are not. The Network app shows their correct IP, but shows the network field as empty when this occurs.
Proof - they are on VLAN 12 (10.12.1.84/16):
If I disconnect/reconnect these clients via the Network App, the information is eventually refreshed and the warning goes away in Network Optimizer.
This is clearly a Ubiquiti bug. The consistent thing I see is that it only happens with certain PPSK hosts. It appears to be a cosmetic-only issue, as there is never any interruption to the hosts when it happens - just new recommendations popping up in NetWork optimizer.