UniFi flagging up adopted APs as rogue

[jthompson]

Hi all

 

Our UniFi Controller (v5.6.26) is flagging up some of our AP-AC-PROs as unknown neighbours in the Neighbouring Access Points list (i.e. rogue). These are APs which have been adopted by the controller for a while, are showing as connected, etc. in the Devices list and otherwise serving WiFi okay as far as I can tell. I'm pretty sure that earlier versions of the controller weren't flagging them up as rogue. Anyone come across this before?

[Michael]

Can't say I have; are they running the latest 3.9 firmware? And have you tried forgetting and re-adopting? Takes minutes.

[jthompson]

The APs are only running 3.7.17.5220 firmware. Another issue I'm having is getting the firmware updated, now that the controller doesn't come bundled with firmware packages. I can't get the controller to cache the firmware, and the APs aren't able to download it directly either. There are a couple of other things for me to try there still.

 

I've just gone through a forget/adopt with one of the APs, but it's still being marked as unknown in the neighbours list. I'll carry on and do a few more, to see if things start to straighten out.

[Michael]

I've had no issues. Do you use a proxy?

[BKGarry]

I've had two occurrences of this, just marked them as known, since they are unifi APs.

 

Everything is up to date, just shrugged it off as an oddity.

 

Was more fun while I was installed and all the rogue APs and SSIDs from Meru's "Virtual Cell" architecture, where it gives every client its on BSSID for allowing the controller to move the connection rather than the client.

[jthompson]

I've done a forget/adopt on two UniFi points now, and there are no more rogue AP detections events occurring. They're still listed in the neighbours list, but that's just because it's viewing log events: the "last seen" timestamp is from before the latest adoption.

 

I didn't want to just mark them as known, in case there was a deeper issue that needed sorting.

 

Yes, our controller is behind a proxy (two, in fact).

[ollyyllo]

Our controller is behind a proxy, like you the AP's can't connect so they don't update. For the time being I have been able to upgraded the firmware using the Standard SSH Method without any problems. Edited December 14, 2017 by ollyyllo

[jthompson]

Our controller is behind a proxy, like you the AP's can't connect so they don't update. For the time being I have been able to upgraded the firmware using the Standard SSH Method without any problems.

 

Brill, thanks. Will try that.