Virtual Private Networks (VPNs)
When you define a Connection Profile as using L2TP by selecting L2TP as the datalink encapsulation method, and then select Encapsulation Options, the L2TP Tunnel Options screen appears.
L2TP Tunnel Options
L2TP Partner IP Address: | 0.0.0.0 |
L2TP Tunnel Authentication: | No |
PPP Authentication: | PAP |
Data Compression... | Standard LZS |
Send Host Name: |
|
Send Password: |
|
Receive Host Name: |
|
Receive Password: |
|
Initiate Connections: | Yes |
On Demand: | Yes |
Idle Timeout (seconds): | 300 |
Enter an IP address in decimal and dot form (xxx.xxx.xxx.xxx).
•Enter the L2TP Partner IP Address. This specifies the address of the other end of the tunnel. If you do not specify the L2TP Partner IP Address the Router cannot initiate tunnels.
•If you specify the L2TP Partner IP Address, and the address is in the same subnet as the Remote IP Address you specified in the IP Profile Parameters, the Tunnel Via Gateway option becomes visible. You can enter the address by which the Router partner is reached.
If you do not specify the L2TP Partner IP Address, the Router will use the default gateway to reach the partner and the Tunnel Via Gateway field is hidden. If the partner should be reached via an alternate port (i.e. the LAN instead of the WAN), the Tunnel Via Gateway field allows this path to be resolved.
•Toggle L2TP Tunnel Authentication to No or Yes.
If you set authentication on the tunnel, an editable
•From the
•You can specify a Data Compression algorithm, either None or Standard LZS, for the L2TP connection.
•You can specify a Send Host Name which is used with Send Secret for authenticating with a remote PNS when the profile is used for initiating a tunnel connection.
•You must specify a Send Password (or Secret, the CHAP term for password), used for authenticating the tunnel when initiating a tunnel connection.
•You can specify a Receive Host Name which is used with the Receive Secret for authenticating a remote L2TP client.
•You must specify a Receive Password (or CHAP Secret), used for authenticating the remote L2TP client.
