02-09-2020 02:59 AM
06-02-2020 03:30 PM
06-07-2020 01:36 AM
09-17-2021 04:56 PM
I just bought an r710 in an attempt to get a faster and more solid connection than the Ubiquiti AP I was previously connected to and, despite being closer (~3' away, on the other side of a wall, versus ~25' through ~5 walls, it's no better, and possibly worse, and the overall reach is worse than the Ubiquiti. I was excited about it based on stuff I read with people raving about Ruckus, but it's been a massive disappointment and waste of money. The absolute best speed I've been able to achieve is just under 480Mbps, and with what should be a proper/normal setup, it's between 10 and 80. I've tried multiple firmware versions (6, 8, and 10) and have tested the speed with an online speed test, SpeedFlex, and copying a file over the network.
The only thing I've found that helps is limiting it to 5GHz only, which is what allows me to get 400-480Mbps, otherwise it always uses 2.4GHz and moves extremely slow. But those speeds I'm getting on 5GHz are much, much slower than they should be, and even slower than I should get on 2.4GHz. It just doesn't make any sense, and the only conclusion I can draw at this point is that Ruckus APs are just complete junk. I wish that wasn't the case, because I was really hoping to have found a new and great one that I could use as well as recommend to others, but clearly this isn't it.
There's almost no other 5GHz traffic here, and only a small handful of 2.4GHz networks, most of which are relatively weak, so it's no an interference issue, not to mention one of the big things with Ruckus is its supposed ability to handle that with ChannelFly. If anybody has any suggestions, I'd love to hear it.
09-17-2021 10:57 PM
@s_j Did you put it into performance mode which allows use of DFS channels if you don't live near.an airport or weather station... ... not sure if your R710 Is fine but mine on average now gets about 550ish to 600mbps on an iPad Pro 2018..... Note, channel fly might take a few days to adapt. Note, don't use speedflex to check speeds unless you are checking on an AP in which you are not connected via wifi . It gives very inaccurate results on if you are wifi connected to the same AP whiing checking speed flex. Gives much different results on a different AP. Best I suggest is testing with iperf3. What kind of Wifi clients are you testing it with? You can always separate the wifi SSID for one 5ghz and one 2ghz. oh Also what are you powering it with? POE+ and have you checked if it's in 802.3at mode? Anyway if you getting on average 10-80mbps...... something is wrong... sounds like 2.4ghz connection or somehow you encountered that old speed bug which was a security fix which plagued unleashed firmware 200.7.x.x to 200.8.x.x. I haven't had that issue anymore nor more clients.
Anyway how old is your home and what kind of materials is it?
09-19-2021 03:11 PM
@hayward_kong I've tried performance and compatibility, as well as every other possible option I've found in various threads. And the issue isn't with ChannelFly taking time to adapt, because a) I've had this running for a couple weeks now, and b) there's hardly anything using 5GHz near me, and nothing at all on the frequencies it's using. Also, with regards to ChannelFly, it appears to have a serious issue, because I tried multiple times to transfer a large file over the network to test it, and every, single time it would run (slowly) for a few minutes then the connection would drop, and when it came back I'd see that the Ruckus had jumped to a different channel, despite almost the entire 5GHz spectrum being completely empty, and none of the channels it used had any other usage. So I have no idea why it was changing channels unnecessarily, or why every time it did it causes the connection to break and the file transfer to fail. If it can't happen seamlessly, then what's the point? And to add to the mess that ChannelFly apparently is, after reenabling it, it's now using one of the two small parts of the spectrum with other devices, leaving a large swatch of completely untouched channels unused. Ridiculous.
I personally believe file transfers are the best way to test the true performance of a network, and as I said, I was maxing out at ~480Mbps, and often not even getting that. It also allows for finding issues like mentioned with ChannelFly. That said, I just tested with iperf3, and it's still abysmal. Between 50-150Mbps, and the vast majority between 50-100. (Repeat tests several minutes later achieved ~150-250).
I've tested with my laptop which has an AX200 WiFi 6 adapter and is capable of Gb+ as well as my Galaxy A71.
I realize I can create two separate SSIDs, but I shouldn't have to, it should automatically use the fastest one that has a strong enough signal. And even with using 5GHz only, I'm not even getting 2.4GHz speeds.
I've tried both at and af modes (don't remember which is the preferred one found where I saw it before and that it needs to be at) and it's the same with each. When setting it to af, I get a warning that not enough power is supplied, which is interesting because I'm using a Ruckus 24V/0.5A POE injector, which is both what I read is needed, and supplies the same 24W that the label states it requires (12V/2A) for the DC adapter. So apparently yet another issue with this thing. Regardless, AFAICT based on the manual, speed isn't impacted by not having enough power, at least not on 5GHz, though it's not really clear. Also, I thought the af/at problem was going to be resolved in the .8 firmware.
The house is very old, but considering I'm ~3' from the AP with a single wall between me, unless that wall were solid steel (it's not), none of that should matter. Even so, I ran iperf with both devices in direct LOS with the AP from a few feet away in one direction and ~5' in another, and the results were the same.
Another thing I've found is that I get frequent lag when online gaming, and I ran ongoing pings with the AP, the router, the modem, and 8.8.8.8 last night to see which was was having latency spikes when the lag happened, and while there was some decent mix of which one had the issue for any given occurrence--and at least a couple occasions where the ping to the router seemed, somehow, less than that to the AP, which I have no idea how that's even possible--the majority of the issues appeared to be mainly due to high latency with the AP, which I'm guessing was because it was running so slow it was getting bottlenecked, which is just really, really bad, since that's the only thing I was doing at the time.