MikroTik MTCRE lab 5 of 14
PPP VPNs: L2TP over IPsec and SSTP between sites
Join a branch to head office with the PPP-based VPNs of the MTCRE outline: L2TP protected by IPsec as the main tunnel and SSTP over TLS with your own certificate authority as the backup, with routes pushed from the PPP secrets and automatic fall-back.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 2,816 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCRE RouterOS v7 guided labs, then 05 - PPP VPNs - L2TP over IPsec and SSTP between sites
- Level
- Advanced
- Time
- About 70 minutes
- Nodes need
- 5 vCPU, 2,816 MB
- Smallest plan
- Lite
The scenario
A firm of surveyors runs a branch office whose firewall policy only allows "standard" VPNs: L2TP with IPsec, or TLS-based SSTP on port 443, which passes almost any hotel or office firewall. Fernvale will build both between HQ and the Branch router: L2TP/IPsec as the main tunnel, SSTP as the backup, each carrying the routes between the two LANs.
| Item | Value |
|---|---|
| HQ WAN / Branch WAN | 203.0.113.2/30 / 198.51.100.2/30 |
| L2TP account | branch-l2tp / Branch-l2tp1, tunnel 172.16.20.1 (HQ) ↔ 172.16.20.2 (Branch), IPsec pre-shared key L2tp-psk1 |
| SSTP account | branch-sstp / Branch-sstp1, tunnel 172.16.30.1 ↔ 172.16.30.2 |
| LANs | HQ 192.168.1.0/24 · Branch 192.168.2.0/24 |
What you’ll practise
- Compare VPN types: IPIP, EoIP, GRE, PPTP, SSTP, L2TP, PPPoE and WireGuard
- Run an L2TP server with IPsec required and a matching client
- Create a certificate authority and a server certificate on RouterOS, and run an SSTP server
- Use PPP secrets with fixed tunnel addresses and routes that are added when a client connects
- Use two tunnels with different route distances for fail-over
- Read PPP sessions, IPsec peers and tunnel status
The tasks
- Choose the tunnel type
- Prepare the PPP accounts on HQ
- L2TP with IPsec
- Build your own certificate authority for SSTP
- SSTP as the backup tunnel
- Test the fall-back
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- ISP
ether1to HQether1 - ISP
ether2to Branchether1 - HQ
ether2to PC-HQeth0 - Branch
ether2to PC-BReth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| ISP | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| HQ | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| Branch | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PC-HQ | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC-BR | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCRE RouterOS v7 guided labs.Open
05 - PPP VPNs - L2TP over IPsec and SSTP between sitesand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More MikroTik MTCRE labs
Related labs in other courses
CloudLabBox is independent of MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.