FortiGate lab 24 of 25
Troubleshooting: VPN and authentication faults
The branch tunnel is down and directory logins fail. Work through six stacked faults in phase 1, phase 2, policies, LDAP and RADIUS with the IKE debug, the tunnel lists, debug flow, fnbamd and the directory server's own log.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 7,168 MB in total. That fits the free demo too.
In your workspace: Shared, then FortiGate NSE 4 guided labs, then 24 - Troubleshooting - VPN and authentication faults
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 6 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
A colleague rebuilt the Cardiff branch FortiGate and "tidied up" head office's VPN and directory settings on the same afternoon. Now the branch can't reach head office, and the FortiGate's LDAP and RADIUS tests fail, so nobody can use directory logins. The intended design is the one from labs 11 and 17: an IKEv2 tunnel with des-sha256, DH 14 and key LabVpnKey1!, protecting 10.1.10.0/24 ↔ 10.2.10.0/24 in both directions; LDAP base DN DC=corp,DC=lab; RADIUS secret RadSecret1!. Find and fix every fault.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| FGT-HQ | port1 / port2 / port3 | 203.0.113.1 / 10.1.10.1 / 10.1.30.1 (/24) | Internet / H1 10.1.10.50 / SRV1 10.1.30.10 |
| FGT-BR | port1 / port2 | 203.0.113.2 / 10.2.10.1 (/24) | Internet / H2 10.2.10.50 |
Evaluation licence. These FortiGates run with low-strength encryption only, so IPsec offers DES only (
des-md5todes-sha512): no AES, no 3DES. The tunnel is meant to usedes-sha256with DH group 14. Never use DES in production: use AES-256-GCM (aes256gcm-prfsha384) with DH group 19, 20 or 21.
What you’ll practise
- Read IKE debug output to tell proposal, authentication and selector failures apart
- Use tunnel summaries, gateway lists and debug flow to find one-way traffic
- Debug LDAP and RADIUS from both ends: fnbamd on the FortiGate and the server log
- Record each fault as symptom, evidence, root cause and fix
The tasks
- Start the lab
- Collect the symptoms
- Phase 1
- Phase 2
- Traffic works one way only
- LDAP
- RADIUS
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 H1eth0 - FGT-HQ
port3to SRV1eth0 - 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 |
| SRV1 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 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
24 - Troubleshooting - VPN and authentication faultsand 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.