I have an install where there are 3 wAP ACs in a building. All 3 are set up in caps mode. All 2.4 radios have been assigned 20 mhz channels on non overlapping frequencies (1,6,11).
devices in one part of the building will suddenly “stop working”. Going into the caps-man router and looking at the log… there are messages that shows devices connecting to the radio then “sending station leaving” a few seconds later. But this will continue until the radio is rebooted or disabled/renenabled using a script.
This is really upsetting the client.
I have tried to “get around the problem” with this.
I have a netwatch pinging a wireless printer that is near the radio that keeps doing this.
When netwatch misses a ping to the printer… a script fires 5 pings at the printer. If it gets back less than 4 pings… it goes to cap and DISABLES THE 2.4 radio on that wAP AC.
Waits 3 seconds.
Then enables the radio.
Devices reconnect then the systems works for hours or days. I can’t get an exact time as one time this happend several times in an hour. Then it will sometimes not happen for what netwatch shows to be several days.
This “work around” has been effective enough, that the client is not yelling at us anymore. But I am extremely frustrated with Mikrotik.
I got a clear as day log entry that showed all devices no longer able to use the radio. Then you could see how I “toggled the radio on and off”. After which, you could see devices able to associate and use the radio again.
I generated sup files for the cap and router WHEN THE SYSTEM WAS NOT ACCEPTING CLIENTS ON THE RADIO. I sent this to support.
I also explained that this was the second wAP AC that had been put in the exact same spot and showed the EXACT SAME PROBLEM. (this points directly to the config in caps-man + radio settings being a repeatable issue.)
Several days later, I get back an email asking me to put that radio in standalone mode.
I email back with in a few hours to confirm… “you want me to take it out of caps-mode and set it up as a standalone radio with the same settings I would have if it was in caps?”
Few more days later, I get basically “yes”.
This is not trouble shooting. This is a waste of mine and the clients time… there was no reference to having even looked at the sup files for something to give me a reason to try anything. And the turn around time is not reasonable at all for random… “TRY THIS AND HOPE FOR THE BEST”.
Ticket is [Ticket#2018083022004995]
Mikrotik support. Please actually look at the sup files and give me something to work with and a reason why.
Other members… anyone have any ideas?