This AP ran fine for years always updated with some versions behind of latest stable ROS (and firmware upgraded)
rb532a has two cards, one for AP in AP-bridge mode, one as BH as station.
No WDS, no nstreme.
A month ago installed v4.16 with nv2 package but radio working in normal 802.11 ("unspecified") since some clients are ubnt.
Since then one very close proximity nanostation irregulad disconnected.
Tried all kind of configs but disconnect problem didn't dissapear.
Upgraded rb532A to v5.0.rc10 and later rc11 and also updated all MT clients to same.
Discovered now ping times to clients are very high at times. With less then 500 kbps of traffic over the AP ping times could run into several hundreds up to over 1000! But only on the AP radio. Ping times on the backhaul card stayed fine..
Today changed nanostation for rb411 wit ros4.17 but ping problem was still around.
So started to play with OS versions on AP.
Tried following:
rb532A with 4.16 normal wireless package >>>> normal pings on all clients (1-10ms)
rb532A with 5.0rc11 >>>>> very high ping times, lowest 20, highest way over 2000ms!
rb532A with 4.16 but nv2 wireless package >>> ping times all over but lowest 10, highest 2380!
rb532A with 4.17 normal wireless package >>>> normal ping times on all clients
rb532A with 4.17 nv2 wireless package >>>>> normal ping times on all clients
rb532A with 5.0rc11 >>>>> normal ping times, (1-10ms)
On each occasion the nv2 wireless was installed only, but radio(s) just work in normal 802.11 each test.
As reader (and MT) can see, the nv2 package on 4.16 is bad. Normal wireless is OK.
4.17 seems to have good nv2 package.
5.0rc11 first gave bad results for days, even after at least 3 or 4 reboots.
Only after downgrading and upgrading severeal times for thsi test purpose the last install of 5.0rc11 suddenly works normal!
So, the ATTENTION to users of 532(A) board that want to go to nv2 package:
Use either v4.17 nv2 or don't expect board to start working fine after first install of 5.0rc11....
