User's Manual

Chapter 14: Connecting an EnRoute500 Mesh Network to a WAN
TR0153 Rev. E1 107
14 Connecting an EnRoute500 Mesh Network to a WAN
The options for connecting an EnRoute500 gateway to a WAN and establishing layer 3 IP
routing include:
• Static route configuration on the WAN router
• Source network address translation (NAT) on the mesh gateways
• Layer 2 mesh emulation as part of DHCP relay mode.
Table 13 shows compatibility of single vs. multiple mesh gateways with the use of implicit vs.
explicit addressing for the first two configuration options. Note that different options and
requirements exist depending on whether a single or multiple gateways devices are used.
Table 13. Supported WAN connection options for single and multi-gateway
mesh neighborhoods using implicit or explicit client addressing schemes
14.1 Static Routing Configuration on WAN Router
14.1.1 “Single Gateway, Implicit Addressing Scheme” Option
A single EnRoute500 gateway can be directly connected to a WAN without using Network
Address Translation. With this gateway configuration and with the implicit addressing scheme
in use, the router on the network that the gateway is attached to must be configured to forward
the mesh subnet and the LAN subnets to the gateway’s Ethernet interface. The subnets that
need to be forwarded are:
Class B subnet: <LAN prefix>.<Mesh ID>.0.0
Class C subnet: <Mesh prefix >.<Mesh ID>.0
Static Route Configuration on WAN Router NAT on Mesh Gateway
Supported? Requirements Supported? Requirements
Single gateway, implicit
addressing
Yes
Define EnRoute500 mesh
gateways as next hop gateway in
WAN router or enable L2
emulation mode on mesh gateway
Yes
Single gateway, explicit
addressing
Yes
Define EnRoute500 mesh gateway
as next hop gateway in WAN
router
Yes
Multiple gateways,
implicit addressing
Yes
Enable L2 mode on all mesh
gateways
Yes
Multiple gateways,
explicit addressing
No N/A Yes
No client
access
interface can
be in central
DHCP mode