Ruckus H320 DHCP/NAT
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2018 08:19 AM
Hi,
I am doing some testing with a H320, vSZ-H version 3.6.0.0.510, AP firmware 3.6.0.0.771, specifically the DHCP/NAT on the AP feature.
I have it working fine over the WiFi, I have set up the DHCP pool attached to a VLAN (11), and then an SSID also on that VLAN, when I connect I get DHCP from the AP and connection NAT'd out to the internet. No issues.
However, if I configure the physical LAN ports on the H320 to be access ports on the same VLAN (11), I do not get DHCP from the AP, I get nothing.
I have configured the ports as access ports on another VLAN (200) that does exist on our local network and that passes through fine and I get DHCP from our DHCP server on VLAN 200, so VLAN passthrough seems to be working fine. VLAN 11 does not exist anywhere else on our network apart from the AP.
Is it possible to get DHCP from the AP to a device using the LAN ports?
Thanks,
I am doing some testing with a H320, vSZ-H version 3.6.0.0.510, AP firmware 3.6.0.0.771, specifically the DHCP/NAT on the AP feature.
I have it working fine over the WiFi, I have set up the DHCP pool attached to a VLAN (11), and then an SSID also on that VLAN, when I connect I get DHCP from the AP and connection NAT'd out to the internet. No issues.
However, if I configure the physical LAN ports on the H320 to be access ports on the same VLAN (11), I do not get DHCP from the AP, I get nothing.
I have configured the ports as access ports on another VLAN (200) that does exist on our local network and that passes through fine and I get DHCP from our DHCP server on VLAN 200, so VLAN passthrough seems to be working fine. VLAN 11 does not exist anywhere else on our network apart from the AP.
Is it possible to get DHCP from the AP to a device using the LAN ports?
Thanks,
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2018 12:48 PM
You would need to sniff the traffic when you attach a wired device, to see if DHCP requests go out, and what happens then...
Otw, I think this should work.
Otw, I think this should work.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2018 01:31 AM
Hi Michael,
Thanks for the reply. The packet captures show pretty much what I was expecting, DHCP requests going out from the client, but nothing coming back;
Not working on LAN port with access VLAN same as wireless DHCP subnet;

Working on LAN port with access VLAN that exists on our network;

It seems as though the LAN ports are only passing traffic through the AP to the uplink port, and we can't get DHCP from the AP using the LAN ports?
Is there an official, this should or shouldn't work, for this? I can raise a support ticket if that's a better avenue to go down?
Thanks,
Chris.
Thanks for the reply. The packet captures show pretty much what I was expecting, DHCP requests going out from the client, but nothing coming back;
Not working on LAN port with access VLAN same as wireless DHCP subnet;
Working on LAN port with access VLAN that exists on our network;
It seems as though the LAN ports are only passing traffic through the AP to the uplink port, and we can't get DHCP from the AP using the LAN ports?
Is there an official, this should or shouldn't work, for this? I can raise a support ticket if that's a better avenue to go down?
Thanks,
Chris.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2018 03:40 AM
Chris,
DHCP/NAT Hierarchical Network Topology (HNT) Feature was released on Smartzone 5.0.
Check the release note of 5.0 for the details.
Prior to that version, it will only assign to WLAN devices.
Hope that helps.
DHCP/NAT Hierarchical Network Topology (HNT) Feature was released on Smartzone 5.0.
Check the release note of 5.0 for the details.
Prior to that version, it will only assign to WLAN devices.
Hope that helps.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2018 01:29 AM
Thanks for the reply Manuel. We tend to wait for a .1 release before upgrading, so we're not running 5.0 just yet, but I will check that out. Looks like the 5.1 release isn't too far away either.

