Hello! I have a very strange glitch with my RB 941. For a while it was controlled by CAPsMAN from RB 951G-2HnD. But some weeks ago, after regular update his CAP stop connecting to CAPsMAN, while CAP from second RB 951G-2HnD works without any problems. All boards was updated in one day. I hoped what it is a problem in last update and what a next update will fix it. But it’s not. For now, all boards updated to ROS v6.35 and problem dont go. I tried to disable firewall - nope. I tried downgrade ROS on RB941 to 6.33 - nope. I even tried to connect CAP from 941 to his own local CAPsMAN - nope! Attached screenshot show log on RB941 while i tried to connect to CAPsMAN on RB951 and his own. Sulking… What is it mean??
PS: and one more detail: when is CAP connection is established (from other 951) i can see 2 UDP connections from CAP on ports 5246 and 5247. But while a problem RB941 trying to connect i can see onle one: on port 5246
I`m install wireless-rep package on 941 and 951(CAPsMAN) boards. Then tried to connect CAP to 951 CAPsMAN and to local CAPsMAN. All stand for same, screenshot attached. Any ideas?
There is an issue with CAPsMAN in 6.35.
It could lockup wireless interface on CAP, if CAP looses connection to CAPsMAN on second retry, We are working on fix for that right now. For now, simple reboot will help till the next connection loss.
We had the same problem after upgrading to 6.35. Some CAPs didn’t connect and after reprovisioning the number of remote CAPs got even smaller. After downgrading to 6.32.4 (manually for 50 APs was quite a lot of work ) they operate again and connect to the CAPsMAN. Rebooting as suggested is just a short term solution till the next config change.
Downgrading to 6.32.4 don’t help, so as upgrading to 6.36rc6 and to 6.35.1. First of all i checking connection of CAP to local CAPsMAN, then to remote. No luck.
Hello! At last i have success! All problem was in cfg, but i don’t know what exactly. Tonight just upgraded to last 6.36rc10 and after that reset the configuration without restoring CFG. Revert old settings by hand and CAP is work! oO oO
Very interesting what was SO wrong in OLD cfg? Maybe it’s was just “broken”?
) they operate again and connect to the CAPsMAN. Rebooting as suggested is just a short term solution till the next config change.