User's Manual

EnRoute500 User’s Guide
TR0149 Rev. C5
74
On the gateway:
> use sys
sys> set dhcp.relay.base=3
on the first repeater node:
> use sys
sys> set dhcp.relay.base=8
and on the second repeater node:
> use sys
sys> set dhcp.relay.base=13
The ‘dhcp.relay.base’ parameter can be set via the web interface on the “DHCP Relay” sub-tab
under the “DHCP” tab on the “System Parameters” page (see Figure 37).
10.2.2 Configuring the Central DHCP Server
Guidelines for configuring the central DHCP server are provided below. The full configuration
of the central DHCP server will depend on the type of DHCP server that is used and is beyond
the scope of this document.
Typically the following information must be available in order to configure the server:
1. The local interface (to the DHCP server) over which the DHCP-related messages from
the mesh cluster arrive
2. The parameter(s) that define the address lease time
3. Whether DNS and domain names are to be provided by the DHCP server to clients
4. The range of the flat IP address that is used for assigning addresses to clients. The
range must not include the addresses set aside for the client interfaces on each mesh
node.
The following is a segment of the dhcpd.conf file for a Linux DHCP server (ISC server) that
illustrates the scope settings for the mesh segment:
subnet 192.168.5.0 netmask 255.255.255.0
{
option broadcast-address 192.168.5.255;
option subnet-mask 255.255.255.0;
option domain-name "domain.com";
range 192.168.5.18 192.168.5.254;
}
Note that in this definition no “routers” option is needed. If a global “routers” option is defined,
it will be set to the correct value for proper operation inside the mesh segment. In this
example, the mesh segment includes 3 mesh nodes, 2 addresses are set aside for the DHCP
server and the mesh gateway, and therefore the address pool starts from 192.168.5.18.