I started upgrading Ros 3.23 last night. In every instance I saw a drop in ccq ,connection rate and throughput.
Ack seems to be the source of the problem.
Clents that would normally sit at 56ms and are physically 3 km away are now all the way out to 488ms.
Connect rates have gone from 48/48 to 1/18
ccq’s have gone from 66/50 to 3/12.
This is consistant for every access point and for every client on those access points. exept those very close to the AP.
Customers are already calling to complain some will have to drive to work today.
My guess is that as there was a revision of the ack in 3.23 and it has not gone well.
The vast majority of my network is now MT AP’s with XR2’s and Ubiquity clients NS2’s, PS2’s, LS2’s all running AirOS 3.3.2.
In the older parts of the network where I still have realtek 8186 based gear I’m seeing the same thing as where it’s “pure” MT-UBNT.
I have been very happy for along time now with the consistant improvements in wireless performance with the later ROS versions.
So I’m sorry to have to report this but others should be warned.
Can anyone point me to the downgrade procedure ?
I can’t find it the manual or the wiki and the forum postings I have read are not clear to me.
upload the 3.22 package then go to system package and click downgrade
it should revert to 3.22
Thanks I hoped it was that simple I had never done it before.
I’m going to add that it appears that MT ros3.23-MT Ros 3.23 seems to work fine.
The problem is isolated to MT-UBNT, .*
Thanks for that last note. I will hold off on the upgrade of my MT APs that connect to any Ubiquiti stations.
I think its because of the latest RTS/CTS changes.
Having any progress with this issue? I agree that this maybe related to the return of RTS/CTS responses, how are your UBNT configurations for RTS/CTS?
I had the same problem after upgrading to V3.23, CCQ noise dived to less that 5%. I played arround with settings on the NS2 and got CCQ back to 78-100%. The images below show my new NS2 settings.
first i upgrade to 3.23 on router with cm9, but, on other side was router MT , with 3.22 UBNT card, and RX on cm9, was drop to 36mb, and not move.
I downgrade to 3.22 , and RX stiil are bad to bad
edit:
then I upgrade other side , and then other UBNT for another link, in second router, drop to 36Mbps,
then downgrade this second router to 3.22, and RX still 50-60% , then after reboot , signal go back to 100% with 3.22.
I do not dare to upgrade to 3.23, again.
Another guy said that 3.23 was the best ROS version he’s ever used with mixed bag of clients lol - what a difference in opinion… You guys should compare notes.
Scott
it makes sense because of the RTS/CTS revival, especially in a mixed environment. Anyone else with a mixed environment, point-to-multipoint have tried it?
I can’t add anything new as I downgraded everything except the one MT-MT link that I had upgraded it remains fine but I don’t have any mixed manufacturer Pt->MP that I’m willing to test this on.
This is production for me so I’ll have to wait and see what comes of this in the forums.
If it’s going to require a lot playing around with settings to get it happy I won’t do it, I have close to 200 Nano’s in the field that’s a lot work for nothing if 3.22 works fine.
This ROS rev is kicking ass - need to use RTS/CTS on UB!