Network flooded and devices badly provisioned (see below) Reproducible: Didn't try Steps to Reproduce: net-wireless/unifi 5.14.17 running with all devices provisioned & working * /etc/init.d/unifi stop * emerge net-wireless/unifi 6.0.3 * /etc/init.d/unifi start * Clean reboot Actual Results: After the reboot, my 3 UniFi devices (2x AP-Pro and 1x AP-SHD) went crazy: * Network was basically flooded/unusable. For typically, as soon as I plugged one of them into a Gbit switch, nothing could talk across that switch anymore. I didn't capture a tcpdump sorry! * Looks like they were provisioned with both 2.4 and 5 GHz radios off! In short that rendered my whole LAN unusable. Took me a couple hours to find that the Unifis were the culprits. Expected Results: All devices properly provisioned and working, like with prior versions of UniFi controller Steps to resolve: * /etc/init.d/unifi stop * emerge net-wireless/unifi 5.14.17 * restore /var/lib/unifi from an earlier backup * /etc/init.d/unifi start At this point the devices immediately got reprovisioned and everything went back to normal.
Do you know if they got automatic firmware updates that came with unifi-6.0.3?
(In reply to Ben Kohler from comment #1) > Do you know if they got automatic firmware updates that came with > unifi-6.0.3? Hi Ben, I'm pretty certain that they did not, because: * I always keep Firmware auto-update disabled in the Controller settings (and indeed, it never happened automatically so far) * After the controller downgrade, the devices only got reprovisioned (no firmware up/downgrade) and the problem went away
I don't see anything specific regarding your issue in the changelog but you may still want to try 6.0.4 to see if the issue still exists there
(In reply to Ben Kohler from comment #3) > I don't see anything specific regarding your issue in the changelog but you > may still want to try 6.0.4 to see if the issue still exists there Hi Ben, Thanks for the update. I tried it as follows: * /etc/init.d/unifi stop * Backed up /var/lib/unifi * Upgraded net-wireless/unifi from 5.14.17 to 6.0.4 * No problems * Forced controller to provision one UniFi device * Mayhem!! Everything (on the network switch) was almost dead. Only way to connect to my embedded system was through the serial console * Unplugged the offending Unifi device * Network was fine again * Stopped controller, restored backup and downgraded it to 5.14.18 * /etc/init.d/unifi start (and waited for it to start) * Plugged in the UniFi device * This automatically happened: "adopting" and then "provisioning" * And everything was fine again. So in my case at least, the provisioning by controller 6.x appears to be the culprit. I would kindly suggest that you package.mask version >=6 by default, what do you think? It could happen to other people, so (imho) ~amd64 might not be sufficient. Thanks again!
If you are still experiencing this problem or able to reproduce it, can you report it upstream?
Hi Joël, I also would like to encourage you to report that problem to upstream (aka Ubiquiti), since I don't think, we can do anything here about it. I am using a couple of UniFi APs and all are provisioning and working correctly. I don't think, that this is any way realted to our package, since we are not even compiling, but only installed a bunch of files. I strongly suspect, that this would even happend with the upstream packages on Ubuntu for example. As a conclusion, I would close here for now. Conrad
Hi Conrad, Thanks for your help and apologies for the late reply. I have good news: the problem is definitely gone with 6.1.26 (and maybe also with earlier 6.1.x versions). All good now! Thanks again for maintaining this package, and all the best! :)
