Digi TransPort WR11 - Page 485

Configuring Virtual Private Networking (VPN) Configure Internet Protocol security (IPsec)
Digi TransPort® Routers User Guide
485
Command Instance Parameter Values Equivalent web parameter
eroute n ipadd Integer IKE negotiation source IP address
is taken from the Interface x,y.
y=Interface number
eroute n intunnel on, off Tunnel this IPsec tunnel inside
another IPsec tunnel.
eroute n natkaint Integer NAT-Traversal Keepalive timer s
seconds.
eroute n proto off, tcp, udp,
gre
Allow protocol IP protocol(s) in
this tunnel.
eroute n toslist Comma-
separated list
of Integers
IP packets with ToS values n must
use this tunnel.
eroute n locport 0-65535 Only tunnel IP packets with local
TCP/UDP port.
eroute n remport 0-65535 Only tunnel IP packets with
remote TCP/UDP port.
eroute n locfirstport 0-65535 Only tunnel IP packets with local
TCP/UDP port in the range of n1
to n2.
eroute n loclastport 0-65535 Only tunnel IP packets with local
TCP/UDP port in the range of n1
to n2.
eroute n remfirstport 0-65535 Only tunnel IP packets with
remote TCP/UDP port in the
range of n1 to n2.
eroute n remlastport 0-65535 Only tunnel IP packets with
remote TCP/UDP port in the
range of n1 to n2.
Set up IPsec tunnels for multiple users
For small numbers of users it is usual to set up an individual eroute for each user. However, to ease
configuration where large numbers of users are required, you can use the * character as a wildcard to
match multiple user IDs. For example, setting the Peer ID parameter to Digi* would match all remote
units having an Our ID parameter starting with Digi, such as Digi01, Digi02, etc.
Example
To set up multiple users in this way, first set up the Our ID parameter on the host unit to a suitable
name, such as Host1. Then set the Peer ID parameter to Remote* for example. In addition, an entry
would be made in the user table with Remote* for the Username and a suitable Password value, such
as mysecret.
Each of the remote units that required access to the host would then have to be configured with an
Our ID parameter of Remote01, Remote02, etc., and each would have to have an entry in their user
table for User Host1 along with its password, such as the pre-shared key.