I have it pretty much completely on auto because of very noisy neighboring APs. Stable so far. I may do a wireless survey with Netspot this weekend to see what things are like with these replacing the much cheaper UAP-AC-PROs I had.
Ruckus Wireless as an Unifi alternative?
- Thread starter pcmoore
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
I have used NetSpot; I really should get a GPS receiver for my laptop to be able to map precisely.
Good lord, Ekahau is expensive. Even if I had that kind of cash to throw around willy-nilly, I don't think I could convince myself to buy it for home use. If you're in the business of doing site surveys and high-end/large scale deployments, I guess $13k up front + $2k/year ongoing is fine.
Good lord, Ekahau is expensive. Even if I had that kind of cash to throw around willy-nilly, I don't think I could convince myself to buy it for home use. If you're in the business of doing site surveys and high-end/large scale deployments, I guess $13k up front + $2k/year ongoing is fine.
I thought they had a free version of their heat mapping tool but it appears that they now charge for it ...
This release closes the vulnerability I was using to region-unlock APs or add filtering licenses.
So if you buy US model APs for use elsewhere, or think you might want URL Filtering one day, then I recommend applying these patches before you upgrade to any firmware released after August 30th (e.g. 200.14.6.1.203+, 200.7.10.202.145+).
Related, the latest ZoneDirector release closes the vulnerability I was using to add licenses and support to ZD1200s.
So you'll need to apply the license patch before you apply any firmware released after August 30th (e.g. 10.2.1.0.236+, 10.5.1.0.265+).
Last edited:
I've never had problems with background scanning knocking devices off the WLAN, but I have had issues with clients not liking frequent channel changes from an AP and eventually deciding not to reconnect.
As I said in a comment above, it's possible you have interference which is causing your AP to ping-pong between 2 channels. The background scanning algo doesn't seem clever enough to detect interference in a channel before moving, or remember which channels it's previously abandoned due to interference.
seems like ruckus took it one step further than sending you a letter from counsel.
I turned off background scanning and no devices dropped off overnight! These are all based on Espressif ESP32 SOCs
Would one of the logs show when channels were changed? If channels did not change, could the act of scanning disrupt the WiFi connection?
Since all detectable APs are mine, I should do a site survey and set up static channels, dial down transmit power etc. I keep putting it off :-(
Last edited:
Unfortunately that's not how it works.
I had a choice...
I could've reported the issue, waited several months for it to be fixed, then received credit on the announcement.
There was a guy on the Ruckus forums who did that. It appears he was offered $15k in return for not disclosing a POC exploit.
But my aim was to enable US model APs to be unlocked for use elsewhere. There were a bunch of WiFi 6 APs for which the previous Aleph root exploit didn't work, so I found a new exploit & didn't report it, hoping Ruckus wouldn't notice for a long time.
Last edited:
I'm having an issue with a T710-US01...
Bought with Firmware 110.0.0.663, performed the country unlock, changed country code to Germany, upgraded to Unleashed 200.14.6.1.203 - but the Wifi doesn't work. The AP itself also doesn't show up under the AP group (where it should show up). It is completely isolated in its own network.
Did a factory reset, then downgraded to Solo 114.0.0.0.6565, confirmed that Wifi hardware works (logged in with my phone and accessed the web UI). Note: This automatically changed the country code to US.
Upgraded to Unleashed 200.14.6.1.203 again, set up a simple default config. Instead of the configured wifi it hosts the Configure.Me network??
Any idea what this could be?
Bought with Firmware 110.0.0.663, performed the country unlock, changed country code to Germany, upgraded to Unleashed 200.14.6.1.203 - but the Wifi doesn't work. The AP itself also doesn't show up under the AP group (where it should show up). It is completely isolated in its own network.
Did a factory reset, then downgraded to Solo 114.0.0.0.6565, confirmed that Wifi hardware works (logged in with my phone and accessed the web UI). Note: This automatically changed the country code to US.
Upgraded to Unleashed 200.14.6.1.203 again, set up a simple default config. Instead of the configured wifi it hosts the Configure.Me network??
Any idea what this could be?
The country unlock is just setting a config flag, so that should be out of the picture for causing the problem.
I haven't had those exact symptoms before. I usually install the same unleashed version as the rest of my APs using a direct wired connection to my PC then plug it into my switch. If it picks up a DHCP lease on the same subnet then everything is up and running.
Edited:
After another factory reset and upgrading via some other unleashed releases @NablaSquaredG is up and running. Do let me know, in the thread or a private message, if you're here after a google search because you have the same issue and an extra factory reset didn't fix it.
I haven't had those exact symptoms before. I usually install the same unleashed version as the rest of my APs using a direct wired connection to my PC then plug it into my switch. If it picks up a DHCP lease on the same subnet then everything is up and running.
Edited:
After another factory reset and upgrading via some other unleashed releases @NablaSquaredG is up and running. Do let me know, in the thread or a private message, if you're here after a google search because you have the same issue and an extra factory reset didn't fix it.
Last edited:
Ha thanks, I just wanted to give an update.
I upgraded through Unleashed 200.7.10.2.339 -> 200.10.10.5.229 -> 200.14.6.1.199 -> 200.14.6.1.203 and it somehow fixed the issue... I don't know what exactly was the issue, but I'm glad it is working now
I was able to pickup some XClaim Xi-3 APs, so I've written instructions for converting the firmware from Xi3 to R500.
Convert an XClaim Xi-3 AP to a Ruckus R500
I was a bit surprised that the XClaim internals are absolutely identical to the R500. Performance seems great, and you can't argue with the price (free, or almost).
Convert an XClaim Xi-3 AP to a Ruckus R500
I was a bit surprised that the XClaim internals are absolutely identical to the R500. Performance seems great, and you can't argue with the price (free, or almost).
Many thanks to @asuz for testing the Xclaim Xi-3 to Ruckus R500 conversion and helping me stamp out all the bugs.
I was also able to add instructions for Xclaim Xo-1 to Ruckus T300 conversion, since @asuz has one of these and didn't mind turning it into a brick to help me test (thanks!).
The Xo-1 is maybe the more useful conversion, since the T300 is an outdoor AC model which is still quite expensive.
I was also able to add instructions for Xclaim Xo-1 to Ruckus T300 conversion, since @asuz has one of these and didn't mind turning it into a brick to help me test (thanks!).
The Xo-1 is maybe the more useful conversion, since the T300 is an outdoor AC model which is still quite expensive.
Last edited:
r770
Ruckus goes wifi 7 and adds Matter/thread (though likely locked up behind $$$ licenses). Should work with unleashed as well.
Probably more notable for the potential 2nd hand r*50 APs that will hit the market as enterprise updates. Also sounds like they made additional efforts to lockdown access to the underlying OS.
Ruckus goes wifi 7 and adds Matter/thread (though likely locked up behind $$$ licenses). Should work with unleashed as well.
Probably more notable for the potential 2nd hand r*50 APs that will hit the market as enterprise updates. Also sounds like they made additional efforts to lockdown access to the underlying OS.