FortiWAN Configuring Network Interface (Network Setting)

Configuring Network Interface (Network Setting)

As an edge router of a network site, FortiWAN is supposed to operate with connected networks, the WAN, LAN and DMZ networks. FortiWAN must guarantee general communication among the connected networks (routing), and so that can provide the advanced load balancing and fault tolerance functions. To establish connectivity between FortiWAN and the networks, you need to complete the following basic network settings:

  1. Decide a FortiWAN’s network port for connecting the FortiWAN with the network. This network port can be a physical port, an aggregated, redundant or VLAN port. Whether it is a physical or logical port, you have to program it as what the type that the connected network is (WAN, LAN or DMZ). VLAN and Port Mapping is the configuration that you can create logical network ports (aggregated, redundant and VLAN ports) and define the port mapping to the physical and logical ports (see Configurations for VLAN and Port Mapping).
  2. Configure the basic IP network setting and static routing information to the network port for the connected network. The settings here are necessary for FortiWAN to guarantee basic communication among the connected networks, packets can be routed correctly between the networks. According to the type of connected network, settings are divided into:
    • WAN Setting (DMZ setting is included): WAN Settings is the major part to deploy FortiWAN in various types of WAN links (see Configuring your WAN).
    • WAN/DMZ Private Subnet: This includes settings for deploying private subnets to WAN/DMZ port (see WAN/DMZ Private Subnet).
    • LAN Private Subnet: This includes settings for deploying private subnets to LAN port (see LAN Private Subnet).

Generally speaking, a network site consists of a WAN link and a private LAN network at least. WAN Setting and LAN Private Subnet are the necessary configurations for FortiWAN to connect the internal and external networks.

Some of FortiWAN’s functions, such as system time synchronization, log push, ping and trace commands, require cooperating with external servers. When FortiWAN itself (localhost) communicates with those external servers, such as NTP, FTP, SMTP servers, an appropriate DNS server is required for domain name resolving.

Configuration of DNS Server is part of the basic network setting (see Set DNS server for FortiWAN).

Briefly, network setting of a FortiWAN contains the configurations of:

  1. DNS for FortiWAN’s localhost (DNS Server, see Set DNS server for FortiWAN)
  2. Network port programing (VLAN and Port Mapping, see Configurations for VLAN and Port Mapping)
  3. Individual network connected to FortiWAN and the relative routing information (WAN Setting, WAN/DMZ Private Subnet and LAN Private Subnet, see Configuring your WAN and DMZ, WAN/DMZ Private Subnet and LAN Private Subnet)

Having trouble configuring your Fortinet hardware or have some questions you need answered? Check Out The Fortinet Guru Youtube Channel! Want someone else to deal with it for you? Get some consulting from Fortinet GURU!

This entry was posted in Administration Guides, FortiWAN and tagged on by .

About Mike

Michael Pruett, CISSP has a wide range of cyber-security and network engineering expertise. The plethora of vendors that resell hardware but have zero engineering knowledge resulting in the wrong hardware or configuration being deployed is a major pet peeve of Michael's. This site was started in an effort to spread information while providing the option of quality consulting services at a much lower price than Fortinet Professional Services. Owns PacketLlama.Com (Fortinet Hardware Sales) and Office Of The CISO, LLC (Cybersecurity consulting firm).

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.