Allow the device in the DMZ zone (DMZ Server) to access the internet securely, with proper firewall policy and NAT configuration. This is useful when, for example, a public-facing server in the DMZ needs to download updates or reach a cloud service.
Prerequisites:
● DMZ Servere IP: 192.168.2.10/24, Gateway: 192.168.2.1
● Fortinet port3 (DMZ): 192.168.2.1/24
● Internet is reachable via port1: 192.168.100.1/24, Default route and DNS are already set (Lab 3)
We already configured zone mapping (Lab 2)
From GUI:
1. Navigate to Policy & Objects > Addresses
2. Click Create New
● Name: DMZ-Subnet
● Type: Subnet
● Subnet/IP Range: 192.168.2.0/24
● Interface: port3 (DMZ-Zone)
3. Click OK
From CLI:
! config firewall address edit "DMZ-Subnet" set subnet 192.168.2.0 255.255.255.0 next end ! |
From GUI:
1. Go to Policy & Objects > Firewall Policy
2. Click Create New
● Name: DMZ-to-Untrust
● Incoming Interface: port3 (DMZ-Zone)
● Outgoing Interface: port1 (Untrust-Zone)
● Source: DMZ-Subnet
● Destination: all
● Schedule: always
● Service: ALL
● Action: ACCEPT
● NAT: Enable NAT using Use Outgoing Interface Address
3. Enable Log Allowed Traffic → All Sessions
4. Click OK
From CLI:
! config firewall policy edit 2 set name "DMZ-to-Untrust" set srcintf "port3" set dstintf "port1" set srcaddr "DMZ-Subnet" set dstaddr "all" set action accept set schedule "always" set service "ALL" set nat enable set logtraffic all next end ! Show firewall policy |
On the DMZ Server, open a terminal.
Test internet connectivity:
ping 8.8.8.8 nslookup www.uninets.com |
On Fortinet, go to:
● Log & Report > Forward Traffic
● Confirm sessions from 192.168.2.10 to the internet are logged.