Hi Guys,
it seems that since I upgraded to ROS 7.13, my CAPsMAN (RB5009) will often not show an error with one of the remote cAPs related to "no available channels". So when I look at CAPsMAN, everything looks good but in reality one of the cAPs is actually not running due to the above error message. When I look at the cAP, it tells me that the interface is managed by CAPsMAN, but there are no available channels - which Is actually what I'd like (and expect) to see on the CAPsMAN. (This has happened on cAP AX as well as wAP AC.)
Am I doing anything wrong? I seem to remember that CAPsMAN used to show a problematic status like that, but apparently no longer so. Any ideas what I might be looking at here?
(The channel might actually be blocked due to DFS, so I'm not debating the truthfulness of the error, I'm just annoyed that CAPsMAN doesn't show it.)
it seems that since I upgraded to ROS 7.13, my CAPsMAN (RB5009) will often not show an error with one of the remote cAPs related to "no available channels". So when I look at CAPsMAN, everything looks good but in reality one of the cAPs is actually not running due to the above error message. When I look at the cAP, it tells me that the interface is managed by CAPsMAN, but there are no available channels - which Is actually what I'd like (and expect) to see on the CAPsMAN. (This has happened on cAP AX as well as wAP AC.)
Am I doing anything wrong? I seem to remember that CAPsMAN used to show a problematic status like that, but apparently no longer so. Any ideas what I might be looking at here?
(The channel might actually be blocked due to DFS, so I'm not debating the truthfulness of the error, I'm just annoyed that CAPsMAN doesn't show it.)
Statistics: Posted by Smoerrebroed — Sun Jan 07, 2024 8:56 pm