It is not removed. You can run client to AP speed test using both web browser on your PC/laptop and also using Ruckus Unleashed moblie app.
On the browser,
1. Click 'Wireless Clients' bar 2. Choose the client of your interest 3. Up above, click 'More' button (next to 'Troubleshooting') 4. Under, 'More' button you will see 'Speed Test' option.
On the mobile app, on the dashboard, upper right corner you have three lines. Once you tap those lines it will take you to the next page where you will see 'Troubleshoot' as an option. Inside that 'Troubleshoot' option you will see 'SpeedFlex' option to run the speed test. Pl note that 'SpeedFlex' is Ruckus trademark.
Hi. That isn't the same as the reported speed by the client, and it interrupts WiFi. It should be simple to add. Can I make a feature request? As mentioned, this is available on anything from a Linksys to a D-Link so I don't know why Ruckus doesn't have it.
What exactly is the information you're looking for. Connected speed can refer to a few different things all of varying value:
The maximum theoretical speed of the client's capabilities (for example, that it's a 2 stream 802.11ac client on a 80MHz channel therefore 867mbps)
The last MCS rate that the AP used when talking to the client (download from the client's perspective)
The last MCS rate the client used talking to the AP (upload, from the client's perspective)
IMO None of these are very useful pieces of information. #2 and #3 are instantaneous readings, and both due to Beamflex as well as how any rate control algorithm works, the AP and client are trying many different transmit speeds that may or may not correlate to actual throughput, in an attempt to find the best setting. What it shows on the screen is just one reading out of thousands of packets that could've been interchanged during the time it takes for that page to load. Not really much of a data point. #1 is somewhat useful in understanding a client's capabilities but that's also information you can get from just experience and knowing what device the customer is using.
(By the way, even if the user interface no longer has this info, there are CLI commands that can get you access to this kind of data or more. It's just whether or not it's actually useful is highly questionable in my opinion.)
Attached are examples from an ASUS and TP-Link access point. Even though it is theoretical, it helps with understanding the capability of the client and what they can do at that given dB or distance. If nothing else, it helps distinguish 802.11a from 802.11ac and 802.11g from 802.11n, not to mention general health. I don't understand why everyone else has it but not Ruckus. From the Enterprise realm, Cisco's do too, and Aruba. Attached are two examples.