Bugs in 200.16.70.325. Beware! I just downgraded.

[rajdude]

On my R550 AP, I upgraded from 200.15.6.112.54 to 200.16.7.0.325 and encountered so many issues that I downgraded. These are the issues:

• Older clients do not stay connected.

I have older clients which are 802.11b only. They no longer stay connected. They lose connection after a few hours and have to be rebooted. At the older firmware level, they were stable.

• Travel router in client mode no longer works

A TPlink travel router which I use in the client mode for a very old internet radio no longer works. DHCP passthrough stopped working. I believe this is a known issue, judging from other threads.

• TVs constantly lose connection

I have lots of Android TV devices, every few hours they lose connection for a few seconds. It is as if the AP is doing band balancing and encouraging them to connect to 5G. I turned that feature off in the R550, but the clients still lose connection. I do want those clients to use the 5G band so interference from things like my microwave oven does not happen.

I recommend stay away from 200.16.7. This has wasted hours of my time, troubleshooting, until I decided to downgrade

[gritech]

I'd avoid 200.16.7.0.402 as well.  I tried it briefly and all my clients that were present after-hours (including desktops that don't move) had very slow connections, at least looking from the Ruckus side.   Across the board in a brief run.  Ex. 866Mbps on 200.16 to 2XXMbps on 200.16.

At least this version didn't wipe all my channel configs and disable 5GHz upon upgrade.

[rajdude]

About  "...wipe all my channel configs and disable 5GHz upon upgrade." ...... that really happened? if so, wow, that is totally crazy! That tells me that I should back up my config before upgrading any firmware versions.

[gritech]

Yep...but I had a backup.  Also, when reverting to the version before an upgrade the last config from that version is still preserved so it's painless to step back.

The downside was all the time I spent resetting the channels, only to have them hold for a few min and then disappear.  And still have no 5GHz.  Per an admin post after I reverted, toggling 5GHz off and back on for the AP group would have gotten 5GHz working again.  Not sure if that included the manual channels; I never tried before the first 200.16 was pulled and I felt better to leave it alone.