User's Manual

EnRoute500 User’s Guide
TR0149 Rev. C5
69
10 Client DHCP Configuration
Two configuration options exists for assigning IP addresses to client devices using DHCP:
• Each EnRoute500 hosts a local DHCP server and supplies addresses to devices attaching
to any of the client interfaces
• A centralized DHCP server supplies addresses to client devices, with the EnRoute500s in a
mesh relaying DHCP messages between client devices and the centralized server.
All client interfaces in a mesh cluster must use the same DHCP option or have DHCP
disabled.
10.1 Using Local DHCP Servers
The EnRoute500 can be set to serve DHCP addresses to clients on enabled access point
interfaces and the Ethernet interface on repeater nodes. The ‘dhcp.role’ parameters in the
‘wlanN’ and ‘eth0’ interfaces control DHCP behavior. When set to ‘server’, the EnRoute500 will
respond to DHCP requests received from client devices connected to the interface. The
examples below show how to set the DHCP server state for the ‘wlan1’ interface.
> use wlan1
wlan1> set dhcp.role=server
To disable the DHCP server, set the ‘dhcp.role’ parameter to ‘none’
> use wlan1
wlan1> set dhcp.role=none
The access point and wired interface DHCP servers’ state can be set via the web interface
using the “DHCP” sub-tab under the “DHCP” tab on the “System Parameters” page (see
Figure 36). All of the access points’ DHCP settings can be configured on this page.
The addresses provided by the DHCP server will be in the subnet defined by the ‘id.lanprefix’,
‘id.mesh’, ‘id.node’ in the ‘sys’ interface and the ‘ip.start.actual’ and ‘ip.size.actual’ parameters
in the appropriate client interface. For example, for the ‘wlan1’ interface, the start and end of
the address range are:
Start address = <sys.id.lanprefix>.
<sys.id.mesh>.
<sys.id.node>.
<wlan1.ip.start.actual> + 1