FortiGate lab 1
FortiGate initial setup: interfaces, admin access and a default route
Take a factory-new FortiGate to a working edge firewall: hostname, WAN and LAN interfaces with roles, safe administrative access, and a default route to the ISP.
About 20 minutes 4 devices 4 tasksBeginner
Scenario
FGT1 has just been racked at head office. port1 connects to the ISP (you are 203.0.113.2/24, the ISP router is 203.0.113.1) and port2 to the LAN (10.0.1.0/24, where the FortiGate is .1). Name the unit HQ-FGT. Administrators on the LAN manage it over HTTPS and SSH, and may ping it. From the Internet side it may only answer ping: no GUI or SSH on the WAN. Finally, give the FortiGate a default route so it can reach the Internet itself.
Your tasks
- The FortiGate's hostname is HQ-FGT.
- port1 is 203.0.113.2/24 with the WAN role; port2 is 10.0.1.1/24 with the LAN role.
- PC1 can ping 10.0.1.1 and open its HTTPS GUI; port1 allows ping only (no HTTPS, HTTP, SSH or Telnet on the WAN).
- FGT1 has a default route via 203.0.113.1 on port1 and can ping 8.8.8.8 itself.
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.