Known Issues

The following table provides information on the known issues in the current release.

Issues Description
ACX-66646

Summary: Control packet priority issue with RUCKUS Edge.

Symptom: The RUCKUS Edge device does not prioritize the control packets in the network.

Condition: User may experience a lag when configuring RUCKUS One if there is a heavy data traffic.

Workaround: None
ACX-65424

Summary: SD-LAN profile issue with VLAN IDs.

Symptom: When managing SD-LAN profiles with Captive Portal networks across different venues, there's a conflict between actual traffic behavior onRUCKUS Edge devices and how RUCKUS One GUI displays network configurations.

Condition: RUCKUS Edge devices can only identify and forward traffic based on VLAN ID, and not WLAN ID, which means:

  • Networks with the same VLAN ID will share the same traffic behavior.
  • Changing tunnel settings for one network does not affect traffic if another network with the same VLAN ID still has tunneling enabled.

If two different networks are configured with the same VLAN ID and both are tunneled to the DMZ initially, then turning off one of them from tunneling to the DMZ does not change the behavior of that network. It will still be tunneled to the DMZ because another network with the same VLAN ID is still tunneling to the DMZ.

Workaround: None
ACX-74102

Summary: DHCP configuration issue with RUCKUS One.

Symptom: RUCKUS Edge cannot obtain an IP address when configured in mixed mode with both internal and external DHCP.

Condition:

  1. Turn on the PIN and Sub-interface FF on RUCKUS One.
  2. Set up two RUCKUS Edge devices (RE1 and RE2) with three interfaces (WAN, LAN and Cluster) and onboard them to RUCKUS One.
  3. After completing the enrollment process and waiting for the Need port config status on the node.

Test case:

A PIN profile is set up to use an external DHCP pool for the PIN UE (User Equipment) and an internal DHCP pool is configured for WebAuth. Due to this mixed configuration, the UE will not be able to obtain an IP address. This happens because the system is trying to manage two different DHCP pools (external for PIN UE and internal for WebAuth), leading to a conflict that prevents the UE from successfully receiving an IP address.

Allowed configuration for a PIN profile:

  • Both WebAuth and PIN-UE using internal DHCP
  • Both WebAuth and PIN-UE using external DHCP

Prohibited configuration for a PIN profile:

  • WebAuth using internal DHCP with PIN-UE using external DHCP
  • WebAuth using external DHCP and PIN-UE using internal DHCP

Workaround:

Parent topic: Known Issues in Release 2.3.0