Template:Networking rut configuration example l2tp over ipsec work use case default gateway

Networking rutxxx VPN between HQ topology v4.png

Configuration overview and prerequisites

Prerequisites:

  • One RUTxxx routers of any type (excluding RUT850)
  • A Public Static or Public Dynamic IP addresses
  • At least one end device with Windows 10


The topology above depicts the L2TP/IPsec scheme. - The router with the Public IP address (RUT955) acts as the L2TP/IPsec server and the Windows 10 device acts as client. L2TP connects the networks of RUT955 and Windows 10 client, IPsec provides the encryption for the L2TP tunnel.

When the scheme is realized, home workers will be able to reach corporation’s internal network with all internal systems, allowing working from home to be possible. All of the home worker's LAN and WAN traffic is going to go through that tunnel.

Configuring HQ corporation router

L2TP


Networking rut955 configuration examples l2tp over ipsec windows 10 1 v2.png

Login to the router's WebUI and navigate to the Services → VPN → L2TP page and do the following:

  1. Select Role: Server.
  2. Enter a custom configuration name.
  3. Click the Add New button.
  4. Click the Edit button next to the newly created L2TP instance.

Networking rut955 configuration examples l2tp over ipsec windows 10 2 v2.png
  1. Enable the L2TP instance.
  2. Enter a User name and Password for authentication for the client.
  3. Optionaly, set a fixed IP for this client (if left empty, client will receive first free IP from the IP range).
  4. Don't forget to Save the changes.

IPsec


Networking rutxxx configuration examples l2tp over ipsec windows 10 3 v1.png

Go to the Services → VPN → IPsec page and do the following:

  1. Enter a custom name for the IPsec instance.
  2. Click the Add button.
  3. Click the Edit button next to the newly created instance.

Networking rutxxx configuration examples l2tp over ipsec windows 10 4 v1.png

In the IPsec Configuration page, do the following (and leave the rest as defaults, unless your specific configuration requires otherwise):

  1. Enable the instance.
  2. Select Type: Transport and Save changes.

Networking rutxxx configuration examples l2tp over ipsec windows 10 5 v1.png

After saving the changes, you will be redirected back to the main IPsec page. While there, locate the Pre-shared Keys section and do the following:

  1. Click the Add button.
  2. Enter your Pre-shared key.
  3. Enter %any under Secret's ID selector.
  4. Click the Save button.

Firewall


Networking rutxxx configuration examples l2tp over ipsec windows 10 16 v2.png

Go to the Network → Firewall → General Settings and press edit next to the L2TP zone forwarding rule:


Networking rutxxx configuration examples l2tp over ipsec windows 10 17 v1.png

Allow L2TP forward to WAN and click the Save button:

Home worker’s computer

Networking rutxxx configuration examples l2tp over ipsec windows 10 6 v1.png

Type VPN settings in the Windows search bar:


Networking rutxxx configuration examples l2tp over ipsec windows 10 7 v1.png

Click the Add a VPN connection button:


Networking rutxxx configuration examples l2tp over ipsec windows 10 8 v1.png

Configure the following parameters:

  1. Select VPN provider: Windows (built-in).
  2. Enter a custom Connection name.
  3. Enter the router's WAN IP address into the Server name or address field.
  4. Select VPN type: L2TP/IPsec with pre-shared key.
  5. Enter the Pre-shared key exactly as it was specified on the router.
  6. Select Type of sign-in info: User name and password.
  7. Enter the User name and Password exactly as they were specified on the router.
  8. Click Save

Networking rutxxx configuration examples l2tp over ipsec windows 10 9 v1.png

After you are redirected back to the VPN settings page, locate your new connection and click the Connect button. If the connection was successful, you should see the word "connected" appear under the connection name:

Results

Networking rutxxx configuration examples l2tp over ipsec windows 10 10 v1.png

Home worker should now be able to access HQ network resources. To verify the connection you can ping some internal HQ server and if you get a reply, you have successfully connected to HQ‘s internal network.