Internet access: firewall policy, source NAT and an IP pool
Write the policy that lets the LAN out, see why replies never come back without source NAT, then move the LAN behind a dedicated public address with an IP pool.
Scenario
HQ-FGT is addressed and routed, but nothing from the LAN reaches the Internet: with no firewall policy, the implicit deny (policy 0) drops everything. Allow the LAN (port2) out to the Internet (port1) with a policy named LAN-to-Internet that logs all sessions. The ISP routes only 203.0.113.0/24 back to you, so the LAN's private addresses must be translated. The ISP has also assigned 203.0.113.100 for user traffic: make LAN sessions leave from that address, not from the firewall's own 203.0.113.2.
Your tasks
- PC1 can ping 8.8.8.8, open its web server (TCP 80) and use it for DNS (UDP 53).
- That policy is named LAN-to-Internet, accepts traffic and logs all sessions.
- Traffic from PC1 reaches the Internet with source address 203.0.113.100.
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.