User's Manual

11.2.2 Network Settings (Common Settings)

Static Route Settings

Static Route

This table is for defining static routing rules for the LAN segment. A static route consists of

the network address, subnet mask, and gateway address. The address and subnet mask

values are in w.x.y.z format.

The local LAN subnet and subnets behind the LAN will be advertised to the VPN. Remote

routes sent over the VPN will also be accepted. Any VPN member will be able to route to

the local subnet. Click to create a new route. Click to remove a route.

Entries in this list will allow traffic to route to a different subnet that is connected to the LAN

interface. Any traffic destined for a network/mask pair will be directed to the corresponding

gateway instead of routed through WANs.

- Advanced feature, please click the button on the top right hand corner of the Static Route session

to activate and configure Virtual Network Mapping to resolve network address conflict with remote peers.

In case of a network address conflict with remote peers (i.e. PepVPN / IPsec VPN / IP Forwarding WAN

are considered as remote connections), you can define Virtual Network Mapping to resolve it.

Note: OSPF & RIPv2 settings should be updated as well to avoid advertising conflicted networks.

For further details on virtual network mapping watch this video: https://youtu.be/C1FMdZCn3Z8

Virtual Network Mapping

One-to-One

NAT

Every IP Address in the Local Network has a corresponding unique Virtual IP Address for

NAT.

Traffic originating from the Local Network to remote connections will be SNAT'ed and

behave like coming from the defined Virtual Network.

While traffic initiated by remote peers to the Virtual Network will be DNAT'ed accordingly.

Many-to-One

NAT

The subnet range defined in Local Network will be mapped to a single Virtual IP Address for

NAT. Traffic can only be initiated from local to remote, and these traffic will be NAT'ed and

behaves like coming from the same Virtual IP Address.

https://www.peplink.com