Difference between revisions of "Template:Networking rutx configuration example l2tp over ipsec work use case default gateway"
Line 17: | Line 17: | ||
'''Prerequisites''': | '''Prerequisites''': | ||
− | * One | + | * One RUTxxx router (In this article RUTX11 will be used) |
* A Public Static or Public Dynamic IP addresses | * A Public Static or Public Dynamic IP addresses | ||
* At least one end device with Windows 10 | * At least one end device with Windows 10 | ||
<br> | <br> | ||
− | The topology above depicts the L2TP/IPsec scheme. - The router with the Public IP address ('''''RUTX11''''') acts as the '''L2TP/IPsec server''' and the '''Windows 10 device''' acts as '''client'''. L2TP connects the networks of '''RUTX11''' and '''Windows 10 client''', IPsec provides the encryption for the L2TP tunnel | + | The topology above depicts the L2TP/IPsec scheme. - The router with the Public IP address ('''''RUTX11''''') acts as the '''L2TP/IPsec server''' and the '''Windows 10 device''' acts as '''client'''. L2TP connects the networks of '''RUTX11''' 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. | + | 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 workers LAN and WAN traffic is going to go through that tunnel. |
==Configuring HQ corporation router== | ==Configuring HQ corporation router== | ||
Line 106: | Line 106: | ||
</table> | </table> | ||
− | == | + | ===Firewall=== |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
---- | ---- | ||
<table class="nd-othertables_2"> | <table class="nd-othertables_2"> | ||
<tr> | <tr> | ||
− | <th width= | + | <th width=355; style="border-bottom: 1px solid white;></th> |
− | <th width= | + | <th width=790; style="border-bottom: 1px solid white;" rowspan=2>[[File:Networking_rutx_configuration_examples_l2tp_over_ipsec_windows_10_5_v1.png|770px|right]]</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="border-bottom: 1px solid white> | <td style="border-bottom: 1px solid white> | ||
− | + | Go to the '''Network → Firewall → General Settings''' and press edit next to the L2TP zone forwarding rule: | |
</td> | </td> | ||
</tr> | </tr> | ||
Line 138: | Line 125: | ||
<table class="nd-othertables_2"> | <table class="nd-othertables_2"> | ||
<tr> | <tr> | ||
− | <th width= | + | <th width=355; style="border-bottom: 1px solid white;></th> |
− | <th width= | + | <th width=790; style="border-bottom: 1px solid white;" rowspan=2>[[File:Networking_rutx_configuration_examples_l2tp_over_ipsec_windows_10_6_v1.png|770px|right]]</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="border-bottom: 1px solid white> | <td style="border-bottom: 1px solid white> | ||
− | + | Allow L2TP forward to/from '''WAN''' and click the '''Save & Apply''' button: | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</td> | </td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
− | + | ==Home worker’s computer== | |
<table class="nd-othertables_2"> | <table class="nd-othertables_2"> | ||
<tr> | <tr> | ||
<th width=525; style="border-bottom: 1px solid white;"></th> | <th width=525; style="border-bottom: 1px solid white;"></th> | ||
− | <th width=620; style="border-bottom: 1px solid white;" rowspan=2>[[File: | + | <th width=620; style="border-bottom: 1px solid white;" rowspan=2>[[File:Networking_rutxxx_configuration_examples_l2tp_over_ipsec_windows_10_6_v2.png|border|class=tlt-border|550px|right]]</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="border-bottom: 1px solid white> | <td style="border-bottom: 1px solid white> | ||
− | + | Type '''VPN settings''' in the Windows search bar: | |
</td> | </td> | ||
</tr> | </tr> | ||
Line 191: | Line 155: | ||
<tr> | <tr> | ||
<th width=525; style="border-bottom: 1px solid white;"></th> | <th width=525; style="border-bottom: 1px solid white;"></th> | ||
− | <th width=620; style="border-bottom: 1px solid white;" rowspan=2>[[File: | + | <th width=620; style="border-bottom: 1px solid white;" rowspan=2>[[File:Networking_rutxxx_configuration_examples_l2tp_over_ipsec_windows_10_7_v2.png|border|class=tlt-border|550px|right]]</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="border-bottom: 1px solid white> | <td style="border-bottom: 1px solid white> | ||
− | + | Click the '''Add a VPN connection''' button: | |
</td> | </td> | ||
</tr> | </tr> | ||
Line 205: | Line 169: | ||
<tr> | <tr> | ||
<th width=525; style="border-bottom: 1px solid white;"></th> | <th width=525; style="border-bottom: 1px solid white;"></th> | ||
− | <th width=620; style="border-bottom: 1px solid white;" rowspan=2>[[File: | + | <th width=620; style="border-bottom: 1px solid white;" rowspan=2>[[File:Networking_rutxxx_configuration_examples_l2tp_over_ipsec_windows_10_8_v2.png|border|class=tlt-border|550px|right]]</th> |
</tr> | </tr> | ||
<tr> | <tr> | ||
<td style="border-bottom: 1px solid white> | <td style="border-bottom: 1px solid white> | ||
− | + | Configure the following parameters: | |
− | + | <ol> | |
− | + | <li>Select '''VPN provider: Windows (built-in)'''.</li> | |
− | </ | + | <li>Enter a custom '''Connection name'''.</li> |
− | + | <li>Enter the router's WAN IP address into the '''Server name or address''' field.</li> | |
− | - | + | <li>Select '''VPN type: L2TP/IPsec with pre-shared key'''.</li> |
− | + | <li>Enter the '''Pre-shared key''' exactly as it was specified on the router.</li> | |
− | < | + | <li>Select '''Type of sign-in info: User name and password'''.</li> |
− | + | <li>Enter the '''User name''' and '''Password''' exactly as they were specified on the router.</li> | |
− | + | <li>Click '''Save'''</li> | |
− | + | </ol> | |
− | |||
− | |||
− | |||
− | |||
</td> | </td> | ||
</tr> | </tr> | ||
Line 237: | Line 197: | ||
<tr> | <tr> | ||
<td style="border-bottom: 1px solid white> | <td style="border-bottom: 1px solid white> | ||
− | + | 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: | |
</td> | </td> | ||
</tr> | </tr> |
Revision as of 11:55, 19 October 2022
|
Configuration overview and prerequisites
Prerequisites:
- One RUTxxx router (In this article RUTX11 will be used)
- 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 (RUTX11) acts as the L2TP/IPsec server and the Windows 10 device acts as client. L2TP connects the networks of RUTX11 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 workers LAN and WAN traffic is going to go through that tunnel.
Configuring HQ corporation router
L2TP
Login to the router's WebUI and navigate to the Services → VPN → L2TP page and do the following:
|
|
IPsec
Go to the Services → VPN → IPsec page and do the following:
|
In the IPsec Configuration page, do the following (and leave the rest as defaults, unless your specific configuration requires otherwise):
|
Firewall
Go to the Network → Firewall → General Settings and press edit next to the L2TP zone forwarding rule: |
Allow L2TP forward to/from WAN and click the Save & Apply button: |
Home worker’s computer
Type VPN settings in the Windows search bar: |
Click the Add a VPN connection button: |
Configure the following parameters:
|
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
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. |