

- #UNIFI NOT SHOWING WIRED CLIENT ACTIVITY UPDATE#
- #UNIFI NOT SHOWING WIRED CLIENT ACTIVITY MANUAL#
- #UNIFI NOT SHOWING WIRED CLIENT ACTIVITY PRO#
This is a good thing – sites with less than 10 APs will now no longer see this bug. So, for me, 6.5.54 still shows the issue (which explains why, in my testing, the fault wasn’t fixed in 6.5.54). My site does have more than 10 APs assigned to the SSID concerned.
#UNIFI NOT SHOWING WIRED CLIENT ACTIVITY UPDATE#
I’ve reported it to Ubiquiti because I think they need to urgently make a further update to fix this pretty fundamental bug, and hopefully they’ll indeed fix it. I proved this is the issue by turning the setting back on and – bingo – instant network faults. See the screen shots below to help you find where those settings located on the UniFi Web console interface.Īs soon as I took the steps above, the UDP-Pro re-provisioned all my UniFI WiFi access points and everything started working again – printer started working perfectly, Sonos started working fine.
#UNIFI NOT SHOWING WIRED CLIENT ACTIVITY MANUAL#
I didn’t take any manual action to break the network – all I did was leave automatic OS updates turned on and a few days ago – these mysterious faults appeared. Hosts can all talk to ‘the wider Internet’ just fine, but they can’t talk to each other. When on, it is literally blocking things as fundamental as ARP broadcast packets so that IP connections can’t even be established reliably between hosts on the local network. Ii is that latter setting that is doing the damage.

Turn OFF the checkbox called “Block LAN to WLAN Multicast and Broadcast Traffic” on the Settings->Wireless Networks-> -> EDIT WIRELESS NETWORK page.This is necessary in order to unlock the ability to change the next setting Turn OFF the ‘AUTO OPTIMIZE NETWORK’ setting under the Settings->Site menu.Since it seemed to be impacting broadcast and multicast frames, I started looking for, and adjusting settings related to that functionality in the UDM-Pro. Eventually, via various network diagnostic steps, I figured out that a strange network failure mode was the real issue. I started digging deeper, with that new data point (that it wasn’t actually the printer at fault). It was something far more fundamental about the network. In the meantime, we actually went and bought a new printer! When I fired that up, it failed to work as well (!). I didn’t initially register the timing coincidence with the printer fault because, frankly, Sonos network communication sometimes get flakey ‘all by itself’…and I had shelved that issue to figure out ‘later’. In a similar timeframe, the Sonos audio devices in our house also stopped working. The failure to work even on a wired connection convinced me the printer was just… b0rked, and that it was time to replace it. It didn’t work wireless-to-wireless, and it didn’t work when I tried cabling it into a switch and accessing it via wireless on my laptop. The way this first manifested was that our printer stopped working. This impacted some network nodes but not to all of them. Broken things included Multicast based protocols (such as AirPrint) and also initial connection establishment (with the ARP protocol’s broadcast frames apparently being filtered as well) The way the ‘breakage’ occurs is subtle – some, but not all, peer to peer IP traffic over the wireless LAN was being silently dropped. It took me a few days to figure out that the UniFi network was the cause of broken printer operation and also the cause of our on-site Sonos audio devices all ceasing to work.
#UNIFI NOT SHOWING WIRED CLIENT ACTIVITY PRO#
I turned on automatic software updates on the UDM-Pro a while ago, and I am presuming that the issue that has occurred here is as a result of the latest software that got auto-installed (UniFi UDM Pro Version 1.10.4 and ‘Network’ version 6.5.53). I run a moderately sized UniFi based network consisting of a UDM-Pro, 10 UniFi switches on a fibre ring, and 19 UniFI Wireless LAN access points. I’m writing this down in the hope that someone else trying to solve this issue via some random ‘Googling’ may find this article and that it may save them some time… compared to how long it took me to solve this!
