User's Manual

EnRoute500 User’s Guide
TR0149 Rev. C5
54
8.1.2 Ethernet Interface IP Address
The EnRoute500’s Ethernet interface address should not be changed directly using the ‘ip.*’
parameters in the ‘eth0’ interface when it is in repeater mode. To set the IP address to the
desired value, modify the ‘id.node’, ‘id.mesh’, and ‘id.lanprefix’ parameters in the ‘sys’ interface
and the ‘ip.start.requested’ parameter in the ‘eth0’ interface (see sections 6.3 and 6.5). You
can view the resulting settings for the Ethernet interface with the ‘ip.*’ parameters in the ‘eth0’
interface as shown in the example below.
> use eth0
eth0> get ip.*
ip.address = 10.2.4.225 [read-only]
ip.address_force =
ip.broadcast = 10.2.4.255 [read-only]
ip.broadcast_force =
ip.gateway = [read-only]
ip.gateway_force =
ip.netmask = 255.255.255.0 [read-only]
ip.netmask_force =
ip.size.actual = [read-only]
ip.size.requested = 31
ip.start.actual = [read-only]
ip.start.requested = 225
The Ethernet IP settings are also available through the web interface on the “Status” page.
It is strongly recommended that all the ‘ip.*_force’ variables are cleared when the EnRoute500
is configured as a repeater. This ensures that the Ethernet interfaces settings are inherited
from the ‘id.*’ settings in the ‘sys’ interface and client devices will get addresses that the mesh
can route to.
8.1.3 IP Configuration of Clients Devices via DHCP
When configured as a repeater, the EnRoute500 can be set to serve DHCP addresses to
clients on the Ethernet interface. Two distinct modes for providing addresses via DHCP exist.
These are described in depth in section 10.
8.1.4 Manual IP Configuration of Client Devices
The client devices connected via the Ethernet interface that use static IP addresses must have
addresses that are within the subnet of the Ethernet interface. The IP address and subnet of
the Ethernet interface can viewed with
> use eth0
eth0> get ip.address ip.netmask
eth0.ip.address = 10.2.4.225 [read-only]