Hi

We moved into the new house and I am unable to use the Ruckus Wifi System in the house. I am new this system and donot know how to reset this wifi access point.

Thanks Raghu

We found a tricky issue.

We were using 2 x R770 as the 1st and 2nd preferred masters, not in dedicated mode.

About 35 member APs (R370) here. If we created more than one SSID (the default one), the R370 rebooted and looped in "Kernel panic".

Moreover, if we disconnect both R770s from the PoE switch, no R370 became as a new master of Unleashed, and the whole WIFI was dead.

WE are using 200.19.7.112.238.

If we reset all APs and only put 370 to online as master and member, everything is working well.

Does anyone know how we can fix this?

For example if I want to change the password for the network how would I do that?

Thank you.

I have Purchase new Ruckus R550 and i try to configure 1st i configure that put poe cable from poe switch to Ap POE Port and from that Same Poe Switch to my laptop and i put one from ip from the same ip segment of the ruckus that is 192.168.0.122 and gateway 192.168.0.1 but it was not pinging 192.168.0.1 the default ip after that i was tryint to connect its Configure.Me. it was asking password and i checked behind there is no SSID-Password Mention it was frusted with this AP that no able to ping on lan and dont know the default ssid password can u please help me in that

how do i get into the app and the web based login to manage my network? unleashed app?

AP: Ruckus R720
Role: Master AP
Unleashed Firmware: 200.15.6.212.27
Guest SSID: Open authentication / No encryption
Guest Authentication: Enabled
Guest Access: Captive portal authentication
Additional AP: Ruckus R650, same firmware
Guest Authentication Methods:
Unique password for each guest
Single shared password among all guests

Issue Summary
We are experiencing a reproducible Guest Access authentication failure when "Allow users to reconnect without re-authentication for" (Grace Period) is enabled.

Initial Guest SSID authentication works normally. The client completes the Guest Access/captive portal process and receives network access.

However, after disconnecting from Wi-Fi and reconnecting within the configured Grace Period, the client briefly connects and then immediately disconnects.

The client does not reach DHCP and does not receive an IP address.

This is reproducible using a single AP, so it is not dependent on roaming.

Grace Period Testing
Tested Grace Period values:
10 minutes
1440 minutes
14400 minutes
43200 minutes

Grace Period Disabled
When "Allow users to reconnect without re-authentication" is disabled, the client reconnects normally and proceeds through the expected Guest Access authentication/captive portal process.

Grace Period Enabled

After the client has successfully authenticated, disconnects, and reconnects within the Grace Period:

Client associates/connects to the Guest SSID.
Client immediately disconnects.
No DHCP transaction occurs.
No IP address is assigned.
Client cannot reach the captive portal/network access stage.
If the Grace Period expires, the client can reconnect normally and authenticate again.
The same behavior occurs with both "Unique password per guest" and "Single shared password."

Client Testing

Reproduced with:

Apple iPhone
Android phone
Private/randomized MAC address
Device MAC address
The behavior is independent of client OS and MAC-address mode, making a client-specific issue unlikely.
Troubleshooting / Configuration Checks

The following were tested or eliminated as likely causes:

Restricted Subnet Access: Private IP pool entries removed during testing.
Walled Garden: Private IP pool and other relevant entries added; no change.
ACLs: No ACL applied to the AP port or relevant VLANs.
802.11r / Fast BSS Transition: Not enabled/not applicable for this Guest SSID.
802.11v: Not enabled/not shown as applicable.
802.11k: Enabled.
802.11d: Enabled.
Wireless Client Isolation: Disabled during testing; no change.
DHCP: Failure occurs before DHCP.
VLAN/ACL configuration: No change when modified/tested.
Roaming Eliminated

The issue can be reproduced using one AP only:

Connect phone to Guest SSID.
Complete Guest Access authentication.
Confirm connectivity.
Disconnect Wi-Fi.
Reconnect to the same SSID on the same AP within the Grace Period.
Client connects briefly and immediately disconnects.
Therefore, the issue does not require:
AP-to-AP roaming
Mobility between APs
Inter-AP guest-state synchronization
The issue was also reproduced between APs, but roaming is not required to trigger the failure.

R720 vs. R650 Testing

The issue is not specific to the R720.

It was reproduced on a Ruckus R650 running Unleashed 200.15.6.212.27:

R650 as part of an Unleashed deployment
R650 tested separately
The behavior remained the same.
When testing between APs in an Unleashed deployment, the issue also occurred regardless of which AP the client initially connected to or subsequently connected to.

802.11 Events

During the failed reconnect attempt, the following events are observed:

802.11 Disassociation — Reason Code 1: Unspecified
802.11 Deauthentication — Reason Code 5: Disassociation due to AP busy
802.11 Deauthentication — Reason Code 6: Received class 2 frame from non-auth STA
No DHCP transaction occurs after the failed reconnect.
Firmware Upgrade Path

The current R720-Master Unleashed cluster does not report 200.19 as an available/valid upgrade path.

Although newer Unleashed releases may exist for some Ruckus AP platforms, the R720-Master cluster reports no available upgrade to 200.19.

Therefore, upgrading to 200.19 is not currently an available remediation path for this deployment unless Ruckus confirms a supported upgrade path.

Expected Behavior

When a previously authenticated Guest Access client reconnects within the configured Grace Period, it should:

Be allowed to reconnect without re-authentication.
Remain associated.
Obtain an IP address through DHCP.
Receive normal network access according to the Guest Access configuration.
Actual Behavior
With Grace Period enabled:

Initial authentication → disconnect → reconnect within Grace Period → brief association → immediate disconnect → no DHCP/IP address.

With Grace Period disabled, or after the Grace Period expires, the client reconnects and proceeds through normal Guest Access authentication successfully.

Assessment

The failure appears specifically associated with:

Guest Access → Allow users to reconnect without re-authentication for (Grace Period)

Testing has largely eliminated:

Client OS/device-specific behavior
Private/randomized MAC addressing
Device MAC addressing
DHCP
VLAN ACLs
Walled Garden
Restricted Subnet Access
Wireless Client Isolation
AP-to-AP roaming
R720-specific hardware
A single defective AP
The failure occurs before DHCP and is reproducible across multiple client platforms and AP hardware.
Operational Impact

Due to this Guest Access Grace Period issue, we are currently using DPSK (Dynamic Pre-Shared Key) as an alternative guest-access method.

The Ruckus DPSK implementation provides a per-usage option, which is relevant to our guest-user requirements and differs from the DPSK implementation currently available in Ubiquiti UniFi.

Resolving the Guest Access Grace Period issue is therefore important for determining whether the Ruckus Guest Access workflow can meet our desired guest authentication model without requiring users to repeatedly authenticate.

Request to Ruckus / TAC

Can anyone confirm whether this is a known issue/software defect in Unleashed 200.15.6.212.27 involving:

Guest Access → Allow users to reconnect without re-authentication for (Grace Period)

Specifically:

Why is a previously authenticated Guest Access client being disconnected when reconnecting during the Grace Period instead of being permitted to reconnect without authentication?
Is this a known issue in 200.15.6.212.27?
Is there a firmware release containing a fix that is actually supported as an upgrade path for an Unleashed cluster with an R720 as Master?
Is any additional configuration required for Guest Access Grace Period functionality?
What debug commands, support logs, or packet captures are required by Ruckus TAC?
Are 802.11 Reason Codes 1, 5, and 6 expected consequences of a Guest Access Grace Period failure, or do they indicate a separate AP/client state-machine issue?
Are there known limitations with Grace Period and either:
Unique password for each guest
Single shared password among all guests?
Minimal Reproduction

Configuration:

Ruckus R720
Unleashed 200.15.6.212.27
Guest SSID: Open / No Encryption
Guest Authentication: Enabled
Captive Portal
Authentication method: Unique password per guest OR Single shared password
Grace Period: Enabled
Steps:
Connect client to Guest SSID.
Complete Guest Access authentication.
Confirm connectivity.
Disconnect Wi-Fi.
Reconnect within the configured Grace Period.
Observe brief connection followed by immediate disconnect.
Confirm that no DHCP address is obtained.

Reproduced with iPhone and Android, using both private/randomized MAC and device MAC, and on both R720 and R650 hardware.

To that end, I have already downloaded the unleased version R850_200.19.7.112.238.bl7 file.

Article number 000005720 https://support.ruckuswireless.com/articles/000005720 lists the procedure for just this, but it was last updated in March 2021.

• Is this still valid?
• The current device that I am looking to purchase was purchased in Aug 2025, and I do not know the current firmware on it.
• Does it matter what the current non unleashed firmware version is on it?

This is the first time I am dealing with Ruckus products, and I want to make sure the educated / experienced community here says that I am ok to proceed with the purchase on these grounds.

Thank you.

Root Cause:
The issue is due to the Security DNS introduced in the IOS. The new IOS versions support security DNS, but our AP's dnsspoof can work for our fixed domain Unleashed.ruckuswireless.com.  When mobile App use this domain to access the master AP, it fails.

Fix:
The issue is addressed in the latest Unleashed version 200.14.6.1.199 and with the new iOS mo
https://support.ruckuswireless.com/software/3780-ruckus-unleashed-ap-200-7-mr-refresh8-software-for-r310
bile app.
You need to upgrade the AP and the IOS app to resolve the issue.

We have also released a 200.7 MR version to fix the issue on older AP models.
Ruckus Unleashed AP 200.7 (MR Refresh8) : 200.7.10.202.145
Check out the release notes for the AP models supported.
https://support.ruckuswireless.com/software/3780-ruckus-unleashed-ap-200-7-mr-refresh8-software-for-r310

Since the mobile app is not working in order to upgrade the AP, you can use the below options to access the AP.
1. Open the browser and access the AP's IP address >> enter the admin credentials >> Upgrade the AP firmware to 200.14.6.1.199
2. Use a PC to access the AP.

Below is the complete steps for accessing the AP from PC:

1. Please connect your laptop/PC to the Unleashed SSID Or to the LAN network where the AP is connected.
2. If you are connecting to LAN, Make sure the Laptop has same IP range as AP’s.
3. Open browser and enter address https://unleashed.ruckuswireless.com Or use AP’s IP address.
4. Login with your Unleashed username and password.
   

    

5. Once successfully logged in go to Admin & Services -> Administration >> Upgrade >> Select the firmware version 200.14.6.1.199 and upgrade.
   Or, you can also use “Local Upgrade” option if you have the 200.14.6.1.199 firmware downloaded from the support site.
   
   
    
   

Regards,
Sanjay Kumar

Been using 3 Ruckus R510 AP's, latest Unleashed firmware 200.15.6.212.20.

Something i did while streaming from my phone to my Nvidia Shield gave a popup 'streaming over 2.4ghz causes slowdowns' or something along those lines.

For some reason all devices seem to only get 2.4Ghz hardly any device connects on 5Ghz? And even when a device is connected on 5Ghz the speeds are miserable. 

Yes i know 3 AP's seems a lot, i got 1 in the office, 1 in living room and 1 in bedroom. Coverage seems extreme but i also like to have a good signal outside.

On average ~20 devices are on this network, peaks up to 45.

My setup :

>Fiber 2/2Gbit. (Yes waiting for new router to do 2.5/2.5)
- Edgerouter (Hardware offloading on)
- Juniper EX4200 48T 8xPOE
- 3x R510 on POE ports. (normal use for all devices)
- 3x Ap AC lite on POE ports. (mainly iot stuff, lights, censors, cameras, switches etc overall 40 devices)

Tested on several devices from the same spot not even ~1M away from AP.

- PC - Wired Download Mbps 943.79/Upload Mbps 938.05

- OnePlus 8T 2.4Ghz (oldest phone) ~88Mbps down/58Mbps up.

- OnePlus 11 5G 5Ghz ~ 177Mbps down/100Mpbs up.
>Device info shows Link speed 702Mpbs on 5Ghz.

- OnePlus 13 2.4Ghz ~87Mbps down/63Mbps up.
>Device info shows Link speed 144Mbps on 2.4Ghz

Using the app 'Wifiman' on both the OnePlus 11 and 13 i'm connected to the same AP (same Mac address shows)
 On the OP11 it shows my SSID and both 2.4 and 5Ghz (connected) 
 On the OP13 it shows my SSD and ONLY 2.4Ghz (connected) 

. Is there a way to without creating 2 different SSID's (like: mywifi 2.4 and mywifi 5)  to 'push' the 5Ghz capable devices to 5Ghz? 

• Network connectivity issues
• Master AP election problems 
• Potential hardware failures
• Assessing controller connection status 

It's important to note that the presence and functionality of LED lights on a Ruckus AP can vary depending on the specific model and series. However, most Ruckus APs feature the following five LED indicators: PWR, CTL, AIR, 2.4G, and 5G.

PWR (Power Indicator):

Solid RED: Bootup in progress.

Flashing Green: AP firmware image booted. No routable IP received or assigned.

Solid Green: Routable IP address received.

CTL/DIR (Control/Direction Indicator):

Off: AP is a RUCKUS Unleashed member AP.

Slowly Flashing Green (every 2 sec): RUCKUS Unleashed Master AP discovery in progress.

Fast Flashing Green (twice a sec): Receiving configuration or image upgrade.

Solid Green: AP is the RUCKUS Unleashed Master.

AIR (Mesh indicator:)

Off: AP is operating in standalone or Root or non-Mesh AP        

Solid Green: AP is functioning as Mesh AP (MAP)        

Blinking Solid Green (2 Hz): AP is functioning as Mesh AP (MAP)        

Blinking Solid Green (0.5 Hz):         

2.4G (WLAN Service Indicator):

Off: The WLAN service is down.

Green: The WLAN is up, and at least one client is associated.

Amber: The WLAN is up, but no clients are associated.

5G (WLAN Service and Mesh Downlink Indicator):

Off: The WLAN service is down.

Green: The WLAN is up, and at least one client is associated. No downlink MAPs are connected.

Slow Flashing Green (one flash every two seconds): The WLAN is up, and at least one downlink MAP is connected. No clients are associated.

Fast Flashing Green (two flashes every second): The WLAN is up, at least one downlink MAP is connected, and at least one client is associated.

More info about the LEDs can be found here: https://docs.commscope.com/bundle/unleashed-200.10-troublshootingref/page/GUID-738984DA-2A47-4E71-A690-B6DF9023AA50.html

on a test system we try to integrate the pfSense captive portal into Ruckus unleashed and ran into issues.
I just explain below what we have done and what is the issue with that setup.

Maybe somebody can enlighten me.

On pfSense we have done following:

Adding a VLAN 100 on top of a physical link:

Creating a new interface GUESTNET on this VLAN with a static IPv4 address with CIDR 24:

Adding a firewall rule for the GUESTNET with full access for testing:

Enabled DHCP on GUESTNET with a range, no limitations, rest is default:

Adding a Captive Portal zone getcom_Guest_Net on interface GUESTNET with max 100 concurrent connections and a idle time of 1440 minutes, customized login page with terms and conditions and SSL enabled server name plus letsencrypt wildcard certificate:

Creation of a Voucher list:

Created a host override entry in the DNS resolver for the virtual server name:

The letsencrypt cert is working for all services and with this we have no issue here.

Cisco VLAN setup: all stacking ports/LACP ports/PoE ports for Ruckus APs are trunk ports.
VLAN 100 was added into the VLAN setup.

On Ruckus:

Created a SSID / WiFi Network with a Hotspot Service and added VLAN 100, Access Control, Radio Control, Others is default:

Hotspot Service has a redirection URL for unauthorized users to https://guestlogin.getcom.de:8003/index.php?zone=getcom_guest_net which is only reachable from VLAN 100: 

On iOS or Android client:

After selecting the new WiFi "getcom guest net" the login page is popping up, you can type in a Vouche code, accept the terms and conditions and press the login button. Then it tells you you are connected but nothing else is happening. It stays on this side. iOS and Android is telling you that you are not connected to the internet.
It looks like a name server issue, but if I connect to the pfSense I can nslookup over the GUESTNET interface.

If I check the client status it is telling me it is unauthorized:

The question is, how Ruckus unleashed is getting the information that the client is authenticated?

Thanks for reading this post...

1. Client Connection Troubleshooting

Link as reference https://docs.commscope.com/bundle/unleashed-200.16-troublshootingref/page/GUID-5BBF52D0-939D-416F-B696-FABB12AC5EE9.html

This is a demonstration for the client troubleshooting.

Select Clients, and then click the Troubleshooting button.

Figure 1: Clients Tab

Here, we can enter the MAC address of the client device in the specified format to begin troubleshooting process. If the device is already connected to the network, simply click on it, and the troubleshooting process will begin automatically.

Figure 2: Troubleshooting button.

Identify the MAC Address: Obtain the MAC address of the client device you want to analyze. Ensure you have this information handy as it will be used to filter the capture.

Input the MAC address of the client device into the designated filter.

Click the Start button to begin the troubleshooting.

In this demonstration I will use the following Mac-address for one of my Wireless clients 62:b6:b1:eb:09:89

Figure 3: Start Troubleshooting Process

Once you click Start, no data will be displayed initially because the device has not yet connected to the network or attempted to connect to any of the AP's SSIDs.

Figure 4: Troubleshooting Process

In this example, I will attempt to connect my end client to the SSID of the Access Point and intentionally use an incorrect password.

Figure 5: Initial Packet Capture View

First, we will analyze what we are observing firsthand during this test. We can identify which Access Point the end device is connecting to, the band it is using (whether 2.4 GHz or 5 GHz), and in this case, it is 5 GHz on channel 157. Additionally, we can observe the environmental SNR and the timestamp of the events according to the Access Point's log.

Now we will analyze the packets exchanged between the end client and the Access Point.

Figure 6: Analysis of Packet Exchange Between Client and Access Point

The client device initiates the connection by sending authentication and association requests, which the AP responds to. During the 4-way handshake, each attempt fails repeatedly, suggesting there is an issue. After multiple failures, the AP deauthenticates the client, ending the connection attempt.

Figure 7: Final Analysis - Client Failed Handshake

When the Information button on the error is pressed, it often provides a suggested error code and status, which can also be copied for reference. In this example, the tool indicates an "invalid passphrase" error, accurately reflecting the intentional use of an incorrect password for testing purposes. This tool is highly effective for troubleshooting connectivity issues, as it provides insights into client behavior during the authentication process, in roaming scenarios, and across various other network situations.

2.    Capturing Remote Packets

Remote packet capture enables one or more APs to operate in packet sniffer mode, allowing them to capture wireless packets on the network. These packets can either be saved locally on the device or streamed in real time to a packet analysis tool, such as Wireshark, for detailed inspection and troubleshooting. This feature is valuable for diagnosing connectivity issues and monitoring network performance by analyzing the captured packet data.

Link as reference https://docs.commscope.com/bundle/unleashed-200.16-onlinehelp/page/GUID-FE747C7C-8F63-409B-A423-63F898CA8331.html

Go to Admin & Services > Administration > Diagnostics > Packet Capture.

Figure 8: Packet capture tab

In this section, we will find the Access Points in our network, along with their model, device name, and corresponding IP address.

To troubleshoot the client connectivity issue, select the desired APs, and then choose Add to Capture. This action will move the APs to the Capture APs table.

Figure 9: Selecting the Access Point for the Packet Capture

For Radio, select either 2.4 GHz or 5 GHz/6 GHz. In this case, since we are working with a 5 GHz connection, select the 5 GHz option.

You can Select Local Mode or Streaming Mode as the capture mode:

+To capture a limited snapshot on each AP, select Local Mode.
+To stream the captured packets directly to Wireshark for real-time analysis, select Streaming Mode.

In this example we are going to select Local Mode.

In this example, since the MAC address of the problematic device is known, enter it to filter the capture data specifically for that client. Click Start to begin capturing packets. At this stage, reproduce the issue. Once the issue has been reproduced, click Stop to end the capture.

Figure 10: Initiate the Packet Capture

Then click Save to store the packet capture as a local file for later analysis.

Figure 11 : Downloaded PCAP from the Unlashed UI.

Once the file is downloaded, it will be saved in the Downloads folder. Extract the contents, and you’ll find folders containing the PCAP files. These files include detailed information on the association process for the end client , which will help you investigating if there is any incidents.

Note : Remember to remove the AP from the capture list and disable packet capture after completing this process.

By analyzing the packet exchange during the connection process, you can pinpoint where the failure occurs and take appropriate corrective actions. This method provides valuable insights into the interaction between client devices and APs in real time.

Unleashed Overview

In an Unleashed network, a RUCKUS Unleashed 'Master' Access Point acts similarly to a controller, managing all control functions. These settings are then propagated to the other APs in the network. If the Master AP go offline, a 'Member' AP will automatically take on the role of the Unleashed Master, assuming control and maintaining network operations.

Unleashed Support

-Bridge mode 128 APs and 2,048 clients.

-Gateway mode supports up to 25 APs and 512 clients.

-Dedicated Master

Overview Limitations from Zone Director

-IPv6 is not supported.

-No interface to communicate with SmartCell Insight analytics engine or SPoT location.

-No Northbound Interface to pass client authentication responsibility to an external entity.

-No WLAN groups.

What are the necessary conditions or prerequisites for an access point to successfully connect to an existing Unleashed network?

Connect the Member Access Point (AP) to the network, ensuring it is on the same VLAN as the Master AP. Upon powering up, the Member AP will engage in an election to determine if a Master already exists. It's important that the Member AP either matches or has a lower firmware version than the Master.

Additionally, it must be able to ping the Master AP and share the same country code setting.

Commands to check if a member Access Point is not joining to the Unleashed Network.

•  ping < Master_AP>
•  get version 
•  get boarddata : Display hardware version and system board information
•  get discovery-agent: Check if LLWAP protocol is enable.
• get countrycode :
• get director : show Master AP information.
• get election: shows the status of all Unleashed APs
• get syslog log

The same information can be collected on the Master AP.

• Ping <Member_IP>
• get version 
• get countrycode 
• get boarddata 
• get election 

Ruckus CLI on unleashed when SSH to the Access Points.

The 'ruckus>' CLI prompt indicates you are logged into the 'Master' Access Point. From here, you can navigate through various configuration modes to manage settings and preferences.

Enable:

ruckus#

Under enable mode we can go to different modes example:

ap-mode: Note under this mode you can run set-get commands.

ruckus(ap-mode)#

Config

ruckus(config)#

Under config there are some different modes

+Admin:

ruckus(config-admin)#

+System:

ruckus(config-sys)#

+Using the Mac-address of the AP: 

ruckus(config)# ap d4:bd:4f:01:bc:10
The AP 'd4:bd:4f:01:bc:10' has been loaded. To save the AP, type 'end' or 'exit'.
ruckus(config-ap)#

The 'rkscli:' prompt indicates that you are logged into a 'Member' Access Point. In this CLI, you can execute 'get' or 'set' commands to retrieve or configure the Access Point settings. For example:

Best Regards 

Fernando Vasquez 

I have about 10 APs R550's running the latest firmware with 4 VLANs - we want to put certain people on certain VLANs only and prevent them from logging in otherwise.   The first group is about 50 mac addresses, the second is about 100 and the third is about 25 mac addresses.

We'd really prefer to import a mac address list rather than add 175 mac addresses 1 at a time.

Anyone know a way to import the CSVs?

On Unleased AP, when we try to create the Guest SSID with Facebook login option, we get the below error when we click on "Register"
"Register guest service [Facebook] to Facebook failed.

Root Cause:
This is due to Facebook has officially announced the discontinuation of the “Facebook Wi-Fi” feature, which took  effect from June 12th, 2023.

Workaround :
We would request you to choose alternate login options available for now.

Solution :
We will be implementing Facebook Oauth 2.0, and this will be available in Unleashed 200.15.
Current ETA is set to January. I will keep the thread updated if there any change.

As compared to Unleashed bridge mode, the following features are supported in Dedicated Master mode:

• Cross-network segment networking
• Dedicated Master VLAN and AP VLAN
• Smart Redundancy
• Maximum capacity limit to 4,000 clients (compared to Unleashed bridge mode)
• Tunnel WLAN
• ZoneDirector AP migration to Unleashed network

To disable dedicated master a factory reset must be done.

Is important to highlight that this is different from setting a preferred master, as this setting is not bounded to an ap model, any other Ethernet-connected member AP can take the Master role. For more info on preferred master please visit Designating a Preferred Master AP

The moment I enabled bond the R720 rebooted and the two interfaces/slaves already added.

I then went to adjust lacp-rate + hash but doesn't appear to be available?  Why?

lacp-rate [0,1], 0 for slow, 1 for fast
xmit-hash [0,1,2], 0 for L(ayer2), 1 for L3+4, 2 for L2+3

Also the unleashed GUI / AP info still shows LACP/LAG disabled.  Why?

Thank you

------

R720 on unleashed 200.14.6.1.203

ruckus(ap-mode)# get power-mode
PoE Configured Mode : bt5
Power Consumption Status : 802.3bt5 Switch/Injector
USB Status : Disabled
OK

---

ruckus(ap-mode)# get bond bond0
LACP/Bonding is ENABLED.
<bond0>
Mode: 8023AD
LACP-rate: slow
MII-Mon: 100 (ms)
Xmit-Hash: layer2+3
Slaves: 2
Slave-0: eth0, ACTIVE, UP, link-fail-count: 1
Slave-1: eth1, ACTIVE, UP, link-fail-count: 0
OK

ruckus(ap-mode)# set bond bond0 lacp-rate 1
Error: parameter error

ruckus(ap-mode)# set bond bond0 xmit-hash 1
Error: parameter error

Root Cause:

The issue is caused due to the recent upgrade in Facebook's services, causing the RUCKUS Unleashed app to  unable to authenticate logins through Facebook accounts. Our Unleashed team is actively collaborating with Facebook to address and resolve this situation. 

Workaround:
As a workaround, customers can continue to access the system remotely using alternative options such as Google, Apple, or email accounts.

Fix:
Our team is working on the issue. Since the issue was caused by 3rd party verification, we need to go through the effort with the 3rd party and this will take some time.

I will keep the thread updated any any updates about the fix.
Your patience and understanding during this period are greatly appreciated.

Regards,
Sanjay Kumar

— Requirements:

*SSH client access (Putty on Windows, macOS command Terminal, or Linux terminal).

*Download putty for Windows computer.

https://putty.org/

*For macOS, you will use the terminal app integrated into your MAC.

Enter the next command from the MAC terminal for SSH access

Format

ssh <unleashed user>@<IP of the master Access Point>

Example

ssh admin@192.168.1.1

*Or from Windows open Putty and add the next information, then hit open

Note: the credentials for the CLI access to the master Access Point are the same credentials you used for the APP or the Web GUI

1: Using your SSH client application such as a putty or MAC terminal, gain access via CLI to the AP Master Unleashed.

2: Now enter the credentials:

Note: the credentials for the CLI access to the master Access Point are the same credentials you used for the APP or the Web GUI

Enter the username and password

You should be at the command prompt 

Enter the username and password

You should be at the command prompt 

ruckus>

Enter the following command: enable

ruckus>enable

ruckus#

Enter the command: config

ruckus#config

ruckus(config)#

Enter the command: show wlan

ruckus(config)#show wlan

Enter the command: wlan home-WiFi

Replace home-WiFi with the name of your Wi-Fi SSID

ruckus(config)# wlan home-WiFi

ruckus(config-wlan)#

Enter the command: no qos directed-multicast

ruckus(config-wlan)# no qos directed-multicast

Enter the command: qos directed-threshold 0

ruckus(config-wlan)# qos directed-threshold 0

Enter the command: end

ruckus(config-wlan)# end

This will save the changes.

Now restart your SONOS components

Gmail SMTP configuration example:

The Gmail SMTP server settings for sending mail through Gmail from any email program are:

Gmail SMTP server-address: smtp.gmail.com

Gmail SMTP username: Your full Gmail address (e.g. example@gmail.com)

Gmail SMTP password: Your Gmail password “This step will be explained in the App Password section”

Gmail SMTP port (TLS): 587

Gmail SMTP TLS/SSL required: yes

Note: Starting from May 30, 2022, Google has deprecated the option to 'allow less secure apps.' Please utilize App passwords to generate the SMTP authentication password.

To configure APP password:

1. Go to https://myaccount.google.com/security
2. Scroll down to Signing in to Google
3. Ensure 2-step verification is “On”

4. If two step verification is not “On” we will not be able to setup App passwords
5. Click App Passwords

6. Gooogle prompts to enter your account password
7. Enter a name for the custom device > click create

8. A unique 16-character password has been generated for the Gmail SMTP authentication . Please use this password in the 'Gmail SMTP password' step.

In Admin & Services --> Administration --> Certificate --> Advanced Options, we see options for the Unleashed web server.  Although this is "just" Unleashed which is usually an internal web server in SMB and home environments, I still think it's important to follow industry best practices.  I believe that 1024-bit RSA has been deprecated many years ago; I've seen various articles that talked about retiring it in 2009, 2013, 2015, etc.

I propose completely removing 1024-bit and making 2048-bit private keys the new minimum default.  But also adding a new option for 4096-bit.  It doesn't really hurt anything, in my experience.

There's also a few grammatical errors in the English version of Unleashed (sorry!) that would look better if fixed.

In case my screenshot is too small:

"Re-generate a new private key of a specific key length. This function is only needed when your certificate vendor only accepts 2048 key length instead of 1024 key length. Warning: The Unleashed will be rebooted after re-generating a new private key."

* get rid of "The" Unleashed in the last sentence.  Also the middle sentence will no longer be necessary with the new 2048-bit default so maybe delete it.

"Import a trusted CA to Unleashed. When Unleashed received receives a server's certificate, Unleashed it will match the server's CA against the Unleashed's list of trusted CAs. If there is not match, Unleashed will send an error."

should be "Import a trusted CA to Unleashed.  When Unleashed receives a server's certificate, it will match the server's CA against Unleashed's list of trusted CAs.  If there is no match, Unleashed will send an error.

Thank you for your consideration.  I appreciate the hard work of the internal team in making Unleashed a great product for SMB and advanced home users.  I hope it sticks around for many, many more generations of AP and ICX products.

To disable status LEDs on all APs of a specific model:

1. Go to Access Points > Summary > Edit > Other.
2. Select the AP model from the list and enable the option Disable Status LEDs. The setting must be configured for each AP model individually.
3. Click Finish to save your changes

For more info on the LED behavior meaning please visit: https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/Ruckus-AP-LED-indicator-meaning/td-p/67848

Initially, need to connect with the Server Manager. Subsequently, we will install the DHCP feature. The installation choices are discretionary; I plan to implement a role-based approach with a focus on the "basic" configuration.

At this point, we will proceed with the installation of the DHCP function.

We will incorporate the essential features as required.

Install

We should expect a warning. In such a situation, we will proceed by selecting "commit" and then closing it.

Navigate to the Tools tab and proceed to choose the DHCP option.

This action will launch the DHCP manager, providing us with the capability to generate scopes and configure DHCP groups based on our specific preferences.

I will now conduct a demonstration of a fundamental IPv4 configuration. Please note that these values can be adjusted to align with your preferences and the necessary configurations.

To proceed, select the "IPv4" option, followed by "New Scope."

I will configure the scope range  from the following range 10.0.0.3 to 10.0.0.30, ensuring that the devices are assigned valid IP addresses within this range.

The subsequent options are provided on an optional basis:

+Exclusion addresses

+Lease time

+DHCP options

+Default Gateway

+DNS

+Server

I will incorporate the feature to assign a default gateway to the client's IP configuration.

In the DNS server there are some by default you can delete them and add the directory of your preference

You have the choice to enable DHCP here, but if you prefer, you can opt to activate it later. For now, I'll proceed with its activation.

After setting up the DHCP server, you will notice its presence within the administrator interface. From there, you'll be able to customize the configuration according to your preferences, review leasing information, monitor statistics, and easily manage additions or removals of configurations as needed.