FortiGate lab 17 of 25
Site-to-site IPsec VPN
Join head office and the new branch with a route-based IKEv2 tunnel: phase 1 and phase 2, routes with a blackhole safety net, policies in both directions, then read the tunnel's state and find a pre-shared key mismatch with IKE debug.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 7,680 MB in total. That fits the free demo too.
In your workspace: Shared, then FortiGate NSE 4 guided labs, then 17 - Site-to-site IPsec VPN
- Level
- Intermediate
- Time
- About 70 minutes
- Nodes need
- 5 vCPU, 7,680 MB
- Smallest plan
- Lite
The scenario
Harbourside has opened a branch in Cardiff with its own FortiGate (FGT-BR) on the same ISP. Branch staff need the HQ file servers and HQ staff need the branch printers, privately and without opening anything to the internet. You build a route-based IPsec tunnel between the two FortiGates and prove traffic flows both ways.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| FGT-HQ | port1 (ISP-A) | 203.0.113.1/24 | Internet (gateway 203.0.113.254) |
| FGT-HQ | port2 (LAN) | 10.1.10.1/24 | PC1 10.1.10.10 |
| FGT-BR | port1 (ISP-A) | 203.0.113.2/24 | Internet (gateway 203.0.113.254) |
| FGT-BR | port2 (LAN) | 10.2.10.1/24 | H2 10.2.10.50 (DHCP reservation) |
Tunnel parameters (both sides): IKEv2, pre-shared key LabVpnKey1!, proposal des-sha256, DH group 14, phase 2 selectors HQ 10.1.10.0/24 ↔ branch 10.2.10.0/24.
Evaluation licence. These FortiGates run with low-strength encryption only, so IPsec offers DES only (
des-md5todes-sha512): no AES, no 3DES, not even NULL. The lab usesdes-sha256to get a working tunnel. Never use DES in production: use AES-256-GCM (aes256gcm-prfsha384) with DH group 19, 20 or 21.
What you’ll practise
- Explain IKE phase 1 and phase 2, IKEv1 and IKEv2, selectors, PFS and DPD
- Build a route-based IPsec tunnel between two FortiGates from the CLI
- Route traffic into the tunnel, with a blackhole route so it never leaks
- Allow traffic in both directions with firewall policies
- Check the tunnel with summary, gateway and tunnel lists, and debug IKE
- Describe what the IPsec wizard creates for you
The tasks
- Start the lab
- Phase 1 on both FortiGates
- Phase 2 with selectors
- Routes and a blackhole safety net
- Policies in both directions
- Break it and debug IKE
- What the wizard does (GUI)
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
- FGT-HQ
port1to Internet (network) - FGT-BR
port1to Internet (network) - INET
eth0to Internet (network) - FGT-HQ
port2to PC1eth0 - FGT-BR
port2to H2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| FGT-HQ | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| FGT-BR | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| INET | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| PC1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 2,048 MB |
| H2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
FortiGate NSE 4 guided labs.Open
17 - Site-to-site IPsec VPNand 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 FortiGate labs
Related labs in other courses
CloudLabBox is independent of Fortinet. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.