Ruckus Wireless as an Unifi alternative?

[tgl]

Yes, this is quite important, and is a big reason why 'WiFi extenders' often fail to provide any value (I just helped a neighbor deal with this). The 'extender' just rebroadcasts the same SSID, but is otherwise not integrated with the existing APs, so the APs and extended cannot assist the WiFi clients in making decisions about where to associate.

The same will happen with independent APs broadcasting the same SSID; they aren't aware of each other.

When a configuration with multiple integrated APs is used (for Ruckus that's Unleashed, SmartZone, etc.) then the 'controller' will help the APs configure themselves to minimize interference, maximize coverage, and assist clients as they roam around the coverage area.

Yeah. Couple of points worth noting here:

• While AP-to-client signaling for 802.11k/v is standardized, the infrastructure underlying the APs' behavior is not, and every manufacturer seems to do that their own way. This is part of why you can't put together a random set of APs and expect to get k/v roaming support.
• A lot of manufacturers do seem to use the controller as an active part of k/v behavior. I'm currently using UniFi gear, and they don't: the controller tells the APs they are siblings and then the APs do the rest. This stems from what seems to be an ancient architectural decision on Ubiquiti's part that they would not require the controller functionality to be alive 24x7. They're in the minority on that AFAIK.

 

[delamonpansie]

802.11k/v offers a much more plausible answer,

I've tried configuring this on unleashed. More often than not, 802.11k doesn't work. First, UI is misleading, it never shows any 5GHz neighbors. Second, most of the time requesting neighbors list with wpa_cli neighbor_rep_request simply fails.

 

[gigi-biji]

I've tried configuring this on unleashed. More often than not, 802.11k doesn't work. First, UI is misleading, it never shows any 5GHz neighbors. Second, most of the time requesting neighbors list with wpa_cli neighbor_rep_request simply fails.

How do you check for neighbors? I assuming something on a client, linux/windows command?

 

[delamonpansie]

How do you check for neighbors? I assuming something on a client, linux/windows command?

Two ways:
1. You can check in the Unleashed UI: "Access Points" -> Select specfic AP -> "Show AP Info" -> "Neighbor APs". Somehow it only shows 2.4GHz neighbors.
2. If you are running Linux with wpa_supplicant, you can request a neighbor list with wpa_cli neighbor_rep_request command.

 

[weeds]

I recently purchased 3 - Ruckus a750 APs.

I was able to connect to one of the APs and get it set up as an Unleashed AP and broadcasting. However, when powering up one of the other APs and trying to connect to it, it fails.

I then tried to set up the originally configured AP as a Master, then powering up the 2nd AP and letting it pick up the config from the master, but nothing happens and the Master doesn't show another AP in it's admin screen.

Both are hardwired to the same 2-jack ethernet plate in my office, so they are on the same network. Doing a LAN scan, I can see 2 Ruckus devices and their IPs, but putting that IP into the browser doesn't connect me to the admin page

What am I missing?

 

[gigi-biji]

I recently purchased 3 - Ruckus a750 APs.

I was able to connect to one of the APs and get it set up as an Unleashed AP and broadcasting. However, when powering up one of the other APs and trying to connect to it, it fails.

I then tried to set up the originally configured AP as a Master, then powering up the 2nd AP and letting it pick up the config from the master, but nothing happens and the Master doesn't show another AP in it's admin screen.

Both are hardwired to the same 2-jack ethernet plate in my office, so they are on the same network. Doing a LAN scan, I can see 2 Ruckus devices and their IPs, but putting that IP into the browser doesn't connect me to the admin page

What am I missing?

I am no expert, but check if this setting is enabled?


My experience was like this:
With pretty much default settings of WAP1 (I did updated from 200.13 to 200.15), I plugged in second wap and came back to system 10-15 minutes later. The new wap had joined and firmware was matching the first one.

 

[kpfleming]

However, when powering up one of the other APs and trying to connect to it, it fails.

Did you purchase them as 'new' or 'new in box'? If not, you'll probably need to follow the procedure to factory-reset each of them as they will have the prior owner's configuration.

 

[weeds]

Did you purchase them as 'new' or 'new in box'? If not, you'll probably need to follow the procedure to factory-reset each of them as they will have the prior owner's configuration.

They were purchased "used", so I wouldn't consider them "new in box". However, I've reset them back to factory settings multiple times.

 

[weeds]

I am no expert, but check if this setting is enabled?
View attachment 43168

My experience was like this:
With pretty much default settings of WAP1 (I did updated from 200.13 to 200.15), I plugged in second wap and came back to system 10-15 minutes later. The new wap had joined and firmware was matching the first one.

Confirmed I have that box checked.....