Professional Documents
Culture Documents
Fortigate Admin PDF
Fortigate Admin PDF
Trademarks
Dynamic Threat Prevention System (DTPS), APSecure, FortiASIC, FortiBIOS, FortiBridge, FortiClient,
FortiGate®, FortiGate Unified Threat Management System, FortiGuard®, FortiGuard-Antispam,
FortiGuard-Antivirus, FortiGuard-Intrusion, FortiGuard-Web, FortiLog, FortiAnalyzer, FortiManager,
Fortinet®, FortiOS, FortiPartner, FortiProtect, FortiReporter, FortiResponse, FortiShield, FortiVoIP, and
FortiWiFi are trademarks of Fortinet, Inc. in the United States and/or other countries. The names of actual
companies and products mentioned herein may be the trademarks of their respective owners.
Contents
Contents
Introduction ............................................................................................ 23
Fortinet products .......................................................................................................... 23
Before you begin........................................................................................................... 24
How this guide is organized......................................................................................... 24
Document conventions ................................................................................................ 27
IP addresses............................................................................................................. 27
Cautions, Notes and Tips ......................................................................................... 27
Typographical conventions ....................................................................................... 27
CLI command syntax ................................................................................................ 28
Registering your Fortinet product............................................................................... 29
Fortinet products End User License Agreement ....................................................... 29
Customer service and technical support.................................................................... 29
Training .......................................................................................................................... 29
Fortinet documentation ............................................................................................... 30
Tools and Documentation CD................................................................................... 30
Fortinet Knowledge Base ......................................................................................... 30
Comments on Fortinet technical documentation ..................................................... 30
Index...................................................................................................... 731
Introduction
Ranging from the FortiGate®-50 series for small businesses to the FortiGate-5000 series
for large enterprises, service providers and carriers, the FortiGate line combines the
FortiOS™ security operating system with FortiASIC™ processors and other hardware to
provide a high-performance array of security and networking functions including:
• firewall, VPN, and traffic shaping
• Intrusion Prevention system (IPS)
• antivirus/antispyware/antimalware
• web filtering
• antispam
• application control (for example, IM and P2P)
• VoIP support (H.323, SIP, and SCCP)
• Layer 2/3 routing
• multiple redundant WAN interface options
FortiGate appliances provide cost-effective, comprehensive protection against network,
content, and application-level threats, including complex attacks favored by
cybercriminals, without degrading network availability and uptime. FortiGate platforms
include sophisticated networking features, such as high availability (active/active,
active/passive) for maximum network uptime, and virtual domain capabilities to separate
various networks requiring different security policies.
This chapter contains the following sections:
• Fortinet products
• Before you begin
• How this guide is organized
• Registering your Fortinet product
• Fortinet products End User License Agreement
• Customer service and technical support
• Training
• Fortinet documentation
Fortinet products
Fortinet's portfolio of security gateways and complementary products offers a powerful
blend of ASIC-accelerated performance, integrated multi-threat protection, and constantly
updated, in-depth threat intelligence. This unique combination delivers network, content,
and application security for enterprises of all sizes, managed service providers, and
telecommunications carriers, while providing a flexible, scalable path for expansion. For
more information on the Fortinet product family, go to www.fortinet.com/products.
• System Status describes the System Status page, the dashboard of your FortiGate
unit. At a glance you can view the current system status of the FortiGate unit including
serial number, uptime, FortiGuard license information, system resource usage, alert
messages and network statistics. You can also access the CLI from this page. This
section also describes status changes that you can make, including changing the unit
firmware, host name, and system time. Finally this section describes the topology
viewer that is available on all FortiGate models except those with model numbers 50
and 60.
• Managing firmware versions describes upgrading and managing firmware versions.
You should review this section before upgrading your FortiGate firmware because it
contains important information about how to properly back up your current
configuration settings and what to do if the upgrade is unsuccessful.
• Using virtual domains describes how to use VDOMs to operate your FortiGate unit as
multiple virtual FortiGate units, which effectively provides multiple separate firewall and
routing services to multiple networks.
• System Network explains how to configure physical and virtual interfaces and DNS
settings on the FortiGate unit.
• System Wireless describes how to configure the Wireless LAN interface on a
FortiWiFi-60 unit.
• System DHCP explains how to configure a FortiGate interface as a DHCP server or
DHCP relay agent.
• System Config contains procedures for configuring HA and virtual clustering,
configuring SNMP and replacement messages, and changing the operation mode.
• System Admin guides you through adding and editing administrator accounts, defining
admin profiles for administrators, configuring central management using the
FortiGuard Management Service or FortiManager, and defining general administrative
settings such as language, timeouts, and web administration ports.
• System Certificates explains how to manage X.509 security certificates used by
various FortiGate features such as IPSec VPN and administrator authentication.
• System Maintenance details how to back up and restore the system configuration
using a management computer or a USB disk, as well as how to use revision control,
enable FortiGuard services and FortiGuard Distribution Network (FDN) updates, and
enter a license key to increase the maximum number of virtual domains.
• Router Static explains how to define static routes and create route policies. A static
route causes packets to be forwarded to a destination other than the factory-configured
default gateway.
• Router Dynamic explains how to configure dynamic protocols to route traffic through
large or complex networks.
• Router Monitor explains how to interpret the Routing Monitor list. The list displays the
entries in the FortiGate routing table.
• Firewall Policy describes how to add firewall policies to control connections and traffic
between FortiGate interfaces, zones, and VLAN subinterfaces. This chapter also
describes how to add DoS policies to apply DoS sensors to network traffic and how to
add sniffer policies to operate the FortiGate unit as an Intrusion Detection System
(IDS) appliance by sniffing packets for attacks without actually receiving and otherwise
processing the packets.
• Firewall Address describes how to configure addresses and address groups for firewall
policies.
• Firewall Service describes available services and how to configure service groups for
firewall policies.
• Firewall Schedule describes how to configure one-time and recurring schedules for
firewall policies.
• Traffic Shaping describes how to create traffic shaping instances and add them to
firewall policies.
• Firewall Virtual IP describes how to configure and use virtual IP addresses and IP
pools.
• Firewall Load Balance describes how to use FortiGuard load balancing to intercept
incoming traffic and balance it across available servers.
• Firewall Protection Profile describes how to configure protection profiles for firewall
policies.
• SIP support includes some high-level information about VoIP and SIP and describes
how FortiOS SIP support works and how to configure the key SIP features.
• The AntiVirus, Intrusion Protection, Web Filter, and Email filtering chapters explain how
to configure these options associated with a firewall protection profile.
• Data Leak Prevention explains how to use FortiGate data leak prevention to prevent
sensitive data from leaving your network.
• Application Control describes how to configure the application control options
associated with firewall protection profiles.
• IPSec VPN provides information about the tunnel-mode and route-based (interface
mode) Internet Protocol Security (IPSec) VPN options available through the web-
based manager.
• PPTP VPN explains how to use the web-based manager to specify a range of IP
addresses for PPTP clients.
• SSL VPN provides information about basic SSL VPN settings.
• User describes how to control access to network resources through user
authentication.
• WAN optimization and web caching describes how to use FortiGate units to improve
performance and security of traffic passing between locations on your wide area
network (WAN) or over the Internet.
• Endpoint NAC describes how to use FortiGate endpoint NAC to enforce the use of
FortiClient End Point Security (Enterprise Edition) in your network.
• Wireless Controller describes how to configure a FortiGate unit to act as a wireless
network controller, managing the wireless Access Point (AP) functionality of FortiWiFi
units
• Log&Report describes how to enable logging, view log files, and view the basic reports
available through the web-based manager.
Document conventions
Fortinet technical documentation uses the conventions described below.
IP addresses
To avoid publication of public IP addresses that belong to Fortinet or any other
organization, the IP addresses used in Fortinet technical documentation are fictional and
follow the documentation guidelines specific to Fortinet. The addresses used are from the
private IP address ranges defined in RFC 1918: Address Allocation for Private Internets,
available at http://ietf.org/rfc/rfc1918.txt?number-1918.
Caution: Warns you about commands or procedures that could have unexpected or
undesirable results including loss of data or damage to equipment.
Note: Presents useful information, usually focused on an alternative, optional method, such
as a shortcut, to perform a step.
Tip: Highlights useful additional information, often tailored to your workplace activity.
Typographical conventions
Fortinet documentation uses the following typographical conventions:
Table 1: Typographical conventions in Fortinet technical documentation
Convention Example
Button, menu, text box, From Minimum log level, select Notification.
field, or check box label
CLI input* config system dns
set primary <address_ipv4>
end
CLI output FGT-602803030703 # get system settings
comments : (null)
opmode : nat
Emphasis HTTP connections are not secure and can be intercepted by a third
party.
File content <HTML><HEAD><TITLE>Firewall
Authentication</TITLE></HEAD>
<BODY><H4>You must authenticate to use this
service.</H4>
Hyperlink Visit the Fortinet Technical Support web site,
https://support.fortinet.com.
Keyboard entry Type a name for the remote VPN peer or client, such as
Central_Office_1.
Navigation Go to VPN > IPSEC > Auto Key (IKE).
Convention Description
Square brackets [ ] A non-required word or series of words. For example:
[verbose {1 | 2 | 3}]
indicates that you may either omit or type both the verbose word and
its accompanying option, such as:
verbose 3
Angle brackets < > A word constrained by data type.
To define acceptable input, the angled brackets contain a descriptive
name followed by an underscore ( _ ) and suffix that indicates the
valid data type. For example:
<retries_int>
indicates that you should enter a number of retries, such as 5.
Data types include:
• <xxx_name>: A name referring to another part of the
configuration, such as policy_A.
• <xxx_index>: An index number referring to another part of the
configuration, such as 0 for the first static route.
• <xxx_pattern>: A regular expression or word with wild cards
that matches possible variations, such as *@example.com to
match all email addresses ending in @example.com.
• <xxx_ipv4>: An IPv4 address, such as 192.168.1.99.
• <xxx_ipv4range>: An IPv4 address range.
• <xxx_ipv4/mask>: A dotted decimal IPv4 address and CIDR-
notation netmask separated by a slash, such as such as
192.168.1.99/24.
• <xxx_ipv6>: An IPv6 address.
• <xxx_v6mask>: A dotted decimal IPv6 netmask.
• <xxx_ipv6mask>: A dotted decimal IPv6 address and netmask
separated by a space.
• <xxx_str>: A string of characters that is not another data type,
such as P@ssw0rd. Strings containing spaces or special
characters must be surrounded in quotes or use escape
sequences
• <xxx_int>: An integer number that is not another data type,
such as 15 for the number of minutes.
Training
Fortinet Training Services provides a variety of training programs to serve the needs of
our customers and partners world-wide. Visit the Fortinet Training Services web site at
http://campus.training.fortinet.com, or email training@fortinet.com.
Fortinet documentation
The Fortinet Technical Documentation web site, http://docs.fortinet.com, provides the
most up-to-date versions of Fortinet publications, as well as additional technical
documentation such as technical notes.
In addition to the Fortinet Technical Documentation web site, you can find Fortinet
technical documentation on the Fortinet Tools and Documentation CD, and on the Fortinet
Knowledge Base.
Note: As noted in this section, some new features are available from the FortiGate CLI
only. See the FortiGate CLI Reference for more information about them.
• Reliable syslog
• Web filtering combined block/exempt list
• Web filtering by content header
• Safe search
• Data Leak Prevention supports international character sets
• SNMPv3 enhancements
• Schedule groups
• RAID support
FortiOS 4.0 provided software detection on endpoints. Using FortiOS 4.0 MR1, you can
now also allow or block endpoints based on detected software. The Software Detection
List is now called an Application Detection List and you can create multiple lists.
FortiGuard services provide all application signatures. You create your application
detection list entries by selecting applications from lists of categories, vendors, and
application names. Go to Endpoint NAC > Application Detection > Detection List to create
detection lists. To view application information from FortiGuard services, go to
Endpoint NAC > Application Detection > Predefined.
Endpoint check options are no longer configured in the firewall policy. These options and
the application detection list are now selected in an Endpoint NAC profile. In the firewall
policy, you simply enable Endpoint NAC and select the Endpoint NAC profile to apply.
For more information, see “Endpoint NAC” on page 687.
WCCP widget
Using the FortiOS 4.0 customizable GUI feature, you can add a WCCP widget to the
web-based manager and use this widget to add WCCP entries to the FortiGate
configuration.
For more information, see “Configuring WCCP” on page 183.
Single Sign-On
With the new single sign-on feature, a web bookmark can include login credentials to
automatically log the SSL VPN user into the web site. This means that once the user logs
into the SSL VPN, he or she does not have to enter any more credentials to visit
preconfigured web sites. When the administrator configures bookmarks, the web site
credentials must be the same as the user’s SSL VPN credentials. Users configuring their
own bookmarks can specify alternative credentials for the web site.
For more information, see “Bookmarks widget” on page 634.
OS Check changes
You can now configure the client operating system checks only in the CLI, but the
supported operating systems now include Windows Vista.
config vpn ssl web portal
edit <portal_name>
set os-check enable
config os-check-list {windows-2000 | windows-xp |
windows-vista}
set action {allow | check-up-to-date | deny}
set latest-patch-level {disable | 0 - 255}
set tolerance {tolerance_num}
end
Two-factor authentication
In FortiOS 4.0 MR1, PKI users can be required to authenticate by password in addition to
their certificate authentication, for both administrative and SSL VPN access. This two-
factor authentication provides additional security to meet ICSA 4.0 requirements.
For more information, see “Configuring peer users and peer groups” on page 657.
You can also configure two-factor authentication in an SSL VPN, by using these settings:
config vpn ssl settings
set force-two-factor-auth enable
end
If this option is enabled, only users with two-factor authentication can log in to the SSL
VPN.
Source based The FortiGate unit load balances sessions among ECMP routes based on the
(also called source IP address of the sessions to be load balanced.
source IP based)
Weighted (also The FortiGate unit load balances sessions among ECMP routes based on
called weights added to ECMP routes. More traffic is directed to routes with higher
weight-based) weights.
Spill-over (also The FortiGate unit distributes sessions among ECMP routes based on how busy
called the FortiGate interfaces added to the routes are.
usage-based)
For more information, see “ECMP route failover and load balancing” on page 322.
SCEP extensions
FortiOS 4.0 MR1 supports automatic update of system certificates. When a certificate is
about to expire, the FortiGate unit uses SCEP to request and download a new certificate.
This applies to both Local and CA certificates. You can also configure periodic updating of
a Certificate Revocation List (CRL).
Certificate auto-update is configured in the CLI.
Tip: An IPv6 command is often denoted by the number “6” at the end of the command.
The following dynamic routing commands were added or modified to support IPv6 traffic:
router access-list6
Use the new router access-list6 command to add, edit, or delete access lists for
IPv6 traffic. Access lists are filters used by FortiGate unit routing processes. For an access
list to take effect, it must be called by a FortiGate unit routing process (for example, a
process that supports RIPng or OSPF).
router ospf6
Use the new router ospf6 command to configure OSPF routing for IPv6 traffic.
router prefix-list6
Use the new router prefix-list6 command to add, edit, or delete prefix lists for IPv6
traffic. A prefix list is an enhanced version of an access list that allows you to control the
length of the prefix netmask.
router ripng
Use this command to configure FortiGate support for RIPng. RIPng is the next generation
(ng) version of RIP that supports IPv6. See RFC 2080 for details about RIPng for IPv6.
IPv6 DNS
In FortiOS 4.0 MR1, you can configure DNS server addresses for IPv6 traffic. For more
information about IPv6 DNS, see “Configuring Networking Options” on page 176.
Note: IPS for IPv6 traffic is supported using DoS policy in both Transparent and
NAT/Route mode (same as 4.0).
VDOM dashboard
In previous FortiOS versions, only administrators with the super_admin profile could view
the dashboard. In FortiOS 4.0 MR1, VDOM administrators see their own VDOM-specific
dashboard when they log in or go to System > Status. The super_admin can view only the
global dashboard.
For more information, see “VDOM and global dashboards” on page 68.
Password policy
Optionally, you can set a password policy to require more secure passwords than the
FortiGate defaults. The password policy can apply to administrators or IPsec VPN pre-
shared keys. You can:
• require the use of special characters in the password
• require periodic password changes
• set a minimum amount of change in the new password (available in CLI only).
For more information, see “Settings” on page 261.
Logging enhancements
Due to the new per-VDOM FortiAnalyzer unit feature, there are some general changes to
logging configuration.
CLI changes
In the CLI, the global FortiAnalyzer configuration has moved from
system fortianalyzer to log fortianalyzer setting. The keywords within the
command are unchanged.
• fortianalyzer override-setting
• syslogd override-setting
• antivirus quar-override-setting
Antivirus changes
For FortiOS 4.0 MR1, if you enable VDOMs, all UTM > Antivirus options are now
configured separately for each VDOM. In FortiOS 4.0 GA, only administrators with global
access could configure and manage the file quarantine, view the virus list, and configure
the grayware list.
In addition, the following antivirus functionality has been renamed or moved:
• Go to Log & Report > Quarantined Files to view the quarantined files list. The
functionality of the quarantined files list is unchanged except that with VDOMs
enabled, the Quarantined files list is now available for each VDOM and only shows
files quarantined from that VDOM.
• UTM > Antivirus > Quarantine was UTM > Antivirus > Config. Functionally is
unchanged.
• Go to UTM > Virus Database to view information about the current virus database on
the FortiGate unit. For FortiGate units that support the extended virus database, you
can go to UTM > Virus Database and select the virus database to use for virus
scanning. With VDOMs enabled, you select the virus database to use for virus
scanning for the VDOM.
• For FortiGate units that support the extended virus database, you can select the virus
database to use for individual protection profiles from the CLI. The Protection Profile
Antivirus > Extended AV Database option has been removed from the web-based
manager. New CLI options for selecting the antivirus database for a protection profile
are available for each protocol. For example, to select the antivirus database in the
scan protection profile for http and for FTP, enter:
config firewall profile
edit scan
set http-avdb {default | extended | normal}
set ftp-avdb {default | extended | normal}
end
• Go to UTM > Virus Database to enable grayware detection. The previous UTM >
Grayware page has been removed and you can no longer enable or disable individual
grayware categories.
For more information, see “Selecting the virus database” on page 519.
Reliable syslog
Reliable syslog protects log information through authentication and data encryption and
ensures that the log messages are reliably delivered in order. FortiOS 4.0 MR1
implements the RAW profile of RFC 3195. You can configure this feature only in the CLI.
For more information, see “Remote logging to a syslog server” on page 707.
Safe search
FortiOS 4.0 MR1 can prevent users from disabling the safe search feature of the Google,
Yahoo!, or Bing search engines. This is important in environments such as education
where web filtering is used to block sites with inappropriate content. If users can bypass
the search engine safe search feature, the returned search results can contain
inappropriate material in either summary text or thumbnail images.
Safe search is enabled in the Web Filtering part of a protection profile.
For more information, see “Web Filtering options” on page 480.
To view the list of available character sets, enter set http-post-lang ? from within
the edit shell for the profile.
For more information, see “Character sets and Web content filtering, Email filtering
banned word, and DLP scanning” on page 483.
SNMPv3 enhancements
FortiOS 4.0 introduced basic support for SNMPv3, the latest version of the Simple
Network Management Protocol. FortiOS Version 4.0 MR1 adds support for
• snmpEngineID
• user authentication and encryption capabilities.
You can configure these new features only in the CLI.
To specify engine-id
config system snmp sysinfo
set engine-id <string>
end
Schedule groups
You can now create schedule groups, similar to address groups or service groups. In a
firewall policy you can select either an individual schedule or a schedule group.
For more information, see “Configuring schedule groups” on page 413.
RAID support
Some FortiGate units that contain multiple hard disks also support redundant array of
independent disks (RAID). For more information, see “Configuring the RAID array” on
page 94.
Web-based manager
This section describes the features of the user-friendly web-based manager administrative
interface (sometimes referred to as a graphical user interface, or GUI) of your FortiGate
unit.
Using HTTP or a secure HTTPS connection from any management computer running a
web browser, you can connect to the FortiGate web-based manager to configure and
manage the FortiGate unit. The recommended minimum screen resolution for the
management computer is 1280 by 1024. Some of the information displayed by the
web-based manager uses features only supported by the most recent versions most
popular web browsers. Older versions of these web browsers may not always work
correctly with the web-based manager.
You can configure the FortiGate unit for HTTP and HTTPS web-based administration from
any FortiGate interface. To connect to the web-based manager you require a FortiGate
administrator account and password. The web-based manager supports multiple
languages, but by default appears in English on first use.
You can go to System > Status to view detailed information about the status of your
FortiGate unit on the system dashboard. The dashboard displays information such as the
current FortiOS firmware version, antivirus and IPS definition versions, operation mode,
connected interfaces, and system resources. It also shows whether the FortiGate unit is
connected to a FortiAnalyzer unit and a FortiManager unit or other central management
services.
You can use the web-based manager menus, lists, and configuration pages to configure
most FortiGate settings. Configuration changes made using the web-based manager take
effect immediately without resetting the FortiGate unit or interrupting service. You can
back up your configuration at any time using the Backup Configuration button on the
button bar. The button bar is located in the upper right corner of the web-based manager.
The saved configuration can be restored at any time.
The web-based manager also includes detailed context-sensitive online help. Selecting
Online Help on the button bar displays help for the current web-based manager page.
You can use the FortiGate command line interface (CLI) to configure the same FortiGate
settings that you can configure from the web-based manager, as well as additional CLI-
only settings. The system dashboard provides an easy entry point to the CLI console that
you can use without exiting the web-based manager.
This section describes:
• Common web-based manager tasks
• Changing your FortiGate administrator password
• Changing the web-based manager language
• Changing administrative access to your FortiGate unit
• Changing the web-based manager idle timeout
• Connecting to the FortiGate CLI from the web-based manager
• Button bar features
• Contacting Customer Support
• Backing up your FortiGate configuration
Note: See the Fortinet Knowledge Center article Recovering lost administrator account
passwords if you forget or lose an administrator account password and cannot log into your
FortiGate unit.
Note: You can also add new administrator accounts by selecting Create New. For more
information about adding administrators, changing administrator account passwords and
related configuration settings, see “System Admin” on page 241.
Contact Customer
Support
Online Help
Logout
Back up your FortiGate
configuration
You must register your Fortinet product to receive product updates, technical support, and
FortiGuard services. To register a Fortinet product, go to Product Registration and follow
the instructions.
Show Navigation Open the online help navigation pane. From the navigation pane you
can use the online help table of contents, index, and search to access
all of the information in the online help. The online help is organized in
the same way as the FortiGate web-based manager and the FortiGate
Administration Guide.
Previous Display the previous page in the online help.
Next Display the next page in the online help
Email Send an email to Fortinet Technical Documentation at
techdoc@fortinet.com if you have comments on or corrections for the
online help or any other Fortinet technical documentation product.
Print Print the current online help page.
Bookmark Add an entry for this online help page to your browser bookmarks or
favorites list to make it easier to find useful online help pages. Not
supported by all browsers.
When you select help for a VDOM configuration settings web-based
manager page the help display includes the VDOM icon. For
information about VDOM configuration settings, see “VDOM
configuration settings” on page 126.
When you select help for a Global configuration settings web-based
manager page the help display includes the Global icon. For
information about Global configuration settings, see “Global
configuration settings” on page 129.
To view the online help table of contents or index, and to use the search feature, select
Online Help in the button bar in the upper right corner of the web-based manager. From
the online help, select Show Navigation.
Figure 5: Online help page with navigation pane and content pane
Contents Display the online help table of contents. You can navigate through the
table of contents to find information in the online help. The online help
is organized in the same way as the FortiGate web-based manager
and the FortiGate Administration Guide.
Index Display the online help index. You can use the index to find
information in the online help.
Search Display the online help search. For more information, see “Searching
the online help” on page 54.
Show in Contents If you have used the index, search, or hyperlinks to find information in
the online help, the table of contents may not be visible or the table of
contents may be out of sync with the current help page. You can select
Show in Contents to display the location of the current help page
within the table of contents.
Go
Search
Field
Search
Results
Key Function
Alt+1 Display the table of contents.
Alt+2 Display the index.
Alt+3 Display the Search tab.
Alt+4 Go to the previous page.
Alt+5 Go to the next page.
Alt+7 Send an email to Fortinet Technical Documentation at
techdoc@fortinet.com if you have comments on or corrections for the
online help or any other Fortinet technical documentation product.
Alt+8 Print the current online help page.
Alt+9 Add an entry for this online help page to your browser bookmarks or
favorites list, to make it easier to find useful online help pages.
Logging out
The Logout button immediately logs you out of the web-based manager. Log out before
you close the browser window. If you simply close the browser or leave the web-based
manager, you remain logged in until the idle timeout (default 5 minutes) expires. To
change the timeout, see “Changing the web-based manager idle timeout” on page 50.
Menu
Delete
Edit
If you log in as an administrator with an admin profile that allows Read Only access to a
list, you will only be able to view the items on the list (see Figure 9).
View
• Endpoint NAC list of known endpoints (see “Monitoring endpoints” on page 693)
• Log and report log access list (see “Accessing and viewing log messages” on
page 714).
Filters are useful for reducing the number of entries that are displayed on a list so that you
can focus on the information that is important to you.
For example, you can go to System > Status, and, in the Statistics section, select Details
on the Sessions line to view the communications sessions that the FortiGate unit is
currently processing. A busy FortiGate unit may be processing hundreds or thousands of
communications sessions. You can add filters to make it easier to find specific sessions.
For example, you might be looking for all communications sessions being accepted by a
specific firewall policy. You can add a Policy ID filter to display only the sessions for a
particular Policy ID or range of Policy IDs.
You add filters to a web-based manager list by selecting any filter icon to display the Edit
Filters window. From the Edit Filters window you can select any column name to filter, and
configure the filter for that column. You can also add filters for one or more columns at a
time. The filter icon remains gray for unfiltered columns and changes to green for filtered
columns.
Figure 10: An intrusion protection predefined signatures list filtered to display all signatures
containing “apache” with logging enabled, action set to drop, and severity set to
high
Filter added to
display names that
include “apache” No filter added
The filter configuration is retained after leaving the web-based manager page and even
after logging out of the web-based manager or rebooting the FortiGate unit.
Different filter styles are available depending on the type of information displayed in
individual columns. In all cases, you configure filters by specifying what to filter on and
whether to display information that matches the filter, or by selecting NOT to display
information that does not match the filter.
Note: Filter settings are stored in the FortiGate configuration and will be maintained the
next time that you access any list for which you have added filters.
On firewall policy, IPv6 policy, predefined signature and log and report log access lists,
you can combine filters with column settings to provide even more control of the
information displayed by the list. See “Using filters with column settings” on page 63 for
more information.
Figure 11 shows a numeric filter configured to control the source addresses that are
displayed on the session list. In this example, a filter is enabled for the Source Address
column. The filter is configured to display only source addresses in the range of 1.1.1.1-
1.1.1.2. To view the session list, go to System > Status. In the Statistics section, beside
Sessions, select Details.
Figure 11: A session list with a numeric filter set to display sessions with source IP address
in the range of 1.1.1.1-1.1.1.2
Figure 12: A firewall policy list filter set to display all policies that do not include a source
address with a name that contains “My_Address”
Figure 13: An intrusion protection predefined signature list filter set to display all signatures
with Action set to block
Custom filters
Other custom filters are also available. You can filter log messages according to date
range and time range. You can also set the level filter to display log messages with
multiple severity levels.
Figure 14: A log access filter set to display all log messages with level of alert, critical, error,
or warning
• intrusion protection predefined signatures list (see “Viewing the predefined signature
list” on page 525)
• web filtering lists (see “Web Filter” on page 541)
• antispam lists (see “Email filtering” on page 559)
• Firewall user monitor list (see “Firewall user monitor list” on page 668)
• IPSec VPN Monitor (see “Monitoring VPNs” on page 618)
• Banned user list (see “NAC quarantine and the Banned User list” on page 670)
• log and report log access lists (see “Accessing and viewing log messages” on
page 714).
• Endpoint NAC list of known endpoints (see “Monitoring endpoints” on page 693)
Last Page
Note: Any changes that you make to the column settings of a list are stored in the FortiGate
configuration and will display the next time that you access the list.
To change column settings on a list that supports it, select Column Settings. From
Available fields, select the column headings to be displayed and then select the Right
Arrow to move them to the “Show these fields in this order” list. Similarly, to hide column
headings, use the Left Arrow to move them back to the Available fields list. Use Move Up
and Move Down to change the order in which to display the columns.
For example, you can change interface list column headings to display only the
IP/Netmask, MAC address, MTU, and interface Type for each interface.
Figure 18: A pre-defined signatures list displaying pre-defined signatures for the Veritas and
Winamp applications
For more information, see “Adding filters to web-based manager lists” on page 57.
Comment Hover the mouse pointer over this icon to view the text from
the Comment field.
Delete Delete an item. This icon appears in lists where the item can
be deleted and you have edit permission for the item.
Description The tooltip for this icon displays the Description or
Comments field for this table entry.
Diff Determine the differences between two revisions of the
FortiGate unit configuration.
Enter a VDOM Enter a virtual domain and use the web-based manager to
configure settings for the virtual domain.
Expand Arrow Expand this section to reveal more fields. This icon is used in
(closed) some dialog boxes and lists.
Expand Arrow Close this section to hide some fields. This icon is used in
(open) some dialog boxes and lists.
Filter Set a filter on one or more columns in this table. See “Adding
filters to web-based manager lists” on page 57.
System Status
This section describes the System Status page, the dashboard of your FortiGate unit. At a
glance you can view the current system status of the FortiGate unit including serial
number, uptime, FortiGuard™ license information, system resource usage, alert
messages and network statistics.
Note: Your browser must support Javascript to view the System Status page.
If you enable virtual domains (VDOMs) on the FortiGate unit, the status page is available
globally and system status settings are configured globally for the entire FortiGate unit.
The Topology viewer is not available when VDOMs are enabled. For details, see “Using
virtual domains” on page 125.
This section describes:
• Viewing the system dashboard
• Changing system information
• Changing the FortiGate firmware
• Viewing operational history
• Manually updating FortiGuard definitions
• Viewing Log and Archive Statistics
• Configuring the RAID array
• Configuring AMC modules
• Viewing application, policy, and DLP archive usage data
• Using the topology viewer
Note: The information on the System Status page applies to the whole HA cluster, not just
the primary unit. This includes information such as URLs visited, emails sent and received,
and viruses caught.
Global administrators with the super_admin admin profile can view only the
global dashboard.
History
Widget title Edit
Open/Close arrow Refresh
Close
System Information
Go to System > Status > Dashboard to find System Information.
To add the System Information widget to the dashboard go to System > Status >
Dashboard, select Add Content and select System Information from the list.
Serial Number The serial number of the FortiGate unit. The serial number is specific to the
FortiGate unit and does not change with firmware upgrades.
Uptime The time in days, hours, and minutes since the FortiGate unit was started.
System Time The current date and time according to the FortiGate unit’s internal clock.
Select Change to change the time or configure the FortiGate unit to get the
time from an NTP server. For more information, see “Configuring system time”
on page 86.
HA Status The status of high availability for this unit.
Standalone indicates the unit is not operating in HA mode.
Active-Passive or Active-Active indicate the unit is operating in HA mode.
Select Configure to configure the HA status for this unit. For more information,
see “HA” on page 205.
License Information
License Information displays the status of your technical support contract and FortiGuard
subscriptions. The FortiGate unit updates the license information status indicators
automatically when attempting to connect to the FortiGuard Distribution Network (FDN).
FortiGuard Subscriptions status indicators are green if the FDN was reachable and the
license was valid during the last connection attempt, grey if the FortiGate unit cannot
connect to the FDN, and orange if the FDN is reachable but the license has expired.
When a new FortiGate unit is powered on, it automatically searches for FortiGuard
services. If the unit is configured for central management, it will look for FortiGuard
services on the configured FortiManager system. The FortiGate unit sends its serial
number to the FortiGuard service provider, which then determines whether the FortiGate
unit is registered and has valid contracts for FortiGuard subscriptions and FortiCare
support services. If the FortiGate unit is registered and has a valid contract, the License
Information is updated.
If the FortiGate unit is not registered, any administrator with the super_admin profile sees
a reminder message that provides access to a registration form.
When a contract is due to expire within 30 days, any administrator with the super_admin
profile sees a notification message that provides access to an Add Contract form. Simply
enter the new contract number and select Add. Fortinet Support also sends contract
expiry reminders.
Optionally, you can disable notification for registration or contract inquiry.
Support Contract Displays details about your current Fortinet Support contract including
expiry dates and registration status.
• If Not Registered appears, select Register to register the unit.
• If Expired appears, select Renew for information on renewing your
technical support contract. Contact your local reseller.
• If Registered appears the name of the support that registered this
FortiGate unit is also displayed.
• You can select Login Now to log into the Fortinet Support account that
registered this FortiGate unit.
FortiGuard Services
AntiVirus The FortiGuard Antivirus version, license issue date and service status. If
your license has expired, you can select Renew to renew the license.
AV Definitions The currently installed version of the FortiGuard Antivirus definitions. To
update the definitions manually, select Update. For more information, see
“Manually updating FortiGuard definitions” on page 91.
Extended set The currently installed version of the extended FortiGuard Antivirus
definitions. For more information about the extended antivirus database,
see “Selecting the virus database” on page 519.
To update the definitions manually, select Update. For more information,
see “Manually updating FortiGuard definitions” on page 91.
The extended antivirus database is not available on all models.
Intrusion The FortiGuard Intrusion Prevention System (IPS) license version, license
Protection issue date and service status. If your license has expired, you can select
Renew to renew the license.
IPS Definitions The currently installed version of the IPS attack definitions. To update the
definitions manually, select Update. For more information, see “Manually
updating FortiGuard definitions” on page 91.
Web Filtering The FortiGuard Web Filtering license status, expiry date and service status.
If your license has expired, you can select Renew to renew the license.
Email Filtering The FortiGuard Email Filtering or Antispam license status, license expiry
date and service status. If your license has expired, you can select Renew
to renew the license.
Email Filtering The currently installed version of the FortiGuard Email Filtering rule set. To
Rule Set update the rule set manually, select Update. For more information, see
“Manually updating FortiGuard definitions” on page 91.
Analysis & The FortiGuard Analysis Service and Management Service license, license
Management expiry date, and reachability status. For more information, see “Configuring
Service FortiGuard Analysis & Management Service Options” on page 306.
Services Account Select Change to enter a different Service Account ID. This ID is used to
ID validate your license for subscription services such as FortiGuard
Management Service and FortiGuard Analysis Service. For more
information, see “Configuring FortiGuard Analysis & Management Service
Options” on page 306.
Virtual Domain
VDOMs Allowed The maximum number of virtual domains the unit supports with the current
license.
For high-end FortiGate models, you can select the Purchase More link to
purchase a license key through Fortinet technical support to increase the
maximum number of VDOMs. For more information, see “Adding VDOM
Licenses” on page 311.
Endpoint Security
FortiClient View information about the latest version of the FortiClient application
Software available from FortiGuard for EndPoint NAC. Select Download to download
Windows Installer the FortiClient application installer to your PC. For more information, see
“Configuring FortiClient installer download and version enforcement” on
page 688.
Application The version number of the current endpoint NAC application detection
Signature predefined signature package. For more information, see “Configuring
package application detection lists” on page 689.
Unit Operation
In the Unit Operation widget, an illustration of the FortiGate unit’s front panel shows the
status of the unit’s Ethernet network interfaces. If a network interface is green, that
interface is connected. Pause the mouse pointer over the interface to view the name, IP
address, netmask and current status of the interface.
If you select Reboot or ShutDown, a pop-up window opens allowing you to enter the
reason for the system event.
You can only have one management and one logging/analyzing method displayed for
your FortiGate unit. The graphic for each will change based on which method you choose.
If none are selected, no graphic is shown.
Caution: Abruptly powering off your FortiGate unit may corrupt its configuration. Using the
reboot and shutdown options here or in the CLI ensure proper shutdown procedures are
followed to prevent any loss of configuration.
Note: Your reason will be added to the Disk Event Log if disk logging, event logging, and
admin events are enabled. For more information on Event Logging, see “Configuring Event
logging” on page 711.
INT / EXT / DMZ / HA / The network interfaces on the FortiGate unit. The names and number of
WAN1 / WAN2 / 1 / 2 / these interfaces vary by model.
3/4 The icon below the interface name indicates its up/down status by color.
Green indicates the interface is connected. Grey indicates there is no
connection.
For more information about the configuration and status of an interface,
pause the mouse over the icon for that interface. A tooltip displays the full
name of the interface, its alias if one is configured, the IP address and
netmask, the status of the link, the speed of the interface, and the number
of sent and received packets.
AMC-SW1/1, ... If your FortiGate unit supports Advanced Mezzanine Card (AMC) modules
AMC-DW1/1, ... and if you have installed an AMC module containing network interfaces (for
example, the ASM-FB4 contains 4 interfaces) these interfaces are added to
the interface status display. The interfaces are named for the module, and
the interface. For example AMC-SW1/3 is the third network interface on the
SW1 module, and AMC-DW2/1 is the first network interface on the DW2
module.
AMC modules support hard disks as well, such as the ASM-S08 module.
When a hard disk is installed, ASM-S08 is visible as well as a horizontal bar
and percentage indicating how full the hard disk is.
You can also add the ASM-CX4 and ASM-FX2 modules to bridge FortiGate
interfaces when the FortiGate unit is operating in transparent mode.
For more information about AMC modules, see “Configuring AMC modules”
on page 98.
FortiAnalyzer The icon on the link between the FortiGate unit graphic and the
FortiAnalyzer graphic indicates the status of their OFTP connection. An ‘X’
on a red icon indicates there is no connection. A check mark on a green
icon indicates there is OFTP communication.
Select the FortiAnalyzer graphic to configure remote logging tot he
FortiAnalyzer unit on your FortiGate unit. For more information, see
“Remote logging to a FortiAnalyzer unit” on page 704.
FortiGuard Analysis The icon on the link between the FortiGate unit graphic and the FortiGuard
Service Analysis Service graphic indicates the status of their OFTP connection. An
‘X’ on a red icon indicates there is no connection. A check mark on a green
icon indicates there is OFTP communication.
Select the FortiGuard Analysis Service graphic to configure remote logging
to the FortiGuard Analysis Service. For more information, see the
FortiGuard Analysis and Management Service Administration Guide.
FortiManager The icon on the link between the FortiGate unit graphic and the
FortiManager graphic indicates the status of the connection. An ‘X’ on a red
icon indicates there is no connection. A check mark on a green icon
indicates there is communication between the two units.
Select the FortiManager graphic to configure central management on your
FortiGate unit. For more information, see “Central Management” on
page 260.
FortiGuard The icon on the link between the FortiGate unit graphic and the FortiGuard
Management Service Management Service graphic indicates the status of the connection. An ‘X’
on a red icon indicates there is no connection. A check mark on a green
icon indicates there is communication.
Select the FortiGuard Management Service graphic to configure central
management on your FortiGate unit. For more information, see “Central
Management” on page 260.
Reboot Select to shutdown and restart the FortiGate unit. You will be prompted to
enter a reason for the reboot that will be entered into the logs.
Shutdown Select to shutdown the FortiGate unit. You will be prompted for
confirmation, and also prompted to enter a reason for the shutdown that will
be entered into the logs.
System Resources
The System Resources widget displays basic FortiGate unit resource usage, such as
CPU and memory (RAM) usage. Any System Resources that are not displayed on the
status page can be viewed as a graph by selecting the History icon.
To see the most recent CPU and memory usage, select the Refresh icon.
View History
Edit
Refresh
Close
History A graphical representation of the last minute of CPU, memory, sessions, and
network usage. This page also shows the virus and intrusion detections over
the last 20 hours. For more information, see “Viewing operational history” on
page 90.
CPU Usage The current CPU status displayed as a dial gauge and as a percentage.
The web-based manager displays CPU usage for core processes only. CPU
usage for management processes (for example, for HTTPS connections to
the web-based manager) is excluded.
The displayed CPU usage is equivalent to using the CLI command get
system performance status and adding user, system, and nice
percentages. Both the web-based CPU Usage and the CLI command access
the same CPU information.
Memory Usage The current memory (RAM) status displayed as a dial gauge and as a
percentage.
The web-based manager displays memory usage for core processes only.
Memory usage for management processes (for example, for HTTPS
connections to the web-based manager) is excluded.
FortiAnalyzer Usage The current status of the FortiAnalyzer disk space used by this FortiGate
unit’s quota, displayed as a pie chart and a percentage.
You can use the System Resources edit menu to select not to display this
information.
This is available only if you have configured logging to a FortiAnalyzer unit.
Disk Usage The current status of the FortiGate unit disk space used, displayed as a pie
chart and a percentage.
This is available only if you have a hard disk on your FortiGate unit.
Close
Acknowledge this
message
The following types of messages can appear in the Alert Message Console:
System restart The system restarted. The restart could be due to operator
action or power off/on cycling.
System shutdown An administrator shut down the FortiGate unit from the
web-based manager or CLI.
Firmware upgraded by The named administrator upgraded the firmware to a more
<admin_name> recent version on either the active or non-active partition.
Firmware downgraded by The named administrator downgraded the firmware to an older
<admin_name> version on either the active or non-active partition.
FortiGate has reached connection The antivirus engine was low on memory for the duration of
limit for <n> seconds time shown and entered conserve mode. Depending on model
and configuration, content can be blocked or can pass
unscanned under these conditions.
Found a new FortiAnalyzer Shows that the FortiGate unit has either found or lost the
Lost the connection to FortiAnalyzer connection to a FortiAnalyzer unit. For more information, see
“Remote logging to a FortiAnalyzer unit” on page 704.
New firmware is available from An updated firmware image is available to be downloaded to
FortiGuard this FortiGate unit.
4 Select OK.
Refresh
Reset
Close
Close
Since The date and time when the counts were last reset.
Counts are reset when the FortiGate unit reboots, or when you select Reset.
Reset Reset the Log and Archive Statistic counts to zero.
DLP A summary of the HTTP, HTTPS, email, FTP IM, and VoIP (also called session
Archive control) traffic that has passed through the FortiGate unit, and has archived by DLP.
The Details pages list the last 64 items of the selected type and provides links to the
FortiAnalyzer unit where the archived traffic is stored. If logging to a FortiAnalyzer unit
is not configured, the Details pages provide a link to Log & Report > Log Config >
Log Settings.
You configure the FortiGate unit to collect DLP archive data for the widget by
configuring protection profiles to display content meta-information on the system
dashboard. To configure a protection profile, see “To configure a protection profile
(DLP archive)” on page 79.
You must also add the protection profile to a firewall policy. When the firewall policy
receives sessions for the selected protocols, meta-data is added to the statistics
widget.
The Email statistics are based on email protocols. POP3 and IMAP traffic is registered
as email received, and SMTP is email sent. If your FortiGate unit supports SSL content
scanning and inspection, incoming email also includes POP3S and IMAPS and
outgoing email also includes SMTPS. If incoming or outgoing email does not use these
protocols, these statistics will not be accurate.
The IM statistics are based on the AIM, ICQ, MSN, and Yahoo! protocols and
configured by selecting Archive in DLP Sensors for IM DLP rules.
The VoIP statistics are based on the SIP, SIMPLE and SCCP session control protocols
and configured by selecting Archive in DLP Sensors for Session Control DLP rules.
Log A summary of traffic, viruses, attacks, spam email messages, and blocked URLs that
the FortiGate unit has logged. Also displays the number of sessions matched by DLP
and event log messages. The Details pages list the 20 most recent items, providing the
time, source, destination and other information.
DLP data loss detected actually displays the number of sessions that have matched
DLP sensors added to protection profiles. DLP collects meta-data about all sessions
matched by DLP sensors and records this meta-data in the DLP log. Every time a DLP
log message is recorded, the DLP data loss detected number increases. If you are
using DLP for summary or full archiving the DLP data loss detected number can get
very large. This number may not indicate that data has been lost or leaked.
CLI Console
The System Status page can include a CLI console. To use the console, select it to
automatically log in to the admin account you are currently using in the web-based
manager. You can copy (CTRL-C) and paste (CTRL-V) text from or to the CLI Console.
Customize
The two controls located on the CLI Console widget title bar are Customize, and Detach.
Detach moves the CLI Console widget into a pop-up window that you can resize and
reposition. The two controls on the detached CLI Console are Customize and Attach.
Attach moves the CLI console widget back onto the System Status page.
Customize allows you to change the appearance of the console by defining fonts and
colors for the text and background.
Top Sessions
Top Sessions displays either a bar graph or a table showing the IP addresses that have
the most sessions currently open on the FortiGate unit. The sessions are sorted by their
source or destination IP address, or the port address. The sort criteria being used is
displayed in the top right corner.
The Top Sessions widget polls the FortiGate unit for session information, and this slightly
impacts the FortiGate unit performance. For this reason when this display is not shown on
the dashboard, it is not collecting data, and not impacting system performance. When the
display is shown, information is only stored in memory.
Note: Rebooting the FortiGate unit will reset the Top Session statistics to zero.
Number of Report By
active
sessions
Select Details to view the current sessions list, a list of all sessions currently processed by
the FortiGate unit. For more information, see “Viewing the current sessions list” on
page 82.
To view detailed information about the sessions represented by a bar in the chart, click on
the bar.
Sort Criteria Select the method used to sort the Top Sessions on the System Status
display. Choose one of:
• Source Address
• Destination Address
• Port Address
Display User Name Select to include the username associated with this source IP address, if
available. In the table display format this will be a separate column.
Display UserName is available only when the sort criteria is Source
Address.
Resolve Host Name Select to resolve the IP address to the host name.
Resolve Host Name is not available when the sort criteria is Destination
Port.
Resolve Service Select to resolve a port addresses into their commonly associated service
names. Any port address without a service, will continue to be displayed as
the port address. For example port 443 would resolve to HTTPS.
Resolve Service is only available when the sort criteria is Destination Port.
Display Format Select how the Top Session information is displayed. Choose one of:
• Chart
• Table
Top Sessions to Select the number of sessions to display. Choose to display 5, 10, 15, or 20
Show sessions.
Refresh Interval Select how often the display is updated. The refresh interval range is from
10 to 240 seconds. Selecting 0 will disable the automatic refresh of the
display. You will still be able to select the manual refresh option on the Top
Sessions title bar.
Shorter refresh intervals may impact the performance of your FortiGate
unit. If this occurs, try increasing the refresh interval or disabling the
automatic refresh.
Edit Filters
Edit the Top Sessions display Attach the widget to the dashboard
Delete a Session
Virtual Domain Select a virtual domain to list the sessions being processed by that virtual
domain. Select All to view sessions being processed by all virtual domains.
This is only available if virtual domains are enabled. For more information see
“Using virtual domains” on page 125.
Refresh Icon Update the session list.
First Page Select to go to the first displayed page of current sessions.
Previous Page Select to go to the page of sessions immediately before the current page
Page Enter the page number of the session to start the displayed session list. For
example if there are 5 pages of sessions and you enter 3, page 3 of the
sessions will be displayed.
The number following the ‘/’ is the number of pages of sessions.
Next Page Select to go to the next page of sessions.
Last Page Select to go to the last displayed page of current sessions.
Total The total number sessions.
Clear All Filters Select to reset any display filters that may have been set.
Return Return to the Top Sessions display.
Filter Icon The icon at the top of all columns except #, and Expiry. When selected it brings
up the Edit Filter dialog allowing you to set the display filters by column. See
“Adding filters to web-based manager lists” on page 57.
Protocol The service protocol of the connection, for example, udp, tcp, or icmp.
Source Address The source IP address of the connection.
Source Port The source port of the connection.
Destination The destination IP address of the connection.
Address
Destination Port The destination port of the connection.
Policy ID The number of the firewall policy allowing this session or blank if the session
involves only one FortiGate interface (admin session, for example).
Expiry (sec) The time, in seconds, before the connection expires.
Duration The age of each session in seconds. The age is the amount of time the session
has been active.
Delete icon Stop an active communication session. Your admin profile must include read
and write access to System Configuration.
Top Viruses
Top Viruses displays a bar graph representing the virus threats that have been detected
most frequently by the FortiGate unit.
The Top Viruses display is not part of the default dashboard display. It can be displayed by
selecting Add Content >Top Viruses from the drop down menu.
Selecting the history icon opens a window that displays up to the 20 most recent viruses
that have been detected with information including the virus name, when it was last
detected, and how many times it was detected. The system stores up to 1024 entries, but
only displays up to 20 in the web-based manager.
Selecting the edit icon for Top Viruses allows changes to the:
• refresh interval
• top viruses to show
Top Attacks
Top Attacks displays a bar graph representing the most numerous attacks detected by the
FortiGate unit.
The Top Attacks display is not part of the default dashboard display. It can be displayed by
selecting Add Content > Top Attacks from the drop down menu.
Selecting the history icon opens a window that displays up to the 20 most recent attacks
that have been detected with information including the attack name, when it was last
detected, and how many times it was detected. The FortiGate unit stores up to 1024
entries, but only displays up to 20 in the web-based manager.
Selecting the Edit icon for Top Attacks allows changes to the:
• refresh interval
• top attacks to show
Traffic History
The traffic history display shows the traffic on one selected interface over the last hour,
day, and month. This feature can help you locate peaks in traffic that you need to address
as well as their frequency, duration, and other information.
Only one interface at a time can be monitored. You can change the interface being
monitored by selecting Edit, choosing the interface from the drop down menu, and
selecting Apply. Doing this will clear all the traffic history data.
Interface being
monitored
RAID monitor
The RAID monitor display shows the current state of the RAID array and each RAID disk.
For information on configuring the RAID array, see “Configuring the RAID array” on page 94.
The RAID monitor display is not part of the default dashboard display. It can be displayed
by selecting Add Content > RAID Monitor from the drop down menu.
The RAID monitor will not be displayed unless your FortiGate unit has more than one disk
installed.
Configure Select to configure the RAID array, or rebuild a degraded array. For
more information, see “Configuring the RAID array” on page 94.
Array Status
Array status icon Shows the status of the RAID array.
Green with a check mark shows a healthy RAID array.
Yellow triangle shows the array is in a degraded state but it is still
functioning. A degraded array is slower than a healthy array. Rebuild
the array to fix the degraded state.
A wrench shows the array is being rebuilt.
Positioning the mouse over the array status icon displays a text
message of the status of the array.
Disk status icon There is one icon for each disk in the array.
Green with a check mark shows a healthy disk.
Red with an X shows the disk has failed and needs attention.
Positioning the mouse over the disk status icon displays the status of
the disk, and the storage capacity of the disk.
RAID Level The RAID level of this RAID array. The RAID level is set as part of
configuring the RAID array. For more information, see “RAID Level” on
page 96.
Disk Space Usage
Status bar The bar shows the percentage of the RAID array that is currently in
use.
Used/Free/Total These three numbers show the amount of RAID array storage that is
being used, the amount of storage that is free, and the total storage in
the RAID array. The values are in GB.
Used added to Free should equal Total.
Synchronizing status Display the percent complete of the RAID array synchronization.
Synchronizing may take several hours.
When synchronizing the status of the RAID array will indicate
synchronizing is happening in the background.
Synchronizing progress bar is visible only when the RAID array is
synchronizing.
You may need to select the refresh icon in the widget title bar to update
this progress bar.
Rebuild status Display the percent complete of the RAID array rebuild. Rebuilding the
array may take several hours.
While rebuilding the array, it is in a degraded and vulnerable state —
any disk failure during a rebuild will result in data loss.
A warning is displayed indicating the RAID array is running in reduced
reliability mode until the rebuild is completed.
You may need to select the refresh icon in the widget title bar to update
this progress bar.
Synchronize with Select to use a Network Time Protocol (NTP) server to automatically
NTP Server set the system date and time. You must specify the server and
synchronization interval.
FortiGate units use NTP Version 4. No RFC is currently available for
NTP version 4. The RCF for NTP Version 3 is RFC 1305. For more
information about NTP see http://www.ntp.org.
Server Enter the IP address or domain name of an NTP server. To find an NTP
server that you can use, see http://www.ntp.org.
Sync Interval Specify how often the FortiGate unit should synchronize its time with
the NTP server. For example, a setting of 1440 minutes causes the
FortiGate unit to synchronize its time once a day.
Note: If the FortiGate unit is part of an HA cluster, you should use a unique host name to
distinguish the unit from others in the cluster.
Note: To access firmware updates for your FortiGate model, you will need to register your
FortiGate unit with Customer Support. For more information go to
http://support.fortinet.com or contact Customer Support.
Caution: By installing an older firmware image, some system settings may be lost. You
should always backup your configuration before changing the firmware image.
For more information about using the USB disk, and the FortiGuard Network see “System
Maintenance” on page 289.
Upgrade From Select the firmware source from the drop down list of available sources.
Possible sources include Local Hard Disk, USB, and FortiGuard Network.
This field does not appear on all models.
Upgrade File Browse to the location of the firmware image on your local hard disk.
This field is available for local hard disk and USB only.
Allow Firmware Select to confirm the the installation of an older firmware image (downgrade).
Downgrade This field only displayed when attempting to downgrade firmware.
More Info Go to the FortiGuard Center to learn more about firmware updates through
the FortiGuard network.
Firmware changes either upgrade to a newer version or revert to an earlier version. Follow
the appropriate procedure to change your firmware.
For more information about managing firmware, see “Managing firmware versions” on
page 113.
Note: Installing firmware replaces the current antivirus and attack definitions with the
definitions included with the firmware release that you are installing. After you install new
firmware, use the procedure “To update antivirus and attack definitions” on page 307 to
make sure that antivirus and attack definitions are up to date.
Note: Installing firmware replaces the current antivirus and attack definitions with the
definitions included with the firmware release that you are installing. After you install new
firmware, use the procedure “To update antivirus and attack definitions” on page 307 to
make sure that antivirus and attack definitions are up to date.
Time Interval Select the time interval to display along the bottom axis of
the graphs.
CPU Usage History Percentage CPU usage for the preceding interval.
Memory Usage History Percentage memory usage for the preceding interval.
Session History Number of sessions over the preceding interval.
Network Utilization History Network utilization for the preceding interval.
Virus History Number of Viruses detected over the preceding interval.
Intrusion History Number of intrusion attempts detected over the preceding
interval.
Note: For information about configuring automatic FortiGuard updates, see “Configuring
FortiGuard Services” on page 300.
Date and Time The time when the URL was accessed.
From The IP address from which the URL was accessed.
URL The URL that was accessed.
Date and Time The time that the email passed through the FortiGate unit.
From The sender’s email address.
To The recipient’s email address.
Subject The subject line of the email.
Date and Time The time when the virus was detected.
From The sender’s email address or IP address.
To The intended recipient’s email address or IP address.
Service The service type, such as POP or HTTP.
Virus The name of the virus that was detected.
Date and Time The time that the attack was detected.
From The source of the attack.
To The target host of the attack.
Service The service type.
Attack The type of attack that was detected and prevented.
Date and Time The time that the spam was detected.
From->To IP The sender and intended recipient IP addresses.
From->To Email Accounts The sender and intended recipient email addresses.
Service The service type, such as SMTP, POP or IMAP.
SPAM Type The type of spam that was detected.
Date and Time The time that the attempt to access the URL was detected.
From The host that attempted to view the URL.
URL Blocked The URL that was blocked.
Date and Time The time that the attempt to access the URL was detected.
Service The service type, such as HTTP, SMTP, POP or IMAP.
Source The source address of the session.
From The host that attempted to view the URL.
URL Blocked The URL that was blocked.
From The sender’s email address or IP address.
To The intended recipient’s email address or IP address.
Caution: Do not remove a disk while the RAID array is synchronizing — you may loose
stored information. Also this will cause a degraded array and will require a rebuild.
Caution: A RAID array provides no redundancy in a degraded state. Any disk failure while
the raid is in a degraded state will cause data loss.
RAID Level
When changing the RAID level, the available levels depend on the number of working
disks that are actually present in the unit. For example, RAID 5 is not available on units
with fewer than three disks. When a disk fails, becomes corrupt, or is removed you must
rebuild the RAID array. For more information, see “Rebuilding the RAID array” on page 97.
If the FortiGate unit only has one disk installed, the RAID monitor widget will not be
displayed as it is not possible to configure a RAID array with only one disk.
Available RAID levels include:
• RAID 0
• RAID 1
• RAID 5
RAID 0
A RAID 0 array is also referred to as striping. The FortiGate unit writes information evenly
across all hard disks. The total space available is that of all the disks in the RAID array.
There is no redundancy available. If any single drive fails, the data on that drive cannot be
recovered. This RAID level is beneficial because it provides better performance, since the
FortiGate unit can distribute disk writing across multiple disks.
For example if your FortiGate unit has three disks each with a one TeraByte (TB) capacity,
your RAID 0 array will have a three TB capacity.
RAID 1
A RAID 1 array is also referred to as mirroring. The FortiGate unit writes information to
one hard disk, and writes a copy (a mirror image) of all information to all other hard disks.
The total disk space available is that of only one hard disk, as the others are solely used
for mirroring. This provides redundant data storage with no single point of failure. Should
any of the hard disks fail, there are several backup hard disks available. For example, if
one disk fails, the unit can still access three other hard disks and continue functioning.
In a RAID 1 array, if you have four disks of one TB capacity, the array will have a two TB
capacity. Since RAID 1 pairs disks for mirroring, if you have an odd number of disks then
one disk will not be used. If you have three disks, only two will be used in the RAID 1 array.
RAID 5
A RAID 5 array employs striping with a parity check. Similar to RAID 0, the FortiGate unit
writes information evenly across all drives but additional parity blocks are written on the
same stripes. The parity block is staggered for each stripe. The total disk space is the total
number of disks in the array, minus one disk for parity storage. For example, with four hard
disks, the total capacity available is actually the total for three hard disks. RAID 5
performance is typically better with reading than with writing, although performance is
degraded when one disk has failed or is missing. With RAID 5, one disk can fail without
the loss of data. If a drive fails, it can be replaced and the FortiGate unit will restore the
data on the new disk by using reference information from the parity volume.
Before you rebuild the RAID array, you should have a replacement disk for the one that
failed if that is the cause of the degraded array. You cannot rebuild an array that is missing
a disk. A replacement disk should be the same storage capacity as the disk it is replacing.
Also before rebuilding the array, you should backup the data if possible. As soon as the
RAID array becomes degraded you should backup the array if possible to prevent data
loss.
If you have added the name of a module to a slot and you are planning or removing the
module and replacing it with a different type of module (for example, if you are removing a
FortiGate-ASM-S08 and replacing it with a FortiGate-ASM-FX2) you should reset the slot
to the default before removing the module. Then after adding the new module you should
add its name to the slot.
You configure AMC slot settings from the FortiGate CLI using the config system amc
command. For information about this command, see the FortiGate CLI Reference.
In bypass mode all traffic flows between interfaces on the FortiGate-ASM-CX4 and
FortiGate-ASM-FX2 modules and not through the FortiGate unit. You can configure a
recovery watchdog to verify that the bridged FortiGate interfaces cannot process traffic. If
you fix the problem or the problem fixes itself, the recovery watchdog automatically
detects that traffic can resume and switches the module back to normal operation by
turning off bypass mode.
ASM-CX4 in slot 2:
amc-sw2/1 <--> amc-sw2/2: mode=normal
amc-sw2/3 <--> amc-sw2/4: mode=normal
Edit
Reset Refresh
Close
Edit
Reset Refresh
Close
Sort Criteria Select whether to sort the applications by number of Bytes or number
of Messages.
Report By Select Source Address or Destination Address.
Display User Name Select the check box to show the user name (when known) instead of
the IP address.
Resolve Host Name Select to use reverse-DNS lookup to determine the host name instead
of displaying the IP address.
VDOM Select the VDOM to monitor or select Global. This is available for
global administrators only. VDOM administrators see only their only
VDOM.
Display Format Select Chart or Table display.
Top Entries To Show Select whether to display top 5, 10, 15, or 20 applications.
Refresh Interval Select display update interval in seconds. Range 10 to 240 seconds.
Select 0 to disable updating. You can also update using the Refresh
icon in the module header.
Edit
Reset Refresh
Close
Edit
Reset Refresh
Close
Sort Criteria Select whether to sort the policies by number of Bytes or number of
Packets.
VDOM Select the VDOM to monitor or select Global. This is available for
global administrators only. VDOM administrators see only their only
VDOM.
Display Format Select Chart or Table display.
Top Entries To Show Select whether to display top 5, 10, 15, or 20 applications.
Refresh Interval Select display update interval in seconds. Range 10 to 240 seconds.
Select 0 to disable updating. You can also update using the Refresh
icon in the module header.
Edit
Reset Refresh
Close
The Topology page consists of a large canvas upon which you can draw a network
topology diagram of your FortiGate installation.
Zoom in. Select to display a smaller portion of the drawing area in the viewport, making
objects appear larger.
Zoom out. Select to display a larger portion of the drawing area in the viewport, making
objects appear smaller.
Add a subnet object to the diagram. The subnet object is based on the firewall address
that you select, and is connected by a line to the interface associated with that
address. See “Adding a subnet object” on page 110.
Insert Text. Select this control and then click on the diagram where you want to place
the text object. Type the text and then click outside the text box.
Delete. Select the object(s) to delete and then select this control or press the Delete
key.
Customize. Select to change the colors and the thickness of lines used in the drawing.
See “Customizing the topology diagram” on page 111.
Drag. Select this control and then drag objects in the diagram to arrange them.
Scroll. Select this control and then drag the drawing area background to move the
viewport within the drawing area. This has the same effect as moving the viewport
rectangle within the viewport control.
Select. Select this control and then drag to create a selection rectangle. Objects within
the rectangle are selected when you release the mouse button.
Select from existing Create a subnet object based on an existing firewall address. The
address/group object has the name of the firewall address and is connected by a line
to the interface associated with that address. For more information
about firewall addresses, see “Firewall Address” on page 395.
Address Name Enter a name to identify the firewall address. Addresses, address
groups, and virtual IPs must have unique names to avoid confusion in
firewall policies.
Connect to interface Select the interface or zone to associate with this address. If the field
already displays a name, changing the setting changes the interface
or zone associated with this existing address.
If the address is currently used in a firewall policy, you can choose
only the interface selected in the policy.
New addresses Create a new firewall address and add a subnet object based on that
address to the topology diagram. The address is associated with the
interface you choose.
Address Name Enter a name to identify the firewall address. Addresses, address
groups, and virtual IPs must have unique names to avoid confusion in
firewall policies.
Type Select the type of address: Subnet/IP Range or FQDN.
Subnet / IP Range If Type is Subnet / IP Range, enter the firewall IP address, followed by
a forward slash and then the subnet mask. Alternatively, enter IP
range start address, followed by a hyphen (-) and the IP range end
address.
FQDN If Type is FQDN, enter the fully qualified domain name.
Connect to interface Select the interface or zone to associate with this address.
Preview A simulated topology diagram showing the effect of the selected appearance
options.
Canvas Size The size of the drawing in pixels.
Resize to Image If you selected an image as Background, resize the diagram to fit within the
image.
Background One of:
Solid A solid color selected in Background Color.
U.S. Map A map of the United States.
World Map A map of the world.
Upload My Upload the image from Image Path
Image
Background Select the color of the diagram background.
Color
Image path If you selected Upload My Image for Background, enter the path to your image,
or use the Browse button to find it.
Exterior Color Select the color of the border region outside your diagram.
Line Color Select the color of connecting lines between subnet objects and interfaces.
Line Width Select the thickness of connecting lines.
Reset to Default Reset all topology diagram settings to default.
Note: For more information about the settings that are available on the Backup and
Restore page, (such as remotely backing up to a FortiManager unit), see “System
Maintenance” on page 289.
You can back up configuration settings to a local PC, a FortiManager unit, FortiGuard
Management server, or to a USB key. You can also back up to a FortiGuard Management
server if you have FortiGuard Analysis and Management Service enabled.
Fortinet recommends backing up all configuration settings from your FortiGate unit before
upgrading to FortiOS 4.0. This ensures all configuration settings are still available if you
require downgrading to FortiOS 3.0 MR7 and want to restore those configuration settings.
2 Enter the following to back up the configuration file to a TFTP or FTP server:
execute backup config {tftp | ftp} <backup_filename>
<tftp_server_ipaddress> <ftp server [:ftp port] <ftp_username>
<ftp_passwd> <encrypt_passwd>
3 Enter the following to back up the configuration to a FortiGuard Management server:
execute backup config management-station <comment>
After successfully backing up your configuration file, either from the CLI or the web-based
manager, proceed with upgrading to FortiOS 4.0.
The following procedure describes how to upgrade to FortiOS 4.0 in the web-based
manager. Fortinet recommends using the CLI to upgrade to FortiOS 4.0. The CLI upgrade
procedure reverts all current firewall configurations to factory default settings.
6 Select OK.
The FortiGate unit uploads the firmware image file, upgrades to the new firmware
version, restarts, and displays the FortiGate login. This process may take a few
minutes.
When the upgrade is successfully installed:
• ping to your FortiGate unit to verify there is still a connection.
• clear the browser’s cache and log in to the web-based manager.
After logging back in to the web-based manager, you should save the configuration
settings that carried forward. Some settings may have carried forward from FortiOS
3.0 MR7, while others may not have, such as certain IPS group settings. Go to System >
Maintenance > Backup and Restore to save the configuration settings that carried
forward.
Note: After upgrading to FortiOS 4.0, perform an “Update Now” to retrieve the latest
FortiGuard signatures from the FortiGuard Distribution Network (FDN) as these signatures
included in the firmware may be older than those currently available on the FDN.
The following procedure uses a TFTP server to upgrade the firmware. The CLI upgrade
procedure reverts all current firewall configurations to factory default settings.
See the Fortinet Knowledge Center article, Loading FortiGate firmware using TFTP for
CLI procedure, for additional information about upgrading firmware in the CLI.
The following procedure assumes that you have already downloaded the firmware image
to your management computer.
6 Type y.
The FortiGate unit uploads the firmware image file, upgrades to the new firmware
version, and restarts. This process takes a few minutes.
7 Reconnect to the CLI.
8 Enter the following command to confirm the firmware image installed successfully:
get system status
9 To update antivirus and attack definitions from the CLI, enter the following:
execute update-now
If you want to update antivirus and attack definitions from the web-based manager
instead, log in to the web-based manager and go to System > Maintenance >
FortiGuard.
When downgrading to a previous firmware, only the following settings are retained:
• operation mode
• Interface IP/Management IP
• route static table
• DNS settings
• VDOM parameters/settings
• admin user account
• session helpers
• system accprofiles.
If you created additional settings in FortiOS 4.0, make sure to back up the current
configuration before downgrading. For more information, see “Backing up your
configuration” on page 114.
When downgrading to a previous firmware, only the following settings are retained:
• operation mode
• Interface IP/Management IP
• route static table
• DNS settings
• VDOM parameters/settings
• admin user account
• session helpers
• system accprofiles.
If you have created additional settings in FortiOS 4.0, make sure you back up your
configuration before downgrading. For more information, see “Backing up your
configuration” on page 114.
The following procedure assumes that you have already downloaded the firmware image
to your management computer.
6 Type y.
The FortiGate unit uploads the firmware image file. After the file uploads, a message
similar to the following is displayed:
Get image from tftp server OK.
Check image OK.
This operation will downgrade the current firmware version!
Do you want to continue? (y/n)
7 Type y.
The FortiGate unit reverts to the old firmware version, resets the configuration to
factory defaults, and restarts. This process takes a few minutes.
After the FortiGate unit uploads the firmware, you need to reconfigure your IP address
since the FortiGate unit reverts to default settings, including its default IP address. See
your install guide for configuring IP addresses.
8 Reconnect to the CLI.
9 Enter the following command to confirm the firmware image installed successfully:
get system status
See “Restoring your configuration” on page 123 to restore you previous configuration
settings.
5 Enter the following command to copy the backed -up configuration file to restore the
file on the FortiGate unit:
execute restore allconfig <name_str> <tftp_ipv4> <passwrd>
Where <name_str> is the name of the backed up configuration file and
<tftp_ipv4> is the IP address of the TFTP server and <passwrd> is the password
you entered when you backed up your configuration settings. For example, if the
backed up configuration file is confall and the IP address of the TFTP server is
192.168.1.168 and the password is ghrffdt123:
execute restore allconfig confall 192.168.1.168 ghrffdt123
The FortiGate unit responds with the message:
This operation will overwrite the current settings and the
system will reboot!
Do you want to continue? (y/n)
6 Type y.
The FortiGate unit uploads the backed up configuration file. After the file uploads, a
message, similar to the following, is displayed:
Getting file confall from tftp server 192.168.1.168
##
Restoring files...
All done. Rebooting...
This may take a few minutes.
Use the CLI show shell command to verify your settings are restored, or log in to the
web-based manager.
Virtual domains
Virtual domains (VDOMs) are a method of dividing a FortiGate unit into two or more virtual
units that function as multiple independent units. A single FortiGate unit is then flexible
enough to serve multiple departments of an organization, separate organizations, or to act
as the basis for a service provider’s managed security service.
Benefits of VDOMs
Some benefits of VDOMs are:
• Easier administration
• Continued security maintenance
• Savings in physical space and power
Easier administration
VDOMs provide separate security domains that allow separate zones, user authentication,
firewall policies, routing, and VPN configurations. Using VDOMs can also simplify
administration of complex configurations because you do not have to manage as many
routes or firewall policies at one time. For more information, see “VDOM configuration
settings” on page 126.
By default, each FortiGate unit has a VDOM named root. This VDOM includes all of the
FortiGate physical interfaces, modem, VLAN subinterfaces, zones, firewall policies,
routing settings, and VPN settings.
Also you can assign an administrator account restricted to that VDOM. If the VDOM is
created to serve an organization, this feature enables the organization to manage its own
configuration.
Management systems such as SNMP, logging, alert email, FDN-based updates and NTP-
based time setting use addresses and routing in the management VDOM to communicate
with the network. They can connect only to network resources that communicate with the
management virtual domain. The management VDOM is set to root by default, but you
can change it. For more information, see “Changing the management VDOM” on
page 139.
Note: During configuration on a FortiAnalyzer unit, VDOMs count toward the maximum
number of FortiGate units allowed by the FortiAnalyzer unit’s license. The total number of
devices registered can be seen on the FortiAnalyzer unit’s System Status page under
License Information.
If virtual domain configuration is enabled and you log in as the default super_admin, you
can go to System > Status and look at Virtual Domain in the License Information section to
see the maximum number of virtual domains supported on your FortiGate unit.
For more information on VDOMs, see the FortiGate VLANs and VDOMs Guide.
The following configuration settings are exclusively part of a virtual domain and are not
shared between virtual domains. A regular VDOM administrator sees only these settings.
The default super_admin can also access these settings, but must first select which
VDOM to configure.
Table 6: VDOM configuration settings
When virtual domains are enabled, the web-based manager and the CLI are changed as
follows:
• Global and per-VDOM configurations are separated. For more information, see “VDOM
configuration settings” on page 126, and “Global configuration settings” on page 129.
• A new VDOM entry appears under the System option.
• Within a VDOM, reduced dashboard menu options are available, and a new Global
option appears. Selecting Global exits the current VDOM.
• There is no operation mode option at the Global level.
• Only super_admin profile accounts can view or configure Global level options.
• Super_admin profile accounts can configure configurations for all VDOM.
• One or more administrators can be configured for each VDOM; however, these admin
accounts cannot edit settings for any VDOMs for which they are not configured.
When virtual domains are enabled, the current virtual domain is displayed at the bottom
left of the screen, in the format Current VDOM: <name of the virtual domain>.
VDOM licenses
All FortiGate units, except the 30B, support 10 VDOMs by default.
High-end FortiGate models support the purchase of a VDOM license key from customer
service to increase their maximum allowed VDOMs to 25, 50, 100, 250, or 500.
Configuring 250 or more VDOMs will result in reduced system performance.
Table 9: VDOM support by FortiGate model
Note: Your FortiGate unit has limited resources that are divided amongst all configured
VDOMs. These resources include system memory, and CPU. When running 250 or more
VDOMs, you cannot run Unified Threat Management (UTM) features such as proxies, web
filtering, or antivirus—your FortiGate unit can only provide basic firewall functionality.
Tip: If you do not have a System > Maintenance > License tab, your FortiGate model does
not support more than 10 VDOMs.
Note: VDOMs created on a registered FortiGate unit are recognized as real devices by
connected FortiAnalyzer units. FortiAnalyzer units include VDOMs in their total number of
registered devices. For example, if three FortiGate units are registered on a FortiAnalyzer
unit and they contain a total of four VDOMs, the total number of registered FortiGate units
on the FortiAnalyzer unit is seven units. For more information, see the FortiAnalyzer
Administration Guide.
Note: The VDOM names vsys_ha and vsys_fgfm are in use by the FortiGate unit. If
you attempt to name a new VDOM vsys_ha or vsys_fgfm, the FortiGate unit will
generate an error.
Note: When creating 250 or more VDOMs, you cannot enable UTM features such as
proxies, web filtering, and antivirus due to limited resources. Also when creating large
numbers of VDOMs, you may experience reduced performance. To improve performance
with multiple VDOMs, see “Configuring resource usage for individual VDOMs” on
page 141.
Disabling a VDOM
When you have multiple VDOMs configured, it can be useful to disable one VDOM
temporarily instead of deleting and re-creating it later.
Disabling can be used during initial configuration, equipment changes, or even a DoS
attack.
A disabled VDOM has en empty Enable checkbox. A VDOM with a greyed-out checkbox
is the management VDOM can cannot be disabled.
Re-enabling is simply a matter of checking the Enable box and answering the prompt.
To disable a VDOM
1 Log in as a super_admin profile admin.
2 Go to System > VDOM.
3 For the VDOM to be disabled, unselect the Enable checkbox.
4 Confirm your choice when prompted.
Disabled VDOM
Create New Select to add a new VDOM. Enter the new VDOM name and select OK.
The VDOM must not have the same name as an existing VDOM, VLAN or
zone. The VDOM name can have a maximum of 11 characters and must
not contain spaces.
Management Virtual Change the management VDOM to the selected VDOM in the list. The
Domain management VDOM is then grayed out in the Enable column. The default
management VDOM is root.
For more information, see “Changing the management VDOM” on
page 139.
Apply Select to save your changes to the Management VDOM.
Enable There are three states this column can be in.
• A green check mark indicates this VDOM is enabled, and that you can
select the Enter icon to change to that VDOM.
• An empty check box indicates this VDOM is disabled. When disabled,
the configuration of that VDOM is preserved. The Enter icon is not
available.
• A grayed-out check box indicates this VDOM is the management
VDOM. It cannot be deleted or changed to disabled; it is always active.
Name The name of the VDOM.
Operation Mode The VDOM operation mode, either NAT or Transparent.
When a VDOM is in Transparent mode, SNMP can display the
management address, address type and subnet
mask for that VDOM. For more information, see “SNMP” on page 213.
Interfaces The interfaces associated with this VDOM, including virtual interfaces.
Every VDOM includes an SSL VPN virtual interface named for that VDOM.
For the root VDOM this interface is ssl.root.
Comments Comments added by an admin when this VDOM was created.
Delete icon Delete the VDOM.
The Delete icon appears only when there are no configuration objects
associated with that VDOM. For example, you must remove all referring
interfaces, profiles, and so on before you can delete the VDOM.
If the icon does not appear and you do not want to delete all the referring
configuration, you can disable the VDOM instead. The disabled VDOM
configuration remains in memory, but the VDOM is not usable until it is
enabled.
Edit icon Change the description of the VDOM. The name of the VDOM cannot be
changed.
Enter icon Enter the selected VDOM.
After entering a VDOM you will only be able to view and change settings
specific to that VDOM.
This icon will not be displayed for disabled VDOMs.
Inter-VDOM links
An inter-VDOM link is a pair of interfaces that enable you to communicate between two
VDOMs internally without using a physical interface. Inter-VDOM links have the same
security as physical interfaces, but allow more flexible configurations that are not limited
by the number of physical interfaces on your FortiGate unit. As with all virtual interfaces,
the speed of the link depends on the CPU load, but generally it is faster than physical
interfaces. There are no MTU settings for inter-VDOM links. DHCP support includes inter-
VDOM links.
A packet can pass through an inter-VDOM link a maximum of three times. This is to
prevent a loop. When traffic is encrypted or decrypted, it changes the content of the
packets and this resets the inter-VDOM counter. However, using IPIP or GRE tunnels
does not reset the counter.
In HA mode, inter-VDOM links must have both ends of the link within the same virtual
cluster. DHCP over IPSec is supported for inter-VDOM links, however regular DHCP
services are not available.
To view inter-VDOM links, go to System > Network > Interface. When an inter-VDOM link
is created, it automatically creates a pair of virtual interfaces that correspond to the two
internal VDOMs. Each of the virtual interfaces is named using the inter-VDOM link name
with an added “0” or “1”. So if the inter-VDOM link is called “vlink” the interfaces are
“vlink0” and “vlink1”. Select the Expand Arrow beside the VDOM link to display the virtual
interfaces.
Up Down
Delete Edit
5 Enter the name for the new VDOM link, up to a maximum of 11 characters.
The name must not contain any spaces or special characters. Hyphens (“-”) and
underlines (“_”) are allowed. Remember that the name will have a “0” or “1” attached to
the end for the actual interfaces.
6 Configure VDOM link “0”.
7 Select the VDOM from the menu that this interface will connect to.
8 Enter the IP address and netmask for this interface.
9 Select the administrative access method or methods. Keep in mind that PING,
TELNET, and HTTP are less secure methods.
10 Optionally enter a description for this interface.
11 Repeat steps 7 through 10 for VDOM link “1”.
12 Select OK to save your configuration and return to the System > Interface screen.
Note: You can reassign or remove an interface or subinterface once the Delete icon is
displayed. Absence of the icon means that the interface is being used in a configuration
somewhere.
Tip: You can disable a VDOM instead of deleting it. Your configuration will be preserved,
saving time you would otherwise need to remove and reconfigure it. For more information,
see “Working with VDOMs and global settings” on page 134.
Note: If an admin account is assigned to a VDOM, that VDOM cannot be deleted until that
account is assigned to another VDOM or removed.
Note: You cannot change the management VDOM if any administrators are using RADIUS
authentication.
• The number of SSL VPN user sessions that can be started in a VDOM. When this limit
is reached the VDOM displays a system busy message instead of the login page when
a user attempts to login to start an SSL VPN session.
Static resources are controlled by limits in the FortiGate configuration. These limits vary by
model and are listed in the FortiGate Maximum Values Matrix. Limiting static resources
does not limit the amount of traffic that the VDOM process. Instead limiting static
resources controls the number of configuration elements that can be added to a VDOM.
You can set the following static resource limits:
• The number of VPN IPSec Phase 1 and Phase 2 tunnels that can be added to a VDOM
configuration. The number of tunnels is limited by the maximum values for the
FortiGate model.
• The number of Firewall policies, Protection Profiles, Firewall Addresses, Firewall
Address Groups, Firewall Custom Services, Firewall Service Groups, Firewall
One-Time Schedules, and Firewall Recurring Schedules that can be added to a VDOM
configuration.
• The number of Local Users and User Groups that can be added to a VDOM
configuration.
Figure 57: Configuring global resource limits that apply to all VDOMs
• The Maximum value limits the amount of the resource that can be used by the VDOM.
When you add a VDOM, all maximum resource usage settings are 0 indicating that
resource limits for this VDOM are controlled by the global resource limits. You do not
have to override the maximum settings unless you need to override global limits to
further limit the resources available for the VDOM. You cannot set maximum resource
usage higher in a VDOM than the corresponding global resource limit.
Note: To set global resource limits go to System > VDOM > Global Resources. See
“Setting VDOM global resource limits” on page 140
• The Guaranteed value represents the minimum amount of the resource available for
that VDOM. Setting the guaranteed value makes sure that other VDOMs do not use all
of a resource. A guaranteed value of 0 means that an amount of this resource is not
guaranteed for this VDOM. You only have to change guaranteed settings if your
FortiGate may become low on resources and you want to guarantee that a minimum
level is available for this VDOM.
System Network
This section describes how to configure your FortiGate unit to operate in your network.
Basic network settings include configuring FortiGate interfaces and DNS options. More
advanced configuration includes adding zones and VLAN subinterfaces to the FortiGate
network configuration. Optional configurations also include configuring the FortiGate unit
as a DNS server and an explicit web proxy server
If you enable virtual domains (VDOMs) on the FortiGate unit, you configure interface and
networking options globally for the entire FortiGate unit. All interface settings, including
adding interfaces to VDOMs, are part of the global configuration. You configure zones, the
modem interface, the DNS database, the explicit web proxy, and the Transparent mode
routing table separately for each VDOM. For more information, see “Using virtual
domains” on page 125.
Note: Unless stated otherwise, the term interface can refer to either a physical FortiGate
interface or to a virtual FortiGate VLAN subinterface.
Note: If you can enter both an IP address and a netmask in the same field, you can use the
short form of the netmask. For example, 192.168.1.100/255.255.255.0 can also be entered
as 192.168.1.100/24.
Configuring interfaces
Go to System > Network > Interface to configure FortiGate interfaces. Many interface
options are available. Different options are available in NAT/Route mode and in
Transparent mode.
Some of the options available include:
• modify the configuration of a physical interface
• add VLAN subinterfaces
• aggregate several physical interfaces into an IEEE 802.3ad aggregate interface (some
models)
• combine several physical interfaces into a redundant interface (some models)
• add loopback interfaces
• add wireless interfaces (FortiWiFi models) and service set identifiers (SSIDs)
• add VDOM links on FortiGate units with multiple VDOMs enabled
• configure the modem interface (on some models)
• detect interface status for gateway load balancing
• change the information displayed about the interfaces
• configure a virtual wireless access point (VAP) interface
Edit
Interface Link Status Aggregate Interface Delete
VLAN Interface
Figure 61: Example switch mode interface list (on supported models)
Switch Interface
AMC
Interfaces
Create New Select Create New to add a new interface. Depending on the model you can
add a VLAN interface, a loopback interface, a IEEE 802.3ad aggregated
interface, or a redundant interface.
• “Adding VLAN interfaces” on page 158
• “Adding loopback interfaces” on page 158
• “Adding 802.3ad aggregate interfaces” on page 159
• “Adding redundant interfaces” on page 160
When VDOMs are enabled, you can also select Create New to add Inter-
VDOM links. For more information see “Inter-VDOM links” on page 136.
Switch Mode On supported models, select Switch Mode to change between switch mode
and interface mode. Switch mode combines some FortiGate interfaces into one
switch with one IP address. Interface mode allows you to configure them as
separate interfaces.
On some FortiGate models you can also select Hub Mode. Hub mode is similar
to switch mode except that in hub mode the interfaces do not learn the MAC
addresses of the devices on the network they are connected to and may also
respond quicker to network changes. Normally, you would only select Hub
Mode if you are having network performance issues when operating with
switch mode. The configuration of the FortiGate unit is the same whether in
switch mode or hub mode.
Before switching modes, all configuration settings for the interfaces affected by
the change must be set to defaults. When you select Switch Mode the
web-based manager displays the list of affected interfaces.
See “Switch Mode” on page 150.
Show backplane Select to make FortiGate-5000 series backplane interfaces visible. Once
interfaces visible these interfaces can be configured as regular physical interfaces.
Column Settings Select to change the columns of information that are displayed on the interface
list. Fore more information, see “Using column settings to control the columns
displayed” on page 61.
Description icon Display a description for the interface is one has been added. For more
information, see “Configuring interface settings” on page 151.
Name The names of the physical interfaces on your FortiGate unit. This includes any
alias names that have been configured.
The names of the physical interfaces depend on the model. Some names
indicate the default function of the interface such as internal, external, wan1
(wide are network), wlan (wireless LAN) and dmz. Other names are more
generic such as port1, port20, and so on.
Some FortiGate models also include a modem interface named modem. See
“Configuring the modem interface” on page 170.
When you combine several interfaces into an aggregate or redundant
interface, only the aggregate or redundant interface is listed, not the
component interfaces. See “Adding 802.3ad aggregate interfaces” on
page 159 or “Adding redundant interfaces” on page 160.
On FortiGate models that support switch mode, the individual interfaces in the
switch are not displayed when in switch mode. For more information, see
“Switch Mode” on page 150.
If you have added VLAN interfaces, they also appear in the name list, below
the physical or aggregated interface to which they have been added. See the
FortiGate VLANs and VDOMs Guide.
If you have added loopback interfaces, they also appear in the interface list,
below the physical interface to which they have been added.
If you have software switch interfaces configured, you will be able to view
them. For more information, see “Adding software switch interfaces” on
page 169.
If you have interface mode enabled on a FortiGate model with a switch
interface, you will see multiple internal interfaces. If switch mode is enabled,
there will only be one internal interface. For more information see “Switch
Mode” on page 150.
If your FortiGate unit supports AMC modules and have installed an AMC
module containing interfaces (for example, the ASM-FB4 contains 4 interfaces)
these interfaces are added to the interface status display. The interfaces are
named amc-sw1/1, amc-dw1/2, and so on. sw1 indicates it is a single width or
double width card respectively in slot 1. The last number “/1” indicates the
interface number on that card - for the ASM-FB4 card there would be “/1”
through “/4”.
IP/Netmask The current IP address/netmask of the interface.
In VDOM mode, when VDOMs are not all in NAT or Transparent mode some
values may not be available for display and will be displayed as “-” instead.
When IPv6 Support is enabled on the web-based manager, IPv6 addresses
may be displayed in this column.
Access The administrative access configuration for the interface.
For more information, see “Configuring administrative access to an interface”
on page 165.
Administrative The administrative status for the interface.
Status If the administrative status is a green arrow, the interface is up and can accept
network traffic. If the administrative status is a red arrow, the interface is
administratively down and cannot accept traffic. To change the administrative
status of an interface, select the Edit icon to edit the interface and change the
Administrative Status setting for the interface.
Link Status The status of the interface physical connection. Link status can be either up or
down. If link status is up there is an active physical connection between the
physical interface and a network switch. If link status is down the interface is
not connected to the network or there is a problem with the connection. You
cannot change link status from the web-based manager.
Link status is only displayed for physical interfaces.
MAC The MAC address of the interface.
Mode Shows the addressing mode of the interface. The addressing mode can be
manual, DHCP, or PPPoE.
MTU The maximum number of bytes per transmission unit (MTU) for the interface.
See “Changing interface MTU packet size” on page 167.
Secondary IP Displays the secondary IP addresses added to the interface. See “Adding
secondary IP addresses to an interface” on page 167.
Switch Mode
Select switch mode to switch a group of related FortiGate interfaces to operate as a multi-
port switch with one IP address. Switch mode is available on FortiGate models with switch
hardware.
Note: From the FortiGate CLI you can also add software switch interfaces. See “Adding
software switch interfaces” on page 169.
The switch mode feature has two states - switch mode and interface mode. Switch mode
is the default mode with only one interface and one address for the entire internal switch.
Interface mode allows you to configure each of the internal switch physical interface
connections separately. This allows you to assign different subnets and netmasks to each
of the internal physical interface connections.
Selecting Switch Mode on the System > Network > Interface screen displays the Switch
Mode Management screen.
Caution: Before you are able to change between switch mode and interface mode all
configuration settings for the affected interfaces must be set to defaults. This includes
firewall policies, routing, DNS forwarding, DHCP services, VDOM interface assignments,
and routing. If they are not removed, you will not be able to switch modes, and you will see
an error message. The web-based manager displays the list of affected interfaces.
Switch Mode Select Switch Mode. Only one internal interface is displayed. This is the default
mode.
Interface Mode Select Interface Mode. All internal i nterfaces on the switch are displayed as
individually configurable interfaces.
Hub Mode On some FortiGate models you can select Hub Mode. Hub mode is similar to
switch mode except t hat in hub mode the interfaces do not learn the MAC
addresses of the devices on the network they are connected to and may also
respond quicker to network changes in some circumstances. You should only
select Hub Mode if you are having network performance issues when operating
with switch mode. The configuration of the FortiGate unit is the same whether
in switch mode or hub mode.
Name The name of the interface. You can specify and change the names of VLAN,
loopback, IEEE 802.3ad aggregated, and redundant interfaces.
You cannot change the name of an existing interface.
The interface display also includes the MAC address of the physical interface.
Alias Enter another name for the interface that will easily distinguish this interface from
another. This is available only for physical interfaces where you cannot configure
the name. The alias can be a maximum of 15 characters.
The alias name is not part of the interface name, but it will appear in brackets
beside the interface name. It will not appears in logs.
Link Status Indicates whether the interface is connected to a network (link status is Up) or not
(link status is Down).
Type When adding a new interface, set Type to the type of interface that you want to
add:
• Set Type to VLAN to add a VLAN interface. See“Adding VLAN interfaces” on
page 158
• Set Type to Loopback Interface to add a loopback interface. See “Adding
loopback interfaces” on page 158
• On some models you can set Type to 802.3ad Aggregate to add an aggregate
interface. See“Adding 802.3ad aggregate interfaces” on page 159)
• On some models you can set Type to Redundant Interface to add a redundant
interface. See“Adding redundant interfaces” on page 160
Other types include:
• Software Switch - a software switch interface. See “Adding software switch
interfaces” on page 169.
• Tunnel - a virtual IPSec VPN interface. See “Configuring virtual IPSec
interfaces” on page 164.
• VAP Interface - a wireless controller virtual access point (VAP or virtual AP)
interface. See “Configuring a virtual wireless access point” on page 698.
You cannot change the Type except when adding a new interface.
Interface Select the name of the physical interface to which to add a VLAN interface. Once
created, the VLAN interface is listed below its physical interface in the Interface
list.
You cannot change the physical interface of a VLAN interface except when
adding a new VLAN interface.
Displayed when Type is set to VLAN.
VLAN ID Enter the VLAN ID that matches the VLAN ID of the packets to be received by this
VLAN subinterface. You cannot change the VLAN ID except when add a new
VLAN interface.
The VLAN ID can be any number between 1 and 4094 and must match the VLAN
ID added by the IEEE 802.1Q-compliant router or switch connected to the VLAN
subinterface. For more information, see “Adding VLAN interfaces” on
page 158.
Displayed when Type is set to VLAN.
Virtual Domain Select the virtual domain to add the interface to.
Admin accounts with super-admin profile can change the Virtual Domain.
Physical This section has two different forms depending on the interface type:
Interface • Software switch interface - this section is a display-only field showing the
Members interfaces that belong to the software switch virtual interface. See “Adding
software switch interfaces” on page 169.
• 802.3ad aggregate or Redundant interface - this section includes available
interface and selected interface lists to enable adding or removing interfaces
from the interface. See “Adding 802.3ad aggregate interfaces” on page 159
and “Adding redundant interfaces” on page 160.
Available Select interfaces from this list to include in the grouped interface - either
Interfaces redundant or aggregate interface. Select the right arrow to add an interface to the
grouped interface.
Selected These interfaces are included in the aggregate or redundant interface.
interfaces Select the left arrow to remove an interface from the grouped interface.
For redundant interfaces, the interfaces will be activated during failover from the
top of the list to the bottom
Addressing Select the addressing mode for the interface.
mode • Select Manual and add an IP/Netmask for the interface. If IPv6 configuration is
enabled you can add both a IPv4 and an IPv6 IP address.
• Select DHCP to get the interface IP address and other network settings from a
DHCP server. See “Configuring DHCP on an interface” on page 161
• Select PPPoE to get the interface IP address and other network settings from
a PPPoE server. See “Configuring PPPoE on an interface” on page 162.
IP/Netmask If Addressing Mode is set to Manual, enter an IPv4 address/subnet mask for the
interface.
Two FortiGate interfaces cannot have IP addresses on the same subnet.
IPv6 Address If Addressing Mode is set to Manual and IPv6 support is enabled on the
web-based manager, enter an IPv6 address/subnet mask for the interface. A
single interface can have both an IPv4 and IPv6 address or just one or the other.
Enable one-arm Select to configure this interface to operate as a one-armed sniffer as part of
sniffer configuring a FortiGate unit to operate as an IDS appliance by sniffing packets for
attacks without actually receiving and otherwise processing the packets. Once the
interface is enabled for sniffing you cannot use the interface for other traffic. You
must add sniffer policies for the interface to actually sniff packets.
For more information on one-armed IPS, see “Firewall Policy Using one-arm
sniffer policies to detect network attacks” on page 382.
Enable explicit Select to enable explicit web proxying on this interface. When enabled, this
Web Proxy interface will be displayed on System > Network > Web Proxy under Listen on
Interfaces and web traffic on this interface will be proxied according to the Web
Proxy settings. For more information, see “Configuring the explicit web proxy” on
page 182.
Enable DDNS Select Enable DDNS to configure a Dynamic DNS service for this interface. For
more information, see “Configuring Dynamic DNS on an interface” on page 163.
Override To change the MTU, select Override default MTU value (1 500) and enter the
Default MTU MTU size based on the addressing mode of the interface
Value • 68 to 1 500 bytes for static mode
• 576 to 1 500 bytes for DHCP mode
• 576 to 1 492 bytes for PPPoE mode
• larger frame sizes if supported by the FortiGate model
Only available on physical interfaces. Virtual interfaces associated with a physical
interface inherit the physical interface MTU size.
For more information on MTU size, see “Changing interface MTU packet size” on
page 167.
Note: In Transparent mode, if you change the MTU of an interface, you must
change the MTU of all interfaces to match the new MTU.
Enable DNS Select to configure the interface to accept DNS queries. Select recursive or non-
Query recursive. For more information, see “Configuring FortiGate DNS services” on
page 177.
recursive Look up domain names in the FortiGate DNS database. If the entry is not found,
relay the request to the DNS servers configured under System > Network >
Options.
non- Look up domain names in the FortiGate DNS database. Do not relay the request
recursive to the DNS servers configured under System > Network > Options.
Administrative Select the types of administrative access permitted for IPv4 connections to this
Access interface.
Ipv6 Select the types of administrative access permitted for IPv6 connections to this
Administrative interface.
Access
HTTPS Allow secure HTTPS connections to the web-based manager through this
interface.
PING Interface responds to pings. Use this setting to verify your installation and for
testing.
HTTP Allow HTTP connections to the web-based manager through this interface. HTTP
connections are not secure and can be intercepted by a third party.
SSH Allow SSH connections to the CLI through this interface.
SNMP Allow a remote SNMP manager to request SNMP information by connecting to
this interface. See “Configuring SNMP” on page 214.
TELNET Allow Telnet connections to the CLI through this interface. Telnet connections are
not secure and can be intercepted by a third party.
Detect Interface Configure interface status detection for the main interface IP address. See
Status for “Configuring interface status detection for gateway load balancing” on page 165.
Gateway Load
Balancing
Secondary IP Add additional IPv4 addresses to this interface. Select the blue arrow to expand
Address or hide the section. See “Adding secondary IP addresses to an interface” on
page 167.
Description Enter a description up to 63 characters to describe the interface.
Administrative Select either Up (green arrow) or Down (red arrow) as the status of this interface.
Status Up indicates the interface is active and can accept network traffic.
Down indicates the interface is not active and cannot accept traffic.
4 Select OK.
Note: You can add an accelerated interface (FA2 interfaces) to an aggregate link, but you
will lose the FA2 acceleration. For example, if you aggregate two accelerated interfaces
you will get slower throughput than if the two interfaces were separate.
Interfaces included in an aggregate interface are not listed on the System > Network >
Interface list. You cannot configure the interface individually and it is not available for
inclusion in firewall policies, firewall virtual IPs, or routing.
Status Displays DHCP status messages as the interface connects to the DHCP
server and gets addressing information. Select Status to refresh the
addressing mode status message.
Status can be one of:
• initializing - No activity.
• connecting - interface attempts to connect to the DHCP server.
• connected - interface retrieves an IP address, netmask, and other
settings from the DHCP server.
• failed - interface was unable to retrieve an IP address and other
settings from the DHCP server.
Obtained The IP address and netmask leased from the DHCP server.
IP/Netmask Only displayed if Status is connected.
Status Displays PPPoE status messages as the FortiGate unit connects to the
PPPoE server and gets addressing information. Select Status to refresh the
addressing mode status message.
Only displayed if you selected Edit.
Status can be one of the following 4 messages.
initializing No activity.
connecting The interface is attempting to connect to the PPPoE server.
connected The interface retrieves an IP address, netmask, and other settings from the
PPPoE server.
When the status is connected, PPPoE connection information is displayed.
failed The interface was unable to retrieve an IP address and other information from
the PPPoE server.
Reconnect Select to reconnect to the PPPoE server.
Only displayed if Status is connected.
User Name The PPPoE account user name.
Password The PPPoE account password.
Unnumbered IP Specify the IP address for the interface. If your ISP has assigned you a block
of IP addresses, use one of them. Otherwise, this IP address can be the
same as the IP address of another interface or can be any IP address.
Initial Disc Timeout Enter Initial discovery timeout. Enter the time to wait before starting to retry a
PPPoE discovery.
Initial PADT timeout Enter Initial PPPoE Active Discovery Terminate (PADT) timeout in seconds.
Use this timeout to shut down the PPPoE session if it is idle for this number of
seconds. PADT must be supported by your ISP. Set initial PADT timeout to 0
to disable.
Distance Enter the administrative distance for the default gateway retrieved from the
PPPoE server. The administrative distance, an integer from 1-255, specifies
the relative priority of a route when there are multiple routes to the same
destination. A lower administrative distance indicates a more preferred route.
The default distance for the default gateway is 1.
Retrieve default Enable to retrieve a default gateway IP address from a PPPoE server. The
gateway from default gateway is added to the static routing table.
server
Override internal Enable to replace the DNS server IP addresses on the System DNS page
DNS with the DNS addresses retrieved from the PPPoE server.
When VDOMs are enabled, you can override the internal DNS only on the
management VDOM.
Server Select a DDNS server to use. The client software for these services is built into the
FortiGate firmware. The FortiGate unit can connect only to one of these services.
Domain Enter the fully qualified domain name of the DDNS service.
Username Enter the user name to use when connecting to the DDNS server.
Password Enter the password to use when connecting to the DDNS server.
IP If you want to use dynamic routing with the tunnel or be able to ping the tunnel
Remote IP interface, enter IP addresses for the local and remote ends of the tunnel. These
two addresses must not be used anywhere else in the network.
Administrative Select the types of administrative access permitted on this interface.
Access
HTTPS Allow secure HTTPS connections to the web-based manager through this
interface.
PING Allow the interface to respond to pings. Use this setting to verify your
installation and for testing.
HTTP Allow HTTP connections to the web-based manager through this interface.
HTTP connections are not secure and can be intercepted by a third party.
SSH Allow SSH connections to the CLI through this interface.
SNMP Allow a remote SNMP manager to request SNMP information by connecting to
this interface. See “Configuring SNMP” on page 214.
TELNET Allow Telnet connections to the CLI through this interface. Telnet connections
are not secure and can be intercepted by a third party.
Description Enter a description of the interface. It can be up to 63 characters.
Interface status detection is used for ECMP route failover and load balancing. See “ECMP
route failover and load balancing” on page 322.
Since its possible that a response may not be received, even if the server and the network
are operating normally, the dead gateway detection configuration controls the time interval
between testing the connection to the server and the number times the test can fail before
the FortiGate unit assumes that the interface cannot connect to the server. See
“Configuring Networking Options” on page 176 for information about configuring dead
gateway detection.
To configure gateway failover detection for an interface, from the web-based manager go
to System > Network > Interface and edit an interface. Select Detect Interface Status for
Gateway Load Balancing, enter the IP address of the server to test connecting to and
select one or more protocols to use to test the connection to the server. If you have added
secondary IP addresses to an interface you can also configure interface status detection
separately for each secondary IP address.
Note: As long as the FortiGate unit receives responses for at least one of the protocols that
you select, the FortiGate unit assumes the server is operating and can forward packets.
Responses received to more than one protocol does not enhance the status of the server
or interface and receiving responses from fewer protocols does not reduce the status of the
server or interface.
Note: For more information about TCP echo and UDP echo, see RFC 862.
Note: If you change the MTU, you need to reboot the FortiGate unit to update the MTU
value of VLAN subinterfaces on the modified interface.
Note: In Transparent mode, if you change the MTU of an interface, you must change the
MTU of all interfaces on the FortiGate unit to match the new MTU.
All of the IP addresses added to an interface are associated with the single MAC address
of the physical interface and all secondary IP addresses are in the same VDOM as the
interface that are added to. You configure interface status detection for gateway load
balancing separately for each secondary IP addresses. As with all other interface IP
addresses, secondary IP addresses cannot be on the same subnet as any other primary
or secondary IP address assigned to a FortiGate interface unless they are in separate
VDOMs.
Tip: After adding secondary IP addresses and selecting OK to save changes to the Edit
Interface dialog you should edit the interface again to make sure the secondary IP
addresses have been added as expected.
Edit
Delete
Administrative Select the types of administrative access permitted on the secondary IP.
Access
HTTPS Allow secure HTTPS connections to the web-based manager through this
secondary IP.
PING Allow secondary IP to respond to pings. Use this setting to verify your
installation and for testing.
HTTP Allow HTTP connections to the web-based manager through this secondary
IP. HTTP connections are not secure and can be intercepted by a third party.
SSH Allow SSH connections to the CLI through this secondary IP.
SNMP Allow a remote SNMP manager to request SNMP information by connecting
to this secondary IP. See “Configuring SNMP” on page 214.
TELNET Allow Telnet connections to the CLI through this secondary IP. Telnet
connections are not secure and can be intercepted by a third party.
OK Select to add the configured secondary IP address to the secondary IP table.
Addresses in this table are not added to the interface until you select OK or
Apply.
Secondary IP A table that displays all the secondary IP addresses that have been added to
address table this interface.
These addresses are not permanently added to the interface until you select
OK or Apply at the bottom of the Edit Interface dialog.
# The identifying number of the secondary IP address.
IP/Netmask The IP address and netmask for the secondary IP.
Detect Server Indicates whether interface status detection is enabled for the secondary IP
Enable address.
Detect Server The IP address of the detect server for the secondary IP address. The same
detect server can be shared by multiple secondary IP addresses.
Detect Protocol The detect protocols configured for the secondary IP address.
Administrative The administrative access methods for this address. They can be different
Access from the primary IP address.
Delete Icon Select to remove this secondary IP address.
Edit Icon Edit the selected secondary IP address. When you select the Edit icon the
settings for the secondary IP address to edit appear in the fields above the
secondary IP address table. You can edit these settings and select OK to
save changes to the secondary IP address.
Note: If you select the Edit icon to edit a secondary IP address and change
the IP/Netmask, when you select OK a new secondary IP address is added.
If you only wanted to change the IP/Netmask and not add a new secondary
IP address you should delete the secondary IP address that you selected the
Edit icon for.
Configuring zones
Group interfaces into zones to simplify policy creation. By grouping interfaces into a zone
you can add one set of firewall policies for the zone instead of adding separate policies for
each interface. Once you add interfaces to a zone you cannot configure policies for the
interfaces, but only for the zone.
You can add all types of interfaces to a zone (physical, VLAN, switch, and so on) and a
zone can consist of any combination of interface types. You can add zones, rename and
edit zones, and delete zones from the zone list. When you add a zone, you select the
names of the interfaces to add to the zone.
Zones are configured from virtual domains. If you have added multiple virtual domains to
your FortiGate configuration, make sure you are configuring the correct virtual domain
before adding or editing zones.
Edit
Delete
• You can connect a supported USB mode to any FortiGate model with a USB interface.
• You can connect a supported serial model to any FortiGate model with a serial modem
port.
• You can insert a supported PCMCIA modem into any FortiGate model with a PCMCIA
slot. Power off the FortiGate unit before inserting the PCMCIA modem. After inserting
the modem, when you power up the FortiGate unit it should automatically find the
modem and create the modem interface.
In NAT/Route mode the modem can be in one of two modes:
• In redundant (backup) mode, the modem interface automatically takes over from a
selected ethernet interface when that ethernet interface is unavailable.
• In standalone mode, the modem interface is the connection from the FortiGate unit to
the Internet.
In redundant or standalone mode when connecting to the ISP, you can configure the
FortiGate unit to automatically have the modem dial up to three dialup accounts until the
modem connects to an ISP.
Other models can connect to an external modem through a USB-to-serial converter. For
these models, you must configure modem operation using the CLI.
Initially modem interfaces are disabled, and must be enabled in the CLI to be visible in the
web-based manager. See the system modem command in the FortiGate CLI Reference.
Note: The modem interface is not the AUX port. While the modem and AUX port may
appear similar, the AUX port has no associated interface and is used for remote console
connection. The AUX port is only available on FortiGate models 1000A, 1000AFA2, and
3000A. For more information, see the config system aux command in the
FortiGate CLI Reference.
Note: You cannot configure and use the modem in Transparent mode.
Figure 76 shows the only the settings specific to standalone mode. The remaining settings
are common to both standalone and redundant modes and are shown in Figure 77.
The FortiGate unit disconnects the modem interface and switches back to the ethernet
interface when the ethernet interface is able to connect to its network. You can set a
holddown timer that delays the switch back to the ethernet interface to ensure it is stable
and fully active before switching the traffic.
The modem will disconnect after a period of network inactivity set by the value in idle
timeout. This saves money on dialup connection charges.
For the FortiGate unit to be able to switch from an ethernet interface to the modem, you
must select the name of the interface in the modem configuration and configure a ping
server for that interface. You must also configure firewall policies for connections between
the modem interface and other FortiGate interfaces.
Note: Do not add policies for connections between the modem interface and the ethernet
interface that the modem is backing up.
Redundant for From the list, select the interface to back up.
Holddown timer Enter the number of seconds to continue using the modem after the
network connectivity is restored.
Redial Limit Enter the maximum number of times to retry if the ISP does not answer.
Dialup Account 1 Enter the ISP phone number, user name and password for up to three
Dialup Account 2 dialup accounts.
Dialup Account 3
4 Select Apply.
5 Configure interface status detection for the ethernet interface the modem backs up.
See “Configuring interface status detection for gateway load balancing” on page 165.
6 Configure firewall policies for network connectivity through the modem interface.
See “Adding firewall policies for modem connections” on page 175.
Auto-dial Select if you want the modem to dial when the FortiGate unit restarts.
Dial on demand Select if you want the modem to connect to its ISP whenever there are
unrouted packets.
Idle timeout Enter the timeout duration in minutes. After this period of inactivity, the
modem disconnects.
Redial Limit Enter the maximum number of times to retry if the ISP does not answer.
Dialup Account 1 Enter the ISP phone number, user name and password for up to three
Dialup Account 2 dialup accounts.
Dialup Account 3
4 Select Apply.
5 Configure firewall policies for network connectivity through the modem interface.
See “Adding firewall policies for modem connections” on page 175.
6 Go to Router > Static and set device to modem to configure static routes to route
traffic to the modem interface.
See “Adding a static route to the routing table” on page 320.
Note: The modem must be in Standalone mode before connecting or disconnecting from a
dialup account.
DNS Settings
Primary DNS Server Enter the primary DNS server IP address.
Secondary DNS Server Enter the secondary DNS server IP address.
Local Domain Name Enter the domain name to append to addresses with no domain
portion when performing DNS lookups.
IPv6 DNS Settings
Primary DNS Server Enter the primary IPv6 DNS server IP address.
Secondary DNS Server Enter the secondary IPv6 DNS server IP address.
Dead Gateway Detection Configure interface status detection for one or more FortiGate
interfaces and use the dead gateway detection settings to configure
how interface status detection functions. For information, see
“Configuring interface status detection for gateway load balancing”
on page 165.
Detection Interval Enter a number in seconds to specify how often the FortiGate unit
detects interface status.
Fail-over Detection Enter the number of times that interface status tests fail before the
FortiGate unit assumes that the interface is no longer functioning.
DNS Servers
Several FortiGate functions use DNS, including alert email and URL blocking. You can
specify the IP addresses of the DNS servers to which your FortiGate unit connects. DNS
server IP addresses are usually supplied by your ISP.
You can configure FortiGate models numbered 100 and lower to obtain DNS server
addresses automatically. To obtain these addresses automatically, at least one FortiGate
unit interface must use the DHCP or PPPoE addressing mode. See “Configuring DHCP
on an interface” on page 161 or “Configuring PPPoE on an interface” on page 162.
FortiGate models 100 and lower can provide DNS Forwarding on their interfaces. Hosts
on the attached network use the interface IP address as their DNS server. DNS requests
sent to the interface are forwarded to the DNS server addresses that you configured or
that the FortiGate unit obtained automatically.
recursive Look up domain names in the FortiGate DNS database. If the entry is not
found, relay the request to the DNS servers configured under System >
Network > Options. Can be used for a split DNS configuration.
non-recursive Look up domain names in the FortiGate DNS database. Do not relay the
request to the DNS servers configured under System > Network > Options.
4 Go to System > Network > DNS Database and configure the FortiGate DNS database.
Add zones and entries as required. See “Configuring the FortiGate DNS database” on
page 180.
5 Configure the hosts on the internal network to use the FortiGate interface as their DNS
server.
If you are also using a FortiGate DHCP server to configure the hosts on this network,
add the IP address of the FortiGate interface to the DNS Server IP address list.
To configure a FortiGate interface to resolve DNS requests using only the FortiGate
DNS database
Configure a FortiGate interface to resolve DNS requests using the FortiGate DNS
database and to drop requests for host names that not in the FortiGate DNS database.
1 Go to System > Network > Options and add the IP addresses of a Primary and
Secondary DNS server.
These should be the DNS servers provided by your ISP or other public DNS servers.
The FortiGate unit uses these DNS servers for its own DNS lookups and can be used
to supply DNS look ups for your internal networks. See “Configuring Networking
Options” on page 176.
2 Go to System > Network > Interface and edit the interface connected to a network that
you want the FortiGate unit to be a DNS server for.
3 Select Enable DNS Query and select Non-Recursive.
When you select Non-Recursive only the entries in the FortiGate DNS database are
used.
4 Go to System > Network > DNS Database and configure the FortiGate DNS database.
Add zones and entries as required. See “Configuring the FortiGate DNS database” on
page 180.
5 Configure the hosts on the internal network to use the FortiGate interface as their DNS
server.
If you are also using a FortiGate DHCP server to configure the hosts on this network,
add the IP address of the FortiGate interface to the DNS Server IP address list.
Delete
Edit
Delete
Edit
IP Address Enter the host’s IP address (IPv4). Available if Type is Address (A).
IPv6 Address Enter the host’s IP address (IPv6). Available if Type is IPv6 Address (AAAA).
Canonical Name Enter the host’s fully qualified domain name. Available if Type is
Canonical Name (CNAME).
Preference Enter the MX preference value. Range 0 to 65 535. Available if Type is
Mail Exchange (Mx).
TTL (seconds) Enter the TTL value. Enter 0 to use the Zone TTL value.
Note: To enable protection profiles for explicit web proxy traffic, you must configure 2
VDOMs and use inter-VDOM routing to pass the web traffic between them.
Web proxies are configured for each VDOM when VDOMs are enabled.
For a more complete description of the FortiGate web proxy, including a configuration
example, see the FortiGate WAN Optimization, Web Cache, and Web Proxy User Guide.
To configure the explicit web proxy go to System > Network > Web Proxy.
Proxy FQDN Enter the fully qualified domain name (FQDN) for the proxy server.
This is the domain name to enter into browsers to access the proxy
server.
Max HTTP request length Enter the maximum length of an HTTP request. Larger requests
will be rejected.
Max HTTP message length Enter the maximum length of an HTTP message. Larger messages
will be rejected.
Add headers to Forwarded The web proxy server will forward HTTP requests to the internal
Requests network. You can include the following headers in those requests:
Client IP Header Enable to include the Client IP Header from the original HTTP
request.
Via Header Enable to include the Via Header from the original HTTP request.
X-forwarded-for Header Enable to include the X-Forwarded-For (XFF) HTTP header.
The XFF HTTP header identifies the originating IP address of a
web client or browser that is connecting through an HTTP proxy,
and the remote addresses it passed through to this point.
Front-end HTTPS Header Enable to include the Front-end HTTP Header from the original
HTTPS request.
Explicit Web Proxy Options Web proxies can be transparent or explicit. Transparent web proxy
does not modify the web traffic in any way, but just forwards it to the
destination. Explicit web proxy can modify web traffic to provide
extra services and administration.
Explicit web proxy is configured with the following options.
Enable Explicit Web Enable the explicit web proxy.
Proxy
Port Enter the explicit web proxy server port. To use the explicit proxy,
users must add this port to their web browser proxy configuration.
The default value of 0 means 8080.
Listen on Interfaces Displays the interfaces that are being monitored by the explicit web
proxy server.
Unknown HTTP version Select the action to take when the proxy server must handle an
unknown HTTP version request or message. Choose from either
Reject or Best Effort. The Reject option is more secure.
Configuring WCCP
Using the FortiOS 4.0 customizable GUI feature you can add a WCCP widget to the
web-based manager and use this widget to add WCCP entries to the FortiGate
configuration.
Configure settings for Web Cache Communication Protocol (WCCP) version 2 to optimize
web traffic, thus reducing transmission costs and downloading time.
When a web client (on a computer) makes a request for web content, WCCP allows the
routers on the local network to redirect the web content requests to the appropriate web
cache server on the local network. If the web cache server contains the information in the
web content request, the web cache server sends the content directly to the local client. If
the web cache does not contain the requested information, the web cache server will
download the HTTP information, cache it, and send it to the local client. The local client is
not aware this caching is taking place.
For web caching to function, local network traffic must be directed through one or more
routers that are able to forward the HTTP requests to the web cache servers. The
FortiGate unit can act as a WCCP version 2 enabled router and direct web content
requests to configured web cache servers.
The web caching will speed up downloads by not accessing remote websites for each
HTTP request. It will also reduce the amount of data a company network sends and
receives over the Internet, reducing costs.
To configure WCCP from the web-based manager, go to System > Admin > Admin Profile
and create a custom menu layout in your administrative profile and add the WCCP page. It
is in the Additional content category. See “Configuring an admin profile” on page 258.
Delete
Edit
Note: In NAT/Route mode the static routing table is located at System > Routing > Static.
Delete
Edit
System Wireless
This section describes how to configure the Wireless LAN interfaces on FortiWiFi units.
The majority of this section is applicable to all FortiWiFi units.
If you enable virtual domains (VDOMs) on the FortiGate unit, MAC filters and wireless
monitor are configured separately for each virtual domain. System wireless settings are
configured globally. For details, see “Using virtual domains” on page 125.
This section describes:
• FortiWiFi wireless interfaces
• Channel assignments
• Wireless settings
• Wireless MAC Filter
• Wireless Monitor
• Rogue AP detection
Channel assignments
Depending on the wireless protocol selected, you have specific channels available to you,
depending on what region of the world you are in. Set the channel for the wireless network
by going to System > Wireless > Settings. For more information see “Wireless settings” on
page 190.
The following tables list the channel assignments for wireless networks for each supported
wireless protocol.
Wireless settings
To configure the wireless settings, go to System > Wireless > Settings.
By default the FortiWiFi unit includes one wireless interface, called wlan. If you are
operating your FortiWiFi unit in access point mode, you can add up to three virtual
wireless interfaces. All wireless interfaces use the same wireless parameters. That is, you
configure the wireless settings once, and all wireless interfaces use those settings. For
details on adding more wireless interfaces, see “Adding a wireless interface” on page 191.
When operating the FortiWiFi unit in Client mode, radio settings are not configurable.
Note: You cannot add additional wireless interfaces when the FortiWiFi unit is in Client
mode or Monitoring mode.
Name Enter a name for the wireless interface. The name cannot be the same
as an existing interface, zone or VDOM.
Type Select Wireless.
Address Mode The wireless interface can only be set as a manual address. Enter a
valid IP address and netmask.
If the FortiWiFi is running in Transparent mode, this field does not
appear. The interface will be on the same subnet as the other interfaces.
Administrative Set the administrative access for the interface.
Access
4 In the Wireless Settings section, complete the following and select OK:
SSID Enter the wireless service set identifier (SSID) or network name for this
wireless interface. Users who want to use the wireless network must configure
their computers with this network name.
SSID Broadcast Select to broadcast the SSID. Broadcasting the SSID enables clients to
connect to your wireless network without first knowing the SSID. For better
security, do not broadcast the SSID. If the interface is not broadcast, there is
less chance of an unwanted user connecting to your wireless network. If you
choose not to broadcast the SSID, you need to inform users of the SSID so
they can configure their wireless devices.
Security mode Select the security mode for the wireless interface. Wireless users must use
the same security mode to be able to connect to this wireless interface.
None — has no security. Any wireless user can connect to the wireless
network.
WEP64 — 64-bit web equivalent privacy (WEP). To use WEP64 you must
enter a Key containing 10 hexadecimal digits (0-9 a-f) and inform wireless
users of the key.
WEP128 — 128-bit WEP. To use WEP128 you must enter a Key containing 26
hexadecimal digits (0-9 a-f) and inform wireless users of the key.
WPA — Wi-Fi protected access (WPA) security. To use WPA you must select
a data encryption method. You must also enter a pre-shared key containing at
least eight characters or select a RADIUS server. If you select a RADIUS
server the wireless clients must have accounts on the RADIUS server.
WPA2 — WPA with more security features. To use WPA2 you must select a
data encryption method and enter a pre-shared key containing at least eight
characters or select a RADIUS server. If you select a RADIUS server the
wireless clients must have accounts on the RADIUS server.
WPA2 Auto — the same security features as WPA2, but also accepts wireless
clients using WPA security. To use WPA2 Auto you must select a data
encryption method You must also enter a pre-shared key containing at least 8
characters or select a RADIUS server. If you select a RADIUS server the
wireless clients must have accounts on the RADIUS server.
Key Enter the security key. This field appears when selecting WEP64 or WEP128
security.
Data Encryption Select a data encryption method to be used by WPA, WPA2, or WPA Auto.
Select TKIP to use the Temporal Key Integrity Protocol (TKIP). Select AES to
use Advanced Encryption Standard (AES) encryption. AES is considered
more secure that TKIP. Some implementations of WPA may not support AES.
Pre-shared Key Enter the pre-shared key. This field appears when selecting WPA, WPA2, or
WPA2 Auto security.
RADIUS Server Select to use a RADIUS server when selecting WPA or WPA2 security. You
can use WPA or WPA2 Radius security to integrate your wireless network
configuration with a RADIUS or Windows AD server. Select a RADIUS server
name from the list. You must configure the Radius server by going to User >
RADIUS. For more information, see “RADIUS” on page 647.
RTS Threshold Set the Request to Send (RTS) threshold.
The RTS threshold is the maximum size, in bytes, of a packet that the
FortiWiFi will accept without sending RTS/CTS packets to the sending
wireless device. In some cases, larger packets being sent may cause
collisions, slowing data transmissions. By changing this value from the default
of 2346, you can configure the FortiWiFi unit to, in effect, have the sending
wireless device ask for clearance before sending larger transmissions. There
can still be risk of smaller packet collisions, however this is less likely.
A setting of 2346 bytes effectively disables this option.
Fragmentation Set the maximum size of a data packet before it is broken into smaller
Threshold packets, reducing the chance of packet collisions. If the packet is larger than
the threshold, the FortiWiFi unit will fragment the transmission. If the packet
size less than the threshold, the FortiWiFi unit will not fragment the
transmission.
A setting of 2346 bytes effectively disables this option.
Alternatively, you can create a deny list. Similar to the allow list, you can configure the
wireless interface to allow all connections except those in the MAC address list.
Using MAC address filtering makes it more difficult for a hacker using random MAC
addresses or spoofing a MAC address to gain access to your network. Note you can
configure one list per WLAN interface.
To allow or deny wireless access to wireless clients based on the MAC address of the
client wireless cards, go to System > Wireless > MAC Filter.
List Access Select to allow or deny the addresses in the MAC Address list from
accessing the wireless network.
MAC Address Enter the MAC address to add to the list.
Add Add the entered MAC address to the list.
Remove Select one or more MAC addresses in the list and select Remove to
deleted the MAC addresses from the list.
Wireless Monitor
Go to System > Wireless > Monitor to view information about your wireless network. In
Access Point mode, you can see who is connected to your wireless LAN. In Client mode,
you can see which access points are within radio range.
Clients list (AP mode) Real-time details about the client wireless devices that can
reach this FortiWiFi unit access point. Only devices on the
same radio band are listed.
MAC Address The MAC address of the connected wireless client.
IP Address The IP address assigned to the connected wireless client.
AP Name The name of the wireless interface that the client is connected
to.
Neighbor AP list (Client mode) Real-time details about the access points that the client can
receive.
MAC Address The MAC address of the connected wireless client.
SSID The wireless service set identifier (SSID) that this access point
broadcasts.
Channel The wireless radio channel that the access point uses.
Rate (M) The data rate of the access point in Mbits/s.
RSSI The received signal strength indication, a relative value
between 0 (minimum) and 255 (maximum).
Rogue AP detection
On models that support Rogue Access Point Detection, you can select Monitoring mode to
scan for available wireless access points. You can also enable scanning in the
background while the unit is in Access Point mode.
Refresh Interval Set time between information updates. none means no updates.
Refresh Updates displayed information now.
Inactive Access Points Select which inactive access points to show: all, none, those detected
less than one hour ago, or those detected less than one day ago.
Online A green checkmark indicates an active access point. A grey X indicates
that the access point is inactive.
SSID The wireless service set identifier (SSID) or network name for the
wireless interface.
MAC Address The MAC address of the Wireless interface.
Signal Strength /Noise The signal strength and noise level.
Channel The wireless radio channel that the access point uses.
Rate The data rate of the access point.
First Seen The data and time when the FortiWifi unit first detected the access point.
Last Seen The data and time when the FortiWifi unit last detected the access point.
Mark as ‘Accepted AP’ Select the icon to move this entry to the Accepted Access Points list.
Mark as ‘Rogue AP’ Select the icon to move this entry to the Rogue Access Points list.
Forget AP Return item to Unknown Access Points list from Accepted Access Points
list or Rogue Access Points list.
You can also enter information about accepted and rogue APs in the CLI without having to
detect them first. See the system wireless ap-status command in the FortiGate
CLI Reference.
System DHCP
This section describes how to use DHCP to provide convenient automatic network
configuration for your clients.
DHCP is not available in Transparent mode. DHCP requests are passed through the
FortiGate unit when it is in Transparent mode.
If you enable virtual domains (VDOMs) on the FortiGate unit, DHCP is configured
separately for each virtual domain. For details, see “Using virtual domains” on page 125.
This section describes:
• FortiGate DHCP servers and relays
• Configuring DHCP services
• Viewing address leases
Note: You can configure a Regular DHCP server on an interface only if the interface is a
physical interface with a static IP address. You can configure an IPSec DHCP server on an
interface that has either a static or a dynamic IP address.
You can configure one or more DHCP servers on any FortiGate interface. A DHCP server
dynamically assigns IP addresses to hosts on the network connected to the interface. The
host computers must be configured to obtain their IP addresses using DHCP.
If an interface is connected to multiple networks via routers, you can add a DHCP server
for each network. The IP range of each DHCP server must match the network address
range. The routers must be configured for DHCP relay.
To configure a DHCP server, see “Configuring a DHCP server” on page 201.
You can configure a FortiGate interface as a DHCP relay. The interface forwards DHCP
requests from DHCP clients to an external DHCP server and returns the responses to the
DHCP clients. The DHCP server must have appropriate routing so that its response
packets to the DHCP clients arrive at the FortiGate unit.
To configure a DHCP relay see “Configuring an interface as a DHCP relay agent” on
page 201.
DHCP services can also be configured through the Command Line Interface (CLI). See
the FortiGate CLI Reference for more information.
Note: You can not configure DHCP in Transparent mode. In Transparent mode DHCP
requests pass through the FortiGate unit.
Note: An interface must have a static IP before you configure a DHCP server on it.
These settings are appropriate for the default Internal interface IP address of
192.168.1.99. If you change this address to a different network, you need to change the
DHCP server settings to match.
Edit
Delete
Interface List of FortiGate interfaces. Expand each listed interface to view the Relay and
Servers.
Server Name/ Name of FortiGate DHCP server or IP address of DHCP server accessed by
Relay IP relay.
Type Type of DHCP relay or server: Regular or IPSec.
Enable Green check mark icon indicates that server or relay is enabled.
Add DHCP Server Select to configure and add a DHCP server for this interface.
icon
IP Assignment Configure how the IP addresses for an IPSec DHCP server are assigned to
Mode Dialup IPSec VPN users. Select:
• Server IP Range - The IPSec DHCP server will assign the IP addresses
as specified in IP Range, and Exclude Ranges.
• User-group defined method - The IP addresses will be assigned by a user
group used to authenticate the user. The user group is used to
authenticate XAUTH users. See “Dynamically assigning VPN client IP
addresses from a user group” on page 665.
When User-group defined method is selected, the IP Range fields are greyed
out, and the Exclude Ranges table and controls are not visible.
DNS Server 1 Enter the IP addresses of up to 3 DNS servers that the DHCP server assigns
DNS Server 2 to DHCP clients.
DNS Server 3
WINS Server 1 Add the IP addresses of one or two WINS servers that the DHCP server
WINS Server 2 assigns to DHCP clients.
Option 1 Enter up to three custom DHCP options that can be sent by the DHCP
Option 2 server. Code is the DHCP option code in the range 1 to 255. Option is an
Option 3 even number of hexadecimal characters and is not required for some option
codes. For detailed information about DHCP options, see RFC 2132, DHCP
Options and BOOTP Vendor Extensions.
Exclude Ranges
Add Add an range of IP addresses to exclude.
You can add up to 16 exclude ranges of IP addresses that the DHCP server
cannot assign to DHCP clients. No range can exceed 65536 IP addresses.
Starting IP Enter the first IP address of the exclude range.
End IP Enter the last IP address of the exclude range.
Delete icon Delete the exclude range.
System Config
This section describes the configuration of several non-network features, such as HA,
SNMP, custom replacement messages, and Operation mode.
If you enable virtual domains (VDOMs) on the FortiGate unit, HA, SNMP, and replacement
messages are configured globally for the entire FortiGate unit. Changing operation mode
is configured for each individual VDOM. For details, see “Using virtual domains” on
page 125.
This section describes:
• HA
• SNMP
• Replacement messages
• Operation mode and VDOM management access
HA
FortiGate high availability (HA) provides a solution for two key requirements of critical
enterprise networking components: enhanced reliability and increased performance. This
section contains a brief description of HA web-based manager configuration options, the
HA cluster members list, HA statistics, and disconnecting cluster members.
If you enable virtual domains (VDOMs) on the FortiGate unit, HA is configured globally for
the entire FortiGate unit. For details, see “Using virtual domains” on page 125.
For complete information about how to configure and operate FortiGate HA clusters see
the FortiGate HA Overview, the FortiGate HA Guide.
The following topics are included in this section:
• HA options
• Cluster members list
• Viewing HA statistics
• Changing subordinate unit host name and device priority
• Disconnecting a cluster unit from a cluster
HA options
Configure HA options so that a FortiGate unit can join a cluster or to change the
configuration of an operating cluster or cluster member.
To configure HA options so that a FortiGate unit can join an HA cluster, go to System >
Config > HA.
Note: FortiGate HA is not compatible with PPP protocols such as PPPoE. FortiGate HA is
also not compatible with DHCP. If one or more FortiGate unit interfaces is dynamically
configured using DHCP or PPPoE you cannot switch to operate in HA mode. Also, you
cannot switch to operate in HA mode if one or more FortiGate unit interfaces is configured
as a PPTP or L2TP client or if the FortiGate unit is configured for standalone session
synchronization.
If HA is already enabled, go to System > Config > HA to display the cluster members list.
Select Edit for the FortiGate unit with Role of master (also called the primary unit). When
you edit the HA configuration of the primary unit, all changes are synchronized to the other
units in the cluster.
You can configure HA options for a FortiGate unit with virtual domains (VDOMs) enabled
by logging into the web-based manager as the global admin administrator and going to
System > Config > HA. If HA is enabled, you will have to select Edit for the cluster member
before you see the virtual cluster configuration screen for that cluster unit. For more
information, see“Cluster members list” on page 209.
Note: If your FortiGate cluster uses virtual domains, you are configuring HA virtual
clustering. Most virtual cluster HA options are the same as normal HA options. However,
virtual clusters include VDOM partitioning options. Other differences between configuration
options for regular HA and for virtual clustering HA are described below and in the
FortiGate HA Overview and the FortiGate HA Guide.
Mode Select an HA mode for the cluster or return the FortiGate units in the cluster to
standalone mode. When configuring a cluster, you must set all members of the
HA cluster to the same HA mode. You can select Standalone (to disable HA),
Active-Passive, or Active-Active.
If virtual domains are enabled you can select Active-Passive or Standalone.
Device Priority Optionally set the device priority of the cluster unit. Each unit in a cluster can
have a different device priority. During HA negotiation, the unit with the highest
device priority usually becomes the primary unit.
In a virtual cluster configuration, each cluster unit can have two different device
priorities, one for each virtual cluster. During HA negotiation, the unit with the
highest device priority in a virtual cluster becomes the primary unit for that virtual
cluster.
Changes to the device priority are not synchronized. You can accept the default
device priority when first configuring a cluster. When the cluster is operating you
can change the device priority for different cluster units as required.
Group Name Enter a name to identify the cluster. The maximum length of the group name is 32
characters. The group name must be the same for all cluster units before the
cluster units can form a cluster. After a cluster is operating, you can change the
group name. The group name change is synchronized to all cluster units.
The default group name is FGT-HA. You can accept the default group name
when first configuring a cluster, however two clusters on the same network
cannot have the same group name. When the cluster is operating you can
change the group name, if required.
Password Enter a password to identify the cluster. The maximum password length is 15
characters. The password must be the same for all cluster units before the cluster
units can form a cluster.
The default is no password. You can accept the default password when first
configuring a cluster. When the cluster is operating, you can add a password, if
required. Two clusters on the same network must have different passwords.
Enable Session Select to enable session pickup so that if the primary unit fails, sessions are
pickup picked up by the cluster unit that becomes the new primary unit.
You must enable session pickup for session failover protection. If you do not
require session failover protection, leaving session pickup disabled may reduce
HA CPU usage and reduce HA heartbeat network bandwidth usage.
Session pickup is disabled by default. You can accept the default setting for
session pickup and later choose to enable session pickup after the cluster is
operating.
Port Monitor Select to enable or disable monitoring FortiGate interfaces to verify the monitored
interfaces are functioning properly and are connected to their networks.
If a monitored interface fails or is disconnected from its network, the interface
leaves the cluster and a link failover occurs. The link failover causes the cluster to
reroute the traffic being processed by that interface to the same interface of
another cluster unit that still has a connection to the network. This other cluster
unit becomes the new primary unit.
Port monitoring (also called interface monitoring) is disabled by default. Leave
port monitoring disabled until the cluster is operating and then only enable port
monitoring for connected interfaces.
You can monitor up to 16 interfaces. This limit only applies to FortiGate units with
more than 16 physical interfaces.
Heartbeat Select to enable or disable HA heartbeat communication for each interface in the
Interface cluster and set the heartbeat interface priority. The heartbeat interface with the
highest priority processes all heartbeat traffic. If two or more heartbeat interfaces
have the same priority, the heartbeat interface with the lowest hash map order
value processes all heartbeat traffic. The web-based manager lists interfaces in
alphanumeric order:
• port1
• port2 through 9
• port10
Hash map order sorts interfaces in the following order:
• port1
• port10
• port2 through port9
The default heartbeat interface configuration is different for each FortiGate unit.
This default configuration usually sets the priority of two heartbeat interfaces to
50. You can accept the default heartbeat interface configuration or change it as
required.
The heartbeat interface priority range is 0 to 512. The default priority when you
select a new heartbeat interface is 0.
You must select at least one heartbeat interface. If heartbeat communication is
interrupted, the cluster stops processing traffic. For more information about
configuring heartbeat interfaces, see the FortiGate HA Overview.
You can select up to 8 heartbeat interfaces. This limit only applies to FortiGate
units with more than 8 physical interfaces.
VDOM If you are configuring virtual clustering, you can set the virtual domains to be in
partitioning virtual cluster 1 and the virtual domains to be in virtual cluster 2. The root virtual
domain must always be in virtual cluster 1.
For more information about configuring VDOM partitioning, see the FortiGate HA
Overview.
If virtual domains are enabled, you can display the cluster members list to view the status
of the operating virtual clusters. The virtual cluster members list shows the status of both
virtual clusters including the virtual domains added to each virtual cluster.
To display the virtual cluster members list for an operating cluster log in as the global
admin administrator and go to System > Config > HA.
View HA Statistics Displays the serial number, status, and monitor information for each cluster
unit. See “Viewing HA statistics” on page 211.
Up and down arrows Changes the order of cluster members in the list. The operation of the
cluster or of the units in the cluster are not affected. All that changes is the
order of the units on the cluster members list.
Cluster member Illustrations of the front panels of the cluster units. If the network jack for an
interface is shaded green, the interface is connected. Pause the mouse
pointer over each illustration to view the cluster unit host name, serial
number, how long the unit has been operating (up time), and the interfaces
that are configured for port monitoring.
Hostname The host name of the FortiGate unit. The default host name of the
FortiGate unit is the FortiGate unit serial number.
• To change the primary unit host name, go to System > Status and select
Change beside the current host name.
• To change a subordinate unit host name, from the cluster members list
select the Edit icon for a subordinate unit.
Role The status or role of the cluster unit in the cluster.
• Role is MASTER for the primary (or master) unit
• Role is SLAVE for all subordinate (or backup) cluster units
Priority The device priority of the cluster unit. Each cluster unit can have a different
device priority. During HA negotiation, the unit with the highest device
priority becomes the primary unit.
The device priority range is 0 to 255.
Disconnect from Select to disconnect a selected cluster unit from the cluster. See
cluster “Disconnecting a cluster unit from a cluster” on page 212.
Viewing HA statistics
From the cluster members list, you can select View HA Statistics to display the serial
number, status, and monitor information for each cluster unit. To view HA statistics, go to
System > Config > HA and select View HA Statistics.
Refresh every Select to control how often the web-based manager updates the HA
statistics display.
Back to HA monitor Select to close the HA statistics list and return to the cluster members list.
Unit The host name and serial number of the cluster unit.
Status Indicates the status of each cluster unit.
A green check mark indicates that the cluster unit is operating normally.
A red X indicates that the cluster unit cannot communicate with the primary
unit.
Up Time The time in days, hours, minutes, and seconds since the cluster unit was last
started.
Monitor Displays system status information for each cluster unit.
CPU Usage The current CPU status of each cluster unit. The web-based manager
displays CPU usage for core processes only. CPU usage for management
processes (for example, for HTTPS connections to the web-based manager)
is excluded. For more information about CPU usage, see “System
Resources” on page 75.
Memory Usage The current memory status of each cluster unit. The web-based manager
displays memory usage for core processes only. Memory usage for
management processes (for example, for HTTPS connections to the
web-based manager) is excluded. For more information about memory
usage, see “System Resources” on page 75.
Active Sessions The number of communications sessions being processed by the cluster
unit.
Total Packets The number of packets that have been processed by the cluster unit since it
last started up.
Virus Detected The number of viruses detected by the cluster unit.
Network Utilization The total network bandwidth being used by all of the cluster unit interfaces.
Total Bytes The number of bytes that have been processed by the cluster unit since it
last started up.
Intrusion Detected The number of intrusions or attacks detected by Intrusion Protection running
on the cluster unit.
Figure 102: Changing the subordinate unit host name and device priority
Peer View and optionally change the subordinate unit host name.
Priority View and optionally change the subordinate unit device priority.
The device priority is not synchronized among cluster members. In a functioning cluster
you can change device priority to change the priority of any unit in the cluster. The next
time the cluster negotiates, the cluster unit with the highest device priority becomes the
primary unit.
The device priority range is 0 to 255. The default device priority is 128.
Serial Number Displays the serial number of the cluster unit to be disconnected from the cluster.
Interface Select the interface that you want to configure. You also specify the IP address
and netmask for this interface. When the FortiGate unit is disconnected, all
management access options are enabled for this interface.
IP/Netmask Specify an IP address and netmask for the interface. You can use this IP address
to connect to this interface to configure the disconnected FortiGate unit.
SNMP
Simple Network Management Protocol (SNMP) allows you to monitor hardware on your
network. You can configure the hardware, such as the FortiGate SNMP agent, to report
system information and send traps (alarms or event messages) to SNMP managers. An
SNMP manager, or host, is a typically a computer running an application that can read the
incoming trap and event messages from the agent and send out SNMP queries to the
SNMP agents. A FortiManager unit can act as an SNMP manager, or host, to one or more
FortiGate units.
Using an SNMP manager, you can access SNMP traps and data from any FortiGate
interface or VLAN subinterface configured for SNMP management access.
The FortiGate SNMP implementation is read-only. SNMP v1, v2c, and v3 compliant SNMP
managers have read-only access to FortiGate system information through queries and
can receive trap messages from the FortiGate unit.
To monitor FortiGate system information and receive FortiGate traps, you must first
compile the proprietary Fortinet and FortiGate Management Information Base (MIB) files.
A MIB is a text file that describes a list of SNMP data objects that are used by the SNMP
manager. These MIBs provide information the SNMP manager needs to interpret the
SNMP trap, event, and query messages sent by the FortiGate unit SNMP agent. For
information on how to download the MIB files, see the Fortinet Knowledge Base.
Note: There were major changes to the MIB files between FortiOS v3.0 and v4.0. You need
to use the new MIBs for FortiOS v4.0 or you may be accessing the wrong traps and fields.
The Fortinet implementation of SNMP includes support for most of RFC 2665 (Ethernet-
like MIB) and most of RFC 1213 (MIB II). For more information, see “Fortinet MIBs” on
page 217.
RFC support for SNMP v3 includes Architecture for SNMP Frameworks (RFC 3411), and
partial support of User-based Security Model (RFC 3414).
SNMP traps alert you to events that happen, such as an a log disk being full or a virus
being detected. For more information about SNMP traps, see “Fortinet and FortiGate
traps” on page 218.
SNMP fields contain information about your FortiGate unit, such as percent CPU usage or
the number of sessions. This information is useful to monitor the condition of the unit, both
on an ongoing basis and to provide more information when a trap occurs. For more
information about SNMP fields, see “Fortinet and FortiGate MIB fields” on page 221.
The FortiGate SNMP v3 implementation includes support for queries, traps,
authentication, and privacy. Authentication and encryption are configured in the CLI. See
the system snmp user command in the FortiGate CLI Reference.
Configuring SNMP
Go to System > Config > SNMP v1/v2c to configure the SNMP agent.
Note: When the FortiGate unit is in virtual domain mode, SNMP traps can only be sent on
interfaces in the management virtual domain. Traps cannot be sent over other interfaces.
Traps Enter the Local and Remote port numbers (port 162 for each by default) that
the FortiGate unit uses to send SNMP v1 and SNMP v2c traps to the SNMP
managers in this community. Select the Enable check box to activate traps for
each SNMP version.
Note: The SNMP client software and the Fortigate unit must use the same
port for traps.
SNMP Event Enable each SNMP event for which the FortiGate unit should send traps to the
SNMP managers in this community.
“CPU overusage” traps sensitivity is slightly reduced, by spreading values out
over 8 polling cycles. This prevents sharp spikes due to CPU intensive short-
term events such as changing a policy.
“Power Supply Failure” event trap is available only on some FortiGate models.
“AMC interfaces enter bypass mode” event trap is available only on FortiGate
models that support AMC modules.
Fortinet MIBs
The FortiGate SNMP agent supports Fortinet proprietary MIBs as well as standard RFC
1213 and RFC 2665 MIBs. RFC support includes support for the parts of RFC 2665
(Ethernet-like MIB) and the parts of RFC 1213 (MIB II) that apply to FortiGate unit
configuration.
There are two MIB files for FortiGate units - the Fortinet MIB, and the FortiGate MIB. The
Fortinet MIB contains traps, fields and information that is common to all Fortinet products.
The FortiGate MIB contains traps, fields and information that is specific to FortiGate units.
Each Fortinet product has its own MIB—if you use other Fortinet products you will need to
download their MIB files as well.
The Fortinet MIB and FortiGate MIB along with the two RFC MIBs are listed in tables in
this section. You can download the two FortiGate MIB files from Fortinet Customer
Support. For information on how to download the MIB files, see the Fortinet Knowledge
Base.
Note: There were major changes to the MIB files between FortiOS v3.0 and v4.0. You need
to use the new MIBs for FortiOS v4.0 or you may mistakenly access the wrong traps and
fields.
Your SNMP manager may already include standard and private MIBs in a compiled
database that is ready to use. You must add the Fortinet proprietary MIB to this database
to have access to the Fortinet specific information. You need to obtain and compile the
two MIBs for this release.
Replacement messages
Go to System > Config > Replacement Message to change replacement messages and
customize alert email and information that the FortiGate unit adds to content streams such
as email messages, web pages, and FTP sessions.
The FortiGate unit adds replacement messages to a variety of content streams. For
example, if a virus is found in an email message attachment, the file is removed from the
email and replaced with a replacement message. The same applies to pages blocked by
web filtering and email blocked by email filtering.
Reset
Edit
Name The replacement message category. Select the expand arrow to expand or collapse
the category. Each category contains several replacement messages that are used
by different FortiGate features. The replacement messages are described below.
Description A description of the replacement message.
Edit or view Select to change or view a replacement message.
icon
Reset icon Only displayed on the a VDOM replacement message list. Select to revert to the
global version of this replacement message.
Note: FortiOS uses HTTP to send the Authentication Disclaimer page for the user to accept
before the firewall policy is in effect. Therefore, the user must initiate HTTP traffic first in
order to trigger the Authentication Disclaimer page. Once the Disclaimer is accepted, the
user can send whatever traffic is allowed by the firewall policy.
Replacement messages can be text or HTML messages. You can add HTML code to
HTML messages. Allowed Formats shows you which format to use in the replacement
message. There is a limit of 8192 characters for each replacement message. The
following fields and options are available when editing a replacement message. Different
replacement messages have different sets of fields and options.
Example
The following is an example of a simple authentication page that meets the requirements
listed above.
<HTML><HEAD><TITLE>Firewall Authentication</TITLE></HEAD>
<BODY><H4>You must authenticate to use this service.</H4>
<FORM ACTION="/" method="post">
<INPUT NAME="%%MAGICID%%" VALUE="%%MAGICVAL%%" TYPE="hidden">
<TABLE ALIGN="center" BGCOLOR="#00cccc" BORDER="0"
CELLPADDING="15" CELLSPACING="0" WIDTH="320"><TBODY>
<TR><TH>Username:</TH>
<TD><INPUT NAME="%%USERNAMEID%%" SIZE="25" TYPE="text"> </TD></TR>
<TR><TH>Password:</TH>
<TD><INPUT NAME="%%PASSWORDID%%" SIZE="25" TYPE="password">
</TD></TR>
<TR><TD COLSPAN="2" ALIGN="center" BGCOLOR="#00cccc">
<INPUT NAME="%%STATEID%%" VALUE="%%STATEVAL%%" TYPE="hidden">
<INPUT NAME="%%REDIRID%%" VALUE="%%PROTURI%%" TYPE="hidden">
<INPUT VALUE="Continue" TYPE="submit"> </TD></TR>
</TBODY></TABLE></FORM></BODY></HTML>
Tag Description
%%AUTH_LOGOUT%% The URL that will immediately delete the current policy and close the
session. Used on the auth-keepalive page.
%%AUTH_REDIR_URL%% The auth-keepalive page can prompt the user to open a new window
which links to this tag.
%%CATEGORY%% The name of the content category of the web site.
%%DEST_IP%% The IP address of the request destination from which a virus was
received. For email this is the IP address of the email server that sent
the email containing the virus. For HTTP this is the IP address of web
page that sent the virus.
Tag Description
%%EMAIL_FROM%% The email address of the sender of the message from which the file was
removed.
%%EMAIL_TO%% The email address of the intended receiver of the message from which
the file was removed.
%%FAILED_MESSAGE%% The failed to login message displayed on the auth-login-failed page.
%%FILE%% The name of a file that has been removed from a content stream. This
could be a file that contained a virus or was blocked by antivirus file
blocking. %%FILE%% can be used in virus and file block messages.
%%FORTIGUARD_WF%% The FortiGuard - Web Filtering logo.
%%FORTINET%% The Fortinet logo.
%%LINK%% The link to the FortiClient Host Security installs download for the
Endpoint Control feature.
%%HTTP_ERR_CODE%% The HTTP error code. “404” for example.
%%HTTP_ERR_DESC%% The HTTP error description.
%%NIDSEVENT%% The IPS attack message. %%NIDSEVENT%% is added to alert email
intrusion messages.
%%OVERRIDE%% The link to the FortiGuard Web Filtering override form. This is visible
only if the user belongs to a group that is permitted to create FortiGuard
web filtering overrides.
%%OVRD_FORM%% The FortiGuard web filter block override form. This tag must be present
in the FortiGuard Web Filtering override form and should not be used in
other replacement messages.
%%PROTOCOL%% The protocol (http, ftp, pop3, imap, or smtp) in which a virus was
detected. %%PROTOCOL%% is added to alert email virus messages.
%%QUARFILENAME%% The name of a file that has been removed from a content stream and
added to the quarantine. This could be a file that contained a virus or
was blocked by antivirus file blocking. %%QUARFILENAME%% can be
used in virus and file block messages. Quarantining is only available on
FortiGate units with a local disk.
%%QUOTA_INFO%% Display information about the traffic shaping quota setting that is
blocking the user. Used in traffic quota control replacement messages.
%%QUESTION%% Authentication challenge question on auth-challenge page.
Prompt to enter username and password on auth-login page.
%%SERVICE%% The name of the web filtering service.
%%SOURCE_IP%% The IP address of the request originator who would have received the
blocked file. For email this is the IP address of the user’s computer that
attempted to download the message from which the file was removed.
%%TIMEOUT%% Configured number of seconds between authentication keepalive
connections. Used on the auth-keepalive page.
%%URL%% The URL of a web page. This can be a web page that is blocked by web
filter content or URL blocking. %%URL%% can also be used in http virus
and file block messages to be the URL of the web page from which a
user attempted to download a file that is blocked.
%%VIRUS%% The name of a virus that was found in a file by the antivirus system.
%%VIRUS%% can be used in virus messages
Management IP/Netmask Enter the management IP address and netmask. This must be a
valid IP address for the network from which you want to
manage the FortiGate unit.
Default Gateway Enter the default gateway required to reach other networks from the
FortiGate unit.
Interface IP/Netmask Enter a valid IP address and netmask for the network from which
you want to manage the FortiGate unit.
Device Select the interface to which the Interface IP/Netmask settings
apply.
Default Gateway Enter the default gateway required to reach other networks from the
FortiGate unit.
Gateway Device Select the interface to which the default gateway is connected.
Management access
Management access defines how administrators are able to log on to the FortiGate unit to
perform management tasks such as configuration and maintenance. Methods of access
can include local access through the console connection, or remote access over a
network or modem interface using various protocols including Telnet and HTTPS.
You can configure management access on any interface in your VDOM. See “Configuring
administrative access to an interface” on page 165. In NAT/Route mode, the interface IP
address is used for management access. In Transparent mode, you configure a single
management IP address that applies to all interfaces in your VDOM that permit
management access. The FortiGate also uses this IP address to connect to the FDN for
virus and attack updates (see “Configuring FortiGuard Services” on page 300).
The system administrator (admin) can access all VDOMs, and create regular
administrator accounts. A regular administrator account can access only the VDOM to
which it belongs. The management computer must connect to an interface in that VDOM.
It does not matter to which VDOM the interface belongs. In both cases, the management
computer must connect to an interface that permits management access and its IP
address must be on the same network. Management access can be via HTTP, HTTPS,
telnet, or SSH sessions if those services are enabled on the interface. HTTPS and SSH
are preferred as they are more secure.
You can allow remote administration of the FortiGate unit. However, allowing remote
administration from the Internet could compromise the security of the FortiGate unit. You
should avoid this unless it is required for your configuration. To improve the security of a
FortiGate unit that allows remote administration from the Internet:
• Use secure administrative user passwords.
• Change these passwords regularly.
• Enable secure administrative access to this interface using only HTTPS or SSH.
• Use Trusted Hosts to limit where the remote access can originate from.
• Do not change the system idle timeout from the default value of 5 minutes (see
“Settings” on page 261).
System Admin
This section describes how to configure administrator accounts on your FortiGate unit.
Administrators access the FortiGate unit to configure its operation. The factory default
configuration has one administrator, admin. After connecting to the web-based manager
or the CLI, you can configure additional administrators with various levels of access to
different parts of the FortiGate unit configuration.
If you enable virtual domains (VDOMs) on the FortiGate unit, system administrators are
configured globally for the entire FortiGate unit. For details, see “Using virtual domains” on
page 125.
Note: Always end your FortiGate session by logging out, in the CLI or the web-based
manager. If you do not, the session remains open.
Administrators
There are two levels of administrator accounts:
Regular An administrator with any admin profile other than super_admin. A regular
administrators administrator account has access to configuration options as determined by its
Admin Profile. If virtual domains are enabled, the regular administrator is
assigned to one VDOM and cannot access global configuration options or the
configuration for any other VDOM. For information about which options are global
and which are per VDOM, see “VDOM configuration settings” on page 126 and
“Global configuration settings” on page 129.
System Includes the factory default system administrator admin, any other administrators
administrators assigned to the super_admin profile, and any administrator that is assigned to the
super_admin_readonly profile. Any administrator assigned to the super_admin
admin profile, including the default administrator account admin, has full access
to the FortiGate unit configuration and general system settings that includes the
ability to:
• enable VDOM configuration
• create VDOMs
• configure VDOMs
• assign regular administrators to VDOMs
• configure global options
• customize the FortiGate web-based manager.
The super_admin admin profile cannot be changed; it does not appear in the list
of profiles in System > Admin > Admin Profile, but it is one of the selections in the
Admin Profile drop-down list in System > Admin New/Edit Administrator dialog
box.
Figure 109: New Administrator dialog box displaying super_admin readonly option
Note: The password of users with the super_admin admin profile can be reset in the CLI. If
the password of a user who is logged in is changed, the user will be logged out and
prompted to re-authenticate with the new password.
Example: For the user ITAdmin with the admin profile super_admin, to set that user’s
password to 123456:
config sys admin
edit ITAdmin
set password 123456
end
Example: For the user ITAdmin with the admin profile super_admin, to reset the password
from 123456 to the default ‘empty’:
config sys admin
edit ITAdmin
unset password 123456
end
There is also an admin profile that allows read-only super admin privileges called
super_admin_readonly. This profile cannot be deleted or changed, similar to the
super_admin profile. The read-only super_admin profile is suitable in a situation where it is
necessary for a system administrator to troubleshoot a customer configuration without
being able to make changes. Other than being read-only, the super_admin_readonly
profile can view all the FortiGate configuration tools.
You can authenticate an administrator by using a password stored on the FortiGate unit, a
remote authentication server (such as LDAP, RADIUS, or TACACS+), or by using PKI
certificate-based authentication. To authenticate an administrator with an LDAP or
TACACS+ server, you must add the server to an authentication list, include the server in a
user group, and associate the administrator with the user group. The RADIUS server
authenticates users and authorizes access to internal network resources based on the
admin profile of the user. Users authenticated with the PKI-based certificate are permitted
access to internal network resources based on the user group they belong to and the
associated admin profile.
A VDOM/admin profile override feature supports authentication of administrators via
RADIUS. The admin user will have access depending on which VDOM and associated
admin profile he or she is restricted to. This feature is available only to wildcard
administrators, and can be set only through the FortiGate CLI. There can only be one
VDOM override user per system. For more information, see the FortiGate CLI Reference.
Change password
Delete
Edit
Local Authentication of an account with a local password stored on the FortiGate unit.
Remote Authentication of a specific account on a RADIUS, LDAP, or TACACS+ server.
Remote+ Authentication of any account on an LDAP, RADIUS, or TACACS+ server.
Wildcard
PKI PKI-based certificate authentication of an account.
Delete icon Delete the administrator account.
You cannot delete the original “admin” account until you create another user with
the super_admin profile, log out of the “admin” account, and log in with the
alternate user that has the super_admin profile.
Edit or View Edit or view the administrator account.
icon
Change Change the password for the administrator account. See “Changing an
Password administrator account password” on page 246.
icon
Trusted Host #1 Enter the trusted host IP address and netmask this administrator login is
Trusted Host #2 restricted to on the FortiGate unit. You can specify up to three trusted hosts.
Trusted Host #3 These addresses all default to 0.0.0.0/0 or 0.0.0.0/0.0.0.0.
For more information, see “Using trusted hosts” on page 254.
IPv6 Trusted Host #1 Enter the trusted host IPv6 address and netmask this administrator login is
IPv6 Trusted Host #2 restricted to on the FortiGate unit. You can specify up to three trusted hosts.
IPv6 Trusted Host #3 These addresses all default to ::/0.
For more information, see “Using trusted hosts” on page 254.
Admin Profile Select the admin profile for the administrator. You can also select Create New
to create a new admin profile. For more information on admin profiles, see
“Configuring an admin profile” on page 258.
Note: If you forget or lose an administrator account password and cannot log in to your
FortiGate unit, see the Fortinet Knowledge Base article Recovering lost administrator
account passwords.
Note: Access to the FortiGate unit depends on the VDOM associated with the administrator
account.
The following instructions assume there is a RADIUS server on your network populated
with the names and passwords of your administrators. For information on how to set up a
RADIUS server, see the documentation for your RADIUS server.
To view the RADIUS server list, go to User > Remote > RADIUS.
Delete
Edit
4 Select OK.
For further information about RADIUS authentication, see “Configuring a RADIUS server”
on page 648.
For more information about using a RADIUS server to authenticate system administrators,
see the Fortinet Knowledge Base article Using RADIUS for Admin Access and
Authorization.
• Admin profiles
• Configuring a RADIUS server
• Configuring a user group
Delete
Edit
Name The name that identifies the LDAP server on the FortiGate unit.
Server Name/IP The domain name or IP address of the LDAP server.
Server Port The TCP port used to communicate with the LDAP server.
Common Name The common name identifier for the LDAP server.
Identifier
Distinguished Name The base distinguished name for the server in the correct X.500 or
LDAP format.
Query icon View the LDAP server Distinguished Name Query tree for the LDAP
server that you are configuring so that you can cross-reference to the
Distinguished Name.
For more information, see “Using Query” on page 652.
Bind Type The type of binding for LDAP authentication.
Anonymous Bind using anonymous user search.
Regular Bind using a user name/password and then search.
Simple Bind using a simple password authentication without a search.
Filter Filter used for group searching. Available only if Bind Type is
Anonymous or Regular.
User DN Distinguished name of user to be authenticated. Available only if Bind
Type is Regular.
Password Password of user to be authenticated. Available only if Bind Type is
Regular.
Secure Connection A check box that enables a secure LDAP server connection for
authentication.
Protocol The secure LDAP protocol to use for authentication. Available only if
Secure Connection is selected.
Certificate The certificate to use for authentication. Available only if Secure
Connection is selected.
For further information about LDAP authentication, see “Configuring an LDAP server” on
page 650.
Password The password the administrator uses to authenticate. Not available if Wildcard
is enabled.
Confirm The re-entered password that confirms the original entry in Password. Not
Password available if Wildcard is enabled.
Admin Profile The admin profile to apply to the administrator.
4 Configure additional features as required. For more information, see “Configuring an
administrator account” on page 244.
5 Select OK.
Delete
Edit
4 Select OK.
Delete
Edit
4 Select OK.
Admin profiles
Each administrator account belongs to an admin profile. The admin profile separates
FortiGate features into access control categories for which an administrator with
read/write access can enable none (deny), read only, or read/write access.
The following table lists the web-based manager pages to which each category provides
access.
Read-only access for a web-based manager page enables the administrator to view that
page. However, the administrator needs write access to change the settings on the page.
You can expand the firewall configuration access control to enable more granular control
of access to the firewall functionality. You can control administrator access to policy,
address, service, schedule, profile, and other virtual IP (VIP) configurations.
Note: When Virtual Domain Configuration is enabled (see “Settings” on page 261), only the
administrators with the admin profile super_admin have access to global settings. Other
administrator accounts are assigned to one VDOM and cannot access global configuration
options or the configuration for any other VDOM.
For information about which settings are global, see “VDOM configuration settings” on
page 126.
The admin profile has a similar effect on administrator access to CLI commands. The
following table shows which command types are available in each Access Control
category. You can access “get” and “show” commands with Read Only access. Access to
“config” commands requires Read-Write access.
To add admin profiles for FortiGate administrators, go to System > Admin > Admin Profile.
Each administrator account belongs to an admin profile. An administrator with read/write
access can create admin profiles that deny access to, allow read-only, or allow both read-
and write-access to FortiGate features.
When an administrator has read-only access to a feature, the administrator can access
the web-based manager page for that feature but cannot make changes to the
configuration. There are no Create or Apply buttons and lists display only the View ( )
icon instead of icons for Edit, Delete or other modification commands.
Delete
Edit
Central Management
The Central Management tab provides the option of remotely managing your FortiGate
unit by either a FortiManager unit or the FortiGuard Analysis and Management Service.
From System > Admin > Central Management, you can configure your FortiGate unit to
back up or restore configuration settings automatically to the specified central
management server. The central management server is the type of service you enable,
either a FortiManager unit or the FortiGuard Analysis and Management Service. If you
have a subscription for FortiGuard Analysis and Management Service, you can also
remotely upgrade the firmware on the FortiGate unit.
Enable Central Enables the Central Management feature on the FortiGate unit.
Management
Type Select the type of central management for this FortiGate unit. You can
select FortiManager or the FortiGuard Management Service.
FortiManager Select to use FortiManager as the central management service for the
FortiGate unit.
Enter the IP address or name of the FortiManager unit in the IP/Name
field.
If your organization is operating a FortiManager cluster, add the IP
address or name of the primary FortiManager unit to the IP/Name field
and add the IP address or name of the backup FortiManager units to
the Trusted FortiManager list.
Status indicates whether or not the FortiGate unit can communicate
with the FortiManager unit added to the IP/Name field.
Select Register to include the FortiManager unit in the Trusted
FortiManager List.
A red arrow-down indicates that there is no connection enabled.
A green arrow-up indicates that there is a connection.
A yellow caution symbol appears when your FortiGate unit is
considered an unregistered device by the FortiManager unit.
FortiGuard Select to use the FortiGuard Management Service as the central
Management Service management service for the FortiGate unit.
Enter the Account ID in the Account ID field. If you do not have an
account ID, register for the FortiGuard Management Service on the
FortiGuard Management Service website.
Select Change to go directly to System > Maintenance > FortiGuard.
Under Analysis & Management Service Options, enter the account ID
in the Account ID field.
When you are configuring your FortiGate unit to connect to and communicate with a
FortiManager unit, the following steps must be taken because of the two different
deployment scenarios.
• FortiGate is directly reachable from FortiManager:
• In the FortiManager GUI, add the FortiGate unit to the FortiManager database in
the Device Manager module
• Change the FortiManager IP address
• Change the FortiGate IP address
• FortiGate behind NAT
• In System > Admin > Central Management, choose FortiManager
• Add the FortiManager unit to the Trusted FortiManager List, if applicable
• Change the FortiManager IP address
• Change the FortiGate IP address
• Contact the FortiManager administrator to verify the FortiGate unit displays in the
Device list in the Device Manager module
Revision control
The Revision Control tab displays a list of the backed up configuration files. The list
displays only when your FortiGate unit is managed by a central management server. For
more information, see “Managing configuration revisions” on page 297.
Settings
The Settings tab includes the following features that you can configure:
• ports for HTTP/HTTPS administrative access and SSL VPN login
• password policy for administrators and IPsec pre-shared keys
• the idle timeout setting
• settings for the language of the web-based manager and the number of lines displayed
in generated reports
• PIN protection for LCD and control buttons (LCD-equipped models only)
• SCP capability for users logged in via SSH
• Wireless controller capability
• IPv6 support on the web based manager.
To configure settings, go to System > Admin > Settings, enter or select the following and
select OK.
Note: If you make a change to the default port number for HTTP, HTTPS, Telnet, or SSH,
ensure that the port number is unique.
Monitoring administrators
To see the number of logged-in administrators, go to System > Status. Under System
Information, you will see Current Administrators. Select Details to view information about
the administrators currently logged in to the FortiGate unit.
See also
IP version 6 address
While 32-bits of addresses, or just under 5 billion addresses, seems like a lot, they have
been used up quickly. Between servers and routers that provide the backbone
communications of the Internet, to large companies and governments with thousands of
computers large portions of the IP address space were either reserved or used up.
In 1998, IP version 6 was designed mainly to provide more addresses but also improve
slightly on IP version 4 (IPv4). IP version 6 (IPv6) is defined in RFC 2460.
With four bytes of addresses there are a total just under 5 billion addresses. IPv6
addresses are 32 bytes long, and have no problems of ever running out. This very large
address space also allows for more logical organization of addresses which in turn
promotes more efficient network management and routing.
IPv6 addresses are normally written as eight groups of 4 hexadecimal digits each. For
example,
3f2e:6a8b:78a3:0d82:1725:6a2f:0370:6234
is a valid IPv6 address.
If a 4 digit group is 0000, it may be omitted. For example,
3f2e:6a8b:78a3:0000:1725:6a2f:0370:6234
is the same IPv6 address as
3f2e:6a8b:78a3::1725:6a2f:0370:6234
You can use the “::” notation to indicate multiple consecutive omitted zero groups. There
must not be more than one use of “::” in an address, as this is ambiguous. Also, you can
omit leading zeros in a group. Thus
19a4:0478:0000:0000:0000:0000:1a57:ac9e
19a4:0478:0000:0000:0000::1a57:ac9e
19a4:478:0:0:0:0:1a57:ac9e
19a4:478:0::0:1a57:ac9e
19a4:478::1a57:ac9e
are all valid and are the same address.
For IPv4-compatible or IPv4-mapped IPv6 addresses, you can enter the IPv4 portion
using either hexadecimal or dotted decimal, but the FortiGate CLI always shows the IPv4
portion in dotted decimal format. For all other IPv6 addresses, the CLI accepts and
displays only hexadecimal.
IPv6 Netmasks
As with IP addresses, hexadecimal notation replaces the dotted decimal notation of IPv4.
CIDR notation can also be used. This notation appends a slash (“/”) to the IP address,
followed by the number of bits in the network portion of the address.
IP Address 3ffe:ffff:1011:f101:0210:a4ff:fee3:9566
Netmask ffff:ffff:ffff:ffff:0000:0000:0000:0000
Network 3ffe:ffff:1011:f101:0000:0000:0000:0000
CIDR IP/Netmask 3ffe:ffff:1011:f101:0210:a4ff:fee3:9566/64
IPv4-compatible addresses are used for hosts and routers to dynamically tunnel IPv6
packets over IPv4 routing infrastructure. IPv4-mapped addresses are used for nodes that
do not support IPv6.
IPv6 tunneling
Networks using IPv6 addressing can be linked through IPv4-addressed infrastructure
using several tunneling techniques:
IPv6-over-IPv4 Encapsulates IPv6 packets within IPv4 so that they can be carried
across IPv4 routing infrastructures.
Configured The endpoint address is determined by configuration information
on the encapsulating node.
Automatic The IPv4 tunnel endpoint address is determined from the IPv4
address embedded in the IPv4-compatible destination address of
the IPv6 packet being tunneled.
IPv4 multicast IPv4 tunnel endpoint address is determined using Neighbor
Discovery. No address configuration is required, but the IPv4
infrastructure must support IPv4 multicast.
Tip: Increase the timeout settings before creating or editing a GUI layout. See “Settings” on
page 261.
Note: The current administrator Access Control settings apply only to the fixed components
of the layout (default), not to the customized items. If you want to create a completely
customized layout profile, you must set access for all fixed components to None and also
set all the standard menu items to Hide from within the GUI layout dialog box (see
Figure 128).
Figure 126: Admin Profile dialog box - Log & Report access
Access denied
to other layout
items
Read-only access
selected for Log &
Report
Standard GUI
Control Menu
Layout selection
Figure 127: Selection of Customize GUI Control option for Report Profile
Select Customize
to access the
layout dialog box
Figure 128: Customize GUI layout dialog box for Report Profile
Customization
drop-down menu Save layout
Cancel layout changes
In the GUI layout dialog box, select the customization drop-down menu icon beside
System and select hide (see Figure 128). Repeat for each menu item except Log&Report.
To start the configuration of customized menu items, select the Create New (Tier-1 menu
item) icon in the FortiGate menu. You will need to:
• configure Tier-1 and Tier-2 menu items
• add tabs to each of these items as required
• add content to the page layout.
Figure 129: Creating Tier-1 and Tier-2 menu items in the FortiGate menu
1 2
Creation of new
Tier-1 menu item
Custom Log Report
3 4
Creation of new
Tier-2 menu item
Custom Log Menu1
5 6
Creation of new
Tier-2 menu item
Custom Log Menu2
After you create Tier-1 and Tier-2 menu items, you need to create the subset of tab items
across the page layout. The Create New tab icon is not available until you have created
the Tier-1 and Tier-2 menu items.
2 Select and rename the default name to Custom Log Report Tab1 (see Figure 131).
3 Press Enter to save your change.
4 Repeat steps 1 to 3 to create a second tab called Custom Log Report Tab2.
5 To save your customized layout, select Save in the GUI layout dialog box (see
Figure 128).
Creation of tab
Custom Log Report Tab1
To add content to the page layout, select Add Content (see Figure 128). The Add content
to the Custom Log Report Tab1 dialog box appears (see Figure 133).
The Add content dialog box includes a search feature that you can use to find widgets.
This search employs a real-time filtering mechanism with a “contains” type search on the
widget names. For example, if you search on “use”, you will be shown User Group, IM
User Monitor, Firewall User Monitor, Banned User, and Top Viruses (see Figure 134).
Search results
For Custom Log Report Tab1, select the Log&Report category. All the items related to the
Log&Report menu item are listed (see Figure 135). Select Add next to an item that you
want to include in the tab. The item is placed in the page layout behind the Custom Log
Report Tab1 dialog box. You will see the configured layout when you close the Add
content to the Custom Log Report Tab1 dialog box. The maximum number of items that
can be placed in a page layout is 8.
For the Custom Log Report Tab1, select the following items for inclusion in the layout:
• Alert E-mail
• Schedule.
Close the Edit Layout dialog box.
Figure 135: Log&Report category selection for Custom Log Report Tab1
For the Custom Log Report Tab2, select the following items for inclusion in the layout:
• Event Log
• Log Setting.
Figure 137: Log&Report category selection for Custom Log Report Tab2
To preview a customized layout in the custom GUI layout dialog box, select Show Preview
(see Figure 139). When you have completed the configuration selections for the page
layout, select Save to close the custom GUI layout dialog box (see Figure 139). To
abandon the configuration, select Reset menus (see Figure 139). To exit the GUI layout
dialog box without saving your changes, select Cancel (see Figure 139).
Figure 139: Report Profile customized GUI layout dialog box - complete
Cancel
Show Preview
Save
Reset menus
When you complete the customization, close the dialog box to return to the Admin Profile
dialog box in which you configured the custom GUI. To save the configuration, select OK
to close the Admin Profile dialog box (see Figure 125).
To view the web-based manager configuration created in Report Profile, you must log out
of the FortiGate unit, then log back in using the name and password of an administrator
assigned the Report Profile administrative profile. The FortiGate web-based manager
reflects the customized configuration of Report Profile (see Figure 140).
System Certificates
This section explains how to manage X.509 security certificates using the FortiGate web-
based manager. Certificate authentication allows administrators to generate certificate
requests, install signed certificates, import CA root certificates and certificate revocation
lists, and back up and restore installed certificates and private keys.
Authentication is the process of determining if a remote host can be trusted with access to
network resources. To establish its trustworthiness, the remote host must provide an
acceptable authentication certificate by obtaining a certificate from a certification authority
(CA). The FortiGate unit can then use certificate authentication to reject or allow
administrative access via HTTPS, and to authenticate IPSec VPN peers or clients, as well
as SSL VPN user groups or clients.
If you enable virtual domains (VDOMs) on the FortiGate unit, system certificates are
configured globally for the entire FortiGate unit. For details, see “Using virtual domains” on
page 125.
There are several certificates on the FortiGate unit that have been automatically
generated.
Table 46: Automatically generated FortiGate certificates
System administrators can use these certificates wherever they may be required, for
example, with SSL VPN, IPSec, LDAP, and PKI.
For additional background information on certificates, see the FortiGate Certificate
Management User Guide.
Local Certificates
Certificate requests and installed server certificates are displayed in the Local Certificates
list. After you submit the request to a CA, the CA will verify the information and register the
contact information on a digital certificate that contains a serial number, an expiration date,
and the public key of the CA. The CA will then sign the certificate and send it to you to
install on the FortiGate unit.
Local certificates can update automatically online prior to expiry. This must be configured
in the CLI. See the vpn certificate local command in the FortiGate CLI Reference.
To view certificate requests and/or import signed server certificates, go to System >
Certificates > Local Certificates. To view certificate details, select the View Certificate
Detail icon in the row that corresponds to the certificate.
Download
View Certificate Detail
Delete
Generate Generate a local certificate request. For more information, see “Generating a
certificate request” on page 281.
Import Import a signed local certificate. For more information, see “Importing a signed
server certificate” on page 283.
Name The names of existing local certificates and pending certificate requests.
Subject The Distinguished Names (DNs) of local signed certificates.
Remove/Add OU
Certification Name Enter a certificate name. Typically, this would be the name of the
FortiGate unit. To enable the export of a signed certificate as a PKCS12
file later on if required, do not include spaces in the name.
Subject Information Enter the information needed to identify the FortiGate unit:
Host IP If the FortiGate unit has a static IP address, select Host IP and enter the
public IP address of the FortiGate unit. If the FortiGate unit does not have
a public IP address, use an email address (or domain name if available)
instead.
Domain Name If the FortiGate unit has a static IP address and subscribes to a dynamic
DNS service, use a domain name if available to identify the FortiGate unit.
If you select Domain Name, enter the fully qualified domain name of the
FortiGate unit. Do not include the protocol specification (http://) or any
port number or path names. If a domain name is not available and the
FortiGate unit subscribes to a dynamic DNS service, an “unable to verify
certificate” message may be displayed in the user’s browser whenever
the public IP address of the FortiGate unit changes.
E-Mail If you select E-mail, enter the email address of the owner of the FortiGate
unit.
Optional Information Complete as described or leave blank.
Organization Unit Enter the name of your department or departments. You can enter a
maximum of 5 Organization Units. To add or remove a unit, use the plus
(+) or minus (-) icon.
Organization Enter the legal name of your company or organization.
Locality (City) Enter the name of the city or town where the FortiGate unit is installed.
State/Province Enter the name of the state or province where the FortiGate unit is
installed.
Country Select the country where the FortiGate unit is installed.
e-mail Enter the contact email address.
Key Type Only RSA is supported.
Key Size Select 1024 Bit, 1536 Bit or 2048 Bit. Larger keys are slower to generate
but they provide better security.
Enrollment Method Select one of the following methods:
File Based Select to generate the certificate request.
Online SCEP Select to obtain a signed SCEP-based certificate automatically over the
network.
CA Server URL: Enter the URL of the SCEP server from which to retrieve
the CA certificate.
Challenge Password: Enter the CA server challenge password.
3 Select OK.
3 Select OK.
Note: The certificate file must not use 40-bit RC2-CBC encryption.
3 Select OK.
Remote Certificates
For dynamic certificate revocation, you need to use an Online Certificate Status Protocol
(OCSP) server. Remote certificates are public certificates without a private key. The
OCSP is configured in the CLI only. For more information, see the FortiGate CLI
Reference.
Installed Remote (OCSP) certificates are displayed in the Remote Certificates list.
Import Import a public OCSP certificate. See “Importing CA certificates” on page 286.
Name The names of existing Remote (OCSP) certificates. The FortiGate unit assigns
unique names (REMOTE_Cert_1, REMOTE_Cert_2, REMOTE_Cert_3, and so
on) to the Remote (OCSP) certificates when they are imported.
Subject Information about the Remote (OCSP) certificate.
Delete icon Delete a Remote (OCSP) certificate from the FortiGate configuration.
View Certificate Display certificate details.
Detail icon
Download icon Save a copy of the Remote (OCSP) certificate to a local computer.
The system assigns a unique name to each Remote (OCSP) certificate. The names are
numbered consecutively (REMOTE_Cert_1, REMOTE_Cert_2, REMOTE_Cert_3, and
so on).
CA Certificates
When you apply for a signed personal or group certificate to install on remote clients, you
must obtain the corresponding root certificate and CRL from the issuing CA.
When you receive the certificate, install it on the remote clients according to the browser
documentation. Install the corresponding root certificate and CRL from the issuing CA on
the FortiGate unit.
CA certificates can update automatically online prior to expiry. This must be configured in
the CLI. See the vpn certificate local command in the FortiGate CLI Reference.
Installed CA certificates are displayed in the CA Certificates list. You cannot delete the
Fortinet_CA certificate. To view installed CA root certificates or import a CA root
certificate, go to System > Certificates > CA Certificates. To view root certificate details,
select the View Certificate Detail icon in the row that corresponds to the certificate.
For detailed information and step-by-step procedures related to obtaining and installing
digital certificates, see the FortiGate Certificate Management User Guide.
Importing CA certificates
After you download the root certificate of the CA, save the certificate on a PC that has
management access to the FortiGate unit.
To import a CA root certificate, go to System > Certificates > CA Certificates and select
Import.
If you choose SCEP, the system starts the retrieval process as soon as you select OK.
The system assigns a unique name to each CA certificate. The names are numbered
consecutively (CA_Cert_1, CA_Cert_2, CA_Cert_3, and so on).
CRL
A Certificate Revocation List (CRL) is a list of CA certificate subscribers paired with
certificate status information. Installed CRLs are displayed in the CRL list. The FortiGate
unit uses CRLs to ensure that the certificates belonging to CAs and remote clients are
valid.
To view installed CRLs, go to System > Certificates > CRL.
Download
Import Import a CRL. For more information, see “Importing a certificate revocation list”
on page 288.
Name The names of existing certificate revocation lists. The FortiGate unit assigns
unique names (CRL_1, CRL_2, CRL_3, and so on) to certificate revocation lists
when they are imported.
Subject Information about the certificate revocation lists.
Delete icon Delete the selected CRL from the FortiGate configuration.
View Certificate Display CRL details such as the issuer name and CRL update dates.
Detail icon
Download icon Save a copy of the CRL to a local computer.
Note: When the CRL is configured with an LDAP, HTTP, and/or SCEP server, the latest
version of the CRL is retrieved automatically from the server when the FortiGate unit does
not have a copy of it or when the current copy expires.
To import a certificate revocation list, go to System > Certificates > CRL and select Import.
HTTP Select to use an HTTP server to retrieve the CRL. Enter the URL of the HTTP
server.
LDAP Select to use an LDAP server to retrieve the CRL, then select the LDAP
server from the list.
SCEP Select to use an SCEP server to retrieve the CRL, then select the Local
Certificate from the list. Enter the URL of the SCEP server from which the
CRL can be retrieved.
Local PC Select to use a local administrator’s PC to upload a public certificate. Enter
the location, or browse to the location on the management computer where
the certificate has been saved, select the certificate, and then select OK.
The system assigns a unique name to each CRL. The names are numbered consecutively
(CRL_1, CRL_2, CRL_3, and so on).
System Maintenance
This section describes how to maintain your system configuration as well as how to enable
and update FDN services. This section also explains the types of FDN services that are
available for your FortiGate unit.
If you enable virtual domains (VDOMs) on the FortiGate unit, system maintenance is
configured globally for the entire FortiGate unit. For more information, see “Using virtual
domains” on page 125.
This section includes the following topics:
• About the Maintenance menu
• Backing up and restoring
• Managing configuration revisions
• Using script files
• Configuring FortiGuard Services
• Troubleshooting FDN connectivity
• Updating antivirus and attack definitions
• Enabling push updates
• Adding VDOM Licenses
When virtual domain configuration is enabled, the content of the backup file depends on
the administrator account that created it. A backup of the system configuration from the
super_admin account contains global settings and the settings included in each VDOM.
Only the super_admin can restore the configuration from this file. When you back up the
system configuration from a regular administrator account, the backup file contains the
global settings and the settings for the VDOM that the regular administrator belongs to. A
regular administrator is the only user account that can restore the configuration from this
file.
Some FortiGate models support FortiClient by storing a FortiClient image that users can
download. The FortiClient section of Backup & Restore is available if your FortiGate model
supports FortiClient.
Tip: For simplified procedures on managing firmware, including backup and restore
options, and on uploading and downloading firmware for your FortiGate unit, see
For
“Managing firmware versions” on page 113.
Figure 153: Backup & Restore options with FortiGuard services option enabled
Backup
Backup configuration to: The options available for backing up your current configuration. Select
one of the displayed options:
Local PC Back up the configuration to the management computer the FortiGate
unit is connected to. Local PC is always displayed regardless of
whether a USB disk is available, FortiGuard Analysis & Management
Service is enabled, or the FortiGate unit is connected to a
FortiManager unit.
FortiGuard Analysis & Back up the configuration to the FortiGuard Analysis & Management
Management Service Service. If the service is not enabled, Management Station is
displayed.
USB Disk Back up the configuration file to the USB disk connected to the
FortiGate unit. USB Disk is displayed only if the FortiGate unit includes
a USB port. If you do not connect a USB disk, this option is grayed out.
For more information, see “Formatting USB Disks” on page 296.
FortiManager Back up the configuration to the configured FortiManager unit. If the
FortiGate unit is not connected to a FortiManager unit, this option is not
displayed.
Encrypt configuration Select to encrypt the backup file.
file Encryption must be enabled to save VPN certificates with the
configuration.
This option is not available for configurations backed up to a
FortiManager unit.
Password Enter a password to encrypt the configuration file. You will need this
password to restore the configuration file.
Confirm Enter the password again to confirm the password.
Filename Enter the name of the backup file or select Browse to locate the file.
The Filename field is available only when you choose to back up the
configuration to a USB disk.
Backup Select to back up the configuration.
If you are backing up to a FortiManager device, a confirmation
message is displayed after successful completion of the backup.
Restore
Restore configuration The options available for restoring the configuration from a specific file.
from: Select one of the displayed options:
Local PC Restore a configuration file from the management computer the
FortiGate unit is connected to. Local PC is always displayed regardless
of whether a USB disk is available, FortiGuard Analysis &
Management Service is enabled, or the FortiGate unit is connected to
a FortiManager unit.
USB disk Restore a configuration file from the USB disk connected to the
FortiGate unit. USB Disk is displayed only if the FortiGate unit includes
a USB port. If you do not connect a USB disk, this option is grayed out.
See “Formatting USB Disks” on page 296.
FortiGuard Analysis & Restore a configuration from the FortiGuard Analysis & Management
Management Service Service. If FortiGuard Management Services is not enabled, this option
is not displayed and instead displays Management Station.
FortiManager Restore a configuration from the configured FortiManager unit. If the
FortiGate unit is not connected to a FortiManager unit, this option is not
displayed.
Filename Select the configuration file name from the Browse list if you are
restoring the configuration from a USB disk.
Enter the configuration file name or select Browse if you are restoring
the configuration from a file on the management computer.
Password Enter the password you entered when backing up the configuration file.
Restore Select to restore the configuration.
Figure 154: Backup & Restore options with FortiManager option enabled
\
Tip: For simplified procedures on managing firmware, including backup and restore
options, and on uploading and downloading firmware for your FortiGate unit, see
For
“Managing firmware versions” on page 113.
When restoring the configuration from a remote location, a list of revisions is displayed so
that you can choose the configuration file to restore.
To view the basic backup and restore options, go to System > Maintenance >
Backup & Restore.
Backup The options available for backing up your current configuration to the
FortiGuard Analysis & Management Service.
Backup configuration Select the FortiGuard option to upload the configuration to the
to: FortiGuard Analysis & Management Service.
The Local PC option is always available.
Comments: Enter a description or information about the file in the Comments field.
This is optional.
Backup Select to back up the configuration file to the FortiGuard Analysis &
Management Service.
A confirmation message appears after successful completion of the
backup.
Restore The options for restoring a configuration file.
Restore configuration Select the FortiGuard option to download the configuration file from
from: the FortiGuard Analysis & Management Service.
Please Select: Select the configuration file you want to restore from the list. This list
includes the comments you included in the Comment field before it
was uploaded to the FortiGuard Analysis & Management Service.
The list is in numerical order, with the recent uploaded configuration
first.
Restore Select to restore the configuration from the FortiGuard Analysis &
Management Service.
Partition A partition can contain one version of the firmware and the system
configuration. FortiGate-100A units and higher have two partitions.
One partition is active and the other is used as a backup.
Active A green check mark indicates the partition currently in use.
Last upgrade The date and time of the last update to this partition.
Firmware Version The version and build number of the FortiGate firmware. If your
FortiGate model has a backup partition, you can:
• Select Upload to replace with firmware from the management
computer or a USB disk. The USB disk must be connected to the
FortiGate unit USB port. See “Formatting USB Disks” on page 296.
• Select Upload and Reboot to replace the existing firmware and
make this the active partition.
Boot alternate firmware Restart the FortiGate unit using the backup firmware.
This is available only for FortiGate-100 units or higher.
Figure 157: Firmware Upgrade section of the Backup & Restore page
Upgrade from FortiGuard Select one of the available firmware versions. The list contains the
network to firmware following information for each available firmware release:
version: [Please Select] • continent (for example, North America)
• maintenance release number
• patch release number
• build number.
For example, if you are upgrading to FortiOS 3.0 MR6 and the
FortiGate unit is located in North America, the firmware version
available is v3.0 MR6-NA (build 0700).
Allow firmware Select to allow installation of older versions than the one currently
downgrade installed.
This is useful if the current version changed functionality you need and
you have to revert to an older firmware image.
Upgrade by File Select Browse to locate a file on your local PC to upload to the
FortiGate unit.
OK Select OK to enable your selection.
On system restart, Automatically update the configuration on restart. Ensure that the
automatically update default configuration file name matches the configuration file name on
FortiGate the USB disk.
configuration... If the configuration file on the disk matches the currently installed
configuration, the FortiGate unit skips the configuration update
process.
On system restart, Automatically update the firmware on restart. Ensure that the default
automatically update image name matches the firmware file name on the USB disk.
FortiGate firmware... If the firmware image on the disk matches the currently installed
firmware, the FortiGate unit skips the firmware update process.
Apply Select to apply the selected settings.
Download Debug Log Download an encrypted debug log to a file. You can send this debug
log to Fortinet Technical Support to help diagnose problems with your
FortiGate unit.
Caution: Formatting the USB disk deletes all information on the disk. Back up the
information on the USB disk before formatting to ensure all information on the disk is
recoverable.
There are two ways that you can format the USB disk, either by using the CLI or a
Windows system. You can format the USB disk in the CLI using the command syntax,
exe usb-disk format. When using a Windows system to format the disk, at the
command prompt type, “format <drive_letter>: /FS:FAT /V:<drive_label>”
where <drive_letter> is the letter of the connected USB drive you want to format, and
<drive_label> is the name you want to give the USB drive for identification.
Diff
Download
Revert
Current Page The current page number of list items that are displayed. Select the left
and right arrows to display the first, previous, next or last page of
system configuration backups.
For more information, see “Using page controls on web-based
manager lists” on page 60.
Revision An incremental number indicating the order in which the configurations
were saved. These may not be consecutive numbers if configurations
are deleted.
The most recent, and highest, number is first in the list.
Date/Time The date and time this configuration was saved on the FortiGate unit.
Administrator The administrator account that was used to back up this revision.
Comments Any relevant information saved with the revision, such as why the
revision was saved, who saved it, and if there is a date when it can be
deleted to free up space.
Diff icon Select to compare two revisions.
A window will appear, from which you can view and compare the
selected revision to one of:
• the current configuration
• a selected revision from the displayed list including revision history
and templates
• a specified revision number.
Download icon Download this revision to your local PC.
Revert icon Restore the previous selected revision. You will be prompted to confirm
this action.
Execute Script from Scripts can be uploaded directly to the FortiGate unit from the
management PC. If you have configured either a FortiManager unit or
the FortiGuard Analysis & Management Service, scripts that have
been stored remotely can also be run on the FortiGate unit.
Upload Bulk CLI Select Browse to locate the script file and then select Apply to upload
Command File and execute the file.
If the FortiGate unit is configured to use the FortiGuard Analysis &
Management Service, the script will be saved on the server for later
use.
Select From remote Select to execute a script from the FortiManager unit or the FortiGuard
management station Analysis & Management Service. Choose the script you want to run
from the list of all scripts stored remotely.
Tip: An unencrypted configuration file uses the same structure and syntax as a script file.
You can save a configuration file and copy the required parts to a new file, making any edits
you require. You can generate script files more quickly this way.
Caution: Commands that require the FortiGate unit to reboot when entered on the
command line will also force a reboot if included in a script.
To execute a script
1 Go to System > Maintenance > Scripts.
2 Verify that Upload Bulk CLI Command File is selected.
3 Select Browse to locate the script file.
4 Select Apply.
If the FortiGate unit is not configured for remote management, or if it is configured to use a
FortiManager unit, uploaded scripts are discarded after execution. Save script files to your
management PC if you want to execute them again later.
If the FortiGate unit is configured to use the FortiGuard Analysis & Management Service,
the script file is saved to the remote server for later reuse. You can view the script or run it
from the FortiGuard Analysis & Management Service portal web site. For more
information about viewing or running an uploaded script on the portal web site, see the
FortiGuard Analysis & Management Service Users Guide.
FortiGuard services
Worldwide coverage of FortiGuard services is provided by FortiGuard service points.
When the FortiGate unit is connecting to the FDN, it is connecting to the closest
FortiGuard service point. Fortinet adds new service points as required.
If the closest service point becomes unreachable for any reason, the FortiGate unit
contacts another service point and information is available within seconds. By default, the
FortiGate unit communicates with the service point via UDP on port 53. Alternately, you
can switch the UDP port used for service point communication to port 8888 by going to
System > Maintenance > FortiGuard.
If you need to change the default FortiGuard service point host name, use the hostname
keyword in the system fortiguard CLI command. You cannot change the FortiGuard
service point name using the web-based manager.
For more information about FortiGuard services, see the FortiGuard Center web page.
Configuring the FortiGate unit for FDN and FortiGuard subscription services
FDN updates, as well as FortiGuard services, are configured in System > Maintenance >
FortiGuard. The FDN page contains four sections of FortiGuard services:
• Support Contract and FortiGuard Subscription Services
• Downloading antivirus and IPS updates
• Configuring Web Filtering and Email Filtering Options
• Configuring FortiGuard Analysis & Management Service Options
Support Contract The availability or status of your FortiGate unit support contract. The
status displays can be one of the following: Unreachable, Not
Registered or Valid Contract.
If Valid Contract is shown, the FortiOS firmware version and contract
expiry date appear. A green checkmark also appears.
[Register] Select to register your FortiGate unit support contract.
This option is available only when the support contract is not
registered.
FortiGuard Subscription Availability and status information for each of the FortiGuard
Services subscription services including:
• AntiVirus
• Intrusion Protection
• Web Filtering
• AntiSpam
• Analysis & Management Service
Use override server Select to configure an override server if you cannot connect to the
address FDN or if your organization provides updates using their own
FortiGuard server.
When selected, enter the IP address or domain name of a FortiGuard
server and select Apply. If the FDN Status still indicates no connection
to the FDN, see “Troubleshooting FDN connectivity” on page 306.
Allow Push Update Select to allow push updates. Updates are then sent automatically to
your FortiGate unit when they are available, eliminating any need for
you to check if they are available.
Allow Push Update The status of the FortiGate unit for receiving push updates:
status icon Gray (Unreachable) - theFortiGate unit is not able to connect to push
update service
Yellow (Not Available) - the push update service is not available with
current support license
Green (Available) - the push update service is allowed. See
“Enabling push updates” on page 308.
If the icon is gray or yellow, see “Troubleshooting FDN connectivity”
on page 306.
Use override push IP Available only if both Use override server address and Allow Push
Update are enabled.
Select to allow you to create a forwarding policy that redirects
incoming FDS push updates to your FortiGate unit.
Enter the IP address of the NAT device in front of your FortiGate unit.
FDS will connect to this device when attempting to reach the FortiGate
unit.
The NAT device must be configured to forward the FDS traffic to the
FortiGate unit on UDP port 9443. See “Enabling push updates through
a NAT device” on page 309.
Port Select the port on the NAT device that will receive the FDS push
updates. This port must be forwarded to UDP port 9443 on the
FortiGate unit.
Available only if Use override push is enabled.
Schedule Updates Select this check box to enable scheduled updates.
Every Attempt to update once every 1 to 23 hours. Select the number of
hours between each update request.
Daily Attempt to update once a day. You can specify the hour of the day to
check for updates. The update attempt occurs at a randomly
determined time within the selected hour.
Weekly Attempt to update once a week. You can specify the day of the week
and the hour of the day to check for updates. The update attempt
occurs at a randomly determined time within the selected hour.
Update Now Select to manually initiate an FDN update.
Submit attack Fortinet recommends that you select this check box. It helps to
characteristics… improve the quality of IPS signature.
(recommended)
Enable Web Filter Select to enable the FortiGuard Web Filter service.
Enable Cache Select to enable caching of web filter queries.
This improves performance by reducing FortiGate unit requests to the
FortiGuard server. The cache uses 6 percent of the FortiGate memory.
When the cache is full, the least recently used IP address or URL is
deleted.
Available if Enable Web Filter is selected.
TTL Time to live. The number of seconds to store blocked IP addresses
and URLs in the cache before contacting the server again.TTL must
be between 300 and 86400 seconds.
Available only if both Enable Web Filter and Enable Cache are
selected.
Enable Email Filter Select to enable the FortiGuard AntiSpam service.
Enable Cache Select to enable caching of antispam queries.
This improves performance by reducing FortiGate unit requests to the
FortiGuard server. The cache uses 6 percent of the FortiGate memory.
When the cache is full, the least recently used IP address or URL is
deleted.
Available only if Enable Email Filter is selected.
TTL Time to live. The number of seconds to store blocked IP addresses
and URLs in the cache before contacting the server again.TTL must
be between 300 and 86400 seconds.
Port Section Select one of the following ports for your web filtering and antispam
requirements:
Use Default Port (53) Select to use port 53 for transmitting with FortiGuard Antispam
servers.
Use Alternate Port Select to use port 8888 for transmitting with FortiGuard Antispam
(8888) servers.
Test Availability Select to test the connection to the servers. Results are shown below
the button and on the Status indicators.
To have a URL's category Select to re-evaluate a URL’s category rating on the FortiGuard Web
rating re-evaluated, please Filter service.
click here.
Account ID Enter the name for the Analysis & Management Service that identifies
the account.
The account ID that you entered in the Account ID field when
registering is used in this field.
To launch the service Select to go directly to the FortiGuard Analysis & Management Service
portal, please click here portal web site to view logs or configuration. You can also select this to
register your FortiGate unit with the FortiGuard Analysis &
Management Service.
To configure FortiGuard Select the link please click here to configure and enable logging to the
Analysis Service options, FortiGuard Analysis & Management server. The link redirects you to
please click here Log&Report > Log Config > Log Setting.
This appears only after registering for the service.
To purge logs older than n Select the number of months from the list that will remove those logs
months, please click here from the FortiGuard Analysis & Management server and select the link
please click here. For example, if you select 2 months, the logs from
the past two months will be removed from the server.
You can also use this option to remove logs that may appear on a
current report.
This appears only after logging is enabled and log messages are sent
to the FortiGuard Analysis server.
Note: Updating antivirus and IPS attack definitions can cause a very short disruption in
traffic scanning while the FortiGate unit applies the new signature definitions. Fortinet
recommends scheduling updates when traffic is light to minimize disruption.
Every Once every 1 to 23 hours. Select the number of hours and minutes
between each update request.
Daily Once a day. You can specify the time of day to check for updates.
Weekly Once a week. You can specify the day of the week and the time of
day to check for updates.
5 Select Apply.
The FortiGate unit starts the next scheduled update according to the new update
schedule.
Whenever the FortiGate unit runs a scheduled update, the event is recorded in the
FortiGate event log.
If you cannot connect to the FDN, or if your organization provides antivirus and IPS
attack updates using its own FortiGuard server, you can use the following procedure to
add the IP address of an override FortiGuard server.
Fortinet does not recommend enabling push updates as the only method for obtaining
updates. The FortiGate unit might not receive the push notification. When the FortiGate
unit receives a push notification, it makes only one attempt to connect to the FDN and
download updates.
Internal Virtual IP
network 172.16.35.144 10.20.6.135
(external interface) (external interface)
Internet
2 Configure the following FortiGuard options on the FortiGate unit on the internal
network.
• Enable Allow push updates.
• Enable Use override push IP and enter the IP address. Usually this is the IP
address of the external interface of the NAT device.
• If required, change the override push update port.
3 Add a port forwarding virtual IP to the NAT device.
• Set the external IP address of the virtual IP to match the override push update IP.
Usually this is the IP address of the external interface of the NAT device.
Add a firewall policy to the FortiGate NAT device that includes the port forwarding virtual
IP.
Note: Push updates are not supported if the FortiGate unit must use a proxy server to
connect to the FDN. See “To enable scheduled updates through a proxy server” on
page 308 for more information.
External IP Enter the IP address and/or range. This is the IP address to which
Address/Range the FDN sends the push updates. This is usually the IP address of
the external interface of the NAT device. This IP address must be
the same as the IP address in User override push update for the
FortiGate unit on the internal network.
Mapped IP Enter the IP address and/or range of the FortiGate unit on the
Address/Range internal network.
Port Forwarding Select Port Forwarding. When you select Port Forwarding, the
options Protocol, External Services Port and Map to Port appear.
Protocol Select UDP.
External Service Port Enter the external service port. The external service port is the port
that the FDN connects to. The external service port for push
updates is usually 9443. If you changed the push update port in the
FortiGuard configuration of the FortiGate unit on the internal
network, you must set the external service port to the changed push
update port.
Map to Port Enter 9443. This is the port number to which the NAT FortiGate unit
will send the push update after it comes through the virtual IP.
FortiGate units expect push update notifications on port 9443.
4 Select OK.
Source Interface/Zone Select the name of the interface that connects to the Internet.
Source Address Select All
Destination Select the name of the interface of the NAT device that connects to
Interface/Zone the internal network.
Destination Address Select the virtual IP added to the NAT device.
Schedule Select Always.
Service Select ANY.
Action Select Accept.
NAT Select NAT.
4 Select OK.
Verify that push updates to the FortiGate unit on the internal network are working by going
to System > Maintenance > FortiGuard and selecting Test Availability under Web Filtering
and AntiSpam Options. The Push Update indicator should change to green.
Note: VDOMs created on a registered FortiGate unit are recognized as real devices by any
connected FortiAnalyzer unit. The FortiAnalyzer unit includes VDOMs in its total number of
registered devices. For example, if three FortiGate units are registered on the FortiAnalyzer
unit and they contain a total of four VDOMs, the total number of registered FortiGate units
on the FortiAnalyzer unit is seven. For more information, see the FortiAnalyzer
Administration Guide.
Router Static
This section explains some general routing concepts, and how to define static routes and
route policies.
A route provides the FortiGate unit with the information it needs to forward a packet to a
particular destination on the network. A static route causes packets to be forwarded to a
destination other than the factory configured default gateway.
The factory configured static default route provides you with a starting point to configure
the default gateway. You must either edit the factory configured static default route to
specify a different default gateway for the FortiGate unit, or delete the factory configured
route and specify your own static default route that points to the default gateway for the
FortiGate unit. For more information, see “Default route and default gateway” on
page 318.
You define static routes manually. Static routes control traffic exiting the FortiGate unit—
you can specify through which interface the packet will leave and to which device the
packet should be routed.
As an option, you can define route policies. Route policies specify additional criteria for
examining the properties of incoming packets. Using route policies, you can configure the
FortiGate unit to route packets based on the IP source and destination addresses in
packet headers and other criteria such as on which interface the packet was received and
which protocol (service) and port are being used to transport the packet.
If you enable virtual domains (VDOMs) on the FortiGate unit, static routing is configured
separately for each virtual domain. For more information, see “Using virtual domains” on
page 125.
This section describes:
• Routing concepts
• Static Route
• ECMP route failover and load balancing
• Policy Route
Routing concepts
The FortiGate unit functions as a security device on a network and packets must pass
through it. You need to understand a number of basic routing concepts in order to
configure the FortiGate unit appropriately.
Whether you administer a small or large network, this section will help you understand
how the FortiGate unit performs routing functions.
The following topics are covered in this section:
• How the routing table is built
• How routing decisions are made
• Multipath routing and determining the best route
• Route priority
• Blackhole Route
Administrative Distance
Administrative distance is based on the expected reliability of a given route. It is
determined through a combination of the number of hops from the source and the routing
protocol being used. More hops from the source means more possible points of failure.
The administrative distance can be from 1 to 255, with lower numbers being preferred. A
distance of 255 is seen as infinite and will not be installed in the routing table.
Here is an example to illustrate how administration distance works—if there are two
possible routes traffic can take between 2 destinations with administration distances of 5
(always up) and 31 (sometimes not available), the traffic will use the route with an
administrative distance of 5. whenever possible. Different routing protocols have different
default administrative distances. The default administrative distances for any of these
routing protocols are configurable. For more information on changing the administrative
distance associated with a routing protocol, see the config routing in the FortiGate CLI
Reference.
Another method to manually resolve multiple routes to the same destination is to manually
change the priority of both of the routes. If the next-hop administrative distances of two
routes on the FortiGate unit are equal, it may not be clear which route the packet will take.
Configuring the priority for each of those routes will make it clear which next-hop will be
used in the case of a tie. You can set the priority for a route only from the CLI. Lower
priorities are preferred. For more information, see the FortiGate CLI Reference.
All entries in the routing table are associated with an administrative distance. If the routing
table contains several entries that point to the same destination (the entries may have
different gateways or interface associations), the FortiGate unit compares the
administrative distances of those entries, selects the entries having the lowest distances,
and installs them as routes in the FortiGate forwarding table. As a result, the FortiGate
forwarding table contains only those routes having the lowest distances to each
destination. For information about how to change the administrative distance associated
with a static route, see “Adding a static route to the routing table” on page 320.
Route priority
After the FortiGate unit selects static routes for the forwarding table based on their
administrative distances, the priority field of those routes determines routing preference.
You configure the priority field through the CLI. The route with the lowest value in the
priority field is considered the best route, and the primary route. The command to set the
priority field is: set priority <integer> under the config route static
command. For more information, see the FortiGate CLI Reference.
In summary, because you can use the CLI to specify which priority field settings to use
when defining static routes, you can prioritize routes to the same destination according to
their priority field settings. For a static route to be the preferred route, you must create the
route using the config router static CLI command and specify a low priority for the
route. If two routes have the same administrative distance and the same priority, then they
are equal cost multipath (ECMP) routes. Since this means there is more than one route to
the same destination, it can be confusing which route or routes to install and use.
However, you can configure ECMP Route Failover and Load Balancing to control how
sessions are load balanced among ECMP routes. See “ECMP route failover and load
balancing” on page 322.
Blackhole Route
A blackhole route is a route that drops all traffic sent to it. It is very much like a /dev/null
interface in Linux programming.
Blackhole routes are used to dispose of packets instead of responding to suspicious
inquiries. This provides added security since the originator will not discover any
information from the target network.
Blackhole routes can also limit traffic on a subnet. If some subnet addresses are not in
use, traffic to those addresses (traffic which may be valid or malicious) can be directed to
a blackhole for added security and to reduce traffic on the subnet.
The loopback interface, a virtual interface that does not forward traffic enables easier
configuration of blackhole routing. Similar to a normal interface, this loopback interface
has fewer parameters to configure, and all traffic sent to it stops there. Since it cannot
have hardware connection or link status problems, it is always available, making it useful
for other dynamic routing roles. Once configured, you can use a loopback interface in
firewall policies, routing, and other places that refer to interfaces. Loopback interfaces can
be configured from both the web-based manager and the CLI. For more information, see
“Adding loopback interfaces” on page 158 or the system chapter of the FortiGate CLI
Reference.
Static Route
You configure static routes by defining the destination IP address and netmask of packets
that you intend the FortiGate unit to intercept, and by specifying a (gateway) IP address
for those packets. The gateway address specifies the next-hop router to which traffic will
be routed.
Note: Unless otherwise specified, static route examples and procedures are for IPv4 static
routes.
Note: You can use the config router static6 CLI command to add, edit, or delete
static routes for IPv6 traffic. For more information, see the “router” chapter of the FortiGate
CLI Reference.
To view the static route list, go to Router > Static > Static Route.
Figure 167 shows the static route list belonging to a FortiGate unit that has interfaces
named “port1” and “port2”. The names of the interfaces on your FortiGate unit may be
different.
Figure 167: Static Route list when IPv6 is enabled in the GUI
Expand Delete
Arrow Edit
Create New Add a static route to the Static Route list. For more information, see “Adding a
static route to the routing table” on page 320.
Select the down arrow for the option to create an IPv6 static Route.
ECMP Route Select the load balancing and failover method for ECMP routes. See “ECMP
Failover & Load route failover and load balancing” on page 322.
Balance Method
Source based The FortiGate unit load balances sessions among ECMP routes based on the
source IP address of the sessions to be load balanced. This is the default
load balancing method. No configuration changes are required to support
source IP load balancing.
Weighted The FortiGate unit load balances sessions among ECMP routes based on
weights added to ECMP routes. More traffic is directed to routes with higher
weights.
After selecting weight-based you must add weights to static routes. For more
information, see “Configuring weighted static route load balancing” on
page 326.
Spill-over The FortiGate unit distributes sessions among ECMP routes based on how
busy the FortiGate interfaces associated with the routes are.
After selecting spill-over you add route Spillover Thresholds to interfaces
added to ECMP routes. For more information, see “Configuring interface
status detection for gateway load balancing” on page 165.
The FortiGate unit sends all ECMP-routed sessions to the lowest numbered
interface until the bandwidth being processed by this interface reaches its
spillover threshold. The FortiGate unit then spills additional sessions over to
the next lowest numbered interface.
For more information, including the order in which interfaces are selected,
see “Configuring spill-over or usage-based ECMP” on page 323.
Apply Select to save the ECMP Route Failover and load balance method.
Route Select the Expand Arrow to display or hide the IPv4 static routes. By default
these routes are displayed.
This is displayed only when IPv6 is enabled in the web-based manager.
IPv6 Route Select the Expand Arrow to display or hide the IPv6 static routes. By default
these routes are hidden.
This is displayed only when IPv6 is enabled in the web-based manager.
IP/Mask The destination IP addresses and network masks of packets that the
FortiGate unit intercepts.
Gateway The IP addresses of the next-hop routers to which intercepted packets are
forwarded.
Device The names of the FortiGate interfaces through which intercepted packets are
received and sent.
Distance The administrative distances associated with each route. The values
represent distances to next-hop routers.
Weight If ECMP Route Failover & Load Balance Method is set to weighted, add
weights for each route. Add higher weights to routes that you want to assign
more sessions to when load balancing. For more information, see
“Configuring weighted static route load balancing” on page 326.
Delete and Edit Delete or edit an entry.
icons
Note: For network traffic to pass, even with the correct routes configured, you must have
the appropriate firewall policies. For details, see “Configuring firewall policies” on page 367.
For example, Figure 168 shows a FortiGate unit connected to a router. To ensure that all
outbound packets destined to any network beyond the router are routed to the correct
destination, you must edit the factory default configuration and make the router the default
gateway for the FortiGate unit.
Internet
Gateway
Router
192.168.10.1
external
FortiGate_1
internal
Internal network
192.168.20.0/24
To route outbound packets from the internal network to destinations that are not on
network 192.168.20.0/24, you would edit the default route and include the following
settings:
• Destination IP/mask: 0.0.0.0/0.0.0.0
• Gateway: 192.168.10.1
• Device: Name of the interface connected to network 192.168.10.0/24 (in this example
“external”).
• Distance: 10
The Gateway setting specifies the IP address of the next-hop router interface to the
FortiGate external interface. The interface connected to the router (192.168.10.1) is the
default gateway for FortiGate_1.
In some cases, there may be routers behind the FortiGate unit. If the destination IP
address of a packet is not on the local network but is on a network behind one of those
routers, the FortiGate routing table must include a static route to that network. For
example, in Figure 169, the FortiGate unit must be configured with static routes to
interfaces 192.168.10.1 and 192.168.11.1 in order to forward packets to Network_1 and
Network_2 respectively. Also firewall policies must be configured to allow traffic to pass
through the FortiGate unit along these routes. For details, see “Configuring firewall policies” on
page 367.
Internet
FortiGate_1
internal dmz
192.168.10.1 192.168.11.1
Gateway Gateway
Router_1 Router_2
Network_1 Network_2
192.168.20.0/24 192.168.30.0/24
To route packets from Network_1 to Network_2, Router_1 must be configured to use the
FortiGate internal interface as its default gateway. On the FortiGate unit, you would create
a new static route with these settings:
To route packets from Network_2 to Network_1, Router_2 must be configured to use the
FortiGate dmz interface as its default gateway. On the FortiGate unit, you would create a
new static route with these settings:
Note: If you are using DHCP or PPPoE over a modem interface on your FortiGate unit, you
may have problems configuring a static route on this interface. After trying to either Renew
your DHCP license, or Reconnect the PPPoE connection, go to the CLI and enable
dynamic-gateway under config system interface for the modem interface. Doing
this will remove the need to specify a gateway for this interface’s route. For more
information see FortiGate CLI Reference.
5 Enter the gateway IP address. Continuing with the example, 172.1.2.11 would be a
valid address.
6 Enter the administrative distance of this route.
The administrative distance allows you to weight one route to be preferred over
another. This is useful when one route is unreliable. For example, if route A has an
administrative distance of 30 and route B has an administrative distance of 10, the
preferred route is route A with the smaller administrative distance of 10. If you discover
that route A is unreliable, you can change the administrative distance for route A from
10 to 40, which will make the route B the preferred route.
7 Select OK to confirm and save your new static route.
When you add a static route through the web-based manager, the FortiGate unit adds the
entry to the Static Route list.
Figure 170 shows the Edit Static Route dialog box belonging to a FortiGate unit that has
an interface named “internal”. The names of the interfaces on your FortiGate unit may be
different.
Destination Type the destination IP address and network mask of packets that the
IP/Mask FortiGate unit has to intercept. The value 0.0.0.0/0.0.0.0 is reserved
for the default route.
Gateway Type the IP address of the next-hop router to which the FortiGate unit will forward
intercepted packets.
Device Select the name of the FortiGate interface through which the intercepted packets
may be routed to the next-hop router.
Distance Type an administrative distance from 1 to 255 for the route. The distance value is
arbitrary and should reflect the distance to the next-hop router. A lower value
indicates a more preferred route.
Weight Add weights for each route. Add higher weights to routes that you want to load
balance more sessions to. See “Configuring weighted static route load balancing”
on page 326.
Available if ECMP Route Failover & Load Balance Method is set to weighted.
Note: If multiple routes to the same destination have the same priority but different
distances, the route with the lowest distance is used. If multiple routes to the same
destination have the same distance but different priorities, the route with the lowest priority
is used. Distance takes precedence over priority. If multiple routes to the same destination
have the different distances and different priorities, the route with the lowest distance is
always used even if it has the highest priority.
Using ECMP, if more than one ECMP route is available you can configure how the
FortiGate unit selects the route to be used for a communication session. If only one ECMP
route is available (for example, because an interface cannot process traffic because
interface status detection does not receive a reply from the configured server) then all
traffic uses this route.
Previous versions of FortiOS provided source IP-based load balancing for ECMP routes.
FortiOS 4.0 MR1 includes three configuration options for ECMP route failover and load
balancing:
Source based The FortiGate unit load balances sessions among ECMP routes based on the
(also called source IP address of the sessions to be load balanced. This is the default load
source IP based) balancing method. No configuration changes are required to support source IP
load balancing.
Weighted (also The FortiGate unit load balances sessions among ECMP routes based on
called weights added to ECMP routes. More traffic is directed to routes with higher
weight-based) weights.
After selecting weight-based you must add weights to static routes. See
“Configuring weighted static route load balancing” on page 326.
Spill-over (also The FortiGate unit distributes sessions among ECMP routes based on how busy
called the FortiGate interfaces added to the routes are.
usage-based) After selecting spill-over you add route Spillover Thresholds to interfaces added
to ECMP routes. The FortiGate unit sends all ECMP-routed sessions to the
lowest numbered interface until the bandwidth being processed by this interface
reaches its spillover threshold. The FortiGate unit then spills additional sessions
over to the next lowest numbered interface.
The Spillover Thresholds range is 0-2097000 KBps.
For more information, including the order in which interfaces are selected, see
“Configuring spill-over or usage-based ECMP” on page 323.
You can configure only one of these ECMP route failover and load balancing methods in a
single VDOM. If your FortiGate unit is configured for multiple VDOM operation, each
VDOM can have its own ECMP route failover and load balancing configuration.
To configure the ECMP route failover and load balancing method from the
web-based manager
1 Go to Router > Static > Static Route.
2 Set ECMP Route failover & Load Balance Method to source based, weighted, or
spill-over.
3 Select Apply.
Figure 171: Configuring ECMP route failover and load balancing method
To configure the ECMP route failover and load balancing method from the CLI
1 Enter the following command:
config system settings
set v4-ecmp-mode {source-ip-based | usage-based |
weight-based}
end
Interface port3
Spillover Threshold (KBps) 100
Interface port4
Spillover Threshold (KBps) 200
In this example, the FortiGate unit sends all sessions to the 192.168.20.0 network through
port3. When port3 exceeds its spillover threshold of 100 Kbps the FortiGate unit sends all
new sessions to the 192.168.20.0 network through port4.
3 Enter the following commands to add three ECMP default routes, one for each
interface.
config router static
edit 1
set dst 0.0.0.0/0.0.0.0
set gwy 172.20.110.1
set dev port1
next
edit 2
set dst 0.0.0.0/0.0.0.0
set gwy 172.20.120.2
set dev port2
next
edit 3
set dst 0.0.0.0/0.0.0.0
set gwy 172.20.130.3
set dev port3
end
4 Enter the following command to display static routes in the routing table:
get router info routing-table static
S 0.0.0.0/0 [10/0] via 172.20.110.1, port1
[10/0] via 172.20.120.2, port2
[10/0] via 172.20.130.3, port3
In this example, the FortiGate unit sends all sessions to the Internet through port1. When
port1 exceeds its spillover threshold of 400 KBps the FortiGate unit sends all new
sessions to the Internet through port2. If both port1 and port2 exceed their spillover
thresholds the FortiGate unit would send all new sessions to the Internet through port3.
Note: A new session to a destination IP address that already has an entry in the routing
cache is routed using the route already added to the cache for that destination address. For
more information, see “ECMP routing of simultaneous sessions to the same destination IP
address” on page 323.
For example, consider a FortiGate unit with interfaces port3 and port4 both connected to
the Internet through different ISPs. ECMP routing is set to usage-based and route
spillover for to 100 KBps for port3 and 200 KBps for port4. Two ECMP default routes are
added, one for port3 and one for port4.
If the route to port3 is higher in the routing table than the route to port4, the FortiGate unit
sends all default route sessions out port3 until port3 is processing 100 KBps of data.
When port3 reaches its configured bandwidth limit, the FortiGate unit sends all default
route sessions out port4. When the bandwidth usage of port3 falls below 100 KBps, the
FortiGate again sends all default route sessions out port3.
New sessions to designating IP addresses that are already in the routing cache; however,
use the cached routes. This means that even of port3 is exceeding its bandwidth limit, new
sessions can continue to be sent out port3 if their destination addresses are already in the
routing cache. As a result, new sessions are sent out port4 only if port3 exceeds its
bandwidth limit and if the routing cache does not contain a route for the destination IP
address of the new session. The limit on port4 is important only if there are additional
interfaces for spillover.
Also, the switchover to port4 does not occur as soon as port3 exceeds its bandwidth limit.
Bandwidth usage has to exceed the limit for a period of time before the switchover takes
place. If port3 bandwidth usage drops below the bandwidth limit during this time period,
sessions are not switched over to port4. This delay reduces route flapping. Route flapping
occurs when routes change their status frequently, forcing routers to continually change
their routing tables and broadcast the new information.
FortiGate usage-based ECMP routing is not actually load balancing, since routes are not
distributed evenly among FortiGate interfaces. Depending on traffic volumes, most traffic
would usually be processed by the first interface with only spillover traffic being processed
by other interfaces.
If you are configuring usage-based ECMP in most cases you should add spillover
thresholds to all of the interfaces with ECMP routes. The default spillover threshold is 0
which means no bandwidth limiting. If any interface has a spillover threshold of 0, no
sessions will be routed to interfaces lower in the list unless the interface goes down or is
disconnected. An interface can go down if Detect interface status for Gateway Load
Balancing does not receive a response from the configured server.
Weights only affect how routes are selected for sessions to new destination IP addresses.
New sessions to IP addresses already in the routing cache are routed using the route for
the session already in the cache. So in practice sessions will not always be distributed
according to the routing weight distribution.
In this example:
• one third of the sessions to the 192.168.20.0 network will use the first route and be
sent out port1 to the gateway with IP address 172.20.110.1.
• the other two thirds of the sessions to the 192.168.20.0 network will use the second
route and be sent out port2 to the gateway with IP address 172.20.120.2.
edit 1
set dst 192.168.20.0/24
set gwy 172.20.110.1
set dev port1
set weight 100
next
edit 2
set dst 192.168.20.0/24
set gwy 172.20.120.2
set dev port2
set weight 200
next
edit 3
set dst 192.168.20.0/24
set gwy 172.20.130.3
set dev port3
set weight 300
end
Note: In this example the priority remains set to 0 and the distance remains set to 10
for all three routes. Any other routes with a distance set to 10 will not have their weight
set, so will have a weight of 0 and will not be part of the load balancing.
In this example:
• one sixth of the sessions to the 192.168.20.0 network will use the first route and be
sent out port1 to the gateway with IP address 172.20.110.1.
• one third of the sessions to the 192.168.20.0 network will use the second route and be
sent out port2 to the gateway with IP address 172.20.120.2.
• one half of the sessions to the 192.168.20.0 network will use the third route and be
sent out port3 to the gateway with IP address 172.20.130.3.
Policy Route
A routing policy allows you to redirect traffic away from a static route. This can be useful if
you want to route certain types of network traffic differently. You can use incoming traffic’s
protocol, source address or interface, destination address, or port number to determine
where to send the traffic. For example, generally network traffic would go to the router of a
subnet, but you might want to direct SMTP or POP3 traffic addressed to that subnet
directly to the mail server.
If you have configured the FortiGate unit with routing policies and a packet arrives at the
FortiGate unit, the FortiGate unit starts at the top of the Policy Route list and attempts to
match the packet with a policy. If a match is found and the policy contains enough
information to route the packet (a minimum of the IP address of the next-hop router and
the FortiGate interface for forwarding packets to it), the FortiGate unit routes the packet
using the information in the policy. If no policy route matches the packet, the FortiGate unit
routes the packet using the routing table.
Note: Most policy settings are optional, so a matching policy alone might not provide
enough information for forwarding the packet. The FortiGate unit may refer to the routing
table in an attempt to match the information in the packet header with a route in the routing
table. For example, if the outgoing interface is the only item in the policy, the FortiGate unit
looks up the IP address of the next-hop router in the routing table. This situation could
happen when the interfaces are dynamic (such as DHCP or PPPoE) and you do not want
or are unable to specify the IP address of the next-hop router.
Policy route options define which attributes of a incoming packet cause policy routing to
occur. If the attributes of a packet match all the specified conditions, the FortiGate unit
routes the packet through the specified interface to the specified gateway.
Figure 173 shows the policy route list belonging to a FortiGate unit that has interfaces
named “external” and “internal”. The names of the interfaces on your FortiGate unit may
be different.
To edit an existing policy route, see “Adding a policy route” on page 329.
Delete
Edit
Move To
Create New Add a policy route. See “Adding a policy route” on page 329.
# The ID numbers of configured route policies. These numbers are sequential
unless policies have been moved within the table.
Incoming The interfaces on which packets subjected to route policies are received.
Outgoing The interfaces through which policy routed packets are routed.
Source The IP source addresses and network masks that cause policy routing to occur.
Destination The IP destination addresses and network masks that cause policy routing to
occur.
Delete icon Delete a policy route.
Edit icon Edit a policy route.
Move To icon After selecting this icon, enter the destination position in the window that
appears, and select OK.
For more information, see “Moving a policy route” on page 332.
Figure 174: Example policy route to route all HTTP traffic received at port5 to port4
Protocol To perform policy routing based on the value in the protocol field of the
packet, enter the protocol number to match. The Internet Protocol Number is
found in the IP packet header. RFC 5237 describes protocol numbers and
you can find a list of the assigned protocol numbers here. The range is from 0
to 255. A value of 0 disables the feature.
Tip: Commonly used Protocol settings include 6 to route TCP sessions, 17
for UDP sessions, 1 for ICMP sessions, 47 for GRE sessions, and 92 for
multicast sessions.
For protocols other than 6 and 17, the port number is ignored.
Incoming Interface Select the name of the interface through which incoming packets subjected to
the policy are received.
Source Address / To perform policy routing based on the IP source address of the packet, type
Mask the source address and network mask to match. A value of
0.0.0.0/0.0.0.0 disables the feature.
Destination To perform policy routing based on the IP destination address of the packet,
Address / Mask type the destination address and network mask to match. A value of
0.0.0.0/0.0.0.0 disables the feature.
Destination Ports To perform policy routing based on the port on which the packet is received,
type the same port number in the From and To fields. To apply policy routing
to a range of ports, type the starting port number in the From field and the
ending port number in the To field. A value of 0 disables this feature.
The Destination Ports fields are only used for TCP and UDP protocols. The
ports are skipped over for all other protocols.
Type of Service Use a two digit hexadecimal bit pattern to match the service, or use a two digit
hexadecimal bit mask to mask out. For more information, see “Type of
Service” on page 331.
Outgoing Interface Select the name of the interface through which packets affected by the policy
will be routed.
Gateway Address Type the IP address of the next-hop router that the FortiGate unit can access
through the specified interface. A value of 0.0.0.0 is not valid.
Protocol 6
Incoming interface port1
Source address / mask 0.0.0.0/0.0.0.0
Destination address / mask 0.0.0.0/0.0.0.0
Figure 175: Example policy route to route all FTP traffic received at port1 to port10
Type of Service
Type of service (TOS) is an 8-bit field in the IP header that enables you to determine how
the IP datagram should be delivered, with such qualities as delay, priority, reliability, and
minimum cost.
Each quality helps gateways determine the best way to route datagrams. A router
maintains a ToS value for each route in its routing table.The lowest priority TOS is 0, the
highest is 7 - when bits 3, 4,and 5 are all set to 1. The router tries to match the TOS of the
datagram to the TOS on one of the possible routes to the destination. If there is no match,
the datagram is sent over a zero TOS route.
Using increased quality may increase the cost of delivery because better performance
may consume limited network resources. For more information, see RFC 791 and RFC
1349.
Table 49: The role of each bit in the IP header TOS 8-bit field
bits 0, 1, 2 Precedence Some networks treat high precedence traffic as more important
traffic. Precedence should only be used within a network, and
can be used differently in each network. Typically you do not
care about these bits.
bit 3 Delay When set to 1, this bit indicates low delay is a priority. This is
useful for such services as VoIP where delays degrade the
quality of the sound.
bit 4 Throughput When set to 1, this bit indicates high throughput is a priority.
This is useful for services that require lots of bandwidth such
as video conferencing.
bit 5 Reliability When set to 1, this bit indicates high reliability is a priority. This
is useful when a service must always be available such as with
DNS servers.
bit 6 Cost When set to 1, this bit indicates low cost is a priority. Generally
there is a higher delivery cost associated with enabling bits 3,4,
or 5, and bit 6 indicates to use the lowest cost route.
bit 7 Reserved for Not used at this time.
future use
For example, if you want to assign low delay, and high reliability, say for a VoIP application
where delays are unacceptable, you would use a bit pattern of xxx1x1xx where an ‘x’
indicates that bit can be any value. Since all bits are not set, this is a good use for the bit
mask; if the mask is set to 0x14, it will match any TOS packets that are set to low delay
and high reliability.
Before/After Select Before to place the selected Policy Route before the indicated route.
Select After to place it following the indicated route.
Policy route ID Enter the Policy route ID of the route in the Policy route table to move the
selected route before or after.
Router Dynamic
This section explains how to configure dynamic protocols to route traffic through large or
complex networks. Dynamic routing protocols enable the FortiGate unit to automatically
share information about routes with neighboring routers and learn about routes and
networks advertised by them. The FortiGate unit supports these dynamic routing
protocols:
• Routing Information Protocol (RIP)
• Open Shortest Path First (OSPF)
• Border Gateway Protocol (BGP).
The FortiGate unit selects routes and updates its routing table dynamically based on the
rules you specify. Given a set of rules, the unit can determine the best route or path for
sending packets to a destination. You can also define rules to suppress the advertising of
routes to neighboring routers and change FortiGate routing information before it is
advertised.
If you enable virtual domains (VDOMs) on the FortiGate unit, dynamic routing is
configured separately for each virtual domain. For details, see “Using virtual domains” on
page 125.
Note: A FortiGate unit can operate as a Protocol Independent Multicast (PIM) version 2
router in the root virtual domain. FortiGate units support PIM sparse mode and dense mode
and can service multicast servers or receivers on the network segment to which a FortiGate
interface is connected. PIM can use static routes, RIP, OSPF, or BGP to forward multicast
packets to their destinations.
Bi-Directional Forwarding (BFD) is a protocol that works with BGP and OSPF to quickly
discover routers on the network that cannot be contacted, and to re-route traffic
accordingly until those routers can be contacted.
A useful part of the FortiOS web-based management interface is the customizable menus
and widgets. These widgets include the following routing widgets: access list, distribute
list, key chain, offset list, prefix list, and route map. For more information on these routing
widgets, see “Customizable routing widgets” on page 353.
This section describes:
• RIP
• OSPF
• BGP
• Multicast
• Bi-directional Forwarding Detection (BFD)
• Customizable routing widgets
RIP
Routing Information Protocol (RIP) is a distance-vector routing protocol intended for small,
relatively homogeneous networks. The FortiGate implementation of RIP supports RIP
version 1 (see RFC 1058) and RIP version 2 (see RFC 2453).
Expand
Arrow
Delete
Edit
RIP Version Select the level of RIP compatibility needed at the FortiGate unit. You
can enable global RIP settings on all FortiGate interfaces connected
to RIP-enabled networks:
1 — send and receive RIP version 1 packets.
2 — send and receive RIP version 2 packets.
You can override the global settings for a specific FortiGate interface if
required. For more information, see “Configuring a RIP-enabled
interface” on page 337.
Advanced Options Select the Expand Arrow to view or hide advanced RIP options. For
more information, see “Selecting advanced RIP options” on page 336.
Networks The IP addresses and network masks of the major networks
(connected to the FortiGate unit) that run RIP. When you add a
network to the Networks list, the FortiGate interfaces that are part of
the network are advertised in RIP updates. You can enable RIP on all
FortiGate interfaces whose IP addresses match the RIP network
address space.
IP/Netmask Enter the IP address and netmask that defines the RIP-enabled
network.
Add Select to add the network information to the Networks list.
Note: You can configure additional advanced options through customizable GUI widgets,
and the CLI. For example, you can filter incoming or outgoing updates by using a route
map, an access list, or a prefix list. The FortiGate unit also supports offset lists, which add
the specified offset to the metric of a route. For more information on customizable GUI
widgets, see “Customizable routing widgets” on page 353. For more information on CLI
routing commands, see the “router” chapter of the FortiGate CLI Reference.
Expand
Arrow
Rip Version Select the version of RIP packets to send and receive.
Advanced Options Select the Expand Arrow to view or hide advanced options.
Default Metric Enter the default hop count that the FortiGate unit should assign to routes
that are added to the FortiGate routing table. The range is from 1 to 16. This
metric is the hop count, with 1 being best or shortest.
This value also applies to Redistribute unless otherwise specified.
Default-information- Select to generate and advertise a default route into the FortiGate unit’s RIP-
originate enabled networks. The generated route may be based on routes learned
through a dynamic routing protocol, routes in the routing table, or both.
RIP Timers Enter new values to override the default RIP timer settings. The default
settings are effective in most configurations — if you change these settings,
ensure that the new settings are compatible with local routers and access
servers.
If the Update timer is smaller than Timeout or Garbage timers, you will get an
error.
Update Enter the amount of time (in seconds) that the FortiGate unit will wait
between sending RIP updates.
Timeout Enter the maximum amount of time (in seconds) that a route is considered
reachable while no updates are received for the route. This is the maximum
time the FortiGate unit will keep a reachable route in the routing table while
no updates for that route are received. If the FortiGate unit receives an
update for the route before the timeout period expires, the timer is restarted.
The Timeout period should be at least three times longer than the Update
period.
Garbage Enter the amount of time (in seconds) that the FortiGate unit will advertise a
route as being unreachable before deleting the route from the routing table.
The value determines how long an unreachable route is kept in the routing
table.
Redistribute Select one or more of the options to redistribute RIP updates about routes
that were not learned through RIP. The FortiGate unit can use RIP to
redistribute routes learned from directly connected networks, static routes,
OSPF, and BGP.
Connected Select to redistribute routes learned from directly connected networks. To
specify a hop count for those routes, select Metric, and enter the hop count
in the Metric field. The valid hop count range is from 1 to 16.
Static Select to redistribute routes learned from static routes. To specify a hop
count for those routes, select Metric, and enter the hop count in the Metric
field. The range is from 1 to 16.
OSPF Select to redistribute routes learned through OSPF. To specify a hop count
for those routes, select Metric, and enter the hop count in the Metric field.
The range is from 1 to 16.
BGP Select to redistribute routes learned through BGP. To specify a hop count for
those routes, select Metric, and enter the hop count in the Metric field. The
range is from 1 to 16.
Note: Additional options such as split-horizon and key-chains can be configured per
interface through the CLI. For more information, see the “router” chapter of the FortiGate
CLI Reference or the Fortinet Knowledge Center.
Figure 179 shows the New/Edit RIP Interface dialog box belonging to a FortiGate unit that
has an interface named “internal”. The names of the interfaces on your FortiGate unit may
be different.
Interface Select the name of the FortiGate interface to which these settings apply. The
interface must be connected to a RIP-enabled network. The interface can be a
virtual IPSec or GRE interface.
Send Version, Select to override the default RIP-compatibility setting for sending and
Receive Version receiving updates through the interface: RIP version 1, version 2 or Both.
Authentication Select an authentication method for RIP exchanges on the specified interface:
None — Disable authentication.
Text — Select if the interface is connected to a network that runs RIP version
2. Type a password (up to 35 characters) in the Password field. The FortiGate
unit and the RIP updates router must both be configured with the same
password. The password is sent in clear text over the network.
MD5 — Authenticate the exchange using MD5.
Passive Interface Select to suppress the advertising of FortiGate unit routing information over
the specified interface. Clear the check box to allow the interface to respond
normally to RIP requests.
OSPF
Open Shortest Path First (OSPF) is a link-state routing protocol that is most often used in
large heterogeneous networks to share routing information among routers in the same
Autonomous System (AS). FortiGate units support OSPF version 2 (see RFC 2328).
The main benefit of OSPF is that it advertises routes only when neighbors change state
instead of at timed intervals, so routing overhead is reduced.
OSPF-enabled routers generate Link-State Advertisements (LSA) and send them to their
neighbors whenever the status of a neighbor changes or a new neighbor comes online. As
long as the OSPF network is stable, LSAs between OSPF neighbors do not occur. An LSA
identifies the interfaces of all OSPF-enabled routers in an area, and provides information
that enables OSPF-enabled routers to select the shortest path to a destination. All LSA
exchanges between OSPF-enabled routers are authenticated.
The FortiGate unit maintains a database of link-state information based on the
advertisements that it receives from OSPF-enabled routers. To calculate the best route
(shortest path) to a destination, the FortiGate unit applies the Shortest Path First (SPF)
algorithm to the accumulated link-state information. OSPF uses relative path cost metric
for choosing the best route. The path cost can be any metric, but is typically the speed of
the path—how fast traffic will get from one point to another. The path cost, similar to
“distance” for RIP, imposes a penalty on the outgoing direction of a FortiGate interface.
The path cost of a route is calculated by adding together all of the costs associated with
the outgoing interfaces along the path to a destination. The lowest overall path cost
indicates the best route, and generally the fastest route.
Note: The inter-area routes may not be calculated when a Cisco type ABR has no fully
adjacent neighbor in the backbone area. In this situation, the router considers summary-
LSAs from all Actively summary-LSAs from all Actively Attached areas (RFC 3509).
The FortiGate unit dynamically updates its routing table based on the results of the SPF
calculation to ensure that an OSPF packet will be routed using the shortest path to its
destination. Depending on the network topology, the entries in the FortiGate routing table
may include:
• the addresses of networks in the local OSPF area (to which packets are sent directly)
• routes to OSPF area border routers (to which packets destined for another area are
sent)
• if the network contains OSPF areas and non-OSPF domains, routes to AS boundary
routers, which reside on the OSPF network backbone and are configured to forward
packets to destinations outside the OSPF AS.
The number of routes that a FortiGate unit can learn through OSPF depends on the
network topology. A single unit can support tens of thousands of routes if the OSPF
network is configured properly.
To define an OSPF AS
1 Go to Router > Dynamic > OSPF.
2 Under Areas, select Create New.
3 Define the characteristics of one or more OSPF areas. See “Defining OSPF areas” on
page 343.
4 Under Networks, select Create New.
5 Create associations between the OSPF areas that you defined and the local networks
to include in the OSPF AS. See “Specifying OSPF networks” on page 344.
6 If you need to adjust the default settings of an OSPF-enabled interface, select Create
New under Interfaces.
7 Select the OSPF operating parameters for the interface. See “Selecting operating
parameters for an OSPF interface” on page 344.
Repeat steps 6 and 7 for any additional OSPF-enabled interfaces.
8 Optionally select advanced OSPF options for the OSPF AS. See “Selecting advanced
OSPF options” on page 342.
9 Select Apply.
Expand
Arrow
Router ID Enter a unique router ID to identify the FortiGate unit to other OSPF routers.
By convention, the router ID is the numerically highest IP address assigned to
any of the FortiGate interfaces in the OSPF AS.
If you change the router ID while OSPF is configured on an interface, all
connections to OSPF neighbors will be broken temporarily. The connections
will re-establish themselves.
If Router ID is not explicitly set, the highest IP address of the VDOM or unit
will be used.
Advanced Options Select the Expand Arrow to view or hide advanced OSPF settings. For more
information, see “Selecting advanced OSPF options” on page 342.
Areas Information about the areas making up an OSPF AS. The header of an OSPF
packet contains an area ID, which helps to identify the origination of a packet
inside the AS.
Create New Define and add a new OSPF area to the Areas list. For more information, see
“Defining OSPF areas” on page 343.
Area The unique 32-bit identifiers of areas in the AS, in dotted-decimal notation.
Area ID 0.0.0.0 references the backbone of the AS and cannot be changed or
deleted.
Type The types of areas in the AS:
• Regular - a normal OSPF area
• NSSA - a not so stubby area
• Stub - a stub area.
For more information, see “Defining OSPF areas” on page 343.
Authentication The methods for authenticating OSPF packets sent and received through all
FortiGate interfaces linked to each area:
None — authentication is disabled
Text — text-based authentication is enabled
MD5 — MD5 authentication is enabled.
A different authentication setting may apply to some of the interfaces in an
area, as displayed under Interfaces. For example, if an area employs simple
passwords for authentication, you can configure a different password for one
or more of the networks in that area.
Networks The networks in the OSPF AS and their area IDs. When you add a network to
the Networks list, all FortiGate interfaces that are part of the network are
advertised in OSPF link-state advertisements. You can enable OSPF on all
FortiGate interfaces whose IP addresses match the OSPF network address
space. For more information, see “Specifying OSPF networks” on page 344.
Create New Add a network to the AS, specify its area ID, and add the definition to the
Networks list.
Network The IP addresses and network masks of networks in the AS on which OSPF
runs. The FortiGate unit may have physical or VLAN interfaces connected to
the network.
Area The area IDs that have been assigned to the OSPF network address space.
Interfaces Any additional settings needed to adjust OSPF operation on a FortiGate
interface. For more information, see “Selecting operating parameters for an
OSPF interface” on page 344.
Create New Create additional/different OSPF operating parameters for a unit interface
and add the configuration to the Interfaces list.
Name The names of OSPF interface definitions.
Interface The names of FortiGate physical or VLAN interfaces having OSPF settings
that differ from the default values assigned to all other interfaces in the same
area.
IP The IP addresses of the OSPF-enabled interfaces having additional/different
settings.
Authentication The methods for authenticating LSA exchanges sent and received on specific
OSPF-enabled interfaces. These settings override the area Authentication
settings.
Delete and Edit Delete or edit an OSPF area entry, network entry, or interface definition. Icons
icons are visible only when there are entries in Areas, Networks, and Interfaces
sections.
Expand
Arrow
Router ID Enter a unique router ID to identify the FortiGate unit to other OSPF routers.
Expand Arrow Select to view or hide Advanced Options.
Default Generate and advertise a default (external) route to the OSPF AS. You may base
Information the generated route on routes learned through a dynamic routing protocol, routes
in the routing table, or both.
None Prevent the generation of a default route.
Regular Generate a default route into the OSPF AS and advertise the route to neighboring
autonomous systems only if the route is stored in the FortiGate routing table.
Always Generate a default route into the OSPF AS and advertise the route to neighboring
autonomous systems unconditionally, even if the route is not stored in the
FortiGate routing table.
Redistribute Select one or more of the options listed to redistribute OSPF link-state
advertisements about routes that were not learned through OSPF. The FortiGate
unit can use OSPF to redistribute routes learned from directly connected networks,
static routes, RIP, and BGP.
Connected Select to redistribute routes learned from directly connected networks.
Enter a cost for those routes in the Metric field. The range is from 1 to 16 777 214.
Static Select to redistribute routes learned from static routes.
Enter a cost for those routes in the Metric field. The range is from 1 to 16 777 214.
RIP Select to redistribute routes learned through RIP.
Enter a cost for those routes in the Metric field. The range is from 1 to 16 777 214.
BGP Select to redistribute routes learned through BGP.
Enter a cost for those routes in the Metric field. The range is from 1 to 16 777 214.
Note: You can configure additional advanced options through customizable GUI widgets,
and the CLI. For example, you can filter incoming or outgoing updates by using a route
map, an access list, or a prefix list. The FortiGate unit also supports offset lists, which add
the specified offset to the metric of a route. For more information on customizable GUI
widgets, see “Customizable routing widgets” on page 353. For more information on CLI
routing commands, see the “router” chapter of the FortiGate CLI Reference.
Note: If required, you can define a virtual link to an area that has lost its physical
connection to the OSPF backbone. Virtual links can be set up only between two FortiGate
units that act as area border routers. For more information on virtual links, see the
FortiGate CLI Reference.
Area Type a 32-bit identifier for the area. The value must resemble an IP address in
dotted-decimal notation. Once you have created the OSPF area, the area IP
value cannot be changed; you must delete the area and restart.
Type Select an area type to classify the characteristics of the network that will be
assigned to the area:
Regular — If the area contains more than one router, each having at least one
OSPF-enabled interface to the area.
NSSA — If you want routes to external non-OSPF domains made known to
OSPF AS and you want the area to be treated like a stub area by the rest of the
AS.
STUB — If the routers in the area must send packets to an area border router in
order to reach the backbone and you do not want routes to non-OSPF domains to
be advertised to the routers in the area.
Authentication Select the method for authenticating OSPF packets sent and received through all
interfaces in the area:
None — Disable authentication.
Text — Enables text-based password authentication. to authenticate LSA
exchanges using a plain-text password. The password is sent in clear text over
the network.
MD5 — Enable MD5-based authentication using an MD5 cryptographic hash
(RFC 1321).
If required, you can override this setting for one or more of the interfaces in the
area. For more information, see “Selecting operating parameters for an OSPF
interface” on page 344.
Note: To assign a network to the area, see “Specifying OSPF networks” on page 344.
IP/Netmask Enter the IP address and network mask of the local network that you want to assign
to an OSPF area.
Area Select an area ID for the network. The attributes of the area must match the
characteristics and topology of the specified network. You must define the area
before you can select the area ID. For more information, see “Defining OSPF areas”
on page 343.
You can configure different OSPF parameters for the same FortiGate interface when more
than one IP address has been assigned to the interface. For example, the same FortiGate
interface could be connected to two neighbors through different subnets. You could
configure an OSPF interface definition containing one set of Hello and dead-interval
parameters for compatibility with one neighbor’s settings, and a second OSPF interface
definition for the same interface to ensure compatibility with the second neighbor’s
settings.
To select OSPF operating parameters for a FortiGate interface, go to Router > Dynamic >
OSPF, and then under Interfaces, select Create New. To edit the operating parameters of
an OSPF-enabled interface, go to Router > Dynamic > OSPF and select the Edit icon in
the row that corresponds to the OSPF-enabled interface.
Figure 184 shows the New/Edit OSPF Interface dialog box belonging to a FortiGate unit
that has an interface named “port1”. The interface names on your FortiGate unit may
differ.
Add
Name Enter a name to identify the OSPF interface definition. For example, the
name could indicate to which OSPF area the interface will be linked.
Interface Select the name of the FortiGate interface to associate with this OSPF
interface definition (for example, port1, external, or VLAN_1). The
FortiGate unit can have physical, VLAN, virtual IPSec or GRE interfaces
connected to the OSPF-enabled network.
IP Enter the IP address that has been assigned to the OSPF-enabled
interface. The interface becomes OSPF-enabled because its IP address
matches the OSPF network address space.
For example, if you defined an OSPF network of 172.20.120.0/24 and
port1 has been assigned the IP address 172.20.120.140, type
172.20.120.140.
Authentication Select an authentication method for LSA exchanges on the specified
interface:
None — Disable authentication.
Text — Authenticate LSA exchanges using a plain-text password. The
password can be up to 35 characters, and is sent in clear text over the
network.
MD5 — Use one or more keys to generate an MD5 cryptographic hash.
Password Enter the plain-text password. Enter an alphanumeric value of up to 15
characters. The OSPF neighbors that send link-state advertisements to
this FortiGate interface must be configured with an identical password.
This field is available only if you selected plain-text authentication.
MD5 Keys Enter the key identifier for the (first) password in the ID field (the range is
from 1 to 255) and then type the associated password in the Key field.
The password is a 128-bit hash, represented by an alphanumeric string of
up to 16 characters.
The OSPF neighbors that send link-state advertisements to this FortiGate
interface must be configured with an identical MD5 key. If the OSPF
neighbor uses more than one password to generate MD5 hash, select the
Add icon to add additional MD5 keys to the list.
This field is available only if you selected MD5 authentication.
Hello Interval Optionally, set the Hello Interval to be compatible with Hello Interval
settings on all OSPF neighbors.
This setting defines the period of time (in seconds) that the FortiGate unit
waits between sending Hello packets through this interface.
Dead Interval Optionally, set the Dead Interval to be compatible with Dead Interval
settings on all OSPF neighbors.
This setting defines the period of time (in seconds) that the FortiGate unit
waits to receive a Hello packet from an OSPF neighbor through the
interface. If the FortiGate unit does not receive a Hello packet within the
specified amount of time, the FortiGate unit declares the neighbor
inaccessible.
By convention, the Dead Interval value is usually four times greater than
the Hello Interval value.
BGP
Border Gateway Protocol (BGP) is an Internet routing protocol typically used by ISPs to
exchange routing information between different ISP networks. For example, BGP enables
the sharing of network paths between the ISP network and an autonomous system (AS)
that uses RIP, OSPF, or both to route packets within the AS. The FortiGate implementation
of BGP supports BGP-4 and complies with RFC 1771 and RFC 2385.
Note: You can configure graceful restarting and other advanced settings only through CLI
commands. For more information on advanced BGP settings, see the “router” chapter of
the FortiGate CLI Reference.
To view and edit BGP settings, go to Router > Dynamic > BGP. The web-based manager
offers a simplified user interface to configure basic BGP options. You can also configure
many advanced BGP options through the CLI. For more information, see the “router”
chapter of the FortiGate CLI Reference.
Delete
Local AS Enter the number of the local AS to which the FortiGate unit belongs.
Router ID Enter a unique router ID to identify the FortiGate unit to other BGP routers. The
router ID is an IP address written in dotted-decimal format, for example
192.168.0.1.
If you change the router ID while BGP is configured on an interface, all
connections to BGP peers will be broken temporarily. The connections will re-
establish themselves.
If Router ID is not explicitly set, the highest IP address of the VDOM will be
used.
Neighbors The IP addresses and AS numbers of BGP peers in neighboring autonomous
systems.
IP Enter the IP address of the neighbor interface to the BGP-enabled network.
Remote AS Enter the number of the AS that the neighbor belongs to.
Add/Edit Add the neighbor information to the Neighbors list, or edit an entry in the list.
Neighbor The IP addresses of BGP peers.
Remote AS The numbers of the autonomous systems associated with the BGP peers.
Delete icon Delete a BGP neighbor entry.
Networks The IP addresses and network masks of networks to advertise to BGP peers.
The FortiGate unit may have a physical or VLAN interface connected to those
networks.
IP/Netmask Enter the IP address and netmask of the network to be advertised.
Add Add the network information to the Networks list.
Network The IP addresses and network masks of major networks that are advertised to
BGP peers.
Delete icon Delete a BGP network definition.
Note: The get router info bgp CLI command provides detailed information about
configured BGP settings. For a complete list of the command options, see the “router”
chapter of the FortiGate CLI Reference.
Multicast
A FortiGate unit can operate as a Protocol Independent Multicast (PIM) version 2 router in
the root virtual domain. FortiGate units support PIM sparse mode (RFC 2362) and PIM
dense mode (RFC 3973) and can service multicast servers or receivers on the network
segment to which a FortiGate interface is connected.
A PIM domain is a logical area comprising a number of contiguous networks. The domain
contains at least one Boot Strap Router (BSR). If sparse mode is enabled, the domain
also contains a number of Rendezvous Points (RPs) and Designated Routers (DRs).
When you enable PIM on a FortiGate unit, the FortiGate unit can perform any of these
functions at any time as configured. If required for sparse mode operation, you can define
static RPs.
Note: You can configure basic options through the web-based manager. Many additional
options are available, but only through the CLI. For complete descriptions and examples of
how to use CLI commands to configure PIM settings, see multicast in the “router”
chapter of the FortiGate CLI Reference.
Note: For more information about FortiGate multicast support, see the FortiGate Multicast
Technical Note or the FortiGate Routing Guide.
Add Static RP
Delete
Edit
Enable Multicast Select to enable PIM version 2 routing. A firewall policy must be created on
Routing PIM-enabled interfaces to pass encapsulated packets and decapsulated data
between the source and destination,
Add Static RP If required for sparse mode operation, enter the IP address of a Rendezvous
Point (RP) that may be used as the root of a packet distribution tree for a
multicast group. Join messages from the multicast group are sent to the RP,
and data from the source is sent to the RP.
If an RP for the specified IP’s multicast group is already known to the Boot
Strap Router (BSR), the RP known to the BSR is used and the static RP
address that you specify is ignored.
Apply Save the specified static RP addresses.
Create New Create a new multicast entry for an interface.
You can use the new entry to fine-tune PIM operation on a specific FortiGate
interface or override the global PIM settings on a particular interface. For
more information, see “Overriding the multicast settings on an interface” on
page 350.
Interface The names of FortiGate interfaces having specific PIM settings.
Mode The mode of PIM operation (Sparse or Dense) on that interface.
Status The status of parse-mode RP candidacy on the interface.
To change the status of RP candidacy on an interface, select the Edit icon in
the row that corresponds to the interface.
Priority The priority number assigned to RP candidacy on that interface. Available
only when RP candidacy is enabled.
DR Priority The priority number assigned to Designated Router (DR) candidacy on the
interface. Available only when sparse mode is enabled.
Delete and Edit Delete or edit the PIM settings on the interface.
icons
Interface Select the name of the root VDOM FortiGate interface to which these
settings apply. The interface must be connected to a PIM version 2 enabled
network segment.
PIM Mode Select the mode of operation: Sparse Mode or Dense Mode. All PIM routers
connected to the same network segment must be running the same mode
of operation. If you select Sparse Mode, adjust the remaining options as
described below.
DR Priority Enter the priority number for advertising DR candidacy on the FortiGate
unit’s interface. The range is from 1 to 4 294 967 295.
The unit compares this value to the DR interfaces of all other PIM routers on
the same network segment, and selects the router having the highest DR
priority to be the DR.
RP Candidate Enable RP candidacy on the interface.
RP Candidate Priority Enter the priority number for advertising RP candidacy on the FortiGate
interface. The range is from 1 to 255.
Configuring BFD
BFD is intended for networks that use BGP or OSPF routing protocols. This generally
excludes smaller networks.
BFD configuration on your FortiGate unit is very flexible. You can enable BFD for the
whole unit, and turn it off for one or two interfaces. Alternatively you can specifically
enable BFD for each neighbor router, or interface. Which method you choose will be
determined by the amount of configuring required for your network
The timeout period determines how long the unit waits before labeling a connection as
down. The length of the timeout period is important—if it is too short connections will be
labeled down prematurely, and if it is too long time will be wasted waiting for a reply from a
connection that is down. There is no easy number, as it varies for each network and unit.
High end FortiGate models will respond very quickly unless loaded down with traffic. Also
the size of the network will slow down the response time—packets need to make more
hops than on a smaller network. Those two factors (CPU load and network traversal time)
affect how long the timeout you select should be. With too short a timeout period, BFD will
not connect to the network device but it will keep trying. This state generates unnecessary
network traffic, and leaves the device unmonitored. If this happens, you should try setting
a longer timeout period to allow BFD more time to discover the device on the network.
Access List
Access lists are filters used by FortiGate unit routing processes to limit access to the
network based on IP addresses. For an access list to take effect, it must be called by a
FortiGate unit routing process (for example, a process that supports RIP or OSPF). The
offset list is part of the RIP and OSPF routing protocols. For more information about RIP,
see “RIP” on page 334. For more information about OSPF, see “OSPF” on page 338.
Each rule in an access list consists of a prefix (IP address and netmask), the action to take
for this prefix (permit or deny), and whether to match the prefix exactly or to match the
prefix and any more specific prefix.
Note: If you are setting a prefix of 128.0.0.0, use the format 128.0.0.0/1. The default route,
0.0.0.0/0 can not be exactly matched with an access-list. A prefix-list must be used for this
purpose. For more information, see “Prefix List” on page 356.
The FortiGate unit attempts to match a packet against the rules in an access list starting at
the top of the list. If it finds a match for the prefix, it takes the action specified for that
prefix. If no match is found the default action is deny.
Access-list Enter the name of a new access list. Select Add to save the new access list.
Name The name of the access list.
Action The action to take when the prefix of this access list is matched. Actions can
be either permit or deny.
Prefix The IP address prefix for this access-list. When this prefix is matched, the
action is taken. The prefix can match any address, or a specific address.
Delete Icon Select delete to remove this access-list.
Add Icon Select to add a rule to this access-list. Rules include actions and prefixes.
Rules are processed from smallest to highest number.
For more information on access list, see the “router” chapter of the FortiGate CLI
Reference.
Distribute List
The distribute list is a subcommand of OSPF. It filters the networks in routing updates
using an access or prefix list. Routes not matched by any of the distribution lists will not be
advertised. The offset list is part of the RIP and OSPF routing protocols. For more
information about OSPF, see “OSPF” on page 338.
Note: You must configure the access list that you want the distribution list to use before you
configure the distribution list. To configure an access list, see “Access List” on page 353.
Create New Select to create a new distribute list. This includes setting the direction,
selecting either the prefix-list or access-list, and interface.
Direction The name of the access list.
Filter The prefix-list or access-list to apply to this interface.
Interface The interface to apply the filter on.
Enable A green check indicates this distribute list is enabled.
Delete Icon Select to remove a distribution list rule.
Edit Icon Select to change the direction, filter, or interface of the distribute list.
For more information on the distribute list, see the “router” chapter of the FortiGate CLI
Reference.
Key Chain
A key chain is a list of one or more keys and the send and receive lifetimes for each key.
Keys are used for authenticating routing packets only during the specified lifetimes. The
FortiGate unit migrates from one key to the next according to the scheduled send and
receive lifetimes. The sending and receiving routers should have their system dates and
times synchronized, but overlapping the key lifetimes ensures that a key is always
available even if there is some difference in the system times.
RIP version 2 uses authentication keys to ensure that the routing information exchanged
between routers is reliable. For authentication to work both the sending and receiving
routers must be set to use authentication, and must be configured with the same keys.
The offset list is part of the RIP and OSPF routing protocols. For more information about
RIP, see “RIP” on page 334.
Key-chain Enter the name for a new key-chain. Select Add to save the new key-chain.
Name The name of the key-chain, or the number of the key on that chain.
Accept Lifetime The start and end time that this key can accept routing packets.
Start The start time for this key. The format is H:M:S M/D/YYYY.
End The end time for this key. The end can be infinite, a set duration in seconds,
or a set time as with the start time.
Send Lifetime The start and end time that this key can send routing packets.
Start The start time for this key. The format is H:M:S M/D/YYYY.
End The end time for this key. The end can be infinite, a set duration in seconds,
or a set time as with the start time.
Delete Icon Select to remove a key or key-chain
Add Icon Select to add keys to the key-chain.
Edit Icon Select to edit an existing key.
For more information on key-chains, see the “router” chapter of the FortiGate CLI
Reference.
Offset List
Use the offset list to change the weighting of the metric (hop count) for a route from the
offset list.
The offset list is part of the RIP and OSPF routing protocols. For more information about
RIP, see “RIP” on page 334. For more information about OSPF, see “OSPF” on page 338.
For more information on the offset list, see the “router” chapter of the FortiGate CLI
Reference.
Prefix List
A prefix list is an enhanced version of an access list that allows you to control the length of
the prefix netmask.
Each rule in a prefix list consists of a prefix (IP address and netmask), the action to take
for this prefix (permit or deny), and maximum and minimum prefix length settings.
The FortiGate unit attempts to match a packet against the rules in a prefix list starting at
the top of the list. If it finds a match for the prefix it takes the action specified for that prefix.
If no match is found the default action is deny. A prefix-list should be used to match the
default route 0.0.0.0/0.
For a prefix list to take effect, it must be called by another FortiGate unit routing feature
such as RIP or OSPF. For more information about RIP, see “RIP” on page 334. For more
information about OSPF, see “OSPF” on page 338.
Prefix-list Enter the name of a new prefix-list. Select Add to save the new prefix list
entry.
Name The name of the prefix list, or the number of the prefix entry.
Action The action of the prefix entry. Actions can be permit or deny.
Prefix The IP address and netmask associated with this prefix. Optionally this can
be set to match any address.
GE Select the number of bits to match in the address. This number or greater
will be matched for there to be a match.
LE Select the number of bits to match in the address. This number or less will
be matched for there to be a match
Delete Icon Select to remove a prefix entry or list.
Add Icon Select to add a prefix entry to a list.
Edit Icon Select to edit an existing prefix entry.
For more information on the prefix list, see the “router” chapter of the FortiGate CLI
Reference.
Route Map
Route maps provide a way for the FortiGate unit to evaluate optimum routes for
forwarding packets or suppressing the routing of packets to particular destinations using
the BGP routing protocol. Compared to access lists, route maps support enhanced
packet-matching criteria. In addition, route maps can be configured to permit or deny the
addition of routes to the FortiGate unit routing table and make changes to routing
information dynamically as defined through route-map rules.
The FortiGate unit compares the rules in a route map to the attributes of a route. The rules
are examined in ascending order until one or more of the rules in the route map are found
to match one or more of the route attributes:
• When a single matching match-* rule is found, changes to the routing information are
made as defined through the rule’s set-ip-nexthop, set-metric, set-metric-type, and/or
set-tag settings.
• If no matching rule is found, no changes are made to the routing information.
• When more than one match-* rule is defined, all of the defined match-* rules must
evaluate to TRUE or the routing information is not changed.
• If no match-* rules are defined, the FortiGate unit makes changes to the routing
information only when all of the default match-* rules happen to match the attributes of
the route.
The default rule in the route map (which the FortiGate unit applies last) denies all routes.
For a route map to take effect, it must be called by a FortiGate unit routing process.
Route-map Enter the name of a new route-map. Select Add to save the new route-
map.
Name The name of the route map, or the number of the prefix entry.
Action The action of the route map. Actions can be permit or deny.
Rules The rules include the criteria to match and a value to set. The criteria to
match can be an interface, address from access or prefix list, the next-hop
to match from access or prefix list, a metrics, or other information. The
value to set can be the next-hop IP address, the metric, metric type, and a
tag number.
Delete Icon Select to remove a route map or entry.
Add Icon Select to add a route map entry to a route map.
Edit Icon Select to edit an existing route map entry.
For more information on the route map, see the “router” chapter of the FortiGate CLI
Reference.
Router Monitor
This section explains how to interpret the Routing Monitor list. The list displays the entries
in the FortiGate routing table.
If you enable virtual domains (VDOMs) on the FortiGate unit, router monitoring is available
separately for each virtual domain. For more information, see “Using virtual domains” on
page 125.
This section describes:
• Viewing routing information
• Searching the FortiGate routing table
IP version Select IPv4 or IPv6 routes. Fields displayed vary depending on which IP version is
selected.
Displayed only if IPv6 display is enabled on the web-based manager
Type Select one of the following route types to search the routing table and display routes
of the selected type only:
All — all routes recorded in the routing table.
Connected — all routes associated with direct connections to FortiGate interfaces.
Static — the static routes that have been added to the routing table manually. For
more information see “Static Route” on page 316.
RIP — all routes learned through RIP. For more information see “RIP” on page 334.
OSPF — all routes learned through OSPF. For more information see “OSPF” on
page 338.
BGP — all routes learned through BGP. For more information see “BGP” on
page 346
HA — RIP, OSPF, and BGP routes synchronized between the primary unit and the
subordinate units of a high availability (HA) cluster. HA routes are maintained on
subordinate units and are visible only if you are viewing the router monitor from a
virtual domain that is configured as a subordinate virtual domain in a virtual cluster.
Not displayed when IP version IPv6 is selected.
For details about HA routing synchronization, see the FortiGate HA User Guide.
Network Enter an IP address and netmask (for example, 172.16.14.0/24) to search the
routing table and display routes that match the specified network.
Not displayed when IP version IPv6 is selected.
Gateway Enter an IP address and netmask (for example, 192.168.12.1/32) to search the
routing table and display routes that match the specified gateway.
Not displayed when IP version IPv6 is selected.
Apply Filter Select to search the entries in the routing table based on the specified search criteria
and display any matching routes.
Not displayed when IP version IPv6 is selected.
Type The type values assigned to FortiGate routes (Static, Connected, RIP, OSPF, or
BGP).
Not displayed when IP version IPv6 is selected.
Subtype If applicable, the subtype classification assigned to OSPF routes.
• An empty string implies an intra-area route. The destination is in an area to which
the FortiGate unit is connected.
• OSPF inter area — the destination is in the OSPF AS, but the FortiGate unit is
not connected to that area.
• External 1 — the destination is outside the OSPF AS. The metric of a
redistributed route is calculated by adding the external cost and the OSPF cost
together.
• External 2 — the destination is outside the OSPF AS. In this case, the metric of
the redistributed route is equivalent to the external cost only, expressed as an
OSPF cost.
• OSPF NSSA 1 — same as External 1, but the route was received through a not-
so-stubby area (NSSA).
• OSPF NSSA 2 — same as External 2, but the route was received through a not-
so-stubby area.
Not displayed when IP version IPv6 is selected.
Network The IP addresses and network masks of destination networks that the FortiGate unit
can reach.
Distance The administrative distance associated with the route. A value of 0 means the route
is preferable compared to routes to the same destination.
To modify the administrative distance assigned to static routes, see “Adding a static
route to the routing table” on page 320. To modify this distance for dynamic routes,
see FortiGate CLI Reference.
Metric The metric associated with the route type. The metric of a route influences how the
FortiGate unit dynamically adds it to the routing table. The following are types of
metrics and the protocols they are applied to.
• Hop count — routes learned through RIP.
• Relative cost — routes learned through OSPF.
• Multi-Exit Discriminator (MED) — routes learned through BGP. However, several
attributes in addition to MED determine the best path to a destination network.
Gateway The IP addresses of gateways to the destination networks.
Interface The interface through which packets are forwarded to the gateway of the destination
network.
Up Time The total accumulated amount of time that a route learned through RIP, OSPF, or
BGP has been reachable.
Not displayed when IP version IPv6 is selected.
Note: All of the values that you specify as search criteria must match corresponding values
in the same routing table entry in order for that entry to be displayed.
Firewall Policy
Firewall policies control all traffic attempting to pass through the FortiGate unit, between
FortiGate interfaces, zones, and VLAN subinterfaces.
Firewall policies are instructions the FortiGate unit uses to decide connection acceptance
and packet processing for traffic attempting to pass through. When the firewall receives a
connection packet, it analyzes the packet’s source address, destination address, and
service (by port number), and attempts to locate a firewall policy matching the packet.
Firewall policies can contain many instructions for the FortiGate unit to follow when it
receives matching packets. Some instructions are required, such as whether to drop or
accept and process the packets, while other instructions, such as logging and
authentication, are optional.
Policy instructions may include network address translation (NAT), or port address
translation (PAT), by using virtual IPs or IP pools to translate source and destination IP
addresses and port numbers. For details on using virtual IPs and IP pools, see “Firewall
Virtual IP” on page 421.
Policy instructions may also include protection profiles, which can specify application-layer
inspection and other protocol-specific protection and logging. For details on using
protection profiles, see “Firewall Protection Profile” on page 467.
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall policies are
configured separately for each virtual domain, and you must first enter the virtual domain
to configure its firewall policies. For details, see “Using virtual domains” on page 125.
This section describes:
• How list order affects policy matching
• Multicast policies
• Viewing the firewall policy list
• Configuring firewall policies
• Using DoS policies to detect and prevent attacks
• Using one-arm sniffer policies to detect network attacks
• How FortiOS selects unused NAT ports
• Firewall policy examples
}Exception
}General
FTP connections would immediately match the deny policy, blocking the connection.
Other kinds of services do not match the FTP policy, and so policy evaluation would
continue until reaching the matching general policy. This policy order has the intended
effect. But if you reversed the order of the two policies, positioning the general policy
before the policy to block FTP, all connections, including FTP, would immediately match
the general policy, and the policy to block FTP would never be applied. This policy order
would not have the intended effect.
}General
}Exception
Similarly, if specific traffic requires authentication, IPSec VPN, or SSL VPN, you would
position those policies above other potential matches in the policy list. Otherwise, the
other matching policies could always take precedence, and the required authentication,
IPSec VPN, or SSL VPN might never occur.
Note: A default firewall policy may exist which accepts all connections. You can move,
disable or delete it. If you move the default policy to the bottom of the firewall policy list and
no other policy matches the packet, the connection will be accepted. If you disable or delete
the default policy and no other policy matches the packet, the connection will be dropped.
Multicast policies
FortiGate units support multicast policies. You can configure and create multicast policies
using the following CLI command:
config firewall multicast-policy
For more information, see the FortiOS CLI Reference and the FortiGate Multicast
Technical Note.
Filter
Create New Add a new firewall policy. Select the down arrow beside Create New to add a
new section to the list to visually group the policies.
For security purposes, selecting Create New adds the new policy to the bottom
of the list. Once the policy is added to the list you can use the Move To icon to
move the policy to the required position in the list. You can also use the Insert
Policy before icon to add a new policy above another policy in the list. See “How
list order affects policy matching” on page 363.
Column Settings Customize the table view. You can select the columns to hide or display and
specify the column displaying order in the table. For more information, see
“Using column settings to control the columns displayed” on page 61 and
“Web-based manager icons” on page 63.
Section View Select to display firewall policies organized by source and destination interfaces.
Note: Section View is not available if any policy selects Any as the source or
destination interface.
Global View Select to list all firewall policies in order according to a sequence number.
Filter icons Edit the column filters to filter or sort the policy list according to the criteria you
specify. For more information, see “Adding filters to web-based manager lists”
on page 57.
ID The policy identifier. Policies are numbered in the order they are added to the
policy list.
From The source interface of the policy. Global view only.
To The destination interface of the policy. Global view only.
Source The source address or address group to which the policy applies. For more
information, see “Firewall Address” on page 395.
Destination The destination address or address group to which the policy applies. For more
information, see “Firewall Address” on page 395.
Schedule The schedule that controls when the policy should be active. For more
information, see “Firewall Schedule” on page 411.
Service The service to which the policy applies. For more information, see “Firewall
Service” on page 401.
Profile The protection profile that is associated with the policy.
Action The response to make when the policy matches a connection attempt.
Status Select the checkbox to enable a policy or deselect it to disable a policy. See
“Enabling and disabling policies” on page 365.
From The source interface.
To The destination interface.
VPN Tunnel The VPN tunnel the VPN policy uses.
Authentication The user authentication method the policy uses.
Comments Comments entered when creating or editing the policy.
Log A green check mark indicates traffic logging is enabled for the policy; a grey
cross mark indicates traffic logging is disabled for the policy.
Count The FortiGate unit counts the number of packets and bytes that hit the firewall
policy.
For example, 5/50B means that five packets and 50 bytes in total have hit the
policy.
The counter is reset when the FortiGate unit is restarted or the policy is deleted
and re-configured.
Delete icon Delete the policy from the list.
Edit icon Edit a policy.
Insert Policy Add a new policy above the corresponding policy. Use this option to simplify
Before icon policy ordering. See “How list order affects policy matching” on page 363.
Move To icon Move the corresponding policy before or after another policy in the list. For more
information, see “Moving a policy to a different position in the policy list” on
page 364.
• Destination Address
• schedule and time of the session’s initiation
• service and the packet’s port numbers.
If the initial packet matches the firewall policy, the FortiGate unit performs the configured
Action and any other configured options on all packets in the session.
Packet handling actions can be ACCEPT, DENY, IPSEC or SSL-VPN.
• ACCEPT policy actions permit communication sessions, and may optionally include
other packet processing instructions, such as requiring authentication to use the policy,
or specifying a protection profile to apply features such as virus scanning to packets in
the session. An ACCEPT policy can also apply interface-mode IPSec VPN traffic if
either the selected source or destination interface is an IPSec virtual interface. For
more information, see “Overview of IPSec VPN configuration” on page 603.
• DENY policy actions block communication sessions, and may optionally log the denied
traffic.
• IPSEC and SSL-VPN policy actions apply a tunnel mode IPSec VPN or SSL VPN
tunnel, respectively, and may optionally apply NAT and allow traffic for one or both
directions. If permitted by the firewall encryption policy, a tunnel may be initiated
automatically whenever a packet matching the policy arrives on the specified network
interface, destined for the local private network. For more information, see “Configuring
IPSec firewall policies” on page 376 and “Configuring SSL VPN identity-based firewall
policies” on page 376.
To add or edit a firewall policy, go to Firewall > Policy. Select Create New to add a policy
or select the edit icon beside an existing firewall policy. Configure the settings as
described in the following table and in the references to specific features for IPSec, SSL
VPN and other specialized settings, and then select OK.
If you want to create a DoS policy, go to Firewall > Policy > DoS Policy, and configure the
settings according to the following table. DoS policies are independent from firewall
policies and are used to associate DoS sensors with traffic that reaches a FortiGate
interface. DoS policies deliver packets to the IPS before they are accepted by firewall
policies. This arrangement results in more effective protection from denial service attacks
and other benefits. For more information, see “Using DoS policies to detect and prevent
attacks” on page 379.
If you want to create a Sniffer policy, go to Firewall > Policy > Sniffer Policy, and configure
the settings according to the following table. For more information, see “Using one-arm
sniffer policies to detect network attacks” on page 382.
If you want to use IPv6 firewall addresses in your firewall policy, first go to System > Admin
> Settings. Select IPv6 Support on GUI. Then go to Firewall > Policy > IPv6 Policy, and
configure the settings according to the following table. Configuring IPv6 policies is the
same as configuring IPv4 policies. You can add a protection profile to and IPv6 firewall
policy and you can also configure shared traffic shaping and log allowed or denied traffic.
You cannot create IPv6 firewall policies for IPSec or SSL VPN and you cannot add
authentication to IPv6 policies.
Firewall policy order affects policy matching. Each time that you create or edit a policy,
make sure that you position it in the correct location in the list. You can create a new policy
and position it right away before an existing one in the firewall policy list, by selecting
Insert Policy before (see “Viewing the firewall policy list” on page 366).
Note: You can configure differentiated services (DSCP) firewall policy options through the
CLI. See the “firewall” chapter of the FortiGate CLI Reference.
Source Select the name of the FortiGate network interface, virtual domain (VDOM) link,
Interface/Zone or zone on which IP packets are received. Interfaces and zones are configured
on the System Network page. For more information, see “Configuring interfaces”
on page 145 and “Configuring zones” on page 170.
If you select Any as the source interface, the policy matches all interfaces as
source.
If Action is set to IPSEC, the interface is associated with the local private
network.
If Action is set to SSL-VPN, the interface is associated with connections from
remote SSL VPN clients.
Source Address Select the name of a firewall address to associate with the Source
Interface/Zone. Only packets whose header contains an IP address matching
the selected firewall address will be subject to this policy.
You can also create firewall addresses by selecting Create New from this list.
For more information, see “Configuring addresses” on page 397.
If you want to associate multiple firewall addresses or address groups with the
Source Interface/Zone, from Source Address, select Multiple. In the dialog box,
move the firewall addresses or address groups from the Available Addresses
section to the Members section, then select OK.
If Action is set to IPSEC, the address is the private IP address of the host,
server, or network behind the FortiGate unit.
If Action is set to SSL-VPN and the policy is for web-only mode clients, select all.
If Action is set to SSL-VPN and the policy is for tunnel mode clients, select the
name of the address that you reserved for tunnel mode clients.
Destination Select the name of the FortiGate network interface, virtual domain (VDOM) link,
Interface/Zone or zone to which IP packets are forwarded. Interfaces and zones are configured
on the System Network page. For more information, see “Configuring interfaces”
on page 145 and “Configuring zones” on page 170.
If you select Any as the destination interface, the policy matches all interfaces as
destination.
If Action is set to IPSEC, the interface is associated with the entrance to the VPN
tunnel.
If Action is set to SSL-VPN, the interface is associated with the local private
network.
Destination Select the name of a firewall address to associate with the Destination
Address Interface/Zone. Only packets whose header contains an IP address matching
the selected firewall address will be subject to this policy.
You can also create firewall addresses by selecting Create New from this list.
For more information, see “Configuring addresses” on page 397.
If you want to associate multiple firewall addresses or address groups with the
Destination Interface/Zone, from Destination Address, select Multiple. In the
dialog box, move the firewall addresses or address groups from the Available
Addresses section to the Members section, then select OK.
If you select a virtual IP, the FortiGate unit applies NAT or PAT. The applied
translation varies by the settings specified in the virtual IP, and whether you
select NAT (below). For more information on using virtual IPs, see “Firewall
Virtual IP” on page 421.
If Action is set to IPSEC, the address is the private IP address to which packets
may be delivered at the remote end of the VPN tunnel.
If Action is set to SSL-VPN, select the name of the IP address that corresponds
to the host, server, or network that remote clients need to access behind the
FortiGate unit.
Schedule Select a one-time or recurring schedule or a schedule group that controls when
the policy is in effect.
You can also create schedules by selecting Create New from this list. For more
information, see “Firewall Schedule” on page 411.
Service Select the name of a firewall service or service group that packets must match to
trigger this policy.
You can select from a wide range of predefined firewall services, or you can
create a custom service or service group by selecting Create New from this list.
For more information, see “Configuring custom services” on page 406 and
“Configuring service groups” on page 408.
By selecting the Multiple button beside Service, you can select multiple services
or service groups.
Action Select how you want the firewall to respond when a packet matches the
conditions of the policy. The options available will vary widely depending on this
selection.
ACCEPT Accept traffic matched by the policy. You can configure NAT, protection profiles,
log traffic, shape traffic, set authentication options, or add a comment to the
policy.
DENY Reject traffic matched by the policy. The only other configurable policy options
are Log Violation Traffic to log the connections denied by this policy and adding
a Comment.
IPSEC You can configure an IPSec firewall encryption policy to process IPSec VPN
packets, as well as configure protection profiles, log traffic, shape traffic or add a
comment to the policy. See “Configuring IPSec firewall policies” on page 376.
SSL-VPN You can configure an SSL-VPN firewall encryption policy to accept SSL VPN
traffic. This option is available only after you have added a SSL-VPN user group.
You can also configure NAT and protection profiles, log traffic, shape traffic or
add a comment to the policy. See “Configuring SSL VPN identity-based firewall
policies” on page 376.
NAT Available only if Action is set to ACCEPT or SSL-VPN. Enable or disable
Network Address Translation (NAT) of the source address and port of packets
accepted by the policy. When NAT is enabled, you can also configure Dynamic
IP Pool and Fixed Port.
If you select a virtual IP as the Destination Address, but do not select the NAT
option, the FortiGate unit performs destination NAT (DNAT) rather than full NAT.
Source NAT (SNAT) is not performed.
Dynamic IP Pool Select the check box, then select an IP pool to translate the source address to
an IP address randomly selected from addresses in the IP Pool.
IP Pool cannot be selected if the destination interface, VLAN subinterface, or
one of the interfaces or VLAN subinterfaces in the destination zone is configured
using DHCP or PPPoE.
For details, see “Configuring IP pools” on page 437.
Fixed Port Select Fixed Port to prevent NAT from translating the source port.
Some applications do not function correctly if the source port is translated. In
most cases, if Fixed Port is selected, Dynamic IP pool is also selected. If
Dynamic IP pool is not selected, a policy with Fixed Port selected can allow only
one connection to that service at a time.
Note: Fixed Port is only visible if enabled from the CLI.
Enable Identity Select to configure firewall policies that require authentication. For more
Based Policy information, see “Adding authentication to firewall policies” on page 372. This
section also describes the Firewall, Directory Service (FSAE), NTLM
Authentication, and Enable Disclaimer and Redirect URL to options.
Protection Select a protection profile to apply to a firewall policy. You can also create a
Profile protection profile by selecting Create New from this list. For more information,
see “Firewall Protection Profile” on page 467.
If you intend to apply authentication to this policy, do not make a Protection
Profile selection. The user group you choose for authentication is already linked
to a protection profile. For more information, see “Adding authentication to
firewall policies” on page 372.
Traffic Shaping Select a shared traffic shaper for the policy. You can also create a new shared
traffic shaper. Shared traffic shapers control the bandwidth available to and set
the priority of the traffic as its processed by, the policy.
For information about configuring shared traffic shapers, see “Configuring
shared traffic shapers” on page 417.
Reverse Select to enable reverse traffic shaping and select a shared traffic shaper. For
Direction example, if the traffic direction that a policy controls is from port1 to port2, select
Traffic this option will also apply the policy shaping configuration to traffic from port2 to
port1.
Shaping
For information about configuring shared traffic shapers, see “Configuring
shared traffic shapers” on page 417.
Per-IP Traffic Select a Per-IP traffic shaper for the policy. Per-IP traffic shaping applies traffic
Shaping shaping to the traffic generated from the IP addresses added to the Per-IP traffic
shaper added to the firewall policy.
For information about configuring per-IP traffic shapers, see “Configuring Per IP
traffic shaping” on page 419.
Log Allowed Select to record messages to the traffic log whenever the policy processes a
Traffic connection. You must also enable traffic log for a logging location (syslog,
WebTrends, local disk if available, memory, or FortiAnalyzer) and set the logging
severity level to Notification or lower using the Log and Report screen. For more
information see “Log&Report” on page 703.
Log Violation Available only if Action is set to DENY. Select Log Violation Traffic, for Deny
Traffic policies, to record messages to the traffic log whenever the policy processes a
connection. You must also enable traffic log for a logging location (syslog,
WebTrends, local disk if available, memory, or FortiAnalyzer) and set the logging
severity level to Notification or lower using the Log and Report screen. For more
information, see “Log&Report” on page 703.
Enable Endpoint Select to enable the Endpoint NAC feature and select the Endpoint NAC profile
NAC to apply. For more information, see “Endpoint NAC” on page 687.
Notes:
• You cannot enable Endpoint NAC in firewall policies if Redirect HTTP
Challenge to a Secure Channel (HTTPS) is enabled in User > Options >
Authentication.
• If the firewall policy involves a load balancing virtual IP, the Endpoint NAC
check is not performed.
Comments Add information about the policy. The maximum length is 63 characters.
Note: If you do not install certificates on the network user’s web browser, the network users
may see an SSL certificate warning message and have to manually accept the default
FortiGate certificate, which the network users’ web browsers may then deem as invalid. For
information on installing certificates, see “System Certificates” on page 279.
Note: When you use certificate authentication, if you do not specify any certificate when
you create a firewall policy, the FortiGate unit will use the default certificate from the global
settings will be used. If you specify a certificate, the per-policy setting will override the
global setting. For information on global authentication settings, see “Options” on
page 667.
Authentication requires that Action is ACCEPT or SSL-VPN, and that you first create
users, assign them to a firewall user group, and assign a protection profile to that user
group. For information on configuring user groups, see “User Group” on page 658. For
information on configuring authentication settings, see “Configuring identity-based firewall
policies” on page 373 and “Configuring SSL VPN identity-based firewall policies” on
page 376.
Schedule The one-time or recurring schedule that controls when the policy is in effect.
You can also create schedules by selecting Create New from this list. For more
information, see “Firewall Schedule” on page 411.
Protection Profile The protection profile to apply to this policy. You can also create a protection
profile by selecting Create New from this list. For more information, see
“Firewall Protection Profile” on page 467.
Traffic Shaping The traffic shaping configuration for this policy.
For more information, see “Firewall Policy” on page 363.
Reverse Select to enable the reverse traffic shaping and choose the traffic shaper. For
Direction example, if the traffic direction that a policy controls is from port1 to port2, select
Traffic Shaping this option to apply traffic shaping to traffic from port2 to port1.
Log Allowed If the Log Allowed Traffic option is selected when adding an identity-based
Traffic policy, a green check mark appears. Otherwise, a white cross mark appears.
Firewall Include firewall user groups defined locally on the FortiGate unit, as well as on
any connected LDAP and RADIUS servers. This option is selected by default.
Directory Service Include Directory Service groups defined in User > User Group. The groups are
(FSAE) authenticated through a domain controller using Fortinet Server Authentication
Extensions (FSAE). If you select this option, you must install the FSAE on the
Directory Service domain controller. For information about FSAE, see the
Fortinet Server Authentication Extension Administration Guide. For information
about configuring user groups, see “User Group” on page 658.
NTLM Include Directory Service groups defined in User > User Group. If you select
Authentication this option, you must use Directory Service groups as the members of the
authentication group for NTLM. For information about configuring user groups,
see “User Group” on page 658.
Certificate Certificate-based authentication only. Select the protection profile that guest
accounts will use. Note: In order to implement certificate-based authentication,
you must select a firewall service group that includes one of the supported
authentication protocols that use certificate-based authentication. You should
also install the certificate on the network user’s web browser. For more
information, see “Adding authentication to firewall policies” on page 372.
Enable Disclaimer Select this option to display the Authentication Disclaimer replacement
and Redirect URL message HTML page after the user authenticates. The user must accept the
to disclaimer to connect to the destination. For information about customizing user
authentication replacement messages, see “User authentication replacement
messages” on page 232.
You can also optionally enter an IP address or domain name to redirect user
HTTP requests after accepting the authentication disclaimer. The redirect URL
could be to a web page with extra information (for example, terms of usage).
.To prevent web browser security warnings, this should match the CN field of
the specified auth-cert, which is usually a fully qualified domain name
(FQDN).
VPN Tunnel Select the VPN tunnel name defined in the phase 1 configuration. The specified
tunnel will be subject to this firewall encryption policy.
Allow Inbound Select to enable traffic from a dialup client or computers on the remote private
network to initiate the tunnel.
Allow outbound Select to enable traffic from computers on the local private network to initiate
the tunnel.
Inbound NAT Select to translate the source IP addresses of inbound decrypted packets into
the IP address of the FortiGate interface to the local private network.
Outbound NAT Select only in combination with a natip CLI value to translate the source
addresses of outbound cleartext packets into the IP address that you specify.
When a natip value is specified, the source addresses of outbound IP packets
are replaced before the packets are sent through the tunnel. For more
information, see the “firewall” chapter of the FortiGate CLI Reference.
Note: For a route-based (interface mode) VPN, you do not configure an IPSec firewall
policy. Instead, you configure two regular ACCEPT firewall policies, one for each direction
of communication, with the IPSec virtual interface as the source or destination interface as
appropriate.
For more information, see the FortiGate IPSec VPN User Guide.
Note: The SSL-VPN option is only available from the Action list after you have added SSL
VPN user groups. To add SSL VPN user groups, see “SSL VPN user groups” on page 660.
Source Select the name of the FortiGate network interface, virtual domain (VDOM)
Interface/Zone link, or zone on which IP packets are received.
Source Address Select the name of a firewall address to associate with the Source
Interface/Zone. Only packets whose header contains an IP address
matching the selected firewall address will be subject to this policy.
You can also create firewall addresses by selecting Create New from this
list. For more information, see “Configuring addresses” on page 397.
If Action is set to SSL-VPN and the policy is for web-only mode clients,
select all.
If Action is set to SSL-VPN and the policy is for tunnel mode clients, select
the name of the address that you reserved for tunnel mode clients.
Destination Select the name of the FortiGate network interface, virtual domain (VDOM)
Interface/Zone link, or zone to which IP packets are forwarded. If Action is set to SSL-VPN,
the interface is associated with the local private network.
Destination Address Select the name of a firewall address to associate with the Destination
Interface/Zone. Only packets whose header contains an IP address
matching the selected firewall address will be subject to this policy.
You can also create firewall addresses by selecting Create New from this
list. For more information, see “Configuring addresses” on page 397.
If you want to associate multiple firewall addresses or address groups with
the Destination Interface/Zone, from Destination Address, select Multiple. In
the dialog box, move the firewall addresses or address groups from the
Available Addresses section to the Members section, then select OK.
If you select a virtual IP, the FortiGate unit applies NAT or PAT. The applied
translation varies by the settings specified in the virtual IP, and whether you
select NAT (below). For more information on using virtual IPs, see “Firewall
Virtual IP” on page 421.
If Action is set to IPSEC, the address is the private IP address to which
packets may be delivered at the remote end of the VPN tunnel.
If Action is set to SSL-VPN, select the name of the IP address that
corresponds to the host, server, or network that remote clients need to
access behind the FortiGate unit.
Action Select SSL-VPN to configure the firewall encryption policy to accept SSL
VPN traffic. This option is available only after you have added a SSL-VPN
user group.
SSL Client Certificate Allow traffic generated by holders of a (shared) group certificate. The
Restrictive holders of the group certificate must be members of an SSL VPN user
group, and the name of that user group must be present in the Allowed field.
Cipher Strength Select the bit level of SSL encryption. The web browser on the remote client
must be capable of matching the level that you select: Any, High >= 164, or
Medium >= 128.
User Authentication Select the authentication server type by which the user will be
Method authenticated:
Any For all of the above authentication methods. Local is attempted first, then
RADIUS, then LDAP.
Local For a local user group that will be bound to this firewall policy.
RADIUS For remote clients that will be authenticated by an external RADIUS server.
LDAP For remote clients that will be authenticated by an external LDAP server.
TACACS+ For remote clients that will be authenticated by an external TACACS+
server.
NAT Enable or disable Network Address Translation (NAT) of the source address
and port of packets accepted by the policy. When NAT is enabled, you can
also configure Dynamic IP Pool and Fixed Port.
If you select a virtual IP as the Destination Address, but do not select the
NAT option, the FortiGate unit performs destination NAT (DNAT) rather than
full NAT. Source NAT (SNAT) is not performed.
Tip: If you select NAT, the IP address of the outgoing interface of the
FortiGate unit is used as the source address for new sessions started by
SSL VPN.
Fixed Port Select Fixed Port to prevent NAT from translating the source port.
Note: Fixed Port is only visible if enabled from the CLI.
Add Select to add identity-based policies to the SSL VPN policy.
Delete icon Select to remove this identity-based policy.
Edit icon Select to modify this identity-based policy.
Move To icon Select to change the position of this identity-based policy in the identity-
based policy list.
User Group The selected user groups that must authenticate to be allowed to use this
policy.
Service The firewall service or service group that packets must match to trigger this
policy.
Schedule Select a one-time or recurring schedule that controls when the policy is in
effect.
You can also create schedules by selecting Create New from this list. For
more information, see “Firewall Schedule” on page 411.
Protection Profile Select a protection profile to apply to a firewall policy. You can also create a
protection profile by selecting Create New from this list. For more
information, see “Firewall Protection Profile” on page 467.
Traffic Shaping Select a traffic shaper for the policy. You can also select to create a new
traffic shaper. Traffic Shaping controls the bandwidth available to, and sets
the priority of the traffic processed by, the policy.
For information about traffic shaping, see “Traffic Shaping” on page 415.
Note: The traffic shaping option can be used to traffic shape tunnel-mode
SSL VPN traffic, but has no effect on web-mode SSL VPN traffic.
Reverse Direction Select to enable the reverse traffic shaping. For example, if the traffic
Traffic Shaping direction that a policy controls is from port1 to port2, select this option will
also apply the policy shaping configuration to traffic from port2 to port1.
Log Allowed Traffic Select to record messages to the traffic log whenever the policy processes
a connection. You must also enable traffic log for a logging location (syslog,
WebTrends, local disk if available, memory, or FortiAnalyzer) and set the
logging severity level to Notification or lower using the Log and Report
screen. For more information see “Log&Report” on page 703.
Comments Add information about the policy. The maximum length is 63 characters.
DoS policies examine network traffic very early in the sequence of protective measures
the FortiGate unit deploys to protect your network. Because of this, DoS policies are a
very efficient defence, using few resources. The previously mentioned denial of service
would be detected and its packets dropped before requiring firewall policy look-ups,
antivirus scans, and other protective but resource-intensive operations.
This section provides an introduction to configuring DoS Policies. For more information
see the FortiGate UTM User Guide.
Filter
Create New Add a new DoS policy. Select the down arrow beside Create New to
add a new section to the list to visually group the policies.
Column Settings Customize the table view. You can select the columns to hide or
display and specify the column displaying order in the table. See
“Using column settings to control the columns displayed” on page 61.
Section View Select to display firewall policies organized by interface.
Global View Select to list all firewall policies in order according to a sequence
number.
Filter icon Edit the column filters to filter or sort the policy list according to the
criteria you specify. For more information, see “Adding filters to
web-based manager lists” on page 57.
Status When selected, the DoS policy is enabled. Clear the checkbox to
disable the policy. See “Enabling and disabling policies” on page 365.
ID A unique identifier for each policy. Policies are numbered in the order
they are created.
Source The source address or address group to which the policy applies. For
more information, see “Firewall Address” on page 395.
Destination The destination address or address group to which the policy applies.
For more information, see “Firewall Address” on page 395.
Service The service to which the policy applies. For more information, see
“Firewall Service” on page 401.
DoS The DoS sensor selected in this policy.
Interface The interface to which this policy applies.
Delete icon Delete the policy from the list.
Edit icon Edit the policy.
Insert Policy Before icon Add a new policy above the corresponding policy (the New Policy
screen appears).
Move To icon Move the corresponding policy before or after another policy in the list.
Note: If you add VLAN interfaces to an interface configured for one-arm sniffer operation
this VLAN interface also operates in one-arm sniffer mode and you can add sniffer policies
for this VLAN interface.
After you have configured the interface for one-arm sniffer mode, connect the interface to
a hub or to the SPAN port of a switch that is processing network traffic.
Internet
SPAN
port
Hub or switch
Internal
network
Then you can go to Firewall > Policy > Sniffer Policy and add Sniffer policies for that
FortiGate interface that include a DoS sensor, an IPS sensors, and an Application
black/white list to detect attacks and other activity in the traffic that the FortiGate interface
receives from the hub or switch SPAN port.
In one-arm sniffer mode, the interface receives packets accepted by sniffer mode policies
only. All packets not received by sniffer model policies are dropped. All packets received
by sniffer mode policies go through IPS inspection and are dropped after then are
analyzed by IPS.
One-arm IDS cannot block traffic. However, if you enable logging in the DoS and IPS
sensors and the application black/white lists, the FortiGate unit records log messages for
all detected attacks and applications.
This section provides an introduction to configuring sniffer policies. For more information
see the FortiGate UTM User Guide.
Create New Add new a sniffer policy. Select the down arrow beside Create New to
add a new section to the list to visually group the policies.
Column Settings Customize the table view. You can select the columns to hide or
display and specify the column displaying order in the table. See
“Using column settings to control the columns displayed” on page 61.
Section View Select to display firewall policies organized by interface.
Global View Select to list all firewall policies in order according to a sequence
number.
Filter icon Edit column filters to filter or sort the policy list according to the criteria
you specify. For more information, see “Adding filters to web-based
manager lists” on page 57.
Status When selected, the DoS policy is enabled. Clear the checkbox to
disable the policy. See “Enabling and disabling policies” on page 365.
ID A unique identifier for each policy. Policies are numbered in the order
they are created.
Source The source address or address group to which the policy applies. For
more information, see “Firewall Address” on page 395.
Destination The destination address or address group to which the policy applies.
For more information, see “Firewall Address” on page 395.
Service The service to which the policy applies. For more information, see
“Firewall Service” on page 401.
DoS The DoS sensor selected in this policy.
Sensor The IPS sensor selected in this policy.
Application Black/White The Application Black/White List selected in this policy.
List
Delete icon Delete the policy from the list.
Edit icon Edit the policy.
Insert Policy Before icon Add a new policy above the corresponding policy (the New Policy
screen appears).
Move To icon Move the corresponding policy before or after another policy in the list.
Destination Address Select an address, address range, or address group to limit traffic
monitoring to network traffic sent to the specified address or range.
Select Multiple to include multiple addresses or ranges. You can also
select Create New to add a new address or address group.
Service Select a firewall pre-defined service or a custom service to limit traffic
monitoring to only the selected service or services. You can also
select Create new to add a custom service.
DoS Sensor Select and specify a DoS sensor to have the FortiGate unit apply the
sensor to matching network traffic. You can also select Create new to
add a new DoS Sensor. See “DoS sensors” on page 537.
IPS Sensor Select and specify an IPS sensor to have the FortiGate unit apply the
sensor to matching network traffic. You can also select Create new to
add a new IPS Sensor. See “IPS sensors” on page 529.
Application Black/White Select and specify an Application Black/White List sensor to have the
List FortiGate unit apply the application control black/white list to matching
network traffic. You can also select Create new to add a new
Application Black/White List. See “Creating a new application control
black/white list” on page 597.
Student Network
10.0.0.0/8
Video Sharing
Student A External IP 172.20.120.1
address
192.168.1.1
Internet
Student B
Search Engine
172.20.120.2
Student C
Social Networking
172.20.120.3
Student Z
The university does not give a publicly routable IP address to its students. Instead each
student uses DHCP to obtain an IP address from the 10.0.0.0/8 range from the FortiGate
unit. The FortiGate unit then uses Network Address Port Translation (NAPT) to translate
all traffic so that it appears to come from IP address 192.168.1.1.
For example, consider student A (IP address 10.78.33.97) who wants to connect to search
engine (IP address 172.20.120.2) and sends a packet with the following IP addresses and
port numbers:
src-ip: 10.78.33.97
dst-ip: 172.20.120.2
src-port: 10000
dst-port: 80
When this packet passes through the FortiGate unit with NAT enabled the packet is
modified to be:
src-ip: 92.168.1.1
dst-ip: 172.20.120.2
src-port: 46372
dst-port: 80
Where 192.168.1.1 is the external IP address of the FortiGate unit and 46372 is an
unused port chosen by the FortiGate unit.
The following sections describe three solutions to choosing the unused port. These
solutions provide some context for the last section which describes how FortiOS chooses
an unused port.
Global pool
In this approach there is a single pool of ports which are available for assignment. When a
port is assigned it is removed from the pool. Because the port is removed from the pool, it
is not possible to assign the same port twice. Once a port is no longer needed for NAT it is
returned to the pool so that it can be assigned again.
For example if the range is from 0x7000 (28672) to 0xF000 (61440) then there 215
(32768) possible ports that can be simultaneously used (the reason for choosing this
range is described below). The maximum number of simultaneous connections is 32768.
This maximum is independent of transport protocol.
This approach was one of the first approaches used to choosing a NAT port because it is
simple to implement. It is viable if the number of connections is unlikely to reach the pool
size, for example in the case of a NAT firewall for home use. However, it is not really a
viable solution for a large university or ISP that would usually be processing thousands of
simultaneous sessions.
This is not the approach that FortiOS uses.
Figure 211: Example university Internet connection topology with two Internet connections
Student Network
10.0.0.0/8
Video Sharing
Student A External IP 172.20.120.1
address
192.168.1.1
Internet
Student B
External IP
Search Engine
address
172.20.120.2
192.168.2.2
Student C
Social Networking
172.20.120.3
Student Z
If the FortiGate configuration includes equal-cost multipath (ECMP) routing, both Internet
connections can be used simultaneously and the maximum number of connections is
N*R*P where N is the number of NAT IP addresses, R is the port range, and P is the
number of protocols. So for the case where there are two NAT IPs, the range is 32768 and
the protocols are TCP and UDP then the maximum number of simultaneous connections
is:
2*32768*2 = 131,072
This solution scales with the number of NAT IPs that can be deployed and so could
feasibly be used by a university or a small ISP.
This is not the approach that FortiOS uses.
dst-port: 80
And the other index is for traffic flowing in the opposite/reply direction:
src-ip: 172.20.120.2
dst-ip: 192.168.1.1
proto: tcp
src-port: 80
dst-port: 46372
Where 46372 is the chosen NAT port. In both cases when traffic matches either of these
indexes the session that the traffic belongs to can be uniquely identified.
Using a per NAT IP, destination IP, port, and protocol pool, when choosing the NAT port
FortiOS only has to ensure that the chosen port combined with the other four attributes are
unique to uniquely identify the session. So for example, if student A simultaneously makes
a connection to the search engine (destination IP address 172.20.120.2) on port 443 this
would create another session and the index in the reply direction would be:
src-ip: 172.20.120.2
dst-ip: 192.168.1.1
proto: tcp
src-port: 443
dst-port: NP
The value of NP can be any value as long as the five values together are unique. For
example, FortiOS could choose 46372 again:
src-ip: 172.20.120.2
dst-ip: 192.168.1.1
proto: tcp
src-port: 443
dst-port: 46372
This is acceptable because:
src-ip: 172.20.120.2
dst-ip: 192.168.1.1
proto: tcp
src-port: 80
dst-port: 46372
and
src-ip: 172.20.120.2
dst-ip: 192.168.1.1
proto: tcp
src-port: 443
dst-port: 46372
have different src-port values.
The result of using the per NAT IP, destination IP, port, and protocol pool approach is that
a pool of 32768 ports are available for each unique combination of src-ip, dst-ip,
proto and src-port.
The maximum number of simultaneous connections that can be supported is
N*R*P*D*Dp where N is the number of NAT IP addresses, R is the port range, P is the
number of protocols, D is the number of unique destination IP addresses and Dp the
number of unique destination ports.
Considering the large number of destination IP addresses available, the number of
simultaneous connections that can be supported is very large. To get an idea of how
large, for one destination IP address and one NAT IP address the calculation would be
N=1, R=32, 768, P=2, D=1 and Dp=32,768:
Internet
192.168.100.1
Internal Network
Company A requires secure connections for home-based workers. Like many companies,
they rely heavily on email and Internet access to conduct business. They want a
comprehensive security solution to detect and prevent network attacks, block viruses, and
decrease spam. They want to apply different protection settings for different departments.
They also want to integrate web and email servers into the security solution.
To deal with their first requirement, Company A configures specific policies for each
home-based worker to ensure secure communication between the home-based worker
and the internal network.
1 Go to Firewall > Policy.
2 Select Create New and enter or select the following settings for Home_User_1:
Outbound NAT no
Protection Profile Select the check mark and select standard_profile
3 Select OK.
4 Select Create New and enter or select the following settings for Home_User_2:
5 Select OK.
Email Server
Internal
10.10.10.2
192.168.100.1
The proposed network is based around a ForitGate 100A unit. The 15 internal computers
are behind the FortiGate unit. They now access the email and web servers in a DMZ,
which is also behind the FortiGate unit. All home-based employees now access the office
network through the FortiGate unit via VPN tunnels.
The library must be able to set different access levels for patrons and staff members.
The first firewall policy for main office staff members allows full access to the Internet at all
times. A second policy will allow direct access to the DMZ for staff members. A second
pair of policies is required to allow branch staff members the same access.
The staff firewall policies will all use a protection profile configured specifically for staff
access. Enabled features include virus scanning, email filtering, IPS, and blocking of all
P2P traffic. FortiGuard web filtering is also used to block advertising, malware, and
spyware sites.
A few users may need special web and catalog server access to update information on
those servers, depending on how they are configured. Special access can be allowed
based on IP address or user.
The proposed topography has the main branch staff and the catalog access terminals
going through a FortiGate HA cluster to the servers in a DMZ. The public access terminals
first go through a FortiWiFi unit, where additional policies can be applied, to the HA
Cluster and finally to the servers.
The branch office has all three users routed through a FortiWiFi unit to the main branch via
VPN tunnels.
Policies are configured in Firewall > Policy. Protection Profiles are configured in Firewall >
Protection Profile.
Main office “staff to Internet” policy:
Firewall Address
Firewall addresses and address groups define network addresses that you can use when
configuring firewall policies’ source and destination address fields. The FortiGate unit
compares the IP addresses contained in packet headers with firewall policy source and
destination addresses to determine if the firewall policy matches the traffic. You can add
IPv4 addresses and address ranges, IPv6 addresses, and fully qualified domain names
(FQDNs).
You can organize related addresses into address groups and related IPv6 addresses into
IPv6 address groups to simplify your firewall policy lists.
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall addresses are
configured separately for each virtual domain, and you must first enter the virtual domain
to configure its firewall addresses. For details, see “Using virtual domains” on page 125.
This section describes:
• About firewall addresses
• About IPv6 firewall addresses
• Viewing the firewall address list
• Configuring addresses
• Viewing the address group list
• Configuring address groups
When representing hosts by an IP Range, the range indicates hosts with continuous IP
addresses in a subnet, such as 192.168.1.[2-10], or 192.168.1.* to indicate the
complete range of hosts on that subnet. Valid IP Range formats include:
• x.x.x.x-x.x.x.x, such as 192.168.110.100-192.168.110.120
• x.x.x.[x-x], such as 192.168.110.[100-120]
• x.x.x.*, such as 192.168.110.*
When representing hosts by a FQDN, the domain name can be a subdomain, such as
mail.example.com. A single FQDN firewall address may be used to apply a firewall policy
to multiple hosts, as in load balancing and high availability (HA) configurations. FortiGate
units automatically resolve and maintain a record of all addresses to which the FQDN
resolves. Valid FQDN formats include:
• <host_name>.<second_level_domain_name>.<top_level_domain_name>, such as
mail.example.com
• <host_name>.<top_level_domain_name>
Caution: Be cautious if employing FQDN firewall addresses. Using a fully qualified domain
name in a firewall policy, while convenient, does present some security risks, because
policy matching then relies on a trusted DNS server. Should the DNS server be
compromised, firewall policies requiring domain name resolution may no longer function
properly.
Delete
Edit
Create New Add a firewall address.
If IPv6 Support is enabled you can select the down arrow in the Create New
button and select IPv6 Address, to add an IPv6 firewall address. To enable IPv6
support on the web-based manager, see “Settings” on page 261.
Name The name of the firewall address.
Address / FQDN The IP address and mask, IP address range, or fully qualified domain name.
Interface The interface, zone, or virtual domain (VDOM) to which you bind the IP address.
IP/Netmask The list of IPv4 firewall addresses and address ranges.
FQDN The list of fully qualified domain name firewall addresses.
IPv6 The list of IPv6 firewall addresses.
Delete icon Select to remove the address. The Delete icon appears only if a firewall policy
or address group is not currently using the address.
Edit icon Select to edit the address.
Configuring addresses
To add a firewall address go to Firewall > Address and select Create New. You can add a
static IP address, an IP address range, or a FQDN.
Caution: Be cautious when FQDN firewall addresses. Using a fully qualified domain name
in a firewall policy, while convenient, does present some security risks, because policy
matching then relies on a trusted DNS server. Should the DNS server be compromised,
firewall policies requiring domain name resolution may no longer function properly.
If IPv6 Support is enabled, to add an IPv6 firewall address, go to Firewall > Address and
select Create New > IPv6 Address.
Tip: You can also add firewall addresses when configuring a firewall policy: Go to Firewall >
Policy, select the appropriate policy tab and then Create New. From the Source Address
list, select Address > Create New.
Address Name Enter a name to identify the firewall address. Addresses, address groups, and
virtual IPs must have unique names.
Type Select the type of address: Subnet/IP Range or FQDN. You can enter either an IP
range or an IP address with subnet mask.
Subnet / IP Enter the firewall IP address, followed by a forward slash (/), then subnet mask, or
Range enter an IP address range separated by a hyphen. See “About firewall addresses”
on page 395.
Interface Select the interface, zone, or virtual domain (VDOM) link to which you want to
bind the IP address. Select Any if you want to bind the IP address with the
interface/zone when you create a firewall policy.
IPv6 Address Enter the firewall IPv6 address, followed by a forward slash (/), then subnet mask.
See “About IPv6 firewall addresses” on page 396.
Delete
Edit
Tip: You can also create firewall address groups when configuring a firewall policy: Go to
Firewall > Policy, select the appropriate policy tab and then Create New. From the Source
Address list, select Address Group > Create New.
Group Name Enter a name to identify the address group. Addresses, address groups, and
virtual IPs must have unique names.
Available The list of all IPv4 or IPv6 firewall addresses. Use the arrows to move selected
Addresses addresses between the lists of available and member addresses.
You cannot add IPv4 and IPv6 firewall addresses to the same address group. If
you are adding an IPv4 firewall address group only the IPv4 addresses and FQDN
addresses appear. If you are added an IPv6 firewall address group, only the IPv6
addresses appear.
Members The list of addresses included in the address group. Use the arrows to move
selected addresses between the lists of available and member addresses.
Firewall Service
Firewall services define one or more protocols and port numbers associated with each
service. Firewall policies use service definitions to match session types.
You can organize related services into service groups to simplify your firewall policy list.
If you enable virtual domains (VDOMs) on the FortiGate unit, you must configure firewall
services separately for each virtual domain. For more information, see “Using virtual
domains” on page 125.
This section describes:
• Viewing the predefined service list
• Viewing the custom service list
• Configuring custom services
• Viewing the service group list
• Configuring service groups
SQUID A proxy server and web cache daemon that has a TCP 3128
wide variety of uses that includes speeding up a
web server by caching repeated requests; caching
web, DNS and other computer network lookups for
a group of people sharing network resources;
aiding security by filtering traffic.
SSH Secure Shell. SSH allows secure remote TCP 22
management and tunneling.
UDP 22
SYSLOG Syslog service for remote logging. UDP 514
TALK Talk allows conversations between two or more UDP 517-518
users.
TCP Matches connections using any TCP port. TCP 0-65535
TELNET Allows plain text remote management. TCP 23
TFTP Trivial File Transfer Protocol. TFTP is similar to UDP 69
FTP, but without security features such as
authentication.
TIMESTAMP ICMP timestamp request messages. ICMP 13
TRACEROUTE A computer network tool used to determine the TCP 33434
route taken by packets across an IP network.
UDP 33434
UDP Matches connections using any UDP port. UDP 0-65535
UUCP Unix to Unix Copy Protocol. UUCP provides simple UDP 540
file copying.
VDOLIVE VDO Live streaming multimedia traffic. TCP 7000-7010
VNC Virtual Network Computing.VNC is a graphical TCP 5900
desktop sharing system which uses the RFB
protocol to remotely control another computer.
WAIS Wide Area Information Server. WAIS is an Internet TCP 210
search protocol which may be used in conjunction
with Gopher.
Delete
Edit
Delete
Delete
Edit
To organize services into a service group, go to Firewall > Service > Group.
Tip: You can also create custom service groups when you configure a firewall policy. Go to
Firewall > Policy, select the appropriate policy tab and then Create New. From the Service
list, select Service Group > Create New.
Firewall Schedule
Firewall schedules control when policies are in effect. You can create one-time schedules
or recurring schedules. One-time schedules are in effect only once for the period of time
specified in the schedule. Recurring schedules are in effect repeatedly at specified times
of specified days of the week.
If you enable virtual domains (VDOMs) on the FortiGate unit, you must configure firewall
schedules separately for each virtual domain. For more information, see “Using virtual
domains” on page 125.
This section describes:
• Viewing the recurring schedule list
• Configuring recurring schedules
• Viewing the one-time schedule list
• Configuring one-time schedules
• Configuring schedule groups
Note: If a recurring schedule has a stop time that is earlier than the start time, the schedule
will take effect at the start time but end at the stop time on the next day. You can use this
technique to create recurring schedules that run from one day to the next. For example, to
prevent game playing except at lunchtime, you might set the start time for a recurring
schedule at 1:00 p.m. and the stop time at 12:00 noon. To create a recurring schedule that
runs for 24 hours, set the start and stop times to 00.
To view the recurring schedule list, go to Firewall > Schedule > Recurring.
Delete
Edit
Delete icon Remove the schedule from the list. The Delete icon appears only if the schedule
is not being used in a firewall policy.
Edit icon Edit the schedule.
Tip: You can also create recurring schedules when you configure a firewall policy. Go to
Firewall > Policy, select the appropriate policy tab and then Create New. From the Schedule
list, select Recurring > Create New.
Delete
Edit
Delete icon Remove the schedule from the list. The Delete icon appears only if the schedule
is not being used in a firewall policy.
Edit icon Edit the schedule.
Tip: You can also create one-time schedules when you configure a firewall policy. Go to
Firewall > Policy, select the appropriate policy tab and then Create New. From the Schedule
list, select One-time > Create New.
Traffic Shaping
Traffic shaping, once included in a firewall policy, controls the bandwidth available to, and
sets the priority of the traffic processed by, the policy. Traffic shaping makes it possible to
control which policies have the highest priority when large amounts of data are moving
through the FortiGate unit. For example, the policy for the corporate web server might be
given higher priority than the policies for most employees’ computers. An employee who
needs extra high speed Internet access could have a special outgoing policy set up with
higher bandwidth.
Traffic shaping is available for firewall policies whose Action is ACCEPT, IPSEC, or SSL-
VPN. It is also available for all supported services, including H.323, TCP, UDP, ICMP, and
ESP.
Guaranteed and maximum bandwidth in combination with queuing ensures minimum and
maximum bandwidth is available for traffic.
Traffic shaping cannot increase the total amount of bandwidth available, but you can use it
to improve the quality of bandwidth-intensive and sensitive traffic.
For more information about firewall policy, see “Firewall Policy” on page 363.
Note: For more information about traffic shaping you can also see the FortiGate Traffic
Shaping Technical Note.
Once included in a firewall policy, the guaranteed and maximum bandwidth is the total
bandwidth available to all traffic controlled by the policy. If multiple users start multiple
communications session using the same policy, all of these communications sessions
must share from the bandwidth available for the policy.
However, bandwidth availability is not shared between multiple instances of using the
same service if these multiple instances are controlled by different policies. For example,
you can create one FTP policy to limit the amount of bandwidth available for FTP for one
network address and create another FTP policy with a different bandwidth availability for
another network address.
Note: If you set both guaranteed bandwidth and maximum bandwidth to 0 (zero), the policy
does not allow any traffic.
Traffic priority
when adding a traffic shaper, you can set traffic priority to manage the relative priorities of
different types of traffic. Important and latency-sensitive traffic should be assigned a high
priority. Less important and less sensitive traffic should be assigned a low priority.
The FortiGate unit provides bandwidth to low-priority connections only when bandwidth is
not needed for high-priority connections.
For example, you can add policies to guarantee bandwidth for voice and ecommerce
traffic. Then you can assign a high priority to the policy that controls voice traffic and a
medium priority to the policy that controls e-commerce traffic. During a busy time, if both
voice and e-commerce traffic are competing for bandwidth, the higher priority voice traffic
will be transmitted before the ecommerce traffic.
Note that traffic shaping is effective for normal IP traffic at normal traffic rates. Traffic
shaping is not effective during periods when traffic exceeds the capacity of the FortiGate
unit. Since packets must be received by the FortiGate unit before they are subject to traffic
shaping, if the FortiGate unit cannot process all of the traffic it receives, then dropped
packets, delays, and latency are likely to occur.
To ensure that traffic shaping is working at its best, make sure that the interface ethernet
statistics show no errors, collisions or buffer overruns. If any of these problems do appear,
then FortiGate and switch settings may require adjusting. For more information, see the
FortiGate Traffic Shaping Technical Note.
Note: To ensure that traffic shaping is working at its best, verify that the interface ethernet
statistics show no errors, collisions, or buffer overruns. If any of these problems do appear,
then FortiGate and switch settings may require adjusting. See the “Troubleshooting”
section of the FortiGate Traffic Shaping Technical Note for information about using
diagnose commands to get this information.
Edit
Delete
Edit
Delete
Delete
Firewall Virtual IP
Virtual IP addresses (VIPs) can be used when configuring firewall policies to translate IP
addresses and ports of packets received by a network interface, including a modem
interface.
When the FortiGate unit receives inbound packets matching a firewall policy whose
Destination Address field is a virtual IP, the FortiGate unit applies NAT, replacing packets’
IP addresses with the virtual IP’s mapped IP address.
IP pools, similarly to virtual IPs, can be used to configure aspects of NAT; however, IP
pools configure dynamic translation of packets’ IP addresses based on the Destination
Interface/Zone, whereas virtual IPs configure dynamic or static translation of a packets’ IP
addresses based upon the Source Interface/Zone.
To implement the translation configured in the virtual IP or IP pool, you must add it to a
NAT firewall policy. For details, see “Configuring virtual IPs” on page 426.
Note: In Transparent mode from the FortiGate CLI you can configure NAT firewall policies
that include Virtual IPs and IP pools. See “Adding NAT firewall policies in transparent mode”
on page 442.
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall virtual IPs are
configured separately for each virtual domain. For details, see “Using virtual domains” on
page 125.
This section describes:
• How virtual IPs map connections through FortiGate units
• Viewing the virtual IP list
• Configuring virtual IPs
• Virtual IP Groups
• Viewing the VIP group list
• Configuring VIP groups
• Configuring IP pools
• Viewing the IP pool list
• Configuring IP Pools
• Double NAT: combining IP pool with virtual IP
• Adding NAT firewall policies in transparent mode
Inbound connections
Virtual IPs can be used in conjunction with firewall policies whose Action is not DENY to
apply bidirectional NAT, also known as inbound NAT.
When comparing packets with the firewall policy list to locate a matching policy, if a firewall
policy’s Destination Address is a virtual IP, FortiGate units compares packets’ destination
address to the virtual IP’s external IP address. If they match, the FortiGate unit applies the
virtual IP’s inbound NAT mapping, which specifies how the FortiGate unit translates
network addresses and/or port numbers of packets from the receiving (external) network
interface to the network interface connected to the destination (mapped) IP address or IP
address range.
In addition to specifying IP address and port mappings between interfaces, virtual IP
configurations can optionally bind an additional IP address or IP address range to the
receiving network interface. By binding an additional IP address, you can configure a
separate set of mappings that the FortiGate unit can apply to packets whose destination
matches that bound IP address, rather than the IP address already configured for the
network interface.
Depending on your configuration of the virtual IP, its mapping may involve port address
translation (PAT), also known as port forwarding or network address port translation
(NAPT), and/or network address translation (NAT) of IP addresses.
If you configure NAT in the virtual IP and firewall policy, the NAT behavior varies by your
selection of:
• static vs. dynamic NAT mapping
• the dynamic NAT’s load balancing style, if using dynamic NAT mapping
• full NAT vs. destination NAT (DNAT)
The following table describes combinations of PAT and/or NAT that are possible when
configuring a firewall policy with a virtual IP.
Static NAT Static, one-to-one NAT mapping: an external IP address is always translated to
the same mapped IP address.
If using IP address ranges, the external IP address range corresponds to a
mapped IP address range containing an equal number of IP addresses, and
each IP address in the external range is always translated to the same IP
address in the mapped range.
Static NAT with Static, one-to-one NAT mapping with port forwarding: an external IP address is
Port Forwarding always translated to the same mapped IP address, and an external port number
is always translated to the same mapped port number.
If using IP address ranges, the external IP address range corresponds to a
mapped IP address range containing an equal number of IP addresses, and
each IP address in the external range is always translated to the same IP
address in the mapped range. If using port number ranges, the external port
number range corresponds to a mapped port number range containing an equal
number of port numbers, and each port number in the external range is always
translated to the same port number in the mapped range.
Server Load Dynamic, one-to-many NAT mapping: an external IP address is translated to one
Balancing of the mapped IP addresses, as determined by the selected load balancing
algorithm for more even traffic distribution. The external IP address is not always
translated to the same mapped IP address.
Server load balancing requires that you configure at least one “real” server, but
can use up to eight. Real servers can be configured with health check monitors.
Health check monitors can be used to gauge server responsiveness before
forwarding packets.
Server Load Dynamic, one-to-many NAT mapping with port forwarding: an external IP
Balancing with address is translated to one of the mapped IP addresses, as determined by the
Port Forwarding selected load balancing algorithm for more even traffic distribution. The external
IP address is not always translated to the same mapped IP address.
Server load balancing requires that you configure at least one “real” server, but
can use up to eight. Real servers can be configured with health check monitors.
Health check monitors can be used to gauge server responsiveness before
forwarding packets.
Note: If the NAT check box is not selected when building the firewall policy, the resulting
policy does not perform full (source and destination) NAT; instead, it performs destination
network address translation (DNAT).
For inbound traffic, DNAT translates packets’ destination address to the mapped private IP
address, but does not translate the source address. The private network is aware of the
source’s public IP address. For reply traffic, the FortiGate unit translates packets’ private
network source IP address to match the destination address of the originating packets,
which is maintained in the session table.
A typical example of static NAT is to allow client access from a public network to a web
server on a private network that is protected by a FortiGate unit. Reduced to its essence,
this example involves only three hosts, as shown in Figure 236: the web server on a
private network, the client computer on another network, such as the Internet, and the
FortiGate unit connecting the two networks.
When a client computer attempts to contact the web server, it uses the virtual IP on the
FortiGate unit’s external interface. The FortiGate unit receives the packets. The addresses
in the packets are translated to private network IP addresses, and the packet is forwarded
to the web server on the private network.
The packets sent from the client computer have a source IP of 192.168.37.55 and a
destination IP of 192.168.37.4. The FortiGate unit receives these packets at its external
interface, and matches them to a firewall policy for the virtual IP. The virtual IP settings
map 192.168.37.4 to 10.10.10.42, so the FortiGate unit changes the packets’ addresses.
The source address is changed to 10.10.10.2 and the destination is changed to
10.10.10.42. The FortiGate unit makes a note of this translation in the firewall session
table it maintains internally. The packets are then sent on to the web server.
Figure 237: Example of packet address remapping during NAT from client to server
Note that the client computer’s address does not appear in the packets the server
receives. After the FortiGate unit translates the network addresses, there is no reference
to the client computer’s IP address, except in its session table. The web server has no
indication that another network exists. As far as the server can tell, all packets are sent by
the FortiGate unit.
When the web server replies to the client computer, address translation works similarly,
but in the opposite direction. The web server sends its response packets having a source
IP address of 10.10.10.42 and a destination IP address of 10.10.10.2. The FortiGate unit
receives these packets on its internal interface. This time, however, the session table is
used to recall the client computer’s IP address as the destination address for the address
translation. In the reply packets, the source address is changed to 192.168.37.4 and the
destination is changed to 192.168.37.55. The packets are then sent on to the client
computer.
The web server’s private IP address does not appear in the packets the client receives.
After the FortiGate unit translates the network addresses, there is no reference to the web
server’s network. The client has no indication that the web server’s IP address is not the
virtual IP. As far as the client is concerned, the FortiGate unit’s virtual IP is the web server.
Figure 238: Example of packet address remapping during NAT from server to client
In the previous example, the NAT check box is checked when configuring the firewall
policy. If the NAT check box is not selected when building the firewall policy, the resulting
policy does not perform full NAT; instead, it performs destination network address
translation (DNAT).
For inbound traffic, DNAT translates packets’ destination address to the mapped private IP
address, but does not translate the source address. The web server would be aware of
the client’s IP address. For reply traffic, the FortiGate unit translates packets’ private
network source IP address to match the destination address of the originating packets,
which is maintained in the session table.
Outbound connections
Virtual IPs can also affect outbound NAT, even though they are not selected in an
outbound firewall policy. If no virtual IPs are configured, FortiGate units apply traditional
outbound NAT to connections outbound from private network IP addresses to public
network IP addresses. However, if virtual IP configurations exist, FortiGate units use
virtual IPs’ inbound NAT mappings in reverse to apply outbound NAT, causing IP address
mappings for both inbound and outbound traffic to be symmetric.
For example, if a network interface’s IP address is 10.10.10.1, and its bound virtual IP’s
external IP is 10.10.10.2, mapping inbound traffic to the private network IP address
192.168.2.1, traffic outbound from 192.168.2.1 will be translated to 10.10.10.2, not
10.10.10.1
Virtual IP, load balance virtual server and load balance real server limitations
The following limitations apply when adding virtual IPs, Load balancing virtual servers,
and load balancing real servers. Load balancing virtual servers are actually server load
balancing virtual IPs. You can add server load balance virtual IPs from the CLI.
• Virtual IP External IP Address/Range entries or ranges cannot overlap with each
other or with load balancing virtual server Virtual Server IP entries.
• A virtual IP Mapped IP Address/Range cannot be 0.0.0.0 or 255.255.255.255.
• A real server IP cannot be 0.0.0.0 or 255.255.255.255.
• If a static NAT virtual IP External IP Address/Range is 0.0.0.0, the Mapped IP
Address/Range must be a single IP address.
• If a load balance virtual IP External IP Address/Range is 0.0.0.0, the Mapped IP
Address/Range can be an address range.
• When port forwarding, the count of mapped port numbers and external port
numbers must be the same. The web-based manager does this automatically but
the CLI does not.
• Virtual IP and virtual server names must be different from firewall address or
address group names.
Delete
Edit
Name Enter or change the name to identify the virtual IP. To avoid confusion,
addresses, address groups, and virtual IPs cannot have the same names.
External Interface Select the virtual IP external interface from the list. The external interface is
connected to the source network and receives the packets to be forwarded to
the destination network. You can select any FortiGate interface, VLAN
subinterface, VPN interface, or modem interface.
Type VIP type is Static NAT, read only.
External IP Enter the external IP address that you want to map to an address on the
Address/Range destination network.
To configure a dynamic virtual IP that accepts connections for any IP address,
set the external IP address to 0.0.0.0. For a static NAT dynamic virtual IP you
can only add one mapped IP address. For a load balance dynamic virtual IP
you can specify a single mapped address or a mapped address range.
Mapped IP Enter the real IP address on the destination network to which the external IP
Address/Range address is mapped.
You can also enter an address range to forward packets to multiple IP
addresses on the destination network.
For a static NAT virtual IP, if you add a mapped IP address range the FortiGate
unit calculates the external IP address range and adds the IP address range to
the External IP Address/Range field.
This option appears only if Type is Static NAT.
Port Forwarding Select to perform port address translation (PAT).
Protocol Select the protocol of the forwarded packets.
This option appears only if Port Forwarding is enabled.
External Service Enter the external interface port number for which you want to configure port
Port forwarding.
This option appears only if Port Forwarding is enabled.
Map to Port Enter the port number on the destination network to which the external port
number is mapped.
You can also enter a port number range to forward packets to multiple ports on
the destination network.
For a virtual IP with static NAT, if you add a map to port range the FortiGate unit
calculates the external port number range and adds the port number range to
the External Service port field.
This option appears only if Port Forwarding is enabled.
To configure a virtual IP
1 Go to Firewall > Virtual IP > Virtual IP.
2 Select Create New.
3 Configure the virtual IP by entering the virtual IP address, if any, that will be bound to
the network interface, and selecting the mapping type and mapped IP address(es)
and/or port(s). For configuration examples of each type, see:
• “Adding a static NAT virtual IP for a single IP address” on page 428
• “Adding a static NAT virtual IP for an IP address range” on page 429
• “Adding static NAT port forwarding for a single IP address and a single port” on
page 431
• “Adding static NAT port forwarding for an IP address range and a port range” on
page 432
• “Adding dynamic virtual IPs” on page 434
• “Adding a virtual IP with port translation only” on page 435
4 Select OK.
The virtual IP appears in the virtual IP list.
5 To implement the virtual IP, select the virtual IP in a firewall policy.
For example, to add a firewall policy that maps public network addresses to a private
network, you might add an external to internal firewall policy and select the Source
Interface/Zone to which a virtual IP is bound, then select the virtual IP in the
Destination Address field of the policy. For details, see “Configuring firewall policies” on
page 367.
3 1 3 1
2 NAT with a virtual IP 2
Internal IP Virtual IP
Server IP 10.10.10.2 192.168.37.4 Client IP
10.10.10.42 192.168.37.55
Figure 243: Virtual IP options: static NAT virtual IP for a single IP address
Name static_NAT
External Interface wan1
Type Static NAT
External IP The Internet IP address of the web server.
Address/Range The external IP address is usually a static IP address obtained from your
ISP for your web server. This address must be a unique IP address that is
not used by another host and cannot be the same as the IP address of the
external interface the virtual IP will be using. However, the external IP
address must be routed to the selected interface. The virtual IP address and
the external IP address can be on different subnets. When you add the
virtual IP, the external interface responds to ARP requests for the external IP
address.
Mapped IP The IP address of the server on the internal network. Since there is only one
Address/Range IP address, leave the second field blank.
4 Select OK.
3 Select NAT.
4 Select OK.
Internal network
Client IP
Server IP 172.168.37.55
10.10.10.42
Virtual IPs
192.168.37.4 Client IP
Server IP Internet 172.20.37.126
10.10.10.43 Internal IP 192.168.37.5
10.10.10.2 192.168.37.6
Client IP
Server IP
172.199.190.25
10.10.10.44
Figure 245: Virtual IP options: static NAT virtual IP with an IP address range
Name static_NAT_range
External Interface wan1
Type Static NAT
External IP The Internet IP address range of the web servers.
Address/Range The external IP addresses are usually static IP addresses obtained
from your ISP for your web server. These addresses must be
unique IP addresses that are not used by another host and cannot
be the same as the IP addresses of the external interface the virtual
IP will be using. However, the external IP addresses must be routed
to the selected interface. The virtual IP addresses and the external
IP address can be on different subnets. When you add the virtual
IP, the external interface responds to ARP requests for the external
IP addresses.
Mapped IP The IP address range of the servers on the internal network. Define
Address/Range the range by entering the first address of the range in the first field
and the last address of the range in the second field.
4 Select OK.
3 Select NAT.
4 Select OK.
Adding static NAT port forwarding for a single IP address and a single port
The IP address 192.168.37.4, port 80 on the Internet is mapped to 10.10.10.42, port 8000
on a private network. Attempts to communicate with 192.168.37.4, port 80 from the
Internet are translated and sent to 10.10.10.42, port 8000 by the FortiGate unit. The
computers on the Internet are unaware of this translation and see a single computer at
192.168.37.4, port 80 rather than a FortiGate unit with a private network behind it.
Figure 246: Static NAT virtual IP port forwarding for a single IP address and a single port
example
3 1 3 1
2 NAT with a virtual IP 2
and port forwarding
Source IP 10.10.10.2 Source IP 192.168.37.55
Destination IP 10.10.10.42 Destination IP 192.168.37.4
Destination port 8000 Destination Port 80
Internal IP Virtual IP
Server IP 10.10.10.2 192.168.37.4 Client IP
10.10.10.42 192.168.37.55
To add static NAT virtual IP port forwarding for a single IP address and a single port
1 Go to Firewall > Virtual IP > Virtual IP.
2 Select Create New.
3 Use the following procedure to add a virtual IP that allows users on the Internet to
connect to a web server on the DMZ network. In our example, the wan1 interface of the
FortiGate unit is connected to the Internet and the dmz1 interface is connected to the
DMZ network.
Figure 247: Virtual IP options: Static NAT port forwarding virtual IP for a single IP address
and a single port
Name Port_fwd_NAT_VIP
External Interface wan1
To add static NAT virtual IP port forwarding for a single IP address and a single port
to a firewall policy
Add a wan1 to dmz1 firewall policy that uses the virtual IP so that when users on the
Internet attempt to connect to the web server IP addresses, packets pass through the
FortiGate unit from the wan1 interface to the dmz1 interface. The virtual IP translates the
destination addresses and ports of these packets from the external IP to the dmz network
IP addresses of the web servers.
1 Go to Firewall > Policy and select Create New.
2 Configure the firewall policy:
3 Select NAT.
4 Select OK.
Adding static NAT port forwarding for an IP address range and a port range
Ports 80 to 83 of addresses 192.168.37.4 to 192.168.37.7 on the Internet are mapped to
ports 8000 to 8003 of addresses 10.10.10.42 to 10.10.10.44 on a private network.
Attempts to communicate with 192.168.37.5, port 82 from the Internet, for example, are
translated and sent to 10.10.10.43, port 8002 by the FortiGate unit. The computers on the
Internet are unaware of this translation and see a single computer at 192.168.37.5 rather
than a FortiGate unit with a private network behind it.
Figure 248: Static NAT virtual IP port forwarding for an IP address range and a port range
example
To add static NAT virtual IP port forwarding for an IP address range and a port
range
1 Go to Firewall > Virtual IP > Virtual IP.
2 Select Create New.
3 Use the following procedure to add a virtual IP that allows users on the Internet to
connect to a web server on the DMZ network. In this example, the external interface of
the FortiGate unit is connected to the Internet and the dmz1 interface is connected to
the DMZ network.
Figure 249: Virtual IP options: Static NAT port forwarding virtual IP for a range of IP
addresses and a range of ports
Name Port_fwd_NAT_VIP_port_range
External Interface external
Type Static NAT
External IP The external IP addresses are usually static IP addresses obtained
Address/Range from your ISP. This addresses must be unique, not used by another
host, and cannot be the same as the IP address of the external
interface the virtual IP will be using. However, the external IP
addresses must be routed to the selected interface. The virtual IP
addresses and the external IP address can be on different subnets.
When you add the virtual IP, the external interface responds to ARP
requests for the external IP addresses.
Mapped IP The IP addresses of the server on the internal network. Define the
Address/Range range by entering the first address of the range in the first field and
the last address of the range in the second field.
Port Forwarding Selected
Protocol TCP
External Service Port The ports that traffic from the Internet will use. For a web server,
this will typically be port 80.
Map to Port The ports on which the server expects traffic. Define the range by
entering the first port of the range in the first field and the last port of
the range in the second field. If there is only one port, leave the
second field blank.
4 Select OK.
To add static NAT virtual IP port forwarding for an IP address range and a port
range to a firewall policy
Add a external to dmz1 firewall policy that uses the virtual IP so that when users on the
Internet attempt to connect to the web server IP addresses, packets pass through the
FortiGate unit from the external interface to the dmz1 interface. The virtual IP translates
the destination addresses and ports of these packets from the external IP to the dmz
network IP addresses of the web servers.
1 Go to Firewall > Policy and select Create New.
2 Configure the firewall policy:
3 Select NAT.
4 Select OK.
Note: To apply port forwarding to the external interface without binding a virtual IP address
to it, enter the IP address of the network interface instead of a virtual IP address, then
configure port forwarding as usual.
To disable arp-reply
In some cases, when you have completed this configuration the FortiGate unit will drop
the packets received on the External Interface. To make sure this does not happen you
can log into the FortiGate CLI and use the following procedure to disable arp replies for
the port translation only virtual IP.
1 Log into the FortiGate CLI.
2 Enter the following command where <vip_name> is the name of the port translation
only virtual IP.
config firewall vip
edit <vip_name>
set arp-reply disable
end
Virtual IP Groups
You can organize multiple virtual IPs into a virtual IP group to simplify your firewall policy
list. For example, instead of having five identical policies for five different but related virtual
IPs located on the same network interface, you might combine the five virtual IPs into a
single virtual IP group, which is used by a single firewall policy.
Firewall policies using VIP Groups are matched by comparing both the member VIP IP
address(es) and port number(s).
Delete
Edit
Create New Select to add a new VIP group. See “Configuring VIP groups” on page 436.
Group Name The name of the virtual IP group.
Members Lists the group members.
Interface Displays the interface that the VIP group belongs to.
Delete icon Remove the VIP group from the list. The Delete icon only appears if the VIP
group is not being used in a firewall policy.
Edit icon Edit the VIP group information, including the group name and membership.
Configuring IP pools
Use IP pools to add NAT policies that translate source addresses to addresses randomly
selected from the IP pool, rather than the IP address assigned to that FortiGate unit
interface. In Transparent mode, IP pools are available only from the FortiGate CLI.
An IP pool defines a single IP address or a range of IP addresses. A single IP address in
an IP pool becomes a range of one IP address. For example, if you enter an IP pool as
1.1.1.1 the IP pool is actually the address range 1.1.1.1 to 1.1.1.1.
If a FortiGate interface IP address overlaps with one or more IP pool address ranges, the
interface responds to ARP requests for all of the IP addresses in the overlapping IP pools.
For example, consider a FortiGate unit with the following IP addresses for the port1 and
port2 interfaces:
• port1 IP address: 1.1.1.1/255.255.255.0 (range is 1.1.1.0-1.1.1.255)
• port2 IP address: 2.2.2.2/255.255.255.0 (range is 2.2.2.0-2.2.2.255)
And the following IP pools:
• IP_pool_1: 1.1.1.10-1.1.1.20
• IP_pool_2: 2.2.2.10-2.2.2.20
• IP_pool_3: 2.2.2.30-2.2.2.40
The port1 interface overlap IP range with IP_pool_1 is:
• (1.1.1.0-1.1.1.255) and (1.1.1.10-1.1.1.20) = 1.1.1.10-1.1.1.20
192.168.1.2 172.16.30.2
...... ......
192.168.1.254 172.16.30.254
Scenario 2: The number of source addresses is more than that of IP pool addresses
In this case, the FortiGate unit translates IP addresses using a wrap-around mechanism.
If you enable fixedport in such a case, the FortiGate unit preserves the original source
port. But conflicts may occur since users may have different sessions using the same TCP
5 tuples.
Scenario 3: The number of source addresses is fewer than that of IP pool addresses
In this case, some of the IP pool addresses are used and the rest of them are not be used.
Delete
Edit
Configuring IP Pools
To add an IP pool, go to Firewall > Virtual IP > IP Pool.
10.1.1.0/24
Router Without
NAT
Router Without
NAT
172.16.1.1
172.16.1.3
To allow the local users to access the server, you can use fixed port and IP pool to allow
more than one user connection while using virtual IP to translate the destination port from
8080 to 80.
To create an IP pool
1 Go to Firewall > Virtual IP > IP Pool.
2 Select Create New.
3 Enter the following information and select OK.
Name pool-1
IP Range/Subnet 10.1.3.1-10.1.3.254
Name server-1
External Interface Internal
Type Static NAT
External IP Address/Range 172.16.1.1
Note this address is the same as the server address.
Mapped IP Address/Range 172.16.1.1.
Port Forwarding Enable
Protocol TCP
External Service Port 8080
Map to Port 80
4 Select OK.
The example describes adding an internal to wan1 firewall policy to relay these packets
from the internal interface out the wan1 interface to the Internet. Because the wan1
interface does not have an IP address of its own, you must add an IP pool to the wan1
interface that translates the source addresses of the outgoing packets to an IP address on
the network connected to the wan1 interface.
The example describes adding an IP pool with a single IP address of 10.1.1.201. So all
packets sent by a PC on the internal network that are accepted by the internal to wan1
policy leave the wan1 interface with their source address translated to 10.1.1.201. These
packets can now travel across the Internet to their destination. Reply packets return to the
wan1 interface because they have a destination address of 10.1.1.201. The internal to
wan1 NAT policy translates the destination address of these return packets to the IP
address of the originating PC and sends them out the internal interface to the originating
PC.
Use the following steps to configure NAT in Transparent mode
• Adding two management IPs
• Adding an IP pool to the wan1 interface
• Adding an internal to wan1 firewall policy
Internet
Internal network
Transparent mode 192.168.1.0/24
Management IPs:
Router 10.1.1.99
192.168.1.99
DMZ
DMZ network
10.1.1.0/24
Note: You can add the firewall policy from the web-based manager and then use the CLI to
enable NAT and add the IP Pool.
Internet/Intranet
User
LAN/WAN
Real Server
Delete
Edit
Create New Select to add virtual servers. For more information, see “To create a
virtual server” on page 447.
Name Name of the virtual server.
Type The protocol load balanced by the virtual server.
Comments A description of the virtual server.
Virtual Server IP The IP address of the virtual server. This is an IP address on the external
interface that you want to map to an address on the destination network.
Virtual server Port The external port number that you want to map to a port number on the
destination network. Sessions with this destination port are load
balanced by this virtual server.
Load Balance Method The load balancing method for this virtual server.
Health Check The health check monitor selected for this virtual server. For more
information, see “Health Check” on page 450.
Persistence The type of persistence applied to this virtual server.
Delete icon Remove the virtual server from the list. The Delete icon only appears if
the virtual server is not bound to a real server.
Edit icon Edit the virtual server to change any virtual server option including the
virtual server name.
Name Enter the name for the virtual server. This name is not the hostname for the
FortiGate unit.
Type Select the protocol to be load balanced by the virtual server. If you select a
general protocol such as IP, TCP, or UDP the virtual server load balances all IP,
TCP, or UDP sessions. If you select specific protocols such as HTTP, HTTPS, or
SSL you can apply additional server load balancing features such as Persistence
and HTTP Multiplexing.
• Select HTTP to load balance only HTTP sessions with destination port
number that matches the Virtual Server Port setting. Change Virtual Server
Port to match the destination port of the sessions to be load balanced (usually
port 80 for HTTP sessions). You can also select HTTP Multiplex. You can also
set Persistence to HTTP Cookie to select cookie-based persistence. See the
description of the config firewall VIP command in the FortiGate CLI
Reference for information about advanced HTTP Cookie persistence options.
• Select HTTPS to load balance only HTTPS sessions with destination port
number that matches the Virtual Server Port setting. Change Virtual Server
Port to match the destination port of the sessions to be load balanced (usually
port 443 for HTTPS sessions). You can also select HTTP Multiplex. You can
also set Persistence to HTTP Cookie to select cookie-based persistence. You
can also set Persistence to SSL Session ID. See the description of the
config firewall VIP command in the FortiGate CLI Reference for
information about advanced HTTP Cookie persistence options and advanced
SSL options. HTTPS is available on FortiGate units that support SSL
acceleration.
• Select IP to load balance all sessions accepted by the firewall policy that
contains this virtual server.
• Select SSL to load balance only SSL sessions with destination port number
that matches the Virtual Server Port setting. Change Virtual Server Port to
match the destination port of the sessions to be load balanced.See the
description of the config firewall VIP command in the FortiGate CLI
Reference for information about advanced SSL options.
• Select TCP to load balance only TCP sessions with destination port number
that matches the Virtual Server Port setting. Change Virtual Server Port to
match the destination port of the sessions to be load balanced.
• Select UDP to load balance only UDP sessions with destination port number
that matches the Virtual Server Port setting. Change Virtual Server Port to
match the destination port of the sessions to be load balanced.
Interface Select the virtual server external interface from the list. The external interface is
connected to the source network and receives the packets to be forwarded to the
destination network.
Virtual Server The IP address of the virtual server. This is an IP address on the external
IP interface that you want to map to an address on the destination network.
Virtual server Enter the external port number that you want to map to a port number on the
Port destination network. Sessions with this destination port are load balanced by this
virtual server.
SSL Select to accelerate clients’ SSL connections to the server by using the FortiGate
Offloading unit to perform SSL operations, then select which segments of the connection
will receive SSL offloading.
• Client <-> FortiGate
Select to apply hardware accelerated SSL only to the part of the connection
between the client and the FortiGate unit. The segment between the
FortiGate unit and the server will use clear text communications. This results
in best performance, but cannot be used in failover configurations where the
failover path does not have an SSL accelerator.
• Client <-> FortiGate <-> Server
Select to apply hardware accelerated SSL to both parts of the connection: the
segment between client and the FortiGate unit, and the segment between the
FortiGate unit and the server. The segment between the FortiGate unit and
the server will use encrypted communications, but the handshakes will be
abbreviated. This results in performance which is less than the other option,
but still improved over communications without SSL acceleration, and can be
used in failover configurations where the failover path does not have an SSL
accelerator. If the server is already configured to use SSL, this also enables
SSL acceleration without requiring changes to the server’s configuration.
SSL 3.0 and TLS 1.0 are supported.
SSL Offloading appears only if HTTPS or SSL are selected for Type, and only on
FortiGate models with hardware that supports SSL acceleration.
Note: Additional SSL Offloading options are available in the CLI. For more
information, see the FortiGate CLI Reference.
Certificate Select the certificate to use with SSL Offloading. The certificate key size must be
1024 or 2048 bits. 4096-bit keys are not supported.
This option appears only if HTTPS or SSL are selected for Type, and is available
only if SSL Offloading is selected.
Health Check Select which health check monitor configuration will be used to determine a
server’s connectivity status.
For information on configuring health check monitors, see “Configuring health
check monitors” on page 451.
Comments Any comments or notes about this virtual server.
3 Select OK.
Delete
Edit
Create New Select to add real servers. For more information, see “To create a real
server” on page 451.
IP Address Select the blue arrow beside a virtual server name to view the IP
addresses of the real servers that are bound to it.
Port The port number on the destination network to which the external port
number is mapped.
Weight The weight value of the real server. The higher the weight value, the
higher the percentage of connections the server will handle.
Max Connections The limit on the number of active connections directed to a real server. If
the maximum number of connections is reached for the real server, the
FortiGate unit will automatically switch all further connection requests to
another server until the connection number drops below the specified
limit.
Delete icon Remove the real server from the list.
Edit icon Edit the real server to change any virtual server option.
Virtual Server Select the virtual server to which you want to bind this real server.
IP Enter the IP address of the real server.
Port Enter the port number on the destination network to which the external
port number is mapped.
Weight Enter the weight value of the real server. The higher the weight value,
the higher the percentage of connections the server will handle. A
range of 1-255 can be used. This option is available only if the
associated virtual server’s load balance method is Weighted.
Maximum Connections Enter the limit on the number of active connections directed to a real
server. A range of 1-99999 can be used. If the maximum number of
connections is reached for the real server, the FortiGate unit will
automatically switch all further connection requests to another server
until the connection number drops below the specified limit.
Setting Maximum Connections to 0 means that the FortiGate unit does
not limit the number of connections to the real server.
3 Select OK.
Delete
Edit
Create New Select to add a health check monitor configuration. For more information, see
“To create a health check monitor configuration” on page 452.
Name The name of the health check monitor configuration. The names are grouped
by the health check monitor types.
Details The details of the health check monitor configuration, which vary by the type of
the health check monitor, and do not include the interval, timeout, or retry,
which are settings common to all types.
This field is empty if the type of the health check monitor is PING.
Delete Select to remove the health check monitor configuration. This option appears
only if the health check monitor configuration is not currently being used by a
virtual server configuration.
Edit Select to change the health check monitor configuration.
URL For HTTP health check monitors, add a URL that the FortiGate unit uses
when sending a get request to check the health of a HTTP server. The URL
should match an actual URL for the real HTTP servers. The URL is optional.
The URL would not usually include an IP address or domain name. Instead
it should start with a “/” and be followed by the address of an actual web
page on the real server. For example, if the IP address of the real server is
10.10.10.1, the URL “/test_page.htm” causes the FortiGate unit to send an
HTTP get request to “http://10.10.10.1/test_page.htm”.
This option appears only if Type is HTTP.
Matched Content For HTTP health check monitors, add a phrase that a real HTTP server
should include in response to the get request sent by the FortiGate unit
using the content of the URL option. If the URL returns a web page, the
Matched Content should exactly match some of the text on the web page.
You can use the URL and Matched Content options to verify that an HTTP
server is actually operating correctly by responding to get requests with
expected web pages. Matched content is only required if you add a URL.
For example, you can set Matched Content to “server test page” if the real
HTTP server page defined by the URL option contains the phrase “server
test page”. When the FortiGate unit receives the web page in response to
the URL get request, the system searches the content of the web page for
the Matched Content phrase.
This option appears only if Type is HTTP.
Interval Enter the number of seconds between each server health check.
Timeout Enter the number of seconds which must pass after the server health check
to indicate a failed health check.
Retry Enter the number of times, if any, a failed health check will be retried before
the server is determined to be inaccessible.
3 Select OK.
DMZ network
Real HTTP
Server IP
10.10.10.42 Virtual Server IP
192.168.37.4
Real HTTP
Server IP dmz1 IP
10.10.10.43 10.10.10.2 Client IP
172.199.190.25
Real HTTP
Server IP
10.10.10.44
Name HTTP_health_chk_1
Type HTTP
Port 80
URL /index.html
Matched Content Fortinet products
Interval 10 seconds
Timeout 2 seconds
Retry 3
4 Select OK.
Name Load_Bal_VS1
Type HTTP
Interface wan1
Virtual Server IP 192.168.37.4
The public IP address of the web server.
The virtual server IP address is usually a static IP address
obtained from your ISP for your web server. This address must be
a unique IP address that is not used by another host and cannot be
the same as the IP address of the external interface the virtual IP
will be using. However, the external IP address must be routed to
the selected interface. The virtual IP address and the external IP
address can be on different subnets. When you add the virtual IP,
the external interface responds to ARP requests for the external IP
address.
Virtual Server Port 80
Load Balance Method First Alive
Persistence HTTP cookie
HTTP Multiplexing Select.
The FortiGate unit multiplexes multiple client into a few
connections between the FortiGate unit and a real HTTP server.
This can improve performance by reducing server overhead
associated with establishing multiple connections.
Preserve Client IP Select
The FortiGate unit preserves the IP address of the client in the X-
Forwarded-For HTTP header.
Health Check Move the HTTP_health_chk_1 health check monitor to the
Selected list.
4 Select OK.
To add the real servers and associate them with the virtual server
1 Go to Firewall > Load Balance > Real Server.
2 Select Create New.
3 Configure three real servers that include the virtual server Load_Bal_VS1. Each real
server must include the IP address of a real server on the internal network.
Weight Cannot be configured because the virtual server does not include
weighted load balancing.
Maximum Connections 0
Setting Maximum Connections to 0 means the FortiGate unit does
not limit the number of connections to the real server. Since the
virtual server uses First Alive load balancing you may want to limit
the number of connections to each real server to limit the traffic
received by each server. In this example, the Maximum
Connections is initially set to 0 but can be adjusted later if the real
servers are getting too much traffic.
Service HTTP
Action ACCEPT
NAT Select
Log Allowed Traffic Select to log virtual server traffic
4 Select other firewall options as required.
5 Select OK.
DMZ network
Real HTTP
Server IP
10.10.10.42 Virtual Server IP
192.168.37.4
Real HTTP
Server IP dmz1 IP
10.10.10.43 10.10.10.2 Client IP
172.199.190.25
Real HTTP
Server IP
10.10.10.44
To complete this configuration, all of the steps would be the same as in “Configuring a
virtual web server with three real web servers” on page 454 except for configuring the real
servers.
To add the real servers and associate them with the virtual server
Use the following steps to configure the FortiGate unit to port forward HTTP packets to the
three real servers on ports 8080, 8081, and 8082.
1 Go to Firewall > Load Balance > Real Server.
2 Select Create New.
3 Configure three real servers that include the virtual server Load_Bal_VS1. Each real
server must include the IP address of a real server on the internal network and have a
different port number.
Configuration for the first real server.
Name All_Load_Balance
Type IP
Interface port2
Virtual Server IP 192.168.20.20
Load Balance Method Weighted
All other virtual server settings are not required or cannot be changed.
4 Select OK.
To add the real servers and associate them with the virtual server
1 Go to Firewall > Load Balance > Real Server.
2 Select Create New.
3 Configure three real servers that include the virtual server All_Load _Balance.
Because the Load Balancing Method is Weighted, each real server includes a weight.
Servers with a greater weight receive a greater proportion of forwarded connections,
Configuration for the first real server.
CLI configuration
Load balancing is configured from the CLI using the config firewall vip command
and by setting type to server-load-balance. The default weight is 1 and does not
have to be changed for the first real server.
Use the following command to add the virtual server and the three weighted real servers.
config firewall vip
edit All_Load_Balance
set type server-load-balance
set server-type ip
set extintf port2
set extip 192.168.20.20
set ldb-method weighted
config realservers
edit 1
set ip 10.10.10.1
next
edit 2
set ip 10.10.10.2
set weight 2
next
edit 3
set ip 10.10.10.3
set weight 3
end
end
Name HTTP_Load_Balance
Type HTTP
Interface port2
Virtual Server IP 192.168.20.20
Virtual Server Port 80
In this example the virtual server uses port 8080 for HTTP
sessions instead of port 80.
Load Balance Method Static
Persistence HTTP cookie
3 Select OK.
4 Select Create New.
5 Add the HTTPs virtual server that also includes HTTP Cookie persistence.
Name HTTPS_Load_Balance
Type HTTPS
Interface port2
Virtual Server IP 192.168.20.20
Virtual Server Port 443
Load Balance Method Static
Persistence HTTP cookie
6 Select OK.
To add the real servers and associate them with the virtual servers
1 Go to Firewall > Load Balance > Real Server.
2 Select Create New.
3 Configure three real servers for HTTP that include the virtual server
HTTP_Load_Balance.
Configuration for the first HTTP real server.
4 Configure three real servers for HTTPS that include the virtual server
HTTPS_Load_Balance.
Configuration for the first HTTPS real server.
Note: If the firewall policy requires authentication, do not select the protection profile in the
firewall policy. The protection profile is specific to the authenticating user group. For details
on configuring the protection profile associated with the user group, see “Configuring a user
group” on page 661.
• application control
• logging for traffic which violates the protection profile.
Strict Apply maximum protection to HTTP, FTP, IMAP, POP3, and SMTP traffic. The
strict protection profile may not be useful under normal circumstances, but it is
available when maximum protection is required.
Scan Apply virus scanning to HTTP, FTP, IMAP, POP3, and SMTP traffic. Quarantine is
also selected for all content services. On FortiGate models with a hard drive, if
antivirus scanning finds a virus in a file, the file is quarantined on the FortiGate
hard disk. If a FortiAnalyzer unit is configured, files are quarantined remotely.
Quarantine permits system administrators to inspect, recover, or submit
quarantined files to Fortinet for analysis.
Web Apply virus scanning and web content filtering to HTTP traffic. Add this protection
profile to firewall policies that control HTTP traffic.
Unfiltered Apply no scanning, blocking or IPS. Use the unfiltered content profile if no content
protection for content traffic is required. Add this protection profile to firewall
policies for connections between highly trusted or highly secure networks where
content does not need to be protected.
Delete
Edit
Create New Add a protection profile.
Name The name of the protection profile.
Delete icon Delete a protection profile from the list. The Delete icon appears only if the
protection profile is not currently selected in a firewall policy or user group.
Edit icon Modify a protection profile.
Figure 271: FortiGate SSL content scanning and inspection packet flow
3 1
2
Decrypted
packets
Encrypted 3
2
1 3
2
1
Encrypted
packets Firewall packets
While the SSL sessions are being set up, the client and server communicate in clear text
to exchange SSL session keys. The session keys are based on the client and server
certificates. The FortiGate SSL decrypt/encrypt process intercepts these keys and uses a
built-in signing CA certificate named Fortinet_CA_SSLProxy to create keys to send to the
client and the server. This signing CA certificate is used only by the SSL decrypt/encrypt
process. The SSL decrypt/encrypt process then sets up encrypted SSL sessions with the
client and server and uses these keys to decrypt the SSL traffic to apply content scanning
and inspection.
Some client programs (for example, web browsers) can detect this key replacement and
will display a security warning message. The traffic is still encrypted and secure, but the
security warning indicates that a key substitution has occurred.
You can stop these security warnings by importing the signing CA certificate used by the
server into the FortiGate unit SSL content scanning and inspection configuration. Then the
FortiGate unit creates keys that appear to come from the server and not the FortiGate unit.
Note: You can add one signing CA certificate for SSL content scanning and inspection. The
CA certificate key size must be 1024 or 2048 bits. 4096-bit keys are not supported for SSL
content scanning and encryption.
You can replace the default signing CA certificate, Fortinet_CA_SSLProxy, with another
signing CA certificate. To do this you need the signing CA certificate file, the CA certificate
key file, and the CA certificate password.
All SSL content scanning and inspection uses the same signing CA certificate. If your
FortiGate unit is operating with virtual domains enabled, the same signing CA certificate is
used by all virtual domains.
Figure 272: Importing a signing CA certificate for SSL content scanning and inspection
7 Select OK.
The CA certificate is added to the Local Certificates list. In this example the signing CA
certificate name is Example_CA. This name comes from the certificate file and key file
name. If you want the certificate to have a different name, change these file names.
8 Add the imported signing CA certificate to the SSL content scanning and inspection
configuration. Use the following CLI command if the certificate name is Example_CA.
Predefined firewall The IMAPS, POP3S and SMTPS predefined services. You can select
services these services in a firewall policy and a DoS policy. For more information,
see Table 50, “Predefined services,” on page 402.
Protocol Recognition The TCP port numbers that the FortiGate unit inspects for HTTPS, IMAPS,
POP3S, and SMTPS. Go to Firewall > Protection Profile. Add or edit a
protection profile and configure Protocol Recognition for HTTPS, IMAPS,
POP3S, and SMTPS.
Using protocol recognition you can also configure the FortiGate unit to just
perform URL filtering of HTTPS or to use SSL content scanning and
inspection to decrypt HTTPS so that the FortiGate unit can also apply
Antivirus and DLP content inspection and DLP archiving to HTTPS. Using
SSL content scanning and inspection to decrypt HTTPS also allows you to
apply more web filtering and FortiGuard Web Filtering options to HTTPS.
For more information, see “Protocol recognition options” on page 475.
Antivirus Antivirus options including virus scanning, file filtering, and client
comforting for HTTPS, IMAPS, POP3S, and SMTPS.
Go to Firewall > Protection Profile. Add or edit a protection profile and
configure Anti-Virus for HTTPS, IMAPS, POP3S, and SMTPS. For more
information, see “Anti-Virus options” on page 477.
Antivirus quarantine Antivirus quarantine options to quarantine files in HTTPS, IMAPS, POP3S,
and SMTPS sessions.
Go to UTM > AntiVirus > Config. You can quarantine infected files,
suspicious files, and blocked files found in IMAPS, POP3S, and SMTPS
sessions. You can also quarantine infected files and suspicious files found
in HTTPS sessions. For more information, see “Configuring quarantine
options” on page 518.
Web Filtering Web filtering options for HTTPS:
• Web Content Filter
• Web Content Exempt
• Web URL Filter
• ActiveX Filter
• Cookie Filter
• Java Applet Filter
• Web Resume Download Block
• Block invalid URLs
• HTTP POST Action
Go to Firewall > Protection Profile. Add or edit a protection profile and
configure Web Filtering for HTTPS. For more information, see “Web
Filtering options” on page 480.
Displaying DLP meta- DLP archive information on the Log and Archive Statistics widget on the
information on the system dashboard for HTTPS, IMAPS, POP3S, and SMTPS.
system dashboard Go to Firewall > Protection Profile. Add or edit a protection profile and
open Data Leak Prevention Sensor. For Displaying content meta-
information on the system dashboard select HTTPS, IMAPS, POP3S, and
SMTPS as required.
These options display meta-information on the Statistics dashboard
widget. For more information, see “Viewing DLP Archive information on
the Statistics widget” on page 91.
Archive SPAM email DLP archiving of email tagged as spam by FortiGate Email Filtering in
IMAPS, POP3S, and SMTPS sessions. Archive SPAMed emails to
FortiAnalyzer/FortiGuard is available only if you have configured logging to
a FortiAnalyzer unit or to the FortiGuard Analysis and Management
Service.
Go to Firewall > Protection Profile. Add or edit a protection profile and
select the Expand Arrow to view Data Leak Prevention Sensor. For
Archive SPAMed emails to FortiAnalyzer/FortiGuard, select IMAPS,
POP3S, and SMTPS as required. For more information, see “Data Leak
Prevention Sensor options” on page 488 and “DLP archiving” on
page 580.
Expand Arrow
Expand Arrow
Figure 274: Protection profile Protocol Recognition options (SSL content scanning and
inspection)
Add or
Remove
Port
Numbers
Edit Monitored
Ports
Add or
Remove
Port
Numbers
Edit Monitored
Ports
Note: If your FortiGate unit supports SSL content scanning and inspection, you must set
HTTPS Content Filtering Mode to Deep Scan before you can configure additional HTTPS
content scanning protection profile options.
HTTPS Content Filtering Mode If your FortiGate unit supports SSL content scanning and
inspection, you can select the content filtering mode used for
HTTPS traffic. The mode can be:
URL Filtering This option limits HTTPS content filtering to URL filtering only. If
you select this option the FortiGate unit does not perform SSL
content scanning and inspection of HTTPS traffic. Instead the
FortiGate unit just applies web filtering to HTTPS URLs. Also, if
you select URL Filtering, you cannot select any Anti-Virus options
for HTTPS. Under Web Filtering you can select only Web URL
Filter and Block invalid URLs for HTTPS. Selecting URL Filtering
also limits the FortiGuard Web Filtering options that you can
select for HTTPS.
Deep Scan (Decryption on Select this option to apply full SSL content scanning and
SSL Traffic) inspection of HTTPS traffic.
Protocol The names of the content protocols that you can configure
recognition for: HTTP, HTTPS, SMTP, POP3, IMAP, NNTP, and
FTP.
If your FortiGate unit supports SSL content scanning and
inspection the content protocols also include SMTPS, POP3S,
and IMAPS.
Monitored Ports The port numbers that the protection profile monitors for each
content protocol. You can select multiple port numbers to monitor
for each content protocol. For HTTP, SMTP, POP3, IMAP, NNTP,
and FTP you can also select Inspect All Ports to monitor all ports
for these content protocols. Monitoring all ports means the
protection profile uses protocol recognition techniques to
determine the protocol of a communication session independent
of the port number that the session uses.
Edit icon Select Edit for a content protocol to configure how the protection
profile monitors traffic for that content protocol. Select one of the
following options:
Inspect All Ports Select to monitor all ports for the content protocol. This option is
available for HTTP, SMTP, POP3, IMAP, NNTP, and FTP.
Specify Ports Select this option and then enter the port numbers to monitor for
the content protocol. You can specify up to 20 ports for each
content protocol.
Anti-Virus options
You can apply antivirus options through a protection profile for the HTTP, SMTP, POP3,
IMAP, NNTP, and content protocols.
If your FortiGate unit includes SSL content inspection and filtering, you can also apply
antivirus scanning options through a protection profile for HTTPS, IMAPS, POP3S, and
SMTPS content protocols. For more information, see “SSL content scanning and
inspection” on page 469.
Note: You cannot select Anti-Virus options for HTTPS if under protocol recognition HTTPS
Content Filtering Mode is set to URL Filtering. For more information, see “Protocol
recognition options” on page 475.
To configure antivirus options, go to Firewall > Protection Profile. Select Create New to
add a protection profile, or the Edit icon beside an existing protection profile. Then select
the Expand Arrow beside Anti-Virus, enter the information as described below, and select
OK. For more antivirus configuration options, see “AntiVirus” on page 509.
Figure 276: Protection Profile Anti-Virus options (including SSL content scanning and
inspection)
Virus Scan Select virus scanning for each protocol. Virus Scan includes grayware,
as well as heuristic scanning. However, by default neither is enabled.
To enable specific grayware, go to UTM > AntiVirus > Grayware. To
enable heuristic scanning, see the config antivirus heuristic
command in the FortiGate CLI Reference.
Note: When you enable virus scanning, scanning by splice, also
called streaming mode, is enabled automatically. When scanning by
splice, the FortiGate unit simultaneously scans and streams traffic to
the destination, terminating the stream to the destination if a virus is
detected. For details on configuring splicing, see the splice option
for each protocol in the config firewall profile command in
the FortiGate CLI Reference. For details on splicing behavior for each
protocol, see the Knowledge Center article FortiGate Proxy Splice and
Client Comforting Technical Note.
File Filter Select to filter files, then under Option, specify a file filter, which can
consist of file name patterns and file types. For more information, see
“File Filter” on page 513.
Quarantine Select for each protocol to quarantine suspect files for later inspection
or submission to Fortinet for analysis.
This option appears only if the FortiGate unit has a hard drive or a
configured FortiAnalyzer unit, and will take effect only if you have first
enabled and configured the quarantine. For more information, see
“File Quarantine” on page 516.
Pass Fragmented Emails Select to allow fragmented email for mail protocols (IMAP, POP3, and
SMTP as well as IMAPS, POP3S, and SMTPS if SSL content
scanning and inspection is supported). Fragmented email messages
cannot be scanned for viruses.
Comfort Clients Select client comforting for the HTTP, FTP, and HTTPS protocols. See
“HTTP and FTP client comforting” on page 479.
Interval The time in seconds before client comforting starts sending data after
the download has begun, and also the time interval between sending
subsequent data.
Amount The number of bytes sent at each interval.
Oversized File/Email Select Block or Pass for files and email messages exceeding
configured thresholds for each protocol.
For email scanning, the oversize threshold refers to the final size of
the email, including attachments, after encoding by the email client.
Email clients can use a variety of encoding types; some result in larger
file sizes than the original attachment. The most common encoding,
base64, translates 3 bytes of binary data into 4 bytes of base64 data.
As a result, a file may be blocked or logged as oversized even if the
attachment is several megabytes smaller than the configured oversize
threshold.
Threshold If the file is larger than the threshold value in megabytes, the file is
passed or blocked. The maximum threshold for scanning in memory is
10% of the FortiGate unit’s RAM.
Allow Invalid Server If your FortiGate unit supports SSL content scanning and inspection,
Certificate you can allow HTTPS, IMAPS, POP3S, and SMTPS sessions that
include an invalid server certificate. If these options are not selected,
HTTPS, IMAPS, POP3S, and SMTPS with invalid server certificates
are blocked. Use this feature to validate server certificates.
Quarantine Virus Sender Select Enabled to quarantine or ban either the IP address of the
(to Banned Users List) sender of the virus or the FortiGate interface that received the virus.
The sender’s IP address or the interface that received the virus is
added to the banned users list. For more information about the
banned user list including how to manage the duration of items and
how to remove them manually, see “NAC quarantine and the Banned
User list” on page 670.
Method If a virus is found, select the method used to quarantine the virus
sender. You can select Source IP Address to add the sender’s source
IP address to the banned users list, or you can select Virus’s Incoming
Interface to add the interface that received the virus to the banned
user list.
Expires Select Indefinite to permanently quarantine virus senders. Only a
FortiGate administrator can remove them from the banned users list.
Or, configure how long the virus sender remains on the banned user
list in minutes, hours, or days. A FortiGate administrator can manually
remove a virus sender from the banned user list before the expiry
time.
Add signature to outgoing Create and enable a signature to append to outgoing SMTP email
emails messages. The signature will also be appended to outgoing SMTPS
email messages if your FortiGate unit supports SSL content scanning
and inspection.
Caution: Client comforting can send unscanned and therefore potentially infected content
to the client. You should only enable client comforting if you are prepared to accept this risk.
Keeping the client comforting interval high and the amount low will reduce the amount of
potentially infected data that is downloaded.
IPS options
You can use the IPS options in a protection profile to enable IPS for the protection profile
and add an IPS sensor. To add an IPS sensor, go to Firewall > Protection Profile. Select
Create New to add a protection profile, or the Edit icon beside an existing protection
profile. Then select the Expand Arrow beside IPS, select the check box to enable IPS,
select an IPS Sensor, and select OK.
For more information on IPS, see “Intrusion Protection” on page 523.
Note: Protection profile web filtering also includes FortiGuard Web Filtering. For
information about FortiGuard Web Filtering, see “FortiGuard Web Filtering options” on
page 483.
You can configure web filtering for HTTP and HTTPS traffic. If your FortiGate unit supports
SSL content scanning and inspection and if you have set HTTPS Content Filtering Mode
in the Protocol Recognition part of this protection profile to Deep Scan, you can select the
same web filtering options for HTTPS and HTTP. For more information, see “SSL content
scanning and inspection” on page 469 and “Protocol recognition options” on page 475.
Filters defined in the web filtering settings are turned on through a protection profile. To
configure web filtering options, go to Firewall > Protection Profile. Select Create New to
add a protection profile, or the Edit icon beside an existing protection profile. Then select
the Expand Arrow beside Web Filtering, enter the information as described below, and
select OK.
Note: If your FortiGate unit does not support SSL content scanning and inspection, or if you
have set HTTPS Content Filtering Mode to URL Filtering, you can only select URL filtering
and blocking invalid URLs for HTTPS.
Web Content Filter Select to filter HTTP and HTTPS web pages based on matching the
content of the web page with the words or patterns in the selected web
content filter list. For more information, see “Web content filter” on
page 544.
Web content filter list Select the web content filter list to add to the protection profile. For
more information, see “Creating a new web content filter list” on
page 545.
Threshold Enter a web content filter threshold.
Each entry in the web content filter list added to the protection profile
incudes a score. When a web page is matched with an entry in the
content block list the score is recorded. If a web page matches more
than one entry the score for the web page increases. When the total
score for a web page equals or exceeds the threshold the page is
blocked.
The default score for content block list entry is 10 and the default
threshold is 10. This means that by default a web page is blocked by a
single match. You can change the scores and threshold so that web
pages can only be blocked if there are multiple matches.
Web URL Filter Select to block HTTP and HTTPS web pages based on matching the
URL of the web page with a URL in the selected URL filter list. For
more information, see “URL filter” on page 547.
Web URL filter list Select the URL filter list to add to this protection profile. For more
information, see “Creating a new URL filter list” on page 548.
Web Resume Download Select to block downloading parts of a file that have already been
Block downloaded. Enabling this option will prevent the unintentional
download of virus files hidden in fragmented files. Note that some
types of files, such as PDFs, are fragmented to increase download
speed, and that selecting this option can cause download interruptions
with these types.
Block invalid URLs Select to block web sites whose SSL certificate’s CN field does not
contain a valid domain name.
FortiGate units always validate the CN field, regardless of whether this
option is enabled. However, if this option is not selected, the following
behavior occurs:
• If the request is made directly to the web server, rather than a web
server proxy, the FortiGate unit queries for FortiGuard Web
Filtering category or class ratings using the IP address only, not
the domain name.
• If the request is to a web server proxy, the real IP address of the
web server is not known. Therefore, rating queries by either or
both the IP address and the domain name is not reliable. In this
case, the FortiGate unit does not perform FortiGuard Web
Filtering.
HTTP POST Action Select the action to take with HTTP POST traffic.
Normal Do not affect HTTP POST traffic.
Block Block HTTP POST requests. When the post request is blocked the
FortiGate unit sends a web page to the user’s web browser instead of
the requested POST page. You can configure the content of this web
page by going to from System > Config > Replacement Message by
customizing the HTTP > POST message.
Comfort Use the comfort amount and interval settings to send “comfort” bytes
to the server in case the client connection is too slow. Select this
option to prevent a server timeout when scanning or other filtering tool
is turned on.
Safe Search Enforce the strictest level the safe search feature of the Google,
Yahoo!, and Bing search engines. This feature works by manipulating
search URL requests to add code used by the safe search features of
the search engines.
Enforcing safe searching provides additional protection in
environments such as schools or other environments that use web
filtering to block sites with inappropriate content. Web Filtering alone
may not block offensive content that appears search results. This
offensive content could include offensive text in search results or
offensive images in image search results.
Google Enforce the strict filtering level of safe search protection for Google
searches by adding &safe=on to search URL requests. Strict filtering
filters both explicit text and explicit images.
Yahoo! Enforce filtering out adult web, video, and image search results from
Yahoo! searches by adding &vm=r to search URL requests.
Bing Enforce the strict level of safe search protection for Bing searches by
adding adlt=strict to search URL requests.
Blocked pages are replaced with a message indicating that the page is not accessible
according to the Internet usage policy. To configure replacement messages, go to
System > Config > Replacement Messages.
For more information on web filter configuration options, see “Web Filter” on page 541.
For details on how web URL filter lists are used with HTTP and HTTPS URLs, see “URL
formats” on page 550.
Character sets and Web content filtering, Email filtering banned word,
and DLP scanning
The FortiGate unit converts HTTP, HTTPS, and email content to the UTF-8 character set
before applying email filtering banned word checking, web filtering and DLP content
scanning as specified in the protection profile.
For email messages, while parsing the MIME content, the FortiGate unit converts the
content to UTF-8 encoding according to the email message charset field before applying
Email filtering banned word checking and DLP scanning.
For HTTP get pages, the FortiGate unit converts the content to UTF-8 encoding according
to the character set specified for the page before applying web content filtering and DLP
scanning.
For HTTP post pages, because character sets are not always accurately indicated in
HTTP posts, you can use the following CLI command to specify up to five character set
encodings.
config firewall profile
edit <profile_name>
set http-post-lang <charset1> [<charset2> ... <charset5>]
end
The FortiGate unit performs a forced conversion of HTTP post pages to UTF-8 for each
specified character set. After each conversion the FortiGate unit applies web content
filtering and DLP scanning to the content of the converted page.
Caution: Specifying multiple character sets reduces web filtering and DLP performance.
To view the list of available character sets, enter set http-post-lang ? from within
the edit shell for the protection profile. Separate multiple character set names with a
space. You can add up to 5 character set names.
Enable FortiGuard Web Select to enable FortiGuard Web Filtering for this protection profile.
Filtering
Enable FortiGuard Web Select to enable category overrides. For more information, see
Filtering Overrides “FortiGuard Web filtering overrides” on page 552 and “Configuring
administrative override rules” on page 553.
Provide details for Display a replacement message for 400 and 500-series HTTP errors. If
blocked HTTP 4xx and the error is allowed through, malicious or objectionable sites can use
5xx errors these common error pages to circumvent web filtering. Only supported
for HTTPS if your FortiGate unit supports SSL content scanning and
inspection.
Rate images by URL Block images that have been rated by FortiGuard. Blocked images are
(blocked images will be replaced on the originating web pages with blanks. Rated image file
replaced with blanks) types include GIF, JPEG, PNG, BMP, and TIFF. Only supported for
HTTPS if your FortiGate unit supports SSL content scanning and
inspection.
Allow websites when a Allow web pages that return a rating error from the web filtering service.
rating error occurs
Strict Blocking This option is enabled by default. Strict Blocking only has an effect when
either a URL fits into a protection profile category and classification or
Rate URLs by domain and IP address is enabled. With Rate URLs by
domain and IP address enabled, all URLs have two categories and up to
two classifications (one set for the domain and one set for the IP
address). All URLs belong to at least one category (including the Unrated
category) and may also belong to a classification.
If you enable Strict Blocking, a site is blocked if it is in at least one
blocked category or classification and only allowed if all categories or
classifications it falls under are allowed.
If you do not enable Strict Blocking, a site is allowed if it belongs to at
least one allowed category or classification and only blocked if all
categories or classifications it falls under are allowed.
For example, suppose that a protection profile blocks Search Engines
but allows “Image Search”, and that the URL “images.example.com” falls
into the General Interest / Search Engines category and the Image
Search classification.
With Strict Blocking enabled, this URL is blocked because it belongs to
the Search Engines category, which is blocked.
With Strict Blocking disabled, the URL is allowed because it is classified
as Image Search, which the profile allows. It would be blocked only if
both the Search Engines category and Image Search classification were
blocked.
Rate URLs by domain Select to send both the URL and the IP address of the requested site for
and IP address checking, and thus provide additional security against attempts to bypass
the FortiGuard system.
However, because IP rating is not updated as quickly as URL rating,
some false ratings may occur.
Block HTTP redirects Enable to block HTTP redirects.
by rating Many web sites use HTTP redirects legitimately; however, in some
cases, redirects may be designed specifically to circumvent web filtering,
as the initial web page could have a different rating than the destination
web page of the redirect. Not supported for HTTPS.
Category FortiGuard Web Filtering provides many content categories for filtering
web traffic. Categories reflect the subject matter of the content.
For each category, select to Allow or Block and, if the category is
blocked, whether or not to Allow Override to permit users to override the
filter if they successfully authenticate. You can also select to log each
traffic occurrence of the category.
Classification In addition to content categories, FortiGuard Web Filtering provides
functional classifications that block whole classes of web sites based
upon their functionality, media type, or source, rather than the web site’s
subject matter.
Using classifications, you can block web sites that host cached content or
that facilitate image, audio, or video searches, or web sites from spam
URLs. Classification is in addition to, and can be configured separately
from, the category.
For each class, select to Allow or Block and, if the class is blocked,
whether or not to Allow Override to permit users to override the filter if
they successfully authenticate. You can also select to log each traffic
occurrence of the class.
session. If FortiGuard Antispam does not find a match, the email server sends the email to
the recipient. The email checksum filter calculates the checksum of an email message and
sends this checksum to the FortiGuard servers to determine if the checksum is in the
blacklist. The FortiGate unit then passes or marks/blocks the email message according to
the server response.
To configure email filtering options, go to Firewall > Protection Profile. Select Create New
to add a protection profile, or the Edit icon beside an existing protection profile. Then
select the Expand Arrow beside Email Filtering, enter the information as described below,
and select OK.
You can configure email filtering for IMAP, POP3, and SMTP email. If your FortiGate unit
supports SSL content scanning and inspection you can also configure email filtering for
IMAPS, POP3S, and SMTPS email. For information about SSL content scanning and
inspection, see “SSL content scanning and inspection” on page 469.
For more information about the FortiGuard Antispam service, see “FortiGuard Antispam
service” on page 301 and “Configuring the FortiGate unit for FDN and FortiGuard
subscription services” on page 302.
For more email filter configuration options, see “Email filtering” on page 559.
For information about character sets and email filter banned word, see “Character sets
and Web content filtering, Email filtering banned word, and DLP scanning” on page 483.
Note: Some popular email clients cannot filter messages based on the MIME header. For
these clients, select to tag email message subject lines instead.
FortiGuard Email Filtering Also called FortiGuard Antispam. Select one or more check boxes to
enable protocols (IMAP, POP3, SMTP), then apply the options that
you need. If your FortiGate unit supports SSL content scanning and
inspection you can also enable FortiGuard Antispam for IMAPS,
POP3S, and SMTPS.
IP address check Select to enable the FortiGuard AntiSpam IP address blacklist.
URL check Select to enable the FortiGuard AntiSpam URL blacklist.
E-mail checksum check Select to enable the FortiGuard Antispam email message checksum
blacklist.
Spam submission Select to add a spam submission message and a link to the
message body of all email messages marked as spam by
FortiGuard Antispam. If the receiver considers that the email
message is not spam, he or she can use the link in the message to
inform FortiGuard Antispam. You can change the content of this
message by going to System > Config > Replacement Message and
customizing the Spam > Spam submission message. For more
information, see “Spam replacement messages” on page 231.
IP address BWL check Select to compare the IP address of email message senders to the
selected IP address black/white list and, if a match is found, to take
the action configured in the list for the IP address. For more
information, see “IP address and email address black/white lists” on
page 565.
IP address BWL check Select the IP address black/white list to add to the protection profile.
list For more information, see “Creating a new IP address list” on
page 566.
HELO DNS lookup Select to look up the source domain name (from the SMTP HELO
command) for SMTP email messages.
E-mail address BWL check Select to compare the email address of message senders to the
selected email address black/white list and if a match is found to
take the action configured in the list for the email address. For more
information, see “IP address and email address black/white lists” on
page 565.
E-mail address BWL list Select the email address black/white list to add to the protection
profile. For more information, see “Creating a new email address list”
on page 568.
Return e-mail DNS check Select to enable checking that the domain specified in the reply-to or
from address has an A or MX record.
Banned word check Select to block email messages based on matching the content of
the message with the words or patterns in the selected email filter
banned word list. For more information, see “Banned word” on
page 562.
Banned word list Select the banned word list to add to the protection profile. For more
information, see “Creating a new banned word list” on page 563.
Threshold Enter a email filter banned word block threshold.
Each entry in the banned word list added to the protection profile
incudes a score. When an email message is matched with an entry
in the banned word list, the score is recorded. If an email message
matches more than one entry, the score for the email message
increases. When the total score for an email message equals or
exceeds the threshold, the message is tagged as spam.
The default score for a banned word list entry is 10 and the default
threshold is 10. This means that by default an email message is
tagged as spam by a single match. You can change the scores and
threshold so email messages are only tagged as spam if there are
multiple matches.
Spam Action Select to either tag or discard email that the FortiGate unit
determines to be spam. Tagging adds the text in the Tag Format
field to the subject line or header of email identified as spam.
Note: When you enable virus scanning for SMTP and SMTPS in the
Anti-virus section of the protection profile, scanning by splice, also
called streaming mode, is enabled automatically. When scanning by
splice, the FortiGate unit simultaneously scans and streams traffic to
the destination, terminating the stream to the destination if a virus is
detected. For details on configuring splicing, see the splice option
for each protocol in the config firewall profile command in
the FortiGate CLI Reference. For details on splicing behavior for
SMTP, see the Knowledge Center article FortiGate Proxy Splice and
Client Comforting Technical Note.
When virus scanning is enabled for SMTP the FortiGate unit can
only discard spam email if a virus is detected. Discarding
immediately drops the connection. If virus scanning is not enabled,
you can choose to either tag or discard SMTP spam.
Tag Location Select to add the tag to the subject or MIME header of email
identified as spam.
If you select to add the tag to the subject line, the FortiGate unit
converts the entire subject line, including the tag, to UTF-8 format.
This improves display for some email clients that cannot properly
display subject lines that use more than one encoding. For details on
preventing conversion of subject line to UTF-8, see the “System
Settings” chapter of the FortiGate CLI Reference.
To add the tag to the MIME header, you must enable
spamhdrcheck in the CLI for each protocol (IMAP, SMTP, and
POP3). For more information see “profile” in the FortiGate CLI
Reference.
Tag Format Enter a word or phrase with which to tag email identified as spam.
When typing a tag, use the same language as the FortiGate unit’s
current administrator language setting. Tag text using other
encodings may not be accepted. For example, when entering a
spam tag that uses Japanese characters, first verify that the
administrator language setting is Japanese; the FortiGate unit will
not accept a spam tag written in Japanese characters while the
administrator language setting is English. For details on changing
the language setting, see “Settings” on page 261.
Tags must not exceed 64 bytes. The number of characters
constituting 64 bytes of data varies by text encoding, which may vary
by the FortiGate administrator language setting.
Figure 282: Data Leak Prevention Sensor options (SSL content scanning inspection and
FortiAnalyzer unit configured)
Data Leak Select the check box and then specify the DLP sensor to add to the protection
Prevention profile. For more information, see “Adding and configuring a DLP sensor” on
Sensor page 577.
Display DLP For each protocol, select whether or not to display DLP archiving data in the
meta- dashboard Log and Archive Statistics widget. You can select HTTP, HTTPS, FTP,
information on IMAP, POP3, and SMTP.
the system If your FortiGate unit supports SSL content scanning and inspection you can also
select IMAPS, POP3S, and SMTPS.
dashboard
For more information about the Log and Archive Statistics widget, see “Log and
Archive Statistics” on page 77.
Archive For each email protocol, select to archive email messages identified as spam by
SPAMed emails FortiGate Email filtering or by FortiGuard Antispam. You must configure the
to FortiGate unit to log to a FortiAnalyzer unit or enable the FortiGuard Analysis and
Management Service. For more information, see “Configuring spam email
FortiAnalyzer/ message archiving” on page 585.
FortiGuard
Application Select the check box and then specify the application control black/white list
Black/White List to add to the protection profile. For more information, see “Creating a new
application control black/white list” on page 597.
Logging options
You can enable logging options in a protection profile to write log messages when the
options that you have enabled in this protection profile perform an action. For example, if
you enable antivirus protection you could also enable the antivirus protection profile
logging options to write a an antivirus log message every time a virus is detected by this
protection profile.
To record these log messages you must first configure how the FortiGate unit stores log
messages. See “Configuring how a FortiGate unit stores logs” on page 704.
For information about viewing log messages, see “Accessing and viewing log messages”
on page 714.
You can also view and customize reports based on these log messages. See “Viewing
Executive Summary reports from SQL logs” on page 724 and “Viewing FortiAnalyzer
reports” on page 724.
To configure Logging options, go to Firewall > Protection Profile. Select Create New to
add a protection profile, or the Edit icon beside an existing protection profile. Then select
the Expand Arrow beside Logging, select logging options, and select OK.
Antivirus If antivirus settings are enabled for this protection profile, select the
following options to record Antivirus Log messages.
Viruses Record a log message when this protection profile detects a virus.
Blocked Files Record a log message when antivirus file filtering enabled in this
protection profile blocks a file.
Oversized Files / Record a log message when this protection profile encounters and
E-mails oversized file or email. Oversized files and emails cannot be scanned
for viruses.
Web Filtering If Web Filtering settings are enabled for this protection profile, select the
following options to record Web Filter Log messages.
Content Block Record a log message when this protection profile matches the content
of a web page with the web content filter added to this protection profile.
The log message records whether the web page was blocked or
exempted.
URL Filter Record a log message when this protection profile matches the URL of
a web page with the web URL filter added to this protection profile. The
log message records whether the web page was blocked, exempted, or
allowed.
Invalid Domain Name Record a log message when this protection profile detects an invalid
Warnings domain name. A domain name is considered invalid if the name fails a
reverse DNS lookup.
FortiGuard Web Filtering If FortiGuard Web Filtering settings are enabled for this protection
profile, select the following option to record Web Filter Log messages.
Rating Errors (HTTP Record a log message when FortiGuard Web Filtering configured in this
only) protection profile encounters a rating error.
Email Filtering If Email Filtering settings are enabled for this protection profile, select
the following option to record Email Filter Log messages.
Log Spam Record a log message when the email filtering configured in this profile
determines that an email message is spam.
IPS If Intrusion Protection is enabled for this protection profile, select the
following option to record Attack Log messages.
Log Intrusions Record a log message when this protection profile encounters a session
that the IPS Sensor added to this protection profile determines is an
attack or intrusion. The log message records the IPS signature that
detected the attack or intrusion.
Application Control If Application Control is enabled for this protection profile, select the
following option to record Application Control Log messages.
Log Application Record a log message when the Application Control list added to this
Control protection profile detects an application. The log message records the
application detected and the action taken by application control.
Data Leak Prevention If Data Leak Prevention is enabled for this protection profile, select the
Sensor following option to record DLP Log messages.
Log DLP Record a log message when the data leak prevention sensor added to
this protection profile matches the content of a session.
SIP support
The Session Initiation Protocol (SIP) is a signaling protocol used for establishing and
conducting multiuser calls over TCP/IP networks using any media. Due to the complexity
of the call setup, not every firewall can handle SIP calls correctly, even if the firewall is
stateful. The FortiGate unit has a pre-defined SIP firewall service that tracks and scans
SIP calls and makes adjustments, to both the firewall state and call data, to ensure a
seamless call is established through the FortiGate unit regardless of its operation mode,
NAT, route, or transparent. FortiGate units support SIP RFC 3261.
You can use protection profiles to control the SIP protocol and SIP call activity.
A statistical summary of SIP protocol activity is also available for managing SIP use.
This section includes some information about VoIP and SIP. It also describes how FortiOS
SIP support works and how to configure the key SIP features. For more configuration
information, see the FortiGate CLI Reference.
The FortiGate unit supports the following SIP features:
• stateful SIP tracking
• RTP Pinholing
• request control
• rate limiting
• event logging
• communication archiving
• NAT IP preservation
• client connection control
• register response acceptance
• Application Level Gateway (ALG) control
• SIP stateful HA
• IPv6 support
This section describes:
• VoIP and SIP
• The FortiGate unit and VoIP security
• How SIP support works
• Configuring SIP
In proxy mode (shown in Figure 285), SIP clients send requests to the proxy server. The
proxy server either handles the requests or forwards them to other SIP servers. Proxy
servers can insulate and hide SIP users by proxying the signaling messages. To the other
users on the VoIP network, the signaling invitations look as if they come from the SIP
proxy server.
IP Network 4. Client B is
notified of incoming
RTP Session
call by proxy server
– phone rings
When the SIP server operates in redirect mode (shown in Figure 286), the SIP client
sends its signaling request to a SIP server, which then looks up the destination address.
The SIP server returns the destination address to the originator of the call, who uses it to
signal the destination SIP client.
IP Network 5. Client B is
notified of incoming
RTP Session call by redirect server
– phone rings
SIP NAT
The FortiGate unit supports network address translation (NAT) of SIP because the
FortiGate ALG can modify the SIP headers correctly.
This section uses scenarios to explain the FortiGate SIP NAT support.
217.233.122.132
Internet
10.72.0.57
10.72.0.60 217.233.122.132
Internet
10.72.0.57
In the scenario, shown in Figure 288, the SIP phone connects to a VIP (10.72.0.60). The
FortiGate SIP ALG translates the SIP contact header to 217.10.79.9. The FortiGate ALG
will open the Real-time Transport Protocol (RTP) pinholes and manage NAT.
The FortiGate unit also supports a variation of this scenario—the RTP server hides its real
address.
RTP Server
10.0.0.60
217.233.90.60
Internet
SIP Server
In this scenario, shown in Figure 289, a SIP phone connects to the Internet. The VoIP
service provider only publishes a single public IP (a VIP). The SIP phone connects to the
FortiGate unit (217.233.90.60) and the FortiGate unit then translates the SIP contact
header to the SIP server (10.0.0.60). The SIP server changes the SIP/SDP connection
information (which tells the SIP phone which RTP IP it should contact) also to
217.233.90.60.
Figure 290: Different source and destination NAT for SIP and RTP
RTP Servers
192.168.0.21 - 192.168.0.23 219.29.81.10 219.29.81.20
RTP Server
10.0.0.60
RTP-1: 217.233.90.65
RTP-2: 217.233.90.70
Internet
SIP: 217.233.90.60
SIP Server
In this scenario, shown in Figure 290, assume there is a SIP server and a separate media
gateway. The SIP server is configured so that the SIP phone (219.29.81.20) will connect
to 217.233.90.60. The media gateway (RTP server: 219.29.81.10) will connect to
217.233.90.65.
What happens is as follows:
1 The SIP phone connects to the SIP VIP. The FortiGate ALG translates the SIP contact
header to the SIP server: 219.29.81.20 > 217.233.90.60 (> 10.0.0.60).
2 The SIP server carries out RTP to 217.233.90.65.
3 The FortiGate ALG opens pinholes, assuming that it knows the ports to be opened.
4 RTP is sent to the RTP-VIP (217.233.90.65.) The FortiGate ALG translates the SIP
contact header to 192.168.0.21.
You need to configure the FortiOS SIP support in the following order:
1 Create a firewall protection profile that enables SIP (see “Enabling SIP support and
setting rate limiting from the web-based manager” on page 498).
Once the profile is included in a policy, the ALG will parse the SIP traffic and open the
RTP ports for each specific VoIP call.
When creating a protection profile, you configure SIP features using the web-based
manager and CLI. You then apply the profile to a firewall policy. You can apply a profile
to multiple policies.
2 Create a firewall policy that allows SIP and includes a SIP-enabled protection profile.
Specifically, select the SIP or ANY pre-defined service for the policy.
When the FortiGate unit receives a SIP packet, it checks the packet against the firewall
policies. If the packet matches a policy, the FortiGate firewall inspects and processes
the packet according to the SIP profile applied to the policy.
For more information about firewall policies, see “Firewall Policy” on page 363.
3 Configure advanced SIP features as required (see “Configuring SIP” on page 498).
Configuring SIP
You can enable SIP support, set two rate limits, enable SIP logging, and view SIP
statistics using the web-based manager. You can do this plus configure many other SIP
support features from the CLI.
This section describes the following SIP configuration options:
• Enabling SIP support and setting rate limiting from the web-based manager
• Enabling SIP support from the CLI
• More about rate limiting
• Enabling SIP logging
• Enabling advanced SIP features in an application list
• Turning on SIP tracking
• Managing RTP pinholing
• Blocking SIP requests
• Archiving SIP communication
• Preserving NAT IP
• Controlling SIP client connections
• Accepting SIP register responses
• Controlling how SIP handles contact header NAT
• Opening and closing SIP register and non-register pinholes
• Blocking SIP requests
• Support for RFC 2543-compliant branch parameters
Enabling SIP support and setting rate limiting from the web-based manager
To enable SIP support you need to:
• enable SIP in an application control list
• select this application control list in a protection profile
• add this protection profile to a firewall policy that accepts SIP traffic.
From the web-based manager, you can also configure some SIP rate limiting settings.
Rate limiting for SIP also limits SIMPLE traffic. SIP rate limiting is useful for protecting a
SIP server within a company. Most SIP servers do not have integrated controls and it is
very easy to flood SIP servers with INVITE or REGISTER requests.
Enabling SIP in an application control list actually enables the SIP application level
gateway (SIP ALG) for sessions accepted by a firewall policy that includes the SIP
application.
Tip: The SIP and SCCP application control list entries are used only for enabling the SIP or
SCCP application level gateways (ALGs). They are not like any other application control list
entry. For example, you cannot use the SIP and SCCP application control list entries to
block SIP or SCCP traffic. From the CLI SIP is application number 12 and SCCP is
application number 13.
Tip: The SIP.TCP and SIP.UDP application control list entries are normal application
control list entries and are not involved with the SIP ALG. You can use the SIP.TCP or
SIP.UDP application control list entries to block SIP sessions.
To enable SIP and set REGISTER and INVITE rate limiting from the web-based
manager
1 Go to UTM > Application Control.
2 If you want to enable SIP for an existing application control list, select the Edit icon for
an application control list. Otherwise, select Create New to add a new application
control list.
3 Then, select Create New in the list to add a new application to the list.
4 Set Application to SIP.
You can optionally set Category to voip to make the SIP application easier to find.
5 Optionally configure REGISTER and INVITE limiting.
For example:
• Set Limit REGISTER request to 100.
• Set Limit INVITE request to 100.
6 Select OK.
7 Go to Firewall > Profile and add the application control list to a protection profile.
8 Go to Firewall > Policy and add the protection profile to a firewall policy that accepts
SIP sessions.
For more information about application control, see “Application Control” on page 595.
To enable SIP and set REGISTER and INVITE rate limiting from the CLI
1 Enter the following command to add an application control list called App_list_SIP,
enable SIP support in the list, and limit REGISTER and INVITE requests to 100
requests per second per firewall policy.
config application list
edit App_list_SIP
config entries
edit 1
set category voip
set application SIP
set register-rate 100
set invite-rate 100
end
end
2 Enter the following command to add the App_list_SIP to a protection profile called
SIP_Profile.
config firewall profile
edit SIP_Profile
set application-list-status enable
set application-list App_list_SIP
end
3 Enter the following command to add the SIP_Profile protection profile to a firewall
policy. The example uses generic firewall policy settings. The example also uses the
SIP service. You could also set service to ANY.
config firewall policy
edit 1
set srcintf port1
set dstintf port2
set srcaddr all
set dstaddr all
set action accept
set schedule always
set service SIP
set profile-status enable
set comments "Example SIP policy"
set profile SIP_Profile
end
Preserving NAT IP
In NAT operation mode, you can preserve the original source IP address in the SDP i line.
This allows the SIP server to parse this IP for billing purposes.
From the CLI, type the following commands:
config application list
edit <list_name>
config entries
edit 1
set category voip
set application SIP
set nat-trace enable
end
end
In addition, you can overwrite or append the SDP i line:
config application list
edit <list_name>
config entries
edit 1
set category voip
set application SIP
set preserve-override {enable | disable}
end
end
where selecting enable removes the original source IP address from the SDP i line and
disable appends the address.
Usually you would want to open these pinholes. Keeping the closed may prevent SIP from
functioning properly through the FortiGate unit.They can be disabled, however, for
interconnect scenarios (where all SIP traffic is between proxies and traveling over a single
session). In some cases these settings can also be disabled in access scenarios if it is
known that all users will be registering regularly so that their contact information can be
learned from the register request.
You might want to prevent pinholes from being opened to avoid creating a pinhole for
every register or non-register request. Each pinhole uses additional system memory,
which can affect system performance if there are hundreds or thousands of users, and
requires refreshing which can take a relatively long amount of time if there are thousands
of active calls.
To stop the FortiGate unit from opening register and non-register pinholes:
config application list
edit <list_name>
config entries
edit 1
set category voip
set application SIP
set open-register-pinhole disable
set open-contact-pinhole disable
end
end
AntiVirus
This section describes how to configure the antivirus options associated with firewall
protection profiles. From a protection profile you can configure the FortiGate unit to apply
antivirus protection to HTTP, FTP, IMAP, POP3, SMTP, IM, and NNTP sessions. If your
FortiGate unit supports SSL content scanning and inspection you can also configure
antivirus protection for HTTPS, IMAPS,POP3S, and SMTPS sessions. For more
information, see “SSL content scanning and inspection” on page 469.
This section provides an introduction to antivirus settings. For more information see the
FortiGate UTM User Guide.
If you enable virtual domains (VDOMs) on the FortiGate unit, UTM > Antivirus options are
configured separately for each virtual domain. For details, see “Using virtual domains” on
page 125.
This section describes:
• Order of operations
• Antivirus tasks
• Antivirus settings and controls
• File Filter
• File Quarantine
• Selecting the virus database
• Antivirus CLI configuration
Order of operations
Antivirus scanning function includes various modules and engines that perform separate
tasks. The FortiGate unit performs antivirus processing in the following order:
• File size
• File pattern
• File type
• Virus scan
• Grayware
• Heuristics
If a file fails any of the tasks of the antivirus scan, no further scans are performed. For
example, if the file “fakefile.EXE” is recognized as a blocked pattern, the FortiGate unit will
send the end user a replacement message and the file will be deleted or quarantined. The
virus scan, grayware, heuristics, and file type scans will not be performed as the file is
already been determined to be a threat and has been dealt with.
Note: File filter includes file pattern and file type scans which are applied at different stages
in the antivirus process.
File/email
Oversized
exceeds
file/email
Block Yes oversized
action
threshold
Pass
No
Matching File
Block Pattern
file pattern
file/email Match?
Block action Yes
Allow No
File/email
exceeds Pass
Pass oversized file/email
Yes
file/email threshold
No
No
Block
Yes
Allow
AV scan Matching
detects file type File type
infection? action match?
Yes
No
Antivirus tasks
The antivirus tasks work in sequence to efficiently scan incoming files and offer your
network unparalleled antivirus protection. The first four tasks have specific functions, the
fifth, the heuristics, is to cover any new, previously unknown, virus threats. To ensure that
your system is providing the most protection available, all virus definitions and signatures
are updated regularly through the FortiGuard antivirus services. The tasks will be
discussed in the order that they are applied followed by FortiGuard antivirus.
File size
This task checks if files and email messages exceed configured thresholds. It is enabled
by setting the Oversized File/Email option under Firewall > Protection Profile > Antivirus to
Pass.
For more information, see “Anti-Virus options” on page 477.
File pattern
Once a file is accepted, the FortiGate unit applies the file pattern recognition filter. The
FortiGate unit will check the file against the file pattern setting you have configured. If the
file is a blocked pattern, “.EXE” for example, then it is stopped and a replacement
message is sent to the end user. No other levels of protections are applied. If the file is not
a blocked pattern the next level of protection is applied.
File type
Once a file passes the heuristic scan, the FortiGate unit applies the file type recognition
filter. The FortiGate unit will check the file against the file type setting you have configured.
If the file is a blocked type, then it is stopped and a replacement message is sent to the
end user. No other levels of protections are applied. If the file is not a blocked type, the
next level of protection is applied.
Virus scan
If the file passes the file pattern scan, it will have a virus scan applied to it. The virus
definitions are keep up to date through the FortiNet Distribution Network. The list is
updated on a regular basis so you do not have to wait for a firmware upgrade. For more
information on updating virus definitions, see “FortiGuard antivirus” on page 511.
Grayware
Once past the virus scan, the incoming file will be checked for grayware. Grayware
checking can be turned on and off as required. Grayware signatures are kept up to date
because the are included in the antivirus definitions. For more information on see
“Selecting the virus database” on page 519.
Heuristics
After an incoming file has passed the grayware scan, it is subjected to the heuristics scan.
The FortiGate heuristic antivirus engine, if enabled, performs tests on the file to detect
virus-like behavior or known virus indicators. In this way, heuristic scanning may detect
new viruses, but may also produce some false positive results.
Note: Heuristics is configurable only through the CLI. See the FortiGate CLI Reference.
FortiGuard antivirus
FortiGuard antivirus services are an excellent resource and include automatic updates of
virus and IPS (attack) engines and definitions, as well as the local spam DNSBL, through
the FortiGuard Distribution Network (FDN). The FortiGuard Center also provides the
FortiGuard antivirus virus and attack encyclopedia and the FortiGuard Bulletin. Visit the
Fortinet Knowledge Center for details and a link to the FortiGuard Center.
The connection between the FortiGate unit and FortiGuard Center is configured in
System > Maintenance > FortiGuard. See “Configuring the FortiGate unit for FDN and
FortiGuard subscription services” on page 302 for more information.
Note: If virtual domains are enabled, you configure antivirus file filtering and antivirus
settings in protection profiles separately for each virtual domain. Antivirus file quarantine
and grayware settings are part of the global configuration.
File Filter
Configure the FortiGate file filter to block files by:
• File pattern: Files can be blocked by name, extension, or any other pattern. File pattern
blocking provides the flexibility to block potentially harmful content.
File pattern entries are not case sensitive. For example, adding *.exe to the file
pattern list also blocks any files ending in .EXE.
In addition to the built-in patterns, you can specify more file patterns to block. For
details, see “Configuring the file filter list” on page 516.
• File type: Files can be blocked by type, without relying on the file name to indicate what
type of files they are. When blocking by file type, the FortiGate unit analyzes the file
and determines the file type regardless of the file name. For details about supported
file types, see “Built-in patterns and supported file types” on page 513.
For standard operation, you can choose to disable file filter in the protection profile, and
enable it temporarily to block specific threats as they occur.
The FortiGate unit can take either of these actions toward files that match a configured file
pattern or type:
• Allow: the file is allowed to pass.
• Block: the file is blocked and a replacement messages will be sent to the user. If both
file filter and virus scan are enabled, the FortiGate unit blocks files that match the
enabled file filter and does not scan these files for viruses.
The FortiGate unit also writes a message to the virus log and sends an alert email
message if configured to do so.
Files are compared to the enabled file patterns and then the file types from top to bottom.
If a file does not match any specified patterns or types, it is passed along to antivirus
scanning (if enabled). In effect, files are passed if not explicitly blocked.
Using the allow action, this behavior can be reversed with all files being blocked unless
explicitly passed. Simply enter all the file patterns or types to be passed with the allow
attribute. At the end of the list, add an all-inclusive wildcard (*.*) with a block action.
Allowed files continue to antivirus scanning (if enabled) while files not matching any
allowed patterns are blocked by the wildcard at the end.
Note: The “unknown” type is any file type that is not listed in the table. The “ignored” type is
the traffic the FortiGate unit typically does not scan. This includes primarily streaming audio
and video.
Create New Select Create New to add a new file filter list to the catalog.
Name The available file filter lists.
# Entries The number of file patterns or file types in each file filter list.
Profiles The protection profiles each file filter list has been applied to.
DLP Rule The DLP rules in which each filter is used.
Comments An optional description of each file filter list.
Delete icon Select to remove the file filter list from the catalog. The delete icon is only
available if the file filter list is not selected in any protection profiles.
Edit icon Select to edit the file filter.
File filter lists are selected in protection profiles. For more information, see “Anti-Virus
options” on page 477.
The file filter list has the following icons and features:
Name File filter list name. To change the name, edit the text in the name field and
select OK.
Comment Optional comment. To add or edit comment, enter text in comment field and
select OK.
OK If you make changes to the list name or comments, select OK to save the
changes.
Create New Select Create New to add a new file pattern or type to the file filter list.
Filter The current list of file patterns and types.
Action Files matching the file patterns and types can be set to Block or Allow. For
information about actions, see “File Filter” on page 513.
Enable Clear the checkbox to disable the file pattern or type.
Delete icon Select to remove the file pattern or type from the list.
Edit icon Select to edit the file pattern/type and action.
Move To icon Select to move the file pattern or type to any position in the list.
To add a file pattern or type go to UTM > AntiVirus > File Filter. Select the Edit icon for a
file filter catalog. Select Create New.
File Quarantine
FortiGate units with a local disk can quarantine blocked and infected files. View the file
name and status information about the file in the Quarantined Files list. Submit specific
files and add file patterns to the AutoSubmit list so they will automatically be uploaded to
Fortinet for analysis.
FortiGate units can also quarantine blocked and infected files to a FortiAnalyzer unit. Files
stored on the FortiAnalyzer unit can also be viewed from the Quarantined Files list. To
configure quarantine to a FortiAnalyzer unit, go to Log & Report > Log Config > Log
Setting.
Create New Select to add a new file pattern to the AutoSubmit list.
File Pattern The current list of file patterns that will be automatically uploaded. Create a
pattern by using ? or * wildcard characters. Enable the check box to enable all
file patterns in the list.
Delete icon Select to remove the entry from the list.
Edit icon Select to edit the following information: File Pattern and Enable.
File Pattern Enter the file pattern or file name to be upload automatically to Fortinet.
Enable Select to enable the file pattern
Note: To enable automatic uploading of the configured file patterns, go to UTM >
AntiVirus > Quarantine, select Enable AutoSubmit, and select Use File Pattern.
Figure 300: Quarantine Configuration (SSL content scanning and inspection and quarantine
to disk)
Options Quarantine Infected Files: Select the protocols from which to quarantine infected
files identified by antivirus scanning.
Quarantine Suspicious Files: Select the protocols from which to quarantine
suspicious files identified by heuristic scanning.
Quarantine Blocked Files. Select the protocols from which to quarantine blocked
files identified by antivirus file filtering. The Quarantine Blocked Files option is not
available for IM and HTTPS because a file name is blocked before downloading
and cannot be quarantined.
Age Limit The time limit in hours for which to keep files in quarantine. The age limit is used
to formulate the value in the TTL column of the quarantined files list. When the
limit is reached, the TTL column displays EXP. and the file is deleted (although the
entry in the quarantined files list is maintained). Entering an age limit of 0 (zero)
means files are stored on disk indefinitely, depending on low disk space action.
Max Filesize to The maximum size of quarantined files in MB. Setting the maximum file size too
Quarantine large may affect performance.
Low Disk Space Select the action to take when the local disk is full: overwrite the oldest file or drop
the newest file.
Quarantine to Select to enable storage of blocked and quarantined files on a FortiAnalyzer unit.
FortiAnalyzer See “Log&Report” on page 703 for more information about configuring a
FortiAnalyzer unit.
Enable Enable AutoSubmit: enables the automatic submission feature. Select one or both
AutoSubmit of the options below.
Use File Pattern: Enables the automatic upload of files matching the file patterns
in the autoSubmit list.
Use File Status: Enables the automatic upload of quarantined files based on their
status. Select either Heuristics or Block Pattern.
Apply Select to save the configuration.
Usually the FortiGuard AV definitions are updated automatically from the FortiGuard
Distribution Network (FDN). Go to System > Maintenance > FortiGuard to configure
automatic antivirus definition updates from the FDN.
You can also update the antivirus definitions manually from the system dashboard (go to
System > Status).
The heuristic engine is disabled by default. You need to enable it to pass suspected files
to the recipient and send a copy to the file quarantine. Once enabled in the CLI, heuristic
scanning is enabled in a protection profile when Virus Scan is enabled.
Use the heuristic command to change the heuristic scanning mode.
Intrusion Protection
The FortiGate Intrusion Protection system combines signature and anomaly detection and
prevention with low latency and excellent reliability. With intrusion Protection, you can
create multiple IPS sensors, each containing a complete configuration based on
signatures. Then, you can apply any IPS sensor to each protection profile. You can also
create DoS sensors to examine traffic for anomaly-based attacks.
This section describes how to configure the FortiGate Intrusion Protection settings. For
more information about Intrusion Protection, see the FortiGate UTM User Guide.
If you enable virtual domains (VDOMs) on the FortiGate unit, intrusion protection is
configured separately for each virtual domain. For details, see “Using virtual domains” on
page 125.
This section describes:
• About intrusion protection
• Signatures
• Custom signatures
• Protocol decoders
• IPS sensors
• DoS sensors
• Intrusion protection CLI configuration
Using Intrusion Protection, you can configure the FortiGate unit to check for and
automatically download updated attack definition files containing the latest signatures, or
download the updated attack definition file manually. Alternately, you can configure the
FortiGate unit to allow push updates of the latest attack definition files as soon as they are
available from the FortiGuard Distribution Network.
You can also create custom attack signatures for the FortiGate unit to use in addition to an
extensive list of predefined attack signatures.
Whenever the Intrusion Protection system detects or prevents an attack, it generates an
attack log message. You can configure the FortiGate unit to add the message to the attack
log and send an alert email to administrators, as well as schedule how often it should send
this alert email. You can also reduce the number of log messages and alerts by disabling
signatures for attacks that will not affect your network. For example, you do not need to
enable signatures to detect web attacks when there is no web server to protect.
You can also use the packet logging feature to analyze packets for false positive
detection.
For more information about FortiGate logging and alert email, see “Log&Report” on
page 703.
Note: If virtual domains are enabled on the FortiGate unit, the Intrusion Protection settings
are configured separately in each VDOM. All sensors and custom signatures will appear
only in the VDOM in which they were created.
Signatures
The FortiGate Intrusion Protection system can use signatures once you have grouped the
required signatures in an IPS sensor, and then selected the IPS sensor in the protection
profile. If required, you can override the default settings of the signatures specified in an
IPS sensor. The FortiGate unit provides a number of pre-built IPS sensors, but you should
check their settings before using them, to ensure they meet your network requirements.
By using only the signatures you require, you can improve system performance and
reduce the number of log messages and alert email messages the IPS sensor generates.
For example, if the FortiGate unit is not protecting a web server, do not include any web
server signatures.
Note: Some default protection profiles include IPS Sensors that use all the available
signatures. By using these default settings, you may be slowing down the overall
performance of the FortiGate unit. By creating IPS sensors with only the signatures your
network requires, you can ensure maximum performance as well as maximum protection.
Note: If virtual domains are enabled on the FortiGate unit, the Intrusion Protection settings
are configured separately in each VDOM. All sensors and custom signatures will appear
only in the VDOM in which they were created.
To view the predefined signature list, go to UTM > Intrusion Protection > Predefined. You
can also use filters and column settings to display the signatures you want to view. For
more information, see “Using display filters” on page 526.
By default, the signatures are sorted by name. To sort the table by another column, select
the header of the column to sort by.
Current Page The current page number of list items that are displayed. Select the left and
right arrows to display the first, previous, next or last page of signatures.
Column Settings Select to customize the signature information displayed in the table. You can
also readjust the column order. For more information, see “Using column
settings to control the columns displayed” on page 61 and “Web-based
manager icons” on page 63.
Clear All Filters If you have applied filtering to the predefined signature list display, select this
option to clear all filters and display all the signatures.
Filter icons Edit the column filters to filter or sort the predefined signature list according to
the criteria you specify. For more information, see “Adding filters to web-based
manager lists” on page 57.
Name The name of the signature. Each name is also a link to the description of the
signature in the FortiGuard Center Vulnerability Encyclopedia.
Severity The severity rating of the signature. The severity levels, from lowest to highest,
are Information, Low, Medium, High, and Critical.
Target The target of the signature: servers, clients, or both.
Protocols The protocol the signature applies to.
OS The operating system the signature applies to.
Applications The applications the signature applies to.
Enable The default status of the signature. A green circle indicates the signature is
enabled. A gray circle indicates the signature is not enabled.
Action The default action for the signature:
Pass — allows the traffic to continue without any modification.
Drop — prevents the traffic with detected signatures from reaching its
destination.
If Logging is enabled, the action appears in the status field of the log message
generated by the signature.
ID A unique numeric identifier for the signature.
Logging The default logging behavior of the signature. A green circle indicates logging is
enabled. A gray circle indicates logging is disabled.
Group A functional group that is assigned to that signature. This group is only for
reference and cannot be used to define filters.
Packet Log The default packet log status of the signature. A green circle indicates that the
packet log is enabled. A gray circle indicates that the packet log is not enabled.
Revision The revision level of the signature. If the signature is updated, the revision
number will be incremented.
Tip: To determine what effect IPS protection would have on your network traffic, you can
enable the required signatures, set the action to pass, and enable logging. Traffic will not be
interrupted, but you will be able to examine in detail which signatures were detected.
Custom signatures
Custom signatures provide the power and flexibility to customize the FortiGate Intrusion
Protection system for diverse network environments. The FortiGate predefined signatures
represent common attacks. If you use an unusual or specialized application or an
uncommon platform, you can add custom signatures based on the security alerts released
by the application and platform vendors.
You can also create custom signatures to help you block P2P protocols.
After creation, you need to specify custom signatures in IPS sensors created to scan
traffic. For more information about creating IPS sensors, see “Adding an IPS sensor” on
page 530.
For more information about custom signatures, see the FortiGate UTM User Guide.
Note: If virtual domains are enabled on the FortiGate unit, the Intrusion Protection settings
are configured separately in each VDOM. All sensors and custom signatures will appear
only in the VDOM in which they were created.
Edit
Delete
Note: Custom signatures are an advanced feature. This document assumes the user has
previous experience creating intrusion detection signatures.
Note: Custom signatures must be added to a signature override in an IPS filter to have any
effect. Creating a custom signature is a necessary step, but a custom signature does not
affect traffic simply by being created.
Protocol decoders
The FortiGate Intrusion Protection system uses protocol decoders to identify the abnormal
traffic patterns that do not meet the protocol requirements and standards. For example,
the HTTP decoder monitors traffic to identify any HTTP packets that do not meet the
HTTP protocol standards.
IPS sensors
You can group signatures into IPS sensors for easy selection in protection profiles. You
can define signatures for specific types of traffic in separate IPS sensors, and then select
those sensors in profiles designed to handle that type of traffic. For example, you can
specify all of the web-server related signatures in an IPS sensor, and the sensor can then
be used by a protection profile in a policy that controls all of the traffic to and from a web
server protected by the FortiGate unit.
The FortiGuard Service periodically updates the pre-defined signatures, with signatures
added to counter new threats. Because the signatures included in filters are defined by
specifying signature attributes, new signatures matching existing filter specifications will
automatically be included in those filters. For example, if you have a filter that includes all
signatures for the Windows operating system, your filter will automatically incorporate new
Windows signatures as they are added.
Edit
Delete
Create New Add a new IPS sensor. For more information, see “Adding an IPS
sensor” on page 530.
Name The name of each IPS sensor.
Comments An optional description of the IPS sensor.
Delete and Edit icons Delete or edit an IPS sensor.
Five default IPS sensors are provided with the default configuration.
all_default Includes all signatures. The sensor is set to use the default enable
status and action of each signature.
all_default_pass Includes all signatures. The sensor is set to use the default enable
status of each signature, but the action is set to pass.
protect_client Includes only the signatures designed to detect attacks against clients
and uses the default enable status and action of each signature.
Name The name of the IPS sensor. You can change it at any time.
Comments An optional comment describing the IPS sensor. You can change it at any time.
OK Select to save changes to Name or Comments
IPS sensor filters:
Add Filter Add a new filter to the end of the filter list. For more information, see
“Configuring filters” on page 532.
# Current position of each filter in the list.
Name The name of the filter.
Signature Signature attributes specify the type of network traffic the signature applies to.
attributes
Severity The severity of the included signatures.
Target The type of system targeted by the attack. The targets are client
and server.
Protocol The protocols to which the signatures apply. Examples include
HTTP, POP3, H323, and DNS.
OS The operating systems to which the signatures apply.
Application The applications to which the signatures apply.
Enable The status of the signatures included in the filter. The signatures can be set to
enabled, disabled, or default. The default setting uses the default status of each
individual signature as displayed in the signature list.
Logging The logging status of the signatures included in the filter. Logging can be set to
enabled, disabled, or default. The default setting uses the default status of each
individual signature as displayed in the signature list.
Action The action of the signatures included in the filter. The action can be set to pass
all, block all, reset all, or default. The default setting uses the action of each
individual signature as displayed in the signature list.
Count The number of signatures included in the filter. Overrides are not included in this
total.
Delete icon Delete the filter.
Edit icon Edit the filter.
Insert icon Create a new filter and insert it above the current filter.
Move to icon After selecting this icon, enter the destination position in the window that
appears, and select OK.
View Rules icon Open a window listing all of the signatures included in the filter.
Configuring filters
To configure a filter, go to UTM > Intrusion Protection > IPS Sensor. Select the Edit icon of
the IPS sensor containing the filter you want to edit. When the sensor window opens,
select the Edit icon of the filter you want to change, or select Add Filter to create a new
filter. Enter the information as described below and select OK.
Right Arrow
Left Arrow
Target Select All, or select Specify and then choose the type of system targeted by the
attack. The choices are server or client.
OS Select All, or select Specify and then select one or more operating systems that
are vulnerable to the attack.
Signatures with an OS attribute of All affect all operating systems. These
signatures will be automatically included in any filter regardless of whether a
single, multiple, or all operating systems are specified.
Protocol Select All, or select Specify to list what network protocols are used by the attack.
Use the Right Arrow to move the ones you want to include in the filter from the
Available to the Selected list, or the Left Arrow to remove previously selected
protocols from the filter.
Application Select All, or select Specify to list the applications or application suites vulnerable
to the attack. Use the Right Arrow to move the ones you want to include in the
filter from the Available to the Selected list, or the Left Arrow to remove previously
selected protocols from the filter.
Quarantine Select to enable NAC quarantine for this filter. For more information about NAC
Attackers (to quarantine, see “NAC quarantine and the Banned User list” on page 670.
Banned Users The FortiGate unit deals with the attack according to the IPS sensor or DoS
List) sensor configuration regardless of this setting.
Method Select Attacker’s IP address to block all traffic sent from the attacker’s IP
address. The attacker’s IP address is also added to the banned user list. The
target’s address is not affected.
Select Attacker and Victim IP Addresses to block all traffic sent from the attacker
IP address to the target (victim) IP address. Traffic from the attacker IP address to
addresses other than the victim IP address is allowed. The attacker and target IP
addresses are added to the banned user list as one entry.
Select Attack’s Incoming Interface to block all traffic from connecting to the
FortiGate interface that received the attack. The interface is added to the banned
user list.
Expires You can select whether the attacker is banned indefinitely or for a specified
number of days, hours, or minutes.
Signature Configure whether the filter overrides the following signature settings or accepts
Settings the settings in the signatures.
Enable Select from the options to specify what the FortiGate unit will do with the
signatures included in the filter: enable all, disable all, or enable or disable each
according to the individual default values shown in the signature list.
Logging Select from the options to specify whether the FortiGate unit will create log entries
for the signatures included in the filter: enable all, disable all, or enable or disable
logging for each according to the individual default values shown in the signature
list.
Action Select from the options to specify what the FortiGate unit will do with traffic
containing a signature match: pass all, block all, reset all, or block or pass traffic
according to the individual default values shown in the signature list.
The signatures included in the filter are only those matching every attribute specified.
When created, a new filter has every attribute set to all which causes every signature to be
included in the filter. If the severity is changed to high, and the target is changed to server,
the filter includes only signatures checking for high priority attacks targeted at servers.
• To add an individual signature, not included in any filters, to an IPS sensor. This is the
only way to add custom signatures to IPS sensors.
When a pre-defined signature is specified in an override, the default status and action
attributes have no effect. These settings must be explicitly set when creating the override.
Note: Before an override can affect network traffic, you must add it to a filter, and you must
select the sensor in a protection profile applied to a policy. An override does not have the
ability to affect network traffic until these steps are taken.
To edit a pre-defined or custom override, go to UTM > Intrusion Protection > IPS Sensor
and select the Edit icon of the IPS sensor containing the override you want to edit. When
the sensor window opens, select the Edit icon of the override you want to change.
Signature Select the browse icon to view the list of available signatures. From this list,
select a signature the override will apply to and then select OK.
Enable Select to enable the signature override.
Action Select Pass, Block or Reset. When the override is enabled, the action
determines what the FortiGate will do with traffic containing the specified
signature.
Logging Select to enable creation of a log entry if the signature is discovered in
network traffic.
Packet Log Select to save packets that trigger the override to the FortiGate hard drive for
later examination.
Quarantine Select to enable NAC quarantine for this override. For more information
Attackers (to about NAC quarantine, see “NAC quarantine and the Banned User list” on
Banned Users List) page 670.
The FortiGate unit deals with the attack according to the IPS sensor or DoS
sensor configuration regardless of this setting.
Method Select Attacker’s IP address to block all traffic sent from the attackers IP
address. The attackers IP address is also added to the banned user list. The
target address is not affected.
Select Attacker and Victim IP Addresses to block all traffic sent from the
attacker IP address to the target (victim) IP address. Traffic from the attacker
IP address to addresses other than the victim IP address is allowed. The
attacker and target IP addresses are added to the banned user list as one
entry.
Select Attack’s Incoming Interface to block all traffic from connecting to the
FortiGate interface that received the attack. The interface is added to the
banned user list.
Expires You can select whether the attacker is banned indefinitely or for a specified
number of days, hours, or minutes.
Exempt IP Enter IP addresses to exclude from the override. The override will then apply
to all IP addresses except those defined as exempt. The exempt IP
addresses are defined in pairs, with a source and destination, and traffic
moving from the source to the destination is exempt from the override.
Source The exempt source IP address. Enter 0.0.0.0/0 to include all source IP
addresses.
Destination: The exempt destination IP address. Enter 0.0.0.0/0 to include all
destination IP addresses.
Packet logging
Packet logging is a way you can debug custom signatures or how any signature is
functioning in your network environment.
If a signature is selected in a custom override, and packet logging is enabled, the
FortiGate unit will save any network packet triggering the signature to memory, the internal
hard drive (if so equipped), a FortiAnalyzer, or the FortiGuard Analysis and Management
Service. These saved packets can be later viewed and saved in PCAP format for closer
examination.
Note: Setting packet-log-history to a value larger than 1 can affect the maximum
performance of the FortiGate unit because network traffic must be buffered. The
performance penalty depends on the model, the setting, and the traffic load.
5 Select the packet to view the packet in binary and ASCII. Each table row represents a
captured packet.
6 Select Save to save the packet data in a PCAP formatted file.
PCAP files can be opened and examined in network analysis software such as Wireshark.
DoS sensors
The FortiGate IPS uses a traffic anomaly detection feature to identify network traffic that
does not fit known or common traffic patterns and behavior. For example, one type of
flooding is the denial of service (DoS) attack that occurs when an attacking system starts
an abnormally large number of sessions with a target system. The large number of
sessions slows down or disables the target system so legitimate users can no longer use
it. This type of attack gives the DoS sensor its name, although it is capable of detecting
and protecting against a number of anomaly attacks.
You can enable or disable logging for each traffic anomaly, and configure the detection
threshold and action to take when the detection threshold is exceeded.
You can create multiple DoS sensors. Each sensor consists of 12 anomaly types that you
can configure. When a sensor detects an anomaly, it applies the configured action. One
sensor can be selected for use in each DoS policy, allowing you to configure the anomaly
thresholds separately for each interface. Multiple sensors allow great granularity in
detecting anomalies because each sensor can be configured for the specific needs of the
interface it is attached to by the DoS policy.
The traffic anomaly detection list can be updated only when the FortiGate firmware image
is upgraded.
Note: If virtual domains are enabled on the FortiGate unit, the Intrusion Protection settings
must be configured separately in each VDOM. All sensors and custom signatures will
appear only in the VDOM in which they were created.
Create New Add a new DoS sensor to the bottom of the list.
Name The DoS sensor name.
Comments An optional description of the DoS sensor.
Delete icon Delete the DoS sensor.
Edit icon Edit the following information: Action, Severity, and Threshold.
Note: It is important to know normal and expected network traffic before changing the
default anomaly thresholds. Setting the thresholds too low could cause false positives, and
setting the thresholds too high could allow otherwise avoidable attacks.
To configure DoS sensors, go to UTM > Intrusion Protection > DoS Sensor. Select the Edit
icon of an existing DoS sensor, or select Create New to create a new DoS sensor.
Note: You can configure NAC quarantine for DoS sensors from the FortiGate CLI. For
more information, see “Configuring NAC quarantine” on page 671.
Anomaly Description
tcp_syn_flood If the SYN packet rate, including retransmission, to one destination IP
address exceeds the configured threshold value, the action is executed.
The threshold is expressed in packets per second.
tcp_port_scan If the SYN packets rate, including retransmission, from one source IP
address exceeds the configured threshold value, the action is executed.
The threshold is expressed in packets per second.
Anomaly Description
tcp_src_session If the number of concurrent TCP connections from one source IP address
exceeds the configured threshold value, the action is executed.
tcp_dst_session If the number of concurrent TCP connections to one destination IP
address exceeds the configured threshold value, the action is executed.
udp_flood If the UDP traffic to one destination IP address exceeds the configured
threshold value, the action is executed. The threshold is expressed in
packets per second.
udp_scan If the number of UDP sessions originating from one source IP address
exceeds the configured threshold value, the action is executed. The
threshold is expressed in packets per second.
udp_src_session If the number of concurrent UDP connections from one source IP address
exceeds the configured threshold value, the action is executed.
udp_dst_session If the number of concurrent UDP connections to one destination IP
address exceeds the configured threshold value, the action is executed.
icmp_flood If the number of ICMP packets sent to one destination IP address
exceeds the configured threshold value, the action is executed. The
threshold is expressed in packets per second.
icmp_sweep If the number of ICMP packets originating from one source IP address
exceeds the configured threshold value, the action is executed. The
threshold is expressed in packets per second.
icmp_src_session If the number of concurrent ICMP connections from one source IP
address exceeds the configured threshold value, the action is executed.
icmp_dst_session If the number of concurrent ICMP connections to one destination IP
address exceeds the configured threshold value, the action is executed.
Web Filter
This chapter describes how to configure FortiGate web filtering for HTTP traffic. If your
FortiGate unit supports SSL content scanning and inspection you can also configure web
filtering for HTTPS traffic. For information about SSL content scanning and inspection, see
“SSL content scanning and inspection” on page 469. if your FortiGate unit does not
support HTTPS content scanning and inspection you can configure URL filtering for
HTTPS traffic.
The three main sections of the web filtering function, the Web Content Filter, the URL
Filter, and the FortiGuard Web filter, interact with each other in such a way as to provide
maximum control and protection for the Internet users.
This section provides an introduction to configuring web filtering. For more information see
the FortiGate UTM User Guide.
If you enable virtual domains (VDOMs) on the FortiGate unit, web filtering is configured
separately for each virtual domain. For details, see “Using virtual domains” on page 125.
This section describes:
• Order of web filtering
• How web filtering works
• Web filter controls
• Web content filter
• URL filter
• FortiGuard Web Filtering
• FortiGuard Web filtering overrides
• Category block CLI configuration
• FortiGuard Web Filtering reports
Note: Enabled means that the filter will be used when you turn on web filtering. It does not
mean that the filter is turned on. To turn on all enabled filters you must go to Firewall >
Protection Profile.
Table 55: Web filter and Protection Profile protocol recognition configuration
Table 56: Web filter and Protection Profile web content filter configuration
Table 57: Web filter and Protection Profile web URL filtering configuration
Table 58: Web filter and Protection Profile web script filtering and download configuration
Table 59: Web filter and Protection Profile FortiGuard web filtering configuration
Note: If virtual domains are enabled on the FortiGate unit, web filtering features are
configured globally. To access these features, select Global Configuration on the main
menu.
Note: Perl regular expression patterns are case sensitive for the Web content filter. To
make a word or phrase case insensitive, use the regular expression /i. For example,
/bad language/i blocks all instances of bad language regardless of case. Wildcard
patterns are not case sensitive.
For each pattern you can select Block or Exempt. Block, blocks access to a web page that
matches with the pattern. Exempt allows access to the web page even if other entries in
the list that would block access to the page.
Create New Select to add a new web content filter list to the catalog.
Name The available web content filter lists.
# Entries The number of content patterns in each web content filter list.
Profiles The protection profiles each web content filter list has been applied to.
Comment Optional description of each web content filter list. The comment text must be
less than 63 characters long. Otherwise, it will be truncated.
Delete icon Select to remove the web content filter list from the catalog. The delete icon is
only available if the web content filter list is not selected in any protection
profiles.
Edit icon Select to edit the web content filter list, list name, or list comment.
Select web content filter lists in protection profiles. For more information, see “Web
Filtering options” on page 480.
Note: Enable UTM > Web Filtering > Web Content Filter in a firewall Protection Profile to
activate the content filter settings.
The web content filter list has the following icons and features:
Name Web content filter list name. To change the name, edit text in the name field and
select OK.
Comment Optional comment. To add or edit comment, enter text in comment field and
select OK.
Create new Select to add a pattern to the web content filter list.
Previous Page Select to view the previous page.
icon
Next Page icon Select to view the next page.
Remove All Select to clear the table.
Entries icon
Check Box Select the check box to enable all the patterns in the list. Clear the check box to
disable all of the patterns in the list. Use the check box for individual patterns to
enable or disable them.
Pattern The current list of patterns.
Pattern type The pattern type used in the pattern list entry. Pattern type can be wildcard or
regular expression. See “Using wildcards and Perl regular expressions” on
page 571.
Language The character set to which the pattern belongs: Simplified Chinese, Traditional
Chinese, Cyrillic, French, Japanese, Korean, Spanish, Thai, or Western.
Action Action can be block or exempt.
Score A numerical weighting applied to the pattern. The score values of all the matching
patterns appearing on a page are added, and if the total is greater than the
threshold value set in the protection profile, the page is blocked.
Delete icon Select to delete an entry from the list.
Edit icon Select to edit the following information: Banned Word, Pattern Type, Language,
and Enable.
URL filter
Allow or block access to specific URLs by adding them to the URL filter list. Add patterns
using text and regular expressions (or wildcard characters) to allow or block URLs. The
FortiGate unit allows or blocks web pages matching any specified URLs or patterns and
displays a replacement message instead.
Note: Enable Web filtering > Web URL Filter in a firewall Protection Profile to activate the
URL filter settings.
Note: URL blocking does not block access to other services that users can access with a
web browser. For example, URL blocking does not block access to
ftp://ftp.example.com. Instead, use firewall policies to deny FTP connections.
The URL filter list catalogue has the following icons and features:
Create New Select to add a new web content URL list to the catalog.
Name The available URL filter lists.
# Entries The number of URL patterns in each URL filter list.
Profiles The protection profiles each URL filter list has been applied to.
Comment Optional description of each URL filter list.
Delete icon Select to remove the URL filter list from the catalog. The delete icon is only
available if the URL filter list is not selected in any protection profiles.
Edit icon Select to edit the URL filter list, list name, or list comment.
Select URL filter lists in protection profiles. For more information, see “Web Filtering
options” on page 480.
The URL filter list has the following icons and features:
Name URL filter list name. To change the name, edit text in the name field and select
OK.
Comment Optional comment. To add or edit comment, enter text in comment field and
select OK.
Create New Select to add a URL to the URL block list.
Previous Page Select to view the previous page.
icon
next Page icon Select to view the next page.
Clear All URL Select to clear the table.
Filters icon
URL The current list of blocked/exempt URLs. Select the check box to enable all
the URLs in the list.
Type The type of URL: Simple or Regex (regular expression).
Action The action taken when the URL matches: Allow, Block, or Exempt.
An allow match exits the URL filter list and checks the other web filters.
An exempt match stops all further checking including AV scanning.
A block match blocks the URL and no further checking will be done.
Delete icon Select to remove an entry from the list.
Edit icon Select to edit the following information: URL, Type, Action, and Enable.
Move icon Select to open the Move URL Filter dialog box.
Note: Type a top-level domain suffix (for example, “com” without the leading period) to
block access to all URLs with this suffix.
To add a URL to the URL filter list go to UTM > Web Filter > URL Filter. Select Create New
or edit an existing list.
URL Enter the URL. Do not include http://. For details about URL
formats, see “URL formats” on page 550.
Type Select a type from the dropdown list: Simple or Regex (regular
expression).
Action Select an action from the dropdown list: Allow, Block, or Exempt.
An allow match exits the URL filter list and checks the other web
filters.
An exempt match stops all further checking including AV
scanning.
A block match blocks the URL and no further checking will be
done.
Enable Select to enable the URL.
URL formats
When adding a URL to the URL filter list (see “Configuring the URL filter list” on
page 550), follow these rules:
Note: URLs with an action set to exempt are not scanned for viruses. If users on
the network download files through the FortiGate unit from trusted website, add the
URL of this website to the URL filter list with an action set to exempt so the
FortiGate unit does not virus scan files downloaded from this URL.
Note: Enable Web Filtering > Web URL Filter > HTTP or HTTPS in a firewall Protection
Profile to activate the web URL filter settings for HTTP and/or HTTPS traffic.
To create an override for categories, go to UTM > Web Filter > Override.
The local ratings list has the following icons and features:
Note: FortiGuard Web Filtering reports are only available on FortiGate units with a hard
disk.
Generate a text and pie chart format report on FortiGuard Web Filtering for any protection
profile. The FortiGate unit maintains statistics for allowed, blocked, and monitored web
pages for each category. View reports for a range of hours or days, or view a complete
report of all activity.
To create a web filter report go to UTM > Web Filter > Reports.
See also
• Creating local categories
• Viewing the local ratings list
• Configuring local ratings
• FortiGuard Web filtering overrides
• Configuring administrative override rules
• Configuring FortiGuard Web Filtering
• FortiGuard Web Filtering
Email filtering
This chapter describes how to configure FortiGate email filtering for IMAP, POP3, and
SMTP email. If your FortiGate unit supports SSL content scanning and inspection you can
also configure email filtering for IMAPS, POP3S, and SMTPS email traffic. For information
about SSL content scanning and inspection, see “SSL content scanning and inspection”
on page 469.
If you enable virtual domains (VDOMs) on the FortiGate unit, Email filtering is configured
separately for each virtual domain. For details, see “Using virtual domains” on page 125.
This section provides an introduction to configuring email filtering. For more information
see the FortiGate UTM User Guide.
This section describes:
• FortiGuard Email Filtering (also called the FortiGuard Antispam Service)
• Banned word
• IP address and email address black/white lists
• Advanced Email Filter configuration
• Using wildcards and Perl regular expressions
If the action in the filter is Mark as Clear, the email is exempt from any remaining filters. If
the action in the filter is Mark as Reject, the email session is dropped. Rejected SMTP or
SMTPS email messages are substituted with a configurable replacement message.
Table 60: Email filtering and Protection Profile email filtering configuration (Continued)
Table 60: Email filtering and Protection Profile email filtering configuration (Continued)
Banned word
Control spam by blocking email messages containing specific words or patterns. You can
add words, phrases, wild cards and Perl regular expressions to match content in email
messages.
For information, about wild cards and Perl regular expressions, see “Using wildcards and
Perl regular expressions” on page 571.
Note: Perl regular expression patterns are case sensitive for banned words. To make a
word or phrase case insensitive, use the regular expression /i. For example,
/bad language/i will block all instances of bad language regardless of case. Wildcard
patterns are not case sensitive.
Edit
Delete
Create New Add a new list to the catalog. For more information, see “Creating a new
banned word list” on page 563.
Name The available Email Filter banned word lists.
Name Banned word list name. To change the name, edit text in the name field and
select OK.
Comments Optional comment. To add or edit comment, enter text in comment field and
select OK.
Create New Select to add a word or phrase to the banned word list.
Current Page The current page number of list items that are displayed. Select the left and right
arrows to display the first, previous, next or last page of the banned word list.
Remove All Delete all table entries.
Entries icon
Pattern The list of banned words. Select the check box to enable all the banned words in
the list.
Pattern Type The pattern type used in the banned word list entry. Choose from wildcard or
regular expression. For more information, see “Using wildcards and Perl regular
expressions” on page 571.
Language The character set to which the banned word belongs.
Where The location where the FortiGate unit searches for the banned word: Subject,
Body, or All.
Score A numerical weighting applied to the banned word. The score values of all the
matching words appearing in an email message are added, and if the total is
greater than the Banned word check value set in the protection profile, the email
is processed according to whether the spam action is set to Discard or Tagged
in the protection profile. The score for a banned word is counted once even if the
word appears multiple times on the web page in the email. For more information,
see “Configuring a protection profile” on page 474.
Delete and Edit Delete or edit the banned word.
icons
Pattern Enter the banned word pattern. A pattern can be part of a word, a whole word,
or a phrase. Multiple words entered as a pattern are treated as a phrase. The
phrase must appear exactly as entered to match. You can also use wildcards
or regular expressions to have a pattern match multiple words or phrases.
Pattern Type Select the pattern type for the banned word. Choose from wildcard or regular
expression. For more information, see “Using wildcards and Perl regular
expressions” on page 571.
Language Select the character set for the banned word.
Where Select where the FortiGate unit should search for the banned word: Subject,
Body, or All.
Score Enter a score for the pattern.
Each entry in the banned word list added to the protection profile incudes a
score. When an email message is matched with an entry in the banned word
list, the score is recorded. If an email message matches more than one entry,
the score for the email message increases. When the total score for an email
message equals or exceeds the threshold, the message is considered spam
and handled according to the spam action configured in the protection profile.
The default score for a banned word list entry is 10 and the default threshold is
10. This means that by default an email message is considered spam by a
single match. You can change the scores and threshold so email messages
are only tagged as spam if there are multiple matches.
For more information, see “Email Filtering options” on page 485.
Enable Select to enable scanning for the banned word.
4 Select OK.
Edit
Delete
Move To
Edit
Delete
Name IP address list name. To change the name, edit text in the name field and
select OK.
Comments Optional comment. To add or edit a comment, enter text in the comments field
and select OK.
Create New Add an IP address to the IP address list.
Current Page The current page number of list items that are displayed. Select the left and
right arrows to display the first, previous, next or last page of the IP address
list.
Remove All Entries Delete all table entries.
icon
IP address/Mask The list of IP addresses.
Action The action to take on email from the configured IP address. Actions are: Spam
to apply the configured spam action, Clear to bypass this and remaining email
filters, or Reject (SMTP or SMTPS) to drop the session.
If an IP address is set to reject but mail is delivered from that IP address via
using POP3 or IMAP, the email messages will be marked as spam.
Delete icon Remove the address from the list.
Edit icon Edit address information.
Move To icon Select to move the entry to a different position in the list.
The firewall policy executes the list from top to bottom. For example, if you
have IP address 192.168.100.1 listed as spam and 192.168.100.2 listed as
clear, you must put 192.168.100.1 above 192.168.100.2 for 192.168.100.1 to
take effect.
Adding an IP address
After creating an IP address list, you can add IP addresses to the list.
Enter an IP address or a pair of IP address and mask in the following formats:
• x.x.x.x, for example, 192.168.69.100.
• x.x.x.x/x.x.x.x, for example, 192.168.69.100/255.255.255.0
• x.x.x.x/x, for example, 192.168.69.100/24
To add an IP address go to UTM > Email Filter > IP Address. Select Edit for the IP
address list name to which you want to add an IP address. Then select Create New.
Edit
Delete
You enable email filter addresses in protection profiles. For more information, see “Email
Filtering options” on page 485.
Delete
Edit
Move To
Remove All Entries
Name The email address list name. To change the name, edit text in the name field
and select OK.
Comments Optional comment. To add or edit comment, enter text in comment field and
select OK.
Create New Add a new email address to the email address list.
Current Page The current page number of list items that are displayed. Select the left and
right arrows to display the first, previous, next or last page of the email
address list.
Remove All Entries Delete all table entries.
icon
Email address The list of email addresses.
Pattern Type The pattern type used in the email address entry.
Action The action to take on email from the configured address. Actions are: Spam to
apply the spam action configured in the protection profile, or Clear to let the
email message bypass this and remaining email filters.
Delete icon Remove the email address from the list.
Edit icon Edit the address information.
Move To icon Move the entry to a different position in the list.
The email address scan executes the list from top to bottom. For example, if
you have abc@example.com listed as clear and *@example.com as spam,
you must put abc@example.com above *@example.com for
abc@example.com to take effect.
Note: Because the FortiGate unit uses the server domain name to connect to the DNSBL
or ORDBL server, it must be able to look up this name on the DNS server. For information
on configuring DNS, see “Configuring Networking Options” on page 176.
Note: To add a question mark (?) character to a regular expression from the FortiGate CLI,
enter Ctrl+V followed by ?. To add a single backslash character (\) to a regular expression
from the CLI you must add precede it with another backslash character. For example,
fortinet\\.com.
To match a special character such as '.' and ‘*’ use the escape character ‘\’. For example:
• To match fortinet.com, the regular expression should be: fortinet\.com
In Perl regular expressions, ‘*’ means match 0 or more times of the character before it, not
0 or more times of any character. For example:
• forti*.com matches fortiiii.com but does not match fortinet.com
To match any character 0 or more times, use ‘.*’ where ‘.’ means any character and the ‘*’
means 0 or more times. For example, the wildcard match pattern forti*.com should
therefore be fort.*\.com.
Word boundary
In Perl regular expressions, the pattern does not have an implicit word boundary. For
example, the regular expression “test” not only matches the word “test” but also any word
that contains “test” such as “atest”, “mytest”, “testimony”, “atestb”. The notation “\b”
specifies the word boundary. To match exactly the word “test”, the expression should be
\btest\b.
Case sensitivity
Regular expression pattern matching is case sensitive in the web and Email Filter filters.
To make a word or phrase case insensitive, use the regular expression /i. For example,
/bad language/i will block all instances of “bad language”, regardless of case.
Expression Matches
abc “abc” (the exact character sequence, but anywhere in the string)
^abc “abc” at the beginning of the string
abc$ “abc” at the end of the string
a|b Either “a” or “b”
^abc|abc$ The string “abc” at the beginning or at the end of the string
ab{2,4}c “a” followed by two, three or four “b”s followed by a “c”
ab{2,}c “a” followed by at least two “b”s followed by a “c”
ab*c “a” followed by any number (zero or more) of “b”s followed by a “c”
ab+c “a” followed by one or more b's followed by a c
ab?c “a” followed by an optional “b” followed by a” c”; that is, either “abc” or”
ac”
a.c “a” followed by any single character (not newline) followed by a” c “
a\.c “a.c” exactly
[abc] Any one of “a”, “b” and “c”
[Aa]bc Either of “Abc” and “abc”
[abc]+ Any (nonempty) string of “a”s, “b”s and “c”s (such as “a”, “abba”,
”acbabcacaa”)
[^abc]+ Any (nonempty) string which does not contain any of “a”, “b”, and “c”
(such as “defg”)
\d\d Any two decimal digits, such as 42; same as \d{2}
/i Makes the pattern case insensitive. For example, /bad language/i
blocks any instance of bad language regardless of case.
\w+ A “word”: A nonempty sequence of alphanumeric characters and low
lines (underscores), such as foo and 12bar8 and foo_1
100\s*mk The strings “100” and “mk” optionally separated by any amount of white
space (spaces, tabs, newlines)
abc\b “abc” when followed by a word boundary (for example, in “abc!” but not in
“abcd”)
perl\B “perl” when not followed by a word boundary (for example, in “perlert” but
not in “perl stuff”)
\x Tells the regular expression parser to ignore white space that is neither
preceded by a backslash character nor within a character class. Use this
to break up a regular expression into (slightly) more readable parts.
/x Used to add regular expressions within other text. If the first character in
a pattern is forward slash '/', the '/' is treated as the delimiter. The pattern
must contain a second '/'. The pattern between ‘/’ will be taken as a
regular expressions, and anything after the second ‘/’ will be parsed as a
list of regular expression options ('i', 'x', etc). An error occurs if the
second '/' is missing. In regular expressions, the leading and trailing
space is treated as part of the regular expression.
Current Page
DLP Sensors
DLP sensors are simply collections of DLP rules and DLP compound rules. The DLP
sensor also includes settings such as action, archive, and severity for each rule or
compound rule. Once a DLP sensor is configured, it can be specified in a protection
profile. Any traffic handled by the policy in which the protection profile is specified will
enforce the DLP sensor configuration.
Delete
Edit
Caution: Before use, examine the sensors and rules in the sensors closely to ensure you
understand how they will affect the traffic on your network.
Note: DLP prevents duplicate action. Even if more than one rule in a sensor matches some
content, DLP will not create more than one DLP archive entry, quarantine item, or ban entry
from the same content.
Content_Archive DLP archive all email (POP3, IMAP, and SMTP), FTP, HTTP, and IM traffic.
For each rule in the sensor, Archive is set to Full. No blocking or quarantine is
performed. See “DLP archiving” on page 580.
You can add the All-Session-Control rule to also archive session control
content.
If you have a FortiGate unit that supports SSL content scanning and
inspection, you can edit the All-Email rule to archive POP3S, IMAPS, and
SMTPS traffic. You can also edit the All-HTTP rule to archive HTTPS traffic.
Content_Summary DLP summary archive all email (POP3, IMAP, and SMTP), FTP, HTTP, and IM
traffic. For each rule in the sensor, Archive is set to Summary Only. No
blocking or quarantine is performed. See “DLP archiving” on page 580.
You can add the All-Session-Control rule to also archive session control
content.
If you have a FortiGate unit that supports SSL content scanning and
inspection, you can edit the All-Email rule to archive POP3S, IMAPS, and
SMTPS traffic. You can also edit the All-HTTP rule to archive HTTPS traffic.
Credit-Card The number formats used by American Express, Visa, and Mastercard credit
cards are detected in HTTP and email traffic.
As provided, the sensor is configured not to archive matching traffic and an
action of None is set. Configure the action and archive options as required.
Large-File Files larger than 5MB will be detected if attached to email messages or if send
using HTTP or FTP.
As provided, the sensor is configured not to archive matching traffic and an
action of None is set. Configure the action and archive options as required.
SSN-Sensor The number formats used by U.S. Social Security and Canadian Social
Insurance numbers are detected in email and HTTP traffic.
As provided, the sensor is configured not to archive matching traffic and an
action of None is set. Configure the action and archive options as required.
Delete
Edit
To edit a rule or compound rule already included in a sensor, go to UTM > Data Leak
Prevention > Sensor and select the Edit icon of the sensor to be configured. Select the
edit icon of the rule or compound rule to edit. Change the settings for the rule or
compound rule.
Action Select the action to be taken against traffic matching the configured DLP rule or DLP
compound rule. The actions are:
• None prevents the DLP rule from taking any action on network traffic. Other
matching rules in the same sensor and other sensors may still operate on
matching traffic.
• Block prevents the traffic matching the rule from being delivered. The matching
message or download is replaced with the Data leak prevention replacement
message.
• Exempt prevents any DLP sensors from taking action on matching traffic. This
action overrides any other action from any matching sensors.
• Ban if the user is authenticated, blocks all traffic to or from the user using the
protocol that triggered the rule and the user will be added to the Banned User list.
If the user is not authenticated, all traffic of the protocol that triggered the rule from
the user’s IP address will be blocked. If the user that is banned is using HTTP,
FTP, NNTP (or HTTPS if the FortiGate unit supports SSL content scanning and
inspection) the FortiGate unit displays the Banned by data leak prevention
replacement message for the protocol. If the user is using IM, the IM and P2P
Banned by data leak prevention message replaces the banned IM message and
this message is forwarded to the recipient. If the user is using IMAP, POP3, SMTP
(or MAPS, POP3S, SMTPS if your FortiGate unit supports SSL content scanning
and inspection) the Mail Banned by data leak prevention message replaces the
banned email message and this message is forwarded to the recipient. These
replacement messages also replace all subsequent communication attempts until
the user is removed from the banned user list.
• Ban Sender blocks email or IM traffic from the sender of matching email or IM
messages and adds the sender to the Banned User list. This action is available
only for email and IM protocols. For email, the sender is determined by the From:
address in the email header. For IM, all members of an IM session are senders
and the senders are determined by finding the IM user IDs in the session. Similar
to Ban, the IM or Mail Banned by data leak prevention message replaces the
banned message and this message is forwarded to the recipient. These
replacement messages also replace all subsequent communication attempts until
the user is removed from the banned user list.
• Quarantine IP address blocks access through the FortiGate unit for any IP
address that sends traffic matching a sensor with this action. The IP address is
added to the Banned User list. The FortiGate unit displays the NAC Quarantine
DLP Message replacement message for all connection attempts from this IP
address until the IP address is removed from the banned user list.
• Quarantine Interface blocks access to the network for all users connecting to the
interface that received traffic matching a sensor with this action. The FortiGate unit
displays the NAC Quarantine DLP Message replacement message for all
connection attempts to the interface until the interface is removed from the banned
user list.
Ban, Ban Sender, Quarantine IP, and Quarantine Interface provide functionality
similar to NAC quarantine. However, these DLP options cause DLP to block users
and IP addresses at the application layer while NAC quarantine blocks IP addresses
and interfaces at the network layer. For more information, see “NAC quarantine and
the Banned User list” on page 670.
For more information about configuring DLP replacement messages, see
“Replacement messages” on page 225.
If you have configured DLP to block IP addresses and if the FortiGate unit receives
sessions that have passed through a NAT device, all traffic from that NAT device
could be blocked not just individual users. You can avoid this problem by
implementing authentication or where possible select Ban Sender.
Archive Configure DLP archiving for the rule. Archive is available for Email, FTP, HTTP, IM,
and Session Control rules and compound rules. The options are:
• Disable, do not archive.
• Full, perform full DLP archiving.
• Summary Only, perform summary DLP archiving.
See “DLP archiving” on page 580.
Severity Enter the severity of the content that the rule or compound rule is a match for. Use the
severity to indicate the seriousness of the problems that would result from the content
passing through the FortiGate unit. For example, if the DLP rule finds high-security
content the severity could be 5. On the other hand if the DLP rule finds any content
the severity should be 1.
DLP adds the severity to the severity field of the log message generated when the
rule or compound rule matches content. The higher the number the greater the
severity.
Expires When the action is set to Ban, Ban Sender, or Quarantine IP address, you can specify
how long the ban will last. Select Indefinite for a ban ending only if the offender is
manually removed from the banned user list, or select After and enter the required
number of minutes, hours or days the ban will last. When the specified duration
expires, the offender is automatically removed from the banned user list.
Member Select Rule or Compound Rule. The rules of the selected type will be displayed in the
Type table below.
Name The names of all available rules or compound rules.
Description The optional description entered for each rule or compound rule.
DLP archiving
You can use DLP archiving to collect and view historical logs that have been archived to a
FortiAnalyzer unit or the FortiGuard Analysis and Management service. DLP archiving is
available for FortiAnalyzer when you add a FortiAnalyzer unit to the FortiGate
configuration (see “Remote logging to a FortiAnalyzer unit” on page 704). The FortiGuard
Analysis and Management server becomes available when you subscribe to the
FortiGuard Analysis and Management Service (see the FortiGuard Analysis and
Management Service Administration Guide).
You can configure full DLP archiving and summary DLP archiving. Full DLP archiving
includes all content, for example, full email DLP archiving includes complete email
messages and attachments. Summary DLP archiving includes just the meta data about
the content, for example, email message summary records include only the email header.
You can archive Email, FTP, HTTP, IM, MMS, and session control content:
• Email content includes IMAP, POP3, and SMTP sessions. Email content can also
include email messages tagged as spam by FortiGate Email filtering. If your FortiGate
unit supports SSL content scanning and inspection, Email content can also include
IMAPS, POP3S, and SMTPS sessions.
• HTTP content includes HTTP sessions. If your FortiGate unit supports SSL content
scanning and inspection HTTP content can also include HTTPS sessions.
For more information about SSL content scanning and inspection, see “SSL content
scanning and inspection” on page 469.
• IM content includes AIM, ICQ, MSN, and Yahoo! sessions.
• Session control content includes SIP, SIMPLE and SCCP sessions. Only summary
DLP archiving is available for SIP and SCCP. Full and summary DLP archiving is
available for SIMPLE.
You add DLP sensors to archive Email, Web, FTP, IM, and session control content.
Archiving of spam email messages is configured in protection profiles.
Note: DLP prevents duplicate action. Even if more than one rule in a sensor matches some
content, DLP will not create more than one DLP archive entry from the same content.
Note: Enabling full DLP archiving reduces the amount of system memory available for virus
scanning. Fortinet recommends against using full DLP archiving if antivirus scanning is also
configured because of these memory constraints. Especially on FortiGate units with low
system memory.
Figure 349: Selecting HTTPS POST and HTTPS GET in the All-HTTPS DLP rule
3 Verify that Rule is set to Always so that the rule matches all HTTP and HTTPS post
and get sessions.
4 Select OK to save the changes to the rule.
5 Go to UTM > Data Leak Prevention > Sensor and edit the Content_Archive sensor.
8 Go to Firewall > Policy > Protection Profile and add a new or edit a protection profile.
9 Select the Data Leak Prevention Sensor expand arrow.
10 Select Data Leak Prevention Sensor and select the Content_Archive sensor from the
list.
11 Add the protection profile to a firewall policy that accepts HTTP and HTTPS traffic.
To DLP archive all email messages that contain the string “confidential”
This procedure describes how to add a DLP rule that finds the string “confidential” in the
body of POP3, IMAP, and SMTP email messages. To archive all email messages that
contain this string you must add the DLP rule to a DLP sensor and configure the sensor for
full DLP archiving.
1 Go to UTM > Data Leak Prevention > Rule and add a rule to find the string
“confidential” in POP3, SMTP, and IMAP email messages.
Figure 353: DLP rule to find the string “confidential” in the body of email messages
2 Go to UTM > Data Leak Prevention > Sensor and add a new sensor.
3 Edit the sensor and select Create New to add a rule to the sensor.
4 Configure the rule as follows:
Action None
Archive Full
Severity 1 (Lowest)
Member type Rule
Email_confidential Select
5 Go to Firewall > Policy > Protection Profile and add a new or edit a protection profile.
6 Select the Data Leak Prevention Sensor expand arrow.
7 Select Data Leak Prevention Sensor and select the new sensor from the list.
8 Add the protection profile to a firewall policy that accepts email traffic.
Note: Infected files are clearly indicated in the DLP Archive Email message list.
DLP Rules
DLP rules are the core element of the data leak prevention feature. These rules define the
data to be protected so the FortiGate unit can recognize it. For example, an included rule
uses regular expressions to describe Social Security number:
([0-6]\d{2}|7([0-6]\d|7[0-2]))[ \-]?\d{2}[ \-]\d{4}
Rather than having to list every possible Social Security number, this regular expression
describes the structure of a Social Security number. The pattern is easily recognizable by
the FortiGate unit. For more information about regular expressions, see “Using wildcards
and Perl regular expressions” on page 571.
DLP rules can be combined into compound rules and they can be included in sensors. If
rules are specified directly in a sensor, traffic matching any single rule will trigger the
configured action. If the rules are first combined into a compound rule and then specified
in a sensor, every rule in the compound rule must match the traffic to trigger the configured
action.
Individual rules in a sensor are linked with an implicit OR condition while rules within a
compound rule are linked with an implicit AND condition.
Delete
Edit
Note: These rules affect only unencrypted traffic types. If you are using a FortiGate unit
able to decrypt and examine encrypted traffic, you can enable those traffic types in these
rules to extend their functionality if required.
Caution: Before use, examine the rules closely to ensure you understand how they will
affect the traffic on your network.
All-Email, All-FTP, .These rules will detect all traffic of the specified type.
All-HTTP, All-IM, All-NNTP,
All-Session-Control
Email-AmEx, These four rules detect American Express numbers, Canadian Social
Email-Canada-SIN, Insurance Numbers, U.S. Social Security Numbers, or Visa and
Email-US-SSN, Mastercard numbers within the message bodies of SMTP, POP3, and
IMAP email traffic.
Email-Visa-Mastercard
HTTP-AmEx, These four rules detect American Express numbers, Canadian Social
HTTP-Canada-SIN, Insurance Numbers, U.S. Social Security Numbers, or Visa and
HTTP-US-SSN, Mastercard numbers within POST command in HTTP traffic. The
HTTP POST is used to send information to a web server.
HTTP-Visa-Mastercard
As written, these rules are designed to detect data the user is sending
to web servers. This rule does not detect the data retrieved with the
HTTP GET command, which is used to retrieve load web pages.
Email-Not-Webex, These rules prevent DLP from matching email or HTTP pages that
HTTP-Post-Not-Webex contain the string WebEx.
Large-Attachment This rule detects files larger than 5MB attached to SMTP, POP3, and
IMAP email messages.
Large-FTP-Put This rule detects files larger than 5MB sent using the FTP PUT
protocol. Files received using FTP GET are not examined.
Large-HTTP-Post This rule detects files larger than 5MB sent using the HTTP POST
protocol. Files received using HTTP GET are not examined.
Protocol Select the type of content traffic that the DLP rule the rule will apply to.
The available rule options vary depending on the protocol that you
select. You can select the following protocols: Email, HTTP, FTP,
NNTP, Instant Messaging and Session Control.
AIM, ICQ, MSN, Yahoo! When you select the Instant Messaging protocol, you can configure
the rule to apply to file transfers using any or all of the supported IM
protocols (AIM, ICQ, MSN, and Yahoo!).
Only file transfers using the IM protocols are subject to DLP rules. IM
messages are not scanned.
HTTP POST, HTTP GET When you select the HTTP protocol, you can configure the rule to
apply to HTTP post or HTTP get traffic or both.
HTTPS POST, HTTPS When you select the HTTP protocol, if your FortiGate unit supports
GET SSL content scanning and inspection, you can also configure the
HTTP rule to apply to HTTPS get or HTTPS post sessions or both. For
more information about SSL content scanning and inspection, see
“Configuring SSL content scanning and inspection” on page 472.
To scan these encrypted traffic types, you must set HTTPS Content
Filtering Mode to Deep Scan (Decrypt on SSL Traffic) in the Protocol
Recognition section of the protection profile. If URL Filtering is
selected, the DLP sensors will not scan HTTPS content.
FTP PUT, FTP GET When you select the FTP protocol, you can configure the rule to apply
to FTP put, or FTP get sessions or both.
SMTP, IMAP, POP3 When you select the Email protocol, you can configure the rule to
apply to any or all of the supported email protocols (SMTP, IMAP, and
POP3).
SMTPS IMAPS POP3S When you select the Email protocol, if your FortiGate unit supports
SSL content scanning and inspection, you can also configure the rule
to apply to SMTPS, IMAPS, POP3S or any combination of these
protocols.
For more information about SSL content scanning and inspection, see
“Configuring SSL content scanning and inspection” on page 472.
SIP, SIMPLE, SCCP When you select the Session Control protocol, you can configure the
rule to apply to any or all of the supported session control protocols
(SIP, SIMPLE, and SCCP). The only rule option for the session control
protocols is Always. This option matches all session control traffic is
used for session control DLP archiving.
File Options You can select file options for any protocol to configure how the DLP
rule handles archive files, MS-Word files, and PDF files found in
content traffic. File options appear when you select File Type rule
option.
Scan archive contents When selected, files within archives are extracted and scanned in the
same way as files that are not archived.
Scan archive files When selected, archives are scanned as a whole. The files within the
whole archive are not extracted and scanned individually.
Scan MS-Word text When selected the text contents of MS Word DOC documents are
extracted and scanned for a match. All metadata and binary
information is ignored.
Note: Office 2007/2008 DOCX files are not recognized as MS-Word
by the DLP scanner. To scan the contents of DOCX files, select the
Scan archive contents option.
Scan MS-Word file When selected, MS Word DOC files are scanned. All binary and
whole metadata information is included.
If you are scanning for text entered in a DOC file, use the
Scan MS-Word option. Binary formatting codes and file information
may appear within the text, causing text matches to fail.
Note: Office 2007/2008 DOCX files are not recognized as MS-Word
by the DLP scanner. To scan the contents of DOCX files, select the
Scan archive contents option.
Scan PDF text When selected, the text contents of PDF documents are extracted and
scanned for a match. All metadata and binary information is ignored.
Scan PDF file whole When selected, PDF files are scanned. All binary and metadata
information is included.
If you are scanning for text in PDF files, use the Scan PDF Text
option. Binary formatting codes and file information may appear within
the text, causing text matches to fail.
Rule Use the Rule settings to configure the content that the DLP rule
matches.
Always Match any content.
This option is available for all protocols.
Attachment size Check the attachment file size.
This option is available for Email.
Attachment type Search email messages for file types or file patterns as specified in the
selected file filter.
This option is available for Email.
Authenticated User Search for traffic from the specified authenticated user.
Binary file pattern Search for the specified binary string in network traffic.
Body Search for the specified string in the message or page body.
This option is available for Email, HTTP, and NNTP.
CGI parameters Search for the specified CGI parameters in any web page with CGI
code.
This option is available for HTTP.
Cookie Search the contents of cookies for the specified text.
This option is available for HTTP.
File is/not encrypted Check whether the file is or is not encrypted. Encrypted files are
archives and MS Word files protected with passwords. Because they
are password protected, the FortiGate unit cannot scan the contents
of encrypted files.
File text Search for the specified text in transferred text files.
This option is available in FTP, IM, and NNTP.
File type Search for the specified file patterns and file types. The patterns and
types configured in file filter lists and a list is selected in the DLP rule.
For more information about file filter lists, see “File Filter” on page 513.
This option is available for FTP, HTTP, IM, and NNTP.
Hostname Search for the specified host name when contacting a HTTP server.
HTTP header Search for the specified string in HTTP headers.
Receiver Search for the specified string in the message recipient email address.
This option is available for Email.
Sender Search for the specified string in the message sender user ID or email
address. This option is available for Email and IM.
For email, the sender is determined by the From: address in the email
header. For IM, all members of an IM session are senders and the
senders are determined by finding the IM user IDs in the session.
Server Search for the server’s IP address in a specified address range.
This option is available for FTP, NNTP.
Subject Search for the specified string in the message subject.
This option is available for Email.
Transfer size Check the total size of the information transfer. In the case of email
traffic for example, the transfer size includes the message header,
body, and any encoded attachment.
URL Search for the specified URL in HTTP traffic.
User group Search for traffic from any user in the specified user group.
Rule operators:
matches/does not match This operator specifies whether the FortiGate unit is searching for the
presence of specified string, or for the absence of the specified string.
• Matches: The rule will be triggered if the specified string is found in
network traffic.
• Does not match: The rule will be triggered if the specified string is
not found in network traffic.
ASCII/UTF-8 Select the encoding used for text files and messages.
Regular Select the means by which patterns are defined.
Expression/Wildcard For more information about wildcards and regular expressions, see
“Using wildcards and Perl regular expressions” on page 571
is/is not This operator specifies if the rule is triggered when a condition is true
or not true.
• Is: The rule will be triggered if the rule is true.
• Is not: The rule will be triggered if the rule is not true.
For example, if a rule specifies that a file type is found within a
specified file type list, all matching files will trigger the rule.
Conversely, if the rule specifies that a file type is not found in a file
type list, only the file types not in the list would trigger the rule.
==/>=/<=/!= These operators allow you to compare the size of a transfer or
attached file to an entered value.
• == is equal to the entered value.
• >= is greater than or equal to the entered value.
• <= is less than or equal to the entered value.
• != is not equal to the entered value.
Delete
Edit
Add Rule
Delete Rule
Protocol Select the type of content traffic that the DLP compound rule applies
to. The rules that you can add to the compound rule vary depending
on the protocol that you select. You can select the following protocols:
Email, HTTP, FTP, NNTP, and Instant Messaging.
AIM, ICQ, MSN, Yahoo! When you select the Instant Messaging protocol, you can select the
supported IM protocols for which to add rules. Only the rules that
include all of the selected protocols can be added to the compound
rule.
HTTP POST, HTTP GET When you select the HTTP protocol, you can configure the compound
rule to apply to HTTP post or HTTP get sessions or both. Only the
rules that include all of the selected options can be added to the
compound rule.
HTTPS POST, HTTPS When you select the HTTP protocol, if your FortiGate unit supports
GET SSL content scanning and inspection, you can configure the
compound rule to apply to HTTPS post or HTTPS get sessions or
both. Only the rules that include all of the selected options can be
added to the compound rule.
For more information about SSL content scanning and inspection, see
“Configuring SSL content scanning and inspection” on page 472.
To scan these encrypted traffic types, you must set HTTPS Content
Filtering Mode to Deep Scan (Decrypt on SSL Traffic) in the Protocol
Recognition section of the protection profile. If URL Filtering is
selected, the DLP sensors will not scan HTTPS content.
FTP PUT, FTP GET When you select the FTP protocol, you can configure the compound
rule to apply to FTP put, or FTP get sessions or both. Only the rules
that include all of the selected options can be added to the compound
rule.
SMTP, IMAP, POP3 When you select the Email protocol, you can select the supported
email protocols for which to add rules. Only the rules that include all of
the selected protocols can be added to the compound rule.
SMTPS IMAPS POP3S When you select the Email protocol, if your FortiGate unit supports
SSL content scanning and inspection, you can also select the SMTPS,
IMAPS, POP3S protocols. Only the rules that include all of the
selected protocols can be added to the compound rule.
For more information about SSL content scanning and inspection, see
“Configuring SSL content scanning and inspection” on page 472.
Rules Select the rule to include in the compound rule. Only the rules that
include all of the selected protocols can be added to the compound
rule.
Add Rule/Delete Rule Use the add rule and delete rule icons to add and remove rules from
the compound rule. Select the add rule icon and then select rule from
the list.
Application Control
This section describes how to configure the application control options associated with
firewall protection profiles.
If you enable virtual domains (VDOMs) on the FortiGate unit, the application control
configuration of each VDOM is entirely separate. For example, application black/white lists
created in one VDOM will not be visible in other VDOMs. For details, see “Using virtual
domains” on page 125.
This section provides an introduction to configuring application control. For more
information see the FortiGate UTM User Guide.
This section describes:
• What is application control?
• FortiGuard application control database
• Viewing the application control black/white lists
• Creating a new application control black/white list
• Configuring an application control black/white list
• Adding or configuring an application control black/white list entry
• Application control statistics
Create New Select Create New to add a new application control black/white list.
Name The available application control black/white lists.
# of Entries The number of application rules in each application control black/white
list.
Profiles The protection profile each application control black/white list has
been applied to. If the black/white list has not been applied to a
protection profile, this field will be blank.
Comment An optional description of each application control black/white list.
Delete icon Select to remove the application control black/white list. The delete
icon is only available if the application control black/white list is not
selected in any protection profiles.
Edit icon Select to edit the application control black/white list.
Figure 361: The create a new application control black/white list dialog window
Figure 363: The application control black/white list entry for FTP
In addition to these option, some IM applications and VoIP protocols have additional
options:
IM options
Block Login Select to prevent users from logging in to the selected IM system.
Block File Transfers Select to prevent the sending and receiving of files using the selected
IM system.
Block Audio Select to prevent audio communication using the selected IM system.
Inspect Non-standard Select to allow the FortiGate unit to examine non-standard ports for
Port the IM client traffic.
Display content meta- Select to include meta-information detected for the IM system on the
information on the FortiGate unit dashboard.
system dashboard
VoIP options
Limit Call Setup Enter the maximum number of calls each client can set up per minute.
Limit REGISTER Enter the maximum number of register requests per second allowed
request for the firewall policy.
Limit INVITE request Enter the maximum number of invite requests per second allowed for
the firewall policy.
Enable Logging of Select to enable logging of violations.
Violations
Other options
Command Some of traffic types include a command option. Specify a command
that appears in the traffic that you want to block or pass.
For example, enter GET as a command in the FTP.Command
application to have the FortiGate unit examine FTP traffic for the GET
command. Multiple commands can be entered.
Method A method option is available for HTTP, RTSP, and SIP protocols.
Specify a method that appears in the traffic that you want to block or
pass.
For example, enter POST as a method in the HTTP.Method application
to have the FortiGate unit examine HTTP traffic for the POST method.
Multiple methods can be entered.
Program Number Enter the program number appearing in Sun Remote Procedure Calls
(RPC) that you want to block or pass. Multiple program numbers can
be entered.
UUID Enter the UUID appearing in Microsoft Remote Procedure Calls
(MSRPC) that you want to block or pass. Multiple UUIDs can be
entered.
Automatic Refresh Select the automatic refresh interval for statistics. Set the interval from
Interval none to 30 seconds.
Refresh Click to refresh the page with the latest statistics.
Reset Stats Click to reset the statistics to zero.
IPSec VPN
This section provides information about Internet Protocol Security (IPSec) VPN
configuration options available through the web-based manager. FortiGate units support
both policy-based (tunnel-mode) and route-based (interface mode) VPNs.
Note: For information about how to configure an IPSec VPN, see the FortiGate IPSec VPN
User Guide.
If you enable virtual domains (VDOMs) on the FortiGate unit, VPN IPSec is configured
separately for each virtual domain. For details, see “Using virtual domains” on page 125.
This section describes:
• Overview of IPSec VPN configuration
• Policy-based versus route-based VPNs
• Auto Key
• Manual Key
• Internet browsing configuration
• Concentrator
• Monitoring VPNs
Note: You must use steps 1 and 2 if you want the FortiGate unit to generate unique
IPSec encryption and authentication keys automatically. If a remote VPN peer or client
requires a specific IPSec encryption or authentication key, you must configure the
FortiGate unit to use manual keys instead. For more information, see “Manual Key” on
page 614.
3 Create a firewall policy to permit communication between your private network and the
VPN. For a policy-based VPN, the firewall policy action is IPSEC. For an interface-
based VPN, the firewall policy action is ACCEPT. See “Configuring firewall policies” on
page 367.
For more information about configuring IPSec VPNs, see the FortiGate IPSec VPN User
Guide.
Policy-based Route-based
Available in NAT/Route or Transparent Available only in NAT/Route mode
mode
Requires a firewall policy with IPSEC Requires only a simple firewall policy with
action that specifies the VPN tunnel. One ACCEPT action. A separate policy is required
policy controls connections in both for connections in each direction.
directions.
You create a policy-based VPN by defining an IPSEC firewall policy between two network
interfaces and associating it with the VPN tunnel (phase 1 or manual key) configuration.
You need only one firewall policy, even if either end of the VPN can initiate a connection.
You create a route-based VPN by enabling IPSec interface mode when you create the
VPN phase 1 or manual key configuration. This creates a virtual IPSec interface that is
bound to the local interface you selected. You then define an ACCEPT firewall policy to
permit traffic to flow between the virtual IPSec interface and another network interface. If
either end of the VPN can initiate the connection, you need two firewall policies, one for
each direction.
Virtual IPSec interface bindings are shown on the network interfaces page. (Go to System
> Network > Interface.) The names of all tunnels bound to physical, aggregate, VLAN,
inter-VDOM link or wireless interfaces are displayed under their associated interface
names in the Name column. For more information, see “Configuring interfaces” on
page 145. As with other interfaces, you can include a virtual IPSec interface in a zone.
Hub-and-spoke configurations
To function as the hub of a hub-and-spoke VPN, the FortiGate unit provides a
concentrator function. This is available only for policy-based VPNs, but you can create the
equivalent function for a route-based VPN in any of the following ways:
• Define a firewall policy between each pair of IPSec interfaces that you want to
concentrate. This can be time-consuming to maintain if you have many site-to-site
connections, since the number of policies required increases rapidly as the number of
spokes increases.
• Put all the IPSec interfaces into a zone and then define a single zone-to-zone policy.
• Put all the IPSec interfaces in a zone and enable intra-zone traffic. There must be more
than one IPSec interface in the zone.
For more information and an example, see the FortiGate IPSec VPN User Guide.
Redundant configurations
Route-based VPNs help to simplify the implementation of VPN tunnel redundancy. You
can configure several routes for the same IP traffic with different route metrics. You can
also configure the exchange of dynamic (RIP, OSPF, or BGP) routing information through
VPN tunnels. If the primary VPN connection fails or the priority of a route changes through
dynamic routing, an alternative route will be selected to forward traffic through the
redundant connection.
A simple way to provide failover redundancy is to create a backup IPSec interface. You
can do this in the CLI. For more information, including an example configuration, see the
monitor-phase1 keyword for the ipsec vpn phase1-interface command in the
FortiGate CLI Reference.
Routing
Optionally, through the CLI, you can define a specific default route for a virtual IPSec
interface. For more information, see the default-gw keyword for the
vpn ipsec phase1-interface command in the FortiGate CLI Reference.
Auto Key
You can configure two VPN peers (or a FortiGate dialup server and a VPN client) to
generate unique Internet Key Exchange (IKE) keys automatically during the IPSec
phase 1 and phase 2 exchanges.
When you define phase 2 parameters, you can choose any set of phase 1 parameters to
set up a secure connection for the tunnel and authenticate the remote peer.
Auto Key configuration applies to both tunnel-mode and interface-mode VPNs.
To configure an Auto Key VPN, go to VPN > IPSEC > Auto Key (IKE).
Edit
Delete
Create Phase 1 Create a new phase 1 tunnel configuration. For more information, see
“Creating a new phase 1 configuration” on page 606.
Create Phase 2 Create a new phase 2 configuration. For more information, see “Creating a
new phase 2 configuration” on page 611.
Phase 1 The names of existing phase 1 tunnel configurations.
Phase 2 The names of existing phase 2 configurations.
Interface Binding The names of the local interfaces to which IPSec tunnels are bound. These
can be physical, aggregate, VLAN, inter-VDOM link or wireless interfaces.
Delete and Edit icons Delete or edit a phase 1 configuration.
Local Interface This option is available in NAT/Route mode only. Select the name of
the interface through which remote peers or dialup clients connect to
the FortiGate unit.
By default, the local VPN gateway IP address is the IP address of
the interface that you selected. Optionally, you can specify a unique
IP address for the VPN gateway in the Advanced settings. For more
information, see “Local Gateway IP” on page 609.
Mode Select Main or Aggressive:
• In Main mode, the phase 1 parameters are exchanged in multiple
rounds with encrypted authentication information.
• In Aggressive mode, the phase 1 parameters are exchanged in
single message with authentication information that is not
encrypted.
When the remote VPN peer has a dynamic IP address and is
authenticated by a pre-shared key, you must select Aggressive
mode if there is more than one dialup phase1 configuration for the
interface IP address.
When the remote VPN peer has a dynamic IP address and is
authenticated by a certificate, you must select Aggressive mode if
there is more than one phase 1 configuration for the interface IP
address and these phase 1 configurations use different proposals.
Peer Options settings may require a particular mode. See Peer
Options, below.
Authentication Method Select Preshared Key or RSA Signature.
Pre-shared Key If you selected Pre-shared Key, type the pre-shared key that the
FortiGate unit will use to authenticate itself to the remote peer or
dialup client during phase 1 negotiations. You must define the same
value at the remote peer or client. The key must contain at least 6
printable characters and should be known only by network
administrators. For optimum protection against currently known
attacks, the key should consist of a minimum of 16 randomly chosen
alphanumeric characters.
Certificate Name If you selected RSA Signature, select the name of the server
certificate that the FortiGate unit will use to authenticate itself to the
remote peer or dialup client during phase 1 negotiations. For
information about obtaining and loading the required server
certificate, see the FortiGate Certificate Management User Guide.
Peer Options One or more of the following options are available to authenticate
VPN peers or clients, depending on the Remote Gateway and
Authentication Method settings.
Accept any peer ID Accept the local ID of any remote VPN peer or client. The FortiGate
unit does not check identifiers (local IDs). You can set Mode to
Aggressive or Main.
You can use this option with RSA Signature authentication. But, for
highest security, you should configure a PKI user/group for the peer
and set Peer Options to Accept this peer certificate only.
Accept this peer ID This option is available only if the remote peer has a dynamic IP
address. Enter the identifier that is used to authenticate the remote
peer. This identifier must match the identifier that the remote peer’s
administrator has configured.
If the remote peer is a FortiGate unit, the identifier is specified in the
Local ID field of the phase 1 configuration.
If the remote peer is a FortiClient dialup client, the identifier is
specified in the Local ID field, accessed by selecting Config in the
Policy section of the VPN connection’s Advanced Settings.
Accept peer ID in dialup Authenticate multiple FortiGate or FortiClient dialup clients that use
group unique identifiers and unique pre-shared keys (or unique pre-shared
keys only) through the same VPN tunnel.
You must create a dialup user group for authentication purposes.
(For more information, see “User Group” on page 658.) Select the
group from the list next to the Accept peer ID in dialup group option.
For more information about configuring FortiGate dialup clients, see
the FortiGate IPSec VPN User Guide. For more information about
configuring FortiClient dialup clients, see the Authenticating
FortiClient Dialup Clients Technical Note.
You must set Mode to Aggressive when the dialup clients use unique
identifiers and unique pre-shared keys. If the dialup clients use
unique pre-shared keys only, you can set Mode to Main if there is
only one dialup phase 1 configuration for this interface IP address.
Accept this peer This option is available when Authentication Method is set to
certificate only RSA Signature.
Authenticate remote peers or dialup clients that use a security
certificate. Select the certificate from the list next to the option.
You must add peer certificates to the FortiGate configuration before
you can select them here. For more information, see “PKI” on
page 656.
Accept this peer This option is available when Authentication Method is set to
certificate group only RSA Signature and Remote Gateway is set to Dialup User.
Use a certificate group to authenticate dialup clients that have
dynamic IP addresses and use unique certificates.
Select the name of the peer group from the list. You must first create
the group through the config user peergrp CLI command
before you can select it. For more information, see the “user” chapter
of the FortiGate CLI Reference. Members of the peer group must be
certificates added by using the config user peer CLI command.
You can also add peer certificates using the web-based manager.
For more information, see “PKI” on page 656.
Advanced Define advanced phase 1 parameters. For more information, see
“Defining phase 1 advanced settings” on page 608.
Add
Delete
Add
Delete
P2 Proposal Select the encryption and authentication algorithms that will be proposed to
the remote VPN peer. You can specify up to three proposals. To establish a
VPN connection, at least one of the proposals that you specify must match
configuration on the remote peer.
Initially there are two proposals. Add and Delete icons are next to the
second Authentication field. To specify only one proposal, select Delete to
remove the second proposal. To specify a third proposal, select Add.
It is invalid to set both Encryption and Authentication to NULL.
Encryption Select one of the following symmetric-key algorithms:
NULL — Do not use an encryption algorithm.
DES — Digital Encryption Standard, a 64-bit block algorithm that uses a 56-
bit key.
3DES — Triple-DES, in which plain text is encrypted three times by three
keys.
AES128 — a 128-bit block Cipher Block Chaining (CBC) algorithm that uses
a 128-bit key.
AES192 — a 128-bit block Cipher Block Chaining (CBC) algorithm that uses
a 192-bit key.
AES256 — a 128-bit block Cipher Block Chaining (CBC) algorithm that uses
a 256-bit key.
Authentication Select one of the following message digests to check the authenticity of
messages during an encrypted session:
NULL — Do not use a message digest.
MD5 — Message Digest 5, the hash algorithm developed by RSA Data
Security.
SHA1 — Secure Hash Algorithm 1, which produces a 160-bit message
digest.
SHA256 — Secure Hash Algorithm 2, which produces a 256-bit message
digest.
Enable replay Optionally enable or disable replay detection. Replay attacks occur when an
detection unauthorized party intercepts a series of IPSec packets and replays them
back into the tunnel.
Enable perfect Enable or disable PFS. Perfect forward secrecy (PFS) improves security by
forward secrecy forcing a new Diffie-Hellman exchange whenever keylife expires.
(PFS)
DH Group Select one Diffie-Hellman group (1, 2, 5 or 14). This must match the DH
Group that the remote peer or dialup client uses.
Keylife Select the method for determining when the phase 2 key expires: Seconds,
KBytes, or Both. If you select Both, the key expires when either the time has
passed or the number of KB have been processed. The range is from 120 to
172 800 seconds, or from 5120 to 2 147 483 648 KB.
Autokey Keep Alive Select the check box if you want the tunnel to remain active when no data is
being processed.
DHCP-IPSec Provide IP addresses dynamically to VPN clients. This is available for
phase 2 configurations associated with a dialup phase 1 configuration.
You also need configure a DHCP server or relay on the private network
interface. You must configure the DHCP parameters separately. For more
information, see “System DHCP” on page 199.
If you configure the DHCP server to assign IP addresses based on RADIUS
user group attributes, you must also set the Phase 1 Peer Options to Accept
peer ID in dialup group and select the appropriate user group. See “Creating
a new phase 1 configuration” on page 606.
If the FortiGate unit acts as a dialup server and you manually assigned
FortiClient dialup clients VIP addresses that match the network behind the
dialup server, selecting the check box will cause the FortiGate unit to act as
a proxy for the dialup clients.
Note: You can configure settings so that VPN users can browse the Internet through the
FortiGate unit. For more information, see “Internet browsing configuration” on page 616.
Quick Mode Optionally specify the source and destination IP addresses to be used as selectors
Selector for IKE negotiations. If the FortiGate unit is a dialup server, you should keep the
default value 0.0.0.0/0 unless you need to circumvent problems caused by
ambiguous IP addresses between one or more of the private networks making up
the VPN. You can specify a single host IP address, an IP address range, or a
network address. You may optionally specify source and destination port numbers
and a protocol number.
If you are editing an existing phase 2 configuration, the Source address and
Destination address fields are unavailable if the tunnel has been configured to use
firewall addresses as selectors. This option exists only in the CLI. For more
information, see the dst-addr-type, dst-name, src-addr-type and src-
name keywords for the vpn ipsec phase2 command in the FortiGate CLI
Reference.
Source address If the FortiGate unit is a dialup server, type the source IP
address that corresponds to the local senders or network
behind the local VPN peer (for example, 172.16.5.0/24 or
172.16.5.0/255.255.255.0 for a subnet, or
172.16.5.1/32 or 172.16.5.1/255.255.255.255 for a
server or host, or 192.168.10.[80-100] or
192.168.10.80-192.168.10.100 for an address range).
A value of 0.0.0.0/0 means all IP addresses behind the
local VPN peer.
If the FortiGate unit is a dialup client, source address must
refer to the private network behind the FortiGate dialup client.
Source port Type the port number that the local VPN peer uses to
transport traffic related to the specified service (protocol
number). The range is from 0 to 65535. To specify all ports,
type 0.
Destination Type the destination IP address that corresponds to the
address recipients or network behind the remote VPN peer (for
example, 192.168.20.0/24 for a subnet, or
172.16.5.1/32 for a server or host, or 192.168.10.[80-
100] for an address range). A value of 0.0.0.0/0 means all
IP addresses behind the remote VPN peer.
Destination port Type the port number that the remote VPN peer uses to
transport traffic related to the specified service (protocol
number). The range is from 0 to 65535. To specify all ports,
type 0.
Protocol Type the IP protocol number of the service. The range is from
0 to 255. To specify all services, type 0.
Manual Key
If required, you can manually define cryptographic keys for establishing an IPSec VPN
tunnel. You would define manual keys in situations where:
• You require prior knowledge of the encryption or authentication key (that is, one of the
VPN peers requires a specific IPSec encryption or authentication key).
• You need to disable encryption and authentication.
In both cases, you do not specify IPSec phase 1 and phase 2 parameters; you define
manual keys by going to VPN > IPSEC > Manual Key instead.
Note: You should use manual keys only if it is unavoidable. There are potential difficulties in
keeping keys confidential and in propagating changed keys to remote VPN peers securely.
For general information about how to configure an IPSec VPN, see the FortiGate IPSec
VPN User Guide.
Delete
Edit
Create New Create a new manual key configuration. See “Creating a new manual key
configuration” on page 614.
Tunnel Name The names of existing manual key configurations.
Remote Gateway The IP addresses of remote peers or dialup clients.
Encryption Algorithm The names of the encryption algorithms specified in the manual key
configurations.
Authentication The names of the authentication algorithms specified in the manual key
Algorithm configurations.
Delete and Edit icons Delete or edit a manual key configuration.
Caution: If you are not familiar with the security policies, SAs, selectors, and SA databases
for your particular installation, do not attempt the following procedure without qualified
assistance.
To specify manual keys for creating a tunnel, go to VPN > IPSEC > Manual Key and
select Create New.
Name Type a name for the VPN tunnel. The maximum name length is 15 characters
for an interface mode VPN, 35 characters for a policy-based VPN.
Local SPI Type a hexadecimal number (up to 8 characters, 0-9, a-f) that represents the
SA that handles outbound traffic on the local FortiGate unit. The valid range is
from 0x100 to 0xffffffff. This value must match the Remote SPI value in
the manual key configuration at the remote peer.
Remote SPI Type a hexadecimal number (up to 8 characters, 0-9, a-f) that represents the
SA that handles inbound traffic on the local FortiGate unit. The valid range is
from 0x100 to 0xffffffff. This value must match the Local SPI value in
the manual key configuration at the remote peer.
Remote Gateway Type the IP address of the public interface to the remote peer. The address
identifies the recipient of ESP datagrams.
Local Interface This option is available in NAT/Route mode only. Select the name of the
interface to which the IPSec tunnel will be bound. The FortiGate unit obtains
the IP address of the interface from the network interface settings. For more
information, see “Configuring interfaces” on page 145.
Encryption Select one of the following symmetric-key encryption algorithms:
Algorithm DES — Digital Encryption Standard, a 64-bit block algorithm that uses a 56-
bit key.
3DES — Triple-DES, in which plain text is encrypted three times by three
keys.
AES128 — a 128-bit block Cipher Block Chaining (CBC) algorithm that uses
a 128-bit key.
AES192 — a 128-bit block Cipher Block Chaining (CBC) algorithm that uses
a 192-bit key.
AES256 — a 128-bit block Cipher Block Chaining (CBC) algorithm that uses
a 256-bit key.
Note: The algorithms for encryption and authentication cannot both be NULL.
Encryption Key Enter an encryption key appropriate to the encryption algorithm:
• for DES, type a 16-character hexadecimal number (0-9, a-f).
• for 3DES, type a 48-character hexadecimal number (0-9, a-f) separated
into three segments of 16 characters.
• for AES128, type a 32-character hexadecimal number (0-9, a-f) separated
into two segments of 16 characters.
• for AES192, type a 48-character hexadecimal number (0-9, a-f) separated
into three segments of 16 characters.
• for AES256, type a 64-character hexadecimal number (0-9, a-f) separated
into four segments of 16 characters.
Concentrator
In a hub-and-spoke configuration, policy-based VPN connections to a number of remote
peers radiate from a single, central FortiGate unit. Site-to-site connections between the
remote peers do not exist; however, You can establish VPN tunnels between any two of
the remote peers through the FortiGate unit “hub”.
In a hub-and-spoke network, all VPN tunnels terminate at the hub. The peers that connect
to the hub are known as “spokes”. The hub functions as a concentrator on the network,
managing all VPN connections between the spokes. VPN traffic passes from one tunnel to
the other through the hub.
You define a concentrator to include spokes in the hub-and-spoke configuration.
To define a concentrator, go to VPN > IPSEC > Concentrator. For detailed information and
step-by-step procedures about how to set up a hub-and-spoke configuration, see the
FortiGate IPSec VPN User Guide.
Delete
Edit
Create New Define a new concentrator for an IPSec hub-and-spoke configuration. For
more information, see “Defining concentrator options” on page 617.
Concentrator Name The names of existing IPSec VPN concentrators.
Members The tunnels that are associated with the concentrators.
Delete and Edit Delete or edit a concentrator.
icons
Right Arrow
Left Arrow
Monitoring VPNs
You can use the IPSec monitor to view activity on IPSec VPN tunnels and start or stop
those tunnels. The display provides a list of addresses, proxy IDs, and timeout information
for all active tunnels, including tunnel mode and route-based (interface mode) tunnels.
You can use filters to control the information displayed in the list. For more information,
see “Adding filters to web-based manager lists” on page 57.
To view active tunnels, go to VPN > IPSec > Monitor.
Current Page
Type Select the types of VPN to display: “All”, “Dialup”, or “Static IP or Dynamic DNS”.
Column Customize the table view. You can select the columns to hide or display and
Settings specify the column displaying order in the table. For more information, see “Using
column settings to control the columns displayed” on page 61 and “Web-based
manager icons” on page 63.
Clear All Filters Select to clear any column display filters you might have applied.
Current Page The current page number of list items that are displayed. Select the left and right
arrows to display the first, previous, next or last page of monitored VPNs.
Filter icons Edit the column filters to filter or sort the IPSec monitor list according to the
criteria you specify. For more information, see “Adding filters to web-based
manager lists” on page 57.
Name The name of the phase 1 configuration for the VPN.
Remote The public IP address of the remote host device, or if a NAT device exists in front
Gateway of the remote host, the public IP address of the NAT device.
Remote Port The UDP port of the remote host device, or if a NAT device exists in front of the
remote host, the UDP port of the NAT device. Zero (0) indicates that any port can
be used.
Proxy ID Source The IP addresses of the hosts, servers, or private networks behind the FortiGate
unit. The page may display a network range if the source address in the firewall
encryption policy was expressed as a range of IP addresses.
Proxy ID When a FortiClient dialup client establishes a tunnel:
Destination • If VIP addresses are not used, the Proxy ID Destination field displays the
public IP address of the remote host Network Interface Card (NIC).
• If VIP addresses were configured (manually or through FortiGate DHCP
relay), the Proxy ID Destination field displays either the VIP address belonging
to the FortiClient dialup client, or the subnet address from which VIP
addresses were assigned.
When a FortiGate dialup client establishes a tunnel, the Proxy ID Destination field
displays the IP address of the remote private network.
Tunnel up or A green arrow means the tunnel is currently processing traffic. Select to bring
tunnel down down the tunnel.
icon A red arrow means the tunnel is not processing traffic. Select to bring up the
tunnel.
For Dialup VPNs, the list provides status information about the VPN tunnels established
by dialup clients, including their IP addresses. The number of tunnels shown in the list can
change as dialup clients connect and disconnect.
For Static IP or dynamic DNS VPNs, the list provides status and IP addressing information
about VPN tunnels, active or not, to remote peers that have static IP addresses or domain
names. You can also start and stop individual tunnels from the list.
PPTP VPN
FortiGate units support PPTP to tunnel PPP traffic between two VPN peers. Windows or
Linux PPTP clients can establish a PPTP tunnel with a FortiGate unit that has been
configured to act as a PPTP server. As an alternative, you can configure the FortiGate unit
to forward PPTP packets to a PPTP server on the network behind the FortiGate unit.
PPTP VPN is available only in NAT/Route mode. The current maximum number of PPTP
sessions is 254. If you enable virtual domains (VDOMs) on the FortiGate unit, you need to
configure VPN PPTP separately for each virtual domain. For more information, see “Using
virtual domains” on page 125.
When you intend to use the FortiGate unit as a PPTP gateway, you can select a PPTP
client IP from a local address range or use the server defined in the PPTP user group. You
select which method to use for IP address retrieval and, in the case of the user group
server, provide the IP address and the user group.
This section explains how to specify a range of IP addresses for PPTP clients or configure
the PPTP client-side IP address to be used in the tunnel setup. For information about how
to perform other related PPTP VPN setup tasks, see the FortiGate PPTP VPN User
Guide.
Note: The PPTP feature is disabled by default in the FortiGate web-based manager. You
configure the PPTP tunnel configuration by creating a customized FortiGate screen.
For information about creating customized screens in the FortiGate web-based manager,
see “Customizable web-based manager” on page 268.
PPTP requires two IP addresses, one for each end of the tunnel. The PPTP address
range is the range of addresses reserved for remote PPTP clients. When the remote
PPTP client establishes a connection, the FortiGate unit assigns an IP address from the
reserved range of IP addresses to the client PPTP interface or retrieves the assigned IP
address from the PPTP user group. If you use the PPTP user group, you must also define
the FortiGate end of the tunnel by entering the IP address of the unit in Local IP (web-
based manager) or local-ip (CLI). The PPTP client uses the assigned IP address as its
source address for the duration of the connection.
To enable PPTP and specify the PPTP address range or specify the IP address for the
peer’s remote IP on the PPTP client side, go to the customized screen in the web-based
manager, select the required options, and then select Apply.
Note: The start and end IPs in the PPTP address range must be in the same 24-bit subnet,
e.g. 192.168.1.1 - 192.168.1.254.
Figure 376: Edit PPTP range options, showing both Range and User Group
Enable PPTP Enable PPTP. You must add a user group before you can select the
option. See “User Group” on page 658.
IP Mode Select how PPTP users are assigned an IP address.
Range User’s IP addresses are assigned from the range of IP addresses
configured by Starting IP and Ending IP.
User Group User’s IP addresses are assigned by the user group used to
authenticate the user. Select the user group. See “Dynamically
assigning VPN client IP addresses from a user group” on page 665.
Starting IP Type the starting address in the range of reserved IP addresses.
Ending IP Type the ending address in the range of reserved IP addresses.
Local IP Type the IP address to be used for the peer’s remote IP on the PPTP
client side.
User Group Select the PPTP user group from the list.
Disable PPTP Select to disable PPTP support.
Syntax
config vpn pptp
set eip <address_ipv4>
set ip-mode {range | usrgrp}
set local-ip <address_localip>
set sip <address_ipv4>
set status {disable | enable}
set usrgrp <group_name>
end
Variables Description Default
eip <address_ipv4> The ending address of the PPTP address range. 0.0.0.0
SSL VPN
An SSL VPN (Secure Sockets Layer virtual private network) is a form of VPN that can be
used with a standard Web browser. SSL VPN does not require the installation of
specialized client software on end users’ computers, and is ideal for applications including
web-based email, business and government directories, file sharing, remote backup,
remote system management, and consumer-level electronic commerce.
The two modes of SSL VPN operation (supported in NAT/Route mode only) are:
• web-only mode, for thin remote clients equipped with a web-browser only.
• tunnel mode, for remote computers that run a variety of client and server applications.
When the FortiGate unit provides services in web-only mode, a secure connection
between the remote client and the FortiGate unit is established through the SSL VPN
security in the FortiGate unit and the SSL security in the web browser. After the
connection has been established, the FortiGate unit provides access to selected services
and network resources through a web portal. The FortiGate SSL VPN web portal has a
widget-based layout with customizable themes. Each widget is displayed in a 1- or 2-
column format with the ability to modify settings, minimize the widget window, or other
functions depending on the type of content within the widget.
When users have complete administrative rights over their computers and use a variety of
applications, tunnel mode allows remote clients to access the local internal network as if
they were connected to the network directly.
This section provides information about the features of SSL VPN available for
configuration in the web-based manager. Only FortiGate units that run in NAT/Route mode
support the SSL VPN feature.
If you enable virtual domains (VDOMs) on the FortiGate unit, VPN SSL is configured
separately for each virtual domain. For details, see “Using virtual domains” on page 125.
Note: For detailed instructions about how to configure web-only mode or tunnel-mode
operation, see the FortiGate SSL VPN User Guide.
ssl.root
The FortiGate unit has a virtual SSL VPN interface called ssl.<vdomname>. The root
VDOM, called ssl.root, appears in the firewall policy interface lists and static route
interface lists. You can use the ssl-root interface to allow access to additional networks
and facilitate a connected user’s ability to browse the Internet through the FortiGate unit.
SSL VPN tunnel-mode access requires the following firewall policies:
• External > Internal, with the action set to SSL, with an SSL user group
• ssl.root > Internal, with the action set to Accept
• Internal > ssl.root, with the action set to Accept.
Access also requires a new static route: Destination network - <ssl tunnel mode assigned
range> interface ssl.root.
If you are configuring Internet access through an SSL VPN tunnel, you must add the
following configuration: ssl.root > External, with the action set to Accept, NAT enabled.
Note: If required, you can enable SSL version 2 encryption (for compatibility with older
browsers) through a FortiGate CLI command. For more information, see the ssl
settings command in the FortiGate CLI Reference.
To enable SSL VPN connections and configure SSL VPN settings, go to VPN > SSL >
Config and select Enable SSL-VPN. When you have completed configuring the settings,
select Apply.
Enable Virtual Desktop Enable the virtual desktop and the following settings. If this is
not enabled, user has browser access on the regular desktop.
Allow switching between By default, the regular desktop is not accessible while the
virtual desktop and regular virtual desktop is active. With this option enabled, user can
desktop switch between them.
Allow clipboard contents to Enable to allow cut-and-paste operations between the virtual
be shared with regular desktop and the regular desktop.
desktop
Allow use of removable Enable to allow the user to copy files between the virtual
media desktop and removable media such as USB drives.
Allow network share access Enable to allow the user to copy files between the virtual
desktop and network drives.
Allow printing Enable to allow the user to use printers from the virtual
desktop.
Quit the virtual desktop and By default, the virtual desktop remains in effect even if the user
logout session when closes the browser. Enable to automatically close the virtual
browser is closed desktop and logout if the user closes the browser.
Application Control List Optionally, select an application control list. This controls which
applications the user can run on the virtual desktop. See
“Virtual Desktop Application Control”.
6 Select OK.
7 Select Apply.
Clean Cache Enable to clear client cache when the SSL VPN session ends.
Host Check Select the type of host checking to use.
AV Check for antivirus software recognized by the Windows Security Center.
AV-FW Check for both antivirus and firewall software recognized by the Windows
Security Center.
Custom Check for the security software listed in the Policy field.
FW Check for firewall software recognized by the Windows Security Center.
None Do not perform host checking.
Interval Select how often to recheck the host. Range is every 120 seconds to 259 200
seconds. Enter 0 to not recheck the host during the session.
Policy The list of acceptable security applications for clients. These application names
are from the Host Check list. This field is available if Host Check is Custom.
Select Edit to choose the host check applications to use. Use the arrow buttons
to move applications between the Available and Selected lists. Clients will be
checked for the applications in the Selected list. Select OK.
5 Select OK.
Figure 381: SSL VPN web portal - full-access Default configuration window
OK Select to save the configuration. If you select OK, you exit out of the
SSL VPN web portal configuration window.
Cancel Select to exit the configuration window without saving any changes.
Apply Select to apply any changes made in the web portal configuration. If
you select Apply, you will not leave the portal configuration window.
Settings Select to edit the General or Advanced settings for the SSL VPN web
portal. See “SSL VPN web portal” on page 627.
Help Indicates the location of the SSL VPN web portal online help icon. You
cannot change or move this icon. Active when SSL VPN web portal is
activated by user.
Log out Indicates the location of the SSL VPN web portal log out icon. You
cannot change or move this icon. Active when SSL VPN web portal is
activated by user.
Add Widget list Select to add a widget to the SSL VPN web portal configuration.
Session Information Displays the login name of the user, the amount of time the user has
been logged in, and the inbound and outbound traffic of HTTP and
HTTPS.
Bookmarks Displays configured bookmarks, allows for the addition of new
bookmarks and editing of existing bookmarks.
Connection Tool Enter the URL or IP address for a connection tool application/server
(selected when configuring the Connection Tool). You can also check
connectivity to a host or server on the network behind the FortiGate
unit by selecting the Type Ping.
Tunnel Mode Displays tunnel information and actions in user mode. The
administrator can configure a split-tunneling option.
Remove widget
Edit
Bookmarks widget
Bookmarks are used as links to specific resources on the network. When a bookmark is
selected from a bookmark list, a pop-up window appears with the requested web page.
Telnet, VNC, and RDP all pop up a window that requires a browser plug-in. FTP and
Samba replace the bookmarks page with an HTML file-browser.
A web bookmark can include login credentials to automatically log the SSL VPN user into
the web site. This means that once the user logs into the SSL VPN, he or she does not
have to enter any more credentials to visit preconfigured web sites. When the
administrator configures bookmarks, the web site credentials must be the same as the
user’s SSL VPN credentials. Users configuring their own bookmarks can specify
alternative credentials for the web site.
Value Enter the value to enter in the field identified by Field Name.
If you are an administrator configuring a bookmark for users:
• Enter %usrname% to represent the user’s SSL VPN user name.
• Enter %passwd% to represent the user’s SSL VPN password.
Add Enter another Field Name / Value pair, for the password, for example.
A new set of Field Name / Value fields is added. Fill them in.
4 Select OK.
5 If there is a Done button, you can select another bookmark to edit or select Done to
leave the edit mode.
6 Select Apply at the top of the web portal page to save the changes that you made.
Add bookmark
window
Select OK
Bookmark
added
Select Delete
bookmark bookmark
to edit
Bookmark
detail
window
Select
OK
Select
Done
Bookmarks
widget with
list of bookmarks
To delete bookmarks
1 Open the web portal.
2 In the Bookmarks widget, select the Edit button.
3 Select the X to the right of the bookmark that you want to delete.
4 Select Done.
3 In the Connection Tool widget select the Edit icon in the widget title bar.
4 Enter the following information:
Name Optionally, enter a customized name for the Connection Tool widget.
Applications Select the types of server applications or network services that will be available
to users through the Connection Tool widget.
Type Select the server/application that the FortiGate unit will use to establish a
connection.
5 Select OK.
Name Enter a name for the Tunnel Mode widget. The default is “Tunnel Mode”.
IP Mode Select the mode by which the IP address is assigned to the user.
Range The user IP address is allocated from the IP addresses specified in
IP Pools. If IP Pools is empty, the IP Pools specified in VPN > SSL > Config
are used.
User Group The user is assigned the IP address specified in the Framed-IP-Address
field of the user’s record on the RADIUS server. This option is valid only for
users authenticated by a RADIUS server.
IP Pools Select Edit to select the range or subnet firewall addresses that represent
IP address ranges reserved for tunnel-mode SSL VPN clients. If the
appropriate addresses do not exist, go to Firewall > Address to create them.
You cannot add the all firewall address or a FQDN firewall address. You
also cannot add an address group that includes the all firewall address or a
FQDN address.
Split tunneling Select to enable split tunneling. In a split tunneling configuration, the tunnel
mode client uses the SSL VPN only for traffic destined for the networks
behind the FortiGate unit. The user’s other traffic follows its normal route.
The remaining items in the widget are available to the user during an SSL VPN
session.
Remove widget
Edit
Connect Initiate a session and establish an SSL VPN tunnel with the FortiGate unit.
Disconnect End the session and close the tunnel to the FortiGate unit.
Refresh now Refresh the Fortinet SSL VPN Client page (web portal).
Delete
Edit
Clone
Delete
Edit
Delete
Edit
GUID Enter the globally unique identifier (GUID) for the host check application. The
GUID is usually in the form xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx, where each x
is a hexadecimal digit. Windows uses GUIDs to identify applications in the
Windows Registry.
Add button If you do not know the GUID, add alternative checks for the application. The host
check software is considered found only if all checks succeed.
Check Item entry
Type Select how to check for the application:
• File — Look for a file. This could be the application’s executable file or any
other file that would confirm the presence of the application. In File/Path,
enter the full path to the file. Where applicable, you can use environment
variables enclosed in percent (%) marks. For example,
%ProgramFiles%\Fortinet\FortiClient\FortiClient.exe.
• Process — Look for the application as a running process. In Process, enter
the application’s executable file name.
• Registry — Search for a Windows Registry entry. In Registry, enter a registry
item, for example HKLM\SOFTWARE\Fortinet\FortiClient\Misc.
Action Select one of
Require — If the item is found, the client meets the check item condition.
Deny — If the item is found, the client is considered to not meet the check item
condition. Use this option if it is necessary to prevent use of a particular security
product.
MD5 Signatures If Type is File or Process, enter one or more known MD5 signatures for the
application executable file.You can use a third-party utility to calculate MD5
signatures or hashes for any file. You can enter multiple signatures to match
multiple versions of the application.
Delete
User
This section explains how to set up user accounts, user groups, and external
authentication servers. You can use these components of user authentication to control
access to network resources.
If you enable virtual domains (VDOMs) on the FortiGate unit, user authentication is
configured separately for each virtual domain. For details, see “Using virtual domains” on
page 125.
This section describes:
• Getting started - User authentication
• Local user accounts
• Remote
• RADIUS
• LDAP
• TACACS+
• PKI
• Directory Service
• User Group
• Options
• Monitor
• NAC quarantine and the Banned User list
You can configure your FortiGate unit to authenticate system administrators with your
FortiGate unit, using RADIUS, LDAP and TACACS+ servers and with certificate-based
authentication using PKI. For more information, see “System Admin” on page 241. You
can change the authentication timeout value or select the protocol supported for Firewall
authentication. For more information, see “Options” on page 667. You can view lists of
currently authenticated users, authenticated IM users, and banned users. For more
information, see “Monitor” on page 668.
For each network resource that requires authentication, you specify which user groups are
permitted access to the network. There are three types of user groups: Firewall, Directory
Service, and SSL VPN. For more information, see “Firewall user groups” on page 659,
“Directory Service user groups” on page 660, and “SSL VPN user groups” on page 660.
Delete
Edit
Type The authentication type to use for this user. The authentication types are Local
(user and password stored on FortiGate unit), LDAP, RADIUS, and TACACS+
(user and password matches a user account stored on the authentication
server).
Delete icon Delete the user.
The delete icon is not available if the user belongs to a user group.
Edit icon Edit the user account.
Note: Deleting the user name deletes the authentication configured for the user.
To add a Local user, go to User > Local, select Create New, and enter or select the
following:
To add an IM user, go to User > Local > IM, select Create New, and enter or select the
following:
Protocol Select a protocol from the dropdown list: AIM, ICQ, MSN, or Yahoo!.
Username Enter a name for the user.
Policy Select a policy from the dropdown list: Allow or Block.
The IM user monitor list displays information about instant messaging users who are
currently connected. For more information, see “IM user monitor list” on page 669.
If you want to block a protocol that is older than the ones listed above, use the CLI
command:
config imp2p old-version
For more information, see the FortiGate CLI Reference.
Remote
Remote authentication is generally used to ensure that employees working offsite can
remotely access their corporate network with appropriate security measures in place. In
general terms, authentication is the process of attempting to verify the (digital) identity of
the sender of a communication such as a login request. The sender may be someone
using a computer, the computer itself, or a computer program. Since a computer system
should be used only by those who are authorized to do so, there must be a measure in
place to detect and exclude any unauthorized access.
On a FortiGate unit, you can control access to network resources by defining lists of
authorized users, called user groups. To use a particular resource, such as a network or
VPN tunnel, the user must:
• belong to one of the user groups that is allowed access
• correctly enter a user name and password to prove his or her identity, if asked to do so.
RADIUS
Remote Authentication and Dial-in User Service (RADIUS) servers provide authentication,
authorization, and accounting functions. FortiGate units use the authentication function of
the RADIUS server. To use the RADIUS server for authentication, you must configure the
server before you configure the FortiGate users or user groups that will need it.
If you have configured RADIUS support and a user is required to authenticate using a
RADIUS server, the FortiGate unit sends the user’s credentials to the RADIUS server for
authentication. If the RADIUS server can authenticate the user, the user is successfully
authenticated with the FortiGate unit. If the RADIUS server cannot authenticate the user,
the FortiGate unit refuses the connection. You can override the default authentication
scheme by selecting a specific authentication protocol or changing the default port for
RADIUS traffic.
Note: The default port for RADIUS traffic is 1812. If your RADIUS server is using port 1645,
use the CLI to change the default RADIUS port. For more information, see the config
system global command in the FortiGate CLI Reference.
To view the list of RADIUS servers, go to User > Remote > RADIUS.
Delete
Edit
Create New Add a new RADIUS server. The maximum number is 10.
Name Name that identifies the RADIUS server on the FortiGate unit.
The RADIUS server can use several different authentication protocols during the
authentication process:
• MS-CHAP-V2 is the Microsoft challenge-handshake authentication protocol v2
• MS-CHAP is the Microsoft challenge-handshake authentication protocol v1
• CHAP (challenge-handshake authentication protocol) provides the same functionality
as PAP, but does not send the password and other user information over the network to
a security server
• PAP (password authentication protocol) is used to authenticate PPP connections. PAP
transmits passwords and other user information in clear text (unencrypted).
If you have not selected a protocol, the default protocol configuration uses PAP, MS-
CHAPv2, and CHAP, in that order.
To add a new RADIUS server, go to User > Remote > RADIUS, select Create New, and
enter or select the following:
Name Enter the name that is used to identify the RADIUS server on the
FortiGate unit.
Primary Server Name/IP Enter the domain name or IP address of the primary RADIUS server.
Primary Server Secret Enter the RADIUS server secret key for the primary RADIUS server.
The primary server secret key should be a maximum of 16
characters in length.
Secondary Server Name/IP Enter the domain name or IP address of the secondary RADIUS
server, if you have one.
Secondary Server Secret Enter the RADIUS server secret key for the secondary RADIUS
server. The secondary server secret key should be a maximum of 16
characters in length.
Authentication Scheme Select Use Default Authentication Scheme to authenticate with the
default method. The default authentication scheme uses PAP, MS-
CHAP-V2, and CHAP, in that order.
Select Specify Authentication Protocol to override the default
authentication method, and choose the protocol from the list: MS-
CHAP-V2, MS-CHAP, CHAP, or PAP, depending on what your
RADIUS server needs.
NAS IP/Called Station ID Enter the NAS IP address and Called Station ID (for more
information about RADIUS Attribute 31, see RFC 2548 Microsoft
Vendor-specific RADIUS Attributes). If you do not enter an IP
address, the IP address that the FortiGate interface uses to
communicate with the RADIUS server will be applied.
Include in every User Group Select to have the RADIUS server automatically included in all user
groups.
LDAP
Lightweight Directory Access Protocol (LDAP) is an Internet protocol used to maintain
authentication data that may include departments, people, groups of people, passwords,
email addresses, and printers. An LDAP consists of a data-representation scheme, a set
of defined operations, and a request/response network.
If you have configured LDAP support and require a user to authenticate using an LDAP
server, the FortiGate unit contacts the LDAP server for authentication. To authenticate
with the FortiGate unit, the user enters a user name and password. The FortiGate unit
sends this user name and password to the LDAP server. If the LDAP server can
authenticate the user, the FortiGate unit successfully authenticates the user. If the LDAP
server cannot authenticate the user, the FortiGate unit refuses the connection.
The FortiGate unit supports LDAP protocol functionality defined in RFC 2251: Lightweight
Directory Access Protocol v3, for looking up and validating user names and passwords.
FortiGate LDAP supports all LDAP servers compliant with LDAP v3. In addition, FortiGate
LDAP supports LDAP over SSL/TLS. To configure SSL/TLS authentication, refer to the
FortiGate CLI Reference.
FortiGate LDAP support does not extend to proprietary functionality, such as notification of
password expiration, that is available from some LDAP servers. Nor does the FortiGate
LDAP supply information to the user about why authentication failed.
To view the list of LDAP servers, go to User > Remote > LDAP.
Delete
Edit
Create New Add a new LDAP server. The maximum number is 10.
Name The name that identifies the LDAP server on the FortiGate unit.
Server Name/IP The domain name or IP address of the LDAP server.
Port The TCP port used to communicate with the LDAP server.
Common Name The common name identifier for the LDAP server. Most LDAP servers use cn.
Identifier However, some servers use other common name identifiers such as uid.
Distinguished The distinguished name used to look up entries on the LDAP servers use. The
Name distinguished name reflects the hierarchy of LDAP database object classes
above the common name identifier.
Delete icon Delete the LDAP server configuration.
Edit icon Edit the LDAP server configuration.
Query
Name Enter the name that identifies the LDAP server on the FortiGate unit.
Server Name/IP Enter the domain name or IP address of the LDAP server.
Server Port Enter the TCP port used to communicate with the LDAP server.
By default, LDAP uses port 389.
If you use a secure LDAP server, the default port changes when you
select Secure Connection.
Common Name Identifier Enter the common name identifier for the LDAP server. The maximum
number of characters is 20.
Distinguished Name Enter the base distinguished name for the server using the correct
X.500 or LDAP format. The FortiGate unit passes this distinguished
name unchanged to the server. The maximum number of characters is
512.
Query icon View the LDAP server Distinguished Name Query tree for the LDAP
server that you are configuring so that you can cross-reference to the
Distinguished Name.
For more information, see “Using Query”.
Bind Type Select the type of binding for LDAP authentication.
Regular Connect to the LDAP server directly with user name/password, then
receive accept or reject based on search of given values.
Anonymous Connect as an anonymous user on the LDAP server, then retrieve the
user name/password and compare them to given values.
Simple Connect directly to the LDAP server with user name/password
authentication.
Filter Enter the filter to use for group searching. Available if Bind Type is
Regular or Anonymous.
User DN Enter the Distinguished name of the user to be authenticated.
Available if Bind Type is Regular.
Password Enter the password of the user to be authenticated. Available if Bind
Type is Regular.
Secure Connection Select to use a secure LDAP server connection for authentication.
Using Query
The LDAP Distinguished Name Query list displays the LDAP Server IP address, and all
the distinguished names associated with the Common Name Identifier for the LDAP
server. The tree helps you to determine the appropriate entry for the DN field. To see the
distinguished name associated with the Common Name identifier, select the Expand
Arrow beside the CN identifier and then select the DN from the list. The DN you select is
displayed in the Distinguished Name field. Select OK to save your selection in the
Distinguished Name field of the LDAP Server configuration.
To see the users within the LDAP Server user group for the selected Distinguished Name,
select the Expand arrow beside the Distinguished Name in the LDAP Distinguished Name
Query tree.
TACACS+
In recent years, remote network access has shifted from terminal access to LAN access.
Users connect to their corporate network (using notebooks or home PCs) with computers
that use complete network connections and have the same level of access to the
corporate network resources as if they were physically in the office. These connections
are made through a remote access server. As remote access technology has evolved, the
need for network access security has become increasingly important.
Terminal Access Controller Access-Control System (TACACS+) is a remote
authentication protocol that provides access control for routers, network access servers,
and other networked computing devices via one or more centralized servers. TACACS+
allows a client to accept a user name and password and send a query to a TACACS+
authentication server. The server host determines whether to accept or deny the request
and sends a response back that allows or denies network access to the user. The default
TCP port for a TACACS+ server is 49.
To view the list of TACACS+ servers, go to User > Remote > TACACS+.
Delete
Edit
Create New Add a new TACACS+ server. The maximum number is 10.
Server The server domain name or IP address of the TACACS+ server.
Authentication Type The supported authentication method. TACACS+ authentication methods
include: Auto, ASCII, PAP, CHAP, and MSCHAP.
Delete icon Delete this TACACS+ server.
Edit icon Edit this TACACS+ server.
Directory Service
Windows Active Directory (AD) and Novell eDirectory provide central authentication
services by storing information about network resources across a domain (a logical group
of computers running versions of an operating system) in a central directory database.
Each person who uses computers within a domain receives his or her own unique
account/user name. This account can be assigned access to resources within the domain.
In a domain, the directory resides on computers that are configured as domain controllers.
A domain controller is a server that manages all security-related features that affect the
user/domain interactions, security centralization, and administrative functions.
FortiGate units use firewall policies to control access to resources based on user groups
configured in the policies. Each FortiGate user group is associated with one or more
Directory Service user groups. When a user logs in to the Windows or Novell domain, a
Fortinet Server Authentication Extension (FSAE) sends the FortiGate unit the user’s IP
address and the names of the Directory Service user groups to which the user belongs.
The FSAE has two components that you must install on your network:
• The domain controller (DC) agent must be installed on every domain controller to
monitor user logins and send information about them to the collector agent.
• The collector agent must be installed on at least one domain controller to send the
information received from the DC agents to the FortiGate unit.
The FortiGate unit uses this information to maintain a copy of the domain controller user
group database. Because the domain controller authenticates users, the FortiGate unit
does not perform authentication. It recognizes group members by their IP address.
You must install the Fortinet Server Authentication Extensions (FSAE) on the network and
configure the FortiGate unit to retrieve information from the Directory Service server. For
more information about FSAE, see the Fortinet Server Authentication Extension
Administration Guide.
To view the list of Directory Service servers, go to User > Directory Service.
Delete
Edit User/Group
Note: You can create a redundant configuration on your FortiGate unit if you install a
collector agent on two or more domain controllers. If the current (or first) collector agent
fails, the FortiGate unit switches to the next one in its list of up to five collector agents.
Name Enter the name of the Directory Service server. This name appears in the list of
Directory Service servers when you create user groups.
FSAE Collector Enter the IP address or name of the Directory Service server where this
IP/Name collector agent is installed. The maximum number of characters is 63.
Port Enter the TCP port used for Directory Service. This must be the same as the
FortiGate listening port specified in the FSAE collector agent configuration.
Password Enter the password for the collector agent. This is required only if you
configured your FSAE collector agent to require authenticated access.
LDAP Server Select the check box and select an LDAP server to access the Directory
Service.
PKI
Public Key Infrastructure (PKI) authentication utilizes a certificate authentication library
that takes a list of peers, peer groups, and/or user groups and returns authentication
successful or denied notifications. Users only need a valid certificate for successful
authentication—no user name or password are necessary. Firewall and SSL VPN are the
only user groups that can use PKI authentication.
For more information about certificate authentication, see the FortiGate Certificate
Management User Guide. For information about the detailed PKI configuration settings
available only through the CLI, see the FortiGate CLI Reference.
To view the list of PKI users, go to User > PKI.
Caution: If you use the CLI to create a peer user, Fortinet recommends that you enter a
value for either subject or ca. If you do not do so, and then open the user record in the web-
based manager, you will be prompted to enter a subject or ca value before you can
continue.
To create a peer user for PKI authentication, go to User > PKI, select Create New., and
enter the following:
Two-factor authentication
Require two-factor Require this PKI user to authenticate by password in addition to
authentication certificate authentication. Enter a Password.
Password Enter the password that this PKI user must enter.
Note: You must enter a value for at least one of Subject or CA.
You can configure peer user groups only through the CLI. For more information, see the
FortiGate CLI Reference.
User Group
A user group is a list of user identities. An identity can be:
• a local user account (user name and password) stored on the FortiGate unit
• a local user account with a password stored on a RADIUS, LDAP, or TACACS+ server
• a RADIUS, LDAP, or TACACS+ server (all identities on the server can authenticate)
• a user or user group defined on a Directory Service server.
Each user group belongs to one of three types: Firewall, Directory Service or SSL VPN.
For information about each type, see “Firewall user groups” on page 659, “Directory
Service user groups” on page 660, and “SSL VPN user groups” on page 660. For
information on configuring each type of user group, see “Configuring a user group” on
page 661.
In most cases, the FortiGate unit authenticates users by requesting each user name and
password. The FortiGate unit checks local user accounts first. If the unit does not find a
match, it checks the RADIUS, LDAP, or TACACS+ servers that belong to the user group.
Authentication succeeds when the FortiGate unit finds a matching user name and
password.
For a Directory Service user group, the Directory Service server authenticates users when
they log in to the network. The FortiGate unit receives the user’s name and IP address
from the FSAE collector agent. For more information about FSAE, see the Fortinet Server
Authentication Extension Administration Guide.
You can configure user groups to provide authenticated access to:
• Firewall policies that require authentication
See “Adding authentication to firewall policies” on page 372.
You can choose the user groups that are allowed to authenticate with these policies.
• SSL VPNs on the FortiGate unit
See “Configuring SSL VPN identity-based firewall policies” on page 376.
• IPSec VPN Phase 1 configurations for dialup users
See “Creating a new phase 1 configuration” on page 606.
Only users in the selected user group can authenticate to use the VPN tunnel.
• XAuth for IPSec VPN Phase 1 configurations
See XAUTH in “Defining phase 1 advanced settings” on page 608.
Only user groups in the selected user group can be authenticated using XAuth.
Note: A user group cannot be a dialup group if any member is authenticated using a
RADIUS or LDAP server.
For more information, see “Creating a new phase 1 configuration” on page 606.
For information about configuring a Firewall user group, see “Configuring a user group” on
page 661.
You can also use a firewall user group to provide override privileges for FortiGuard web
filtering. For more information, see “Configuring FortiGuard Web filtering override options”
on page 664. For detailed information about FortiGuard Web Filter, including the override
feature, see “FortiGuard Web Filtering” on page 552.
Note: You cannot use Directory Service user groups directly in FortiGate firewall policies.
You must add Directory Service groups to FortiGate user groups. A Directory Service group
should belong to only one FortiGate user group. If you assign it to multiple FortiGate user
groups, the FortiGate unit recognizes only the last user group assignment.
A Directory Service user group provides access to a firewall policy that requires Directory
Service type authentication and lists the user group as one of the allowed groups. The
members of the user group are Directory Service users or groups that you select from a
list that the FortiGate unit receives from the Directory Service servers that you have
configured. See “Directory Service” on page 654.
Note: A Directory Service user group cannot have SSL VPN access.
You can also use a Directory Service user group to provide override privileges for
FortiGuard web filtering. For more information, see “Configuring FortiGuard Web filtering
override options” on page 664. For detailed information about FortiGuard Web Filter,
including the override feature, see “FortiGuard Web Filtering” on page 552.
For information on configuring user groups, see “Configuring a user group” on page 661.
Note: A user group cannot be an IPSec dialup group if any member is authenticated using
a RADIUS or LDAP server.
For information on configuring user groups, see “Configuring a user group” on page 661.
For information on configuring SSL VPN user group options, see “Configuring SSL VPN
identity-based firewall policies” on page 376.
Delete
Note: By default, the FortiGate web-based manager displays Firewall options. The
following figures show the variations that display for each of the user group types: Firewall,
Directory Service, and SSL VPN.
Note: You cannot add local users to a group that is used to authenticate administrators.
Right Arrow
Right Arrow
Left Arrow
Expand Arrow
Right Arrow
Left Arrow
Expand Arrow
Allow to create FortiGuard Select to allow members of this group to request an override on the
Web Filtering overrides FortiGuard Web Filtering Block page. The firewall protection profile
governing the connection must have FortiGuard overrides enabled.
The protection profile may have more than one user group as an
override group. Members of an override group can authenticate on the
FortiGuard Web Filter Block Override page to access the blocked site.
For more information, see “FortiGuard Web Filtering” on page 552.
Override Scope The override can apply to just the user who requested the override, or
include others. Select one of the following from the list:
User Only the user.
User Group The user group to which the user belongs.
IP Any user at the user’s IP address.
Profile Any user with the specified protection profile of the user group.
Ask Authenticating user, who chooses the override scope.
Override Type Select from the list to allow access to:
Directory Only the lowest level directory in the URL.
Domain The entire website domain.
Categories The FortiGuard category.
Ask Authenticating user, who chooses the override type.
Off-site URLs Select one of the following from the list to set permissions for users
linking to sites off the blocked site:
Figure 409: Using RADIUS records to assign IP addresses for SSL VPN Tunnel Mode
5 Go to User > User Group and create a new user group or edit an SSL VPN user group.
6 Set Type to SSL VPN.
7 Select the name of the Portal that contains the tunnel mode widget.
8 Add the RADIUS server that assigns IP addresses to the Members list and save the
SSL VPN user group.
9 Go to Firewall > Policy and select Create New.
10 Set Action to SSL VPN.
11 Add an identity based policy and add the SSL VPN user group containing the RADIUS
server and the portal to the Selected User Groups list.
12 Configure the remaining firewall policy settings as required.
Options
You can define setting options for user authentication, including authentication timeout,
supported protocols, and authentication certificates.
Authentication timeout controls how long an authenticated firewall connection can be idle
before the user must authenticate again.
When user authentication is enabled on a firewall policy, the authentication challenge is
normally issued for any of the four protocols (depending on the connection protocol):
• HTTP (can also be set to redirect to HTTPS)
• HTTPS
• FTP
• Telnet.
The selections made in the Protocol Support list of the Authentication Settings screen
control which protocols support the authentication challenge. Users must connect with a
supported protocol first so they can subsequently connect with other protocols. If HTTPS
is selected as a method of protocol support, it allows the user to authenticate with a
customized Local certificate.
When you enable user authentication on a firewall policy, the firewall policy user will be
challenged to authenticate. For user ID and password authentication, users must provide
their user names and passwords. For certificate authentication (HTTPS or HTTP
redirected to HTTPS only), you can install customized certificates on the FortiGate unit
and the users can also have customized certificates installed on their browsers.
Otherwise, users will see a warning message and have to accept a default FortiGate
certificate.
Note: When you use certificate authentication, if you do not specify any certificate when
you create the firewall policy, the global settings will be used. If you specify a certificate, the
per-policy setting will overwrite the global setting. For information about how to use
certificate authentication, see FortiGate Certificate Management User Guide.
Monitor
You can go to User > Monitor to view lists of currently authenticated users, authenticated
IM users, and banned users. For each authenticated user, the list includes the user name,
user group, how long the user has been authenticated (Duration), how long until the user’s
session times out (Time left), and the method of authentication used. The list of IM users
includes the source IP address, protocol, and last time the protocol was used. The
Banned User list includes users configured by administrators in addition to those
quarantined based on AV, IPS, or DLP rules.
The following lists are available:
• Firewall user monitor list
• IM user monitor list
• NAC quarantine and the Banned User list
Refresh
Current Page
Stop individual
authentication session
To view the list of active IM users, go to User > Monitor > IM.
Protocol Filter the list by selecting the protocol for which to display current users: AIM, ICQ,
MSN, or Yahoo. All current users can also be displayed.
# The position number of the IM user in the list.
Protocol The protocol being used.
User Name The name selected by the user when registering with an IM protocol. The same user
name can be used for multiple IM protocols. Each user name/protocol pair appears
separately in the list.
Source IP The Address from which the user initiated the IM session.
Last Login The last time the current user used the protocol.
Block Select to add the user name to the permanent black list. Each user name/protocol pair
must be explicitly blocked by the administrator.
Caution: If you have configured NAC quarantine to block IP addresses and if the FortiGate
unit receives sessions that have passed through a NAT device, all traffic—not just
individual users—could be blocked from that NAT device.
NAC quarantine adds blocked IP addresses or interfaces to the Banned User list. To view
the Banned User list, go to User > Monitor > Banned User. When you configure NAC
quarantine settings, you can specify how long to block the IP addresses or interfaces.
FortiGate administrators can manually enable access again by removing IP addresses or
interfaces from the Banned User list. Removing an IP address from the Banned User list
means the user can start accessing network services through the FortiGate unit again.
Removing an interface from the list means the interface can resume normal receiving and
processing of communication sessions. For more information, see “The Banned User list”
on page 672.
SMTP email message, you can configure DLP to block all SMTP email from a sender
identified in the “From:” field of the email messages, without blocking the user from web
browsing. DLP will also add the sender’s name to the Banned User list. For more
information about using actions in DLP sensors, see “Adding or editing a rule or
compound rule in a DLP sensor” on page 577.
Clear
Current Page
Delete
Current Page The current page number of list items that are displayed. Select the left and right
arrows to display the first, previous, next or last page of banned users or IP
addresses.
Clear icon Remove all users and IP addresses from the Banned User list.
# The position number of the user or IP address in the list.
Application The protocol that was used by the user or IP address added to the Banned User
Protocol list.
Cause or rule The FortiGate function that caused the user or IP address to be added to the
Banned User list. Cause or rule can be IPS, Antivirus, or Data Leak Prevention.
Created The date and time the user or IP address was added to the Banned User list.
Expires The date and time the user or IP address will be automatically removed from the
Banned User list. If Expires is Indefinite you must manually remove the user or host
from the list.
Delete icon Delete the selected user or IP address from the Banned User list.
Edit
Delete
Create New Add a new WAN optimization rule. New rules are added to the bottom of the list.
Status Select to enable a rule or deselect to disable a rule. A disabled rule is out of
service.
ID The rule identifier. Rules are numbered in the order they are added to the rule
list.
Source The source address or address range that the rule matches. See “About WAN
optimization addresses” on page 679.
Destination The destination address or address range that the rule matches. See “About
WAN optimization addresses” on page 679.
Port The destination port number or port number range that the rule matches.
Method Indicates whether you have selected byte caching in the WAN optimization rule.
Auto-Detect Indicates whether the rule is an active (client) rule, a passive (server) rule or if
auto-detect is off. If auto-detect is off, the rule can be a peer-to-peer rule or a
Web Cache Only rule.
Protocol The protocol optimization WAN optimization technique applied by the rule. See
the FortiGate WAN Optimization, Web Cache, and Web Proxy User Guide.
Peer For a peer-to-peer rule, the name of the peer WAN optimizer at the other end of
the link.
Mode Indicates whether the rule applies Full Optimization or Web Cache Only.
SSL Indicates whether the rule is configured for SSL offloading.
Secure Tunnel Indicates whether the rule is configured to used a WAN optimization tunnel.
Delete icon Delete a rule from the list.
Edit icon Edit a rule.
Insert WAN Add a new rule above the corresponding rule (the New rule screen appears).
Optimization
Rule Before icon
Move To icon Move the corresponding rule before or after another rule in the list. See “Moving
a rule to a different position in the rule list” on page 677.
Mode Select Full Optimization to add a rule that can apply all WAN optimization features.
Select Web Cache Only to add a rule that just applies web caching. If you select
Web Cache Only, you can configure the source and destination address and port
for the rule. You can also select Transparent Mode and Enable SSL.
Source Enter an IP address, followed by a forward slash (/), then subnet mask, or enter an
IP address range separated by a hyphen. See “About WAN optimization
addresses” on page 679.
Only packets whose source address header contains an IP address matching this
IP address or address range will be accepted by and subject to this rule.
For a passive rule, the server (passive) source address range should be
compatible with the source addresses of the matching client (active) rule. To match
one passive rule with many active rules, the passive rule source address range
should include the source addresses of all of the active rules.
Destination Enter an IP address, followed by a forward slash (/), then subnet mask, or enter an
IP address range separated by a hyphen. See “About WAN optimization
addresses” on page 679.
Only a packet whose destination address header contains an IP address matching
this IP address or address range will be accepted by and subject to this rule.
Tip: For a Web Cache Only rule, if you set Destination to 0.0.0.0, the rule caches
web pages on the Internet or any network.
For a passive rule, the server (passive) destination address range should be
compatible with the destination addresses of the matching client (active) rule. To
match one passive rule with many active rules, the passive rule destination
address range should include the destination addresses of all of the active rules.
Port Enter a single port number or port number range. Only packets whose destination
port number matches this port number or port number range will be accepted by
and subject to this rule.
For a passive rule, the server (passive) port range should be compatible with the
port range of the matching client (active) rule. To match one passive rule with many
active rules, the passive rule port range should include the port ranges of all of the
active rules.
Auto-Detect Available only if Mode is set to Full Optimization.
Specify whether the rule is an Active (client) rule, a Passive (server) rule or if auto-
detect is Off. If auto-detect is off the rule is a peer-to-peer rule.
• For an Active (client) rule, you must select all of the WAN optimization features to
be applied by the rule. You can select the protocol to optimize, transparent mode,
byte caching, SSL offloading, secure tunneling, and an authentication group.
• A Passive (server) rule uses the settings in the active rule on the client FortiGate
unit to apply WAN optimization settings. You can also select web caching for a
passive rule.
• If Auto-Detect is Off, the rule must include all required WAN optimization features
and you must select a Peer for the rule. Select this option to configure peer-to-
peer WAN optimization where this rule can start a WAN optimization tunnel with
this peer only.
Protocol Available only if Mode is set to Full Optimization, and Auto-Detect is set to Off or
Active.
Select CIFS, FTP, HTTP, or MAPI to apply protocol optimization for one of these
protocols. For information about protocol optimization, see the FortiGate WAN
Optimization, Web Cache, and Web Proxy User Guide.
Select TCP if the WAN optimization tunnel accepts sessions that use more than
one protocol or that do not use the CIFS, FTP, HTTP, or MAPI protocol.
Peer Available only if Mode is set to Full Optimization, and Auto-Detect is set to Off.
Select the peer host ID of the peer that this peer-to-peer WAN optimization rule will
start a WAN optimization tunnel with. You can also select [Create New ...] to add a
new peer.
Enable Web Available only if Mode is set to Full Optimization, and Auto-Detect is set to Off or
Cache Passive. If Auto-Detect is set to Off, then Protocol must be set to HTTP.
Select to apply WAN optimization web caching to the sessions accepted by this
rule. For more information, see the FortiGate WAN Optimization, Web Cache, and
Web Proxy User Guide.
Transparent Servers receiving packets after WAN optimization “see” different source addresses
Mode depending on whether or not you select Transparent Mode. You can select this
option if Auto-Detect is set to Active or Off. You can also select it for Web Cache
Only rules.
Select this option to keep the original source address of the packets when they are
sent to servers. The servers appear to receive traffic directly from clients. The
server network should be configured to route traffic with client source IP addresses
from the server side FortiGate unit to the server and back to the server side
FortiGate unit.
If this option is not selected, the server side FortiGate unit changes the source
address of the packets received by servers to the address of the server side
FortiGate unit interface that sends the packets to the servers. So servers appear to
receive packets from the server side FortiGate unit. Routing on the server network
is usually simpler in this case because client addresses are not involved, but the
server sees all traffic as coming from the server side FortiGate unit and not from
individual clients.
Enable Byte Available only if Mode is set to Full Optimization, and Auto-Detect is set to Off or
Caching Active.
Select to apply WAN optimization byte caching to the sessions accepted by this
rule. For more information, see the FortiGate WAN Optimization, Web Cache, and
Web Proxy User Guide.
Enable SSL Available only if Auto-Detect is set to Active or Off.
Select to apply SSL offloading for HTTPS traffic. You can use SSL offloading to
offload SSL encryption and decryption from one or more HTTP servers to the
FortiGate unit. If you enable this option, you must configure the rule to accept
SSL-encrypted traffic, for example, by configuring the rule to accept HTTPS traffic
by setting Port to 443.
If you enable SSL offloading, you must also use the CLI command config
wanopt ssl-server to add an SSL server for each HTTP server that you want
to offload SSL encryption/decryption for. For more information, see the FortiGate
WAN Optimization, Web Cache, and Web Proxy User Guide.
Enable Secure Available only if Mode is set to Full Optimization, and Auto-Detect is set to Active or
Tunnel Off.
If you select Enable Secure Tunnel, the WAN optimization tunnel is encrypted
using SSL encryption. You must also add an authentication group to the rule. For
more information, see the FortiGate WAN Optimization, Web Cache, and Web
Proxy User Guide.
Authentication Available only if Mode is set to Full Optimization, and Auto-Detect is set to Active or
Group Off.
Select this option and select an authentication group from the list if you want
groups of FortiGate units to authenticate with each other before starting the WAN
optimization tunnel. You must also select an authentication group if you select
Enable Secure Tunnel.
You must add identical authentication groups to both of the FortiGate units that will
participate in the WAN optimization tunnel started by the rule. For more
information, see “Configuring authentication groups” on page 681.
When representing hosts by an IP range, the range indicates hosts with continuous IP
addresses in a subnet, such as 192.168.1.[2-10], or 192.168.1.* to indicate the
complete range of hosts on that subnet. Valid IP range formats include:
• x.x.x.x-x.x.x.x, such as 192.168.110.100-192.168.110.120
• x.x.x.[x-x], such as 192.168.110.[100-120]
• x.x.x.*, such as 192.168.110.*
Delete
Edit
Delete
Edit
Authentication The method used to authenticate the tunnels: certificate (plus certificate
method name) or pre-shared key.
Peer(s) The host IDs of the peers added to the authentication group. When you add
the authentication group to a WAN optimization rule, only these FortiGate
units can authenticate to use this WAN optimization rule. Peer(s) can be any
peer, a peer added to the FortiGate unit peer list (defined peers), or a
selected peer.
Adding or modifying an authentication group
Create New Select to add a new authentication group
Edit icon Select Edit beside an existing authentication group to modify it.
Delete icon Select to delete an authentication group.
Name Add or change the name of the authentication group. Select this name when
adding the authentication group to a rule.
Other FortiGate units that participate in WAN optimization tunnels with this
FortiGate unit must have an authentication group with the same name.
Authentication Select the authentication method to use.
Method Select Certificate if you want to use a certificate to authenticate and encrypt
WAN optimization tunnels.
Select Pre-shared key if you want to use a pre-shared key or password to
authenticate and encrypt WAN optimization tunnels.
Certificate (list) Available only when Authentication Method is Certificate.
Select a local certificate that has been added to this FortiGate unit. Other
FortiGate units that participate in WAN optimization tunnels with this
FortiGate unit must have an authentication group with the same name and
certificate.
Go to System > Certificates > Local Certificates to add a local certificate to a
FortiGate unit.
Password Available only when Authentication Method is Pre-shared key.
Add the password (or pre-shared key) used by the authentication group.
Other FortiGate units that participate in WAN optimization tunnels with this
FortiGate unit must have an authentication group with the same name and
password.
The key must contain at least 6 printable characters and should be known
only by network administrators. For optimum protection against currently
known attacks, the key should consist of a minimum of 16 randomly chosen
alphanumeric characters.
Peer Acceptance One or more of the following options are available to authenticate WAN
optimization peers:
Accept Any Peer Authenticate with any peer. Use this setting if you do not know the peer host
IDs or IP addresses of the peers that will use this authentication group. This
setting is most often used for WAN optimization with the FortiClient
application.
Accept Defined Authenticate with any peer in the FortiGate unit peer list.
Peers
Specify Peer Authenticate with the selected peer only. Select this option and then select
the peer to add to this authentication group.
Traffic Summary This section provides traffic optimization information. The piechart illustrates
the percentage of traffic for supported applications processed during the
selected Period. The table displays how much traffic has been reduced by
WAN optimization by comparing the amount of LAN and WAN traffic for
each protocol.
Refresh icon Refresh the Traffic Summary.
Period Select a time period to show traffic summary for. You can select:
• Last 10 Minutes
• Last 1 Hour
• Last 1 Day
• Last 1 Week
• Last 1 Month
Reduction Rate Displays each application’s optimization rate. For example, a rate of 80%
means the amount of data processed by that application has been reduced
by 20%.
LAN The amount of data in MB received from the LAN for each application.
WAN The amount of data in MB sent across the WAN for each application. The
greater the difference between the LAN and WAN data, the greater the
amount of data reduced by WAN optimization byte caching, web caching,
and protocol optimization.
Bandwidth This section shows network bandwidth optimization per time Period. A line
Optimization or column chart compares an application’s pre-optimized (LAN data) size
with its optimized size (WAN data).
Refresh icon Select to refresh the Bandwidth Optimization display.
Period Select a time frame to show bandwidth optimization. You can select:
• Last 10 Minutes
• Last 1 Hour
• Last 1 Day
• Last 1 Week
• Last 1 Month
Protocol Select All to display bandwidth optimization for all applications. Select an
individual protocol to display bandwidth optimization for that individual
protocol.
Chart Type Select to display bandwidth optimization with a line chart or a column chart.
Note: For more information about many of these web cache settings, see RFC 2616.
Always revalidate Select to always revalidate requested cached object with content on the
server before serving it to the client.
Max Cache Object Set the maximum object size to cache. The default size is 512000 KB. This
Size object size determines the maximum object size to store in the web cache.
Objects retrieved that are larger than the maximum size are still delivered to
the client but are not stored in the web cache.
Negative Response Set how long in minutes to cache negative responses. The default is 0,
Duration meaning negative responses are not cached. The content server might send
a client error code (4xx HTTP response) or a server error code (5xx HTTP
response) as a response to some requests. If the web cache is configured to
cache these negative responses, it returns that response in subsequent
requests for that page or image for the specified number of minutes.
Fresh Factor Set the fresh factor as a percentage. The default is 100, and the range is 1 to
100. For cached objects that do not have an expiry time, the web cache
periodically checks the server to see if the objects have expired. The higher
the fresh factor the less often the checks occur. For example, if you set the
Max TTL value and Default TTL at 7200 minutes (5 days) and set the Fresh
Factor at 20, the web cache will check the cached objects 5 times before
they expire, but if you set the Fresh Factor at 100, the web cache will check
once.
Max TTL The maximum amount of time (Time to Live) an object can stay in the web
cache without the cache checking to see if it has expired on the server. The
default is 7200 minutes (120 hours or 5 days).
Min TTL The minimum amount of time an object can stay in the web cache before the
web cache checks to see if it has expired on the server. The default is 5
minutes.
Default TTL The default expiry time for objects that do not have an expiry time set by the
web server. The default expiry time is 1440 minutes (24 hours).
Explicit Proxy Indicates whether the explicit proxy has been enabled for the FortiGate unit.
See “Configuring the explicit web proxy” on page 182.
Enable Cache Select to enable using the WAN optimization web cache to cache for the
Explicit Proxy explicit proxy.
Ignore
If-modified-since By default, if the time specified by the if-modified-since (IMS) header in the
client's conditional request is greater than the last modified time of the object
in the cache, it is a strong indication that the copy in the cache is stale. If so,
HTTP does a conditional GET to the Overlay Caching Scheme (OCS), based
on the last modified time of the cached object. Enable ignoring If-modified-
since to override this behavior.
HTTP 1.1 HTTP 1.1 provides additional controls to the client over the behavior of
Conditionals caches toward stale objects. Depending on various cache-control headers,
the FortiGate unit can be forced to consult the OCS before serving the object
from the cache. For more information about the behavior of cache-control
header values, see RFC 2616.
Pragma-no- Typically, if a client sends an HTTP GET request with a pragma no-cache
cache (PNC) or cache-control no-cache header, a cache must consult the OCS
before serving the content. This means that the FortiGate unit always re-
fetches the entire object from the OCS, even if the cached copy of the object
is fresh.
Because of this behavior, PNC requests can degrade performance and
increase server-side bandwidth utilization. However, if ignore Pragma-no-
cache is enabled, then the PNC header from the client request is ignored.
The FortiGate unit treats the request as if the PNC header is not present at
all.
IE Reload Some versions of Internet Explorer issue Accept / header instead of Pragma
no-cache header when you select Refresh. When an Accept header has only
the / value, the FortiGate unit treats it as a PNC header if it is a type-N object.
When ignore IE Reload is enabled, the FortiGate unit ignores the PNC
interpretation of the Accept / header.
Cache Expired Applies only to type-1 objects. When this option is selected, expired type-1
Objects objects are cached (if all other conditions make the object cacheable).
Revalidated Pragma- The pragma-no-cache (PNC) header in a client's request can affect the
no-cache efficiency of the FortiGate unit’s bandwidth. If you do not want to completely
ignore PNC in client requests (which you can do by selecting to ignore
Pragma-no-cache, above), you can nonetheless lower the impact on the
bandwidth by selecting Revalidate Pragma-no-cache. When this option is
selected, a client's non-conditional PNC-GET request results in a conditional
GET request sent to the OCS if the object is already in the cache. This gives
the OCS a chance to return the 304 Not Modified response, which consumes
less server-side bandwidth, because the OCS has not been forced to
otherwise return full content. By default, Revalidate Pragma-no-cache is
disabled and is not affected by changes in the top-level profile. When the
Substitute Get for PNC configuration is enabled, the revalidate PNC
configuration has no effect.
Most download managers make byte-range requests with a PNC header. To
serve such requests from the cache, you should also configure byte-range
support when you configure the Revalidate pragma-no-cache option.
Endpoint NAC
Endpoint Network Access Control (NAC) enforces the use of the FortiClient End Point
Security (Enterprise Edition) application on your network. It can also allow or deny
endpoints access to the network based on the applications installed on them.
FortiClient enforcement can check that the endpoint is running the most recent version of
the FortiClient application, that the antivirus signatures are up-to-date and that the firewall
is enabled. An endpoint is most often a single PC with a single IP address being used to
access network services through a FortiGate unit.
You enable endpoint NAC in a firewall policy. When traffic attempts to pass through the
firewall policy, the FortiGate unit runs compliance checks on the originating host on the
source interface. Non-compliant endpoints are blocked. If web browsing, the endpoints
are redirected to a web portal that explains the non-compliance and provides a link to
download the FortiClient application installer.
To ease introduction of endpoint NAC on your network, the FortiGate unit can optionally
recommend non-compliant users install FortiClient software but allow them to continue
without doing so.
You can monitor the endpoints that are subject to endpoint NAC, viewing information
about the computer, its operating system and detected applications.
Note: Endpoint NAC does not function if enabled in a firewall policy that contains a load
balance VIP.
• Define application detection lists to specify which applications are allowed or not
allowed. Optionally, you can deny access to endpoints that have applications installed
that are not on the detection list. See “Configuring application detection lists” on
page 689.
• Configure Endpoint NAC profiles which specify the FortiClient enforcement settings
and the application detection list to apply. You select the Endpoint NAC profile to use
when you enable Endpoint NAC in the firewall policy.
• Enable endpoint NAC in firewall policies.
Note: You cannot enable Endpoint NAC in firewall policies if Redirect HTTP Challenge
to a Secure Channel (HTTPS) is enabled in User > Options > Authentication.
• Optionally, modify the inactivity timeout for endpoints. The default is 5 minutes. After
that time period, the FortiGate unit rechecks the endpoint for Endpoint NAC
compliance. To change the timeout, adjust the compliance-timeout value in the
config endpoint-control settings CLI command.
You can also modify the appearance of the Endpoint NAC Download Portal and the
Endpoint NAC Recommendation Portal. These are replacement messages. For more
information, see “Endpoint NAC replacement messages” on page 235.
Information
FortiGuard Availability FortiGuard Services is available if the indicator is green.
FortiClient Endpoint FortiClient software versions available from FortiGuard Services are
Versions listed. Select the Download link to download the installer.
AV Signature Package The latest AV signature package available from FortiGuard Services.
Application Signature The latest application signature package available from FortiGuard
Package Services.
FortiClient Downloads The number of FortiClient software downloads through this FortiGate
unit.
Update Now Retrieve the latest information from FortiGuard Services.
FortiClient Installer Select one of the following options to determine the link that the
Download Location FortiClient Download Portal provides to non-compliant users to
download the FortiClient installer.
FortiGuard Distribution The FortiClient application is provided by the FortiGuard Distribution
Network Network. The FortiGate unit must be able to access the FortiGuard
Distribution Network. See “Configuring FortiGuard Services” on
page 300.
If the FortiGate unit contains a hard disk drive, the files from
FortiGuard Services are cached to more efficiently serve downloads
to multiple end points.
This FortiGate Users download a FortiClient installer file from this FortiGate unit.
This option is available only on FortiGate models that support upload
of FortiClient installer files. Upload your FortiClient installer file using
the execute restore forticlient CLI command. For more
information, refer to the FortiGate CLI Reference.
Custom URL Specify a URL from which users can download the FortiClient
installer. You can use this option to provide custom installer files even
if your FortiGate unit does not have storage space for them.
Enforce Minimum Version From the list select either Latest Available or a specific FortiClient
version as the minimum requirement for endpoints.
The list contains the FortiClient versions available from the selected
FortiClient Installer Download Location.
Fortinet recommends that administrators deploy a FortiClient version
update to their users or ask users to install the update and then wait a
reasonable period of time for the updates to be installed before
updating the minimum version required to the most recent version.
Note: Select This FortiGate or Custom URL if you want to provide a customized FortiClient
application. This is required if a FortiManager unit will centrally manage FortiClient
applications. For information about customizing the FortiClient application, see the
FortiClient Administration Guide.
1 2
3
Edit
4 5 Delete
Edit
Insert
Move To
Page Shows the current page number in the list. Select the left and right
arrows to display the first, previous, next or last page of known
endpoints.
Column Settings Select the columns to display in the list. You can also determine the
order in which they appear. For more information, see “Using column
settings to control the columns displayed” on page 61 and “Web-based
manager icons” on page 63.
Clear All Filters Clear any column display filters you might have applied.
Filter icons Edit the column filters to filter or sort the endpoints list according to the
criteria you specify. For example, you could add a filter to the Detected
Software column to display all endpoints running BitTorrent software.
For more information, see “Adding filters to web-based manager lists”
on page 57.
Delete
Edit
Profile list
Create New Create a new Endpoint NAC profile.
Name The name of the Endpoint NAC profile.
FortiClient Enforcement Green check mark icon - enabled.
Grey X icon - not enabled.
Application Detection List The application detection list specified in this profile.
Delete Delete this profile.
Edit Edit this profile.
Endpoint NAC Profile settings
Name Enter a name for the Endpoint NAC profile.
For non-compliant hosts: Enable one of the following options:
Notify hosts to install Allow users to continue browsing without installing
FortiClient (warn only) FortiClient Endpoint Security.
Quarantine hosts to user Keep endpoint quarantined until user installs FortiClient
portal (enforce compliance) Endpoint Security.
Additional Client Options Enable to enforce any of the following:
Anti-virus Enabled Require that the antivirus feature is enabled.
Anti-virus Up-to-date Require that the antivirus signatures are up-to-date.
Firewall Enabled Require that the firewall feature is enabled.
Monitoring endpoints
To view the list of known endpoints, go to Endpoint NAC > Monitor > Endpoints. An
endpoint is added to the list when it uses a firewall policy that has Endpoint NAC enabled.
Once an endpoint is added to the list it remains there until you manually delete it or until
the FortiGate unit restarts. Every time an endpoint accesses network services through the
FortiGate unit (or attempts to access services) the entry for the endpoint is updated.
The endpoints list can provide an inventory of the endpoints on your network. Entries for
endpoints not running the FortiClient application include the IP address, last update time,
and traffic volume/attempts. The “non-compliant” status indicates the endpoint is not
running the FortiClient application.
Entries for endpoints running the FortiClient application show much more information,
depending on what is available for the FortiClient application to gather. Detailed
information you can view includes endpoint hardware (CPU and model name) and the
software running on the endpoints. You can adjust column settings and filters to display
this information in many different forms.
From the endpoints list, you can view information for each endpoint, temporarily exempt
end points from endpoint NAC, and restore exempted end points to their blocked state.
Figure 425: Endpoints list (showing one endpoint that does not have FortiClient software
installed)
Refresh
Non-Compliant View
Exempt Temporarily
Wireless Controller
Most FortiGate units, but not FortiWiFi models, can act as a wireless network controller,
managing the wireless Access Point (AP) functionality of FortiWiFi units. All units must be
running the most recent FortiOS 4.0 firmware.
You create virtual access points that can be associated with multiple physical access
points. Clients can roam amongst the physical access points, extending the range of the
wireless network.
The following topics are included in this section:
• Configuration overview
• Enabling the wireless controller
• Configuring FortiWiFi units as managed access points
• Configuring a virtual wireless access point
• Configuring a physical access point
• Configuring DHCP for your wireless LAN
• Configuring firewall policies for the wireless LAN
• Monitoring wireless clients
• Monitoring rogue APs
Configuration overview
To set up a wireless network using the Wireless Controller feature, you need to:
• Enable the wireless controller, if it is not already enabled.
• Configure FortiWiFi units to be managed by the wireless controller.
• Configure each virtual access point (VAP). A VAP has the SSID and security
configuration settings you would find on a wireless access point device. Optionally, you
can limit the number of simultaneous wireless clients who can use this VAP.
• Configure each physical access point (AP). The AP settings include the radio settings
and rogue AP scan settings. You select the VAPs that will be carried on the physical
access point. Optionally, you can limit the number of simultaneous clients this AP will
accept.
• Configure DHCP service to provide addresses to your wireless clients.
• Configure firewall policies to enable communication between the wireless LAN and
other networks.
Name Enter a name to identify the VAP. This is also the name of the virtual
network interface you will use in firewall policies.
SSID Enter the wireless service set identifier (SSID) or network name for this
wireless interface. Users who want to use the wireless network must
configure their computers with this network name.
SSID Broadcast Select to broadcast the SSID. Broadcasting the SSID enables clients to
connect to your wireless network without first knowing the SSID. For better
security, do not broadcast the SSID.
Security mode Select the security mode for the wireless interface. Wireless users must
use the same security mode to be able to connect to this wireless
interface.
None — has no security. Any wireless user can connect to the wireless
network.
WEP64 — 64-bit web equivalent privacy (WEP). To use WEP64 you must
enter a Key containing 10 hexadecimal digits (0?9 a?f) and inform wireless
users of the key.
WEP128 — 128-bit WEP. To use WEP128 you must enter a Key
containing 26 hexadecimal digits (0-9 a-f) and inform wireless users of the
key.
WPA — Wi-Fi protected access (WPA) security. To use WPA you must
select a data encryption method. You must also enter a pre-shared key
containing at least eight characters or select a RADIUS server. If you
select a RADIUS server, the wireless clients must have accounts on the
RADIUS server.
WPA2 — WPA with more security features. To use WPA2 you must select
a data encryption method and enter a pre-shared key containing at least
eight characters or select a RADIUS server. If you select a RADIUS server
the wireless clients must have accounts on the RADIUS server.
WPA2 Auto — the same security features as WPA2, but also accepts
wireless clients using WPA security. To use WPA2 Auto you must select a
data encryption method You must also enter a pre-shared key containing
at least 8 characters or select a RADIUS server. If you select a RADIUS
server the wireless clients must have accounts on the RADIUS server.
Data Encryption Select TKIP or AES encryption as appropriate for the capabilities of your
wireless clients. This is available for WPA security modes.
Key Index Many wireless clients can configure up to four WEP keys. Select which
key clients must use.with this access point. This is available when you
select a WEP Security Mode.
Key Enter the encryption key that the clients must use. This is available when
you select a WEP Security Mode.
Authentication Select one of:
Pre-shared key — Enter the pre-shared key that clients must use.
RADIUS Server — Select the RADIUS server that will authenticate the
clients.
These settings are available when you select a WAP Security Mode.
Maximum Clients Enter the maximum number of clients permitted to connect simultaneously.
Enter 0 for no limit.
2 Select OK.
Serial Number Enter the serial number of the FortiWiFi unit. This field is completed
automatically if the AP discovers this AC and registers itself.
Name Enter a name for the physical AP.
Admin Select one of the following:
Discovery — This is the setting for APs that have discovered this AC and
registered themselves. To use such an AP, select Enabled.
Disabled — Do not manage this AP.
Enabled — Manage this AP.
Last Error The last error message, if any, for this AP.
Rogue AP Scan Rogue AP scanning detects other APs and reports them on the Wireless
Controller > Rogue AP page.
Select one of the following:
Dedicated — AP performs scanning only and does not provide service.
Background — AP performs scanning during idle periods while acting as
an AP.
Disabled — Do not perform scanning. Scanning can reduce performance.
Radio Select the wireless frequency band. Keep in mind the capabilities of your
users’ wireless cards or devices.
Geography Select your country or region. This determines which channels are
available.
Channel Select a channel for your wireless network or select Auto. The channels
that you can select depend on the Geography setting.
TX Power Set the transmitter power level. The higher the number, the larger the area
the AP will cover.
Maximum Clients Enter the maximum number of clients permitted to connect simultaneously
to this physical AP. Enter 0 for no limit.
Virtual AP In the Available list, select the virtual APs to be carried on this physical AP
and then select the right-arrow button to move them to the Selected list.
2 Select OK.
Refresh Interval Set time between information updates. none means no updates.
Refresh Updates displayed information now.
Inactive Access Points Select which inactive access points to show: all, none, those detected
less than one hour ago, or those detected less than one day ago.
Online A green checkmark indicates an active access point. A grey X indicates
that the access point is inactive.
SSID The wireless service set identifier (SSID) or network name for the
wireless interface.
MAC Address The MAC address of the Wireless interface.
Signal Strength /Noise The signal strength and noise level.
Channel The wireless radio channel that the access point uses.
Rate The data rate of the access point.
First Seen The data and time when the FortiWifi unit first detected the access point.
Last Seen The data and time when the FortiWifi unit last detected the access point.
Mark as ‘Accepted AP’ Select the icon to move this entry to the Accepted Access Points list.
Mark as ‘Rogue AP’ Select the icon to move this entry to the Rogue Access Points list.
Forget AP Return item to Unknown Access Points list from Accepted Access Points
list or Rogue Access Points list.
Log&Report
FortiGate units provide extensive logging capabilities for traffic, system and network
protection functions. They also allow you to compile reports from the detailed log
information gathered. Reports provide historical and current analysis of network activity to
help identify security issues that will reduce and prevent network misuse and abuse.
This section provides an introduction to FortiGate logging and reporting. For more
information see the Logging and Reporting in FortiOS 4.0.
For better log storage and retrieval, the FortiGate unit can send log messages to a
FortiAnalyzer unit. FortiAnalyzer units provide integrated log collection, analysis tools and
data storage. Detailed log reports provide historical as well as current analysis of network
activity. Detailed log reports also help identify security issues, reducing network misuse
and abuse. The FortiGate unit can send all log message types, including quarantine files
and DLP archives, to a FortiAnalyzer unit for storage. The FortiAnalyzer unit can upload
log files to an FTP server for archival purposes. For more information about configuring
the FortiGate unit to send log messages to a FortiAnalyzer unit, see “Remote logging to a
FortiAnalyzer unit” on page 704.
If you have a subscription for the FortiGuard Analysis and Management Service, your
FortiGate unit can send logs to a FortiGuard Analysis server. This service provides
another way to store and view logs, as well as archiving email messages. For more
information, see the FortiGuard Analysis and Management Service Administration Guide.
For details and descriptions of log messages and formats, see the FortiGate Log Message
Reference.
This section provides information about how to enable logging, view log messages, and
configure reports. If you have VDOMs enabled, see “Using virtual domains” on page 125
for more information.
The following topics are included in this section:
• Configuring how a FortiGate unit stores logs
• Configuring Alert Email
• Configuring Event logging
• Accessing and viewing log messages
• Viewing DLP Archives
• Viewing the File Quarantine list
• Configuring FortiAnalyzer report schedules
• Viewing Executive Summary reports from SQL logs
• Viewing FortiAnalyzer reports
• Viewing basic traffic reports
• Log severity levels
• Log types
• Example configuration: logging all FortiGate traffic
Note: If the FortiGate unit is in transparent mode, certain settings and options for logging
may not be available because certain features do not support logging, or are not available
in transparent mode. For example, SSL VPN events are not available in transparent mode.
Expand
Arrow
Note: You cannot configure a FortiAnalyzer unit to be a backup solution for the FortiGuard
Analysis server, and vice versa. If you require a backup solution for one of these logging
devices, using a syslog server or WebTrends server.
FortiAnalyzer The name of the FortiAnalyzer unit. The default name of a FortiAnalyzer unit is
(Hostname) its product name, for example, FortiAnalyzer-400.
FortiGate The serial number of the FortiGate unit.
(Device ID)
Registration The status of whether or not the FortiGate unit is registered with the
Status FortiAnalyzer unit. If the FortiGate unit is unregistered, it may not have full
privileges. For more information, see the FortiAnalyzer Administration Guide.
Connection The connection status between FortiGate and FortiAnalyzer units. A green
Status check mark indicates there is a connection and a gray X indicates there is no
connection.
Disk Space (MB) The amount of disk space, in MB, on the FortiAnalyzer unit for logs.
Allocated The amount of the FortiAnalyzer unit hard drive space
Space designated for logs, including quarantine files and DLP archives.
Used Space The amount of used space.
Total Free The amount of unused space.
Space
Privileges The permissions of the device for sending and viewing logs, reports, DLP
archives, and quarantined logs.
• Tx indicates the FortiGate unit is allowed to transmit log packets to the
FortiAnalyzer unit.
• Rx indicates the FortiGate unit is allowed to display reports and logs stored
on the FortiAnalyzer unit.
A check mark indicates the FortiGate unit has permissions to send or view log
information and reports. An X indicates the FortiGate unit is not allowed to send
or view log information.
You can also test the connection status between the FortiGate unit and the FortiAnalyzer
unit by using the following CLI command:
execute log fortianalyzer test-connectivity
The command displays the connection status and the amount of disk usage in percent.
For more information, see the FortiGate CLI Reference.
Note: The test connectivity feature also provides a warning when a FortiGate unit requires
a higher-end FortiAnalyzer unit or when the maximum number of VDOMs/FortiGate units
has been reached on the FortiAnalyzer unit.
Note: If more than one syslog server is configured, the syslog servers and their settings
appear on the Log Settings page. You can configure multiple syslog servers in the CLI
using the config log {syslog | syslog2 | syslog3} settings CLI command.
For more information, see the FortiGate CLI Reference.
Note: From the FortiGate CLI you can enable reliable delivery of syslog messages using
the reliable option of the config log {syslog | syslog2 | syslog3}
settings command. The FortiGate unit implements the RAW profile of RFC 3195 for
reliable delivery of log messages. Reliable syslog protects log information through
authentication and data encryption and ensures that the log messages are reliably
delivered in the correct order. This feature is disabled by default.
IP/FQDN The IP address or fully qualified domain name of the syslog server. For
example, the FQDN could be log.example.com.
Port The port number for communication with the syslog server, typically port 514.
Minimum log level The FortiGate unit logs all messages at and above the logging severity level
you select. For more information about the logging levels, see “Log severity
levels” on page 727.
Facility Facility indicates to the syslog server the source of a log message. By
default, FortiGate reports Facility as local7. You may want to change Facility
to distinguish log messages from different FortiGate units.
Enable CSV Format If you enable CSV format, the FortiGate unit produces the log in Comma
Separated Value (CSV) format. If you do not enable CSV format the
FortiGate unit produces plain text files.
To configure the FortiGate unit to save logs on the local hard disk
1 Go to Log&Report > Log Config > Log Setting.
2 Select Local Logging & Archiving and select the check box beside Disk.
3 Select Minimum log level for memory logs
The FortiGate unit logs all messages at and above the logging severity level you
select. For more information about the logging levels, see “Log severity levels” on
page 727.
4 Change the When log disk is full setting if required.
5 Change the Log rolling settings if required.
6 Select which log message types are saved as SQL logs.
7 Select Apply.
Violation traffic Select if you require an alert email message based on violated traffic
detected that is detected by the FortiGate unit.
Firewall authentication Select if you require an alert email message based on firewall
failure authentication failures.
SSL VPN login failure Select if you require an alert email message based on any SSL VPN
logins that failed.
Administrator Select if you require an alert email message based on whether
login/logout administrators log in or out.
IPSec tunnel errors Select if you require an alert email message based on whether there is
an error in the IPSec tunnel configuration.
L2TP/PPTP/PPPoE Select if you require an alert email message based on errors that
errors occurred in L2TP, PPTP, or PPPoE.
Configuration changes Select if you require an alert email message based on any changes
made to the FortiGate configuration.
FortiGuard license Enter the number of days before the FortiGuard license expiry time
expiry time (1-100 notification is sent.
days)
FortiGuard log quota Select if you require an alert email message based on the FortiGuard
usage Analysis server log disk quota getting full.
Disk Usage Select if you require an alert email when the internal hard disk or AMC
disk reaches a disk usage level. You can set the disk usage level at
which the alert email is sent.
Send alert email for logs Select if you want to send an alert email that is based on a specified
based on severity log severity, such as warning.
Minimum log level Select a log severity from the list. For more information about log
severity levels, see “Log severity levels” on page 727.
System activity event All system-related events, such as ping server failure and gateway status.
IPSec negotiation All IPSec negotiation events, such as progress and error reports.
event
DHCP service event All DHCP-events, such as the request and response log.
L2TP/PPTP/PPPoE All protocol-related events, such as manager and socket creation
service event processes.
Admin event All administrative events, such as user logins, resets, and configuration
updates.
HA activity event All high availability events, such as link, member, and state information.
Firewall All firewall-related events, such as user authentication.
authentication event
Pattern update event All pattern update events, such as antivirus and IPS pattern updates and
update failures.
SSL VPN user All user authentication events for an SSL VPN connection, such as logging
authentication event in, logging out and timeout due to inactivity.
SSL VPN All administration events related to SSL VPN, such as SSL configuration
administration event and CA certificate loading and removal.
SSL VPN session All session activity such as application launches and blocks, timeouts, and
event verifications.
VIP ssl event All server-load balancing events happening during SSL sessions, especially
details about handshaking.
VIP server health All related VIP server health monitor events that occur when the VIP health
monitor event monitor is configured, such as an interface failure.
CPU & memory All real-time CPU and memory events, at 5-minute intervals.
usage (every 5 min)
Antivirus log
The Antivirus log records virus incidents in Web, FTP, and email traffic. For example,
when the FortiGate unit detects an infected file, blocks a file type, or blocks an oversized
file or email that is logged, it records an antivirus log. You can also apply filters to
customize what the FortiGate unit logs, which are:
• Viruses – The FortiGate unit logs all virus infections.
• Blocked Files – The FortiGate unit logs all instances of blocked files.
• Oversized Files/Emails – The FortiGate unit logs all instances of files and email
messages exceeding defined thresholds.
• AV Monitor – The FortiGate unit logs all instances of viruses, blocked files, and
oversized files and email. This applies to HTTP, FTP, IMAP, POP3, SMTP, and IM
traffic.
Note: Make sure attack signature and attack anomaly DoS sensor settings are enabled to
log the attack. The logging options for the signatures included with the FortiGate unit are
set by default. Ensure any custom signatures also have the logging option enabled. For
more information, see “Intrusion Protection” on page 523.
Log Type Select the type of log you want to view. Some log files, such as the traffic log,
cannot be stored to memory due to the volume of information logged.
Current Page By default, the first page of the list of items is displayed. The total number of
pages displays after the current page number. For example, if 3/54 appears,
you are currently viewing page 3 of 54 pages.
To view pages, select the left and right arrows to display the first, previous,
next, or last page.
To view a specific page, enter the page number in the field and then press
Enter.
For more information, see “Using page controls on web-based manager lists”
on page 60.
Column Settings Select to add or remove columns. This changes what log information appears
in Log Access. For more information, see “Column settings” on page 718.
Raw or Formatted By default, log messages are displayed in Formatted mode. Select Formatted
to view log messages in Raw mode, without columns. When in Raw mode,
select Formatted to switch back to viewing log messages organized in
columns.
When log messages are displayed in Formatted view, you can customize the
columns, or filter log messages.
Clear All Filters Clear all filter settings. For more information, see “Filtering log messages” on
page 719.
Figure 436: Viewing log files stored on the FortiGate hard disk
Clear log
Delete View
Download
Log Type Select the type of log you want to view. Some log files, such as the traffic log,
cannot be stored to memory due to the volume of information logged.
Refresh Refresh the displayed log messages.
File name The names of the log files of the displayed log type stored on the FortiGate hard
disk.
When a log file reaches its maximum size, the FortiGate unit saves the log files
with an incremental number, and starts a new log file with the same name. For
example, if the current attack log is alog.log, any subsequent saved logs appear
as alog.n, where n is the number of rolled logs.
Size (bytes) The size of the log file in bytes.
Last access The time a log message was recorded on the FortiGate unit. The time is in the
time format name of day month date hh:mm:ss yyyy, for example Fri Feb
16 12:30:54 2007.
Clear log icon Clear the current log file. Clearing deletes only the current log messages of that
log file. The log file is not deleted.
Download icon Download the log file or rolled log file. Select either Download file in Normal
format or Download file in CSV format. Select Return to return to the Disk tab
page. Downloading the current log file includes only current log messages.
View icon View a log file’s log messages.
Delete icon Delete rolled logs. Fortinet recommends to download the rolled log file before
deleting it because the rolled log file cannot be retrieved after deleting it.
Current
Page
Note: The FortiAnalyzer unit must be running firmware version 3.0 or higher to view logs
from the FortiGate unit.
Note: For more information about filtering log messages, see “Adding filters to web-based
manager lists” on page 57.
Column settings
By using Column Settings, you can customize the view of log messages in Formatted
view. By adding columns, changing their order, or removing them, you can view only the
log information you want.
The Column Settings feature is available only in Formatted view.
-> Select the right arrow to move selected fields from the Available fields list to
the Show these fields in this order list.
<- Select the left arrow to move selected fields from the Show these fields in this
order list to the “Available fields” list.
Move up Move the selected field up one position in the Show these fields in this order
list.
Move down Move the selected field down one position in the Show these fields in this
order list.
7 Select OK.
Note: The Detailed Information column provides the entire raw log entry and is needed only
if the log contains information not available in any of the other columns. The VDOM column
displays which VDOM the log was recorded in.
You can view the device ID and device name when customizing columns. The device ID
provides the identification name of the device. The device name is the host name that you
configured for the FortiGate unit, for example Headquarters.
Filter icon
Filter icon
(enabled)
(disabled)
The file quarantine list displays the following information about each quarantined file:
Service The service from which the file was quarantined (HTTP, FTP, IMAP, POP3,
SMTP, IM, NNTP, IMAPS, POP3S, SMTPS, or HTTPS).
Status The reason the file was quarantined: infected, heuristics, or blocked.
Status Specific information related to the status, for example, “File is infected with
Description “W32/Klez.h”” or “File was stopped by file block pattern.”
DC Duplicate count. A count of how many duplicates of the same file were
quarantined. A rapidly increasing number can indicate a virus outbreak.
TTL Time to live in the format hh:mm. When the TTL elapses, the FortiGate unit
labels the file as EXP under the TTL heading. In the case of duplicate files, each
duplicate found refreshes the TTL.
The TTL information is not available if the files are quarantined on a
FortiAnalyzer unit.
Upload status Y indicates the file has been uploaded to Fortinet for analysis, N indicates the
file has not been uploaded.
This option is available only if the FortiGate unit has a local hard disk.
Download icon Select to download the corresponding file in its original format.
This option is available only if the FortiGate unit has a local hard disk.
Submit icon Select to upload a suspicious file to Fortinet for analysis.
This option is available only if the FortiGate unit has a local hard disk.
Note: Duplicates of files (based on the checksum) are not stored, only counted. The TTL
value and the duplicate count are updated each time a duplicate of a file is found.
Note: Make sure to check the Report Title of the report displayed on the FortiAnalyzer page
before printing.
FortiAnalyzer reports are available only when in a VDOM.
The following procedure describes how to clone a report schedule. When you clone a
report schedule, a duplicate of the original is used as a basis for a new one.
To view the list of report schedules, go to Log&Report > Report Config.
To configure a report schedule, go to Log&Report > Report Config, select Create New,
enter the appropriate information and then select OK.
Delete
Edit
Clone
Schedule Select one of the following to have the report generate once only,
daily, weekly, or monthly at a specified date or time period.
Once Select to have the report generated only once.
Daily Select to generate the report every date at the same time, and then
enter the hour and minute time period for the report. The format is
hh:mm.
These Days Select to generate the report on specified days of the week, and then
select the days of the week check boxes.
These Dates Select to generate the report on a specific day or days of the month,
and then enter the days with a comma to separate them. For example,
if you want to generate the report on the first day, the 21st day and
30th day, enter: 1, 21, 30.
Log Data Filtering You can specify the following variables for the report:
Virtual Domain Select to create a report based on virtual domains. Enter a specific
virtual domain to include in the report.
User Select to create a report based on a network user. Enter the user or
users in the field, separated by spaces. If a name or group name
contains a space, if should be specified between quotes, for example,
“user 1”.
Group Select to create a report based on a group of network users, defined
locally. Enter the name of the group or groups in the field.
LDAP Query Select the LDAP Query check box and then select an LDAP directory
or Windows Active Directory group from the list.
Time Period Select to include the time period of the logs to include in the report.
Relative to Report Select a time period from the list. For example, this year.
Runtime
Specify Select to specify the date, day, year and time for the report to run.
From – Select the beginning date and time of the log time range.
To – Select the ending date and time of the log time range.
Output Select the format you want the report to be in and if you want to apply
an output template.
Output Types Select the type of file format for the generated report. You can choose
from PDF, MS Word, Text, and MHT.
Email/Upload Select the check box if you want to apply a report output template from
the list.
This list is empty if a report output template does not exist. For more
information, see the FortiAnalyzer Administration Guide.
Note: FortiAnalyzer reports do not appear if the FortiGate unit is not connected to a
FortiAnalyzer unit, or if the FortiAnalyzer unit is not running firmware 3.0 or higher.
The report updates at the configured time. To update the report immediately, select the
Refresh icon near the right end of the widget title bar. You can also select the Edit icon
to change the report update schedule.
Report Files The name of the generated report. Select the name to view the report.
You can also select the expand arrow to view the report and the select the rolled
report to view the report.
Date The date the report was generated on.
Size(bytes) The size of the report in bytes.
Other Formats Displays the formats PDF, RTF or MHT or all if these formats were chosen in the
report schedule.
Time Period Select a time range to view for the graphical analysis. You can choose from
one day, three days, one week or one month. The default is one day. When
you refresh your browser or go to a different menu, the settings revert to
default.
Services By default all services are selected. When you refresh your browser or go to
a different menu, all services revert to default settings. Clear the check
boxes beside the services you do not want to include in the graphical
analysis.
• Browsing
• DNS
• Email
• FTP
• Gaming
• Instant Messaging
• Newsgroups
• P2P
• Streaming
• TFTP
• VoIP
• Generic TCP
• Generic UDP
• Generic ICMP
• Generic IP
Bandwidth Per This bar graph is based on what services you select, and is updated when
Service you select Apply. The graph is based on date and time, which is the current
date and time.
Top Protocols This bar graph displays the traffic volume for various protocols, in
Ordered by Total decreasing order of volume. The bar graph does not update when you
Volume select different services and then select Apply.
The report is not updated in real-time. You can refresh the report by selecting the Memory
tab.
Note: The data used to present the graphs is stored in the FortiGate system memory.
When the FortiGate unit is reset or rebooted, the data is erased.
Note: If you require a more specific and detailed report, you can configure a simple report
from the FortiAnalyzer web-based manager or CLI. The FortiAnalyzer unit can generate
over 140 different reports providing you with more options than the FortiGate unit provides.
If you need to configure a FortiAnalyzer report schedule, see “Configuring FortiAnalyzer
report schedules” on page 721.
Log types
The FortiGate unit provides a wide range of features to log, enabling you to better monitor
activity that is occurring on your network. For example, you can enable logging of IM/P2P
features, to obtain detailed information on the activity occurring on your network where
IM/P2P programs are used.
Before enabling FortiGate features, you need to configure what type of logging device will
store the logs. For more information, see “Configuring how a FortiGate unit stores logs” on
page 704.
This topic also provides details on each log type and explains how to enable logging of the
log type.
Note: If the FortiGate unit is in transparent mode, certain settings and options for logging
may not be available because they are not available in transparent mode. For example,
SSL VPN events are not available in transparent mode.
Traffic log
The Traffic log records all the traffic to and through the FortiGate interfaces. You can
configure logging of traffic controlled by firewall policies and for traffic between any source
and destination addresses. You can also filter to customize the traffic logged:
• Allowed traffic – The FortiGate unit logs all traffic that is allowed according to the
firewall policy settings.
• Violation traffic – The FortiGate unit logs all traffic that violates the firewall policy
settings.
If you are logging “other-traffic”, the FortiGate unit will incur a higher system load because
“other-traffic” logs log individual traffic packets. Fortinet recommends logging firewall
policy traffic since it minimizes the load. Logging “other-traffic” is disabled by default.
Firewall policy traffic logging records the traffic that is both permitted and denied by the
firewall policy, based on the protection profile. Firewall policy traffic logging records
packets that match the policy.
Note: You need to set the logging severity level to Notification when configuring a logging
location to record traffic log messages. Traffic log messages generally have a severity level
no higher than Notification. If VDOMs are in transparent mode, make sure that VDOM
allows access for enabling traffic logs.
next
edit port2
set log enable
end
4 Use the following command to enable logging of other traffic.
config log syslogd filter
set other-traffic enable
end
5 Go to UTM > Intrusion Protection > IPS Sensor and select Create New to add an IPS
Sensor.
Edit the IPS Sensor and select Add Pre-defined Override to add the following
predefined IPS signatures to the sensor.
• Invalid.Protocol.Header
• TCP.Bad.Flags
• TCP.Invalid.Packet.Size
Enable each of these signatures, set Action to Block and enable Logging.
6 Enter the following CLI commands to add a DoS policy (called an interface policy in the
CLI) that includes the IPS Sensor.
config firewall interface-policy
edit 1
set interface <interface_name>
set srcaddr all
set dstaddr all
set service ANY
set ips-sensor-status enable
set ips-sensor <sensor_name>
end
Where <sensor_name> is the name of the IPS sensor added above.
Index
Symbols DHCP relay agent, 201
DHCP server, 201
Directory Service server, 654, 655
Numerics Directory Service user groups, 660
802.3ad aggregate interface DoS sensors, 538
creating, 159 Dynamic DNS on an interface, 163
dynamic virtual IP, 434
A email filter log, 713
email filtering options, 485
accept action event logs, 711
firewall policy, 683, 684 fail-open, IPS, 540
access profile, See admin profile, 257 firewall address, 397
accessing logs stored in hard disk, 716 firewall address group, 399
action firewall policy, 366, 367, 418, 419
email filter banned word, 564 firewall policy traffic logging, 728
email filter IP address, 567 firewall policy, modem connections, 175
firewall policy, 367 firewall protection profile, 474
action type firewall schedule, 411
email filter email address, 569 firewall service group, 408
firewall user groups, 659
active sessions
firewall virtual IP, 421
HA statistics, 212
firmware upgrade, 295
add signature to outgoing email firmware version, 87
protection profile, 479 FortiAnalyzer report schedules, 721
adding, configuring or defining FortiGuard override options for a user group, 664
admin profile, 258 FortiGuard Web Filtering options, 483
administrative access to interface, 165 FortiWiFi-50B settings, 190, 191
administrator account, 244 FortiWiFi-60B settings, 190, 191
administrator password, 246 gateway for default route, 320
administrator settings, 261 HA, 205
antispam advanced options, 570 HA device priority, 212
antispam email address list, 568, 570 HA subordinate unit host name, 212
antispam IP address, 567 health check monitor, 451
antispam IP address list, 566 IM/P2P/VoIP applications, older versions, 646
antivirus file filter list, 515, 516 interface settings, 151
antivirus file patterns, 516 inter-VDOM links, 136
antivirus file quarantine, 516 IP pool, 440
antivirus log, 713 IPS log (attack), 714
antivirus quarantine options, 518 IPS options, 480
antivirus scanning options, 477 IPS sensor filters, 532
application control options, 489 IPS sensors, 529
attack log (IPS), 714 IPSec encryption policy, 376
authentication settings, 667 IPSec VPN concentrator, 617
authentication, firewall policy, 372 IPSec VPN phase 1, 606
autosubmit list, 517 IPSec VPN phase 1 advanced options, 608
banned word list, 563, 564 IPSec VPN phase 2, 611
basic traffic report, graphical view, 727 IPSec VPN phase 2 advanced options, 611
BFD, 351 IPv6 support, 264
BFD on BGP, 352 LDAP authentication, 249
BFD on OSPF, 353 LDAP server, 649, 650
BGP settings, 346 license key, 311
CA certificates, 286 local ratings, 556
Certificate Revocation List (CRL), 288 local URL block categories, 555
cipher suite, 627 local user account, 644
combined IP pool and virtual IP, 440 log message display, 717
custom firewall service, 406 logging options, 489
custom service, firewall, 406 logging to a FortiAnalyzer unit, 704
custom signatures, 527 logging to a FortiGuard Analysis server, 706
customized CLI console, 68 logging to a Syslog server, 707
DHCP interface settings, 161 logging to memory, 708
backup mode C
modem, 173
band CA certificates
wireless setting, 191 importing, 286
bandwidth viewing, 286
guaranteed, 418 catalog
maximum, 418, 676, 681 banned word, 562
banned word content filter, 545
character set, 483 email address back/white list, 568
IP address black/white list, 565
banned word (email filter)
URL filter, 548
action, 564
viewing file pattern, 514
adding words to the banned word list, 564
catalog, 562 category
language, 564 protection profile, 485
pattern, 564 web category report, 558
banned word (spam filter) category block
language, 564 configuration options, 552
list, 563 reports, 557
pattern, 564 central management, 260
pattern type, 564 revision control, 261
banned word check Certificate Name
protection profile, 487 IPSec VPN, phase 1, 607
banned word list certificate, security. See system certificate
creating new, 563 certificate, server, 627
banned word list catalog certificate. See system certificates
viewing, 562 channel
beacon interval wireless setting, 191
wireless setting, 191 character set
BFD converting, 483
configuring on BGP, 352 DLP, 483
configuring on OSPF, 353 email filter, 483
disabling, 352 web filtering, 483
BGP CIDR, 28, 266, 395, 679
AS, 346 cipher suite
flap, 346 SSL VPN, 627
graceful restart, 346 CLI, 47
MED, 346 admin profile, 256
RFC 1771, 346 connecting to from the web-based manager, 51
service, 402 CLI command
settings, viewing, 346 PPTP tunnel setup, 623
stabilizing the network, 346 CLI configuration
black/white list, 565 antivirus, 520
blackhole route, 315 customizing CLI console, 68
blackhole routing, 158 using in web-based manager, 79
block, 504 web category block, 557
block login (IM) CLI console, 79
protection profile, 489 client certificates
blocked SSL VPN, 627
web category report, 558 client comforting, 479
Boot Strap Router (BSR), 348 cluster member, 209
BOOTP, 203 cluster members list, 210
branch, 508 priority, 210
bridge mode, 99 role, 210
bridge module cluster unit
AMC, 99 disconnecting from a cluster, 212
button bar code, 407
features, 51 column settings, 718
configuring, 61
using with filters, 63
comfort clients
protection profile, 478
comforting D
client, 479
command line interface (CLI), 24 dashboard, 47, 67
comments dashboard statistics
firewall policy, 372, 379 protection profile, 488
comments, documentation, 30 data encryption
concentrator wireless setting, 193
adding, 617 data leak prevention sensor, 488
equivalent for route-based VPN, 604 data leak protection, 575
IPSec tunnel mode, 617 compound rule, 591
IPSec VPN, policy-based, 617 rule, 586
Concentrator Name sensor, 575
IPSec VPN, concentrator, 617 date
config antivirus heuristic quarantine files list, 720
CLI command, 520 daylight saving changes, 86
configuration DC
backing up the configuration, 52 quarantine files list, 721
configuring DCE-RPC
WAN optimization peer, 680 firewall service, 402
WAN optimization rule, 675 Dead Peer Detection
connecting IPSec VPN, phase 1, 610
modem, dialup account, 175 default
web-based manager, 48 password, 24
conservation mode, 220 default gateway, 318
conserve mode, 76 default route, 318
contact information Designated Routers (DR), 348
SNMP, 214 destination
contacting customer support, 51 firewall policy, 367, 370, 375, 378
content archiving destination IP address
DLP archiving, 580 system status, 83
content block destination NAT
catalog, 545 SIP, 496
web filter, 544 destination network address translation (DNAT)
content filtering virtual IPs, 423, 424
character set, 483 destination port, custom services, 407
content filtering mode device priority
HTTPS, 477 HA, 207
content scanning subordinate unit, 212
SSL, 469 DH Group
content streams IPSec VPN, phase 1, 610
replacement messages, 225 IPSec VPN, phase 2, 612
CPU load, 132 DHCP
CPU usage and IP Pools, 371
HA statistics, 211 configuring relay agent, 201
CRL (Certificate Revocation List) configuring server, 201
importing, 288 servers and relays, 199
viewing, 287 service, 200
custom service system, 199
adding, 406 transparent mode, 199
adding a TCP or UDP custom service, 406 viewing address leases, 203
list, 406 DHCP (Dynamic Host Configuration Protocol)
custom signatures configuring on an interface, 161
intrusion protection, 527 service, 402
viewing, 527 DHCP6
customer service, 29, 132 service, 402
customer support DHCP-IPSec
contacting, 51 IPSec VPN, phase 2, 613
customized GUI diagnose
PPTP tunnel setup, 621 commands, 51
CVSPSERVER, concurrent versions system proxy server, diagram
402 topology viewer, 107
cx4, 99
hostname Internet-Locator-Service
cluster members list, 210 service, 403
HTTP, 451 inter-VDOM links, 136
service, 403 introduction
virus scanning large files, 521 Fortinet documentation, 30
HTTPS, 47, 239 intrusion detected
service, 403 HA statistics, 212
HTTPS content filtering mode, 477 intrusion protection
hub-and-spoke custom signature list, 527
IPSec VPN (see also concentrator), 604 DoS sensor list, 538
DoS sensor, protection profile, 480
I fail-open, CLI command for IPS, 540
filter, 532
ICMP custom service, 407 IPS sensor list, 529
code, 407 IPS sensor, protection profile, 480
protocol type, 407 predefined signature list, 525
type, 407 protection profile options, 480
ICMP echo request, 451 protocol decoder, 528
ICMP_ANY protocol decoder list, 528
service, 403 signatures, 524
ID socket-size, CLI command for IPS, 540
firewall policy, 367 Intrusion Protection definitions, 91
idle timeout IP
changing for the web-based manager, 50 virtual IP, 425
IEEE 802.11a, channels, 188 IP address
IEEE 802.11b, channels, 189 action, antispam, 567
IEEE 802.11g, channels, 189 antispam black/white list catalog, 565
IEEE 802.3ad, 159 BWL check, protection profile, 487
IKE defining PPTP range, 621, 623
service, 403 email filter, 565
IPSec VPN, phase 1, 606
IMAP
list, email filter, 566
service, 403
PPTP user group, 621, 623
inbound NAT
IP address, configuring secondary, 167
IPSec firewall policy, 376
IP custom service, 408
index number, 28
protocol number, 408
INFO_ADDRESS protocol type, 408
service, 403
IP pool
INFO_REQUEST adding, 440
service, 403 configuring, 440
insert policy before creating new, 440
firewall policy, 367, 676 DHCP, 371
inspection end IP, 440
SSL, 469 fixed port, 438
installation, 24 IP range/subnet, 440, 441
interface list, 439
adding system settings, 151 name, 440, 441
administrative access, 157, 165, 168 options, 440
administrative status, 149 PPPoE, 371
configuring administrative access, 165 proxy ARP, 426, 446
GRE, 338 SIP, 497
loopback, 149, 316 start IP, 440
modem, configuring, 170 transparent mode, 442
MTU, 157 IP range/subnet
proxy ARP, 426, 446 firewall address, 398
wireless, 187 IP pool, 440, 441
WLAN, 187 IPS
Interface Mode, 151 see intrusion protection
interface monitoring, 208 IPS sensor
HA, 208 filter, 532
internet browsing options, protection profile, 480
IPSec VPN configuration, 616 IPS sensors
creating, 529
N one-time schedule
adding, 413
Name configuring, 413
IP pool, 440, 441 creating new, 412
IPSec VPN, manual key, 615 list, 412
IPSec VPN, phase 1, 606 start, 413
IPSec VPN, phase 2, 611 stop, 413
NAPT, 385 online help
NAT content pane, 53
in transparent mode, 442 keyboard shortcuts, 55
inbound, IPSec firewall policy, 376 navigation pane, 53
multicast, 350 search, 54
NAPT, 385 using FortiGate online help, 52
outbound, IPSec firewall policy, 376 operation mode, 24, 238
port selection, 385 wireless setting, 191
preserving SIP NAT IP, 505 operational history
push update, 309 viewing, 90
SIP, 495 optimize
SIP contact headers, 506 antivirus, 520
symmetric, 424
OSPF
NAT virtual IP area ID, 344
adding for single IP address, 428 AS, 341
adding static NAT virtual IP for IP address range, 429 authentication, 344, 345
Nat-traversal Dead Interval, 346
IPSec VPN, phase 1, 610 dead packets, 346
netmask GRE, 345
administrator account, 246 Hello Interval, 346
NetMeeting Hello protocol, 338
service, 403 interface definition, 344
network IPSec, 345
topology viewer, 107 link-state, 338
Network Address Port Translation, 385 LSA, 345
network address translation (NAT), 422 multiple interface parameter sets, 345
Network Attached Storage (NAS), 248 neighbor, 338
Network Time Protocol, 87 network, 341
network address space, 345
network utilization
NSSA, 343, 360
HA statistics, 212
path cost, 339
NFS regular area, 343
service, 403 service, 404
NNTP settings, 340
service, 403 stub, 343
not registered virtual lan, 344
subscription, 303 virtual link, 343
notification, 709 VLAN, 345
Not-so-stubby Area (NSSA), 343 OSPF AS, 338
not-so-stubby area (NSSA), 360 defining, 339
Novel edirectory, 654 outbound NAT
NTP, 87 IPSec firewall policy, 376
service, 403 override server
sync interval, 87 adding, 308
synchronizing with an NTP server, 87 oversize threshold, 478
oversized file/email
O protection profile, 478
object identifier (OID), 221
OCSP certificates
P
importing, 285 P1 Proposal
OFTP connection, 74 IPSec phase 1, 609
ONC-RPC P2 Proposal
service, 404 IPSec VPN, phase 2, 612
packets
VDOM, 126