Ruckus R510 Slowness

[joseph_nguyen_g]

Ruckus R510 Slowness - My topology Comcast Xfinity X1 router with 1Gbps service, measuring 850Mbps as the output. This goes to a Rucker switch C12P, and the output there is 825Mbps. However, coming out of the 2 APs, even with AP to AP speedtest, its only 400Mbps. At remote location in my house, i am only getting 40Mbps. Troubleshooting with Lennar Home network specialist, everything pointed back to the 2 APs, Ruckus R510 Unleashed. What was the last known working FW version that supported full-duplex speedtest with results near max speed ~800Mbps+?

[chris_clancey]

I'd heavily recommend that you setup a main SSID which is broadcasting on 2.4/5 dual and have a separate SSID (maybe called $SSID-5) which just broadcasts on 5ghz. This will help narrow down the problems you are having and means you can have an always-fast network. Clients choose themselves if they want to use 2.4 or 5 and often make bad decisions. The AP can 'encourage' them to move but cannot force. Have you tried changing the channel width? Whats it currently set to? What devices are you testing these speeds with?

[hayward_kong]

I don’t believe it is a problem with bandsteering. It’s clearly an issue with unleashed firmware 207.10.x and iOS devices and possible other devices. It’s not just an r510 issue, but it affects r610, r710, and one reported r720. It seems to mainly affect wave 2 Unleashed APs. Going back to firmware 206.10.x seems to help.

[hayward_kong]

Again please check out the thread...
 https://forums.ruckuswireless.com/ruckuswireless/topics/slow-download-speeds-r710-unleashed

[jj_69052]

Not just wave 2, I have a pair of R500 aps and it affected them as well. I'm not going to bother testing the latest 200.7 since it looks like a wifi driver or beamflex issue and it's unlikely they would update those bits across minor revisions. I suggest you wait until 200.8 comes out then hopefully it will be fixed.

[jj_69052]

Not just wave 2, I have a pair of R500 aps and it affected them as well. I'm not going to bother testing the latest 200.7 since it looks like a wifi driver or beamflex issue and it's unlikely they would update those bits across minor revisions. I suggest you wait until 200.8 comes out then hopefully it will be fixed.