Unleashed provides a built-in DHCP server that you can enable to assign IP addresses to devices that are connected to the Unleashed network. The internal DHCP server will only assign addresses to devices that are on its own subnet and part of the same VLAN.
To configure the built-in DHCP server:
- Go to Admin & Services > System > IP Settings.
- in WAN Address, select Manual, and enter static IP settings (IP address, Netmask, Gateway and DNS settings) for the WAN IP address.
- In LAN and WLAN Client IP Addresses, enable the DHCP Server check box.
- In Starting IP, type the first IP address that the built-in DHCP server will allocate to DHCP clients. The starting IP address must be on the same subnet as the IP address assigned to the Unleashed Master AP. If the value that you typed is invalid, an error message appears and prompts you to let Unleashed automatically correct the value. Click OK to automatically correct the entry.
- In Ending IP, type the last IP address in the range that you want to allocate to requesting clients. The built-in DHCP server can allocate up to 512 IP addresses including the one assigned to the Unleashed Master AP. The default value is 200.
- In Lease Time, select a time period for which IP addresses will be allocated to DHCP clients. Options range from six hours to two weeks (default is one week).
NOTEIf you typed an invalid value in any of the text boxes, an error message appears and prompts you to let Unleashed automatically correct the value. Click OK to change it to a correct value.NOTERuckus recommends that you only enable the built-in DHCP server if there are no other DHCP servers on the network. If you enable the built-in DCHP server, Ruckus also recommends enabling rogue DHCP server detection. For more information, refer to Rogue DHCP Server Detection.NOTEMake sure the DHCP address pool is routable to the internet and non-overlapping with other devices. Because Unleashed in non-gateway mode does not support NAT (Network Address Translation), this is important to avoid IP address conflicts. For example, if your router uses the 192.168.0.x subnet, you should use any subnet other than 192.168.0.x for your Unleashed DHCP subnet.