How to set up your FortiWAN
Configuring Network Interface (Network Setting)
Check [Enable DHCP] if hosts in the subnet in DMZ require DHCP service. And enter the starting and ending address
in [DHCP Range]. If any host in the subnet uses static IP address, then in [Static Mapping], enter its IP and MAC
address. Note: FortiWAN assumes IP addresses that are unlisted in [IP(s) on Localhost] are all in DMZ. Thus there is
no need to configure them.
[Basic Subnet]: Subnet in WAN and DMZ
This topology is found where cluster hosts in IPv4 private subnet are located in both WAN and DMZ. FortiWAN hereby
assumes IP addresses that are unlisted in [IP(s) on Localhost] and [IP(s) in WAN] are all in the DMZ. Port2 and port5
are connected in dotted line, indicating the subnet spreads across WAN (port2) and DMZ (port5). FortiWAN employs
Proxy ARP to connet the whole subnet togther. In this example, more than one IP addresses are needed for FortiWAN
in bridging. These IP addresses therefore have to be on the same network segment. Enter 192.168.5.20-192.168.5.30
in [IP(s) on Localhost], and 192.168.5.10-192.168.5.19 in [IP(s) in WAN].
[Basic Subnet]: Subnet on Localhost
This topology is found where a whole IPv4 private subnet is designated on FortiWAN. And the IP addresses in this
subnet can be utilized by Virtual Server. An IPv6 private subnet is not supported for this subnet type.
[Static Routing Subnet]: Subnet in WAN
This topology is found where IPv4 private static routing subnet is located on the WAN. In other words, the private
subnet on the WAN does not connect to FortiWAN directly. Instead, it connects to a router which helps to transfer its
packets.
82
FortiWAN Handbook
Fortinet Technologies Inc.
