User's Manual

Chapter 14: Connecting an EnRoute500 Mesh Network to a WAN
TR0153 Rev. E1 109
14.1.4 “Multiple Gateway, Explicit Addressing Scheme” Option
This mode of operation is not supported.
14.2 Network Address Translation (NAT) on Mesh Gateways
Network Address Translation (NAT) provides a simple method for connecting a mesh
neighborhood to a WAN router and also prevents hosts that are located on external networks
from initiating connections with client devices and individual mesh repeaters. However, the
mesh devices, as well as their client devices, are able to establish connections and
communicate with hosts connected to networks external to the mesh.
NAT cannot be used if any of the mesh devices in a mesh neighborhood are
using centralized DHCP server mode.
The advantages of using NAT are:
• You can easily attach a mesh neighborhood to an existing network. You do not need to
modify any settings on the WAN router on your existing network to forward IP packets to
client devices within your mesh neighborhood.
• The devices in the mesh neighborhood are shielded from the network that the gateway is
attached to.
• You only consume a single IP address on your existing network when connecting the mesh
neighborhood to it.
The main disadvantages of using NAT is
• You are not able to initiate connections into the EnRoute500s in the mesh neighborhood or
their clients from outside the mesh neighborhood.
• It is not compatible with centralized DHCP server mode.
CLI
To set the NAT state, use the commands
> use sys
sys> set nat.enable=<yes|no>
Web GUI
The NAT state can be set via the web interface on the “Wired/Backhaul Interface” page (Figure
48).