FortiGate lab 3 of 25
Interfaces, VLANs, zones and DHCP
Split the office into Staff and Finance VLANs on one FortiGate port, serve each VLAN with DHCP (including a reservation), group the VLANs in a zone and control the traffic between them.
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 03 - Interfaces VLANs zones and DHCP
- Level
- Beginner
- Time
- About 60 minutes
- Nodes need
- 6 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
Finance wants its own network: the auditors don't want finance PCs on the same broadcast domain as everyone else. The office switch (SW1) already carries two VLANs to FGT1 on one cable: VLAN 10 for Staff and VLAN 20 for Finance. Your job is the FortiGate side: a gateway and DHCP for each VLAN, a fixed address for the Finance workstation H2, internet access for both, and a rule that lets Staff ping Finance but not the other way round.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| FGT1 | port1 (ISP-A) | 203.0.113.1/24 | INET, gateway 203.0.113.254 |
| FGT1 | port2 | no address (802.1Q trunk) | SW1 Gi0/0 (VLANs 10 and 20) |
| FGT1 | VLAN10 (you create it) | 10.1.10.1/24 | Staff: PC1 10.1.10.10, H1 by DHCP |
| FGT1 | VLAN20 (you create it) | 10.1.20.1/24 | Finance: H2, reserved 10.1.20.50 |
| SW1 | Gi0/1, Gi0/3 / Gi0/2 | access VLAN 10 / VLAN 20 | H1, PC1 / H2 |
Topology: INET above FGT1; SW1 below it on one trunk; H1 and PC1 in VLAN 10, H2 in VLAN 20.
What you’ll practise
- Create 802.1Q VLAN interfaces on a FortiGate port that trunks to a switch
- Run a DHCP server per VLAN with a domain name and a MAC reservation
- Group interfaces in a zone and decide what intra-zone traffic may do
- Write policies that allow internet access for both VLANs and one-way access between them
- Explain why stateful inspection lets replies return without a reverse policy
The tasks
- Start the lab
- VLAN interfaces on the trunk
- DHCP for each VLAN
- A reservation for the Finance workstation
- A zone for the internal VLANs
- One-way access between the VLANs
- Look at the interfaces and leases
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
- FGT1
port1to INETeth0 - FGT1
port2to SW1Gi0/0 - SW1
Gi0/1to H1eth0 - SW1
Gi0/2to H2eth0 - SW1
Gi0/3to PC1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| FGT1 | Fortinet FortiGate | fortinet-FGT-v7.0.17.M-build0682 | 1 vCPU, 2,048 MB |
| SW1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 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 |
| 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
03 - Interfaces VLANs zones and DHCPand 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.