topic Re: Ruckus Cloud DHCP POOL problem in RUCKUS One

Ruckus Cloud DHCP POOL problem

winghung — Thu, 07 May 2026 03:08:23 GMT

I would like to use Ruckus Cloud (R1) with the DHCP POOL service the assign existing IP subnet which it connection lost between the gateway and internet.

Is it NAT problem or DHCP pool configure wrong ?

there are testing case:

Case 1 - Result: Successful
local DHCP server <-------> POE Switch <----------> Ruckus AP R550
local DHCP assign subnet 192.168.10.x/27
POE Switch: VLAN 1, 110, 120 untag
SSID: default VLAN 1

======================

Case 2 - Result: no Successful & cannot access internet & default gateway

local DHCP server <-------> POE Switch <----------> Ruckus AP R550
local DHCP server: no assign the IP
POE Switch: VLAN 1, 110, 120 untag
SSID: VLAN 120
Ruckus AP - DHCP POOL: 192.168.10.x/27 & VLAN 120

===================================

Case 3 - Result: Successful, can access internal & gateway
local DHCP server <-------> POE Switch <----------> Ruckus AP R550
local DHCP server: no assign the IP
POE Switch: VLAN 1, 110, 120 untag
SSID: VLAN 110
Ruckus AP - DHCP POOL: 192.168.0.0/27 & VLAN 110

Re: Ruckus Cloud DHCP POOL problem

Sunil_Acharya — Tue, 30 Jun 2026 04:42:46 GMT

Hi Winghung,

Greetings.

Please find a concise summary of our findings below:

The AP DHCP service in RUCKUS One is working as expected, as clients are successfully receiving IP addresses.
The issue is not related to DHCP configuration or a NAT problem.
The failure observed in Case 2 is specific to VLAN 120, where clients are unable to reach the default gateway.
This indicates that VLAN 120 does not have proper Layer 3 reachability or a valid upstream gateway path.
In contrast, VLAN 110 (Case 3) is correctly mapped to a reachable gateway, which is why connectivity is successful.

Recommendation:

Ensure VLAN 120 has a valid Layer 3 interface (gateway) configured on the router/firewall.
Verify routing and internet access for this subnet from the upstream device.

Please let us know if you need assistance validating the configuration. We are happy to assist you if you could create case via support portal.

Regards,

Sunil Acharya

Re: Ruckus Cloud DHCP POOL problem

winghung — Thu, 02 Jul 2026 06:10:06 GMT

thanks for updated and I solved the problem
while the new issue:

Gateway <-------> POE Switch (all port using default vlan 1 untagged) <----------> Ruckus AP R550
Ruckus AP R550 using Ruckus R1 DHCP pool with vlan 300 (192.168.11.1 /24)
Local Gateway & POE Switch (192.168.10.1/24)

Through Ruckus AP end devices (192.168.11.1/24) can ping / read / write success with local wired device (192.168.10.1/24), but local wired device ping to Ruckus AP connected device fail.

tried to use subnet with 192.168.10.20/27 assign new SSID for testing were identical.

POE switch vlan testing configure as below:
1. all port vlan untagged
2. port 8 untagged (wired to gateway), port 1 tagged vlan 300 (wired to Ruckus R550 AP)

how to solve this problem?