NAT: one public address, a whole office behind it
▶ Start the interactive lesson
Policy added, sessions created... and still no websites. Maya runs a packet capture on the ISP side. "See the source address? 10.1.1.10. That's a private address. The internet has no idea how to send the reply back to it." "So the firewall has to hide the office behind its own public address," you…
Key points
- Private ranges (RFC 1918): 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. They're free to use inside, but not routed on the internet.
- Source NAT / PAT (also "NAT overload"): the firewall swaps the private source for its WAN IP and a unique source port, so hundreds of users share one public address. On a FortiGate it's the NAT toggle on the outbound policy.
- The firewall remembers each translation in its session table. When the reply comes back to the public IP and port, it translates the destination back to the right inside host (reverse NAT).
- Destination NAT (FortiGate: VIP; elsewhere "port forward" / "static NAT") publishes an inside server: public IP:443 → 10.1.1.20:443. You still need a WAN→LAN policy that allows it, as narrow as possible.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →