Hi all, first post and contrary to other meshing questions.
I have a Unifi/PFsense network setup at a sports ground with 10 UniFi APs.
All the APS are either hard wired or connected back to a central point (PfSense in to a fibre and a Starlink inet connections) through NanoBeams. I do not want any meshing as each AP can have up to 100 users connected at a time and I want maximum throughput back to the PFSense router.
Relevant items:
Unifi version 7.4.162 (on mini PC)
UAP-nano-hd version 6.5.64
UAP-flex-hd version 6.5.64
I have meshing turned off in the UniFi network application (never been turned on with APs adopted) and both the nano and the flex are hardwired.
However the nano and flex will not stop meshing with each other. (like a couple of kids in the back seat!)
The nano usually meshes with the flex, however through my various tests, occasionally the flex may mesh with the nano. The two APs are about 25 metres apart. I have tried ‘forgetting’ them in unifi and then re-adopting them to no avail. I have tried factory defaulting them to no avail. I have tried factory resetting them, reloading the firmware, re-adopting them, (all the while the other AP is turned off). As soon as they are back in range, they hook up again!
How do I prevent this happening? It doesn’t happen to the other AP’s.
Not a problem I have encountered but I also don’t have any UnFi Nanos to test. Might want to check if there is an over ride option on the individual AP settings menu.
I am still having trouble with two AP meshing even though they are both hardwired (cable tester checked) and meshing is off globally in the Unifi controller. I have tried many supposed solutions that are posted on the web but still the same result.
I read a post where you can ssh into the ap and edit /tmp/ system.cfg.
When i go into this file I see the following paragraph:
This is despite meshing being disabled in the Unifi GUI.
I change it to "mesh.status=“disabled”, and save the file but it reverts to meshing on reboot. (considering it is in the /tmp/ directory I suppose I should have expected this to happen).
How do I prevent mesh.status from being reset to enabled?
By the way, I am on Unifi 8.3.32 now and this problem has been across several previous versions.
Have you brought this up in the UniFi forums at all? I’m not trying to drive users away from here or anything like that, but you can either create your own thread or add to an existing (FW/controller release comments, etc.) and call-out @UI-Glenn, which is their own account. They’ll want the same details you posted here.
If nothing else, they would likely like to know about this behaviour themselves.