Hi

After much fiddling about, and lost time, with wAP devices and ROS upgrades
I finally manage to update to 6.35 without any issues

Now the problem is with CAPsMAN v2

The wAP is accessible, and I can connect to the network
but then a few seconds later I get disconnected,
then a few seconds later I get reconnected again,
and this goes on incessantly: on, off, on, off, ...

If configured as an individual AP the wAP devices behave properly

Anyone get these to operate correctly with CAPSsMAN ?

thanks
yann

Install a new temporary CAPsMAN v2 router in same network where the current CAPsMAN router is and start enabling/upgrading wireless-cm2 package on the CAPs. All CAPs with the v2 will connect to the new temporary CAPsMAN v2 router. After every CAP is upgraded to v2, upgrade your current CAPsMAN to v2 and then turn off the temporary CAPsMAN v2 router.

Thanks annefmoreno

I think the problem is more an issue with automatic channel selection rather than anything else

I will use CAPsMAN but configure the channel selections for each AP

CAPsMAN will still retain it's raison d'être as a centralised AP management console.

Hi
The wAP is accessible, and I can connect to the network
but then a few seconds later I get disconnected,
then a few seconds later I get reconnected again,
and this goes on incessantly: on, off, on, off, ...

We had same issue when forgot to change wAP MACs and all my wAPs left with identical MAC on LAN interfaces.