VLAN interfaces, DHCP servers and guest isolation
Carry a staff VLAN and a guest VLAN on one FortiGate port, serve addresses on both with the FortiGate's DHCP server, give both Internet access and keep guests away from staff and from the admin GUI.
Scenario
SW1 trunks VLAN 10 (staff, PC1) and VLAN 20 (guest, PC2) to HQ-FGT port2. Create VLAN interfaces on port2: STAFF (VLAN 10, 10.10.10.1/24) and GUEST (VLAN 20, 10.20.20.1/24). The FortiGate is the DHCP server for both, handing out .100 to .200 with itself as the gateway and 8.8.8.8 for DNS. Both VLANs get Internet access, guests must not reach the staff network, and only staff may open the FortiGate's HTTPS GUI.
Your tasks
- port2 carries a VLAN 10 interface at 10.10.10.1/24 and a VLAN 20 interface at 10.20.20.1/24.
- PC1 and PC2 get DHCP leases in their VLAN's subnet.
- Both PCs can ping 8.8.8.8, and PC2 (guest) cannot reach PC1 (staff).
- PC1 can open the FortiGate GUI at 10.10.10.1 (HTTPS); PC2 cannot open it at 10.20.20.1.
The lab checks the result, not the exact commands. For example, a ping task passes only when the ping really succeeds through the network you built.