This topic contains information about FortiGate administration and system configuration that you can do after installing the FortiGate in your network.
Basic system settings
By default, FortiGate has an administrator account with the username admin and no password. See Administrators for more information.
An administrator profile defines what the administrator can see and do on the FortiGate. See Administrator profiles for more information.
Set up a password policy to enforce password criteria and change frequency. See Password policy for more information.
Physical and virtual interface allow traffic to flow between internal networks, and between the internet and internal networks. See Interfaces for more information.
Advanced system settings
The simple network management protocol (SNMP) allows you to monitor hardware on your network. See SNMP for more information.
You can configure one or more DHCP servers on any FortiGate interface. See DHCP server for more information.
You can use virtual domains (VDOMs) to divide a FortiGate into multiple virtual devices that function independently. See Virtual Domains for more information.
You can configure multiple FortiGate devices, including private and public cloud VMs, in HA mode. See High Availability for more information.
You can manage certificates on the FortiGate. See Certificates for more information.
A FortiGate or VDOM (in multi-vdom mode) can operate in either NAT/route mode or transparent mode.
The FortiGate or VDOM is installed as a gateway or router between multiple networks, such as a private network and the internet. One function of NAT/route mode is to allow the FortiGate to hide the IP addresses on the private network using NAT. NAT/route mode can also be used to connect to multiple ISPs in an SD-WAN setup, and to route traffic between different networks. .
By default, new VDOMs are set to NAT/route operation mode.
See NAT mode for more information.
The FortiGate or VDOM operates in layer 2 to forward traffic between network devices such as routers, firewalls, and switches. For example. it can be installed inline between a router and a switch to perform security scanning without changing the network topology or modifying the IP addresses. When you add a FortiGate that is in transparent mode to a network, it only needs to be provided with a management IP address in order to access the device. It is recommended that a dedicated interface is used to connect to the management network in transparent mode.
The following topology is an example of a transparent mode FortiGate inserted inline between a router and a switch:
Using transparent mode VDOMs is recommended when multiple VLANs pass through the FortiGate. Otherwise, they must be separated into different forwarding domains within the same VDOM.
See NAT and transparent mode for more information.
The following is a sample configuration for changing from NAT/route operation mode to transparent operation mode in the CLI:
config system settings set opmode transparent set manageip <IP_address> set gateway <gateway_address> end
The gateway setting is optional. However, once the operation mode is changed from NAT/route to transparent, the gateway configuration is found under the static router settings:
config router static edit <seq-num> set gateway <IP_address> next end
The following is a sample configuration for changing from transparent operation to NAT/route operation mode in the CLI:
config system settings set opmode nat set ip <IP_address> set device <interface> set gateway <gateway_address> end
The IP and device settings are mandatory. Once the operation mode is changed from transparent to NAT/route, the IP address configuration is found under the corresponding interface settings:
config system interface edit <interface> set ip <IP_address> next end
The gateway setting is optional. However, once the operation mode is changed, the gateway configuration is found under the static router settings:
config router static edit <seq-num> set gateway <IP_address> device <interface> next end