Digi IX10 User Manual page 172

Virtual Private Networks (VPN)
16. (Optional) To configure the device to connect to its remote peer as an XAUTH client:
a. Click to expand XAUTH client.
b. Click Enable.
c. Type the Username and Password that the device will use to authenticate as an
XAUTH client with the peer.
17. (Optional) Click Enable MODECFG client to receive configuration information, such as the
private IP address, from the remote peer.
18. Click to expand Local endpoint.
a. For Type, select either:
n
n
b. Click to expand ID.
i. Select the ID type:
19. Click to expand Remote endpoint.
a. For Hostname, select either a hostname or IP address. If your device is not configured to
initiate the IPsec connection (see IKE >
IX10 User Guide
Default route: Uses the same network interface as the default route.
Interface: Select the Interface to be used as the local endpoint.
Auto: The ID will be automatically determined from the value of the tunnels
n
endpoints.
Raw: Enter an ID and have it passed unmodified to the underlying IPsec stack.
n
For Raw ID value, type the ID that will be passed.
Any: Any ID will be accepted.
n
IPv4: The ID will be interpreted as an IP address and sent as an ID_IPV4_ADDR
n
IKE identity.
For IPv4 ID value, type an IPv4 formatted ID. This can be a fully-qualified
domain name or an IPv4 address.
IPv6: The ID will be interpreted as an IP address and sent as an ID_IPV6_ADDR
n
IKE identity.
For IPv6 ID value, type an IPv6 formatted ID. This can be a fully-qualified
domain name or an IPv6 address.
RFC822/Email: The ID will be interpreted as an RFC822 (email address).
n
For RFC822 ID value, type the ID in internet email address format.
FQDN: The ID will be interpreted as FQDN (Fully Qualified Domain Name) and
n
sent as an ID_FQDN IKE identity.
For FQDN ID value, type the ID as an FQDN.
KeyID: The ID will be interpreted as a Key ID and sent as an ID_KEY_ID IKE
n
identity.
For KEYID ID value, type the key ID.
Initiate connection), you can also use the
IPsec
172