networking:mikrotik:split_tunnel_01
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| networking:mikrotik:split_tunnel_01 [2020/04/12 10:14] – rplecko | networking:mikrotik:split_tunnel_01 [2020/08/19 12:02] (current) – rplecko | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| === Split tunnel - Powershell cmdlet === | === Split tunnel - Powershell cmdlet === | ||
| - | 1. In vpn connection properties select **Internet Protocol V4** | + | - In vpn connection properties select **Internet Protocol V4** |
| - | 2. In **General Properties**, | + | |
| - | 3. In **Advanced TCP/IP Settings**, uncheck | + | |
| - | {{ : | + | [[http:// |
| - | Powershell has a cmdlet available that adds routes | + | Now, your computer will no longer use a gateway |
| - | It works without having to specify the interface ID. | + | |
| - | The basic syntax is like this: | + | Next, we need to add a route so the traffic to the remote network could be routed properly. |
| - | | + | Powershell has a cmdlet available that adds routes on VPN connection and removes them again when the VPN is disconnected: |
| - | + | ||
| - | After entering this command, | + | |
| - | There is no adequate **Get-VpnConnectionRoute** to check your current settings, but you can use **Get-VpnConnection** which gives too much information, | + | The basic syntax |
| + | < | ||
| + | Add-VpnConnectionRoute -ConnectionName "VPN Connection Name" -DestinationPrefix 10.0.0.0/16 | ||
| + | </ | ||
| + | |||
| + | After entering this command, the routes will be created/ | ||
| + | There is no adequate **Get-VpnConnectionRoute** | ||
| [[https:// | [[https:// | ||
| [[https:// | [[https:// | ||
| + | < | ||
| + | </ | ||
networking/mikrotik/split_tunnel_01.1586686470.txt.gz · Last modified: 2020/04/12 10:14 by rplecko
