just noticed today that my mr32 to sends out an additional ssid with no name.
The only ssid which i have configured is the Net-Impact with WPA2.
Can someone tell me why i see an additional ssid with no name and WEP?
Solved! Go to Solution.
Strong recommend to reboot your APs again after you disable meshing. I disabled meshing across a couple hundred APs on a few dozen networks a few weeks ago, and about 2-3% (ish) woke up and wouldn't let devices associate reliably.
After rebooting the grumpy APs, they were fine.
It's been my experience that when you enable/disable MESHING, it automatically reboots the AP each time. Tested this on several occasions. However I have ran into a few issues with AP's not responding as well, which is why I setup my weekly AP reboots. In code 24.X, disabling MESHING was a VERY bad idea lol. It wasn't until 25.X that they fixed it so that it wouldn't cause issues (however a few still sneek in every once in a while, but it also might just be general bug and not related, who can really tell these days).
I had the APs reboot when I disabled meshing, but then a small handful wouldn't let devices associate. Had to reboot that handful a second time.