Fortigate Cookbook 52

FortiOS 5.
The FortiGate Cookbook 5.2

November-20-15
Copyright 2015 Fortinet, Inc. All rights reserved. Fortinet, FortiGate, FortiCare and FortiGuard, and
certain other marks are registered trademarks of Fortinet, Inc., in the U.S. and other jurisdictions, and other
Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or
company names may be trademarks of their respective owners. Performance and other metrics contained herein
were attained in internal lab tests under ideal conditions, and actual performance and other results may vary.
Network variables, different network environments and other conditions may affect performance results. Nothing
herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or
implied, except to the extent Fortinet enters a binding written contract, signed by Fortinets General Counsel, with
a purchaser that expressly warrants that the identified product will perform according to certain expresslyidentified performance metrics and, in such event, only the specific performance metrics expressly identified in
such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to
performance in the same ideal conditions as in Fortinets internal lab tests. In no event does Fortinet make any
commitment related to future deliverables, features, or development, and circumstances may change such that
any forward-looking statements herein are not accurate. Fortinet disclaims in full any covenants,
representations,and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to
change, modify, transfer, or otherwise revise this publication without notice, and the most current version of the
publication shall be applicable.
ii
Fortinet Cookbook - http://cookbook.fortinet.com

Fortinet Knowledge Base - http://kb.fortinet.com
Technical Documentation - http://docs.fortinet.com
Video Tutorials - http://video.fortinet.com
Training Services - http://campus.training.fortinet.com
Technical Support - https://support.fortinet.com
Please report errors or omissions in this or any Fortinet technical document to techdoc@fortinet.com.
iii
Table of Contents
Change Log
Introduction
Tips
10
Getting Started
12
Choosing your FortiGate's switch mode
14
Installing a FortiGate in NAT/Route mode
15
Installing a FortiGate in Transparent mode
21
Quick installation using DHCP
27
Redundant Internet connections
31
Troubleshooting your FortiGate installation
36
FortiGate registration and basic settings
40
Updating your FortiGates firmware
45
Setting up FortiGuard services
49
FortiGuard troubleshooting
55
Logging FortiGate traffic
56
Logging with FortiCloud
60
Troubleshooting FortiGate logging
65
Creating security policies
66
Limited access administrator accounts
72
Port pairing in Transparent mode
77
How to upgrade one unit in an HA cluster
81
Port forwarding
87
FortiGuard DDNS
93
SNMP monitoring
96
Packet capture
103
VDOM configuration
107
High Availability with two FortiGates
115
AirPlay for Apple TV
122
iv
Protect a web server withDMZ
127
Traffic shaping for VoIP
132
Creating an IPv6 interface using SLAAC
141
FortiExtender installation
144
Remotely accessing FortiRecorder through a FortiGate
150
Managing a FortiSwitch with a FortiGate
162
Authentication
User and device authentication
166
Excluding users from security scanning
174
FSSO in Polling mode
178
Two-factor authentication with FortiToken Mobile
184
Security
164
191
FortiOS AntiVirus inspection modes
193
AntiVirus with FortiSandbox
195
Blocking Ultrasurf
201
Blocking P2P traffic and YouTube applications
205
Blocking Windows XP traffic
212
Blocking and monitoring Tor traffic
217
Controlling access to Apple's App Store
222
Restricting online gaming to evenings
227
Preventing data leaks
233
Prevent credit card numbers from being leaked
238
Protecting a web server
242
Logging DNS domain lookups
247
Why you should use SSL inspection
252
Preventing certificate warnings
255
Exempting Google from SSLinspection
268
Blocking Facebook
273
Blocking adult/mature content with Google SafeSearch
278
Web rating overrides
287
Web filtering using quotas
292
Blocking Google access for consumer accounts
297
Overriding a web filter profile
300
Troubleshooting web filtering
305
VPNs
306
IPsec VPN with FortiClient
308
IPsec VPNfor iOS devices
314
IPsec VPN with the native Mac OS client
323
IPsec VPN with two-factor authentication
330
IPsec VPNwith external DHCP service
341
Site-to-site IPsec VPN with two FortiGates
349
Site-to-site IPsec VPN with overlapping subnets
355
IPsec VPN to Microsoft Azure
362
Remote Internet browsing using a VPN
372
Remote browsing using site-to-site IPsec VPN
379
IPsec troubleshooting
386
SSLVPN for remote users
388
SSL VPN using FortiClient for iOS
399
SSLVPNfor Windows Phone 8.1
406
SSLVPN with certificate authentication
412
SSLVPNwith RADIUS authentication
423
RADIUS authentication for SSLVPN with FortiAuthenticator
436
LDAP authentication for SSLVPNwith FortiAuthenticator
442
SSLVPNremote browsing with LDAPauthentication
449
SMStwo-factor authentication for SSLVPN
455
SSL VPN troubleshooting
462
WiFi
Setting up WiFi with FortiAP
464
466
vi
Setting up a WiFi bridge with a FortiAP
471
Combining WiFi and wired networks with a software switch
475
WiFi network with external DHCP service
479
Providing remote access to the office and Internet
483
Extending WiFi range with mesh topology
489
Explicit proxy with web caching
495
Guest WiFi accounts
502
Captive portal WiFi access control
507
WP2A WiFi access control
512
MAC access control
516
BYOD scheduling
521
BYOD for a user with multiple wireless devices
525
WiFi RADIUS authentication with FortiAuthenticator
529
Using an external captive portal for WiFi security
534
Assigning WiFi users to VLANs dynamically
540
WiFi with Wireless Single Sign-on
548
RSSO WiFi access control
555
Social WiFi Captive Portal with FortiAuthenticator (Facebook)
566
Social WiFi Captive Portal with FortiAuthenticator (Twitter)
580
Social WiFi Captive Portal with FortiAuthenticator (Google+)
589
Social WiFi Captive Portal with FortiAuthenticator (LinkedIn)
600
Social WiFi Captive Portal with FortiAuthenticator (Form-based)
612
Expert
vii
619
High Availability with FGCP
620
Redundant architecture
628
SLBC setup with one FortiController-5103B
641
SLBC Active-Passive setup with two FortiController-5103Bs
646
SLBC Active-Passive with two FortiController-5103Bs and two chassis
654
SLBC Dual Mode with two FortiController-5103Bs
669
SLBC Active-Passive with four FortiController-5103Bs and two chassis
677
SLBC Dual Mode with two FortiController-5903Cs
696
BGP over a dynamic IPsec VPN
719
OSPF over dynamic IPsec VPN
725
Single Sign-on using LDAPand FSSOagent in advanced mode
732
Single Sign-On using FSSO agent in advanced mode and FortiAuthenticator
741
SSOusing a FortiGate, FortiAuthenticator, and DCPolling
753
Hub-and-spoke VPN using quick mode selectors
760
Glossary
770
viii
Change Log
Date
Change description
Nov 20, 2015
Added and updated recipes throughout.
Oct 2, 2015
Corrected recipe Preventing certificate warnings.
May 12, 2015
Initial publication
Change Log
Introduction
FortiGate is a network security appliance that can apply a number of features to your network traffic, providing a
consolidated security solution to match the needs of any network, big or small.
The FortiGate recipes is divided into the following sections:
l
Getting Started: recipes to help you start using your FortiGate.
Authentication: recipes about authenticating users and devices on your network.
Security: recipes about using a FortiGate to protect your network.
VPNs: recipes about virtual private networks (VPNs), including authentication methods.
WiFi: recipes about managing a wireless network with your FortiGate.
Expert: recipes about advanced FortiGate configurations for users with a higher degree of background
knowledge.
This version of the complete FortiGate cookbook was written using FortiOS 5.2.4.
Introduction
Tips
Before you get started, here are a few tips about using the FortiGate Cookbook:
Understanding the basics

Some basic steps, such as logging intoyour FortiGate, are not included in most recipes. This information can be
found in the QuickStart guide for your product.
Screenshots vs. text

The FortiGate Cookbook uses both screenshots and text to explain the steps of each example. The screenshots
display the entire configuration, while the text highlights key details (i.e. the settings that are strictly necessary for
the configuration) and provides additional information. To get the most out of the FortiGate Cookbook, start with
the screenshots and then read the text for more details.
Model and firmware

GUI menus, options, and interface names may vary depending on the which model you are using and the firmware
build.
For example, some FortiGate models do not have themenu optionRouter > Static > Static Routes.
Ports
The specific ports being used in the documentation are chosen as examples. When you are configuring your unit,
you can substitute your own ports, provided that they have the same function.
For example, in most recipes, wan1 is the port used to provide the FortiGate with access to the Internet. If your
FortiGate uses a different port for this function, you should use that port in the parts of the configuration that the
recipe uses wan1.
IP addresses and object names

IP addresses are sometimes shown in diagrams to make it easier to see the source of the addresses used in the
recipe. When you are configuring your product, substitute your own addresses. You should also use your own
named for any objects, including user accounts, that are created as part of the recipe. Make names as specific as
possible, to make it easier to determine later what the object is used for.
Tips
10
Text elements
Bold text indicates the name of a GUI field or feature. When required, italic text indicates information that you
must enter.
Italic text is also used for notes, which contain information that you may find useful while using a recipe.
Selecting OK/Apply
Always select OK or Apply when you complete a GUI step. Because this must be done frequently, it is an
assumed step and is not included in most recipes.
IPv4 vs IPv6 policies

Most recipes in the FortiGate Cookbook use IPv4 security policies. However, the majority of them could also be
done using IPv6 policies. If you wish to create an IPv6 policy, go to Policy & Objects > Policy > IPv6.
Turning on FortiOS features

Some FortiOS features can be turned off, which means they will not appear in the GUI. If an option required for a
recipe does not appear, go to System > Config > Features and make sure that option is turned on.
Also, on some FortiGate models, certain features are only available using the CLI. For more information about
this, see theFeature/Platform Matrix.
11
Tips
Getting Started
This section contains information about basic tasks to get a FortiGate unit up and running, including installation,
as well common roles and configurations a FortiGate unit can have in your network.
Installation
l
Setting up your FortiGate

l
Common configurations
l
Port forwarding
FortiGuard DDNS
SNMP monitoring
Packet capture
VDOM configuration
Getting Started
12
Using a FortiGate with other Fortinet products
13
Getting Started

This section contains information to help you determine which internal switch mode your FortiGate should use, a
decision that should be made before the FortiGate is installed.
What is the internal switch mode?

The internal switch mode determines how the FortiGates physical ports are managed by the FortiGate. The two
main modes are Switch mode and Interface mode.
What are Switch mode and Interface mode and why are they used?
In Switch mode, all the internal interfaces are part of the same subnet and treated as a single interface, called
either lan or internalby default, depending on the FortiGate model. Switch mode is used when the network layout
is basic, with most users being on the same subnet.
In Interface mode, the physical interfaces of the FortiGate unit are handled individually, with each interface having
its own IP address. Interfaces can also be combined by configuring them as part of either hardware or software
switches, which allow multiple interfaces to be treated as a single interface. This mode is ideal for complex
networks that use different subnets to compartmentalize the network traffic.
Which mode is your FortiGate in by default?

The default mode that a FortiGate starts in varies depending on the model. To determine which mode your
FortiGate unit is in, go to System > Network > Interfaces. Locate the
lan or internal interface. If the interface is listed as a Physical Interface in the Type column, then your FortiGate
is in Switch mode. If the interface is a Hardware Switch, then your FortiGate is in Interface mode.
How do you change the mode?

If you need to change the mode your FortiGate unit is in, first make sure that none of the physical ports that make
up the lan or internal interface are referenced in the FortiGate configuration. Then go to System > Dashboard >
Status and enter either of the following commands into the CLI Console:
1. Command to change the FortiGate to switch mode:
config system global
set internal-switch-mode switch
exit
2. Command to change the FortiGate to interface mode:
set internal-switch-mode interface
exit
Getting Started
14
In this example, you will learn how to connect and configure a new FortiGate unit in NAT/Route mode to securely
connect a private network to the Internet.
In NAT/Route mode, a FortiGate unit is installed as a gateway or router between two networks. In most cases, it
is used between a private network and the Internet. This allows the FortiGate to hide the IP addresses of the
private network using network address translation (NAT).
If you have not already done so, ensure that your FortiGate is using the correct internal switch mode. For more
information, see Choosing your FortiGate's switch mode.
A video of this recipe is available here.
Getting Started
15
1. Connecting the network devices and logging onto the FortiGate

Connect the FortiGates Internet-facing
interface (typically WAN1) to your ISPsupplied equipment and Connect a PC to
the FortiGate using an internal port
(typically port 1).
Power on the ISPs equipment, the
FortiGate unit, and the PC on the internal
network.
From the PC on the internal network,

connect to the FortiGates web-based
manager using either FortiExplorer or an
Internet browser (for information about
connecting to the web-based manager,
please see your models QuickStart
Guide).
Login using an admin account (the
default admin account has the username
admin and no password).
Getting Started
16
2. Configuring the FortiGates interfaces

Go to System > Network > Interfaces
and edit the Internet-facing interface.
If your FortiGateis directly connecting to
your ISP, set Addressing Mode to
Manualand setthe IP/Netmask to
thepublic IP address your ISP has
provided you with.
Ifhave some ISP equipment between
your FortiGate and the Internet (for
example, a router),then the wan1 IP will
also use a private IP assigned by the ISP
equipment. If this equipmentuses
DHCP, setAddressing Mode
toDHCPto get an IP assigned to the
interface.
If the ISP equipment does not use
DHCP, your ISP can provide you with
the correct private IP to use for the
interface.
Edit the internal interface (called lan on
some FortiGate models).
Set Addressing Mode to Manual and
set the IP/Netmask to the private IP
address you wish to use for the
FortiGate.
17
Getting Started
3. Adding a default route

Go to Router > Static > Static Routes
(or System > Network > Routing,
depending on your FortiGate model) and
create a new route.
Set the Destination IP/Mask to
0.0.0.0/0.0.0.0, the Device to the
Internet-facing interface, and the
Gateway to the gateway (or default
route) provided by your ISP or to the next
hop router, depending on your network
requirements.
A default route always has a Destination

IP/Mask of 0.0.0.0/0.0.0.0. Normally,
you would have only one default route. If
the static route list already contains a
default route, you can edit it or delete it
and add a new one.
4. (Optional) Setting the FortiGates DNS servers

The FortiGate units DNS Settings are
set to use FortiGuard DNS servers by
default, which is sufficient for most
networks. However, if you need to
change the DNS servers, go to System
> Network > DNS and add Primary and
Secondary DNS servers.
Getting Started
18
5. Creating a policy to allow traffic from the internal network to the Internet
Some FortiGate models include an IPv4 security policy in the default configuration. If you have one of these
models, edit it to include the logging options shown below, then proceed to the results section.
Go to Policy & Objects > Policy > IPv4
and create a new policy (if your network
uses IPv6 addresses, go to Policy &
Objects > Policy > IPv6).
Set the Incoming Interface to the
internal interface and the Outgoing
Interface to the Internet-facing interface.
Make sure the Action is set to ACCEPT.
Turn on NAT and make sure Use
Destination Interface Address is
selected (later versions of FortiOS 5.2
call this option Use Outgoing Interface
Address).
Scroll down to view the Logging
Options. In order to view the results
later, enable Log Allowed Traffic and
select All Sessions.
19
Getting Started
6. Results
You can now browse the Internet using
any computer that connects to the
FortiGates internal interface.
You can view information about the
traffic being processed by your FortiGate
by going to System > FortiView > All
Sessions and finding traffic that has the
internal interface as the Src Interface
and the Internet-facing interface as the
Dst Interface.
If these two columns are not shown,
right-click on the title row, select Src
Interface and Dst Interface from the
dropdown menu, and then select Apply.
For further reading, check out Installing a

FortiGate in NAT/Route Mode in the
FortiOS 5.2 Handbook.
Getting Started
20
In this example, you will learn how to connect and configure a new FortiGate unit in Transparent mode to securely
connect a private network to the Internet. In Transparent mode, the FortiGate applies security scanning to traffic
without applying routing or network address translation (NAT).
Warning: Changing to Transparent mode removes most configuration changes made in NAT/Route mode. To
keep your current NAT/Route mode configuration, backup the configuration using the System Information
widget, found at System > Dashboard > Status.
Getting Started
21
1. Changing the FortiGates operation mode

Go to System > Dashboard > Status
and locate the System Information
widget.
Beside Operation Mode, select
Change.
Set the Operation Mode to

Transparent. Set the Management
IP/Netmask and Default Gateway to
connect the FortiGate unit to the internal
network.
You can now access the GUI by
browsing to the Management IP (in the
example, you would browse to
http://172.20.120.122).
2. (Optional) Setting the FortiGates DNS servers

The FortiGate units DNS Settings are
set to use FortiGuard DNS servers by
default, which is sufficient for most
networks. However, if you need to
change the DNS servers, go to System
> Network > DNS and add Primary and
Secondary DNS servers.
Getting Started
22
3. Creating a policy to allow traffic from the internal network to the Internet
and create a new policy (if your network
uses IPv6 addresses, go to Policy &
Objects > Policy > IPv6).
Set the Incoming Interface to the an
available external interface (typically
port 1) and the Outgoing Interface to
the Internet-facing interface (typically
WAN1).
It is recommended to avoid using any

security profiles until after you have
successfully installed the FortiGate
unit. After the installation is verified, you
can apply any required security profiles.

23
Getting Started
4. Connecting the network devices

and locate the System Resources
widget. Select Shutdown to power off
the FortiGate unit.
Alternatively, you can enter the
following command in the CLI Console
(also found by going to
System > Dashboard > Status):
execute shutdown
Wait until all the lights, except for the
power light, on your FortiGate have
turned off. If your FortiGate has a
power button, use it to turn the unit off.
Otherwise, unplug the unit.
You can now connect the FortiGate unit
between the internal network and the
router.
Connect the wan1 interface to the router
internal interface and connect the
internal network to the FortiGate internal
interface port.
Power on the FortiGate unit.
Getting Started
24
5. Results
You can now browse the Internet using
any computer that connects to the
FortiGates internal interface.
You can view information about the
traffic being processed by your
FortiGate by going to System >
FortiView > All Sessions and finding
traffic that has port 1 as the Src
Interface and the Internet-facing
interface as the Dst Interface.
25
Getting Started
If these two columns are not shown,

select Column Settings and move Src
Interface and Dst Interface to the list
of fields to be shown.
For further reading, check out Installation in

the FortiOS 5.2 Handbook.
Getting Started
26
In this example, you will use DHCP and your FortiGate's default configuration to securely connect your internal
network to the Internet in two simple steps.
This recipe has the following requirements:
l
l
An ISP that provides connectivity with DHCP and accepts DHCP requests without authentication.
A FortiGate with a default configuration that includes a DHCP server on the lan (or internal) interface and a
security policy that securely allows all sessions from the Internal network to reach the Internet.
Your network uses IPv4 to connect to the FortiGate and Internet.
Getting Started
27
1. Connecting the FortiGate to your ISP and the internal network

Connect the FortiGate wan interface to
your ISP-supplied equipment.
Connect the internal network to the
FortiGate's default lan or internal
interface.
Turn on the ISPs equipment, the
FortiGate unit, and the PCs on the
internal network.
2. Configuring your PCs to use DHCP

Windows Vista/7/8:
Go to Network and Sharing Center and
select Local Area Connections. Select
Properties.
Select Internet Protocol Version 4
(TCP/IPv4), then select Properties.
Select Obtain an IP address
automatically and Obtain DNS server
address automatically.
Getting Started
28
Mac OS X
Go to Network Preferences and select
Ethernet.
Set Configure IPv4 to Using DHCP.
29
Getting Started
3. Results
From any PC on the internal network,
open a web browser and browse to any
website. You can successfully connect
to the Internet.
Go to Policy & Objects > IPv4 > Policy.
Your Internet-access policy is at the top
of list, in the lan - wan section (this
section's name varies based on the
FortiGate model).
View the Count column, which displays
the total amount of traffic that has used
this policy since the FortiGate's last
reboot. The column should display
results, showing that the policy is being
used for traffic.
If this column is not visible, right-click on
the title row, select Count, then Apply.
For further reading, check out Installation in

Getting Started
30
In this example, you will create a WAN link interface that provides your FortiGate unit with redundant Internet
connections from two Internet service providers (ISPs). The WAN link interface combines these two connections
into a single interface.
This example includes weighted load balancing so that most of your Internet traffic is handled by one ISP.
A video of this recipe can be found here.
Getting Started
31
1. Connecting your ISPs to the FortiGate

Connect your ISP devices to your
FortiGate so that the ISP you wish to use
for most traffic is connected to WAN1
and the other connects to WAN2.
2. Deleting security policies and routes that use WAN1 or WAN2

You will not be able to add an interface to the WAN link interface if it is already used in the FortiGates
configuration, so you must delete any policies or routes that use either WAN1 or WAN2.
Many FortiGate models include a default Internet access policy that uses WAN1. This policy must also be
deleted.
and delete any policies that use WAN1 or
WAN2.
After you remove these policies, traffic

will no longer be able to reach WAN1 or
WAN2 through the FortiGate.

and delete any routes that use WAN1 or
WAN2.
Getting Started
32
3. Creating a WAN link interface

Go to System > Network > WAN Link
Load Balancing.
Set WAN Load Balancing to Weighted
Round Robin. This will allow you to
prioritize the WAN1 interface so that
more traffic uses it.
Add WAN1 to the list of Interface
Members, set Weight to 3, and set it to
use the Gateway IP provided by your
ISP.
You can optionally configure Health
Check to verify that WAN1 can connect
to the Internet.
Do the same for WAN2, but instead set

Weight to 1.
You can optionally configure Health
Check to verify that WAN2 can connect
to the Internet.
The weight settings will cause 75% of
traffic to use WAN1, with the remaining
25% using WAN2.
33
Getting Started
4. Creating a default route for the WAN link interface

and create a new default route.
Set Device to the WAN link interface.
5. Allowing traffic from the internal network to the WAN link interface
and create a new policy.
Set Incoming Interface to your internal
networks interface and set Outgoing
Interface to the WAN link interface.
Turn on NAT.
Scroll down to view the Logging Options.

To view the results later, turn on Log
Allowed Traffic and select All Sessions.
Getting Started
34
6. Results
Browse the Internet using a PC on the
internal network and then go to System >
FortiView > All Sessions.
Ensure that the Dst Interface column is
visible in the traffic log. If it is not shown,
right-click on the title row and select Dst
Interface from the dropdown menu.
Scroll to the bottom of the menu and
select Apply.
The log shows traffic flowing through
both WAN1 and WAN2.
Disconnect the WAN1 port, continue to
browse the Internet, and refresh the
traffic log. All traffic is now flowing
through WAN2, until you reconnect
WAN1.
For further reading, check out Installing a

FortiGate in NAT/Route Mode in the
35
Getting Started

If your FortiGate does not function as desired after completing the installation, try the following troubleshooting
methods.
Most methods can be used for both FortiGates in both NAT/Route and Transparent mode. Any exceptions are
marked.
Use FortiExplorer if you cant connect to the FortiGate over Ethernet.

If you cant connect to the FortiGate GUI or CLI, you may be able to connect using FortiExplorer. See your
FortiGate units QuickStart Guide for details.
Check for equipment issues.

Verify that all network equipment is powered on and operating as expected. Refer to the QuickStart Guide for
information about connecting your FortiGate to the network. You will also find detailed information about the
FortiGate unit LED indicators.
Check the physical network connections.

Check the cables used for all physical connections to ensure that they are fully connected and do not appear
damaged, and make sure that each cable connects to the correct device and the correct Ethernet port on that
device. Also, check the Unit Operation widget, found at System > Dashboard > Status, to make sure the
connected interfaces are shown in green.
Verify that you can connect to the internal IP address of the FortiGate unit
(NAT/Route mode).
Connect to the web-based manager from the FortiGates internal interface by browsing to its IP address. From the
PC, try to ping the internal interface IP address; for example, ping 192.168.1.99.
If you cannot connect to the internal interface, verify the IP configuration of the PC. If you can ping the interface
but cant connect to the web-based manager, check the settings for administrative access on that interface.
Getting Started
36
Verify that you can connect to the management IP address of the FortiGate unit
(Transparent mode).
From the internal network, attempt to ping the management IP address. If you cannot connect to the internal
interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other
devices on the network are powered on and operating. Go to the next step when you can connect to the internal
interface.
Check the FortiGate interface configurations (NAT/Route mode).

Check the configuration of the FortiGate interface connected to the internal network, and check the configuration
of the FortiGate interface that connects to the Internet to make sure Addressing Mode is set to the correct mode.
Verify the security policy configuration.

Go to Policy & Objects > Policy > IPv4 (or Policy & Objects > Policy > IPv6) and verify that the internal interface
to Internet-facing interface security policy has been added and is located near the top of the policy list. Check the
Sessions column to ensure that traffic has been processed (if this column does not appear, right-click on the title
row, select Sessions, and select Apply).
If you are using NAT/Route mode, check the configuration of the policy to make sure that NAT is turned on and
that Use Destination Interface Address is selected (later versions of FortiOS 5.2 call this option Use Outgoing
Interface Address).
Verify that you can connect to the Internet-facing interfaces IP address

(NAT/Route mode).
Ping the IP address of the FortiGates Internet-facing interface. If you cannot connect to the interface, the
FortiGate unit is not allowing sessions from the internal interface to Internet-facing interface.
Verify the static routing configuration (NAT/Route mode).

Go to Router > Static > Static Routes (or System > Network > Routing) and verify that the default route is
correct. View the Routing Monitor (found either on the same page or at Router > Monitor > Routing Monitor)
and verify that the default route appears in the list as a static route. Along with the default route, you should see
two routes shown as Connected, one for each connected FortiGate interface.
37
Getting Started
Verify that you can connect to the gateway provided by your ISP.
Ping the default gateway IP address from a PC on the internal network. If you cannot reach the gateway, contact
your ISP to verify that you are using the correct gateway.
Verify that you can communicate from the FortiGate unit to the Internet.
Access the FortiGate CLI and use the command execute ping 8.8.8.8. You can also use the execute
traceroute 8.8.8.8 command to troubleshoot connectivity to the Internet.
Verify the DNS configurations of the FortiGate unit and the PCs.
Check for DNS errors by pinging or using traceroute to connect to a domain name; for example: ping
www.fortinet.com. If the name cannot be resolved, the FortiGate unit or PC cannot connect to a DNS server
and you should confirm that the DNS server IP addresses are present and correct.
Confirm that the FortiGate unit can connect to the FortiGuard network.
Once registered, the FortiGate unit obtains antivirus and application control and other updates from the FortiGuard
network. Once the FortiGate unit is on your network, confirm that it can reach FortiGuard.
First, check the License Information widget to make sure that the status of all FortiGuard services matches the
services that you have purchased. Go to System > Config > FortiGuard. Expand Web Filtering and Email
Filtering Options and select Test Availability. After a minute, the GUI should show a successful
connection.
Consider changing the MAC address of your external interface (NAT/Route

mode).
Some ISPs do not want the MAC address of the device connecting to their network cable to change and so you
may have to change the MAC address of the Internet-facing interface using the following CLI command:
Some ISPs do not want the MAC address of the device connecting to their network cable to change and so you
may have to change the MAC address of the Internet-facing interface using the following CLI command:
config system interface
edit
set macaddr
end
end
Getting Started
38
Check the FortiGate bridge table (Transparent mode).

When the FortiGate is in Transparent mode, the unit acts like a bridge sending all incoming traffic out on the other
interfaces. The bridge is between interfaces on the FortiGate unit. Each bridge listed is a link between interfaces.
Where traffic is flowing between interfaces, you expect to find bridges listed. If you are having connectivity
issues, and there are no bridges listed that is a likely cause. Check for the MAC address of the interface or device
in question.
To list the existing bridge instances on the FortiGate unit, use the following CLI command:
diagnose netlink brctl name host root.b
show bridge control interface root.b host.
fdb: size=2048, used=25, num=25, depth=1
Bridge root.b host table
port no device devname mac addr ttl attributes
3 4 wan1 00:09:0f:cb:c2:77 88
3 4 wan1 00:26:2d:24:b7:d3 0
3 4 wan1 00:13:72:38:72:21 98
4 3 internal 00:1a:a0:2f:bc:c6 6
1 6 dmz 00:09:0f:dc:90:69 0 Local Static
3 4 wan1 c4:2c:03:0d:3a:38 81
3 4 wan1 00:09:0f:15:05:46 89
3 4 c4:2c:03:1d:1b:10 0
2 5 wan2 00:09:0f:dc:90:68 0 Local Static
If your devices MAC address is not listed, the FortiGate unit cannot find the device on the network. Check the
devices network connections and make sure they are connected and operational.
Either reset the FortiGate unit to factory defaults or contact the technical assistance center.
If all else fails, reset the FortiGate unit to factory defaults using the CLI command execute factoryreset.
When prompted, type y to confirm the reset.
Resetting the FortiGate unit to factory defaults puts the unit back into NAT/Route mode.
You can also contact the technical assistance center. For contact information, go to support.fortinet.com.
39
Getting Started
In this example, you will register your FortiGate unit and set the system time. You will also configure several
administrative account settings to prevent unauthorized access.
Getting Started
40
1. Registering your FortiGate

Registering your FortiGate allows you to receive FortiGuard updates and is required for firmware upgrades and
access to Fortinet Support.
Before registering your FortiGate unit, it must have Internet connectivity.
and locate the License Information
widget.
Next to Support Contract, select
Register.
Either use an existing Fortinet Support

account or create a new one. Select your
Country and Reseller.
It is recommend to use a common

account to register all your Fortinet
products, to allow the Support site to
keep a complete listing of your devices.
Getting Started
41
The License Information widget now

displays the unit as Registered.
2. Setting the system time

and locate the System Information
widget.
Next to System Time, select Change.
Select your Time Zone and either set the

time manually or select Synchronize
with NTP Server.
Since not all time zones have names,

you may need to know how many hours
ahead (+) or behind (-) you are from
Greenwich Mean Time (GMT).
42
Getting Started
The System Information widget now

displays the correct time.
3. (Optional) Restricting administrative access to a trusted host

Go to System > Admin >
Administrators and edit the default
admin account.
Enable Restrict this Administrator
Login from Trusted Hosts Only. Set
Trusted Host #1 to the static IP address
of the PC you will use to administer the
FortiGate unit, using /32 as the netmask.
You can also set an entire subnet as the
trusted host, using /24 as the netmask.
If required, set additional trusted hosts.
4. Changing the default admin password

admin account.
Select Change Password. Leave Old
Password blank and enter the New
Password.
You will be automatically signed out after
changing the password.
Getting Started
43
5. Results
Attempt to log in using the admin account
without a password. Access is denied.
Log in using the new password to access
the FortiGate.

and locate the Alert Message Console
widget, which indicates the failed
authentication attempt.
(Optional) If access has been restricted to a trusted host, attempts to connect from a device that is not trusted
will be denied.
For further reading, check out Basic

Administration in the FortiOS 5.2
Handbook.
44
Getting Started
This example verifies the current version of FortiOS firmware and, if necessary, updates it to the latest version.
FortiOS is the operating system used by FortiGate and FortiWiFi units. You can update FortiOS to use the latest
tools and security features available.
Getting Started
45
1. Checking the current FortiOS firmware

Log in to the GUI and go to System >
Dashboard > Status and view the
System Information dashboard widget.
The Firmware Versionsection shows
the firmware that is currently installed
and if a new version is available.
2.Reviewing the Release Notes

If a new version is available, selectView
Release Notes to access the Release
Notes for that version. Review the
release notes to determine if you want to
upgrade to this version.
Pay extra attention to theUpgrade
Information section, to find out if you
can upgrade directly from your current
firmware to the latest version. You
should also check theSupported
Upgrade Paths document, found at the
Fortinet Documentation Library.
Getting Started
46
3. Updating to the latest firmware

If you wish to upgrade to the latest
FortiOS version, selectUpdate.
UnderAvailable Firmware, select
theRecommendedtab, then
selectBackup Config and Upgrade.
4. Results
The FortiGate unit uploads the firmware
image file, updates to the new firmware
version, restarts, and displays the
FortiGate login. This process takes a few
minutes.
You may have to refresh your browser to
see the FortiGate login.
47
Getting Started
Go to System > Dashboard > Status.

In the System Information dashboard
widget, the Firmware Version will show
the updated version of FortiOS.
For further reading, check out Firmware in

Getting Started
48
If you have purchased FortiGuard services and registered your FortiGate unit, the FortiGate should automatically
connect to FortiGuard and display license information about your FortiGuard services. In this example, you will
verify whether the FortiGate unit is communicating with the FortiGuard Distribution Network (FDN) by checking
the License Information dashboard widget.
Getting Started
49
1. Verifying the connection

and go to the License Information
widget. Any subscribed services should
have a green checkmark, indicating that
connections are successful.
A gray X indicates that the FortiGate unit
cannot connect to the FortiGuard
network, or that the FortiGate unit is not
registered.
A red X indicates that the FortiGate unit
was able to connect but that a
subscription has expired or has not been
activated.
Getting Started
50
You can also view the FortiGuard

connection status by going to System >
Config > FortiGuard.
51
Getting Started
2. Troubleshooting communication errors

Go to System > Network > DNS and
ensure that the primary and secondary
DNS servers are correct.
In this screenshot, the FortiGate has

been successfully tested already.
execute ping guard.fortinet.net

To test if you are connected to the
correct DNS server, go to System >
Dashboard > Status and enter the
following command into the CLI Console:
If the connection the is successful, the
CLI Console should display a similar
output as the example.
Getting Started
52
To test if the FortiGuard services are

reachable, go to System > Config >
FortiGuard.
Under the Web Filtering and Email
Filtering Options, select Test
Availability. This will indicate which
ports are open.If the FortiGate default
port (53) cannot be unblocked, go to
System > Config > FortiGuard. Under
the Web Filtering and Email Filtering
Options choose Use Alternate Port
(8888).
If you are updating FortiGuard using a

FortiManager, the FortiGate can also use
port 80.
If further problems occur, you may have
to unblock ports using the CLI. See the
CLI Reference for FortiOS 5.2 for more
information.
3. Results
and go to the License Information
widget.
Any subscribed services should have a
green checkmark, indicating that
connections have been established and
that the licenses have been verified.
53
Getting Started
Go to System > Config > FortiGuard.

Features and services you are
subscribed to should have a green
checkmark, indicating that connections
are successful.
For further reading, check out FortiGuard in

Getting Started
54
This section contains tips to help you with some common challenges of using FortiGuard.
FortiGuard services appear as expired/unreachable.

Verify that you have registered your FortiGate unit, purchased FortiGuard services and that the services have not
expired at support.fortinet.com.
Services are active but still appear as expired/unreachable.

Verify that the FortiGate unit can communicate with the Internet by accessing FortiGate CLI and using the
command execute ping 8.8.8.8. You can also use the execute traceroute 8.8.8.8 command to
troubleshoot connectivity to the Internet.
The FortiGate is connected to the Internet but cant communicate with FortiGuard.
If you have not done so already, verify your DNS settings and ensure that an unblocked port is being used for
FortiGuard traffic.
If the FortiGate interface connected to the Internet gets its IP address using DHCP, go to System > Network >
Interfaces and edit the Internet-facing interface. Ensure that
Override internal DNS is selected.
Communication errors remain.

FortiGate units contact the FortiGuard Network by sending UDP packets with typical source ports of 1027 or
1031, and destination ports of 53 or 8888. The FDN reply packets would then have a destination port of 1027 or
1031. If your ISP blocks UDP packets in this port range, the FortiGate unit cannot receive the FDN reply packets.
In effort to avoid port blocking, You can configure your FortiGate unit to use higher-numbered ports, such as 204820000, using the following CLI command:
set ip-src-port-range 2048-20000
end
Trial and error may be required to select the best source port range. You can also contact your ISP to determine
the best range to use.
Getting Started
55
In this example, you will enable logging to capture the details of the network traffic processed by your FortiGate
unit. Capturing log details will provide you with detailed traffic information that you can use to asses any network
issues.
Getting Started
56
1. Recording log messages and enabling event logging

Go to Log & Report > Log Config >
Log Settings.Select where log
messages will be recorded. You can
save log messages to disk if it is
supported by your FortiGate unit, to a
FortiAnalyzer or FortiManager unit if you
have one, or to FortiCloud if you have a
subscription. Each of these options
allow you to record and view log
messages and to create reports based
on them.In most cases, it is
recommended to Send Logs to
FortiCloud, as shown in the example.
Next, enable Event Logging. You can
choose to Enable All types of logging, or
specific types, such as WiFi activity
events, depending on your needs.
Under the GUI Preferences, ensure
that the Display Logs From is set to the
same location where the log messages
are recorded (in the example,
FortiCloud).
Getting Started
57
2. Enabling logging in the security policies

Go to Policy & Objects > Policy > IPv4.
Edit the policies controlling the traffic
you wish to log.
Under Logging Options, select All
Sessions.
In most cases, you should select
Security Events, as All Sessions
requires more system resources and
storage space. For now, however, All
Sessions will be used to verify that
logging has been set up successfully.
58
Getting Started
3. Results
View traffic logs by going to Log &
Report > Traffic Log > Forward
Traffic. The logs display a variety of
information about your traffic, including
date/time, source, device, and
destination.To change the information
shown, right-click on any column title
and select Column Settings to enable or
disable different columns.
For further reading, check out Logging and

reporting overview in the FortiOS 5.2
Handbook.
Getting Started
59
In this example, you will use FortiCloud, an online logging service provided by Fortinet, to store the logs of your
FortiGate unit's traffic. You will also access logs using the FortiCloud website.
Before you can use FortiCloud, you must register your FortiGate. For more information, seeFortiGate registration
and basic settings.
Getting Started
60
1. Activating FortiCloud
and locate the License Information
widget. In the FortiCloud section, select
Activate.
Either use an existing FortiCloud account

or create a new one.
It is recommend to use a common

FortiCloud account for all your Fortinet
logs.
Information about your FortiCloud

account now appears in the License
Information widget.
2. Sending logs to FortiCloud

Go to Log & Report > Log Config >
Log Settings. Enable Send Logs to
FortiCloud and ensure that Upload
Option is set to Realtime.
Getting Started
61
Select Test Connectivity to verify the

connection between your FortiGate and
FortiCloud.
Adjust the Event Logging settings as

required and set the GUI Preferences to
Display Logs from FortiCloud.
3. Enabling logging in your Internet access security policy

and edit the policy that allows
connections from the internal network to
the Internet.
4. Results
Browse the Internet.Go to Log & Report
> Traffic Log > Forward Traffic. In the
top right corner of the screen, the Log
location is shown as FortiCloud.
62
Getting Started

In the FortiCloud section of the License
Information widget, select Launch
Portal.A screen will open in your
browser, showing all the devices that are
linked with your FortiGate account.
Select the appropriate unit.
You can also access your FortiCloud
account by going to www.forticloud.com
Getting Started
63
After selecting your device, the

FortiCloud Dashboard appears, showing
a variety of information about your traffic.
If traffic does not appear in FortiCloud

right away, wait 10-15 minutes and try
again.
From the portal, you can also access
options for FortiView, Drilldown,
Reports, and Management.
For more information about using
FortiCloud, see the FortiCloud FAQ
For further reading, check out FortiCloud in

64
Getting Started

This section contains tips to help you with some common challenges of FortiGate logging.
No log messages appear.

Ensure that logging is enabled in both the Log Settings and the policy used for the traffic you wish to log, as
logging will not function unless it is enabled in both places.
If logging is enabled in both places, check that the policy in which logging is enabled is the policy being used for
your traffic. Also make sure that the policy is getting traffic by going to the policy list and adding the Sessions
column to the list.
Logs from a FortiAnalyzer, FortiManager, or from FortiCloud do not appear in the

GUI.
Ensure that the correct log source has been selected in the Log Settings, under GUI Preferences.
The FortiGate units performance level has decreased since enabling disk logging.
If enabling disk logging has impacted overall performance, change the log settings to either send logs to a
FortiAnalyzer unit, a FortiManager unit, or to FortiCloud.
Logging to a FortiAnalyzer unit is not working as expected.

The firmware for the FortiGate and FortiAnalyzer units may not be compatible. Check the firmware release notes,
found at support.fortinet.com, to see if this is the case.
Getting Started
65
This example shows how to create and order multiple security policies in the policy table, in order to apply the
appropriate policy to various types of network traffic.
In the example, three IPv4 policies will be configured. PolicyA will be a general policy allowing Internet access to
the LAN. PolicyB will allow Internet access while applying web filtering for specific mobile devices connecting
through the LAN. PolicyC will allow the system administrators PC (named SysAdminPC) to have full access
In this example, a wireless network has already been configured that is in the same subnet as the wired LAN. For
information about this configuration, seeSetting up a WiFi bridge with a FortiAP.
A fourth policy, the default deny policy, will also be used.
Getting Started
66
1. Configuring PolicyA to allow general web access

and edit the policy allowing outgoing
traffic.
Set Service to HTTP, HTTPS, and
DNS.
Ensure that you have enabled NAT.

Getting Started
67
2. Creating PolicyB to allow access for mobile devices

Set Incoming Interface to lan, Source
Device Type to Mobile Devices (a
default device group that includes tablets
and mobile phones).
Using a device group will automatically

enable device identification on the lan
interface.
Outgoing Interface to your Internetfacing interface, and Service to HTTP,
HTTPS, and DNS.
Enable NAT.
Under Security Profiles, enable Web
Filter and set it to use the default profile.
This action will enable Proxy Options
and SSL Inspection. Use the default
profile for Proxy Options and set SSL
Inspection to certificate-inspection to
allow HTTPS traffic to be inspected.

68
Getting Started
3. Defining SysAdminPC
Go to User & Device > Device >
Device Definitions and create a new
definition for the system administrators
PC.
Select an approprate Alias, then set the
MAC Address. Set the appropriate
Device Type.
4. Configuring PolicyC to allow access for SysAdminPC

Set Incoming Interface to lan, Source
Device Type to SysAdminPC,
Outgoing Interface to your Internetfacing interface, and Service to ALL.
Enable NAT.

Getting Started
69
5. Ordering the policy table

to view the policy table. Currently, the
policies are arranged in the order they
were created: PolicyA is at the top,
followed by PolicyB, PolicyC, and the
default deny policy.
In order to have the correct traffic flowing
through each policy, they must be
arranged so that the more specific
policies are located at the top.
In the example, the policy table has been

set to show only the columns that best
display the differences between the
policies. To do this, right-click on the top
of the table, select or deselect columns
as necessary, then select Apply.
To rearrange the policies, select the
column on the far left (in the example,
Seq.#) and drag the policy to the desired
position.
70
Getting Started
6. Results
Browse the Internet using the system administrators PC, a different PC, and a mobile device.
Go to Log & Report > Traffic Log >
Forward Traffic.
You can see that traffic from the three
devices flows through different policies.
In the example, the SysAdmin PC (IP
10.10.11.10), a Windows PC (IP
10.10.11.14), and an iPad (IP
10.10.11.13) were used to generate
traffic.
Policy ID is automatically assigned to a

policy when it is created, and so, in the
example, the ID for PolicyA is 1, PolicyB
is 2, and PolicyC is 3.
(Optional) Attempt to make an SSL connection to a web server with all three devices. Only the system
administrators PC will be able to connect.
For further reading, check out Firewall

policies in the FortiOS 5.2 Handbook.
Getting Started
71
In this recipe you will create a FortiGate administrator account that is limited to read and write access for user and
device authentication and read access for logging and reporting. In addition you will use the Trusted Hosts feature
to control the IP address that the administrator can log in from.
The administrator account will have the same access limitations for both the GUI and CLI.
Getting Started
72
1. Creating a new administrator profile

Go to System > Admin > Admin
Profiles.
Create a new administer profile that
limits administrators with this profile to
read and write access to User and
Devices and read only access to Log &
Report data and report access.
Getting Started
73
2. Adding a new administrator and assigning the profile

Administrators.
Create a new administrator account and
assign it to the Administrator Profile
that you just created.
Add an IP address to at least one of the
Trusted Host fields to control where the
administrator can log in from. In the
example the administrator can log in only
from the 172.20.120.0 network.
74
Getting Started
3. Results
Log into the FortiGate unit with the
t.white. administrator account. t.white
should only see the User & Device and
the Log & Report menus.
t.white should be able to change user and
device authentication settings and view
log messages and reports.
Log in from another browser window with

the admin account.
Go to System > Dashboard > Status,
and view the System Information
widget. It should show two
administrators.
Select Details to view the list of logged
in administrators.
Getting Started
75
Using the admin or t.white account, go to

Log & Report > Event Log > System.
Log messages should show activity for
both administrators. Select a log entry to
view details. Log entries for t.white
should show the source address that
t.white logged in from. This address
should be within the Trusted Hosts
network address.
For further reading, check out

Administrators in the FortiOS 5.2
Handbook.
76
Getting Started
When you create a port pair, all traffic accepted by one of the paired interfaces can only exit out the other interface.
Restricting traffic in this way simplifies your FortiGate configuration because security policies between these
interfaces are pre-configured.
In this example you will create a wan1 to Internal port pair to make it easier to allow access to a web server
protected by a FortiGate in Transparent mode. In this unusual configuration, the web server is connected to the
FortiGates wan1 interface and the FortiGates Internal interface is connected to an internal network. Users on the
internal network access the web server through the FortiGate.
Traffic between port-paired interfaces does not check the bridge table and MAC addresses are not learned.
Instead traffic received by one interface in a port pair is forwarded out the other (if allowed by a firewall policy).
This makes port pairing useful for unusual topologies where MAC addresses do not behave normally. For
example, port paring can be used in a Direct Server Return (DSR) topology where the response MAC address pair
may not match the requests MAC address pair.
Getting Started
77
1. Switching the FortiGate unit to transparent mode and adding a static route
In the System Information widget,
select Change beside Operation
Mode.
Change the Operation Mode to
Transparent. Add a Management
IP/Netmask. Also add a Default
Gateway for your network so that the
FortiGate unit can connect to the
Internet.
If the Management IP is the same as the

IP address that you logged into the
FortiGate unit with, you will remain
logged in after the operation mode has
changed. Otherwise, log into the
FortiGate unit using the management IP
(in the example, 172.20.120.142).
2. Creating an internal and wan1 port pair

Go to System > Network > Interfaces.
Select Create New > Port Pair. Create
a port pair that includes the internal and
wan1 interfaces.
All traffic accepted by the internal
interface can only exit out of the wan1
interface.
Getting Started
78
3. Creating security policies

Create a security policy that allows
internal users to access the protected
web server using HTTP and HTTPS.
Create a second security policy that

allows connections from the web server
to the internal network and to the Internet
using any service.
4. Results
Connect to the web server from the
internal network and surf the Internet
from the server itself.
Forward Traffic to verify that there is
traffic from the internal to wan1 interface.
Select an entry for details.
79
Getting Started
Go to Policy & Objects > Monitor >

Policy Monitor to view the active
sessions.
For further reading, check out Interfaces in

Getting Started
80
In this recipe, which starts with a FortiGate Clustering Protocol (FGCP) cluster of two FortiGate units*, you will
upgrade the primary units firmware, while keeping the subordinate unit as a failsafe backup running the original
firmware.
If the new firmware upgrades and runs successfully, you can quickly upgrade the entire cluster to the new
firmware. If the new firmware fails during or after the upgrade, you can quickly revert the cluster to the older
firmware.
This recipe increases the effort needed to upgrade cluster firmware but allows easily falling back to the original
firmware version and FortiGate configuration with minimal network interruption.
Normally when you upgrade a cluster, network traffic is not interrupted. However, upgrading one unit in a cluster
results in minor network disruptions similar to upgrading the firmware of a single FortiGate unit.
This recipe requires you to enable the dedicated or reserved HA management interface feature.
This example uses the following interfaces:
l
Internal1 is the reserved management interface
Internal2 is connected to the Internal Network
wan1 is connected to the Internet
Internal4 and Internal5 are the HA heartbeat interfaces
Getting Started
81
1. Enable the HA reserved management interface feature

You can configure the HA reserved
management interface feature when
originally setting up the cluster.
If the cluster is already running, log
into the primary unit and go to System
> Config > HA, select the primary
unit, enable the reserved management
interface, and select an interface.
Then go to System > Network >
Interface and configure the interface
that you selected.
You can also use the following

command to set up the reserved
management interface from the CLI.
This is also the only way to add a
default gateway for the reserved
management interface if one is
required.
config system ha
set ha-mgmt-interface internal1
set ha-mgmt-interface-gateway 10.11.101.2
end
set ha-mg
To configure the subordinate unit's reserved management interface, from the primary unit CLI use the execute
ha manage command to access the subordinate unit's CLI. Then use the config system interface
command to set the IP address for the subordinate unit reserved management interface. You can also use the
set ha-mgmt-interface-gateway command to configure the default gateway.
Enabling and selecting the reserved management interface is synchronized to both cluster members. The
management interface gateway and the configuration of the management interface is not synchronized.
Getting Started
82
2. Disable HA configuration synchronization

config system ha
Enter this command to disable HA
set sync-config disable
configuration synchronization. You
end
can enter this command from any CLI
prompt on the primary unit (master) or
subordinate unit (slave). The change is
synchronized to both FortiGate units in
the cluster.
3. Back up the configuration of each cluster unit

Use the reserved management IP
addresses to log into the GUI of each
cluster unit and verify that the serial
numbers and role of the unit in the
cluster match. The first image shows
an example primary unit (master) and
the second an example subordinate
unit (slave).
Primary unit (master)
Subordinate unit (slave)
83
Getting Started
From the system information

dashboard widget of each cluster unit
GUI, back up each cluster unit's
configuration. Back up both
configurations since some settings are
not synchronized (for example, the
reserved management IP address).
4. Isolate the subordinate unit

Isolate of the subordinate unit from the
network. From the subordinate unit
GUI, go to System > Network >
Interface, edit the traffic interfaces (in
this example Internal2 and wan1) and
set their Administrative Status to
Down.
Isolate of the subordinate unit from the

primary unit. Set the Administrative
Status of the heartbeat interfaces
(Internal4 and Internal5) to Down.
To avoid a split brain (when the
heartbeat interfaces become
disconnected and both cluster
members become primary units) you
must bring the traffic interfaces down
before the heartbeat interfaces.
Getting Started
84
Check the System Information

widget of the subordinate unit. It will
think its the primary unit. Because its
traffic interfaces are down, all traffic is
going to the actual primary unit.
Connect to the primary unit GUI. The

System Information widget should
show just one cluster member.
5. Upgrade the cluster firmware and re-establish the cluster

Upgrade the firmware running on the primary unit (the one still processing traffic) using any normal firmware
update procedure. For a short time during the upgrade network traffic is blocked. After the upgrade, make sure
the primary unit is operating as expected. If it is not, go to step 6. Revert to the original firmware version.
Once you have done enough testing to establish that the primary unit is operating as expected with the new
firmware, you can upgrade the subordinate unit to the same version. Log into the subordinate unit using its
reserved management interface and upgrade the firmware.
Log into the primary unit reserved
management interface and re-enable
configuration synchronization.
config system ha
set sync-config enable
end
Log into the subordinate unit, enable configuration synchronization, bring up its heartbeat interfaces and bring up
its traffic interfaces.
The cluster resumes operating normally. You can use the get system ha status and diagnose sys ha
status commands to verify that HA is operating normally.
Back up the configuration of the primary and subordinate FortiGate units. Backed up configuration files are
specific to FortiOS versions.
85
Getting Started
6. Revert to the original firmware version

If the update didn't succeed or the primary unit is not operating as expected, bring down the primary unit traffic
interfaces and then heartbeat interfaces.
Then bring up the subordinate unit traffic and heartbeat interfaces. The subordinate unit, running the original
firmware version, becomes the primary unit and processes traffic normally.
Downgrade the firmware running on the original primary unit to the original firmware version (that is currently
running on the subordinate unit). Bring up the heartbeat and traffic interfaces on the original primary unit. The two
cluster members re-establish the cluster, running the original firmware version.
For further reading, check out Configuring

and connecting HA clusters in the FortiOS
5.2 Handbook.
Getting Started
86
Port forwarding
This example illustrates how to use virtual IPs to configure port forwarding on a FortiGate unit. In this example,
TCP ports 80 (HTTP), 21 (FTP), and 22 (SSH) are opened, allowing remote connections to communicate with a
server behind the firewall.
Getting Started
87
1. Creating three virtual IPs

Go to Policy & Objects > Objects >
Virtual IPs > Create New > Virtual IP.
Enable Port Forwarding and add a
virtual IP for TCP port 80. Label this VIP
webserver-80.
While this example maps port 80 to port

80, any valid External Service port can
be mapped to any listening port on the
destination computer.
Create a second virtual IP for TCP port

22. Label this VIP webserver-ssh.
Getting Started
88
Create a third a virtual IP for TCP port 21.

Label this VIP webserver-ftp.
2. Adding virtual IPs to a VIP group

Virtual IPs > Create New > Virtual IP
Group.
Create a VIP group. Under Members,
include all three virtual IPs previously
created.
89
Getting Started
3. Creating a security policy

and create a security policy allowing
access to a server behind the firewall.
Set Incoming Interface to your Internetfacing interface, Outgoing Interface to
the interface connected to the server,
and Destination Address to the VIP
group. Set Service to allow HTTP, FTP,
and SSH traffic.
Use the appropriate Security Profiles to
protect the servers.
Getting Started
90
4. Results
To ensure that TCP port 80 is open,
connect to the web server on the other
side of the firewall.
To ensure that TCP port 22 is open,

connect to the SSH server on the other
side of the firewall.
91
Getting Started
To ensure that TCP port 21 is open, use

an FTP client to connect to the FTP
server on the other side of the firewall.
For further reading, check out Virtual IPs in

Getting Started
92
FortiGuard DDNS
In this example, you will use FortiGuard Dynamic Domain Name Service (DDNS) to allow a remote administrator
to access your FortiGate's Internet-facing interface using a domain name that remains constant, even when its IP
address changes.
An active FortiCare Support Contract is required to use FortiGuard DDNS.
Getting Started
93
1. Limited administrative access to trusted hosts

admin account.
Enable Restrict this Administrator
Login from Trusted Hosts Only. Add
the required internal or remote devices as
Trusted Hosts. You can also set an
entire subnet as the trusted host, using
/24 as the netmask.
2. Enabling HTTP/HTTPS access on the Internet-facing interface

and edit the Internet-facing interface
(typically wan1).
Make sure that Administrative Access
is allowed for HTTPS.
2. Setting up FortiGuard DDNS

Go to System > Network > DNS and
enable FortiGuard DDNS.
SetInterface to your Internet-facing
interface, select a Server, and select a
Unique Location that will be used in the
domain name.
The FortiGuard DDNS service will verify
that the resulting domain name is unique
and valid. If it is valid, select Apply. The
domain name is now displayed, with the
current IP address of the interface.
You can click the domain name to
browse to the address with a web server.
Getting Started
94
config system ddns

edit 0
set ddns-server FortiGuardDDNS
set ddns-domain branch.float-zone.com
set monitor-interface wan1
end
end
You can also configure FortiGuard

DDNS by using the following CLI
commands:
3. Results
Browse to the domain name assigned to
the interface, using HTTPS (in the
example, https://branch.float-zone.com).
The FortiGate login screen will appear.

and edit the Internet-facing interface.
Change the interface's IP
Address/Netmask.
You will still be able to access the interface using the domain name.
For further reading, check out Dynamic

DNS configuration in the FortiOS 5.2
Handbook.
95
Getting Started
SNMP monitoring
In this example, you configure the FortiGate SNMP agent and an example SNMP manager so that the SNMP
manager can get status information from the FortiGate unit and so that the FortiGate unit can send traps to the
SNMP manager.
The Simple Network Management Protocol (SNMP) enables you to monitor hardware on your network. You
configure the hardware, such as the FortiGate SNMP agent, to report system information and send traps (alarms
or event messages) to SNMP managers.
Getting Started
96
1. Configuring the FortiGate SNMP agent

Go to System > Config > SNMP. Enable
the SNMP Agent and add any necessary
information.
Getting Started
97
Under SNMP v1/v2c, create a new

community.
Add the IP address of SNMP manager (in
the example, 192.168.1.114/32). If
required, change the query and trap ports
to match the SNMP manager.
You can add multiple SNMP managers,
or set the IP address/Netmask to
0.0.0.0/0.0.0.0 and the Interface to
ANY, so that any SNMP manager on any
network connected to the FortiGate unit
can use this SNMP community and
receive traps from the FortiGate unit.
Enable the SNMP Events (traps) that
you need. In most cases, leave them all
enabled.
98
Getting Started
2. Enabling SNMP on a FortiGate interface

and edit the interface connected to the
same network as the SNMP manager.
Enable SNMP for Administrative
Access.
3. Downloading the Fortinet MIB files to and configuring an example SNMP

manage
Two types of MIB files are available 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.
Go to System > Config > SNMP and
select Download FortiGate SNMP MIB
File and Download Fortinet Core MIB
File.Configure the SNMP manager to
receive traps from the FortiGate unit.
Install the FortiGate and Fortinet MIBs.
Getting Started
99
4. Results
This example uses the SolarWinds
SNMP trap viewer.
In the SolarWinds Toolset Launch Pad,
go to SNMP > MIB Viewer and select
Launch.
Choose Select Device, enter the IP

address of the FortiGate unit, and choose
the appropriate community string
credentials.
100
Getting Started
Open the SNMP Trap Receiver and

select Launch.
The SNMP Trap Receiver will appear.
On the FortiGate unit, perform an action

to trigger a trap (for example, change the
IP address of the DMZ interface).
Getting Started
101
Verify that the SNMP manager receives

the trap.
For further reading, check out SNMP in the

102
Getting Started
Packet capture
In this example, you will set up and run some basic packet capture filters on your FortiGate and download and
view the resulting .pcap file.
You can use packet capturing to learn about network activity seen by your FortiGate by creating and saving
packet capture filters that define the packets to capture. You can then run these filters at any time, download the
resulting .pcap (packet capture) file, and use a tool like Wireshark to analyze the results.
Getting Started
103
1. Creating packet capture filters

Go to System > Network > Packet Capture and create a new filter. Below are a few examples of different
filters you can use.
The simplest filter just captures all of the
packets received by an interface. This
example captures 10 packets received
by the mgmt1 interface.
You can select Enable Filters to restrict

the packets to capture.
This filter captures 100 HTTP and
HTTPS packets (port 80 and 443)
received by the Ednet wireless interface
that have a source or destination address
in the range 172.20.120.10 to
172.20.120.20.
Getting Started
104
This filter captures the first 4000 Stream

Control Transmission Protocol (SCTP)
packets received by the port1 interface.
Protocols are identified using IP protocol

numbers; for example, SCTP is protocol
132.
This filter captures the first 1000 DNS

packets querying the Google DNS server
(IP address 8.8.8.8) with VLAN IDs 37 or
39.
105
Getting Started
2. Results
Running packet capture filters may affect
FortiGate performance.
Go to System > Network > Packet
Capture, choose a filter, and select the
Play icon. You can watch the filter
capture packets. When the number of
packets specified in the filter are
captured the filter stops.
You can stop and restart multiple filters
at any time.
Download any saved .pcap file to your
computer. You can open the file with a
.pcap file viewer like Wireshark.
For further reading, check out Monitoring in

Getting Started
106
VDOM configuration
This example illustrates how to use VDOMs to host two FortiOS instances on a single FortiGate unit.
Virtual Domains (VDOMs) can be used to divide a single FortiGate unit into two or more virtual instances of
FortiOS that function as independent FortiGate units. This example simulates an ISP that provides Company A
and Company B with distinct Internet services. Each company has its own VDOM, IP address, and internal
network.
Getting Started
107
1. Switching to VDOM mode and creating two VDOMS

In the System Information widget, find
Virtual Domain and select Enable.
You will be required to re-login after
enabling Virtual Domain due to the GUI
menu options changing.
Go to Global > VDOM > VDOM.

Create two VDOMS: VDOM-A and
VDOM-B. Leave both VDOMs as
Enabled, with Operation Mode set to
NAT.
Getting Started
108
2. Assigning interfaces to each VDOM

Go to Global > Network > Interfaces.
Edit port1 and add it to VDOM-A. Set
Addressing Mode to Manual and
assign an IP/Network Mask to the
interface (in the example,
172.20.120.10/255.255.255.0).
Edit port2 and add it to VDOM-A. Set
Addressing Mode to Manual, assign an
IP/Network Mask to the interface (in the
example, 192.168.10.1/255.255.255.0),
and set Administrative Access to
HTTPS, PING, and SSH. Enable DHCP
Server.
Edit port3 and add it to VDOM-B. Set

Addressing Mode to Manual and
assign an IP/Network Mask to the
interface (in the example,
172.20.120.20/255.255.255.0).
109
Getting Started
Edit port4 and add it to VDOM-B. Set

Addressing Mode to Manual, assign an
IP/Network Mask to the interface (in the
example, 192.168.20.1/255.255.255.0),
and set Administrative Access to
HTTPS, PING, and SSH. Enable DHCP
Server.
3. Creating administrators for each VDOM

Go to Global > Admin >
Administrators.
Create an administrators for VDOM-A,
called a-admin. Set Type to Regular,
set a password, and set Admin Profile to
prof_admin.
Create an administrators for VDOM-B,

called b-admin. Set Type to Regular,
set a password, and set Admin Profile to
prof_admin.
Make sure to remove the root VDOM
from both administrator accounts.
Getting Started
110
4. Creating a basic configuration for VDOM-A

Go to Virtual Domains and select
VDOM-A.
Go to System > Network > Routing.
Create a default route for the VDOM. Set
Destination IP/Mask to 0.0.0.0/0.0.0.0,
set Device to port1, and set Gateway
to the IP of the gateway router (in the
example, 172.20.120.2).
Connect a PC to port2. Using HTTPS
protocol, browse to the IP set for port2
and log into VDOM-A using the a-admin
account (in the example, 192.168.10.1).
Create a policy to allow Internet access.
Set Incoming Interface to port2 and
Outgoing Interface to port1. Ensure
NAT is turned On.
111
Getting Started
5. Creating a basic configuration for VDOM-B

If you have logged out of the FortiGate
unit, log back in.
VDOM-B.
Go to System > Network > Routing
Create a default route for the VDOM. Set
Destination IP/Mask to 0.0.0.0/0.0.0.0,
set Device to port3, and set Gateway
to the IP of the gateway router (in the
example, 172.20.120.2).
Connect a PC to port4. Using HTTPS
protocol, browse to the IP set for port4
and log into VDOM-B using the a-admin
account (in the example,
https://192.168.10.1).
Create a policy to allow Internet access.
Set Incoming Interface to port4 and
Outgoing Interface to port3. Ensure
NAT is turned On.
Getting Started
112
6. Connecting the gateway router

Connect port 1 and port3 of the FortiGate
unit to the gateway router to allow
Internet traffic to flow.
7. Results
Connect to the Internet from the
company A and company B networks
and then log into the FortiGate unit
VDOM-A.
Policy Monitor to view the sessions
being processed on VDOM-A.
113
Getting Started

Policy Monitor to view the sessions
being processed on VDOM-B.
For further reading, check out Virtual

Domains in the FortiOS 5.2 Handbook.
Getting Started
114
In this recipe, a backup FortiGate unit will be installed and connected to a FortiGate unit that has previously been
installed to provide redundancy if the primary FortiGate unit fails. This set up, called High Availability (HA),
improves network reliability.
If you have not already installed a FortiGate, see Installing a FortiGate in NAT/Route mode.
Getting Started
115
1. Adding the backup FortiGate unit and configuring HA

If the FortiGates in the cluster will be running FortiOS Carrier, apply the FortiOS Carrier license before configuring the cluster (and before
applying other licenses). Applying the FortiOS Carrier license sets the configuration to factory defaults, requiring you to repeat steps
performed before applying the license.
Make sure both FortiGates are running

the same FortiOS firmware version.
Register and apply licenses to the new
FortiGate unit before adding it to the
cluster. This includes FortiCloud
activation, FortiClient licensing, and
FortiToken licensing, and entering a
license key if you purchased more than
10 Virtual Domains.
You can also install any third-party
certificates on the primary FortiGate
before forming the cluster. Once the
cluster is formed third-party certificates
are synchronized to the backup
FortiGate.
Connect your network as shown in the
initial diagram, with Ethernet cables
connecting the HA heartbeat interfaces
of the two FortiGate units. If your
FortiGate unit does not have dedicated
HA heartbeat interfaces, you can use
different interfaces, provided they are not
used for any other function.
A switch must be used between the
FortiGates and Internet, and another is
required between the FortiGates and the
internal network, as shown in the
network diagram for this recipe.
Connect to the primary FortiGate and go
to System > Dashboard > Status and
locate the System Information widget.
Change the unit's Host Name to identify
it as the primary FortiGate.
Getting Started
116
In the System Information widget,

configure HA Status. Set the Mode to
Active-Passive and set a Group Name
and Password.
Ensure that the two Heartbeat
Interfaces are selected and their
priorities are both set to 50.
Connect to the backup FortiGate and go

to System > Dashboard > Status.
it as the backup FortiGate.
117
Getting Started
Configure HA Status and set the Mode

to Active-Passive.
Set the Device Priority to be lower than
the primary FortiGate. Ensure that the
Group Name and Password match
those on the primary FortiGate.
Ensure that the two Heartbeat
Interfaces are selected and their
priorities are both set to 50.

to System > Config > HA to view the
cluster information.
Getting Started
118
Select View HA Statistics for more

information on how the cluster is
operating and processing traffic.
2. Results
Normally, traffic should now be flowing through the primary FortiGate. However, if the primary FortiGate is
unavailable, traffic should failover and the backup FortiGate will be used. Failover will also cause the primary
and backup FortiGates to reverse roles, even when both FortiGates are available again.
To test this, ping the IP address 8.8.8.8
using a PC on the internal network. After
a moment, power off the primary
FortiGate
If you are using port monitoring, you can

also unplug the primary FortiGate's
Internet-facing interface to test failover.
You will see a momentary pause in the
Ping results, until traffic diverts to the
backup FortiGate, allowing the Ping
traffic to continue.
119
Getting Started
3. (Optional) Upgrading the firmware for the HA cluster

For information about accessing firmware images, see Updating your FortiGates firmware.
When a new version of the FortiOS
firmware becomes available, upgrading
the firmware on the primary FortiGate will
automatically upgrade the backup
FortiGate's firmware as well.
Always review the Release Notes and
Supported Upgrade Paths
documentation before installing new
firmware. These documents can be
found at the Fortinet Document Library.
widget. Now that the FortiGates are in
HA mode, their configuration is
synchronized and the System
Information widget displays information
for both units.
Select Backup beside System
Configuration. Always remember to
back up your configuration before doing
any firmware upgrades.
widget. Select Upgrade beside
Firmware Version. Find the firmware
image file that you downloaded and
select OK to upload and install the
firmware build.
The firmware will load onto both the
primary FortiGate unit and the backup
unit.
Getting Started
120

and verify that the System Information
widget shows the new firmware version.

5.2 Handbook.
121
Getting Started
In this example, you will create multicast security policies to allow AirPlay communication between an iOS device
and an Apple TV through a FortiGate unit.
Apple TV can also be connected to the Internet wirelessly. AirPlay will function from any iOS device connected to
the same SSID as the Apple TV, without any configuration required on the FortiGate.
This recipe uses a FortiAP in Tunnel mode. For more information, see Setting up WiFi with FortiAP.
Getting Started
122
1. Enabling multicast policies

Go to System > Config > Features.
Select Show More and enable Multicast
Policy. Apply the changes.
2. Creating AirPlay services

Services and create a service as shown
for the connection from the Apple TV to
the iOS device.

Services and create a service as shown
for the connection from the iOS device to
the Apple TV.
Getting Started
123
3. Allowing multicast between the wireless and internal networks

Go to Policy & Objects > Policy >
Multicast and create a policy allowing
local network traffic to reach the wireless
network.
Set Incoming Interface to lan,
Outgoing Interface to the wireless
interface, and Destination Address to
Bonjour.
Bonjour is a default multicast address

that is used by Apple devices to discover
shared services on the local network.
Using it in the multicast policies will
allow the iOS device and Apple TV to
connect to each other through the
FortiGate.
Create a second policy allowing wireless
traffic to reach the internal network.
Set Incoming Interface to the wireless
interface, Outgoing Interface to lan,
and Destination Address to Bonjour.
124
Getting Started
4. Allowing airplay between the wireless and internal networks

and create a policy allowing traffic from
the Apple TV to the iOS device.
Set Incoming Interface to
lan,Outgoing Interface to the SSID,
and Service to allow connections from
the Apple TV to the iOS device.
Create a second policy allowing traffic

from the iOS device to the Apple TV.
Set Incoming Interface to the SSID,
Outgoing Interface to lan, and Service
to allow connections from the iOS device
to the Apple TV.
Getting Started
125
5. Results
Use AirPlay to stream audio or video
from an iOS device to the Apple TV.
Multicast. You will see traffic flowing
between the two devices, using both
multicast policies.
For further reading, check out Multicast

forwarding in the FortiOS 5.2 Handbook.
126
Getting Started
In the following example, you will protect a web server by connecting it using your FortiGates DMZ network.
An internal to DMZ security policy with a virtual IP (VIP) allows internal users to access the web server using an
internal IP address (10.10.10.22). A WAN-to-DMZ security policy also with a VIP hides the internal address,
allowing external users to access the web server using a public IP address (172.20.120.22).
Getting Started
127
1. Configuring the FortiGates DMZ interface

Edit the DMZ interface.
The DMZ Network (from the term
demilitarized zone) is a secure network
connected to the FortiGate that only
grants access if it has been explicitly
allowed. Using the DMZ interface is
recommended but not required.
For enhanced security, disable all
Administrative Access options.
2. Creating virtual IPs (VIPs)

Virtual IPs. Create two virtual IPs: one
for HTTP access and one for HTTPS
access.
Each virtual IP has the same address,
mapping from the public-facing interface
to the DMZ interface. The difference is
the port for each traffic type: port 80 for
HTTP and port 443 for HTTPS.
Getting Started
128

Create a security policy to allow HTTP
and HTTPS traffic from the Internet to
the DMZ interface and the web server.
Do not enable NAT and, for testing
purposes, enable logging for all sessions.
129
Getting Started
Create a second security policy to allow

HTTP and HTTPS traffic from the
internal network to the DMZ interface and
the web server.
Adding this policy allows traffic to pass
directly from the internal interface to the
DMZ interface.
Do not enable NAT and, for testing
purposes, enabe logging for all sessions.
4. Results
External users can access the web server on the DMZ network from the Internet using its Internet address (in
this example, http://172.20.120.22 and https://172.20.120.22). Internal users can access the web server using
its DMZ address (in this example. and https://10.10.10.22). Internal users cannot access the web server using
its Internet access because by default the FortiGate blocks harpining. For more information about hairpining,
see this Knowledge Base article.
Policy Monitor.
Use the policy monitor to verify that
traffic from the Internet and from the
internal network is allowed to access the
web server. This verifies that the policies
are configured correctly.
Getting Started
130

Forward Traffic.
The traffic log shows sessions from the
internal network and from the Internet
accessing the web server on the DMZ
network.
For further reading, check out Firewall in

131
Getting Started
The quality of VoIP phone calls through a firewall often suffers when the firewall is busy and the amount of
bandwidth available for the VoIP traffic fluctuates. This can be irritating, leading to unpredictable results and caller
frustration. This recipe describes how to add traffic shaping to guarantee that enough bandwidth is available for
VoIP traffic, regardless of any other activity on the network.
To achieve high quality real-time voice transmissions, VoIP traffic requires priority over other types of traffic,
minimal packet loss, andjitter buffers. You will limitbandwidth consuming services, likeFTP, while providinga
consistent bandwidth for day-to-day email and web-based traffic.First, you will customize three existing traffic
shapershigh priority, medium priority, andlow priorityand then create aseparatesecurity policy for eachservice
type.
Before you apply QoS measures,ensure you haveenough network bandwidth to support real-time voice traffic.
Getting Started
132
1.Enabling Traffic Shaping and VoIP features

Go to System > Config > Features and
click the Show More button to view
additional features. If necessary,
selectON to enable bothTraffic
Shaping and VoIP. Apply your changes.
Traffic shaping rules and VoIP profiles

can now beapplied to firewall policies.
2. Configuringa high priority VoIP traffic shaper

Traffic Shapers and edittheexisting
high-priority traffic shaper.
Set Typeto Shared. Set Apply shaper
to Per Policy.
SelectPer Policy when you want each

security policy for day-to-day business
traffic to have the same distribution of
bandwidth, regardless of the number of
policies using the shaper. In this
example, 800kb/s (0.8Mbps) each.
Set Traffic Priority to High.Select Max
Bandwidth and enter 1000 kb/s (1
Mbps). Select Guaranteed Bandwidth
and enter 800 kb/s (0.8 Mbps).
Getting Started
133
3. Configuringa low priority FTP traffic shaper

Go toPolicy & Objects > Objects >
Traffic Shapersand edit theexisting
low-priority traffic shaper.
SetTypeto Shared. Set Apply shaper
to All policies using this shaper.
SelectAll policies using this shaperto

ensure thatallpoliciesusing yourshaper
will be restricted to share aset amount of
bandwidth. In this example, 200kb/s (0.2
Mbps) total.
Set Traffic Priority to Low.
If you are creating a new traffic shaper,

the Traffic Priority is set to High by
default. A failure to set different shaper
priorities will result in a lack
ofprioritizedtraffic.
Set Max Bandwidthand Guaranteed
Bandwidthto200kb/s (0.2 Mbps).
Setting a low maximum bandwidth

willprevent sudden spikes in traffic
caused by large FTP file uploads
anddownloads.
134
Getting Started
4. Configuringamediumpriority daily traffic shaper

Traffic Shapersand edit theexisting
medium-priority traffic shaper.
SetTypeto Shared. Set Apply shaper
to Per Policy. Select Max Bandwidth
and enter 600kb/s (0.6 Mbps). Set
Traffic Priority to Medium. Select
Guaranteed Bandwidth and enter 600
kb/s(0.6 Mbps).
This shaper should be set to a moderate

value and set toper policy sothat dayto-day traffic has the same distribution of
bandwidth.
Getting Started
135
5.Applying eachshaper to a device-based policy

and create a new security policy for SIP
traffic.
Enable Shared Shaper and Reverse
Shaperand select high-priority.
Make sure that you include aReverse

Shaperso thatreturn traffic for a VoIP
call hasthe same guaranteed bandwidth
as an outgoing call.
For Logging Options, select All
Sessions for testing purposes.
136
Getting Started

and create a security policy for FTP
traffic.
Getting Started
137

and createasecurity policy for daily webbased, email traffic, and other traffic.
You can also edit your existing general

access security policy.
Arrangeyour policies are in the following

order:
Clickon the far left of the column you

want to move and drag it up or down to
arrange it.
1. High-priority (SIP/VoIP traffic)
2. Low-priority (FTP traffic)
3. Medium-priority (Day-to-daytraffic)
More specific restrictive policies, like the

SIP and FTP policies, should always be
placed at the top of the list, above the
unrestricted general access policy that
allows "all".
138
Getting Started
6. Results
Browse the Internet using a PC on
yourinternal network to generate daily
webtraffic. Then, generate FTP traffic.
In this example, a 56.1 MB file

wasdownloaded from an FTP server.
The FTPdownload or uploadshould
occur slowly.
Finally, generate SIP traffic.
In this example, SIP traffic was

generated byplacing a call witha VoIP
FortiFone connected to theinternal
interface of the FortiGate.
Traffic Shaper Monitor and report by
the Current Bandwidth. You cansee
how much of your current bandwidth is
being used by active traffic shapers. If
the standard traffic volume is high
enough, it will top out at the maximum
bandwidth defined by each shaper.
In the screenshot, the SIP trafficis only

using a small part of theallocated
bandwidth.
You will have normal voice quality on
your VoIP call, even withdaily traffic and
FTP downloads running.
Getting Started
139
Go to Log & Report > Log & Archive

Access > Traffic Log and filter the
Service by SIP to see yourVoIPtraffic.
Select anindividual log message to view
the shaper name in theSent Shaper
Name field.
For further reading, check out Traffic

Shaping in the FortiOS 5.2 Handbook.
140
Getting Started
In this example you will configure your FortiGate to use Stateless Address Auto Configuration (SLAAC) to assign
IPv6 addresses to IPv6-enabled devices on your internal network.
The IPv6 address block used in this recipe (2001:db8::/32) is reserved for documentation purposes and will not
work on your network. If youre not sure how to determine the correct IPv6 address for your environment, refer to
the FortiOS IPv6 Handbook Chapter.
Getting Started
141
1. Enabling IPv6
Go to System > Config > Features
and make sure that IPv6 is turned
ON.
2. Configuring a FortiGate interface for IPv6

Go to System > Network >
Interfaces and edit the interface
connected to your internal network (in
the example, port1).
Set the IPv6 Addressing mode to
Manual
and enter the IPv6 Address/Prefix
for the interface (in this example,
2001:db8::1/32).
The interface can have both IPv4 and
IPv6 addressing. This example only
includes IPv6 addressing.
Enter this CLI command to add the
router advertisements and specific
IPv6 prefixes required to configure
SLAAC on the interface.

edit port1
config ipv6
set ip6-address 2001:db8::1/32
set ip6-send-adv enable
The set ip6-address option is

not required since you already added
an IPv6 address to the interface from
the GUI. But its included in the
example to show the complete CLI
configuration.
config ip6-prefix-list
edit 2001:db8::/32
set autonomous-flag enable
set onlink-flag enable
end
end
end
Getting Started
142
3. Adding IPv6 firewall addresses

Addresses > Create New.
Add an IPv6 firewall address that
matches the IPv6 address added to
the port1 interface.
4. Bouncing the IPv6 interface

You can now bounce the port1 interface (bring the interface down and then back up). Go to System > Network
> Interfaces, edit the port1 interface and set the Administrative Access to Down. Select OK, then edit the
interface again and set the Administrative Access back to Up. This causes a router advertisement using the
Neighbor Discovery Protocol, which performs address autoconfiguration and determines the reachability of
neighboring nodes.
Alternatively, you can reboot the FortiGate or wait for the next router advertisement.
5. Results
Connect a computer to the port1
interface. Configure the computer to
get an IPv6 address automatically.
Then, from a command prompt or
terminal session enter the command
ipconfig to view the computer's IP
configuration.
IPv6 Address............: 2001:db8::44d2:ed21:9733:9245
You should see that an IPv6 address

has been assigned with the prefix
advertised on the port1 interface.
For further reading, check out IPv6 in the

143
Getting Started
This example shows how to set an internet connection using a 3G/4G modem and a FortiExtender. A
FortiExtender is used when the FortiGate unit is located in an area without 3G/4G network coverage, the
FortiExtender can be placed near a window or outdoors.
For information about the compatibility ofFortiExtenderand various modems, see the FortiGate and FortiExtender
Modem Compatibility Matrix.
Getting Started
144
1. Installing the 3G/4G modem in the FortiExtender

Remove the housing cover of the
FortiExtender and use the provided USB
extension cable to connect your 3G/4G
modem to the device.
For more information on installing the
3G/4G modem, see the QuickStart
Guide.
2. Connecting the FortiExtender

Use an Ethernet cable to connect the FortiExtender to the lan interface of a FortiGate unit.
Once connected, FortiGate can control FortiExtender and modem.
Enable FortiExtender in the FortiGates
CLI.
CAPWAP service must be enabled on
the port to which FortiExtender is
connected, lan interface in this example.

set fortiextender enable
set wireless-controller enable
end
edit lan
append allowaccess capwap
end
end
Once enabled, it appears as a virtual

WAN interface in the FortiGate, such as
fext-wan1. Go to System > Network >
Interface to verify fext-wan1 interface.
Getting Started
145
3. Configuring the FortiExtender

FortiExtender and authorize the
FortiExtender.
Once authorized, you can see the status

of the FortiExtender.
146
Getting Started
4. Modem settings
The FortiExtender unit allows for two
modes of operation for the modem; On
Demand and Always Connect.
FortiExtender and click on Configuring
Settings.
Select Always Connect for Dial Mode
and keep other settings to default.
5. Configuring the FortiGate

and add new route through fext-wan1
interface.
Getting Started
147

and create a new security policy allowing
traffic from lan interface to fext-wan1
interface.
6. Results
Browse the Internet and go to Policy &
Objects > Policy > IPv4 to verify the
Count.
148
Getting Started

Forward Traffic.
You can see that traffic flowing from lan
interface to fext-wan1interface.
For further reading, check out FortiExtender

in the FortiOS 5.2 Handbook.
Getting Started
149
In this recipe, you set up a FortiGate with a secondary IP to provide remote access to a FortiRecorder. This allows
you to securely view live FortiCamera video feeds over the Internet, using either the FortiRecorder GUI,
FortiRecorder Mobile, or FortiRecorder Central.
This recipe employs a secondary IP and two port forwarding virtual IPs to forward HTTPS and Real Time
Streaming Protocol (RTSP) packets from the Internet to the FortiRecorder. To use a secondary IP address you
must have a second Internet IP address for your FortiRecorder. Instead of adding this IP address to the
FortiRecorder, you add it to your FortiGate and forward traffic for the FortiRecorder IP address through the
FortiGate.
Getting Started
150
1. Connect the hardware

Connect your devices as shown in the
diagram.
In this example, the FortiCamera
connects to a PoE switch, which is then
connected to port3 on the FortiRecorder.
The FortiRecorder's port1connects to
the FortiGate lan interface.
2. Configuring the FortiRecorder and FortiCamera

Onthe FortiRecorder, go to System >
Network > Interface and edit port1. Set
a manual IP/Netmask for the interface
that is on the same subnet as the
FortiGate lan interface (in the example,
192.168.1.99).
SetAccess to allow HTTPS and any
other protocols you require. If you are
using FortiRecorder Central, you must
enableFRC-Central.
Getting Started
151
Edit port3. Make sure that Discover

cameras on this port is enabled.Set a
manual IP/Netmask for the interface.
Go to System > Network > DHCP and

create a new DHCP server. Set
Interface to port3 andGateway to
port3's IP address (in the example,
192.168.200.2).
Create a new DHCP IP Range that is on
the same subnet as port3.
152
Getting Started
Go to System > Network > Routing.

Add a default route that uses the IP
address of the FortiGate's lan interface
(in the example, 192.168.1.2). Set
Interface to port1.
Go to Camera > Configuration >
Camera. Click on Force Discover to
have connected cameras displayed.
The FortiCamera will appear on the list,
with the Status column displayed as Not
Configured.
Select the FortiCamera and select
Configure. Set the unit'sName
andLocation, andProfile, as well as
any other required configuration settings.
If you do not have any profiles already

created, you will have to configure one.
For more information, see the
FortiRecorder 2.0.0 Administration guide.
3.Adding a secondary IP to the FortiGate

From the FortiGate GUI, go to System >
Network > Interfaces and edityour
Internet-facing interface.
EnableSecondary IP Address and
create a new IP/Network Mask for the
interface.
Getting Started
153
Adding a secondary IP address allows

the FortiGate and the network to see two
IP addresses, the primary and the
secondary,that terminate at the
interface.
In this example, the primary IP address
is used to connect to the FortiGate, while
the secondary IP will be used to connect
to the FortiRecorder.
4. Creating virtual IPs

From the FortiGate GUI, go to Policy
&Objects >Objects > Virtual
IPs.Create the two virtual IPs: one for
HTTPS traffic and one forRTSP traffic.
For both virtual IPs, set External
Interface to your Internet-facing
interface,External IP Address/Range
to the secondary IP of that interface (in
the example, 172.20.120.237)and the
Mapped IP Address/Range to the IP of
port1 on the FortiRecorder unit(in the
example, 192.168.1.99).
EnablePort Forwarding and use the
standard port for each protocol. HTTPS
uses TCP port 443 and RTSP uses TCP
port 554.
154
Getting Started
If you are using FortiRecorder Central,

you must create a third virtual IP to allow
TCP port 8550.
5. Creating a security policy to access to the FortiRecorder

Go to Policy & Object > Policy > IPv4
and create a new policy that allows
access to the FortiRecorder from the
Internet.
Set Incoming Interface to your Internetfacing interface, Outgoing Interface to
lan, andDestination Address to the
new virtual IPs.
Getting Started
155
6. Configuring FortiRecorderMobile for iOS

On your FortiRecorder, go toSystem >
Configuration > Options.
SetFortiRecorder Mobileto useHLS
over HTTPS.
You can also connect using HLS over
HTTP, as long as you add another virtual
IP to allowTCP port 80.
FortiRecorder Mobile for iOS

Downloadthe FortiRecorder Mobile app onto your iOS device.
If you will connect using HTTPS, the iOS device must be able to verify the FortiRecorder certificate. To do this,
you can either sign the FortiRecorder local certificate with one of the world's largest certificate authorities,
whose CA certificate are trusted by the iOS device, or install the CA certificate on the iOS device, if the CA
certificate is not trusted by the iOS device.For information about this, see the technical noteProvisioning CA
Certificate to iOS Devices for FortiRecorder Mobile.
Open FortiRecorder Mobile. Use the + to
add a new location.
Enter the information for the
FortiRecorder device, including the
Address (in the example,
172.20.120.237) and the admin account
username and password.
156
Getting Started
The FortiRecorder is shown in the list

ofLocations.
FortiRecorder Mobile for Android

Downloadthe FortiRecorder Mobile app onto your Androiddevice.
Getting Started
157
Open FortiRecorder Mobile. Select Add

Location.
Enter the information for the
FortiRecorder device, including the
Address (in the example,
172.20.120.237) and the admin account
username and password.
The FortiRecorder is shown in the list

ofLocations.
158
Getting Started
7. Configuring FortiRecorder Central

FortiRecorder Central is a Windows-based video management system that is used to connect and view
information from several FortiRecorder units at the same time. It can be downloaded at the Fortinet Support
website.
The recipe was written using FortiRecorder Central 1.0.0.
From FortiRecorder Central,use the
Settings cogwheel in the topright corner
to go toSettings > Users. Make sure
theadmin account settings are identical
to those on the FortiRecorder because
FortiRecorder Central has to be able to
log into FortiRecorder using these
credentials.
All FortiRecorders must use the same

admin credentials in order to be used by
FortiRecorder Central.
Go to Settings > Recorders. Set

theIPto the FortiGate's secondary IP (in
this example, 172.20.120.237).
The FortiRecorder will appear in the list

of devices, withits connected cameras
listed underneath.
Getting Started
159
8. Results
From the Internet you can browse to the
secondary IP address, using HTTPS (in
the example, https://172.20.120.237).
The FortiRecorder GUI login screen
appears.
Go toMonitor > Video Monitorto see
the live video feed from the FortiCamera.
Quicktime 6.0 or higher is required to

view theVideo Monitor.
In FortiRecorder Mobile for iOS, go the

the Locations list andselect the
FortiRecorder. A list of the available
cameras will be shown. Click on the
camera you wish to view.
160
Getting Started
In FortiRecorder Mobile for Android, go

the the Locations list andselect the
FortiRecorder, then selectCameras. A
list of the available cameras will be
shown. Click on the camera you wish to
view.
In FortiRecorder Central, click on the

listing for the FortiCamera and drag it
onto a square in the grid. The live video
feed will be shown.
Getting Started
161

Manage up to 16 FortiSwitches from the FortiGate web-based manager or CLI. You can create and assign VLANs
and configure port information. The connection between the FortiSwitch and the FortiGate is called a FortiLink.
Prerequisites
l
Connect a cable from the highest FortiSwitch port to an unused port on the FortiGate. For example, use
port 24 on the FS-224D-POE switch.
You may need to enable the Switch Controller using the FortiGate web-based manager.
Turn on the WiFi & Switch Controller feature.
Select Apply.
This recipe is applicable to FortiSwitchOS 3.3.0 and above.
Getting Started
162
Procedure
From the FortiGate web-based manager:
1. Go to System > Network > Interfaces and edit an internal port.
2. Set Addressing mode to Dedicate to Extension Device.
3. Select OK. The FortiSwitch should now be visible
4. Go to WiFi & Switch Controller > Managed Devices > Managed FortiSwitch.
Right-click on the switch and select Authorize.
-> After a delay (while FortiGate processes the request), an icon with a checkmark appears in the Status
column. For smaller FortiSwitch models, such as FS-108D-POE, the delay may be up to 3 minutes.
Notes
1. In some FortiSwitch models (such as FS-124D), the highest port is an optical interface, which requires an
SFP module.
2. In FortiOS 5.4, additional FortiLink features include:
a. POE configuration from the FortiGate
b. Link Aggregation Group (LAG) support for Fortilink
c. Auto-detect the switch FortiLink port. Removes the restriction that only the highest port on the
switch can be used for FortiLink
3. Refer to the document below to see the FortiSwitch and FortiGate releases that support FortiLink, and the
supported FortiSwitch and FortiGate models in each release.
For additional information, see Managing

FortiSwitch with a FortiGate (FortiOS 5.2),
which is also available in the FortiOS 5.2
Handbook.
Getting Started
163
Authentication
This section contains information about authenticating users and devices.
Authentication, the act of confirming the identity of a person or device, is a key part of network security. When
authentication is used, the identities of users or host computers must be established to ensure that only
authorized parties can access the network.
User accounts and device definitions

l
MAC access control
BYOD scheduling
Single Sign-On (SSO)

l
Authentication with other technologies

l
WiFi local authentication

l
Guest WiFi accounts
WiFi remote authentication

l
Authentication
164
Authentication for VPNs
165
Authentication
In this example, user authentication and device authentication provide different access for staff members based
on whether they are full-time or part-time employees, while denying all traffic from mobile phones.
In this example, a wireless network has already been configured that is in the same subnet as the wired LAN. For
information about this configuration, see Setting up a WiFi bridge with a FortiAP.
Authentication
166
1. Defining two users and two user groups

Go to User & Device > User > User
Definitions.
Create two new users (in the example,
dprince and rmontoya).
Authentication
167
Both user definitions now appear in the

user list.

Groups.
Create the user group full-time and add
user dprince.
Create a second user group, part-time,
and add user rmontoya.
2. Creating a schedule for part-time staff

Schedules and create a new recurring
schedule.
Set an appropriate schedule. In order to
get results later, do not select the current
day of the week.
3. Defining a device group for mobile phones

Device Groups and create a new group.
Add the various types of mobile phones
as Members.
168
Authentication
4. Creating a policy for full-time staff

Set Incoming Interface to the local
network interface, Source User(s) to
the full-time group, Outgoing Interface
to your Internet-facing interface, and
ensure that Schedule is set to always.
Turn on NAT.

5. Creating a policy for part-time staff that enforces the schedule

network interface, Source User(s) to
the part-time group, Outgoing Interface
to your Internet-facing interface, and set
Schedule to use the part-time schedule.
Turn on NAT.
Authentication
169

View the policy list. Click on the title row

and select ID from the dropdown menu,
then select Apply. Take note of the ID
number that has been given to the parttime policy.
config firewall policy

edit 2
and enter the following command into the
set schedule-timeout enable
CLI Console, using the ID number of the
end
part-time policy.
end
This will ensure that part-time users will
have their access revoked during days
they are not scheduled, even if their
current session began when access was
allowed.
170
Authentication
6. Creating a policy that denies mobile traffic

network interface, Source Device to
Mobile Devices (a default device group
that includes tablets and mobile phones),
Outgoing Interface to your Internetfacing interface, and set Action to
DENY.

enable device identification on the local
network interface.
Leave Log Violation Traffic turned on.
In order for this policy to be used, it must
be located at the top of the policy list.
Select any area in the far-left column of
the policy and drag it to the top of the list.
Authentication
171
7. Results
Browse the Internet using a computer.
You will be prompted to enter
authentication credentials.
Log in using the dprince account. You will
be able to access the Internet at any
time.
Go to User & Device > Monitor >

Firewall. Highlight dprince and select
De-authenticate.
Attempt to browse the Internet again.
This time, log in using the rmontoya
account. After authentication occurs, you
will not be able to access the Internet.
172
Authentication
Attempts to connect to the Internet using

any mobile phone will also be denied.
You can view more information about the

blocked and allowed sessions by going
to System > FortiView > All Sessions.
Sessions that were blocked when you

attempted to sign in using the rmontoya
account will not have a user account
shown in the User column.
For further reading, check out Users and

user groups in the FortiOS 5.2 Handbook.
Authentication
173
In this example, two company executives are excluded from the security scanning that a FortiGate applies to all
other staff Internet traffic.
The executives in this example connect to the Internet using PCs with static IP addresses, so these addresses
can be used to identify their traffic. If identifying users with a static IP address will not work for your network you
can set up authentication or device identification (BYOD).
Authentication
174
1. Applying security profiles to the staff policy

and edit the general policy that allows
staff to access the Internet.
Filter and Application Control. Set them
to use the default profiles. Also set
SSL/SSH Insection to the deepinspection profile.
To be able to see results enable logging
all sessions.
2. Creating firewall addresses for the executives

Addresses. Create an address for each
executive. Use /32 as the Netmask to
ensure that the firewall address applies
only to the specified IP.
Authentication
175
Select Create New > Address Group

and create an address group for the
executive addresses.
3. Creating a security policy for the executives

and create a policy allowing the
executives to access the Internet. Set
Source Address to Executives. Enable
logging and select Log all Sessions to be
able to view results.
Leave all Security Profiles disabled.
176
Authentication
In the policy list, the policy for executives

(in this example ID=3) must be above the
policy for staff (in this example ID=2).
You can re-order policies by hovering
your mouse cursor over the borders of
the left-most cell of a policy until the
cursor changes into crossed arrows and
then clicking and dragging that policy up
or down into the required order.
Note that in this screen shot the policy ID
(ID) is shown for each policy and the
sequence number (Seq.#) is hidden.
4. Results
Connect to the Internet from two
computers on the internal network: one
from an executive address and one from
a staff address.
Forward Traffic. Right-click the column
headings and make sure that the Policy
ID column is visible.
In this example output, connections from
192.168.13.10 (an executive address)
use policy ID 3 and connections from
192.168.13.144 (a staff address) use
policy ID 2.
For further reading, check out Security

Profiles in the FortiOS 5.2 Handbook.
Authentication
177
In this example, you will configure Fortinet Single Sign-On (FSSO) directly in the security policy using the new
FSSO wizard introduced in FortiOS 5.2.2.
Thisrecipe requires that your FortiGate's DNS point to a DNS server that can resolve the IP addresses or fully
qualified domain names of the users' PCs.
This example uses Active Directory polling to establish FSSO for a Windows AD Domain Controller, without
requiring a FortiAuthenticator or a collector agentto act as an intermediarybetween the FortiGate and the domain.
An LDAP server is also used for authentication.
Authentication
178
1.Adding the LDAP Server to the FortiGate

In the FortiGate web interface, go to
User & Device > Authentication >
LDAP Servers.
For the Server IP/Nameenter theLDAP
Server's fully qualified domain name or
the IP address.
Set theBind Type toRegular and enter
a User DN and Password.
Click Fetch DN to retrieve your
Distinguished Name.
ClickTestandverify that your

connection issuccessful.
2. Configuring the FortiGate unit to poll the Active Directory

Next, go to User & Device >
Authentication > Single Sign-On and
add a new Single Sign-On Server.
For the Type, select Poll Active
Directory Server. Enter the Server
IP/Name, User, and Password, then
select the LDAP Server you added
previously. Make sure Enable Polling is
checked. Add atest user group of your
choice.
You must add at least one user group to

create your SSO server.
Authentication
179
3. Adding a firewall address for the Internal network

Go to Policy & Objects > Objects>
Addressesand create an internal
network address to be used by your
security policy.
4. One-step FSSOconfiguration in the securitypolicy

andedit asecurity policy with access to
the Internet.Set the Source Address to
the Local_LANaddress created in Step
3.
UnderSource User(s) scroll down past

thedropdown menu, and selectCreate
Users/Groupswizard.
180
Authentication
For theUser/Group Type,selectFSSO

and then click Next.
For theRemote Group, select the

appropriateFSSO Agent from the
dropdown menu.
Select the Groups tab and right-click on
the user groups you would like to add.
To add multiple groups, hold the Shiftkey

and click.
Go to theSelected tab.In this example,

Standard_User_Group and Admin_
User_Group are shown.
Click Next.
Authentication
181
Select Create Newand name your new

FSSO user group.
Click Create.
The groups selected have been added to

the new FSSO group,My_Windows_
AD_Group.
To see these groups go to User &

Device > User > User Groups.
Ensure you enable loggingand select All
Sessions.
In the Global View your completed

policy should look similar to
thescreenshot shown on the right.
If necessary, select the policy by clicking
onthe far left column, andmove it as
close as possible to the top of the list.
All other policies must deny Internet

access in order for the user to be forced
to authenticate.
5. Results
ForwardTraffic.
When users log into the Windows AD
network, the FortiGate will automatically
poll the domain for their account
information, and record their traffic.
182
Authentication
Select an entry for more information.
For further reading, check out Single SignOn to Windows AD in the FortiOS 5.2
Handbook.
Authentication
183
In this recipe, two-factor authentication is added to a user account to provide extra security to the authentication
process.
Two-factor authentication requires a user to providefurther means of authentication in addition to their credentials.
In this recipe, FortiToken Mobile app for Android will be used to generate a token, also known as a one-time
password (OTP), to use in the authentication process.
Authentication
184
1. Activating your FortiTokens

Ensure that your FortiGate is connected to the Internet. Go to User & Device > FortiTokens. Your FortiGate
may have two FortiToken Mobile entries listed by default. If so, you may use these tokens and go to step 2.
To add new FortiTokens, select Create
New. Set Type to Mobile Token and
enter your Activation Code.
An error stating that the serial number is

invalid will appear if you mistyped the
code or if it duplicatesone you have
already entered.
After FortiGuard validates the code, your
FortiTokens will appear on the list, with
Status set to Available
If the FortiToken has already been

registered to another FortiGate, the
Status will be Error.
2. Creating a user account with two-factor authentication

Definition and create a new local user.
Authentication
185
In order to use the FortiToken Mobile,

you must enter a mobile number in the
third step, Provide Contact Info. Select
the appropriate Country/Region and
enter the Phone Number without
dashes or spaces. Do not add an email
address.
In the fourth step of the User Creation
Wizard, Provide Extra Info, enable
Two-Factor Authentication and select
an available token.
The user list shows the FortiToken in the

Two-factor Authentication column for
the new user account.
Go to User & Device > FortiTokens.
The FortiToken assigned to the user is
now listed as Pending, until the user
activates the FortiToken.
186
Authentication
3. Sending the activation code to the user

If your FortiGate can send SMS
messages, go to User & Device > User
> User Definition and edit the new user
account. Select Send Activation Code
and send the code by SMS.
If your FortiGate cannot send SMS

messages, go to System > Dashboard
> Status and enter the following into the
CLI Console, substituting the correct
serial number:
config user fortitoken

edit serial number
show
The activation code will be shown in the

output. This code must be given to the
user.
Authentication
187
4. Adding user authentication to your Internet access policy

the Internet. Set Source User(s) to the
new user account.
5. Setting up FortiToken Mobile on an Android device

Using your Android device, download and install FortiToken Mobile.
Open the app and add a new account.
Select Enter Manually. Enter the
activation code into FortiToken Mobile.
188
Authentication
FortiToken Mobile can now generate a

token for use with the FortiGate.
(Optional) For additional security, set a PIN for FortiToken Mobile using the app's Settings options.
6. Results
Attempt to browse the Internet. An
authentication page will appear,
requesting a Username and Password.
Authentication
189
After the correct username and password

are entered, a FortiToken code will be
requested. Enter the code currently
shown in the FortiToken Mobile app.
Once the token is authenticated, you can
connect to the Internet.
For further reading, check out FortiToken in

190
Authentication
Security
This section contains information about using a FortiGates security features, including antivirus, web filtering,
application control, intrusion protection (IPS), email filtering, and data leak prevention (DLP). This section also
includes information about using SSL inspection to inspect encrypted traffic.
AntiVirus
l
Blocking Ultrasurf
Application Control
l
Blocking Ultrasurf
Data Leak Prevention

l
Intrusion Protection
l
SSL Inspection
l
Security
191
Web Filtering
192
Blocking Facebook
Security

If you include both FortiOS 5.0 and 5.2, there are three AntiVirus (AV) scanning inspection modes available.
FortiOS 5.0 includes proxy and flow-based virus scanning. FortiOS 5.2 also uses proxy-based and flow-based
scanning, but the flow-based mode in FortiOS 5.2 uses a new approach to flow-based scanning (that is
sometimes called deepflow or deep flow scanning).
AV Scanning 101
AntiVirus scanning examines files in HTTP, HTTPS, email, and FTP traffic for threats as they pass through your
FortiGate unit. If the AV scanner finds a threat such as a virus or some other malware, FortiOS protects your
network by blocking the file.
FortiOS includes a number of AntiVirus features that make virus scanning more user friendly. One of these
features, called replacement messages, sends a customizable message to anyone whose file is blocked by AV
scanning, to explain what happened and why. Other features make communication between the client and the
server more seamless. The availability of these changes depending on the inspection mode.
Proxy-based AV scanning
Proxy-based AV scanning is the most secure and feature-rich AV scanning mode. This mode uses a proxy to
manage the communication between client and server. The proxy extracts content packets from the data stream
as they arrive and buffers the content until the complete file is assembled. Once the file is whole, the AV scanner
examines the file for threats. If no threats are found, the file is sent to its destination. If a threat is found, the file is
blocked.
Because proxy-based scanning is applied to complete files it provides very effective threat detection. Proxybased scanning also supports the a full range of features, including replacement messages and client comforting,
making proxy-based scanning the most user friendly inspection mode. In addition the proxy manages the
communication between the client and the server, so communication is cleaner.
Proxy-based scanning inspects all files under the oversized threshold. This threshold is 10 MB by default but can
be reconfigured. Any files larger than the threshold are considered oversized and not inspected.
Flow-based AV scanning
Although the name "flow-based scanning" is used in both FortiOS 5.0 and 5.2, the two different versions handle
this mode in very different ways.
Flow AV in FortiOS 5.0

In FortiOS 5.0, flow-based AV scanning scans the content of individual data packets as they pass through the
FortiGate. There is no proxy involved so packets are not changed by the proxy and files are not buffered for
Security
193
analysis. Potentially less memory and CPU resources are used, resulting in a potential performance increase
compared to using proxy-based mode. FortiOS 5.0 flow-based AV scanning is also not limited by file size.
Flow AV uses the IPS engine and the AV database and is effective at many kinds of threat detection; however,
because it can only analyze what is in an individual packet rather than a complete file, flow-based scanning cannot
detect some types of malware, including polymorphic code. Malware in documents, compressed files, and some
archives are also less likely to be detected.
Flow AV does not actually block files, it stops delivering the rest of the file once a threat has been detected. This
means that parts of the file may already have been delivered when the threat has been detected and the recipient
application is responsible for dealing with the partially complete content.
In addition flow AV can be less user friendly. Replacement messages are not supported and clients may have to
wait for sessions to time out without knowing why content has been blocked.
Flow AV in FortiOS 5.2 (deepflow or deep flow)

FortiOS 5.2 introduced a new type of flow-based AV scanning, that is sometimes called deepflow or deep flow,
and that takes a hybrid approach where content packets are buffered while simultaneously being sent to their
destination. When all of the files packets have been collected and buffered, but before the final packet is delivered,
the buffered file is scanned. If a threat is found, the last packet is blocked and the client application has to deal
with not getting the completed file. If no threat is found the final packet is sent and the user gets their file.
Deepflow AV scanning is as good as proxy-based AV scanning at detecting threats. There may be a small
performance advantage over proxy-based AV as files get larger based on the difference between sending the
whole file after analysis and just sending the last packet. Deepflow's most notable limitation is that, just like the
flow-based AV in 5.0, it does not support many of the user-friendly features provided by proxy-based AV.
The future of AV scanning

One of the current plans for FortiOS 5.4 is to add a new, "quick" mode for AV scanning.
194
Security
In this recipe, you will apply antivirus scanning to your network traffic. Any suspicious files entering your network
will be sent to a FortiSandbox for further examination.
This recipe was written using FortiSandbox 2.1.0.
Security
195
1. Connecting the FortiSandbox

Connect the FortiSandbox to your
FortiGate as shown in the diagram, so
that port 1 and port 3 on the FortiSandbox
are on different subnets.
Port 3 on the FortiSandbox is used for
outgoing communication triggered by the
execution of the files under analysis. It is
recommended to connect this port to an
isolated interface on your FortiGate (in
the example, port 15), to protect the rest
of the network from threats currently
being investigated by the FortiSandbox.
The FortiSandbox requires Internet
access on port 3. On the FortiGate, go to
Policy & Objects > Policy > IPv4 and
create a policy allowing connections from
the FortiSandbox to the Internet (using
the isolated interface on the FortiGate
mentioned above).
On the FortiSandbox, go to System >

Network > Static Routing and add
static routes for both port 1 and port 3.
The static route for port 3 must have the
Destination/IP Mask 0.0.0.0/0.0.0.0,
while port 1 is assigned the
Destination/IP Mask for traffic in the
local network.
Security
196
Once the FortiSandbox has access to

the Internet through port 3, it will begin to
activate the VM licenses.
Before continuing with this recipe, wait
until a green arrow shows up beside
Windows VM in the FortiSandbox's
System Information widget, found at
System > Status. This indicates that the
VM activation process is complete.
2. Enabling Sandbox Inspection

On the FortiGate, go to System > Config
> FortiSandbox. Select Enable
Sandbox Inspection and select
FortiSandbox Appliance.[tippy title="*"
class="myclass" showheader="false"
width="auto" height="auto"]If you have a
FortiCloud account, you can also select
FortiSandbox Cloud.[/tippy]
Set the IP Address (in the example,
172.20.121.128) and enter a Notifier
Email, where notifications and reports
will be sent.
After you select Apply, select Test
Connectivity. The Status shows as
unreachable, because the FortiGate
has not been authorized to connect to the
FortiSandbox.
197
Security
On the FortiSandbox, go to File-based

Detection > File Input > Device. Edit
the entry for the FortiGate.
Under Permissions, enable Authorized.
On the FortiGate, go to System > Config

> FortiSandbox and select Test
Connectivity. The Status now shows
that Service is online.
Security
198
3. Enabling FortiSandbox in the default AntiVirus profile

On the FortiGate, go to Security Profiles
> AntiVirus and enable Send Files to
FortiSandbox for Inspection.
4. Applying AntiVirus scanning to network traffic

On the FortiGate, go to Policy & Objects
> Policy > IPv4 and view the policy list.
If the AV column is not visible, right-click
on the title row, select AV, and select
Apply.
If any security policy does not have
AntiVirus applied, highlight that policy to
make the None option visible in the AV
column. Select None, then use the
Select Profile option to set the policy to
use the default profile.
In order to ensure that AntiVirus is
applied to encrypted traffic, you must
also make sure that the deepinspection profile is used for SSL
Inspection.
Using the deep-inspection profile may

cause certificate errors. For information
about avoiding this, see Preventing
certificate warnings.
5. Results
199
Security
If your FortiGate discovers a suspicious

file, it will now be sent to the
FortiSandbox. To view information about
the files that have been sent on the
FortiGate, go to Status > FortiView >
FortiSandbox to see a list of files names
and current status.
You can also view results on the

FortiSandbox, by going to System >
Status and viewing the Scanning
Statistics widget.
There may be a delay before results

appear on the FortiSandbox.
Security
200
Blocking Ultrasurf
In this recipe, you will use antivirus scanning and application control to block network users from downloading and
using Ultrasurf. As mentioned in a recent SysAdmin Note, Ultrasurf is an application that is used to bypass
firewalls and browse the Internet anonymously.
In order to complete the final part of this recipe, download Ultrasurf before any security scanning is applied to your
Internet traffic.
Security
201
1. Enabling AntiVirus and Application Control

make sure both AntiVirus and
Application Control are enabled. If
necessary, Apply your changes.
2. Editing the default Application Control profile

Go to Security Profiles > Application
Control and edit the default profile.
Under Applications Override, select
Add Signatures.
Search for ultrasurf. Select the
signatures, then select Use Selected
Signatures.
The signatures will be added to the list,

with Action set to block. You will also
need to block the signature
Freegate.Searching.
If you want to include all proxy
applications, you can also choose to
block the entire Proxy category.
Security
202
3. Adding AntiVirus and Application Control profiles to a security policy

the Internet.
Under Security Profiles, enable both
AntiVirus and Application Control and
set both to use to default profiles. Set
SSL/SSH Inspection to deepinspection.

certificate warnings
4. Updating your AntiVirus and IPS definitions

Because Ultrasurf is constantly
changing, it is recommended to update
your AntiVirus and IPS definitions
regularly, so that you can continue later
versions of the application.
To set up regular updates, go to System
> Config > FortiGuard and expand AV
& IPS Download Options. Select an
appropriate time for definitions to be
downloaded.
You can also manually push an update
by selecting Update Now.
203
Security
5. Results
Attempt to browse to ultrasurf.us. The
page will not load.
On your FortiGate, go to Log & Report >
Traffic Log > Forward Traffic and filter
for Destination IP: 65.49.14.131 (the
IP of ultrasurf.us). Traffic to this
destination was blocked by the
FortiGate.
Attempt to download the Ultrasurf files
from a third-party website, such as
Download.com.
The download will be blocked.
This result may vary based on which

browser is being used. In the example,
Firefox version 40.0.3 was used.
Attempt to use the copy of Ultrasurf you
downloaded on your computer before
starting this recipe. You will be unable to
contact a server.
On your FortiGate, go to System >
FortiView > Applications > 5 minutes,
you will see that the FortiGate has
blocked Ultrasurf.
You may have to exit Ultrasurf in order to

connect to your FortiGate.
For further reading, check out AntiVirus and

Application control in the FortiOS 5.2
Handbook.
Security
204
In this example, you will learn how to use Application Control to monitor traffic and determine if there are any
applications currently in use that should not have network access. If you discover any applications that you wish
to block, application control will then be used to ensure that these applications cannot access the network.
Security
205
1. Enabling Application Control and multiple security profiles

ensure that Application Control is
turned ON.
Select Show More and enable Multiple

Security Profiles.
Apply the changes.
2. Using the default application profile to monitor network traffic

Control and view the default profile.
A list of application Categories is
shown. By default, most categories are
already set to Monitor. In order to
monitor all applications, select All Other
Known Applications and set it to
Monitor. Do the same for All Other
Unknown Applications.
The default profile also has Deep
Inspection of Cloud Applications turned
ON. This allows web-based applications,
such as video streaming, to be monitored
by your FortiGate.
Security
206
3. Adding the default profile to a security policy

the Internet.
Under Security Profiles, turn on
Application Control and use the default
profile.
Enabling Application Control will
automatically enable SSL Inspection. In
order to inspect traffic from Cloud
Applications, the deep-inspection
profile must be used.

about avoiding this, seePreventing
3. Reviewing the FortiView dashboards

Go to System > FortiView >
Applications and select the now view.
This dashboard shows the traffic that is
currently flowing through your FortiGate,
arranged by application (excluding Cloud
Applications).
207
Security
If you wish to know more about an

applications traffic, double-click on its
entry to view drilldown information,
including traffic sources, traffic
destinations, and information about
individual sessions.
Similar information can be viewed for

Cloud Applications by going to System >
FortiView > Cloud Applications and
selecting Applications that have been
used in the last 5 Minutes.
Cloud Applications also have drilldown
options, including the ability to see which
videos have been viewed if streaming
video traffic was detected.
5. Creating an application profile to block applications

In the above example, traffic from BitTorrent, a Peer-to-Peer (P2P) downloading application, was detected.
Now, you will create an application control profile that will block P2P traffic.
The new profile will also block all applications associated with YouTube, without blocking other applications in
the Video/Audio category.
Security
208

Control and create a new profile.
Select the P2P category and set it to
Block.
Under Application Overrides, select

Add Signatures.
Search for Youtube and select all the
signatures that are shown.
Select Use Selected Signatures.
209
Security
The signatures have been added to the

Application Overrides list and have
automatically been set to Block.
Enable Deep Inspection of Cloud
Applications.
6. Adding the blocking profile to a security policy

the Internet.
Set Application Control to use the new
profile.
Security
210
7. Results
Attempt to browse to YouTube. A
warning message will appear, stating
that the application was blocked.
Traffic from BitTorrent applications will

also be blocked.
To see information about this blocked
traffic, go to System > FortiView > All
Sessions, select the 5 minutes view,
and filter the traffic by application.
For further reading, check out Application

control in the FortiOS 5.2 Handbook.
211
Security
In this example, you will use application control to block web traffic from PCs running Windows operating systems
that NT 5, including Windows XP and Windows Server 2003 (includes Windows virtual machines).
When a computers operating system lacks vendor support, it becomes a threat to the network because newly
discovered exploits will not be patched. Using the FortiGate application control feature, you can restrict these
computers from accessing external resources.
This recipe will only block web traffic from computers running the affected operating systems. If you wish to block
these computers from being on the network entirely, further action will be necessary. However, the logs
generated by this recipe can be used to identify the computers you wish to block.
Security
212
1. Enabling Application Control

Go to System > Config >
Features. Enable Application
Control andApply your changes.
2. Creating a custom application control signature

Go to Security Profiles >
Application Control and select
View Application Signatures.
Create a new signature with this
syntax. (You can copy and paste
this text into the Signature field.)
F-SBID(--attack_id 8151; --vuln_id 8151; --name
"Windows.NT.5.Web.Surfing"; --default_action drop_
[glossary_exclude]session[/glossary_exclude]; -service [glossary_exclude]HTTP[/glossary_exclude]; -protocol tcp; --app_cat 25; --flow from_client; -pattern "Windows NT 5."; --no_case; --context header;
)
The signature will appear at the
top of the application list and be
listed in the Web.Others
category.
Security
213
3. Adding the signature to the default Application Control profile

Go to Security Profiles >
Application Control and edit the
default policy.
Under Application Overrides,
select Add Signature.
The new signature should appear

at the top of the list. If it does not,
search for the signatures name
(in the example, Block-WindowsNT5).
Select the signature, then select
Use Selected Signatures.
214
Security
4. Adding the default profile to a security policy

Go to Policy & Objects > Policy
> IPv4 and edit the policy that
allows connections from the
internal network to the Internet.
Application Control and use the
default profile.
5. Results
When a PC running one of the
affected operating systems
attempts to connect to the
Internet using a browser, a
blocked message appears.
PCs running other operating
systems, including later versions
of Windows, are not affected.
Go to System > FortiView > All

Sessions and select the 5
minutes view.
Filter the results to show
sessions that were blocked.
Security
215
You will see that the Application

Control signature, shown in
theApplication Name column,
was used to block traffic from
PCs running older Windows
versions (in the example, the
device Joscelin).
For further reading, check out Custom

Application & IPS Signatures in the FortiOS
5.2 Handbook.
216
Security
In this recipe, you will allow one user to use the Tor browser application for web traffic, while monitoring the user's
activity. Use of the Tor browser will be blocked for all other users.
The Tor browser allows users to bounce communication traffic around a distributed network of relays located
around the world. For more information about Tor, check out the Fortinet blog entry 5 Things To Know About The
Tor Browser And Your Network.
This recipe uses the default application control signatures for the Tor client and web-based Tor. These signatures
will only match unmodified versions of the Tor application. Also, if a Tor session has already been established
prior to connecting to the network, it may take up to 10 minutes before the FortiGate is able to monitor or block the
traffic.
In this recipe, two user accounts,jack and jill, have already been configured. For more information about creating
user accounts, see User and device authentication.
Security
217
1. Enabling Application Control and multiple security profiles

ensure that Application Control is
turned ON.

Security Profiles.
Apply the changes.
2. Blocking Tor traffic using the default profile


Add Signatures.
Search for Tor, then filter the results to
show only the Proxy category. Two
signatures will appear: one for the Tor
client and one for web-based Tor use.
Highlight both signatures, and select
Use Selected Signatures.
Security
218
Both signatures now appear in the

Application Overrides list, with the
Action set to Block.
3. Creating a profile that monitors Tor traffic

Control and create a new profile. Under
Application Overrides, select Add
Signatures.
Search for and highlight both signatures,
and select Use Selected Signatures.
In the Application Overrides list,
double-click on the Action for each
profile, and set it to Monitor.
4. Adding the application control profiles to your security policies

the Internet. Make sure the user jack is
included in the Source User(s).
Application Control and use the default
profile.
219
Security
Create a second policy allowing

the Internet. Set Sourse User(s) to jill.
Application Control and use the profile
that will monitor Tor traffic.

and view the policy list.
It is best to place more narrowly defined
policies at the top of the list. In this case,
the policy that monitors Tor is the most
narrowly defined, because it is likely that
less people will be using it than the policy
that blocks Tor.
Seq.#) and drag the policy to the desired
position.
5. Results
The Tor browser cannot be used for user authentication, so use a different browser to authenticate using jill's
credentials.
Browse the Internet using the Tor browser. You will be able to connect to the Internet.
Security
220

You will see a listing for the Tor traffic.
If you double-click on the listing, you can

view more information about this traffic,
including detailed information on the
sessions.
Firewall. Select the jill account and
select De-authenticate.
Authenticate using jack's credentials. The Tor browser will be blocked.

You will see that Tor traffic has been
blocked.

221
Security
In this recipe, access to Apples App Store is blocked between 7AM and 5PM. During the rest of the day, access
is allowed.
This recipe applies to devices running MacOS and iOS devices (iPhone, iPad, or iPod).
Security
222
1. Enabling Application Control

ensure thatApplication Control is
turned ON.
2. Blocking the App Store


Add Signatures.
Search for Apple. Highlight the
Apple.Store signature, then select Use
Selected Signatures.
If you wish to restrict updates from the
App Store, you should also select the
Apple.Software.Update signature.
Security
223
The signature now appear in the

Application Overrideslist, with the
Action set toBlock.
3. Creating a schedule
Schedules and create a new schedule.
SetTypetoRecurring, select the
appropriateDays, and setStart Time to
7AM (Hour 7, Minute 0) andStop Time to
5PM (Hour 17, Minute 0).
4. Creating a security policy to block the App Store

Go toPolicy & Objects > Policy > IPv4
and create a new policy thatallows
the Internet.
SetSchedule to the new schedule.
EnableApplication Control and set it to
use the new profile.
Enabling Application Control will
automatically enableSSL Inspection. In
order to inspect traffic from Cloud
Applications, the deep-inspection
224
Security
5. Ordering the security policies

If you do not have a general policy that allows connections from the internal network to the Internet without
blocking the App Store, you will need to create one before you can continue with this step.
Go toPolicy & Objects > Policy >
IPv4and view yourlan - wan1 policies.
In the example, thegeneral policy
allowing Internet access appears first in
the list, followed by the new policy that
blocks the App Store. To make sure the
App Store is blocked, you must re-order
the policies so that the new policy is
higher on the list.
Seq.#) and drag the policy to its new
position.
6. Enforcing the schedule

Go toSystem > Dashboard > Status
and enter the following into theCLI
Console, substituting the correct Policy
ID for the new policy.
This ensures that the App Store is
consistently blocked between 7AM and
5PM, even forsessions that start before
7AM.
Security

edit <policy-id>
end
end
225
7. Results
On a Mac or iOS device, attempt to run
theApp Store application between 7AM
and 5PM. The application will not be able
to fully load and no new apps can be
downloaded.
You can find information about the

blocked traffic by going toSystem >
FortiView > Applications and selecting
the5 minutes view.
After 5PM, you will be able to connect to the App Store.

226
Security
In this example, online gaming will only be allowed from 7-11PM. This includes gaming websites, applications,
and consoles.
This example assumes that a general policy allowing connections from the internal network to the Internet has
already been configured.
Security
227
1. Enabling application control, web filtering, and device identification

Go toSystem > Config > Features and
enable both Application Control and
Web Filter. Apply your changes.
Go toSystem > Network > Interfaces

and edit yourlan interface.
EnableDetect and Identify Devices.
2. Configuring application control and web filtering

Go toSecurity Profiles > Application
Control and edit thedefault policy.
UnderCategories, select Game, and
set the category toBlock.
UnderOptions, enableDeep
Inspection of Cloud Applications.
Security
228
Go toSecurity Profiles > Web Filter

and edit thedefault profile.
EnableFortiGuard Categories. Expand
theGeneral Interest - Personal
category and select the subcategoryGames. Set this sub-category
toBlock.
229
Security
3.Editing your general policy to block gaming

the Internet.
SetSource Device Typeto all devices
types that will be allowed on your
network.
If you need to check the types of devices
that are connecting to your network, go
toUser & Device > Device > Device
Definitions. Do not includeGaming
Consoles.
Under Security Profiles, enable
bothApplication Control and Web
Filterand set both to use to default
profiles. SetSSL/SSH Inspectionto
deep-inspection.

3. Creating a schedule for when gaming is allowed

Schedulesand create a new recurring
schedule.
Select all Days and setStart Time to
Hour 19 (7PM) and Stop Time to Hour 23
(11PM).
Security
230
4. Creating a policy that allows gaming between 7-11PM

and create a new policy that will allow
devices on the LAN to have Internet
access.
SetSchedule to use the new schedule.
Go toSystem > Dashboard >

Statusand enter the following in the CLI
console, substituting the ID for the new
policy.
This will make surethat if someone is
gaming during the allowed time,their
session will beblocked after 11PM.
configfirewall policy
edit <policy_id>
end
end
6. Ordering the policies

Go toPolicy & Objects > Policy >
IPv4and order the policies so that the
general policy is located below the policy
that allows gaming between 7-11PM.
231
Security
7. Results
During the time that gaming is blocked,
attempt to browse to a gaming website,
such as Yahoo Games. The site is
blocked.
Attempt to run an online gaming
application, such Steam. The application
will be unable to connect to the Internet.
To view information about this blocked

traffic, go to System > FortiView >
Applications.
Attempt to connect to the Internet using a gaming console. The console will be unable to connect to the Internet.
Between 7-11PM, you are able to access the website, and all gaming applications and consoles can connect to
the Internet.
For further reading, check out the Security

Profiles in the FortiOS 5.2 Handbook.
Security
232
In this example, you will block files that contain sensitive information from leaving your network. To do this, a Data
Leak Prevention (DLP) profile will be used that blocks files that have a DLP watermark applied to them, as well as
any .exe files.
Security
233
1. Enabling DLP and multiple security profiles

ensure that DLP is turned ON.
Select Show More and ensure that

Multiple Security Profiles is also turned
ON. If necessary, Apply your changes.
2. Applying a DLP watermark to a file

The DLP watermarking client is available as part of FortiExplorer. This feature is currently only available using
FortiExplorer for Microsoft Windows.
If you do not already have FortiExplorer on your computer, clickhereto download it.
Open FortiExplorer. Under Tools, select
DLP Watermark.Select Apply
Watermark to Select File. Select the
file and set the Sensitivity Level,
Identifier, and Output Directory. Select
Apply Watermark.
The dialogue box will show the file being

processed. Ensure that the process was
successful.
Security
234
3. Creating a DLP profile

Go to Security Profiles > Data Leak
Prevention and create a new profile.
In the Filter list, select Create New.

Set the filter to look for Files. Select
Watermark Sensitivity and set it to
match the watermark applied to the file.
Do the same for Corporate Identifier.
Set Examine the Following Services to
all the services required by your network.
Set Action to Block.
Create a second filter.

Set the filter to look for Files. Select
Specify File Types and set File Types
to Executable (exe).
Set Examine the Following Services to
all the services required by your network.
Set Action to Block.
235
Security
Both filters now appear in the Filters list.
4. Adding the profile to a security policy

and edit your Internet-access policy.
Under Security Profiles, enable DLP
Sensor and set it to use the new profile.
SSL Inspectionis automatically
enabled. Set it to use the deepinspection profile to ensure that DLP is
applied to encrypted traffic.

Under Logging Options, enable Log
Allowed Traffic and select Security
Events.
5. Results
Attempt to send either the watermarked file or an .exe file using a protocol that the DLP filer is
examining.Depending on which protocol is used, the attempt will either be blocked by the FortiGate or it will
timeout.
Security
236

Sessionsand select the 5 minutes view
for information about the blocked
session.
For further reading, check out Data leak

prevention in the FortiOS 5.2 Handbook.
237
Security
In this example, you will use DLP to prevent credit card numbers from being sent out of your network using HTTP,
FTP, or SMTP.
Security
238
1. Enabling DLP
make sure that DLP is turned ON.
2. Adding two filters to the defaultDLPsensor

Go toSecurity Profiles > Data Leak
Prevention and edit the default
sensor.SelectCreate New to add a new
filter.
The first filter blocks web pages and
email Messages containing credit card
numbers.
The second filter blocks Files containing

credit card numbers. This includes email
attachments and files uploaded with a
web browser or using FTP.
Security
239
Both filters appear in the default sensor.
3.Adding the new DLP sensor to a security policy

connections from the internal network (in
this case connected to the lan interface)
to the Internet.
Under Security Profiles, turn on DLP
Sensorand use the default sensor.
SetSSL/SSH Inspection todeepinspection.

4. Results
Locatesome examplecredit card numbers to use for testing purposes. These can be found from a variety of
locations, including PayPal.
Testing HTTP:Go to a website with a comment section and attempt to post an example credit card number.
The comment is blocked.
Testing FTP: Transferafilecontaining an example credit card number using FTP. This transfer is blocked.
Testing SNMP: Send an email containing an example credit card number using a SNMP email client. This email
is blocked.
240
Security
To view more information about the

blocked traffic, go toLog & Report>
Traffic Log > Forward Trafficand filter
for Security Actions: Blocked.
For further reading, check out Data leak

prevention in the FortiOS 5.2 Handbook.
Security
241
In this example, you will protect a web server using an Intrusion Prevention System (IPS) profile and a Denial of
Service (DoS) policy. This will prevent a variety of different attacks from reaching the server.
Security
242
1. Enabling Intrusion Protection

ensure that Intrusion Protection is
turned ON. Apply your changes if
necessary.
2. Configuring the default IPS profile to block common attacks

Go to Security Profiles > Intrusion
Protection and edit the default profile.
In the Pattern Based Signatures and
Filters list, highlight the default entry and
select Edit.
Select Severity to view all signatures in
the database.
Scroll down and set the Action to Block

All.
Security
243
Enable all the listed Rate Based

Signatures.
3. Adding the IPS sensor to the server access security policy

and edit the security policy allowing
traffic to the web server from the Internet.
Enable IPS under Security Profiles and
set it to use the default profile.
Enabling IPS will automatically enable
SSL Inspection. In order to inspect
encrypted traffic, the deep-inspection
244
Security
4. Creating a DoS policy

Go to Policy & Objects > Policy > DoS
Set Incoming Interface to your Internetfacing interface.
In the Anomalies list, enable Status and
Logging and set the Action to Block for
all types.
5. Results
Warning: DoS attacks are illegal, unless you own the server under attack. Before performing an attack, ensure
that you have the correct server IP.
Launch a DoS attack on your web servers IP address.
Security
245
Go to System > FortiView > Threats

and select the 5 Minutes view.
You will see that a DoS attack has been
detected and blocked.
For further reading, check out Intrustion

Protection in the FortiOS 5.2 Handbook.
246
Security
In this recipe, you will add a custom Intrusion Protection (IPS) signature to a security policy to record all domain
lookups accepted by the policy. The signature records an IPS log message containing the domain name every
time a DNS lookup occurs.
Security
247
1. Enabling Intrusion Protection and multiple security profiles

enable Intrusion Protection.
security profiles.
Apply the changes.
2. Creating a custom IPS signature

Go to Security Profiles > Intrustion
Protection and select View IPS
Signatures.
Create a new signature with this syntax.
(You can copy and paste this text into the
F-SBID(--name DOM-ALL; --protocol udp; --service
Signature field.)
dns; --log DNS_QUERY;)
3. Adding the signature to an IPS profile

Go to Security Profiles > Intrusion
Protection and create a new profile.
Security
248
Under Pattern Based Signatures and

Filters, select Create New.
Set Sensor Type to Specify Signatures.
The new signature should appear at the
top of the list. If it does not, search for the
signature's name (in the example, logDNS_QUERY).
Select the signature, then select OK.
4. Adding the profile to the DNS server's security policy

and edit the policy allowing traffic to
reach the DNS server.
Under Security Profiles, enable IPS and
select the new profile.
Under Logging Options, enable Log

Allowed Traffic and select Security
Events.
249
Security
5. Results
Go to Log & Report > Security Log >
Intrustion Protection.
This log only appears when an IPS event
has occurred.
You will see that the IPS profile has
detected matching traffic.
If you select an entry, you can view
more information.
The domain name is shown in the
Message field.
If you have a FortiAnalyzer, you can

create a custom dataset for the DNS
query by going to Reports > Advanced
> Dataset.
Security
250
This dataset can then be used in a

custom report.
For further reading, check out DNS Service

in the FortiOS 5.2 Handbook.
251
Security
Most of us are familiar with the benefits of Hypertext Transfer Protocol Secure (HTTPS) and how it protects most
commerce activities on the Internet. HTTPS applies Secure Sockets Layer (SSL) encryption to secure web traffic
from prying eyes. The benefits are obvious; the risks, however are not as obvious, though they do exist.
One major risk is that encrypted traffic could be used in attacks that get around your normal defences. For
example, you could download a file containing a virus during an e-commerce session. Because the session is
encrypted your normal defences would miss it.
In another example, you could receive a phishing email that contains a seemingly harmless downloader file. When
launched, the downloader could create an encrypted HTTPS session to a command and control (C&C) server that
downloads malware onto your computer. Because the session containing the malware is encrypted, your antivirus
protection cant see and block the threat.
To protect your network from these threats, SSL inspection is the key that your FortiGate can use to unlock
encrypted sessions, see into encrypted packets, find threats, and block them. SSL inspection not only protects
you from attacks that use HTTPS, but also from other commonly used SSL-encrypted protocols, such as
SMTPS, POP3S, IMAPS, and FTPS.
Security
252
Full SSL inspection

To make sure thatall SSL encrypted content is inspected, you must use full SSL inspection, which is also known
as deep inspection. When full SSL inspection is used, the FortiGate impersonates the recipient of the originating
SSL session, decrypts and inspects the content. The FortiGate then re-encrypts the content, creates a new SSL
session between the FortiGate and the recipient by impersonating the sender and sends the content to the sender.
When the FortiGate re-encrypts the content it uses a certificate stored on the FortiGate. The client must trust this
certificate to avoid certificate errors.Whether or not this trust exists depends on the client, which can be the
computers OS, a browser or some other application, which will likely maintain its own certificate repository. For
more information about this, see the recipe Preventing certificate warnings.
There are two deployment methods for full SSL inspection:
Multiple Clients Connecting to Multiple Servers:
l
Uses a CA certificate (which can be upload by going to System > Certificates > CA Certificates).
Typically applied to outbound policies where destination are unknown (i.e. normal web traffic).
Address and web category whitelists can be configured to bypass SSL inspection.
Protecting SSL Server

l
l
l
Uses a server certificate (which can be upload by going to System > Certificates > CA Certificates) to protect a single server.
Typically used on inbound policies to protect servers available externally through Virtual IPs
Since this is typically deployed outside-in (clients on the Internet accessing server(s) on the internal side
of the FortiGate), server certificates using the public FQDN of the serverare often purchased from a commercial Certificate Authority and uploaded to the FortiGate. This avoids client applications generating SSL
certificate errors due to certificate mismatch.
More detail is available in the FortiOS 5.2 Handbook. Also, check the Fortinet Knowledge Base for these technical
notes:
l
How to Enable SSL inspection from the CLI and Apply it to a Policy
How to block web-based chat on Gmail webmail using App Sensor + SSL inspection
SSL certificate inspection

FortiGates also support a second type of SSL inspection, called SSL certificate inspection. When certificate
inspection is used, the FortiGate only inspects the header information of the packets.
Certificate inspection is used to verify the identity of web servers and can be used to make sure that HTTPS
protocol isn't used as a workaround to access sites you have blocked using web filtering.
253
Security
The only security feature that can be applied using SSL certificate inspection mode is web filtering. However,
since only the packet is inspected, this method does not introduce certificate errors and can be a useful alternative
to full SSL inspection when web filtering is used.
Troubleshooting
The most common problem with SSL inspection is users receiving SSL errors when the CA certificate is not
trusted. This is because by default the FortiGate uses a certificate that is not trusted by the client. There are two
ways to fix this:
l
l
All users must import the FortiGates default certificate into their client applications as a trusted certificate.
Configure the FortiGate to use a certificate that is already trusted by your clients. For example, a certification signed by a CA that your clients already trust.
The first method can be more labor intensive because you have to distribute a certification to all clients. This can
also be an ongoing problem as new clients are added to your network. The second method is usually less work but
may require paying for a CA. Both of these methods are covered in the recipe Preventing Certificate Warnings.
If you choose to install the cert on clients, this can be easier in a Microsoft Active Directory domain by using
Group Policy Objects to install the certificate on domain members. Check that the Group Policy has propagated to
all computers by opening Internet Explorer on a workstation PC, opening Tools > Internet Options > Content >
Certificates >Trusted Root Certification Authorities, and ensuring that the FortiGate's certificate is present.
For corporate-owned mobile devices, MDM solutions like AirWatch, MobileIron, or Fiberlink, use Simple
Certificate Enrollment Protocol (SCEP) to ease certificate enrollment.
Best practices
Because all traffic needs to be decrypted, inspected, and re-encrypted, using SSL inspection can reduce overall
performance of your FortiGate. To make sure you aren't using too many resources for SSL inspection, do the
following:
l
l
l
Know your traffic Know how much traffic is expected and what percent of the traffic is encrypted. You
can also limit the number of policies that allow encrypted traffic.
Be selective Use white lists or trim your policy to apply SSL inspection only where it is needed.
Use hardware acceleration - FortiGate models with either the CP6 or CPU processor have an SSL/TLS
protocol processor for SSL content scanning and SSL acceleration. For more information about this, see
the Hardware Acceleration handbook.
Test real-world SSL inspection performance yourself - Use the flexibility of FortiGates security policy
to gradually deploy SSL inspection, rather than enabling it all at once.
Security
254
This example illustrates how to prevent your users from getting a security certificate warning when you have
enabled full SSL inspection (also called deep inspection).
Instead of having users select Continue when they receive a warning, a bad habit to encourage, you can use the
examples below to prevent certificate warnings from appearing: Using the default FortiGate certificate or Using a
self-signed certificate .
For more information about SSL inspection, seeWhy you should use SSL inspection.
Security
255
Using the default FortiGate certificate

All FortiGates have a default certificate that is used for SSL deep inspection. This certificate is also used in the
default deep-inspection profile.
To prevent your users from seeing certificate warnings you can distribute this certificate to your user's devices.
A video of this example can be found here.
1. Viewing the deep-inspection SSL profile

Go to Policy & Objects > SSL/SSH
Inspection. In the upper-right hand drop
down menu, select deep-inspection.
The deep-inspection profile will apply

SSL inspection to the content of all
encrypted traffic.
Security
256
In this policy, the web categories Health

and Wellness, Personal Privacy, and
Finance and Banking are excluded
from SSL inspection by default.
Applications that require unique
certificates, such as iTunes and
Dropbox, have also been excluded.
2. Enabling certificate configuration in the web-based manager

Click Show More, enable Certificates,
and Apply the changes.
257
Security
3. Downloading the Fortinet_CA_SSLProxy certificate

Go to System > Certificates > Local
Certificates to download the Fortinet_
CA_SSLProxy certificate.
Make the CA certificate file available to
your users by checkmarking the box next
to the certificate name.
4. Importing the CA certificate into the web browser

For Internet Explorer:
Go to Tools > Internet Options. On the
Content tab, select Certificates and find
the Trusted Root Certification
Authorities.
Import the certificate using the Import
Wizard. Make sure that the certificate is
imported into Trusted Root
Certification Authorities.
You will see a warning because the
FortiGate units certificate is self-signed.
It is safe to select Yes to install the
certificate.
For Firefox:
Depending on the platform, go to Menu >
Options or Preferences > Advanced
and find the Certificates tab.
Security
258
Click View Certificates, specifically the

Authorities certificate list.
Click Import and select the Fortinet_

CA_SSLProxy certificate file.
259
Security
For Google Chrome and Safari:

Locate and open the downloaded
Fortinet_CA_SSLProxy certificate file.
Choose Open and click Install
Certificate. The Import Wizard appears.

Wizard. Make sure that the certificate is
imported into Trusted Root
Certification Authorities.
You will see a warning because the
FortiGate units certificate is self-signed.
It is safe to select Yes to install the
certificate.
Security
260
5. Results
Before installing the FortiGate SSL CA
certificate, even if you bypass the error
message by selecting Continue to this
website, the browser may still show an
error in the toolbar.
After you install the FortiGate SSL CA
certificate, you should not experience a
certificate security issue when you
browse to sites on which the FortiGate
unit performs SSL content inspection.
iTunes will now be able to run without a
certificate error.
For further reading, check out SSL/SSH

Inspection in the FortiOS 5.2 Handbook.
261
Security
Using a self-signed certificate

In this method, a self-signed certificate is created using OpenSSL. This certificate will then be installed on the
FortiGate for use with SSL inspection.
In this recipe, OpenSSL for Windows version 0.9.8h-1 is used.
A video of this example can be found here.
1. Creating a certificate with OpenSSL

If necessary, download and install Open SSL. Make sure that the file openssl.cnf is located in the BIN folder for
OpenSSL.
Using Command Prompt (CMD), navigate to the BIN folder (in the example, the command is cd
c:\OpenSSL\openssl-0.9.8h-1-1bin\bin.
Generate an RSA key with the following
command:
OpenSSL genrsa -aes256 -out fgcaprivkey.pem 2048 -config openssl

cnf
This RSA key uses AES 256 encryption

and a 2058-bit key.
When prompted, enter a pass phrase for
encrypting the private key.
Use the following command to launch
OpenSSL, submit a new certificate
request, and sign the request:
openssl req - new -x509 -days 3650 -extensions v3_ca -key

fgcaprivkey.pem -out fgcacert.pem - config openssl.cnf
The result is a standard x509 binary

certificate that is valid for 3,650 days
(approx. 10 years)
When prompted, re-enter the pass
phrase for encryption, then enter the
details required for the certificate
request, such as location and
organization name.
Two new files have been created: a public certificate (fgcacert.pem) and a private key (in the example,
fgcaprivkey.pem).
Security
262
2. Enabling certificate configuration in the web-based manager

Go to System > Config > Features. Click Show
More, enable Certificates, and Apply the
changes.
3. Importing the self-signed certificate

Once the CSR is signed by an enterprise
root CA, you can import it into the
FortiGate Unit.
Go to System > Certificates and select
Import.
From the Type drop down menu select
Certificate. Select Choose File to set
your Certificate file to your public
certificate and Key file to your private
key. Enter the Password used when
generating the certificate. If desired, you
may also set a new Certificate Name.
The certificate now appears on the Local
Certificates list.
4. Edit the SSL inspection profile

To use your certificate in an SSL
inspection profile go to Policy & Objects
> Policy > SSL/SSH Inspection. Edit
263
Security
the deep-inspection profile.

In the CA Certificate drop down menu,
select the certificate you imported.
5. Editing your Internet policy to use full SSL inspection

and edit the policy controlling Internet
traffic. Under Security Profiles, set SSL
Inspection to deep-inspection.
For testing purposes, make sure Web
Filter is set to default.
6. Importing the CA certificate into the web browser

Internet Explorer:
Go to Tools > Internet Options. On the
Content tab, select Certificates.
Go to Personal and import the
certificate.
For Firefox:
Depending on the version, go to Menu >
Select View Certificates, then select the
Servers list. Import the certificate file.
Security
264
Chrome and Safari:

If you are using Chrome or Safari, you must install the certificate for the OS, rather than directly in the browser.
If you are using Windows, open the
certificate file and select Install
Wizard. Import the certificate into the
Trusted Root Certification Authorities
store.
If you are using Mac OS X, open the

certificate file. Keychain Access opens.
Double-click the certificate. Expand
Trust and select Always Trust.
265
Security
7. Results
Before installing the self-certificate and
using it for SSL inspection, even if you
bypass the error message by selecting
Continue to this website, the browser
may still show an error in the toolbar.
After you install the self-signed
certificate, you should not experience a
certificate security issue when you
browse to sites on which the FortiGate
unit performs SSL content inspection.
If you view the website's certificate
information, the Issued By section
should contain the information of your
custom certificate, indicating that the
traffic is subject to deep inspection.
Security
266

267
Security
In this recipe, you will exempt Google Canada websites from deep SSL inspection. Exempting these websites
allows the Chrome browser to access them without errors.
You should use caution when exempting websites. In general, it is recommended that you only exempt website
that you know you can trust. Another reason for doing this is to exempt websites that do not function properly
when subjected to SSL inspection, such as a site (or application) that uses certificate/public key pinning.
In this example, google.ca is exempted from SSL inspection. If necessary, substitute your local Google search
domain.
268
1. Using the deep-inspection profile

SSL/SSH Inspection and view the
deep-inspection profile.
By default, this profile includes a number
of web categories and addresses that are
listed under Exempt from SSL
Inspection. Currently, google.ca is not
included.

and make sure the policy allowing
the Internet uses the deep-inspection
profile for SSL Inspection. For SSL
inspection to be applied to traffic, make
sure both Web Filter and Application
Control are turned on in the policy.
269
Using Google Chrome, browse to

google.ca. An error appears that you
cannot bypass.
This occurs because Chrome uses
certificate pinning (also called SSL
pinning or public key pinning). This
allows Chrome to determine that,
because full SSL inspection is being
used, the certificate from the website
does not match one belonging to Google
(instead it is the certificate that the SSL
inspection profile is using for SSL
inspection). Because of this, Chrome
believes that a "man in the middle" attack
is occurring and blocks you from the
compromised website. For more
information about why this occurs,
seeWhy you should use SSL inspection.
2. Creating a fully qualified domain name (FQDN) address for google.ca

Addresses and create a new address.
Set Type to FQDN and set FQDN to the
URL used by Google in your region (in
the example,
*.google.ca).
270
3. Exempting google.ca from full SSL inspection

SSL/SSH Inspection and edit the deepinspection profile.
Add the FQDN for Google to the list of
exempt Addresses.
271
4. Results
Using Chrome, browse to google.ca. The
site loads properly.

272
Blocking Facebook
In this example, you will learn how to configure a FortiGate to prevent access to a specific social networking
website, including its subdomains, by means of a static URL filter.
When you allow access to a particular type of content, such as the FortiGuard SocialNetworking category, there
may still be certain websites in that category that you wish toprohibit. And by using SSL inspection, you ensure
that this website is also blocked whenaccessed through HTTPS protocol.
273
1. Verifying FortiGuard Services subscription

Go to System > Dashboard > Status.In
the License Information widget, verify
that you have an active subscription to
FortiGuard Web Filtering. If you have a
subscription, the service will have a
green checkmark beside it.
2. Editing the Web Filter profile

Go to Security Profiles > Web Filter
and edit the default Web Filter profile.
Set Inspection Mode to Proxy.
Enable the FortiGuard Categories that

allow, block, monitor, warn or
authenticate depending on the type of
content.
Learn more about FortiGuard Categories

at the FortiGuard Center web filtering
rating page:
www.fortiguard.com/static/webfiltering.html
274
Under FortiGuard Categories, go to

General Interest - Personal. Rightclick on the Social Networking
subcategory and ensure it is set to
Allow.
To prohibit visiting one particular social

networking site in that category, go to
Static URL filter, select Enable URL
Filter, and then click Create New.
For your new web filter, enter the URL of

the website you are attempting to block.
If you want to block all of the subdomains
for that website, omit the protocol in the
URL and enter an asterisk (*). For this
example, enter:*facebook.com
Set Type to Wildcard, set Action to
block, and set Status to Enable.
3. Creating a security policy

Go to Policy & Objects > Policy > IPv4,
and click Create New.
275
Set the Incoming Interface to allow

packets from your internal network and
set the Outgoing Interface to proceed
to the Internet-facing interface (typically
wan1).
Enable NAT.

Filter and select the default web filter.
This automatically enables SSL/SSH

Inspection. Select certificateinspection from the dropdown menu.
Thisprofile allows the FortiGate to
inspect and apply web filtering to HTTPS
traffic.
After you have created your new policy,
ensure that it is at the top of the policy
list. To move your policy up or down,
click and drag the far left column of the
policy.
276
4. Results
Visit the following sites to verify that your
web filter is blocking websites ending in
facebook.com:
l
facebook.com
attachments.facebook.com
camdencc.facebook.com
mariancollege.facebook.com
A FortiGuard Web Page Blocked! page

should appear.
Visit https://www.facebook.com to verify

that HTTPS protocol is blocked.
A Web Page Blocked! page should
appear.
For further reading, check out Static URL

Filter in the FortiOS 5.2 Handbook.
277
In this recipe, you will use FortiGate web filtering to ensure that SafeSearch is applied to all Google search results.
You will also block access to websites in the adult/mature content FortiGuard category for all network users.
This recipe requires an active FortiGuard web filtering licence.
1. Enabling web filtering

make sure that Web Filter is ON. If
2. Blocking the Adult/Mature Content category and enabling Safe Search

and edit the default profile. Enable
FortiGuard Categories.
278
Select the Adult/Mature Content

category and set it to Block.
Under Search Engines, select Enable
Safe Search and Search Engine Safe
Search - Google, Yahoo!, Bing,
Yandex.
279
3. Adding web filtering to your Internet access policy

the Internet.
Filter and set it to use the default profile.
4. Enforcing Google SafeSearch for all traffic

Because Google search often uses the HTTPS protocol, web filtering alone may not be able to block all
adult/mature content. There are two methods that can be used to enforce Google SafeSearch for all traffic: using
full SSL inspection so that encrypted traffic is fully inspected (which can cause certificate errors), or changing
the DNS records to force search traffic to use forcesafesearch.google.com.
Method 1: Using full SSL inspection

the Internet.
Set SSL/SSH Inspection to use the
deep-inspection profile. Using the
deep-inspection profile may cause
certificate errors. For information about
280
avoiding this, see Preventing certificate

warnings.
Method 2: Changing the DNS records for www.google.com

If you wish to force Google SafeSearch for your entire network, you can set the DNS entry for www.google.com
(and another other Google search domains, such as www.google.[glossary_exclude]ca[/glossary_exclude]) to
be a Canonical Name (CNAME) for forcesafesearch.google.com. This will force all search traffic to use
forcesafesearch.google.com.
The method for changing the DNS records using your FortiGate varies, depending on whether your FortiGate is
the network's DNS server, or if an external server is used.
FortiGate is the network's DNS server

select Show More. Make sure that DNS
Database is ON. If necessary, Apply
your changes.

CLI Console using your internal
interface:
Go to System > Network > DNS

Servers. The new server is listed under
DNS Service on Interface.
Under DNS Database, select Create

New.
Set DNS Zone as Google, Domain
Name to google.com, and disable
Authoritative.
281
config system dns-server

edit internal
set mode recursive
end
Under DNS Entries, select Create

New.
Set Type to Address (A), set
Hostname to www, and IP Address to
216.239.38.120 (the IP address of
forcesafesearch.google.com).
If required, create additional DNS

Database entries for other Google search
domains (entry for www.google.
[glossary_exclude]ca[/glossary_
exclude] shown).
A list of Google search domains can be
found here.
The network uses an external DNS server

Using this method will cause your FortiGate to intercept all DNS queries. Because all DNS traffic will be
forwarded to the FortiGate internal DNS Service, there might be a performance impact on the FortiGate.
select Show More. Make sure that DNS
Database is ON. If necessary, Apply
your changes.
282

and create an interface to be used for the
FortiGate DNS service.
Set Type to Loopback Interface and
assign an IP/Network Mask (in the
example, 10.10.10.10/255.255.255.255).

CLI Console:
Go to System > Network > DNS
Servers. The new server is listed under
DNS Service on Interface.
Under DNS Database, select Create

New.
Set DNS Zone as Google, Domain
Name to google.com, and disable
Authoritative.
Under DNS Entries, select Create

New.
Set Type to Address (A), set
Hostname to www, and IP Address to
216.239.38.120 (the IP address of
forcesafesearch.google.com).
283
config system dns-server

edit dns-loopback
set mode recursive
end
If required, create additional DNS

Database entries for other Google search
domains (entry for www.google.ca
shown).
A list of Google search domains can be
found here.

CLI Console to create a new virtual IP:
Set src-filter to the IP range of your
internal users (in the example,
10.10.80.2-10.10.80.100), extintf to your
internal interface, and mappedip to the
IP address of the loopback interface.
config firewall vip

edit "dns-vip"
set type load-balance
set src-filter "10.10.80.2-10.10.80.100"
set extip 0.0.0.0-239.255.255.255
set extintf internal
set portforward enable
set mappedip "10.10.10.10"
set protocol udp
set extport 53
set mappedport 53
set arp-reply disable
end
284

and create a policy to use the virtual IP to
intercept DNS queries.
Set the Incoming Interface to your
internal interface, the Outgoing
Interface to the loopback interface,
Destination Address to the virtual IP,
and Service to DNS. Make sure NAT is
disabled.
Select the Global View of the policy list.

Make sure that the new policy is located
above the policy that allows connections
from the internal network to the Internet.
Results
If you are using full SSL inspection, go to
google.com and attempt to search for
adult/mature content. When the results
are shown, a message appears stating
that SafeSearch is turned on. This
cannot be undone.
If you are using Google Chrome for
Internet browsing, you may need to
disable SPDY protocol in order for
SafeSearch to turn on automatically.
If you have altered the DNS settings, go
to google.com. A message at the top of
the page states that your network has
turned on SafeSearch.
285
For further reading, check out SafeSearch

and DNS Services in the FortiOS 5.2
Handbook.
286
In this recipe, you will change a website's FortiGuard web rating.
An active license for FortiGuard Web Filtering Services is required to use web ratings.
For testing purposes, the Cookbook website (cookbook.fortinet.com) will be changed from the category
Information Technology to a custom category named Allowed Sites.
By changing the web rating for a website, you can control access to the site without affecting the rest of the sites
in its original category.
This recipe only changes the website's rating on your FortiGate. To request that the rating is changed for all of
FortiGuard, go here.
287

2. Creating a custom category and web rating override

Go to Security Profiles > Advanced >
Web Rating Overrides and select
Custom Categories.
Create a new category named Allowed
Sites.
Go to Security Profiles > Advanced >
Web Rating Overrides and create a
new override.
Enter the website's URL and select
Lookup Rating to see the current rating.
In the Override to section, set
Category to Custom Categories and
Sub-category to Allowed Sites.
288
3. Adding FortiGuard blocking to the default web filter profile

and edit the default profile. Enable
FortiGuard Categories.
Expand Local Categories to make sure

that the Allowed Sites category is set to
Allow.
289
Expand General Interest - Business.

Right-click on Information Technology
to set it to Block.
4. Adding the default web filter profile to a security policy

the Internet.
Under Security Profiles, turn on Web
Filter and use the default profile.
290
5. Results
Browse to www.fortinet.com, which is
part of the Information Technology
category. A message will appear from
FortiGuard, stating that access to this
website is blocked.
If you browse to cookbook.fortinet.com, you will still be able to access the site.
For further reading, check out FortiGuard

Web Filtering Service in the FortiOS 5.2
Handbook.
291
In this example, you will create a web filter profile that allows access to websites that are categorized as
"Personal Interest" at any point during the day, but limits access for a total of 5 minutes for each user.
An active license for FortiGuard Web Filtering Services is required to use web filtering with quotas.
Quotas are the most efficient way of allowing limited access to websites, as they do not require set schedules. To
apply web filtering using quotas, you must use a security policy with either user or device authentication. In this
recipe, a user account, alistair, has already been configured. For more information about creating user accounts,
see User and device authentication.
292

2. Creating a web filter profile that uses quotas

Go to Security Profiles > Web Filter >
Profiles. Edit the default profile and
enable FortiGuard Categories.
Right-click on the category General
Interest - Personal and select Monitor.
Do the same for the category General
Interest - Business.
These categories include a variety of
sites that are commonly blocked in the
workplace, such as games, instant
messaging, and social media.
293
Expand Quota on Categories with

Monitor, Warning and Authenticate
Actions and select Create New.
Select both General Interest Personal and General Interest Business. For testing purposes, set the
Quota amount to 5 Minutes.
The web filter will now list all the subcategories listed in the two categories
and the applied quota.
294
3. Adding web filtering to a security policy with user authentication

the Internet.
Filter and use the default profile.
4. Results
Browse to www.ebay.com, a website
that is found within the General Interest Personal category.
Access to the website is allowed for 5
minutes, after which a block message
appears. The message will persist for all
General Interest - Personal sites until the
quota is reset, which occurs every 24
hours at midnight.
295
Go to System > FortiView > Threats

and select the 5 minutes view. You will
be able to see the blocked traffic.
For further reading, check out FortiGuard

Web Filtering Service in the FortiOS 5.2
Handbook.
296
In this recipe, you will block access to Google services for consumer accounts, while allowing access for
corporate accounts.
If your organization has set up a Google corporate account to be able to use Google services, such as Gmail and
Google Docs, this recipe can be used to block users from accessing those services with their own personal
accounts. In this example, a corporate account has been created that uses the domain fortidocs.com.
297
1. Editing the default web filter profile to restrict Google access

and edit the default profile.
Make sure that Inspection Mode is set
to Proxy. Under Proxy Options, select
Restrict Google Account Usage to
Specific Domains.
Select Create New in the list that
appears and add an entry for the domains
for your Corporate Google accounts (in
the example, fortidocs.com).
2. Adding the profile to your Internet-access policy

the Internet.
Enable Web Filter and set it to use the
default profile. Doing this will
automatically enable SSL/SSH
Inspection. Set this to use the deepinspection profile.
298
3. Results
Log in to Google using a personal
account. After you are authenticated,
attempt to access a Google service,
such as Gmail or Google Drive.
A message appears from Google stating
that the service is not available.
Sign out of the personal account and
instead use your corporate account (in
the example, test@fortidocs.com).
You can now access the Google service.
For further reading, check out Web filter in

299
In this example, one user is temporarily allowed to override a web filter profile to be able to access sites that would
otherwise be blocked.
In this example, web filtering blocks the Bandwidth Consuming category for all users, except those who can
override the filter.
300
1. Enabling web filtering and multiple profiles

make sure thatWeb Filteris turned ON.
Select Show More and enableMultiple

Security Profiles.
Apply the changes.
2. Creating a user group and two users

Groups. Create a new group for users
who can override web filtering (in the
example, web-filter-override).
Definition andcreate two users (in the
example, ckent and bwayne).
301
Assign ckent to theweb-filteroverridegroup, but notbwayne.
3. Creating a web filter profile and override

and createa new profile (in the example,
block-bandwidth-consuming).
Enable FortiGuard Categories, thenrightclick Bandwidth Consuming and select
Block.
302
Go toSecurity Profiles > Advanced >

Web Profile Overridesand create a
new override.
SetScope Range toUser Group,User
Group to theweb-filteroverridegroup,Original Profileto
theblock-bandwidth-consumingprofile,
andNew Profile to thedefault profile.
Set an appropriate Expires time to
control how long the override can be used
(in the example, 100 hoursafter the
override is created).
4.Adding the newweb filter profile to a security policy

the Internet.
SetSource User(s) to allow both
theweb-filter-overridegroup and
userbwayne.
Filter and use thenewprofile.
303
5. Results
Browse to blip.tv, a website that is part of
theBandwidth Consumingcategory.
Authenticate using the bwayne account.
The website is blocked.
Go toUser & Device > Monitor > Firewalland De-authenticate bwayne.

Browse to blip.tv again, this time authenticating using theckent account. You can access the website until the
override expires.
For further reading, check out Web Filter in

304

This section contains tips to help you with some common challenges of FortiGate web filtering.
The Web Filter option does not appear in the GUI.

Go to Config > System > Features and enable Web Filter.
New Web Filter profiles cannot be created.

Go to Config > System > Features and select Show More. Enable Multiple Security Profiles.
Web Filtering has been configured but is not working.

Make sure that web filtering is enabled in a policy. If it is enabled, check that the policy is the policy being used for
the correct traffic. Also check that the policy is getting traffic by going to the policy list and adding the Sessions
column to the list.
An active FortiGuard Web Filtering license displays as expired/unreachable.

First, ensure that web filtering is enabled in one of your security policies. The FortiGuard service will sometimes
show as expired when it is not being used, to save CPU cycles.
If web filtering is enabled in a policy, go to System > Config > FortiGuard and expand Web Filtering. Under Port
Selection, select Use Alternate Port (8888). Select Apply to save the changes. Check whether the license is
shown as active. If it is still inactive/expired, switch back to the default port and check again.
305
VPNs
This section contains information about configuring a variety of different Virtual Private Networks (VPNs), as well
as different methods of authenticating VPN users. FortiGates support two types of VPNs: IPsec and SSL.
IPsec VPNs use Internet Protocol Security (IPsec) to create a VPN that extends a private network across a public
network, typically the Internet. In order to connect to an IPsec VPN, users must install and configure an IPsec
VPN client (such as FortiClient) on their PCs or mobile devices.
SSL VPNs use Secure Sockets Layer (SSL) to create a VPN that extends a private network across a public
network, typically the Internet. Connections to an SSL VPN are done through a web browser and do not require
any additional applications.
IPsec
l
SSL
l
VPNs
306
307
VPNs
This recipe uses the IPsec VPN Wizard to provide a group of remote users with secure, encrypted access to the
corporate network.
The tunnel provides group members with access to the internal network, but forces them through the FortiGate
unit when accessing the Internet. When the tunnel is configured, you will connect using the FortiClient application.
VPNs
308
1. Creating a user group for remote users

Definition.
Create a new Local User with the User
Creation Wizard.
Proceed through each step of the wizard,
carefully entering the appropriate
information.

Groups.
Create a user group for remote users and
add the user you created.
2. Adding a firewall address for the local network

Addresses.
Add a firewall address for the Local LAN,
including the subnet and local interface.
VPNs
309
3. Configuring the IPsec VPN using the IPsec VPN Wizard

Go to VPN > IPSec > Wizard.
Name the VPN connection and select
Dial Up - FortiClient (Windows, Mac
OS, Android) and click Next.
The tunnel name may not have any

spaces in it.

internet-facing interface.
Select Pre-shared Key for the
Authentication Method.
Enter a pre-shared key and select the
new user group, then click Next.
The pre-shared key is a credential for the

VPN and should differ from the users
password.
310
VPNs
Set Local Interface to an internal

interface (in the example, port 1) and set
Local Address to the local LAN
address.
Enter an IP range for VPN users in the
Client Address Range field.
The IP range you enter here prompts

FortiOS to create a new firewall object for
the VPN tunnel using the name of your
tunnel followed by the _range suffix (in
this case, ipsecvpn_range).
In addition, FortiOS automatically
creates a security policy to allow remote
users to access the internal network.
Click Next and select Client Options as
desired.
VPNs
311
4. Creating a security policy for access to the Internet

Create a security policy allowing remote
users to access the Internet securely
through the FortiGate unit.
Set Incoming Interface to the tunnel
interface and set Source Address to all.
Set Outgoing Interface to wan1 and
Destination Address to all.
Set Service to ALL and ensure that you
enable NAT.
5. Configuring FortiClient
Open FortiClient, go to Remote Access
and Add a new connection.
Provide a Connection Name and set the

Type to IPsec VPN.
Set Remote Gateway to the FortiGate
IP address.
Set Authentication Method to PreShared Key and enter the key below.
312
VPNs
Select the new connection, enter the

username and password, and click
Connect.
6. Results
Once the connection is established, the
FortiGate assigns the user an IP address
and FortiClient displays the status of the
connection, including the IP address,
connection duration, and
bytes sent and received.
On the FortiGate unit, go to VPN >

Monitor > IPsec Monitor and verify that
the tunnel Status is Up.
Forward Traffic to view the traffic.
Verify that the Sent/Received column
displays traffic successfully flowing
through the tunnel.
For further reading, check out IPsec VPN in

the web-based manager in the FortiOS 5.2
Handbook.
VPNs
313
This recipe uses the IPsec VPN Wizard to provide a group of remote iOS users with secure, encrypted access to
the corporate network. The tunnel provides group members with access to the internal network, but forces them
through the FortiGate unit when accessing the Internet.
This recipe was tested using an iPad 2 running iOS version 7.1.
VPNs
314
1. Creating a user group for iOS users

Definition.
Create a new user.

Groups.
Create a user group for iOS users and
VPNs
315
2. Adding a firewall address for the local network

Addresses.

Go to VPN > IPsec > Wizard.
Dial Up - iOS (Native) and click Next.
316
VPNs

Enter a pre-shared key and select the
iOS user group, then click Next.

password.

Local Address to the iOS users
address.

this case, iOSvpn_Native_range).
VPNs
317

iOS users to access the Internet
securely through the FortiGate unit.
Set Service to all and ensure that you
enable NAT.
318
VPNs
5. Configuring VPN on the iOS device

On the iPad, go to Settings > General >
VPN and select Add VPN
Configuration.
Enter the VPN address, user account,
and password in their relevant fields.
Enter the pre-shared key in the Secret
field.
6. Results
Monitor > IPsec Monitor and view the
status of the tunnel.
Users on the internal network will be
accessible using the iOS device.
VPNs
319
Select an entry to view more information.
Remote iOS users can also access the

Internet securely via the FortiGate unit.
320
VPNs
You can also view the status of the

tunnel on the iOS device itself.
On the device, go to Settings > VPN >
Status and view the status of the
connection.
VPNs
321
Lastly, using a Ping tool, you can send a

ping packet from the iOS device directly
to an IP address on the LAN behind the
FortiGate unit to verify the connection
through the VPN tunnel.
For further reading, check out FortiGate

dialup-client configurations in the FortiOS
5.2 Handbook.
322
VPNs
In this recipe, you will learn how to create an IPsec VPN on a FortiGate, and connect to it using the default client
built into the Mac OS.
This VPN configurationallows Mac users to securely access an internal network as well as browse the Internet
through the VPN tunnel.
The recipe assumes that a "mac_users"user group and a Local LAN firewall address have been created.
This recipe was tested using MacOS 10.10.2 (Yosemite).
VPNs
323

Name the VPN connectionand select
Dial Up Cisco Firewalland click Next.
The native Mac OS client is a Cisco

client, which is why you select Dialup Cisco Firewall in the VPN Wizard.

Select Pre-shared Key for
theAuthentication Method.
Enter a pre-shared key, select the
appropriate User Group, then click
Next.
VPNs
324

interfaceand set Local Address to the
local LAN address.
Enter an IP address range for VPN users
in the Client Address Rangefield then
click Next.
The IPsec VPN Wizard finishes with a

summary of created objects.

Addresses and confirm that the wizard
has createdthe IPsec VPN firewall
address range.
325
VPNs

and confirm thatthe wizard has created
the policy from the VPN tunnel interface
to the internal interface.
2.Creating a security policy for remote access to the Internet

UnderPolicy & Objects > Policy > IPv4,
create a security policy
allowing remote users to access the
Internet securely through the FortiGate
unit.
Set Outgoing Interface to the Internetfacing interface and Destination
Address to all.
Set Service to ALL and enable NAT.
The policy should appear in the policy list
at Policy & Objects > Policy > IPv4.
VPNs
326
3. Connecting to the IPsec VPN using the native Mac client

On the Mac, go to System Preferences
> Network andclick the Plus (+) button.
Set Interface to VPN, set VPN Type to

Cisco IPSec, and click Create.
327
VPNs
Set the Server Address to the FortiGate

IP address,configure the network
account details for the remote user, then
click Authentication Settings.
Select Shared Secret and enter the preshared key you created above, then click
OK.
VPNs
328
4. Results
On the Mac, ensure thatthe VPN is
selected and click Connect. The Status
should change to Connected and you
should be given an IP Address in the
range specified above.
You should also be able to browse the
Internet, protected by whichever profiles
you applied to the security policy created
in the above step.
On the FortiGate unit, go toVPN >

the tunnel Status is Up, and that
thereareIncoming and Outgoing Data.

Handbook.
329
VPNs
In this recipe, two-factor authentication is added to a user account to provide extra security when connecting to an
IPsec VPN using FortiClient for Mac OS x.
Two-factor authentication requires a user to authenticate twice before being allowed to access the IPsec VPN. In
this recipe the FortiToken Mobile app for iOS provides a one-time password (OTP) (a 6-digit number) that the you
must enter at a second authentication prompt.
This recipe assumes that you have already activated FortiToken Mobile (see Two-factor authentication with
FortiToken Mobile for details).
VPNs
330
1. Creating a user and user group

Enter the user's login credentials. This

example simply creates a local user.
For Contact Info, select SMS and be

sure to include a Phone Number without
dashes or spaces.
This example uses SMS to send an
activation code to the user so we
included the user's mobile phone number
here. Even if your FortiGate cannot send
SMS messages you need to include a
phone number for the IPsec VPN wizard
to work.
Do not add an email address.
VPNs
331
Select the FortiToken assigned to this

user.
The user list shows the FortiToken in the

Two-factor Authentication column for
the new user account.

Groups. Create a user group for remote
users and add the new user.
2. Adding a firewall address for the LAN

Addresses.
Create a firewall address for your LAN's
subnet.
332
VPNs

Dial Up FortiClient (Windows, Mac
OS, Android).

spaces.

Authentication Method. Enter a preshared key and select the new user
group.

password.
VPNs
333

Local Address to the LAN address.

Select Client Options as desired.
334
VPNs

users to access the Internet securely
Set the Source User(s) to the new user
group. Set Outgoing Interface to your
Internet-facing interface and Destination
Address to all.
Ensure that you enable NAT.
5. Sending the FortiToken activation code to the user

If your FortiGate can send SMS
messages, go to User & Device > User
> User Definition and edit the new user
account. Select Send Activation Code
and send the code by SMS.
If your FortiGate cannot send SMS

messages, go to System > Dashboard
> Status and enter the following into the
CLI Console, substituting the correct
serial number:
VPNs
config user fortitoken

edit
show
335
The activation code will be shown in the

output. This code must be given to the
user.
6. Setting up FortiToken Mobile on an iOS device

Using your iOS device, download and install FortiToken Mobile.
Open the app and add a new account.
Select Enter Manually, then select
Fortinet under FORTINET ACCT.
Enter the activation code into FortiToken
Mobile.
336
VPNs
FortiToken Mobile can now generate a

token for use with the FortiGate.
(Optional) For additional security, set a PIN for FortiToken Mobile using the apps Settings options.
VPNs
337
7. Configuring FortiClient for Mac OS X

Using your Mac OS X device, download and install FortiClient.
and select Add a new connection.

Type to IPsec VPN.
Set Remote Gateway to the FortiGate's
IP address.
Set Authentication Method to PreShared Key and enter the key for the
IPsec VPN.
338
VPNs
8. Results
Using FortiClient, select the IPsec VPN
connection, enter the password, and
click Connect.
You will be prompted to enter your code

from FortiToken mobile.
VPNs
339
After your code has been verified, a

connection to the IPsec VPN is
established.
340
VPNs
In this recipe youll use an external DHCP server to assign IP addresses to your IPsec VPN clients, this scenario
is commonly found on enterprises where all DHCP leases need to be centrally managed.
The DHCP server assigns IP addresses in the range of 172.16.6.100 to 172.16.6.120. The server is attached to
port 4 of the FortiGate and has an IP address of 192.168.3.70.
VPNs
341
1. Creating a user group for remote users

Definition.
Create a new Local User with the User
Creation Wizard.
Proceed through each step of the wizard,
carefully entering the appropriate
information.

Groups.
Create a user group for remote users and
2. Adding a firewall address for the local network and IPsec VPN client range
Addresses.
VPNs
342
Add a firewall address for the IPsec VPN

client range.
3. Configuring the IPsec VPN using a Custom VPN Tunnel

Go to VPN > IPSec > Tunnels > Create
New.
Custom VPN Tunnel (No Template)
and click Next.

spaces in it.
343
VPNs
Configure the following parameters:

Set the Remote Gateway to Dialup
User
Set the Interface to the internet-facing
interface.
Enter a Pre-shared Key.

password.
Set the Mode to Aggressive
Set the XAUTH Type to Auto Server
Set the XAUTH User Group to the User
Group created on step 1 and click OK to
apply the configuration
Use the CLI to enable DHCP-IPsec
inside the VPN Phase 2 settings.
VPNs
config vpn ipsec phase2-interface

edit "dhcp_vpn"
set dhcp-ipsec enable
next
end
344
4. Configuring the IPsec VPN Interface

Edit the newly created IPsec VPN
Interface
Set the IP to the same subnet that will be
leased to VPN clients. This is the value
that the DHCP Administrator must use
for the DHCP Option 003 (Router). Set
the Remote IP to the same value.
Enable DHCP Server, then expand
Advanced and change the mode to
Relay. Enter the external DHCP server
IP address and change the Type to
IPsec.
5. Creating a security policy for access to the Local LAN Network

Create a security policy allowing the
VPN IPsec client IP address range to
access the Local LAN network.
interface and set Source Address to the
VPN IPsec client range defined on step
2.
Set Outgoing Interface to port4 and
Destination Address to Local LAN.
Set Service to ALL
and Add a new connection.
345
VPNs

Type to IPsec VPN.
external IP address.
Set Authentication Method to PreShared Key and enter the key below.
Expand Advanced Settings and VPN

Settings.
Select DHCP over IPsec.
VPNs
346

Connect.
7. Results
Once the connection is established, the
external DHCP server assigns the user
an IP address and FortiClient displays
the status of the connection, including
the IP address, connection duration, and
bytes sent and received.

the tunnel Status is Up.
Verify that the Sent/Received column
displays traffic successfully flowing
through the tunnel.
347
VPNs

Handbook.
VPNs
348
In this example, you will allow transparent communication between two networks that are located behind different
FortiGates at different offices using route-based IPsec VPN. The VPN will be created on both FortiGates by using
the VPN Wizards Site to Site FortiGate template.
In this example, one office will be referred to as HQ and the other will be referred to as Branch.
VPNs
349
1. Configuring the HQ IPsec VPN

On the HQ FortiGate, go to VPN > IPsec
> Wizard and select Site to Site FortiGate.
In the Authentication step, set the

Branch FortiGate's IP as the Remote
Gateway (in the example,
172.20.120.142). After you enter the
gateway, an available interface will be
assigned as the Outgoing Interface. If
you wish to use a different interface,
select Change.
Set a secure Pre-shared Key
VPNs
350
In the Policy & Routing section, set

Local Interface to your lan interface.
The Local Subnet will be added
automatically. Set Remote Subnets to
the Branch FortiGate's local subnet (in
the example, 192.168.50.0/24).
A summary page shows the

configuration created by the wizard,
including firewall addresses, firewall
address groups, a static route, and
security policies.
351
VPNs
2. Configuring the Branch IPsec VPN

On the Branch FortiGate, go to VPN >
IPsec > Wizard and select Site to Site FortiGate.
In the Authentication step, set the HQ

FortiGate's IP as the Remote Gateway
(in the example, 172.20.120.123). After
you enter the gateway, an available
interface will be assigned as the
Outgoing Interface. If you wish to use a
different interface, select Change.
Set the same Pre-shared Key that was
used for HQ's VPN.
VPNs
352
In the Policy & Routing section, set

Local Interface to your lan interface.
The Local Subnet will be added
automatically. Set Remote Subnets to
the HQ FortiGate's local subnet (in the
example, 192.168.100.0/24).
A summary page shows the

configuration created by the wizard,
including firewall addresses, firewall
address groups, a static route, and
security policies.
3. Results
A user on either of the office networks should be able to connect to any address on the other office network
transparently.
If you need to generate traffic to test the connection, ping the Branch FortiGate's internal interface from the HQ's
internal network.
353
VPNs
Go to VPN > Monitor > IPsec Monitor

to verify the status of the VPN tunnel.
Ensure that its Status is Up and that
traffic is flowing.
For further reading, check out Gateway-togateway configurations in the FortiOS 5.2
Handbook.
VPNs
354
This recipe describes how to construct a site-to-site IPsec VPN connection between two networks with
overlapping subnets, such that traffic will be directed to the correct address on the correct network, using Virtual
IP addresses and static routes.
VPNs
355
1. Create the IPsec VPN tunnel on FGT_1

Select Site to Site - FortiGate. Give it
an appropriate Name and click Next.
Set Remote Gateway to the IP address

used by the Internet-facing interface of
FGT_2. The Outgoing Interface will
automatically populate.
Enter a Pre-shared key and click Next.
VPNs
356
Set Local Interface to your Internetfacing interface. The Local Subnets will
automatically populate. Set Remote
Subnets to the VIP of the internal
network for FGT_2 (10.31.101.0/24) and
click Create.
The VPN Wizard automatically creates

the required objects, policies, and static
route required for the tunnel to function
properly.
You can verify the policy creation under

Policy & Objects > Policy > IPv4.
357
VPNs
2. Add the Virtual IP Range on FGT_1

Virtual IPs and create a Virtual IP range
to redirect the traffic to the correct
subnet.
Select Virtual IP from the Create New
drop down menu. Select IPv4 for the VIP
Type and give the VIP an appropriate
name.
Set the Interface to the IPsec VPN Site to Site interface from the drop down menu.
Set External IP Address/Range to a range in the subnet you will be redirecting from (10.21.101.1 10.21.101.254) and Mapped IP Address/Range to the internal network range (192.168.1.1 - 192.168.1.254).
Select OK.
3. Create the IPsec VPN tunnel on FGT_2

Select Site to Site - FortiGate. Give it
an appropriate Name and click Next.
VPNs
358
Set Remote Gateway to the IP address

used by the Internet-facing interface of
FGT_1. The Outgoing Interface will
automatically populate.
Enter a Pre-shared key and click Next.
Set Local Interface to your Internetfacing interface. The Local Subnets will
automatically populate. Set Remote
Subnets to the VIP of the internal
network for FGT_1 (10.21.101.0/24) and
click Create.
359
VPNs
The VPN Wizard automatically creates

the required objects, policies, and static
route required for the tunnel to function
properly.
As before, you can verify the policy
creation under Policy & Objects > Policy
> IPv4.
4. Add the Virtual IP Range on FGT_2

Virtual IPs and create a Virtual IP range
to redirect the traffic to the correct
subnet.
Select Virtual IP from the Create New
drop down menu. Select IPv4 for the VIP
Type and give the VIP an appropriate
name.
Set Interface to the IPsec VPN Site to Site interface from the drop down menu.
Set External IP Address/Range to a range in the subnet you will be redirecting from (10.31.101.1 10.31.101.254) and Mapped IP Address/Range to the internal network range (192.168.1.1 - 192.168.1.254).
Select OK.
5. Results
VPNs
360
Go to VPN > Monitor > IPsec Monitor.

Right-click on the Site to Site VPN and
select Bring Up.
You will be able to see Incoming and
Outgoing Data in the IPsec Monitor.
361
VPNs
The following recipe describes how to configure a site-to-site IPsec VPN tunnel. In this example, one site is
behind a FortiGate and another site is hosted on Microsoft Azure, for which you will need a valid Microsoft Azure
profile.
Using FortiOS 5.2, the example demonstrates how to configure the tunnel between each site, avoiding
overlapping subnets, so that a secure tunnel can be established with the desired security profiles applied.
VPNs
362
1. Configuring the Microsoft Azure virtual network

Log into Microsoft Azure and click New
in the lower-left corner to add a new
service.
From the prompt, select Network

Services > Virtual Network > Custom
Create.
Under 'Virtual Network Details', enter a

Name for the VPN and a Location
where you want the VMs to reside, then
click the Next arrow.
Under 'DNS Servers and VPN
Connectivity', enable the Configure a
site-to-site VPN checkbox and enter
DNS server information if required.
Click the Next arrow.
Under 'Site-to-Site Connectivity', enter a

Name and IP Address for the FortiGate
device.
Under Address Space, include a
Starting IP and CIDR (Address Count)
for the tunnel, avoiding overlapping
subnets.
Click the Next arrow.
VPNs
363
Under 'Virtual Network Address Spaces',

configure the desired address space or
accept the default settings.
Select add gateway subnet to
configure a gateway IP and click the
Checkmark in the lower-right corner to
accept the configuration.
After accepting the configuration, you will

have to wait a short period of time for the
virtual network to be created, but it
shouldn't be long.
2. Creating the Microsoft Azure virtual network gateway

On the 'networks' home screen, click the
name of the virtual network you just
created.
Under this virtual network, go to the

Dashboard. You will notice that the
gateway has not yet been created. You
will create the gateway in this step.
At the bottom of the screen, select
Create Gateway > Dynamic Routing.
When prompted, select Yes.
364
VPNs
The operation to create the virtual

network gateway will run. The process
takes a short amount of time.
Azure will indicate to you that the

gateway is being created. You may wish
to leave this running for a few minutes as
wait periods in excess of 10 minutes are
common.
When the operation is complete, the
status changes and you are given a
Gateway IP Address.
The gateway will then attempt to connect

to the Local Network.
At the bottom of the screen, select

Manage Key.
VPNs
365
The 'Manage Shared Key' dialogue

appears. Copy the key that is shown.
You can select regenerate key if you
want to copy a different key.
Click the Checkmark when you are
confident that the key is copied.
You are now ready to configure the FortiGate endpoint of the tunnel.
3. Configuring the FortiGate tunnel

Go to VPN > IPsec > Wizard and select
Custom VPN Tunnel (No Template).
Enter a Name for the tunnel and click
Next.
366
VPNs
Enter the desired parameters. Set the

Remote Gateway to Static IP Address,
and include the gateway IP Address
provided by Microsoft Azure.
Set the Local Interface to wan1.
Under Authentication, enter the Preshared Key provided by Microsoft
Azure.
Disable NAT Transversal and Dead
Peer Detection.
Under Authentication, ensure that you

enable IKEv2 and set DH Group to 2.
Enable the encryption types shown and
set the Keylife to 56660 seconds.
VPNs
367
Scroll down to Phase 2 Selectors and

set Local Address to the local subnet
and Remote Address to the VPN tunnel
endpoint subnet (found under 'Virtual
Network Address Spaces in Microsoft
Azure).
Enable the encryption types to match
Phase 1 and set the Keylife to 7200
seconds.
368
VPNs
4. Creating the FortiGate firewall addresses

Go to Policy & Objects> Objects >
Addresses and configure a firewall
address for the local network.
Create another firewall object for the

Azure VPN tunnel subnet.
5. Creating the FortiGate firewall policies

and create a new policy for the site-tosite connection that allows outgoing
traffic
Set the Source Address and
Destination Address using the firewall
objects you just created.
VPNs
369
When you are done, create another

policy for the same connection to allow
incoming traffic.
This time, invert the Source Address
and Destination Address.
6. Results
Go to VPN > Monitor > IPsec >
Monitor. Right-click the tunnel you
created and select Bring Up to activate
the tunnel.
Go to Log & Report > Event Log >
VPN.
Select an entry to view more information
and verify the connection.
Go to Log & Report > Event Log >
VPN.
Select an entry to view more information
and verify the connection.
370
VPNs
Return to the Microsoft Azure virtual

network Dashboard. The status of the
tunnel will show as Connected.
Data In and Data Out will indicate that
traffic is flowing.
For further reading, check out Gateway-togateway configurations in the FortiOS 5.2
Handbook.
VPNs
371
In this recipe, you will use remote IPsec and SSL VPN tunnels to bypass Internet access restrictions.
Restricted Internet access is simulated with a Web Filter profile that blocks google.com. You will create
FortiClient SSL and IPsec VPN tunnels to bypass the web filter, connect to a remote FortiGate unit, and
transparently browse the Internet to google.com.
The recipe assumes that a "vpn_users"user group and a Local LAN firewall address have already been created.
VPNs
372
1.Starting point
In this example, we simulate restricted
Internet access using a Web Filtering
profile to block Google.
With the user situated behind this
FortiGate, google.com cannot be
accessed, and instead the FortiGuard
"Web Page Blocked" message appears.
For theuser to bypass this Web Filter,
the following VPN configurations must
be made on a remote FortiGate(which is
notblocked by any filter), and the user
must connectto it usingFortiClient.
2. Configuring the IPsec VPN

On the remote Fortigate, go to VPN >
IPSec > Wizard.
Dial Up - FortiClient (Windows, Mac
OS, Android) and click Next.
The tunnel name must not have any

spaces in it.
VPNs
373

internet-facing interface. In this case,
wan1.
Enter a pre-shared key and select
thevpn_users user group, then click
Next.

password.
Set Local Interface to theinternal
interface and set Local Address to the
local LAN address.

Click Next and select Client Options as

desired.
374
VPNs
When using the IPsec VPN Wizard,an IPsec firewall address range is automatically created using the name of
the tunnel you entered into the Wizard. The Wizard also creates an IPsec -> internal IPv4 policy, so all that is
left is to create the Internet access policy. See Step 4.
3. Configuring the SSL VPN

Go to VPN > SSL > Portals, highlight
the full-access portal, and select Edit.
DisableSplit Tunneling so that all VPN

traffic will go through the FortiGate
firewall.
Go to VPN > SSL > Settings. Under

Connection Settings set Listen on
Port to 10443.
Under Authentication/Portal Mapping,

assign the vpn_users user group to the
full-access portal, and assign All Other
Users/Groups to the desired portal.
By default, the FortiGate has an ssl.root firewall address.All that is left is to create the Internet access policy,
as described in the following step.
VPNs
375
4. Creating security policies for VPN access to the Internet

Create twosecurity policies allowing
remote users to access the Internet
securely through the FortiGate unit; one
for each VPN tunnel.
For SSL VPN, set Source User(s) to
the vpn_users user group.
enable NAT.
5. Configuring FortiClient for IPsec and SSL VPN

andadd new connections for both VPNs.
376
VPNs
Type to eitherIPsec VPN or SSL

VPNdepending on the VPN
configuration.
IP address.
l
For IPsec VPN, set Authentication

Method to Pre-Shared Key and enter the
key below.
For SSL VPN, set Customize Port to
10443.
(Optional) For Username, enter

ausernamefrom the vpn_users user
group.

Connect.
If prompted with a server authentication

warning, select Yes.
VPNs
377
6. Results
From FortiClient start an IPsec or SSL
VPN session. Once the connection is
established, the FortiGate assigns the
user an IP address and FortiClient
displays the status of the connection,
including the IP address, connection
duration, andbytes sent and received.
With the tunnel up, you can nowvisit

google.com without being blocked, since
the Internet traffic is handled by the
remote FortiGate and the web filter on the
local FortiGate has been bypassed.

Handbook.
378
VPNs
In this recipe, you will configure a site-to-site, also called gateway-to-gateway, IPsec VPN between an office with
Internet access restrictions (Remote Office) and an office without these restrictions (Head Office) so that the
Remote Office can access the Internet through the Head Office, avoiding the restrictions.
To bypass this restriction, this example shows how create a site-to-site VPN to connect the Remote Office
FortiGate unit to the Head Office FortiGate unit, and allow Remote Office staff to transparently browse the Internet
to google.com using the Head Offices Internet connection.
Note that both FortiGates run FortiOS firmware version 5.2.2 and have static IP addresses on Internet-facing
interfaces. You will also need to know the Remote Offices gateway IP address.
VPNs
379
1. Configuring IPsec VPN on the Head Office FortiGate

In a real world scenario, a Remote Office's ISP or something in their local Internet may be blocking access to
Google, or any other site for that matter.
On the Head Office FortiGate, go to VPN
> IPSec > Wizard.
Name the VPN, select Site to Site FortiGate, and click Next.
Set the Remote Gateway to the

Remote Office FortiGate IP address
The Wizard should select the correct
Outgoing Interfacewhen you click
anywhere else in the window. Depending
on your configuration, you may have to
manually set the outgoing interface.
Enter a pre-shared keythen click Next.

password. Both FortiGate's must have
the same pre-shared key.
VPNs
380
Under Policy & Routing,set theLocal

Interfaceto the interface connected to
the Head Office internal network.
For Local Subnets, enter the subnet
range of the Head Office internal
network. Depending on your
configuration, this may be set
automatically by the wizard.
For Remote Subnets, enter the subnet
range of the Remote Officeinternal
network then click Create.
The VPN Wizard informs you that a
static route has been created, as well as
two two securitypolicies and
twoaddress objects, which are added to
two address groups (also created).
381
VPNs
Create a security policy to allow the

Remote Office to have Internet access.
and select Create New.
Set Incoming Interface to the VPN
interface created by the VPN wizard and
set Source Address to the remote office
address groupcreated by the VPN
wizard.
Set Outgoing Interface to the Internetfacing interface and set Destination
Address toall.
Enable NATand (optionally) enforce any
company security profiles.
2. Adding a route on the RemoteOffice FortiGate

On the Remote Office FortiGate, create a
static route that forwards traffic destined
for the Head Office FortiGate to the ISP's
Internet gateway.
(In this example, the Head Office
FortiGate IP address is 172.20.120.154
so the destination IP/Mask is
172.20.120.154/255.255.255.0 and the
ISP's gateway IP address is
10.10.20.100.)
VPNs
382
3. Configuring IPsec VPN on the RemoteOffice FortiGate

On the Remote Office FortiGate, go to
VPN > IPSec > Wizard.
Name the VPN, select Site to Site FortiGate, and click Next.
Set the Remote Gateway to the Head

Office FortiGate IP address.
The Wizard should select the correct
Outgoing Interface.
Authentication Methodand enterthe
same Pre-shared Key as you entered in
Step 1.
383
VPNs
Under Policy & Routing,set theLocal

Interfaceto the interface connected to
the Remote Office internal network.
For Local Subnets, enter the subnet
range of the RemoteOffice internal
network.
For Remote Subnets, enter the subnet
range of the HeadOfficeinternal network
then click Create.
The VPN Wizard informs you that a
static route has been created, as well as
two address groups and two
securitypolicies.
Allow Internet traffic from the remote

office to enter the VPN tunnel.
On the Remote Office FortiGate, goto
Policy & Objects > Policy > IPv4.
Edit the outbound security policy created
by the VPN Wizard.
Change the Destination Address to all
so that the policy accepts Internet traffic.
VPNs
384
4.Establishing the tunnel

On either FortiGate, go to VPN >
Monitor > IPsec Monitor.
Right-click the newly created tunnel and
select Bring Up.
If the tunnel is established, the Status
columnwill read Up on both of the
FortiGates.
6. Results
With the tunnel up, you can nowvisit
google.com without being blocked, since
the Internet traffic is handled by theHead
OfficeFortiGate and the access
restrictions on the remoteFortiGate have
been bypassed.

Handbook.
385
VPNs
This section contains tips to help you with some common challenges of IPsec VPNs.
The options to configure policy-based IPsec VPN are unavailable.

Go to System > Config > Features. Select Show More and turn on Policy-based IPsec VPN.
The VPN connection attempt fails.

If your VPN fails to connect, check the following:
l
Ensure that the pre-shared keys match exactly.
Ensure that both ends use the same P1 and P2 proposal settings.
Ensure that you have allowed inbound and outbound traffic for all necessary network services, especially if
services such as DNS or DHCP are having problems.
Check that a static route has been configured properly to allow routing of VPN traffic.
Ensure that your FortiGate unit is in NAT/Route mode, rather than Transparent.
Check your NAT settings, enabling NAT traversal in the Phase 1 configuration while disabling NAT in the
security policy.
Ensure that both ends of the VPN tunnel are using Main mode, unless multiple dial-up tunnels are being
used.
If you have multiple dial-up IPsec VPNs, ensure that the Peer ID is configured properly on the FortiGate
and that clients have specified the correct Local ID.
If you are using FortiClient, ensure that your version is compatible with the FortiGate firmware by reading
the FortiOS Release Notes.
Ensure that the Quick Mode selectors are correctly configured. If part of the setup currently uses firewall
addresses or address groups, try changing it to either specify the IP addresses or use an expanded
address range.
If XAUTH is enabled, ensure that the settings are the same for both ends, and that the FortiGate unit is set
to Enable as Server.
If your FortiGate unit is behind a NAT device, such as a router, configure port forwarding for UDP ports 500
and 4500.
Remove any Phase 1 or Phase 2 configurations that are not in use. If a duplicate instance of the VPN tunnel appears on the IPsec Monitor, reboot your FortiGate unit to try and clear the entry.
If you are still unable to connect to the VPN tunnel, run the diagnostic command in the CLI:
diag debug application ike -1diag debug enable
VPNs
386
The resulting output may indicate where the problem is occurring. When you are finished, disable the diagnostics
by using the following command:
diag debug resetdiag debug disable
The VPN tunnel goes down frequently.

If your VPN tunnel goes down often, check the Phase 2 settings and either increase the Keylife value or enable
Autokey Keep Alive.
387
VPNs
This example provides remote users with access to the corporate network using SSL VPN and connect to the
Internet through the corporate FortiGate unit. During the connecting phase, the FortiGate unit will also verify that
the remote users antivirus software is installed and current.
VPNs
388
1. Creating an SSL VPN portal for remote users

Go to VPN > SSL > Portals.
Edit the full-access portal. The fullaccess portal allows the use of tunnel
mode and/or web mode. In this scenario
we are using both modes.
Enable Split Tunneling is not enabled
so that all Internet traffic will go through
the FortiGate unit and be subject to the
corporate security profiles.
VPNs
389
Select Create New in the Predefined

Bookmarks area to add a bookmark for a
remote desktop link/connection.
Bookmarks are used as links to internal
network resources.
You must include a username and
password. You will create this user in the
next step, so be sure to use the same
credentials.
390
VPNs
2. Creating a user and a user group

Definition.
Add a remote user with the User
Creation Wizard (in the example,
twhite, with the same credentials used
for the predefined bookmark).

Groups.
Add the user twhite to a user group for
SSL VPN connections.
VPNs
391
3. Adding an address for the local network

Addresses.
Add the address for the local network.
Set Subnet / IP Range to the local
subnet and set Interface to an internal
port.
4. Configuring the SSL VPN tunnel

Go to VPN > SSL > Settings and set
Listen on Interface(s) to wan1.
Set Listen on Port to 443 and Specify
custom IP ranges.

add the SSL VPN user group.
392
VPNs
5. Adding security policies for access to the Internet and internal network
Add a security policy allowing access to
the internal network through the ssl.root
VPN tunnel interface.
Set Incoming Interface to ssl.root.
Set Source Address to all and select
the Source User group you created in
step 2.
Set Outgoing Interface to the local
network interface so that the remote user
can access the internal network.
Set Destination Address to all, enable
NAT, and configure any remaining
firewall and security options as desired.
Add a second security policy allowing
SSL VPN access to the Internet.
For this policy, Incoming Interface is
set to ssl.root and Outgoing Interface
is set to wan1.
6. Setting the FortiGate unit to verify users have current AntiVirus software
Go to System > Status > Dashboard.
config vpn ssl web portal

edit full-access
In the CLI Console widget, enter the
set host-check av
commands on the right to enable the host
end
to check for compliant AntiVirus software end
on the remote users computer.
VPNs
393
7. Results
Log into the portal using the credentials
you created in step 2.
The FortiGate unit performs the host

check.
394
VPNs
After the check is complete, the portal

appears.
You may need to install the FortiClient

application using the available download
link.
Select the bookmark Remote Desktop

link to begin an RDP session.
Go to VPN > Monitor > SSL-VPN

Monitor to verify the list of SSL users.
The Web Application description
indicates that the user is using web
mode.
VPNs
395

Forward Traffic and view the details for
the SSL entry.
In the Tunnel Mode widget, select

Connect to enable the tunnel.
Select the bookmark Remote Desktop

link to begin an RDP session.
396
VPNs
Go to VPN > Monitor > SSL-VPN

Monitor to verify the list of SSL users.
The tunnel description indicates that the
user is using tunnel mode.
Forward Traffic and view the details for
the SSL entry.

Forward Traffic.
Internet access occurs simultaneously
VPNs
397
For further reading, check out Basic SSL

VPN configuration in the FortiOS 5.2
Handbook.
398
VPNs
In this recipe, you will create an SSL VPN that remote users connect to using FortiClient running on iOS.
When a user using an iOS device connects to this SSL VPN, they can access servers and data on the internal
network. They can alsosecurely browse the Internet using the FortiGate's Internet connection.
This example uses FortiClient 5.2.0.028 for iOS. FortiClient can be downloaded from www.forticlient.com.
VPNs
399
1. Creating users and a user group

Definition.
Add as many local users as requiredwith
the User Creation Wizard.

Groups.
Create a user group for FortiClient users
and add the new user(s) to the group.
2. Creating an SSL VPN portal

Edit the tunnel-access portal. This
portal supports tunnel mode by default.
so that all SSL VPN traffic will go through
the FortiGate unit.
VPNs
400

Set Listen on Port to 10443 and Specify
custom IP ranges. Use the default IP
Range, SSLVPN_TUNNEL_ADDR1.
At the bottom of the page,

underAuthentication/Portal Mapping,
add the FortiClient user group.
If necessary, map a portal for All Other
Users/Groups.
401
VPNs
Create a security policy allowing SSL
VPN user to access the internal network.
Set Incoming Interface to ssl.root. Set
Source Address to all and Source
User to the new user group. Set
Outgoing Interface to the local network
interface so that the remote user can
access the internal network.
SSL VPN users to access the Internet.
is set to wan1.
VPNs
402
5. Configuring FortiClient for SSL VPN in iOS

Install FortiClient on the iOS device.
Add a new VPN Gateway.
Set Host Name to the FortiGate's IP (in
the example, 172.20.120.236), set Host
Port to 10443, and set User Name to
match the new user account.
403
VPNs
6. Results
Select the VPN in FortiClient. Enter the
Password and select Login.
You will be able to connect to the VPN.
VPNs
404
On the FortiGate, go to VPN > Monitor >

SSL-VPN Monitor to see that the user
has connected.
For further reading, check out FortiClient in

405
VPNs
In this example, you will connect to a private network with a Windows Phone, using an SSL VPN.
VPNs
406
1. Creating a VPN portal with custom bookmarks

Go to VPN > SSL > Portals and create a
new portal.
Enable both Tunnel Mode and Web
Mode. Disable Split Tunneling and set
Source IP Pools to use the default SSL
VPN tunnel address range.
Under Predefined Bookmarks, create
bookmarks to access resources on the
internal network.
VPNs
407
2. Creating a user and user group

Go User & Device > User > User

Groups and create a new user group.
Set Members to include the new user.
408
VPNs
3. Configuring the VPN tunnel

Set Listen on Port to 10443 and
Specify custom IP ranges using the
default SSL VPN tunnel addresses.

add the new user group.

Add a security policy allowing access to
the internal network through the ssl.root
VPN tunnel interface.
Set Incoming Interface to ssl.root.
Set Source Address to all and select
the Source User new user group.
Set Outgoing Interface to the local
network interface so that the remote user
can access the internal network.
VPNs
409

SSL VPN access to the Internet.
is set to your Internet-facing interface.
3. Results
Using your Window Phone's web
browser, access the portal. The portal's
address is the IP address of your
Internet-facing interface with the port the
SSL VPN tunnel is listening to, and it
must be accessed using HTTPS (in the
example, https://201.21.161.9:10443).
Log in using the credentials for your SSL
VPN user.
410
VPNs
After your credentials are accepted, you

will be able to see the VPN portal.
Select one of the pre-defined bookmarks

(in the example, the bookmark for a
FortiManager device). You will be able to
access the network resource.
For further reading, check out The SSL

VPN web portal in the FortiOS 5.2
Handbook.
VPNs
411
In this recipe, you will configure an SSL VPN tunnel that requires users to authenticate using a certificate.
This recipe requires that you have three certificates:
l
CA certificate
server certificate (signed by the CA certificate)
user certificate (signed by the CA certificate)
The certificates in the example were created using OpenSSL.
VPNs
412
1. Enabling certificate management

Go to System > Config > Features >
Show More and make sure that
Certificates is enabled.
If necessary, Apply your changes.
2. Installing the server certificate

The server certificate is used for encrypting SSL VPN traffic and will be used for authentication.
Import > Local Certificate.
Set Type to Certificate, choose the
Certificate file and the Key file for your
certificate, and enter the Password. If
desired, you can also change the
Certificate Name.
The server certificate now appears in the

list of Certificates.
VPNs
413
3. Installing the CA certificate

The CA certificate is the certificate that signed both the server certificate and the user certificate. In this
example, it is used to authenticate SSL VPN users.
Import > CA Certificate.
Select Local PC, then select the
certificate file.
The CA certificate now appears in the list

of External CA Certificates (in the
example, it is called CA_Cert_1).
4. Creating PKI users and a user group

In order to use certificate authentication, PKI users must be created in the CLI. Go to System > Dashboard >
Status and enter the following commands into the CLI widget:
config user peer
edit rdiaz
set ca CA_Cert_1
set subject User01
end
Make sure that subject matches the name of the user certificate (in the example, User01)
414
VPNs
Now that you have created a PKI user, a

new menu has been added to the GUI.
[tippy title="*" class="myclass"
showheader="false" width="auto"
height="auto"]You may need to refresh
the GUI before the menu appears.[/tippy]
Go to User & Device > PKI to see the
new user listed.
Edit the user account and expand Twofactor authentication. Enable Require
two-factor authentication and set a
Password for the account.
Groups and create a group for SSL VPN
users. Add the new user to the group.
VPNs
415
5. Creating an SSL VPN portal

Edit the full-access portal. This portal
supports both web and tunnel mode.
the FortiGate unit.
416
VPNs

Go to VPN > SSL > Settings.
Under Connection Settings, set Listen
on Interface(s) to wan1. To avoid
conflicts, set Listen on Port to 10443.
Set Server Certificate to the
authentication certificate and enable
Require Client Certificate.
assign the user group to the full-access
portal. If necessary, assign a portal for
All Other Users/Groups.
User to the new user group. Set
interface so that the remote user can
VPNs
417

SSL VPN users to access the Internet.
is set to wan1.
Make sure that NAT is enabled.
8. Installing the user certificate

To use the user certificate, it must first be installed on the user's PC. When the user attempts to authenticate,
the user certificate will be checked against the CA certificate, to verify that they match.
Every user should have a unique user certificate, so that you can distinguish each user and so that it is possible
to revoke a user's certificate if they should no longer have VPN access.
The installation instructions differ depending on what application is being used to connect to the VPN.
Internet Explorer or Safari (on Windows or Mac OS):

If you are using the above applications to connect to the VPN, you must install the certificate into the certificate
store for your OS. The certificate should be installed in the user's local certificate store (and not on the
machine's local certificate store).
418
VPNs
If you are using Windows 7/8/10, open

the certificate file and select Install
Wizard. Import the certificate into the
Personal store.
If you are using Mac OS X, open the

certificate file. Keychain Access opens.
Double-click the certificate. Expand
Trust and select Always Trust.
VPNs
419
FortiClient (on Windows or Mac OS)

In order to connect to the VPN with FortiClient, you will first have to use the above instructions to install the
certificate for your OS. Once the certificate has been installed, you can configure FortiClient to access the VPN.
Open FortiClient and go to Remote
Access > Configure VPN. Create a new
SSL VPN connection.
Set the Connection Name, Remote
Gateway, and Customize port. Enable
Client Certificate and select the
authentication certificate.
Firefox (on Windows or Mac OS)

Firefox has its own certificate store. If you will be using Firefox to connect to the VPN, then the user certificate
must be installed in this store, rather than in the OS.
420
VPNs
Depending on the version, go to Menu >

Select View Certificates, then select the
Your Certificates list. Import the
certificate file.
9. Results
Using a web browser
Browse to the SSL VPN portal (in the
example, http://172.20.121.46:10443).
A message will appear requesting a
certificate for authentication. Select the
user certificate.
Enter your user credentials when
requested.
VPNs
421
You are able to connect to the SSL VPN

web portal.
Using FortiClient
Open FortiClient and connect to the
VPN. You are able to connect.
On the FortiGate, go to VPN > Monitor >

SSL-VPN Monitor. You can see that the
user is currently connected to the VPN.
422
VPNs
This recipe provides remote FortiClient users with access to the corporate network using SSL VPN and Internet
browsing through the corporate FortiGate unit. Remote users are authenticated using RADIUS (configured in
Microsofts Network Policy Server).
FortiClient is available here.
The recipe includes a brief explanation of the RADIUS server configuration we utilized. It was tested on a
FortiGate 60D. Microsoft Network Policy Server was configured on Windows Server 2008.
VPNs
423
1. Configuring Microsoft's Network Policy Server

In RADIUS Client properties, enable the
client and set Vendor name to RADIUS
Standard.
Uncheck both Access-Request
message must contain the MessageAuthenticator attribute and RADIUS
client is NAP-capable.
VPNs
424
In Connection Request Properties >

Overview, create a policy, name it and
enable it.
Set Type of network access server to
Unspecified.

Conditions, set the Condition to either
NAS Identifier (the FortiGate Name) or
NAS IPv4 Address (the FortiGate IP).
You can also configure both. Just be
aware that if there is more than one
condition configured, they must all pass
to allow the connection.
425
VPNs

Settings > Authentication, make sure
Authenticate requests on this server
is enabled.
VPNs
426

Vendor Specific, add a new VendorSpecific attribute with Vendor set to
RADIUS Standard and the Vendor
Code 12356.
427
VPNs
In Network Policies > Overview, create

a policy, name it and enable it.
Set Type of network access server to
Unspecified.
In Network Policies > Conditions, add

a User Group that contains the users you
want to allow connection to the VPN and
apply the necessary conditions.
VPNs
428
In Network Policies > Constraints >

Authentication Methods, enable MSCHAP-v2.
You do not need to modify any of the
remaining network policy settings.
429
VPNs
2. Configuring the FortiGate to connect to the RADIUS server

On your FortiGate, go to User & Device
> Authentication > RADIUS Servers.
Enter a Name for the RADIUS server,
and enter its Primary Server IP/Name.
Carefully and correctly enter the Primary
Server Secret, and specify the
authentication method MS-CHAP-v2.
Perform a RADIUS connectivity test by
clicking Test Connectivity.
Enter valid RADIUS credentials and

click Test.
If there is an error in the configuration, or

the credentials were entered incorrectly,
the RADIUS connectivity test returns
with a Server is unreachable error. If
this occurs, double-check the
configuration for errors and try again.
If everything is configured and entered
correctly, the RADIUS connectivity test
returns with a Successful confirmation
message.
Click OK.
VPNs
430
3. Adding the SSL VPN remote user group

Groups.
Create an SSL VPN remote user group
and add the RADIUS server as a
Remote group.
You can choose to specify a group name
that matches a group in the RADIUS
configuration, or leave it set to Any (the
default setting), which permits any user
configured on the RADIUS server.
431
VPNs

Edit the full-access portal.
the FortiGate unit.

Set Listen on Port to 10443 .
Disable Require Client Certificate.
User to the remote user group. Set
interface so that the remote user(s) can
VPNs
432
Add a second security policy allowing SSL VPN

users to access the Internet.

is set to wan1.
Set Source User to the remote user
group.
Open FortiClient, go to Remote Access,
and add a new SSL VPN connection.
433
VPNs

Type to SSL VPN.
IP address .
Set Customize Port to 10443.
Select the new connection, enter a valid

Connect.
If prompted with a server authentication

warning, select Yes.
7. Results
VPNs
434
From FortiClient start an SSL VPN
session. As the connection is being

established, the FortiGate authenticates
the user against the RADIUS server and,
if successful, assigns the user an IP
address.
FortiClient then displays the status of the
connection, including the IP address,
connection duration, and bytes sent and
received.
For further reading, check out Basic SSL

VPN configuration in the FortiOS 5.2
Handbook.
435
VPNs
RADIUS authentication for SSLVPN with

FortiAuthenticator
This recipe describes how to set up FortiAuthenticator to function as a RADIUS server for FortiGate SSL VPN
authentication. It involves adding users to FortiAuthenticator, setting up the RADIUS client on the
FortiAuthenticator, and then configuring the FortiGate to use the FortiAuthenticator as a RADIUS server.
VPNs
436
1. Create the User(s) on FortiAuthenticator

From the FortiAuthenticator GUI, go to
Authentication > User Management >
Local Users, and select Create New.
Enter a name for the user (in the
example, ckent), enter and confirm a
password, and select OK. Select OK
again to bypass optional settings.
Next, go to Authentication > User

Management > User Groups, and add
a user group for the FortiGate users. Add
the desired users to the group.
VPNs
437
2. Create the RADIUS Client on FortiAuthenticator

Go to Authentication > RADIUS
Service > Clients, and select Create
New.
Enter a name for the RADIUS Client, set
Client name/IP to the IP of the
FortiGate, and set a Secret. The Secret
is a pre-shared, secure password that the
FortiGate will use to authenticate to the
FortiAuthenticator.
Be sure to set Authentication method
to Password-only authentication
(exclude users without a password),
and set Realms to local | Local users.
3. Connect the FortiGate to the RADIUS Server

From the FortiGate GUI, go to User & Device > Authentication > RADIUS Servers, and select Create New.
Enter a name for the RADIUS server,
enter the IP address of the
FortiAuthenticator, and enter the Secret
created before.
Test the connectivity and enter the
credentials for 'ckent'. The test should
come back with a successful
connection.
438
VPNs
4. Create the RADIUS User Group on the FortiGate

Go to User & Device > User > User Groups, and select Create New.
Enter a name for the user group, and
under Remote Groups, select Create
New.
Select FAC-RADIUS under the Remote

Server dropdown.
FAC-RADIUS has been added to the

RADIUS group.
VPNs
439
5. Configure the SSL VPN

From the FortiGate GUI, go to VPN >
SSL > Portals, and edit the full-access
portal.
Disable Split Tunneling.

Under Connection Settings set Listen
on Port to 10443.
Under Tunnel Mode Client Settings,
select Specify custom IP ranges and
set it to SSLVPN_TUNNEL_ADDR1.
select Create New.
Assign the RADIUSgroup user group to

the full-access portal, and assign All
Other Users/Groups to the desired
portal.
440
VPNs
Select the prompt at the top of the screen

to create a new SSL-VPN policy.
Set Source User(s) to the
RADIUSgroup user group.
enable NAT.
6. Results
From a remote device, access the SSL
VPN Web Portal.
Enter valid RADIUS credentials (in the
example, ckent).
'ckent' is now successfully logged into

the SSL VPN Portal.

Monitor > SSL-VPN Monitor to confirm
the connection.
VPNs
441
LDAP authentication for SSLVPNwith

FortiAuthenticator
This recipe describes how to set up FortiAuthenticator to function as an LDAP server for FortiGate SSL VPN
authentication. It involves adding users to FortiAuthenticator, setting up the LDAP server on the
FortiAuthenticator, and then configuring the FortiGate to use the FortiAuthenticator as an LDAP server.
VPNs
442
1. Create the User and User Group on FortiAuthenticator

From the FortiAuthenticator GUI, go to
Local Users, and select Create New.
Enter a name for the user (in the
example, jgarrick), enter and confirm a
password, and be sure to disable Allow
RADIUS authentication RADIUS
authentication is not required for this
recipe.
Set Role as User, and select OK. New
options will appear.
Make sure to enable Allow LDAP browsing the user will not be able to connect to the FortiGate otherwise.
Next, go to Authentication > User
Management > User Groups, and add
a user group for the FortiGate users. Add
the desired users to the group.
2. Create the LDAP Directory Tree on FortiAuthenticator

Go to Authentication > LDAP Service > Directory Tree, and create a Distinguished Name (DN) (in the
example, dc=fortinet,dc=com). A DN is made up of Domain Components (DC).
VPNs
443
Both the users and the user group

created earlier are the User ID (UID) and
the Common Name (CN) in the LDAP
Directory Tree.
Create an Organizational Unit (OU), and
a Common Name (CN). Under the
cn=HeadOffice entry, add UIDs for
each user.
If you mouse over one of the users, you will see the full DN of the LDAP server.
Later, you will use jgarrick on the FortiGate to query the LDAP directory tree on FortiAuthenticator, and you will
use bwayne credentials to connect to the VPN tunnel.
3. Connect the FortiGate to the LDAP Server

From the FortiGate GUI, go to User & Device > Authentication > LDAP Servers, and select Create New.
Enter a name for the LDAP Server
connection.
Set Server IP/Name as the IP of the
FortiAuthenticator, and set the Common
Name Identifier as uid.
Set the Distinguished Name as
dc=fortinet,dc=com, and set the Bind
Type to Regular.
Next, enter the User DN of the LDAP
server (in the example,
uid=jgarrick,cn=HeadOffice,
ou=techdoc,dc=fortinet,dc=com) and
enter the Password.
The User DN is an account that the
FortiGate uses to query the LDAP
server.
444
VPNs
Select Fetch DN to determine a

successful connection. If successful, a
dropdown menu will appear showing the
LDAP Tree, dc=fortinet,dc=com.
If you select Test, it should show that the

connection is Successful, however this
is a false declaration. Only selecting
Fetch DN will determine a successful
connection.
4. Create the LDAP User Group on the FortiGate

Go to User & Device > User > User Groups, and select Create New.
New.
Select LDAPserver under the Remote

Server dropdown.
VPNs
445
In the new Add Group Match window,

select HeadOffice under the Groups
tab, and select Add Selected, then click
OK.
LDAPserver has been added to the

LDAP group.
5. Configure the SSL VPN

SSL > Portals, and edit the full-access
portal.
446
VPNs

on Port to 10443.
Under Tunnel Mode Client Settings,
select Specify custom IP ranges and
set it to SSLVPN_TUNNEL_ADDR1.
select Create New.
Assign the LDAPgroup user group to the

Select the prompt at the top of the screen

to create a new SSL-VPN policy.
Set Source User(s) to the LDAPgroup
user group.
enable NAT.
VPNs
447
6. Results
From a remote device, access the SSL
VPN Web Portal.
Enter valid LDAP credentials (in the
example, bwayne).
'bwayne' is now successfully logged into

the SSL VPN Portal.

SSL > Monitor to confirm the
connection.
448
VPNs
This recipe describes how to configure an SSL VPN tunnel using LDAP Authentication on a FortiAuthenticator.
The VPN will be tested using FortiClient on a mobile Android device.
The recipe assumes that an LDAP server has already been configured and connected on the FortiGate, containing
the user 'bwayne'. For instructions on configuring FortiAuthenticator as an LDAP server, see LDAP authentication
for SSLVPNwith FortiAuthenticator.
VPNs
449
1. Creating the LDAP user group

From the FortiGate GUI, go to User & Device > User > User Groups, and select Create New.
New.
Select the LDAP server under the

Remote Server dropdown.
This part of the recipe assumes that an

LDAP server has already been
configured and connected on the
FortiGate, containing the user 'bwayne'.
In the new Add Group Match window,
select the desired group under the
Groups tab, select Add Selected, and
click OK.
The LDAP server has been added to the

LDAP group.
VPNs
450

Go to VPN > SSL > Portals, and edit the
full-access portal.

on Port to 10443.
select Create New.
451
VPNs
Assign the LDAPgroup user group to the

3. Creating the security policies for VPN access to the Internet

and create an ssl.root - wan1 policy.
Set Source User(s) to the LDAPgroup
user group.
enable NAT.
If it is not already available, create

another policy allowing internal access to
the Internet.
VPNs
452
4. Results
On your Android smartphone, open the FortiClient app and create a new VPN.
Give the VPN a name (in the example,
SSL to 121.56), and set the VPN Type to
SSL VPN. Select Create.
The SSL VPN settings will appear. Set

Server to the IP of the FortiGate (in the
example, 172.20.121.56), and set the
Port to 10443.
Set Username to the desired LDAP user
(in the example, bwayne), and set the
user's password.
453
VPNs
Return to FortiClient's list of VPN

Tunnels, and connect to the newly
created SSL VPN.
If prompted, enter valid LDAP
credentials.
User 'bwayne' is now connected to the

SSL VPN tunnel and can securely
browse the Internet.
VPNs
454
In this recipe, you will create an SSL VPN with two-factor authentication consisting of a username/password and
an SMS token. The SMS token is generated by FortiAuthenticator using the FortiGuard Messaging Service.
When a user attempts to connect to this SSL VPN, they are prompted to enter their username and password. After
successfully entering their credentials, they receive an SMS message on their mobile phone containing a 6-digit
number (called the FortiToken Code). They must also enter this number to get access to the internal network and
the Internet.
Although this recipe uses the FortiGuard Messaging Service, it will also work with any compatible SMS service
you configure as an SMS Gateway.
VPNs
455
1. Creating an SMS user and user group on the FortiAuthenticator

On the FortiAuthenticator, go to
Local Users and add/modify a user to
include SMS Token-based
authentication and a Mobile number
using the preferred SMS gateway as
shown.
The Mobile number must be in the
format:
+[international_number].
Enable Allow RADIUS authentication.
Go to Authentication > User

Management > User Groups and add
the above user to a new SMS user group
(in the example, ' SMSgroup').
VPNs
456
2. Configuring the FortiAuthenticator RADIUS client

Service > Clients and create a new
RADIUS client.
Enter a Name for the RADIUS client (the
FortiGate) and enter its IP address (in the
example, 172.20.121.56).
Enter the pre-shared Secret and set the
Authentication method. The FortiGate
will use this secret key in its RADIUS
configuration.
Choose to Enforce two-factor authentication and add the SMS user group to the Realms group filter as
shown.
Select Save and then OK.
3. Configuring the FortiGate authentication settings

On the FortiGate, go to User & Device >
Authentication > RADIUS Servers and
create the connection to the
FortiAuthenticator RADIUS server, using
its IP address and pre-shared secret.
Use the Test Connectivity button to
make sure that the FortiGate can
communicate with the
FortiAuthenticator.
457
VPNs
Next, go to User & Device > User >

User Groups and create a RADIUS
user group called RADIUSgroup.
Set the Type to Firewall and add the
RADIUS server to the Remote groups
table.

Under Connection Settings, set Listen
on Port to 10443 and set IP Ranges to
the SSL VPN tunnel address range.
select Create New.
Assign the RADIUSgroup user group to
the full-access portal, and assign All
Other Users/Groups to the desired
portal.
VPNs
458
5. Creating the security policy for VPN access to the Internet

and create an ssl.root wan1 policy.
Set Source User(s) to the
RADIUSgroup user group.
enable NAT.
6. Results
In this example, we will use the web portal to access the SSL VPN and test the two-factor authentication.
Open a browser and navigate to the SSL
VPN web portal, in this case
https://172.20.121.56:10443.
Enter a valid username and password
and select Login. You should be
prompted to enter a FortiToken Code.
459
VPNs
The FortiToken Code should have been

sent to your mobile phone as a text
message containing a 6-digit number.
Enter the number into the SSL VPN login
portal and select Login.
VPNs
460
You should now have access to the SSL

VPN tunnel.
To verify that the user has connected to

the tunnel, go to VPN > Monitor > SSLVPN Monitor.
461
VPNs

This page contains tips to help you with some common challenges for SSL VPN.
There is no response from the SSL VPN URL.

Go to VPN > SSL > Settings and check the SSL VPN port assignment. Also, verify that the SSL VPN policy is
configured correctly.
You receive an error stating that the web page cannot be found.
Check the URL you are attempting to connect to. It should follow this pattern:
https://:/remote/login.
Ensure that you are using the correct port number for the part of the URL.
FortiClient cannot connect.

Read the Release Notes to ensure that the version of FortiClient you are using is compatible with your version of
FortiOS.
When you attempt to connect using FortiClient or in Web mode, you receive the following error message: Unable to logon to the server. Your user name or password may not be configured properly for this connection. (-12).
Ensure that cookies are enabled in your browser. Also, if you are using a remote authentication server, ensure that
the FortiGate is able to communicate with it.
The tunnel connects but there is no communication.

Go to Router > Static > Static Routes (or System > Network > Routing on some FortiGate models) and ensure
that there is a static route to direct packets destined for the tunnel users to the SSL VPN interface.
VPNs
462
You can connect remotely to the VPN tunnel but are unable to access the network
resources.
Go to Policy & Objects > Policy > IPv4 and check the policy allowing VPN access to the local network. If the
destination address is set to all, create a firewall address for the internal network. Change the destination address
and attempt to connect remotely again.
Users are unable to download the SSL VPN plugin.

Go to at VPN > SSL > Portals to check the VPN Portal to ensure that the option to Limit Users to One SSL-VPN
Connection at a Time is disabled. This allows users to connect to the resources on the portal page while also
connecting to the VPN through FortiClient.
Users are being assigned to the wrong IP range.

Ensure that the same IP Pool is used in VPN Portal and VPN Settings to avoid conflicts. If there is a conflict, the
portal settings will be used.
463
VPNs
WiFi
These recipes describe how to use FortiAPs to add WiFi (or Wi-Fi) services to your network.
FortiAPs, managed by FortiGates, provide a full suite of WiFi features. Small offices can use FortiAPs to quickly
add WiFi. Enterprises and educational institutions can take advantage of FortiAP access control features. Each
WiFi network, or SSID, is represented by a WiFi network interface to which you can apply firewall policies,
security profiles, and other features in the same way you would for wired networks.
Getting started with WiFi

l
Combining WiFi and wired networks with a software switch
WiFi with other technologies

l
WiFi local authentication

l
Guest WiFi accounts
MAC access control
BYOD scheduling
WiFi remote authentication
WiFi

464
465
WiFi
In this example, a FortiAP unit is connected to and managed by a FortiGate unit in Tunnel mode, allowing wireless
access to the network.
You can configure a FortiAP unit in either Tunnel mode or Bridge mode. When a FortiAP is in Tunnel mode, a
wireless-only subnet is used for wireless traffic. When a FortiAP is in Bridge mode, the Ethernet and WiFi
interfaces are connected (or bridged), allowing wired and wireless networks to be on the same subnet. Tunnel
mode is the default mode for a FortiAP.
For information about using a FortiAP in Bridge mode, seeSetting up a WiFi bridge with a FortiAP.
WiFi
466
1. Connecting and authorizing the FortiAP unit

Connect the FortiAP unit to the the lan
interface.
Go to WiFi Controller > Managed

Access Points > Managed FortiAPs.
The FortiAP is listed, with a yellow
question mark beside it because the
device is not authorized.
The FortiAP may not appear until a few

minutes have passed.
Highlight the FortiAP unit on the list and
select Authorize. A grey checkmark is
now shown beside the FortiAP, showing
that it is authorized but not yet online.
WiFi
467
2. Creating an SSID
Go to WiFi Controller > WiFi Network >
SSID and create a new SSID.
Set Traffic Mode to Tunnel to Wireless
Controller.
Select an IP/Network Mask for the
wireless interface and enable DHCP
Server.
Set the WiFi Settings as required,
including a secure Pre-shared Key.
468
WiFi
3. Creating a custom FortiAP profile

FortiAP Profiles and create a new
profile.
Set Platform to the correct FortiAP
model you are using (FAP11C in the
example).
Set SSID to use the new SSID.

Access Points > Managed FortiAPs
and edit the FortiAP. Set FortiAP Profile
to use the new profile.
WiFi
469
4. Allowing wireless access to the Internet

Set Incoming Interface to the SSID and
Outgoing Interface to your Internetfacing interface. Ensure that NAT is
turned ON.
5. Results
Access Points > Managed FortiAPs. A
green checkmark now appears beside
the FortiAP, showing that the unit is
authorized and online.
Connect to the SSID with a wireless device. After a connection is established, you are able to browse the
Internet.
For further reading, check out Configuring a

WiFi LAN in the FortiOS 5.2 Handbook.
470
WiFi
In this example, a FortiAP unit is connected to and managed by a FortiGate unit in Bridge mode.
You can configure a FortiAP unit in either Tunnel mode or Bridge mode. When a FortiAP is in Tunnel mode, a
wireless-only subnet is used for wireless traffic. When a FortiAP is in Bridge mode, the Ethernet and WiFi
interfaces are connected (or bridged), allowing wired and wireless networks to be on the same subnet. Tunnel
mode is the default mode for a FortiAP.
For information about using a FortiAP in Tunnel mode, see Setting up WiFi with FortiAP.
WiFi
471
1. Connecting and authorizing the FortiAP unit

Connect the FortiAP unit to the the lan
interface.


2. Creating an SSID
SSID and create a new SSID.
Set Traffic Mode to Local bridge with
FortiAPs Interface.
Set the WiFi Settings as required,
including a secure Pre-shared Key.
WiFi
472
3. Creating a custom FortiAP profile

FortiAP Profiles and create a new
profile.
Set Platform to the correct FortiAP
model you are using (FAP11C in the
example).
Set SSID to use the new SSID.

Access Points > Managed FortiAPs
and edit the FortiAP. Set FortiAP Profile
to use the new profile.
473
WiFi
4. Results
Access Points > Managed FortiAPs. A
green checkmark now appears beside
the FortiAP, showing that the unit is
authorized and online.
Connect to the SSID with a wireless device. After a connection is established, you are able to browse the
Internet.
For further reading, check out Bridge SSID

to FortiGate wired network in the FortiOS
5.2 Handbook.
WiFi
474
Combining WiFi and wired networks with a software

switch
Including mobile (WiFi) users on your office LAN can be more convenient than putting them on a separate wireless
network. The Software Switch feature of your FortiGate is a simple way to do this.
Software Switches are only available if your FortiGate is in Interface mode. For more information, seeChoosing
your FortiGate's switch mode.
WiFi
475
1. Create the SSID

SSID and configure your wireless
network.
Leave the IP address empty. This is
allowed.
You can use any type of
security/authentication. In thisexample,
your users must be members of the
employees group to access the network.
2. Combine the WiFi and wired interfaces

Go to System > Network > Interface.
Edit the existing lan software switch
interface or create a new one.
Make sure your wired and WiFi
interfaces are both included.
Make sure there is a DHCP Server
configured. It will provide IP addresses to
both WiFi and wired users.
WiFi
476
3. Create the security policy

and create a policy allowing all users on
the software switch interface to connect
to the Internet.
4. Connect and authorize the FortiAP unit

Configure a network interface that is
dedicated to extension devices.
Connect the FortiAP unit and wait for it to

be listed in WiFi Controller > Managed
select Authorize.
477
WiFi
5. Add the SSID to the FortiAP profile

FortiAP Profiles and edit the profile for
your FortiAP model.
For each radio:
l
Enable Radio Resource Provision.
Select your SSID.
Results
Go to WiFi Controller > Monitor >
Client Monitor to see connected users.
For further reading, check out Software

switch in the FortiOS 5.2 Handbook.
WiFi
478
In this example, you use an external DHCP server to assign IP addresses to your WiFi clients.
The DHCP server assigns IP addresses in the range of 10.10.12.100 to 10.10.12.200. The server is attached to
Port 13 of the FortiGate and has an IP address of 10.10.13.254.
WiFi
479
1. Configure the FortiGate network interface for the DHCP server

and edit Port13.
The external DHCP server is on the
10.10.13.0 network, so put the interface
on that network.
2. Create the SSID

network.
The DHCP server assigns IP addresses
on the 10.10.12.0 network, so configure
the SSID address on this network.
Enable DHCP Server, then expand
Advanced and change the mode to
Relay. Enter the external DHCP server
IP address.
Set up security and authentication for

your SSID.
In this case, WPA2 Enterprise
authentication allows access only to
members of the employees user group.
WiFi
480
3. Create the security policies

Create a policy to allow the WiFi network
to communicate with the DHCP Server
on Port 13.
The source and destination networks are
directly visible to each other, so NAT is
not required.
Create a policy to allow WiFi clients to

connect to the Internet on wan1.

Configure the network interface where
the FortiAP will be connected.
481
WiFi


FortiAP Profiles and edit the profile,
adding your SSID to each radio.
Results
WiFi devices can connect to the Internet.
You can see them in the client monitor
(WiFi Controller > Monitor > Client
Monitor). Note the IP addresses
assigned by the external DHCP server.
For further reading, check out the

Deploying Wireless Networks in the
WiFi
482
In this example, you pre-configure a FortiAP to provide access to the office network from any remote location
simply by connecting the FortiAP to the Internet. This FortiAP could be given to an employee to use at home or
when traveling.
The FortiAPs configuration also supports Internet browsing from behind the corporate firewall. The remote users
local network remains accessible by defining it as a split tunnel destination that is not routed through the FortiGate
unit.
WiFi
483
1. Enable the split tunneling feature

By default, split tunneling options are not visible in the FortiGate GUI. You can make these options visible using
the CLI.
Go to System > Dashboard >
Status and use the CLI Console.

set gui-fortiap-split-tunneling enable
end
2. Create the WiFi network

Go to WiFi Controller > WiFi
Network > SSID and create a new
SSID. The SSID will accept logons
from the employees user group.
Enable the DHCP Server and make

note of the IP range.
WiFi
484

Addresses and create an address
representing the range of remote user
addresses that the DHCP server can
assign.

IPv4 and create a policy that allows
remote wireless users to access the
Internet and the corporate network.
485
WiFi
4. Create the FortiAP Profile

Go to WiFi Controller > WiFi
Network > FortiAP Profiles and
create a new profile for the FortiAP
model you are using.
The Split Tunneling Subnet(s) entry
exempts a typical home network
subnet from being routed through the
FortiGate.
Select the SSID that the remote
FortiAP will broadcast.
5. Enable CAPWAP on the Internet interface

Interfaces and edit the Internetfacing interface. In Administrative
Access, enable CAPWAP.
6. Pre-authorize the FortiAP unit

Devices > Managed FortiAPs and
create a new entry.
Enter your FortiAPs Serial Number
and a Name to identify whose device
it is.
Choose the FortiAP Profile that you
created.
WiFi
486
7. Configure the FortiAP unit

Use FortiExplorer to access the FortiAP CLI through the USB MGMT port.
Enter these commands to specify the
IP address of the FortiGate WiFi
controller, which will be the Internetfacing interface IP address. Enter exit
to end.
FAP11C3X13000412
FAP11C3X13000412
FAP11C3X13000412
FAP11C3X13000412
#
#
#
#
login: admin
cfg -a AC_IPADDR_1=172.20.120.142
cfg -c
exit
The remote user can now take this

device to a remote location to connect
securely to the corporate FortiGate
unit.
Results
At the remote location, connect the FortiAP to the Internet using an Ethernet cable. Next, connect the FortiAP to
power. The network must provide DHCP service and allow the FortiAP to access the internet.
Once connected, the FortiAP requests an IP address and locates the FortiGate wireless controller.
The remote WiFi user can now access the corporate network and browse the Internet securely from behind the
corporate firewall.
Connections to destinations on the "split tunneling" network are possible, but will not be visible in the FortiGate
logs as the traffic remains local to the FortiAP.
Client Monitor to see remote
wireless users connected to the
FortiAP unit.
487
WiFi

Forward Traffic to see remote
wireless users appear in the logs.
Select an entry to view more
information about remote traffic to the
corporate network and to the Internet.
For further reading, check out Deploying

Wireless Networks in the FortiOS 5.2
Handbook.
WiFi
488
In this example, two FortiAPs are used to extend the range of a single WiFi network. The second FortiAP is
connected to the FortiGate WiFi controller through a dedicated WiFi backhaul network.
In this example, both FortiAPs provide the example-staff network to clients that are in range.
More mesh-connected FortiAPs could be added to further expand the coverage range of the network. Each AP
must be within range of at least one other FortiAP. Mesh operation requires FortiAP models with two radios, such
as the FortiAP-221C units used here.
WiFi
489
1. Create the backhaul SSID

SSID.
Create a new SSID. Set Traffic Mode to
Mesh Downlink.
You will need the pre-shared key when
configuring the mesh-connected FortiAP.
2. Create the client SSID

SSID. Create the WiFi network (SSID)
that clients will use.
Configure DHCP for your clients.
WiFi
490

FortiAP Profiles and create a profile for
the Platform (FortiAP model) that you are
using.
Configure Radio 1 for the client channel
on the 2.4GHz 802.11n/g Band.
Configure Radio 2 for the backhaul
channel on the 5GHz 802.11ac/n Band.
4. Configure the security policy

491
WiFi
5. Configure an interface dedicated to FortiAP

and edit an available interface (in this
example, port 15). Set Addressing
mode to Dedicate to Extension
Device.
6. Preauthorize FortiAP-1
Devices > Managed FortiAPs and
create a new entry.
Enter the serial number of the FortiAP
unit and give it a name. Select the
FortiAP profile that you created earlier.
7. Configure FortiAP-2 for mesh operation

Connect FortiAP-2 to Port15.
Devices > Managed FortiAPs. FortiAP2, identified by serial number, will be
listed within two minutes. Note the
ConnectedVia IP address.
WiFi
492
FP221C3X14019926 login: admin
In the CLI Console, enter

exec telnet 192.168.1.4
(your address might be different) to log in
to the FortiAP as admin. Enter the
commands to change the AP to mesh
uplink on the backhaul-ssid network.
Enter exit to end.
FP221C3X14019926 # cfg -a MESH_AP_TYPE=1

FP221C3X14019926 # cfg -a MESH_AP_SSID=backhaulssid
FP221C3X14019926 # cfg -a MESH_AP_
PASSWD=backhaul-ssid-passwd
FP221C3X14019926 # cfg -c
FP221C3X14019926 # exit
Disconnect FortiAP-2 from the FortiGate.

Install it in its planned location and apply
power.
Connect FortiAP-1 to Port 15 and apply
power.
Devices > Managed FortiAPs. Select
the FortiAP-2 entry (identified by serial
number) and edit the new entry. Enter the
Name, FortiAP-2. Select the FortiAP
Profile that you created earlier. Click
Authorize. Click OK.
8. Connect and authorize the FortiAPs

Devices > Managed FortiAPs. The
FortiAPs will be listed as online within
about two minutes. (Click Refresh to
update the display.)
493
WiFi
9. Results
Client Monitor. Click Refresh to see
updated information.
Use a mobile device near FortiAP-2 to
connect to the example-staff network.
The monitor shows the mobile user
rgreen as a client of FortiAP-2.
Disconnect from the example-staff
network and then reconnect near
FortiAP-1. The monitor shows the mobile
user rgreen as a client of FortiAP-1.
Notice that in both cases FortiAP-2 is listed on backhaul-ssid as a client of FortiAP-1.
For further reading, check out Wireless

Mesh in the FortiOS 5.2 Handbook.
WiFi
494
In this example, you will add explicit proxy with web caching to your wireless network.
All devices on the wireless network will be required to connect to the proxy at port 8080 before they can browse
web pages on the Internet. WAN Optimization web caching is added to reduce the amount of Internet bandwidth
used and improve web browsing performance.
WiFi
495
1. EnablingWAN Optimization and configuring the explicit web proxy for the
wireless interface
Ensure that Explicit Proxy andWAN
Opt & Cache are enabled.
Go to System > Network > Interfaces,

edit the wireless interface and select
Enable Explicit Web Proxy.
WiFi
496
Go to System > Network > Explicit

Proxy. Select Enable Explicit Web
Proxy for HTTP/HTTPS. Make sure that
Default Firewall Policy Action is set to
Deny.
2. Adding an explicit web proxy policy

Explicit Proxy and create a new policy.
Set Explicit Proxy Type to Web and the
Outgoing Interface to the Internetfacing interface.
Turn on Web Cache.
497
WiFi
3. Configuring devices on the wireless network to use the web proxy

To use the web proxy, all devices on the wireless network must be configured to use the explicit proxy server.
The IP address of the server is the IP address of the FortiGate's wireless interface (in the example, 10.10.80.1)
and the port is 8080. Some browsers may have to be configured to use the device's proxy settings.
Windows Vista/7/8:
Open Internet Properties. Go to
Connections > LAN Settings and
enable and configure the Proxy Server.
Mac OS X:
Open Network Preferences > Wi-Fi >
Advanced > Proxies. Select Web
Proxy (HTTP) and configure the proxy
settings.
iOS:
Go to Settings > Wi-Fi. Edit the wireless
network. Scroll down to HTTP PROXY
select Manual and configure the proxy
settings.
WiFi
498
Android:
In WiFi network connection settings, edit
the wireless network. Select Show
advanced options, configure a Manual
proxy and enter the proxy settings.
4. Force HTTP and HTTPS traffic to use the Web Proxy

Block HTTP and Replace...HTTPS
access to the Internet from the wireless
network so that the only path to the
Internet is through the explicit proxy. You
can edit or delete policies that allow
HTTP or HTTPS access. You can also
add a policy to the top of the list that
Denies HTTP and HTTPS traffic.
499
WiFi
5. Results
To confirm that the proxy is processing traffic, attempt to connect to the Internet from the Wireless network
using a device that has not been configured to connect to the proxy. Access should be blocked.
Configure the device to use the proxy.
You should now be able to connect to the
Internet.
Go toWAN Opt. & Cache > Monitor
>WAN Opt. Monitor to view
WEBPROXY traffic in the Traffic
Summary.Check the Bandwidth
Optimization graph for WEBPROXY
traffic.
WiFi
500
Go toWAN Opt. & Cache > Monitor >

Cache Monitor to view web caching
activity.
For further reading, check out The

FortiGate explicit web proxy in the FortiOS
5.2 Handbook.
501
WiFi
Guest WiFi accounts
In this example, a guest user account will be created to allow temporary wireless access to the Internet. Access
will only be allowed using HTTP, HTTPS, and DNS protocols.
In this example, a FortiAP in Tunnel mode is used to provide wireless access to guests.
If you have not already set up a wireless network, see Setting up WiFi with FortiAP.
WiFi
502
1. Creating a WiFi guest user group

Groups and create a new group.
Set Type to Guest. Set User ID to
Email, ensure that Password is set to
Auto-Generate, and set Expiry Type to
After first login. Leave Default Expiry
Time set to 4 Hours.
2. Creating a guest SSID that uses Captive Portal

Go to Wireless Controller > WiFi
Network > SSID and create a new
SSID.
Set Traffic Mode to Tunnel to Wireless
Controller. Assign an IP/Network Mask
to the interface and enable DHCP
server. Under WiFi Settings, set
Security Mode to Captive Portal and
User Group(s) to the WiFi guest user
group.
Go to Wireless Controller > WiFi

Network > FortiAP Profiles and edit the
profile for your FortiAP model (in the
example, FortiAP-11C).
Set the FortiAP to broadcast the new
SSID.
WiFi
503
3. Creating a security policy for WiFi guests

Set Incoming Interface to the guest
SSID, Source User(s) to the WiFi guest
user group, the Outgoing Interface to
your Internet-facing interface, and
Service to HTTP, HTTPS, and DNS.
4. Creating a guest user account

Go to User & Device > User > Guest
Management and create a new account.
Set Email to the user's email address (in
the example, ballen@example.com). To
test the account, set Expiration to 5
Minutes.
After you select OK, a User Created

Successfully notice will appear, listing
the generated Password. This password
can then be printed or emailed to the
guest user.
504
WiFi
(Optional) 5. Creating a restricted admin account for guest user management

To make it easier for guest accounts to be created, an admin account can be made that is only used for guest
user management. In this example, the account is made for use by the receptionist.
Administrators and create a new
account.
Set Type to Regular and set a
Password. Select Restrict to Provision
Guest Accounts and set Guest Groups
to the WiFi guest user group.
Sign in to the FortiGate using this

account. You will only be able to see the
menu for Guest User Management.
WiFi
505
6. Results
On a PC, connect to the guest SSID.
When the authentication screen appears,
log in using the guest user's credentials.
You will be able to connect to the
Internet.
Five minutes after the initial login, the

user account will expire and you will no
longer be able to log in using those
credentials.
For further reading, check out Managing

Guest Access in the FortiOS 5.2
Handbook.
506
WiFi
In this example, your employees can log on to your Wi-Fi network through a captive portal.
Captive portals are often used for public Wi-Fi networks where you want Wi-Fi users to respond to a disclaimer.
Captive portals can also be used to provide unlimited access to open Wi-Fi networks.
As shown in this example, captive portals can also be used as the authentication method for restricting access to
a wireless network. Some users may find it more intuitive to add their account information to a captive portal web
page instead of a entering their user name and password into a wireless network configuration.
WiFi
507
1. Create user accounts

Definition and create a Local user.
Create additional users as needed. You
can use any authentication method.
2. Create a user group

Groups.
Create a user group for employees and
add the new user(s) to the group.
3. Create the SSID

network.
Configure DHCP addressing for clients.
WiFi
508
Configure Captive Portal authentication

using the employees user group.

Create an address for your SSID, using
the same IP range that was set on the
DHCP server.

and create a policy allowing WiFi users
to connect to the Internet. Select the
employees user group as permitted
Source Users.
509
WiFi

Configure an interface dedicated to
extension devices and assign it an IP
address.
Connect the FortiAP unit to the interface
and go to WiFi Controller > Managed
The FortiAP may not appear for a minute

or two.
select Authorize.
A grey check mark is now shown beside

the FortiAP, showing that it is authorized
but not yet online.
FortiAP Profiles and edit the profile. For
each radio:
Select your SSID.
WiFi
510
6. Results
The user's device shows the WiFi
network as "open" and associates with it
without requesting credentials. The first
time that a wireless user attempts to use
a web browser, the captive portal login
screen is displayed. Users who are
members of the employees group can log
on using their username and password
and proceed to access the wireless
network.

For further reading, check out Captive

portals in the FortiOS 5.2 Handbook.
511
WiFi
In this example, you will improve your WiFi security with WPA2 enterprise authentication.
In the Setting up WiFi with FortiAP recipe, you set up a WiFi network with a single pre-shared key. In this
example, there is no longer a pre-shared key that could fall into the wrong hands, or that needs to be changed if
someone leaves the company. Each user has an individual user account and password, and accounts can be
added or removed later as needed.
This example shows how to authenticate local FortiGate users. You can also integrate WPA2 security with most
3rd party authentication solutions including RADIUS.
WiFi
512
1. Create user accounts

2. Create a user group

Groups.
3. Create the SSID and enable the WiFi radio

network.
Configure DHCP addressing for clients.
WiFi
513
Configure WPA2-Enterprise
authentication using the employees user
group.

Create an address for your SSID, using
the same IP range that was set on the
DHCP server.

and create a policy allowing WiFi users
to connect to the Internet.
514
WiFi
Results
Users who are members of the employees group can log on to the WiFi network using their username and
password.

Handbook.
WiFi
515
MAC access control
In this example, you will add device definitions to your FortiGate using Media Access Control (MAC) addresses.
These definitions are then used to determine which devices can access the wireless network.
By using a MAC address for identification, you will also be able to assign a reserved IP for exclusive use by the
device when it connects to the wireless network.
Warning: Since MAC addresses can be easily spoofed, using MAC access control should not be considered a
security measure.
WiFi
516
1. Finding the MAC address of a device

The instructions below were written for the most recent OS versions. Older versions may use different methods.
For Windows devices:

Open the command prompt and type
ipconfig /all
This output displays configuration
information for all of your network
connections. Look for the information
about the wireless adapter and take note
of the Physical Address.
For Mac OS X devices:

Open Terminal and type ifconfig
en1 | grep ether.
Take note of the displayed MAC
address.
For iOS devices:

Open Settings > General and take note
of the
Wi-Fi Address.
WiFi
517
For Android devices:

Open Settings > More > About Device
> Status and take note of the Wi-Fi MAC
address.
2. Defining a device using its MAC address

Device Definitions and create a new
device definition.
Set MAC Address to the address of the
device and set the other fields as
required. In the example, a device
definition is created for an iPhone with
the MAC Address B0:34:95:C2:EF:D8.
The new definition will now appear in
your device list.
If you have enabled device identification

on the wireless interface, device
definitions will be created automatically.
You can then use MAC addresses to
identify which device a definition refers
to.
518
WiFi
3. Creating a device group

Device Groups and create a new group.
Add the new device to the Members list.
4. Reserving an IP address for the device

and edit the wireless interface.
If the FortiAP is in bridge mode, you will

need to edit the internal interface.
Under DHCP Server, expand
Advanced. Create a new entry in the
MAC Reservation + Access Control
list that reserves an IP address within the
DHCP range for the devices MAC
address.
5. Creating a security policy for wireless traffic

Set Incoming Interface to your wireless
interface, Source Device Type to the
device group, and Outgoing Interface to
the Internet-facing interface.
Ensure that NAT is turned on.
WiFi
519
6. Results
Connect to the wireless network with a device that is a member of the device group. The device should be able
to connect and allow Internet access.
Connection attempts from a device that is not a group member will fail.
Sessions and view the results for now.
Filter the results using the reserved
Source IP (in the example, 10.10.80.20),
to see that it is being used exclusively by
the wireless device.

"bring your own device" in the FortiOS 5.2
Handbook.
520
WiFi
BYOD scheduling
In this example, a school blocks Internet access to mobile devices during class time (9am - 12pm and 1pm - 3pm).
This recipe shows how to use a schedule group and a BYOD device policy to permit mobile device Internet
access before and after class time and during lunch. The school is open from 7am to 6pm.
]In this example a FortiWiFi unit provides the wireless network. The steps are the same if the wireless network is
provided by FortiAP with a FortiGate as a wireless controller.
WiFi
521
1. Creating schedules and a schedule group

Schedules. Create recurring schedules
for
the before class (7-9 am), lunch (12-1
pm), and
after class (3-6 pm) periods.
Select Create New > Schedule Group

and add create the schedule group by
adding the outside of class time
schedules to a schedule group.
WiFi
522
2. Creating a policy to block mobile devices outside of class time

and create a policy that allows Internet
access for mobile devices on the
Student-net wireless network according
to the schedule.
interface, Source Device Type to
Mobile Devices (a default device group
that includes tablets and mobile phones),
Outgoing Interface to the Internetfacing interface, and set Schedule to the
new schedule group.

enable device identification on the
wireless interface.
3. Results
Verify that mobile devices can connect to the Internet outside of class time, when the schedule group is valid.
Forward Traffic to view mobile device
traffic.
523
WiFi
When the time in the schedule is

reached, further surfing cannot continue.
This traffic does not appear in the logs,
as only allowed traffic is logged.

"bring your own device" in the FortiOS 5.2
Handbook.
WiFi
524
In this example, you will make a FortiOS security policy that requires both user and device authentication, so that
known users can only access the network when they are using known devices.
Using a combination of user and device authentication improves security in BYOD environments. Any
authenticated user can connect through wireless, using any wireless device that is included in the device group
specified in the policy. Thus, the BYOD policy can even support a user with multiple devices.
WiFi
525
1. Create users and a user group


Groups.
2. Create devices and a device group

Device Definitions and enter the user's
device information.

Device Groups. Create a device group
and add user's devices to it.
WiFi
526
3. Configure WiFi security

network for WPA-Enterprise
authentication using the employees user
group.

and create a policy to enable traffic from
the WiFi interface to the Internet (in the
example, wan1) and office LAN (in the
example, Internal) interfaces.
Restrict the policy to allow only the
employees user group and device group.
527
WiFi
5. Results
User rgreen can connect to the Internet
using the rgreen tablet that belongs to
the staff devices group.
Policy Monitor to see the security policy
in use.
Attempts to access the Internet fail if any of the following are true:
l
the user does not belong to the employees user group
the device does not belong to the staff devices group

Handbook.
WiFi
528
In this example, you use an external RADIUS server to authenticate your WiFi clients.
In the example, a FortiAuthenticator (v3.00-build0176) is used as a RADIUS server to authenticate users who
belong to the employees user group.
WiFi
529
1. Create the user accounts and user group on the FortiAuthenticator

Management > Local Users and create
a user account.
User Role settings are available after
you click OK.
Create additional user accounts as
needed, one for each employee.
Management > User Groups and
create the local user group "employees"
on the FortiAuthenticator.
Add users who are allowed to use the
WiFi network.
2. Register the FortiGate as a RADIUS client on the FortiAuthenticator

Go to Authentication >RADIUS
Service > Clients and create a user
account.
Enable all of the EAP types.
WiFi
530
3. Configure FortiGate to use the RADIUS server

Go to User & Device > Authentication
> RADIUS Servers and add the
FortiAuthenticator unit as a RADIUS
server.
4. Create the SSID and set up authentication

SSID and define your wireless network.
Set up DHCP for your clients.
Configure WPA2 Enterprise security that

uses the external RADIUS server.
531
WiFi
5. Connect and authorize the FortiAP

and configure a dedicated interface for
the FortiAP.
Connect the FortiAP unit. Go to WiFi

Controller > Managed Access Points
> Managed FortiAPs.
When the FortiAP is listed, select and
authorize it.

FortiAP Profiles and edit the profile. For
each radio:
WiFi
Select your SSID.
532

and add a policy that allows WiFi users
to access the Internet.
Results
Client Monitor to see that clients
connect and authenticate.

Deploying Wireless Networks in the
533
WiFi
In this example, wireless users are redirected to a captive portal web page (no matter what URL they enter) that
requires them to authenticate before they can access the Internet. The portal page can also contain links to local
information such as legal notices, terms of service and so on. This is sometimes called a walled garden.
The web portal page is a script that gathers the users logon credentials and sends back to the FortiGate a POST
message of the format https://<FGT_IP>:1000/fgtauth with data magic=session_
id&username=<username>&password=<password>. (The magic value was provided in the initial FortiGate
request to the web server.) The script used for this example is here.
A RADIUS server provides authentication.
WiFi
534
1. Add the RADIUS server

> RADIUS Servers. Define the
connection to the RADIUS server.

Groups. Define a firewall user group
with the RADIUS server as its only
member.
2. Enable HTTPS authentication

Use the CLI to enable use of HTTPS for
authentication so that user credentials
are communicated securely.
config user setting

set auth-secure-http enabled
end
3. Create the WiFi network

SSID to create the WiFi SSID.
WiFi
535
Enable DHCP for clients.
Configure external captive portal

security.
Do not include "http://" or "https://" in the
captive portal URL.
4. Create a "walled garden"

Addresses and create an address for the
captive portal.
536
WiFi

Create a security policy for
unauthenticated users that allows
access only to the captive portal.
In the CLI, enable bypass of the captive

portal so that the user can make the
initial contact with the external server.
ed
se
endObtain <policy_id> from ID column of the policy list (Policy & Obje
Policy > IPv4).
5. Create the Internet access security policy

Create a policy to allow authenticated
users access to the Internet.

Edit an unused interface, making it
WiFi
537
Dedicated to Extension Device. Connect

the FortiAP to this interface and apply
power. Go to WiFi Controller >
Managed Devices > Managed
FortiAPs. Select and authorize the
FortiAP.
FortiAP Profiles. Edit the default profile
for your FortiAP model. Enable your
SSID for each radio.
Results
The WiFi network's security shows as Open. The device can associate and is assigned an IP address.
538
WiFi
On the first attempt to browse the

Internet, the captive portal screen is
displayed.
(The web server certificate must be
verifiable, or the browser will show
warnings.)
After authentication, the browser can
access Internet destinations.
WiFi
539
Virtual LANs (VLANs) are used to assign wireless users to different networks without requiring the use of multiple
SSIDs. Each users VLAN assignment is stored in the user database of the RADIUS server that authenticates the
users.
This example creates dynamic VLANs for the Techdoc and Marketing departments. The RADIUS server is a
FortiAuthenticator.
WiFi
540
1. Configure the FortiAuthenticator

Service > Clients to register the
FortiGate as a client.
Enter a Secret (a password) and
remember it. It will also be used in the
FortiGate configuration.

local user accounts as needed.
For each user, add these RADIUS
WiFi
541
attributes which specify the VLAN

information to be sent to the FortiGate.
Tunnel-Private-Group-Id specifies the
VLAN ID.
In this example, jsmith is assigned VLAN
100 and twhite is assigned VLAN 200.
2. Add the RADIUS server to the FortiGate configuration

> RADIUS Servers. Select Create
New.
Enter the FortiAuthenticator IP address
and the server secret that you entered on
the FortiAuthenticator.
Optionally, you can click Test
Connectivity. Enter a RADIUS user's ID
and password. The result should be
"Successful".
3. Create an SSID with dynamic VLAN assignment

SSID.
Create a new SSID and set up DHCP
service.
542
WiFi
Select WPA2 Enterprise security and

select your RADIUS server for
authentication.
Set the default VLAN ID to 10. This
VLAN is used when RADIUS doesn't
assign a VLAN.

and use the CLI Console to enable
dynamic VLANs on the SSID.
config wireless-controller vap

edit Dynamic_VLAN
set dynamic-vlan enable
end
4. Create the VLAN interfaces

Create the VLAN interface for default
VLAN-10 and set up DHCP service.
WiFi
543
Create the VLAN interface for

marketing-100 and set up DHCP service.
Create the VLAN interface for techdoc200 and set up DHCP service.
544
WiFi
5. Create security policies

Go to Policy > Policy > IPv4.
Create a policy that allows outbound
traffic from marketing-100 to the Internet.
In Logging Options, enable logging for

all sessions.
Create a policy that allows outbound

traffic from techdoc-200 to the Internet.
For this policy too, in Logging Options
enable logging for all sessions.
WiFi
545

FortiAP Profiles.
Create a new profile for your FortiAP
model and select the new SSID for both
Radio 1 and Radio 2.

Go to System > Network > Interfaces and choose an unused interface. Set Addressing mode to Dedicated
to Extension Device. Connect the FortiAP unit to the this interface and apply power.
Devices > Managed FortiAPs.
Right-click on the FortiAP unit and select
the FortiAP profile that you created.
Right-click on the FortiAP unit again.
Select Authorize.
546
WiFi
Results
The SSID will appear in the list of available wireless networks on the users devices. Both twhite and jsmith can
connect to the SSID with their credentials and access the Internet.
(If a certificate warning message appears, accept the certificate.)
Forward Traffic Log.
Note that traffic for jsmith and twhite
pass through
different policies. The policy IDs
correspond to the marketing-100 and
techdoc-200 policies respectively.
The security policies could be made
different so that Marketing and Techdoc
departments are allowed different
access, but we didn't think that was fair.
WiFi
547
This is an example of wireless single-sign-on (WSSO) with a Fortigate. The WiFi users are teachers and students
at a school. Each user belongs to a user group, either TeacherGroup or StudentGroup. A FortiAuthenticator
performs user authentication and passes the user group name to the FortiGate so that the appropriate security
policy is applied. The student security policy applies a more restrictive web filter.
WiFi
548
1. Register the FortiGate as a RADIUS client on the FortiAuthenticator

Authentication > RADIUS Service >
Clients and create an account. Enter and
remember the Secret (password).
Enable all of the EAP types.
WiFi
549
2. Create user accounts on the FortiAuthenticator

a user account.
User Role settings are available after
you click OK.
3. Create user groups on the FortiAuthenticator

Management > User Groups.
Create and populate TeacherGroup and
StudentGroup.
550
WiFi
Re-edit each group. Add the FortinetGroup-Name RADIUS attribute which

specifies the user group name to be sent
to the FortiGate.
Vendor: Fortinet
Attribute ID: Fortinet-Group-Name
Value: TeacherGroup or StudentGroup,
as appropriate.
4. Configure FortiGate to use the RADIUS server

Authentication > RADIUS Servers.
Select Create New.
Enter the FortiAuthenticator IP address
and the server secret that you entered on
Optionally, you can click Test
Connectivity. Enter a RADIUS users ID
and password. The result should be
Successful.
5. Configure user groups on the FortiGate

Groups. Create TeacherGroup and
StudentGroup. Don't add any members.
WiFi
551
6. Create security policies

Create two WiFi-to-Internet policies. One
has StudentGroup as the Source User
(s), the other specifies TeacherGroup.
The student policy selects a more
restrictive Web Filter.
7. Create an SSID with RADIUS authentication

SSID. Create an SSID and set up DHCP
for clients.
552
WiFi
Configure WPA2-Enterprise
authentication that uses the
FortiAuthenticator as RADIUS server.
8. Add the FortiAP

Dedicate an unused network interface to
FortiAP.
Connect the FortiAP to the dedicated

interface. Go to WiFi Controller >
Managed Devices > Managed
FortiAPs. Wait the the FortiAP to be
listed (refresh as needed). Select and
Authorize the FortiAP.
FortiAP Profiles and open the profile for
your FortiAP model. Add your SSID to
both radios.
WiFi
553
Results
Connect to the WiFi network, authenticate, and browse the Internet. Try this with both student and teacher
accounts.
Firewall. You can verify the User Group
and that the WSSO authentication
method was used.

Policy Monitor. You can verify that the
appropriate security policy was applied.
554
WiFi
In this example, you will use RADIUS Single Sign-On (RSSO) to authenticate wireless users.
Users will be required to enter their credentials, which are stored on a RADIUS server, when connecting to the
wireless network. Once they have been authenticated, the same credentials will also be used by the FortiGate to
allow outbound traffic without requiring additional authentication.
In this example, a FortiAP has already been installed in Tunnel mode. For more information, seeSetting up WiFi
with FortiAP.
WiFi
555
1. Adding a RADIUS server and allowing accounting messages to be accepted

> RADIUS servers and create a new
server connection.
Set the Primary Server IP/Name and
Primary Server Secret. Test the
connection.
Configure additional settings as required.
and edit the interface that communicates
with the RADIUS server.
Enable Listen for RADIUS Accounting
Messages.
2. Creating an RSSO agent

> Single Sign-On and create a new
agent.
Set Type to RADIUS Single Sign-On
Agent and enable both Use RADIUS
Shared Secret and Send RADIUS
Responses.
3. Creating an RSSO user group

Set Type to RADIUS Single Sign-On
(RSSO) and enter the RADIUS
Attribute Value.
WiFi
556
4. Creating a security policy for the RSSO user group

interface, Source User(s) to the RSSO
user group, and Outgoing Interface to
your Internet-facing interface.
5. Configuring the RADIUS server

In this example, a Microsoft Network Policy Server (NPS) is used as the RADIUS server.
Create a remote RADIUS server group.
Set the IP address as the FortiGate unit's
IP.
557
WiFi
Go to Authentication/Accounting.
Deselect Use the same share secret
for authentication and accounting and
enter the same secret that is used by the
RSSO agent.
WiFi
558
6. Configuring the RADIUS client

Create a new RADIUS client and go to
Properties.
Select Enable this RADIUS client. Set
Name and Address to match the
FortiAP and enter the Shared secret.
559
WiFi
Go to the Advanced properties.

Set Vendor name to RADIUS
Standard.
7. Creating a network policy

Create a new network policy.
Select Policy enabled and Grant
access.
WiFi
560
Go to Conditions.
Add Windows Group and select
Corp/Internet_user from the AD.
Go to Constraints.
Select Authentication Methods and add
Microsoft: Protected EAP (PEAP)
under EAP Types.
561
WiFi
Select PEAP from the EAP Types list

and select Edit.
Ensure that a certificate is issued for
PEAP.
Go to Settings.
Select Standard and remove all
attributes that are listed.
WiFi
562
8. Creating a connection request policy

Create a new connection request policy.
Select Policy enabled.
Go to Conditions.
Add Client IPv4 Address and enter the
IP of the FortiAP.
563
WiFi
Go to Settings.
Select RADIUS Attributes and add the
same class attribute used by the RSSO
user group (in the example, tac).
Select Accounting and select Forward

accounting requests to the remote
RADIUS server group. Select the
RADIUS server group from the list.
9. Results
WiFi
564
Users in the RSSO group will now be able to use their credentials to connect to the wireless network. They will
then be able to access the Internet without having to authenticate again.

Firewall to verify that users are able to
connect to the FortiGate using RSSO.
For further reading, check out SSO using

RADIUS accounting records in the FortiOS
5.2 Handbook.
565
WiFi
Social WiFi Captive Portal with FortiAuthenticator

(Facebook)
WiFi authentication using social media provides access control without having to manually create guest accounts.
This recipe involves configuring an API for Facebook accounts, setting up a social portal RADIUS service on the
FortiAuthenticator, and configuring the FortiGate for Captive Portal access.
This recipe is similar to theCaptive portal WiFi access control, but involves external security mode configuration,
RADIUS authentication, and does not include FortiAP registration instructions.
Note that some CLI usage is required when configuring the FortiGate.
The FortiAuthenticator has been given an example fully qualified domain name (FQDN)
fortiauthenticator.example.com.
WiFi
566
1. Configuring the Facebook developer account API

Open a browser and log in to your
Facebook account.
In the URL field enter the following:
https://developers.facebook.com/products/login/
Select My Apps and select Register as Developer.
Confirm your Facebook password to
continue.
Select that you have read and agree to
the Facebook Platform and Facebook
Privacy policies, and select Next to
continue.
WiFi
567
Enter your phone number and select to

have your confirmation code sent to you
via text (you may also choose to verify
via phone call).
Once received, enter the code and select
Register to continue. You will now be
registered as a Facebook developer.
Next, select the Website platform to add

a new app.
Enter a name for the website, and select
Create New Facebook App ID.
568
WiFi
Select Communication from the

dropdown Category menu, and select
Create App ID.
Scroll down to the bottom of the page and
enter the site's URL, then select Next.
Scroll back up to the top of the page, and
select Skip Quick Start.
To confirm the configuration, go to

Settings. From here you can see your
App ID, App Secret, Display Name,
and Site URL.
Take note of the App ID and App Secret
as they are required when configuring the
Captive Portal on the FortiAuthenticator.
WiFi
569
Next, go to Status & Review and enable

the application the account needs to be
made "live" before WiFi users can
successfully authenticate through
Facebook.
The App ID and App Secret can be accessed at any time on the LinkedIn developer account, but it may be a
good idea to copy them to a secure location.
570
WiFi
2. Configuring the social portal RADIUS service on FortiAuthenticator

User Groups, and create a Social_
Users user group.
Users that log into LinkedIn will be
placed in this group once it is added to
the Captive Portal General Settings.

Service > Clients, and create a new
RADIUS client.
example, 172.20.121.56).
Enable the Social portal captive portal.
Enter the pre-shared Secret and set the Authentication method. The FortiGate will use this secret key in its
RADIUS configuration.
Add the Social_Users user group to the Realms group filter as shown.
WiFi
571
Next go to Authentication > Captive

Portal > General and enable Social
Portal.
Configure the account expiry time (in the
example it is set to 1 hour).
Set Place registered users into a
group to Social_Users.
Enable the Facebook login option and
add your Facebook key and Facebook
secret.

its IP and pre-shared secret.
Use the Test Connectivity option with
valid credentials to test the connection.

user group called social_users.
table.
572
WiFi
4. Configuring the FortiGate WiFi settings

Go to WiFi & Switch Controller > WiFi
Network > SSID and select the SSID
interface.
Under WiFi Settings, set the Security
Mode to Captive Portal.
For the Authentication Portal, select External, and enter the FQDN of the FortiAuthenticator, followed by
/social_login/.
For this recipe, it is set to:
https://fortiauthenticator.example.com/social_login/
Set User Groups to the social_users group.
5. Configuring the FortiGate to allow access to Facebook

On the FortiGate, configure firewall addresses to allow users to access the Facebook login page.
The following step can be performed in the GUI, but may take considerably longer than using the CLI. You can
also copy and paste the commands below into the CLI console.
Go to System > Dashboard and enter the CLI Console. Enter the following, which creates the firewall
addresses and adds them to a firewall address group called Facebook_Auth:
config firewall address
edit "FB0"
set subnet 5.178.32.0 255.255.240.0
next
edit "FB1"
set subnet 195.27.154.0 255.255.255.0
next
edit "FB2"
set subnet 80.150.154.0 255.255.255.0
edit "FB3"
set subnet 77.67.96.0 255.255.252.0
next
edit "FB4"
set subnet 212.119.27.0 255.255.255.128
next
WiFi
573
edit "FB5"
set subnet 2.16.0.0 255.248.0.0
next
edit "FB6"
set subnet 66.171.231.0 255.255.255.0
next
edit "FB7"
set subnet 31.13.24.0 255.255.248.0
next
edit "FB8"
set subnet 31.13.64.0 255.255.192.0
next
edit "FB9"
set subnet 23.67.246.0 255.255.255.0
next
edit "akamai-subnet-23.74.8"
set subnet 23.74.8.0 255.255.255.0
next
edit "akamai-subnet-23.74.9"
set subnet 23.74.9.0 255.255.255.0
next edit "akamaihd.net"
set type fqdn
set fqdn "akamaihd.net"
next
edit "channel-proxy-06-frc1.facebook.com"
set type fqdn
set fqdn "channel-proxy-06-frc1.facebook.com"
next
edit "code.jquery.com"
set type fqdn
set fqdn "code.jquery.com"
next
edit "connect.facebook.com"
set type fqdn
set fqdn "connect.facebook.com"
next
edit "fbcdn-photos-c-a.akamaihd.net"
set type fqdn
set fqdn "fbcdn-photos-c-a.akamaihd.net"
next
edit "fbcdn-profile-a.akamaihd.net"
set type fqdn
set fqdn "fbcdn-profile-a.akamaihd.net"
next edit "fbexternal-a.akamaihd.net"
set type fqdn
set fqdn "fbexternal-a.akamaihd.net"
next
edit "fbstatic-a.akamaihd.net"
set type fqdn
set fqdn "fbstatic-a.akamaihd.net"
574
WiFi
next
edit "m.facebook.com"
set type fqdn
set fqdn "m.facebook.com"
next
edit "ogp.me"
set type fqdn
set fqdn "ogp.me" next
edit "s-static.ak.facebook.com"
set type fqdn
set fqdn "s-static.ak.facebook.com"
next
edit "static.ak.facebook.com"
set type fqdn
set fqdn "static.ak.facebook.com"
next
edit "static.ak.fbcdn.com"
set type fqdn
set fqdn "static.ak.fbcdn.com"
next
edit "web_ext_addr_SocialWiFi"
set type fqdn
set fqdn "web_ext_addr_SocialWiFi"
next
edit "www.facebook.com"
set type fqdn
set fqdn "www.facebook.com"
next
end
config firewall addrgrp
edit "Facebook_Auth"
set member "FB0" "FB1" "FB2" "FB3" "FB4" "FB5" "FB6" "FB7" "FB8" "FB9"
"akamaisubnet-23.74.8" "akamai-subnet-23.74.9" "akamaihd.net"
"channel-proxy-06-frc1.facebook.com" "code.jquery.com"
"connect.facebook.com" "fbcdn-photos-ca.akamaihd.net"
"fbcdn-profile-a.akamaihd.net" "fbexternal-a.akamaihd.net"
"fbstatic-a.akamaihd.net" "m.facebook.com" "ogp.me"
"s-static.ak.facebook.com" "static.ak.facebook.com"
"static.ak.fbcdn.com" "web_ext_addr_SocialWiFi"
"www.facebook.com" "FortiAuthenticator"
next
end
WiFi
575

and create a policy for Facebook
authentication traffic.
Set Incoming Interface to the WiFi
SSID interface and set Source Address
to all.
Address to Facebook_Auth.
Configure Security Profiles accordingly.
Go to System > Dashboard and enter the CLI Console. Add the following to exempt the Facebook
authentication traffic policy from the captive portal:
edit <policy_id>
set captive-portal-exempt enable
next
end
This command allows access to the external Captive Portal.
6. Configuring the FortiGate to allow access to FortiAuthenticator

> Objects > Addresses and add the
FortiAuthenticator firewall object.
For Subnet/IP Range enter the IP
address of the FortiAuthenticator.
576
WiFi

and create the FortiAuthenticator access
policy.
to all.
Address to FortiAuthenticator.
Add the following to exempt the FortiAuthenticator access policy from the Captive Portal:
edit <policy_id>
next
end
WiFi
577
7. Results
Connect to the WiFi and attempt to
browse the Internet. You will be
redirected to the Captive Portal splash
page.
Select Facebook and you should be
redirected to the Facebook login page.
578
WiFi
Enter valid Facebook credentials and you

will be redirected to the URL initially
requested.
You can now browse freely until the
social login account expires, as
configured on the FortiAuthenticator
under Authentication > Captive Portal
> General.
To view the authenticated user added on

FortiAuthenticator, go to Authentication
> User Management > Social Login
Users.
You can configure Captive Portal to use other social WiFi logins:
WiFi
579

(Twitter)
This recipe involves configuring an API for Twitter accounts, setting up a social portal RADIUS service on the
Note that some minimal CLI usage is required when configuring the FortiGate.
A recipe of this video is available here.
WiFi
580
1. Configuring the Twitter developer account API

Open a browser and log in to your Twitter
account. In the URL field enter the
following:
https://apps.twitter.com/
Select Create New App.
Enter a Name, Description, and Website

for the application.
In the Callback URL field, enter the following:

https://fortiauthenticator.example.com/social/complete/twitter/
Note that the FortiAuthenticator needs to be able to access the Internet.
Accept the Developer Agreement and
select Create your Twitter application.
WiFi
581
Go to Keys and Access Tokens to view

your Consumer Key and Consumer
Secret.
Take note of the Consumer Key and
Consumer Secret as they are required
when configuring the Captive Portal on the
FortiAuthenticator.
The Consumer Key and Consumer Secret can be accessed at any time on the Twitter developer account, but
it may be a good idea to copy them to a secure location.

User Groups, and create a Social_Users
user group.
Users that log into Twitter will be placed in
this group once it is added to the Captive
Portal General Settings.
582
WiFi
Go to Authentication > RADIUS Service

> Clients, and create a new RADIUS
client.
example, 172.20.121.56).
Portal.
Set Place registered users into a group
to Social_Users.
Enable the Twitter login option and add
your Twitter Consumer Key and
Consumer Secret.
WiFi
583

Next, go to User & Device > User > User

Groups and create a RADIUS user group
called social_users.
table.

interface.
/social_login/.
5. Configuring the FortiGate to allow access to Twitter

On the FortiGate, configure firewall addresses to allow users to access the Twitter login page.
584
WiFi
addresses and adds them to a firewall address group called Twitter_Auth:
edit "api.twitter.com"
set type fqdn
set fqdn "api.twitter.com"
next
edit "abs.twimg.com"
set type fqdn
set fqdn "abs.twimg.com"
next
edit "abs-0.twimg.com"
set type fqdn
set fqdn "abs-0.twimg.com"
next
end
config firewall addgrp
edit "Twitter_Auth"
set member "api.twitter.com" "abs.twimg.com" "abs-0.twimg.com"
next
end
and create a policy for Twitter
Set Incoming Interface to the WiFi SSID
Address to Twitter_Auth.
Go to System > Dashboard and enter the CLI Console. Add the following to exempt the Twitter authentication
traffic policy from the captive portal:
edit <policy_id>
next
end
WiFi
585

On the FortiGate, go to Policy & Objects >
Objects > Addresses and add the

policy.
edit <policy_id>
next
end
586
WiFi
7. Results
Connect to the WiFi and attempt to browse
the Internet. You will be redirected to the
Captive Portal splash page.
Select Twitter and you should be
redirected to the Twitter login page.
WiFi
587
Enter valid Twitter credentials and you will

be redirected to the URL initially
requested.
You can now browse freely until the social
login account expires, as configured on the
FortiAuthenticator under Authentication >
Captive Portal > General.

FortiAuthenticator, go to Authentication >
User Management > Social Login
Users.
588
WiFi

(Google+)
This recipe involves configuring an API for Google+ accounts, setting up a social portal RADIUS service on the
WiFi
589
1. Configuring the Google+ developer account API

Open a browser and log in to your Google
account. In the URL field enter the
following:
https://console.developers.google.com
Under Select a project, select Create a
project.
Enter a Project name, and accept the
Terms of Service before continuing.
Go to APIs & auth > Credentials, and

select OAuth 2.0 client ID from the Add
credentials dropdown.
WiFi
590
When prompted, select Configure

consent screen. Enter an Email address
and Product name. You must now create
the client ID.
Set Application type to Web application. Under Authorized JavaScript origins, enter the FortiAuthenticator
FQDN.
Under Authorized redirect URIs, enter the following:
https://fortiauthenticator.example.com/social/complete/google-oauth2/
591
WiFi
Upon creating the client ID, a window

will appear with your client ID and
client secret.
Take note of the c lient ID and client
secret as they are required when
configuring the Captive Portal on the
FortiAuthenticator.
The client ID and client secret can be accessed at any time on the Google developer account, but it may be a

user group.
Users that log into Google will be placed in
WiFi
592

client.
example, 172.20.121.56).

Portal.
to Social_Users.
Enable the Google login option and add
your Google key and Google secret.
593
WiFi


table.

interface.
/social_login/.
WiFi
594
5. Configuring the FortiGate to allow access to Google

On the FortiGate, configure firewall addresses to allow users to access the Google login page.
addresses and adds them to a firewall address group called Google_Auth:
edit "www.googleapis.com"
set type fqdn
set fqdn "www.googleapis.com"
next
edit "accounts.google.com"
set type fqdn
set fqdn "accounts.google.com"
next
edit "ssl.gstatic.com"
set type fqdn
set fqdn "ssl.gstatic.com"
next
edit "fonts.gstatic.com"
set type fqdn
set fqdn "fonts.gstatic.com"
next
edit "www.gstatic.com"
set type fqdn
set fqdn "www.gstatic.com"
next
edit "Google_13"
set subnet 216.58.192.0 255.255.224.0
next
end
edit "Google_Auth"
set member "ssl.gstatic.com" "accounts.google.com" "www.googleapis.com"
"fonts.gstatic.com" "www.gstatic.com" "Google_13"
next
end
595
WiFi

and create a policy for Google
Address to Google_Auth.
Go to System > Dashboard and enter the CLI Console. Add the following to exempt the Google authentication
traffic policy from the captive portal:
edit <policy_id>
next
end

WiFi
596

policy.
edit <policy_id>
next
end
597
WiFi
7. Results
browse the Internet. You will be redirected
to the Captive Portal splash page.
Select Google and you should be
redirected to the Google login page.
WiFi
598
Enter valid Google credentials and you will

be redirected to the URL initially
requested.

Users.
599
WiFi

(LinkedIn)
This recipe involves configuring an API for LinkedIn accounts, setting up a social portal RADIUS service on the
This recipe is similar to theCaptive portal WiFi access control recipe, but involves external security mode
configuration, RADIUS authentication, and does not include FortiAP registration instructions.
WiFi
600
1. Configuring the LinkedIn developer account API

Open a browser and log in to your LinkedIn
account.
In the URL field enter the following:
https://developer.linkedin.com/documents/authentication
Select Create Application.
Enter information in the required fields.
Unlike the other social applications,
LinkedIn requires an Application Logo URL.
Select that you have read and agree to the
LinkedIn API Terms if Use and select
Submit.
WiFi
601
602
WiFi
The next screen shows your Client ID and

Client secret.
Take note of the Client ID and Client
secret as they are required when
configuring the Captive Portal on the
FortiAuthenticator.
Under Authorized Redirect URLs, enter the following:

https://fortiauthenticator.example.com/social/complete/linkedin-oauth2/
The client ID and client secret can be accessed at any time on the LinkedIn developer account, but it may be a
WiFi
603

user group.
Users that log into LinkedIn will be placed
in this group once it is added to the Captive

client.
example, 172.20.121.56).
604
WiFi

Portal.
to Social_Users.
Enable the LinkedIn login option and add
your LinkedIn key and LinkedIn secret.

WiFi
605

table.

interface.
/social_login/.
606
WiFi
5. Configuring the FortiGate to allow access to LinkedIn

On the FortiGate, configure firewall addresses to allow users to access the LinkedIn login page.
addresses and adds them to a firewall address group called LinkedIn_Auth:
edit "www.linkedin.com"
set type fqdn
set fqdn "www.linkedin.com"
next
edit "api.linkedin.com"
set type fqdn
set fqdn "api.linkedin.com"
next edit "static.licdn.com"
set type
fqdn
set fqdn "static.licdn.com"
next
edit "help.linkedin.com"
set type fqdn
set fqdn "help.linkedin.com"
next
edit "www.fortinet.com"
set type fqdn
set fqdn "www.fortinet.com"
next
end
edit "LinkedIn_Auth"
set member "api.linkedin.com" "www.linkedin.com" "help.linkedin.com"
"www.fortinet.com" "static.licdn.com"
next
end
WiFi
607

and create a policy for LinkedIn
Address to LinkedIn_Auth.
Go to System > Dashboard and enter the CLI Console. Add the following to exempt the LinkedIn
authentication traffic policy from the captive portal:
edit <policy_id>
next
end

On the FortiGate, go to Policy & Objects >
Objects > Addresses and add the
For Subnet/IP Range enter the IP address
of the FortiAuthenticator.
608
WiFi

policy.
edit <policy_id>
next
end
WiFi
609
7. Results
Connect to the WiFi and attempt to browse
the Internet. You will be redirected to the
Captive Portal splash page.
Select LinkedIn and you should be
redirected to the LinkedIn login page.
610
WiFi
Enter valid LinkedIn credentials and you

will be redirected to the URL initially
requested.

Users.
WiFi
611

(Form-based)
WiFi authentication using a forms-based portal provides access control without having to manually create guest
accounts.
This recipe involves setting up a social portal RADIUS service on the FortiAuthenticator, and configuring the
FortiGate for Captive Portal access, allowing users to log in to the WiFi network using either SMS or e-mail selfregistration.
This recipe is similar to the Captive portal WiFi access control recipe, but involves RADIUS authentication, and
does not include FortiAP registration instructions.
WiFi
612

Management > User Groups, and
create a Social_Users user group.
Users that log in through the forms-based
authentication method will be placed in

Service > Clients, and create a new
RADIUS client.
example, 172.20.121.56).
WiFi
613

Portal.
Set Place registered users into a
group to Social_Users.
Enable the SMS self-registration and email self-registration login options. Be
sure SMS gateway is set to Use
default.

614
WiFi

user group called social_users.
table.

interface.
/social_login/.

WiFi
615

policy.
to all.
edit <policy_id>
next
end
616
WiFi
5. Results
browse the Internet. You will be
redirected to the Captive Portal splash
page.
Select Form-based and you should be
redirected to the Form-based
authentication login page.
WiFi
617
Select your preferred Verification

method, enter valid credentials, and
select Submit. You will be redirected to
the URL initially requested.
You can now browse freely until the
social login account expires, as
configured on the FortiAuthenticator
under Authentication > Captive Portal
> General.

FortiAuthenticator, go to Authentication
> User Management > Social Login
Users.
618
WiFi
Expert
FortiGate units can be deployed in many ways to meet a wide range of advanced requirements. This section
contains recipes and articles (which discuss topics in greater depth than a recipe) about a variety of these
configurations.
Recipes and articles in this section are intended for users with a high degree of background knowledge about
FortiGates and computer networking, such as users who have completed Fortinets Network Security Expert
(NSE) 4 level of training.
High Availability
l
SLBC Active-Passive setup with two FortiController-5103Bs
SLBC Active-Passive with two FortiController-5103Bs and two chassis
SLBC Active-Passive with four FortiController-5103Bs and two chassis
IPsec VPN
l
Authentication
l
Single Sign-on using LDAPand FSSOagent in advanced mode
Single Sign-On using FSSO agent in advanced mode and FortiAuthenticator
SSOusing a FortiGate, FortiAuthenticator, and DCPolling
Articles
l
Expert
619
This recipe describes how to enhance the reliability of a network protected by a FortiGate unit by adding a second
FortiGate unit and setting up a FortiGate Clustering Protocol (FGCP) High Availability cluster.
The FortiGate already on the network will be configured to become the primary unit by increasing its device priority
and enabling override. The new FortiGate will be prepared by setting it to factory defaults to wipe any configuration
changes. Then it will be licensed, configured for HA, and then connected to the FortiGate already on the network.
The new FortiGate becomes the backup unit and its configuration is overwritten by the primary unit.
The recipe contains instructions for both the GUI and the CLI, with some parts of the configuration requiring use of
the CLI.For a simplified HA recipe that only requires use of the GUI, see High Availability with two FortiGates.
Before you start the FortiGates should be running the same FortiOS firmware version and interfaces should not be
configured to get their addresses from DHCP or PPPoE.
Expert
620
1. Configuring the primary FortiGate

If the FortiGates in the cluster will be running FortiOS Carrier, apply the FortiOS Carrier license before
configuring the cluster (and before applying other licenses). Applying the FortiOS Carrier license sets the
configuration to factory defaults, requiring you to repeat steps performed before applying the license.
to System > Dashboard > Status and
locate the System Information widget.
it as the primary FortiGate.
You can also enter this CLI command:

set hostname Primary_FortiGate
end
If you have not already done so, register

the primary FortiGate and apply licenses
to it before setting up the cluster. This
includes FortiCloud activation,
FortiClient and FortiToken licensing,
and entering a license key if you
purchased more than 10 Virtual
Domains (VDOMs). You can also install
any third-party certificates on the primary
FortiGate before forming the cluster.
Once the cluster is formed third-party
certificates are synchronized to the
backup FortiGate.
Enter this CLI command to set the HA
mode to active-passive, set a group
name and password, increase the device
priority to a higher value (for example,
250) and enable override.
Enabling override and increasing the
device priority means this unit should
always become the primary unit.
config system ha
set mode a-p
set group-name My-HA-Cluster
set password
set priority 250
set override enable
set hbdev ha1 50 ha2 50
end
This command also selects ha1 and ha2

to be the heartbeat interfaces and sets
Expert
621
their priorities to 50.

You can also use the GUI to configure
most of these settings.
Override can only be enabled from the

CLI.
config system ha
set override enable
end
The FortiGate unit negotiates to establish an HA cluster. When you select OK you may temporarily lose
connectivity with the FortiGate unit as FGCP negotiation takes place and the MAC addresses of the FortiGate
unit are changed to HA virtual MAC addresses. These virtual MAC addresses are used for failover. The actual
virtual MAC address assigned to each FortiGate interface depends on the HA group ID. Since this example
does not involved changing the HA group ID, the FortiGate unit's interfaces will have the following MAC
622
Expert
addresses: 00:09:0f:09:00:00, 00:09:0f:09:00:01, 00:09:0f:09:00:02 and so on.

To reconnect sooner, you can update the ARP table of your management PC by deleting the ARP table entry for
the FortiGate unit (or just deleting all arp table entries). You can usually delete the arp table from a command
prompt using a command similar to arp -d.
To confirm these MAC address changes, you can use the get hardware nic (or diagnose hardware
deviceinfo nic) command to view the virtual MAC address of any FortiGate unit interface. Depending on
the FortiGate model, the output from this command could include lines similar to the following:
Current_HWaddr: 00:09:0f:09:00:00
Permanent_HWaddr 02:09:0f:78:18:c9
2. Configuring the backup FortiGate

Enter this command to reset the new FortiGate to factory default settings.
execute factoryreset
You can skip this step if the new FortiGate is fresh from the factory. But if its configuration has been changed at
all it is recommended to set it back to factory defaults to reduce the chance of synchronization problems.
Change the firmware running on the new FortiGate to be the same version as is running on the primary unit.
Register the backup FortiGate and apply
licenses to it before setting up the
cluster. This includes FortiCloud
activation, FortiClient and FortiToken
licensing, and entering a license key if
you purchased more than 10 Virtual
Domains (VDOMs).

and change the unit's Host Name to
identify it as the backup FortiGate.
Expert

set hostname Backup_FortiGate
end
623
Duplicate the primary unit HA settings,

except set the device priority to a lower
value and do not enable override.
You can configure all of these settings
from the GUI.
624
config system ha
set mode a-p
set group-name My-HA-Cluster
set password
set priority 50
set hbdev ha1 50 ha2 50
end
Expert
3. Connecting the cluster

Connect the HA cluster as shown in the initial diagram. Making these connections will disrupt network traffic as
you disconnect and re-connect cables.
When connected the primary and backup FortiGates find each other and negotiate to form an HA cluster. The
Primary unit synchronizes its configuration with the backup FortiGate. Forming the cluster happens
automatically with minimal or no disruption to network traffic.
4. Checking cluster operation and disabling override

Check the cluster synchronization status to make sure the primary and backup units have the same
configuration. Log into the primary unit CLI and enter this command:
diag sys ha cluster-csum
The command output lists all members' checksums. If both cluster units have identical checksums you can be
sure that their configurations are synchronized. If the checksums are different wait a short while and enter the
command again. Repeat until the checksums are identical. It may take a while for some parts of the
configuration to be synchronized. If the checksums never become identical contact Fortinet support to help
troubleshoot the problem.
When the checksums are identical, disable override on the primary unit (recommended).
config system ha
set override disable
end
The HA cluster dynamically responds to network conditions. If you keep override enabled the same FortiGate
will always be the primary FortiGate. Because of this, however; the cluster may negotiate more often potentially
disrupting traffic.
If you disable override it is more likely that the new FortiGate unit could become the primary unit. Disabling
override is recommended unless its important that the same FortiGate remains the primary unit.
Expert
625
Connect to the primary FortiGate GUI

and go to System > Config > HA to view
the cluster information.
Select View HA Statistics for more

information on how the cluster is
operating and processing traffic.
5. Results
Normally, traffic should now be flowing through the primary FortiGate. However, if the primary FortiGate is
unavailable, traffic should failover and the backup FortiGate will be used. Failover will also cause the primary
and backup FortiGates to reverse roles, even when both FortiGates are available again.
To test this, ping the IP address 8.8.8.8
using a PC on the internal network. After
a moment, power off the primary
FortiGate.
If you are using port monitoring, you can

also unplug the primary FortiGate's
Internet-facing interface to test failover.
You will see a momentary pause in the
Ping results, until traffic diverts to the
backup FortiGate, allowing the Ping
626
Expert
traffic to continue.

5.2 Handbook.
Expert
627
The following recipe provides useful instructions for customers with multi-site architecture and redundant
firewalls. It is intended for those customers that want to reduce the number of on-site appliances while increasing
network security and decreasing Total Cost of Ownership, where the goal is simple, cost-effective reliability.
FortiOS 5.2 introduced many new features that we will use in this configuration, which is therefore not possible on
FortiOS 5.0.x or earlier. The recipe is performed with the FortiGate 1xxD/2xxD series.
By following the recipe, you will be able to provide your small-site customers with simple, yet secure infrastructure
that perfectly matches the UTM approach, where we want to centralize as many security features as possible on
a single device or cluster.
Expert
628
The recipe provides task-oriented instructions for administrators to fully complete the installation. It is divided into
the following sections:
1. Scenario: This section section explains the problems that this new network topology solves, including the
cases in which the topology should be used.
2. Topology: This section includes diagrams of the new topology. It also lists key advantages to this kind of
architecture and explains why it solves the problems previously identified in The Scenario.
3. Configuration: This section provides step-by-step instructions for configuring the FortiGates within the new
topology.
629
Expert
Scenario
In the standard scenario, we assume the following topology as the starting point:
Multi-site customers that want to avoid any Single Point of Failure in their remote networks often use this kind of
topology. These customers require two FortiGates in Active/Passive mode and therefore two switches on the
LAN side to transfer Ethernet payloads to the active FortiGate. There are a few downsides to this approach:
l
Four appliances need to be managed and supervised.
Administrators must know how to work with the Firewall OS and with the Switch OS.
If one switch fails, the workstations connected wont be able to reach the Internet.
Most of the firewall ports are not used.
Expert
630
Topology
In this section, we look at the target topology and the scenarios for FortiGate failover. At the end of the section, we
discuss the key advantages of adopting the target topology.
2.1 The Target Topology
In this new topology, we wont be using additional switches. Instead, we will be using the FortiGates Integrated
Switch Fabric (ISF) solution on both master and slave firewalls.
Note that the target topology uses a FortiGate 2xxD, which has 40 ports. In your configuration, ensure that each
FortiGate has enough ports to handle all of the computers in the event of a failover, or switches will still need to be
involved.
Expert
631
The administrator will have to configure a trunk link between the two FortiGate physical switches to expand
subnets and VLANs from one firewall to the other.
In a FortiGate cluster using FGCP, the slave firewalls ISF can still be used to send traffic destined for the active
member across the trunk link.
A representation of the traffic flow appears below:
2.2 FortiGate Failover

Case 1: Link failure
The diagram below represents traffic flow in the event of a failover in the following cases:
632
Expert
The monitored WAN port, on what was originally the Master FortiGate, fails.
The link between the router and the original Master FortiGate fails.
Case 2: FortiGate global failure

If the master were to completely fail (including the ISF), the administrator would have to plug the LANsegments
into the remaining firewall, just as if one switch were to fail in our standard topology.
Expert
633
2.3 Key Advantages

This new topology offers a few key advantages:
634
Only two devices are required, where four are required in the standard topology.
It is easier for the administrator to manage security and switching on a single device.
The use of FortiManager simplifies central management.
There is only one cluster to supervise.
Expert
Configuration
In this section, we reproduce the following network topology. Notice how the router has a switch interface.If your
router does not have a switch interface, you will have to add an extra switch (noted in gray below), and in the event
of a firewall crash, you will have to power cycle the router.
As we will be changing the configuration of the hardware switch, we strongly recommend that you use the
management port to follow the steps below.
By default, the FortiGate management IP address is 192.168.1.99/24.
Expert
635
1. Configuring the hardware switch

By default on a FortiGate 1xxD/2xxD, the unit is in Interface mode and all of the internal ports are attached to a
hardware switch named lan. In this example, we need to use ports 39 and 40 for Trunk and HA respectively.
The first step is to remove ports 39 and 40 from the Hardware Switch lan. Begin by editing the lan interface.
If the unit is in Switch mode, it will have to be reconfigured into Interface mode. For more information, see
Choosing your FortiGate's switch mode.
and double-click lan in the interface list.
Remove the last two ports in the list, in

this case port39 and port40.
Then configure the IP/Network Mask
with the following address:
192.168.100.1/255.255.255.0
When you are done, accept the change.
The interface list should now look like

this:
For the trunk port to work properly, we

need to configure a vlan ID on the Virtual
Switch. This can only be done in the CLI.
636
FGT1 # config system global

FGT1 (global) # set virtual-switch-vlan enable
FGT1 (global) # end
FGT1 # show system global
Expert
First we need to enable this feature

globally. Use the commands shown
here:
Next, edit the Virtual Switch and set the

vlan number:

set fgd-alert-subscription advisory latest-threat
set hostname FGT1
set internal-switch-mode interface
set optimize antivirus
set timezone 04
set virtual-switch-vlan enable
end
FGT1 # config system virtual-switch
FGT1 (virtual-switch) # edit lan
FGT1 (lan) # set vlan 100
FGT1 (lan) # end
You should now be able to see VLAN

Switch in the interface list.
2. Configuring the trunk port

The trunk port will be used to allow traffic
to flow between the Virtual Switch of
each FortiGate.
Configuring the trunk port is only possible
in the CLI:
FGT1 # config system interface

FGT1 (interface) # edit port39
FGT1 (port39) # set trunk enable
FGT1 (port39) # end
FGT1 # show system interface port39
edit port39
set [glossary_exclude]vdom[/glossary_exclude] root
set type physical
set trunk enable
set [glossary_exclude]snmp[/glossary_exclude]-index 10
next
end
You should now be able to see the trunk

port in the interface list.
Expert
637
3. Configuring HA
We will now configure High Availability. Port 40 will be used for HeartBeat/Sync communications between
cluster members. Port Wan1 will be monitored.
Go to System > Config > HA and
configure High Availability as shown:
638
Expert
4. Configuring WAN1 IP routing

and edit wan1 as shown.

and create a new route as shown:
Expert
639
5. Configuring your firewall policies

Go to Policy & Objects > Policy > IPv4 and configure firewall policies as desired.
6. Replicate the entire configuration on the second device

Once the first FortiGate is configured, the
easiest way to configure the second one
is to backup the configuration file of the
first FortiGate and restore it on the
second.
You can change the hostname and HA
priority lines directly in the configuration
file prior to restoring it on the second
FortiGate.
Do not use a text editor, like Notepad or

Word, to do this editing. Instead, use a
code editor, like Notepad++ or
TextWrangler, that wont add unintended
content to the file.
and select Backup next to System
Configuration in the System
Information widget.
For further reading, check out High

Availability in the FortiOS 5.2 Handbook.
640
Expert
This example describes the basics of setting up a Session-aware Load Balancing Cluster (SLBC) that consists of
one FortiController-5103B, installed in chassis slot 1, and three FortiGate-5001C workers, installed in chassis
slots 3, 4, and 5. This SLBC configuration can have up to eight 10 Gbit network connections.
For more information about SLBC go here.
Expert
641
1. Hardware setup
Install a FortiGate-5000 series chassis and connect it to power. Install the FortiController in slot 1. Install the
workers in slots 3, 4, and 5. Power on the chassis.
Check the chassis, FortiController, and FortiGate LEDs to verify that all components are operating normally. (To
check normal operation LED status see the FortiGate-5000 series documents available here.)
Check the FortiSwitch-ATCA release notes and install the latest supported firmware on the FortiController and
on the workers. Get FortiController firmware from the Fortinet Support site. Select the FortiSwitch-ATCA
product.
2. Configuring the FortiController

Connect to the FortiController GUI (using HTTPS) or CLI (using SSH) with the default IP address
(http://192.168.1.99) or connect to the FortiController CLI through the console port (Bits per second: 9600, Data
bits: 8, Parity: None, Stop bits: 1, Flow control: None). Login using the admin administrator account and no
password.
Add a password for the admin
administrator account. From the GUI use
the Administrators widget or from the
CLI enter this command.
config admin user

edit admin
set password <password>
end
Change the FortiController mgmt

interface IP address. From the GUI use
the Management Port widget or from
the CLI enter this command.

edit mgmt
set ip 172.20.120.151/24
end
If you need to add a default route for the

management IP address, enter this
command.
config route static

edit route 1
set gateway 172.20.120.2
end
Set the chassis type that you are using.
Expert

set chassis-type fortigate-5140
end
642
Go to Load Balance > Config to add the

workers to the cluster by selecting Edit
and moving the slots that contain
workers to the Members list.
The Config page shows the slots in
which the cluster expects to find
workers. Since the workers have not
been configured yet their status is Down.
Configure the External Management
IP/Netmask. Once you have connected
workers to the cluster, you can use this
IP address to manage and configure
them.
You can also enter the following CLI
command to add slots 3, 4, and 5 to the
cluster:
config load-balance setting

config slots
edit 3
next
edit 4
next
edit 5
end
end
You can also enter the following CLI

command to configure the external
management IP/Netmask and
management access to this address:

endset base-mgmt-external-ip 172.20.120.100 255.255.255.0
endset base-mgmt-allowaccess https ssh ping
end
3. Adding the workers

Enter this command to reset the workers
to factory default settings.
If the workers are going to run FortiOS

Carrier, add the FortiOS Carrier license
instead. This will reset the worker to
factory default settings.
643
Expert
Register and apply licenses to each

worker before adding the workers to the
SLBC. This includes FortiCloud
10 Virtual Domains. You can also install
worker before forming the cluster. Once
the cluster is formed, third-party
certificates are synchronized to all of the
workers.
Log into the CLI of each worker and enter
this CLI command to set the worker to
operate in FortiController mode.
config system elbc

set mode forticontroller
end
The worker restarts and joins the cluster.

On the FortiController GUI go to Load
Balance > Status. As the workers
restart they should appear in their
appropriate slots.
The worker in the lowest slot number
usually becomes the primary unit.
4. Results
You can now manage the workers in the same way as you would manage a standalone FortiGate. You can
connect to the worker GUI or CLI using the External Management IP. If you had configured the worker mgmt1
or mgmt2 interfaces you can also connect to one of these addresses to manage the cluster.
To operate the cluster, connect networks to the FortiController front panel interfaces and connect to a worker
GUI or CLI to configure the workers to process the traffic they receive. When you connect to the External
Management IP you connect to the primary worker. When you make configuration changes they are
Expert
644
synchronized to all workers in the cluster.

By default on the workers, all FortiController front panel interfaces are in the root VDOM. You can configure the
root VDOM or create additional VDOMs and move interfaces into them.
For example, you could connect the
Internet to FortiController front panel
interface 4 (fctrl/f4 on the worker GUI and
CLI) and an internal network to
FortiController front panel interface 2
(fctrl/f2 on the worker GUI and CLI) .
Then enter the root VDOM and add a
policy to allow users on the Internal
network to access the Internet.

FortiController Session-aware Load
Balancing Guide.
645
Expert
SLBC Active-Passive setup with two

FortiController-5103Bs
This example describes the basics of setting up an active-passive Session-aware Load Balancing Cluster (SLBC)
that consists of two FortiController-5103Bs, installed in chassis slots 1 and 2, and three FortiGate-5001C workers,
installed in chassis slots 3, 4, and 5. This SLBC configuration can have up to eight redundant 10Gbit network
connections.
The FortiControllers in the same chassis to operate in active-passive HA mode for redundancy. The
FortiController in slot 1 becomes the primary unit actively processing sessions. The FortiController in slot 2
becomes the subordinate unit, sharing the primary units session table. If the primary unit fails the subordinate unit
resumes all active sessions.
All networks have redundant connections to both FortiControllers. You also create heartbeat links between the
FortiControllers and management links from the FortiControllers to an internal network.
Expert
646
1. Hardware setup
Install a FortiGate-5000 series chassis and connect it to power. Install the FortiControllers in slots 1 and 2.
Install the workers in slots 3, 4, and 5. Power on the chassis.
Check the chassis, FortiController, and FortiGate LEDs to verify that all components are operating normally (to
check normal operation LED status, see the FortiGate-5000 series documents available here).
Create duplicate connections from the FortiController front panel interfaces to the Internet and to the internal
network.
Create a heartbeat link by connecting the FortiController B1 interfaces together. Create a backup heartbeat link
by connecting the FortiController B2 interfaces together. You can directly connect the interfaces with a patch
cable or connect them together through a switch. If you use a switch, it must allow traffic on the heartbeat VLAN
(default 999) and the base control and management VLANs (301 and 101). These connections establish
heartbeat, base control, and base management communication between the FortiControllers. Only one
heartbeat connection is required but redundant connections are recommended.
Connect the mgmt interfaces of the both FortiControllers to the internal network or any network from which you
want to manage the cluster.
product.
2. Configuring the FortiControllers

Connect to the GUI (using HTTPS) or CLI (using SSH) of the FortiController in slot 1 with the default IP address
bits: 8, Parity: None, Stop bits: 1, Flow control: None).
administrator account. You can either
use the GUI Administrators widget or
enter this CLI command.
config admin user

edit admin
end

interface IP address. Use the
Management Port widget in the GUI or
enter this command. Each FortiController
should have a different Management IP
address.

edit mgmt
set ip 172.20.120.151/24
end
Expert
647

command.
config route static

edit 1
end
end
Configure active-passive HA on the

FortiController in slot 1.
From the FortiController GUI System
Information widget, beside HA Status
select Configure.
Set Mode to Active-Passive, change
the Group ID, and move the b1 and b2
interfaces to the Selected column and
select OK.
You can also enter this command:
config system ha
set mode a-p
set groupid 23
set hbdev b1 b2
end
If you have more than one cluster on the same network, each cluster should have a different Group ID.
Changing the Group ID changes the cluster interface virtual MAC addresses. If your group ID setting causes a
MAC address conflict you can select a different Group ID. The default Group ID of 0 is not a good choice and
normally should be changed.
You can also adjust other HA settings. For example, you could increase the Device Priority of the
648
Expert
FortiController that you want to become the primary unit, enable Override to make sure the FortiController with
the highest device priority becomes the primary unit, and change the VLAN to use for HA heartbeat traffic if it
conflicts with a VLAN on your network.
You would only select Enable chassis redundancy if your cluster has more than one chassis.
Log into the web-based manager of the FortiController in slot 2 and duplicate the HA configuration of the
FortiController in slot 1, except for the Device Priority and override setting, which can be different on each
FortiController.
After a short time, the FortiControllers restart in HA mode and form an active-passive cluster. Both
FortiControllers must have the same HA configuration and at least one heartbeat link must be connected.
Normally the FortiController in slot 1 is the primary unit, and you can log into the cluster using the management
IP address you assigned to this FortiController.
You can confirm that the cluster has
been formed by viewing the HA
configuration from the the FortiController
web-based manager. The display should
show both FortiControllers in the cluster.
Since the configuration of all
FortiControllers is synchronized, you can
complete the configuration of the cluster
from the primary FortiController.
You can also go to Load Balance >

Status to see the status of the cluster.
This page should show both
FortiControllers in the cluster.
The FortiController in slot 1 is the primary
unit (slot icon colored green) and the
FortiController in slot 2 is the backup unit
(slot icon colored yellow).
Expert
649

workers. If the workers have not been
configured yet their status will be Down.
them.
You can also enter this command to add
slots 3, 4, and 5 to the cluster:

config slots
edit 3
next
edit 4
next
edit 5
end
end
You can also enter this command to set

the external management IP/Netmask
and configure management access.

set base-mgmt-external-ip 172.20.120.100 255.255.255.0
set base-mgmt-allowaccess https ssh ping
end
Enable base management traffic

between FortiControllers.

config base-mgmt-interfaces
edit b1
next
edit b2
end
end
Enable base control traffic between

FortiControllers.
650

config base-ctrl-interfaces
edit b1
next
edit b2
Expert

end
end
3. Adding the workers to the cluster

Reset the workers to factory default
settings.

workers.
Optionally give the mgmt1 and or mgmt2 interfaces of each worker IP addresses and connect them to your
network. When a cluster is created, the mgmt1 and mgmt2 IP addresses are not synchronized, so you can
connect to and manage each worker separately.
Optionally give each worker a different hostname. The hostname is also not synchronized and allows you to
identify each worker.
this command to set the worker to
Expert
config system elbc

end
651

appropriate slots.
4. Results
You can now connect to the worker GUI or CLI using the External Management IP and manage the workers in
the same way as you would manage a standalone FortiGate. If you configured the worker mgmt1 or mgmt2
interfaces you can also connect to these interfaces to configure the workers. Configuration changes made to
any worker are synchronized to all workers.
Configure the workers to process the traffic they receive from the FortiController front panel interfaces. By
default all FortiController front panel interfaces are in the root VDOM. You can keep them in the root VDOM or
create additional VDOMs and move interfaces into them.
For example, if you connect the Internet
to FortiController front panel interface 1
(fctrl/f1 on the worker GUI and CLI) and
the internal network to FortiController
front panel interface 6 (fctrl/f6 on the
worker GUI and CLI) you would access
the root VDOM and add this policy to
allow users on the Internal network to
access the Internet.
652
Expert

Balancing Guide.
Expert
653
SLBC Active-Passive with two FortiController-5103Bs

and two chassis
This example describes how to setup an active-passive session-aware load balancing cluster (SLBC) consisting
of two FortiGate-5000 chassis, two FortiController-5103Bs, and six FortiGate-5001Bs acting as workers, three in
each chassis. This SLBC configuration can have up to seven redundant 10Gbit network connections.
The FortiControllers operate in active-passive HA mode for redundancy. The FortiController in chassis 1 slot 1 will
be configured to be the primary unit, actively processing sessions. The FortiController in chassis 2 slot 1 becomes
the subordinate unit. If the primary unit fails the subordinate unit resumes all active sessions.
All networks in this example have redundant connections to both FortiControllers and redundant heartbeat and
base control and management links are created between the FortiControllers using their front panel B1 and B2
interfaces.
This example also includes a FortiController session sync connection between the FortiControllers using the
FortiController F4 front panel interface (resulting in the SLBC having a total of seven redundant 10Gbit network
connections). (You can use any fabric front panel interface.)
Heartbeat and base control and management traffic uses VLANs and specific subnets. So the switches and
network components used must be configured to allow traffic on these VLANs and you should be aware of the
subnets used in case they conflict with any connected networks.
Expert
654
This example sets the device priority of the FortiController in chassis 1 higher than the device priority of the
FortiController in chassis 2 to make sure that the FortiController in chassis 1 becomes the primary FortiController
for the cluster.
655
Expert
1. Hardware setup
Install two FortiGate-5000 series chassis and connect them to power. Ideally each chassis should be connected
to a separate power circuit. Install a FortiController in slot 1 of each chassis. Install the workers in slots 3, 4,
and 5 of each chassis. The workers must be installed in the same slots in both chassis. Power on both chassis.
Create duplicate connections from both FortiController front panel interfaces to the Internet and to the internal
network.
Create a FortiController session sync connection between the chassis by connecting the FortiController F4
interfaces. If you use a switch it must allow traffic on the FortiController session sync VLAN (2000). You can
use any of the F1 to F8 interfaces. We chose F4 in this example to make the diagram easier to understand.
product.
2. Configuring the FortiController in Chassis 1

Connect to the GUI (using HTTPS) or CLI (using SSH) of the FortiController in chassis 1 with the default IP
address (http://192.168.1.99) or connect to the FortiController CLI through the console port (Bits per second:
9600, Data bits: 8, Parity: None, Stop bits: 1, Flow control: None).
From the Dashboard System
Information widget, set the Host
Name to ch1-slot1. Or enter this
command.
Expert

set hostname ch1-slot1
end
656

use the Administrators widget on the
GUI or enter this command.
config admin user

interface IP address. Use the GUI
Management Port widget or enter
this command.

edit mgmt
set ip 172.20.120.151/24
end
If you need to add a default route for

the management IP address, enter
this command.
config route static

edit 1
end
Set the chassis type that you are

using.
edit admin
set password
end

end
Configure Active-Passive HA. From

the FortiController GUI System
Information widget, beside HA
Status select Configure.
Set Mode to Active-Passive, set the
Device Priority to 250, change the
Group ID, select Enable Override,
enable Chassis Redundancy, set
Chassis ID to 1 and move the b1 and
b2 interfaces to the Selected column
and select OK.
config system ha
Enter this command to use the
set session-sync-port f4
FortiController front panel F4 interface
end
for FortiController session sync
communication between
FortiControllers.
You can also enter the complete HA

configuration with this command.
657
config system ha
Expert
set mode active-passive

set groupid 5
set priority 250
set override enable
set chassis-redundancy enable
set chassis-id 1
set hbdev b1 b2
end
Enable Override is selected to make sure the FortiController in chassis 1 always becomes the primary unit.
Enabling override could lead to the cluster renegotiating more often, so once the chassis is operating you can
disable this setting.
You can also adjust other HA settings. For example, you could change the VLAN to use for HA heartbeat
traffic if it conflicts with a VLAN on your network. You can also adjust the Heartbeat Interval and Number of
Heartbeats lost to adjust how quickly the cluster determines one of the FortiControllers has failed.
3. Configuring the FortiController in Chassis 2

Log into the FortiController in chassis
2.

end
Enter these commands to set the

host name to ch2-slot1 and duplicate
the HA configuration of the
FortiController in chassis 1. Except,
do not select Enable Override and
set the Device Priority to a lower
value (for example, 10), and set the
Chassis ID to 2.
config system ha
set groupid 5
set priority 10
set chassis-id 2
set hbdev b1 b2
All other configuration settings are

synchronized from the primary
FortiController when the cluster
forms.
Expert
end
658
4. Configuring the cluster

After a short time the FortiControllers restart in HA mode and form an active-passive SLBC. Both
FortiControllers must have the same HA configuration and at least one heartbeat link (the B1 and B2 interfaces)
must be connected. If the FortiControllers are unable to form a cluster, check to make sure that they both have
the same HA configuration. Also they can't form a cluster if the heartbeat interfaces (B1 and B2) are not
connected.
With the configuration described in the previous steps, the FortiController in chassis 1 should become the
primary unit and you can log into the cluster using the management IP address that you assigned to the
FortiController in chassis 1.
The FortiController in chassis 2 becomes the backup FortiController. You cannot log into or manage the backup
FortiController until you configure the cluster External Management IP and add workers to the cluster. Once you
do this you can use the External Management IP address and a special port number to manage the backup
FortiController. This is described below. (You can also connect to the backup FortiController CLI using the
console port.)
been formed by viewing the
FortiController HA configuration. The
display should show both
Note in some of the screen images in

this example the host names shown
on the screen images may not match
the host names used in the example
configuration.
659
Expert

Status to see the status of the
primary FortiController (slot icon
colored green).
Go to Load Balance > Config to add

the workers to the cluster by selecting
Edit and moving the slots that contain
configured their status will be Down.
Configure the External
Management IP/Netmask. Once
you have connected workers to the
cluster, you can use this IP address
to manage and configure all of the
devices in the cluster.
You can also enter this command to
add slots 3, 4, and 5 to the cluster.

config slots
edit 3
next
edit 4
next
edit 5
end
end
Expert
660

set the External Management IP and
configure management access.

end


edit b1
next
edit b2
end
end

FortiControllers.

edit b1
next
edit b2
end
end

Reset each worker to factory default
settings.

Carrier, add the FortiOS Carrier
license instead. This will reset the
worker to factory default settings.
Give the mgmt1 or mgmt2 interface of
each worker an IP address and
connect these interfaces to your
network. This step is optional but
useful because when the workers are
added to the cluster, these IP
addresses are not synchronized, so
you can connect to and manage each
worker separately.

edit mgmt1
set ip 172.20.120.120
end
Optionally give each worker a

different hostname. The hostname is

set hostname worker-chassis-1-slot-3
661
Expert
also not synchronized and allows you

to identify each worker.
end

worker before adding the workers to
the cluster. This includes FortiCloud
license key if you purchased more
than 10 Virtual Domains. You can
also install any third-party certificates
on the primary worker before forming
the cluster. Once the cluster is
formed third-party certificates are
synchronized to all of the workers.
Log into the CLI of each worker and
enter this command to set the worker
to operate in FortiController mode.
The worker restarts and joins the
cluster.
config system elbc

end
6. Managing the cluster

After the workers have been added to the cluster you can use the External Management IP to manage the the
primary worker. This includes access to the primary worker GUI or CLI, SNMP queries to the primary worker,
and using FortiManager to manage the primary worker. As well SNMP traps and log messages are sent from the
primary worker with the External Management IP as their source address. And finally connections to FortiGuard
for updates, web filtering lookups and so on, all originate from the External Management IP.
You can use the external management IP followed by a special port number to manage individual devices in the
cluster. The special port number identifies the protocol (80 for HTTP, 443 for HTTPS, 22 for SSH, 23 for Telnet,
161 for SNMP) and the chassis and slot number of the device you want to connect to. In fact this is the only way
to manage the backup FortiController. Some examples:
l
To use HTTP to connect to the GUI of the FortiController in chassis 1 slot 1, browse to: https://172.20.120.100:44311
To use HTTP to connect to the GUI of the FortiController in chassis 2 slot 1, (the backup FortiController) browse to:
https://172.20.120.100:44321
To use Telnet to connect to the CLI of the worker in chassis 1 slot 4: telnet 172.20.120.100 2314
To use SSH to connect to the CLI the worker in chassis 2 slot 5: ssh admin@172.20.120.100 -p2225
To use SNMP to query the FortiController in chassis 2 slot 1 (the backup FortiController) use port 16121 in the SNMP query.
You can also manage the primary FortiController using the IP address of its mgmt interface, set up when you
Expert
662
first configured the primary FortiController. You can also manage the workers by connecting directly to their
mgmt1 or mgmt2 interfaces if you set them up. However, the only way to manage the backup FortiController is
by using its special port number.
To manage a FortiController using SNMP you need to load the FORTINET-CORE-MIB.mib file into your SNMP
manager. You can get this MIB file from the Fortinet support site, in the same location as the current
FortiController firmware (select the FortiSwitchATCA product).
On the primary FortiController GUI go
to Load Balance > Status. As the
workers in chassis 1 restart they
should appear in their appropriate
slots.
The primary FortiController should be
the FortiController in chassis 1 slot 1.
The primary FortiController status
display includes a Config Master link
that you can use to connect to the
primary worker.
Log into the backupFortiController

GUI (for example by browsing to
https://172.20.120.100:44321) and go
to Load Balance > Status. As the
workers in chassis 2 restart they
should appear in their appropriate
slots.
The backup FortiController Status
page shows the status of the workers
in chassis 2 and does not include the
Config Master link.
7. Results - Configuring the workers
663
Expert
default all FortiController front panel interfaces are in the worker root VDOM. You can keep them in the root
VDOM or create additional VDOMs and move interfaces into them.
For example, if you connect the
Internet to FortiController front panel 2
interfaces (fctrl/f2 on the worker GUI
and CLI) and the internal network to
FortiController front panel 6 interfaces
(fctrl/f6) you would access the root
VDOM and add this policy to allow
users on the Internal network to
8. Results - Checking the cluster status

You can use the following get and diagnose commands to show the status of the cluster and all of the devices in
it.
Log into the primary FortiController
CLI and enter this command to view
the system status of the primary
FortiController.
For example, you can use SSH to log into the primary FortiController CLI
using the external management IP:
ssh admin@172.20.120.100 -p2211
get system status
Version: FortiController-5103B
v5.0,build0024,140815
Branch Point: 0024
Serial-Number: FT513B3912000029
BIOS version: 04000009
System Part-Number: P08442-04
Hostname: ch1-slot1
Current HA mode: a-p, master
System time: Sat Sep 13 06:51:53 2014
Daylight Time Saving: Yes
Time Zone: (GMT-8:00)Pacific Time(US&Canada)
Expert
664
Enter this command to view the load

balance status of the primary
FortiController and its workers. The
command output shows the workers
in slots 3, 4, and 5, and status
information about each one.
get load-balance status

ELBC Master Blade: slot-3
Confsync Master Blade: slot-3
Blades:
Working: 3 [ 3 Active 0
Ready: 0 [ 0 Active 0
Dead: 0 [ 0 Active 0
Total: 3 [ 3 Active 0
Standby]
Standby]
Standby]
Standby]
Slot 3: Status:Working Function:Active

Link: Base: Up
Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running"
Link: Base: Up Fabric: Up
665
Expert
Enter this command from the primary FortiController to show the HA status of the primary and backup
FortiControllers. The command output shows a lot of information about the cluster including the host names and
chassis and slot locations of the FortiControllers, the number of sessions each FortiController is processing
(this case 0 for each FortiController) the number of failed workers (0 of 3 for each FortiController), the number of
FortiController front panel interfaces that are connected (2 for each FortiController) and so on. The final two lines
of output also show that the B1 interfaces are connected (status=alive) and the B2 interfaces are not
(status=dead). The cluster can still operate with a single heartbeat connection, but redundant heartbeat
interfaces are recommended.
diagnose system ha status
mode: a-p
minimize chassis failover: 1
ch1-slot1(FT513B3912000029), Master(priority=0), ip=169.254.128.41,
uptime=62581.81, chassis=1(1)
slot: 1
sync: conf_sync=1, elbc_sync=1
session: total=0, session_sync=in sync
state: worker_failure=0/3, intf_state=(port up:)=2
force-state(0:none) hbdevs: local_interface= b1 best=yes
local_interface= b2 best=no
ch2-slot1(FT513B3912000051), Slave(priority=1), ip=169.254.128.42,
slot: 1
sync: conf_sync=0, elbc_sync=1, conn=3(connected)
force-state(0:none) hbdevs: local_interface= b1 last_hb_time=66430.35
status=alive
local_interface= b2 last_hb_time= 0.00
status=dead
Log into the backup FortiController
CLI and enter this command to view
the status of the backup
FortiController.
Expert
To use SSH:
ssh admin@172.20.120.100 -p2221
get system status
Version: FortiController-5103B
v5.0,build0020,131118 (Patch 3)
Branch Point: 0020
Hostname: ch2-slot1
Current HA mode: a-p, backup
System time: Sat Sep 13 07:29:04 2014
666

Enter this command to view the
status of the backup FortiController
and its workers.

Confsync Master Blade: N/A
Blades:
Working: 3 [ 3 Active 0
Ready: 0 [ 0 Active 0
Dead: 0 [ 0 Active 0
Total: 3 [ 3 Active 0
Standby]
Standby]
Standby]
Standby]

Enter this command from the backup FortiController to show the HA status of the backup and primary
FortiControllers. Notice that the backup FortiController is shown first. The command output shows a lot of
information about the cluster including the host names and chassis and slot locations of the FortiControllers, the
number of sessions each FortiController is processing (this case 0 for each FortiController) the number of failed
workers (0 of 3 for each FortiController), the number of FortiController front panel interfaces that are connected
(2 for each FortiController) and so on. The final two lines of output also show that the B1 interfaces are
connected (status=alive) and the B2 interfaces are not (status=dead). The cluster can still operate with a single
heartbeat connection, but redundant heartbeat interfaces are recommended.
mode: a-p
slot: 1
force-state(0:none)
hbdevs: local_interface= b1 best=yes
667
Expert

slot: 1
force-state(0:none) hbdevs: local_interface= b1 last_hb_time=68534.90
status=alive
local_interface= b2 last_hb_time= 0.00 status=dead

Balancing Guide.
Expert
668
This example describes the basics of setting up a dual mode Session-aware Load Balancing Cluster (SLBC) that
consists of two FortiController-5103Bs, installed in chassis slots 1 and 2, and three FortiGate-5001C workers,
installed in chassis slots 3, 4, and 5. This SLBC configuration can have up to 16 10Gbit network connections.
The two FortiControllers in the same chassis to operate in dual mode to double the number of network interfaces
available. In dual mode, two FortiControllers load balance traffic to multiple workers. Traffic can be received by
both FortiControllers and load balanced to all of the workers in the chassis. In dual mode configuration the front
panel interfaces of both FortiControllers are active.
In a dual FortiController-5103B cluster this means up to 16 10Gbyte network interfaces are available. The
interfaces of the FortiController in slot 1 are named fctrl/f1 to fctrl/f8 and the interfaces of the FortiController in slot
2 are named fctr2/f1 to fctrl2/f8.
All networks have single connections to the first or second FortiController. One or more heartbeat links are created
between the FortiControllers. Redundant heartbeat links are recommended. The heartbeat links use the front
panel B1 and B2 interfaces.
If one of the FortiControllers fails, the remaining FortiController keeps processing traffic received by its front panel
interfaces. Traffic to and from the failed FortiController is lost.
Expert
669
1. Hardware setup
Install a FortiGate-5000 series chassis and connect it to power. Install the FortiControllers in slots 1 and 2.
Install the workers in slots 3, 4, and 5. Power on the chassis.
Create connections from the FortiController front panel interfaces to the Internet and to the internal network.
product.
2. Configuring the FortiControllers

Connect to the GUI (using HTTPS) or CLI (using SSH) of the FortiController in slot 1 with the default IP address
bits: 8, Parity: None, Stop bits: 1, Flow control: None).
use the Administrators widget in the
GUI or enter the following command in
the CLI.
config admin user

edit admin
set password password
end

interface IP address. Use the
Management Port widget in the GUI or
enter the following command in the CLI.

edit mgmt
set ip 172.20.120.151/24
end

config route static

edit 1
Expert
670
command.
end

end
Configure dual Mode HA on the

FortiController in slot 1.
From the FortiController GUI System
Information widget, beside HA Status
select Configure.
Set Mode to Dual Mode, change the
Group ID, and move the b1 and b2
select OK.
config system ha
set mode dual
set groupid 4
set hbdev b1 b2
end
You can also adjust other HA settings. For example, you could increase the Device Priority of the
FortiController that you want to become the primary unit, enable Override to make sure the FortiController with
the highest device priority becomes the primary unit, and change the VLAN to use for HA heartbeat traffic if it
671
Expert
conflicts with a VLAN on your network.

You would only select Enable chassis redundancy if your cluster has more than one chassis.
Log into the web-based manager of the FortiController in slot 2 and duplicate the HA configuration of the
FortiController in slot 1, except for the Device Priority and override setting, which can be different on each
FortiController.
After a short time, the FortiControllers restart in HA mode and form a dual mode cluster. Both FortiControllers
must have the same HA configuration and at least one heartbeat link must be connected.
Normally the FortiController in slot 1 is the primary unit, and you can log into the cluster using the management
IP address you assigned to this FortiController.
If the FortiControllers are unable to form a cluster, check to make sure that they both have the same HA
configuration. Also they can't form a cluster if the heartbeat interfaces (B1 and B2) are not connected.
been formed by viewing the HA
configuration from the the FortiController
web-based manager. The display should
show both FortiControllers in the cluster.
Since the configuration of the
FortiControllers is synchronized, you can
complete the configuration of the cluster
from the primary FortiController.
Expert
672

Status to see the status of the cluster.
This page should show both
Since both FortiControllers are active
their slot icons are both colored green.

configured yet their status will be Down.
them.
slots 3, 4, and 5 to the cluster.

config slots
edit 3
next
edit 4
next
edit 5
end
end

configure the external management
IP/Netmask and management access to
673

Expert
this address.
end
edit b1
next
edit b2
end
end

FortiControllers.

edit b1
next
edit b2
end
end

Reset the workers to factory default
settings.

workers.
Expert
674
Optionally give the mgmt1 and or mgmt2 interfaces of each worker IP addresses and connect them to your
network. When a cluster is created, the mgmt1 and mgmt2 IP addresses are not synchronized, so you can
connect to and manage each worker separately.
Optionally give each worker a different hostname. The hostname is also not synchronized and allows you to
identify each worker.
config system elbc

set mode dual-forticontroller
end

appropriate slots.
675
Expert
4. Results
You can now connect to the worker GUI or CLI using the External Management IP and manage the workers in
the same way as you would manage a standalone FortiGate. If you configured the worker mgmt1 or mgmt2
interfaces you can also connect to these interfaces to configure the workers. Configuration changes made to
any worker are synchronized to all workers.
default all FortiController front panel interfaces are in the root VDOM. You can keep them in the root VDOM or
create additional VDOMs and move interfaces into them.
of the FortiController in slot 1 (fctrl1/f2 on
the worker GUI and CLI) and the internal
network to FortiController front panel
interface 6 of the FortiController in slot 2
(fctrl2/f6 on the worker GUI and CLI) you
would access the root VDOM and add
this policy to allow users on the Internal
network to access the Internet.

Balancing Guide.
Expert
676
SLBC Active-Passive with four FortiController-5103Bs

and two chassis
This example describes how to setup an active-passive session-aware load balancing cluster (SLBC) consisting
of two FortiGate-5000 chassis, four FortiController-5103Bs two in each chassis, and six FortiGate-5001Bs acting
as workers, three in each chassis. This SLBC configuration can have up to seven redundant 10Gbit network
connections.
The FortiControllers operate in active-passive HA mode for redundancy. The FortiController in chassis 1 slot 1 will
be configured to be the primary unit, actively processing sessions. The other FortiControllers become the
subordinate units.
In active-passive HA with two chassis and four FortiControllers, both chassis have two FortiControllers in activepassive HA mode and the same number of workers. Network connections are duplicated to the redundant
FortiControllers in each chassis and between chassis for a total of four redundant data connections to each
network.
All traffic is processed by the primary unit. If the primary unit fails, all traffic fails over to the chassis with two
functioning FortiControllers and one of these FortiControllers becomes the new primary unit and processes all
traffic. If the primary unit in the second chassis fails as well, one of the remaining FortiControllers becomes the
primary unit and processes all traffic.
Expert
677
Heartbeat and base control and management communication is established between the chassis using the
FortiController B1 and B2 interfaces. Only one heartbeat connection is required but redundant connections are
recommended. Connect all of the B1 and all of the B2 interfaces together using switches. This example shows
using one switch for the B1 connections and another for the B2 connections. You could also use one switch for
both the B1 and B2 connections but using separate switches provides more redundancy.
The following VLAN tags and subnets are used by traffic on the B1 and B2 interfaces:
l
Heartbeat traffic uses VLAN 999.
Base control traffic on the 10.101.11.0/255.255.255.0 subnet uses VLAN 301.
Base management on the 10.101.10.0/255.255.255.0 subnet uses VLAN 101
This example also includes a FortiController session sync connection between the FortiControllers using the
FortiController F4 front panel interface (resulting in the SLBC having a total of seven redundant 10Gbit network
connections). (You can use any fabric front panel interface, F4 is used in this example to make the diagram
clearer.) FortiController-5103B session sync traffic uses VLAN 2000.
This example sets the device priority of the FortiController in chassis 1 slot 1 higher than the device priority of the
other FortiControllers to make sure that the FortiController in chassis 1 slot 1 becomes the primary FortiController
for the cluster. Override is also enabled on the FortiController in chassis 1 slot 1. Override may cause the cluster
to negotiate more often to select the primary unit. This makes it more likely that the unit that you select to be the
primary unit will actually be the primary unit; but enabling override can also cause the cluster to negotiate more
often.
678
Expert
1. Hardware setup
Install two FortiGate-5000 series chassis and connect them to power. Ideally each chassis should be connected
to a separate power circuit. Install FortiControllers in slot 1 and 2 of each chassis. Install the workers in slots 3,
4, and 5 of each chassis. The workers must be installed in the same slots in both chassis. Power on both
chassis.
Create redundant connections from all four FortiController front panel interfaces to the Internet and to the internal
network.
by connecting the FortiController B2 interfaces together.
Create a FortiController session sync connection between the chassis by connecting the FortiController F4
interfaces together.
Connect the mgmt interfaces of all of the FortiControllers to the internal network or any network from which you
Check the FortiSwitch-ATCA release notes and install the latest supported firmware on the FortiControllers and
product.
2. Configuring the FortiController in Chassis 1 Slot 1

This will become the primary FortiController. To make sure this is the primary FortiController it will be assigned
the highest device priority and override will be enabled. Connect to the GUI (using HTTPS) or CLI (using SSH)
of the FortiController in chassis 1 slot 1 with the default IP address (http://192.168.1.99) or connect to the
FortiController CLI through the console port (Bits per second: 9600, Data bits: 8, Parity: None, Stop bits: 1, Flow
control: None).
From the Dashboard System Information
widget, set the Host Name to ch1-slot1.
Or enter this command.

config admin user
Expert

end
edit admin
set password
end
679

Management Port widget or enter this
command.

edit mgmt
set ip 172.20.120.151/24
end

command.
config route static

edit 1
end

end
Configure Active-Passive HA. From the

FortiController GUI System Information
widget, beside HA Status select
Configure.
Set Mode to Active-Passive, set the
Device Priority to 250, change the
Group ID, select Enable Override,
enable Chassis Redundancy, set
Chassis ID to 1 and move the b1 and b2
select OK.
config system ha
Enter this command to use the
FortiController front panel F4 interface for
end
FortiController session sync
communication between
FortiControllers.
680
Expert

config system ha
set groupid 15
set priority 250
set override enable
set chassis-id 1
set hbdev b1 b2
end

Log into the FortiController in chassis 1
slot 2.

end
Enter these commands to set the host

name to ch1-slot2, to configure the mgmt
interface, and to duplicate the HA
configuration of the FortiController in slot
1. Except, do not select Enable
Override and set the Device Priority to
a lower value (for example, 10).

edit mgmt
set ip 172.20.120.152/24
end
config system ha

FortiController when the cluster forms.
set groupid 15
set priority 10
set chassis-id 1
set hbdev b1 b2
end
Expert
681

slot 1.

end

configuration of the FortiController in
chassis 1 slot 1. Except, do not select
Enable Override and set the Device
Priority to a lower value (for example,
10), and set the Chassis ID to 2.

edit mgmt
set ip 172.20.120.251/24
end
config system ha
set groupid 15

set priority 10
set chassis-id 2
set hbdev b1 b2
end

slot 2.

end


edit mgmt
set ip 172.20.120.252/24
end
config system ha
set groupid 15

set priority 10
set chassis-id 2
set hbdev b1 b2
end
682
Expert

After a short time the FortiControllers restart in HA mode and form an active-passive SLBC. All of the
must be connected. If the FortiControllers are unable to form a cluster, check to make sure that they all have the
same HA configuration. Also they can't form a cluster if the heartbeat interfaces (B1 and B2) are not connected.
With the configuration described in the previous steps, the FortiController in chassis 1 slot 1 should become the
primary unit and you can log into the cluster using the management IP address that you assigned to this
FortiController.
The other FortiControllers become backup FortiControllers. You cannot log into or manage the backup
FortiControllers until you configure the cluster External Management IP and add workers to the cluster. Once
you do this you can use the External Management IP address and a special port number to manage the backup
FortiControllers. This is described below. (You can also connect to any backup FortiController CLI using their
console port.)
display should show both
Expert
683

Status to see the status of the primary
FortiController (slot icon colored green).

configured for SLBC operation their
status will be Down.
IP address to manage and configure all of
the devices in the cluster.

config slots
edit 3
next
edit 4
next
edit 5
end
end
684
Expert
You can also enter this command to set

the External Management IP and
configure management access.

end


edit b1
next
edit b2
end
end

FortiControllers.

edit b1
next
edit b2
end
end

settings.

each worker an IP address and connect
these interfaces to your network. This
step is optional but useful because when
the workers are added to the cluster,
these IP addresses are not
synchronized, so you can connect to and
manage each worker separately.

edit mgmt1
set ip 172.20.120.120
end
Optionally give each worker a different

hostname. The hostname is also not
synchronized and allows you to identify
each worker.
Expert

end
685
Register each worker and apply licenses

to each worker before adding the workers
to the cluster. This includes FortiCloud
workers.
operate in FortiController mode. The
worker restarts and joins the cluster.
config system elbc

end

for updates, web filtering lookups and so on, all originate from the External Management IP.
You can use the external management IP followed by a special port number to manage individual devices in the
cluster. The special port number identifies the protocol (80 for HTTP, 443 for HTTPS, 22 for SSH, 23 for Telnet,
161 for SNMP) and the chassis and slot number of the device you want to connect to. In fact this is the only way
to manage the backup FortiControllers. Some examples:
l
To use HTTP to connect to the GUI of the FortiController in chassis 1 slot 2, browse to: https://172.20.120.100:44312
To use HTTP to connect to the GUI of the FortiController in chassis 2 slot 1,browse to: https://172.20.120.100:44321
To use Telnet to connect to the CLI of the worker in chassis 2 slot 4: telnet 172.20.120.100 2324
To use SNMP to query the FortiController in chassis 1 slot 2 use port 16112 in the SNMP query.
mgmt1 or mgmt2 interfaces if you set them up. However, the only way to manage the backup FortiControllers is
by using its special port number (or a serial connection to the Console port).
686
Expert
On the primary FortiController GUI go to
Load Balance > Status. As the workers
in chassis 1 restart they should appear in
their appropriate slots.
The primary FortiController should be the
FortiController in chassis 1 slot 1. The
primary FortiController status display
includes a Config Master link that you
can use to connect to the primary worker.
Log into a backup FortiController GUI (for

example by browsing to
https://172.20.120.100:44321 to log into
the FortiController in chassis 2 slot 1)
and go to Load Balance > Status. If the
workers in chassis 2 are configured
correctly they should appear in their
appropriate slots.
The backup FortiController Status page
shows the status of the workers in
chassis 2 and does not include the
Config Master link.

Expert
687

(fctrl/f2 on the worker GUI and CLI) and
front panel interface 6 (fctrl/f6) you can
access the root VDOM and add a policy
to allow users on the Internal network to
10. Results - Primary FortiController cluster status

Log into the primary FortiController CLI
and enter this command to view the
system status of the primary
FortiController.
For example, you can use SSH to log into the primary FortiController CLI using the
external management IP:
ssh admin@172.20.120.100 -p2211
get system status
Version: FortiController-5103B v5.0,build0024,140815
Branch Point: 0024
Hostname: ch1-slot1
Current HA mode: a-p, master
System time: Sun Sep 14 08:16:25 2014
Enter this command to view the load

balance status of the primary
FortiController and its workers. The
command output shows the workers in
slots 3, 4, and 5, and status information
about each one.

Blades:
Working: 3 [3 Active 0 Standby]
Ready: 0 [0 Active 0 Standby]
Dead: 0 [0 Active 0 Standby]
Total:
3 [3 Active 0 Standby]
688
Expert

Enter this command from the primary FortiController to show the HA status of the FortiControllers. The
command output shows a lot of information about the cluster including the host names and chassis and slot
locations of the FortiControllers, the number of sessions each FortiController is processing (this case 0 for each
FortiController) the number of failed workers (0 of 3 for each FortiController), the number of FortiController front
panel interfaces that are connected (2 for each FortiController) and so on. The final two lines of output also show
that the B1 interfaces are connected (status=alive) and the B2 interfaces are not (status=dead). The cluster can
still operate with a single heartbeat connection, but redundant heartbeat interfaces are recommended.
mode: a-p
ch1-slot1(FT513B3912000029), Master(priority=0), ip=169.254.128.121, uptime=4416.18, chassis=1(1)
slot: 1
force-state(0:none)
ch2-slot1(FT513B3912000051), Slave(priority=2), ip=169.254.128.123, uptime=1181.62, chassis=2(1)
slot: 1
force-state(0:none)
hbdevs: local_interface= b1 last_hb_time= 4739.97 status=alive

slot: 2
Expert
689
force-state(0:none)

slot: 2
force-state(0:none)
11. Results - Chassis 1 Slot 2 FortiController status

Log into the chassis 1 slot 2
FortiController CLI and enter this
command to view the status of this
backup FortiController.
To use SSH:
ssh admin@172.20.120.100 -p2212
get system status
Branch Point: 0024
Hostname: ch1-slot2
Enter this command to view the status of

this backup FortiController and its
workers.

Blades:
Working: 3 [ 3 Active 0 Standby]
Ready: 0 [ 0 Active 0 Standby]
Dead: 0 [ 0 Active 0 Standby]
Total: 3 [ 3 Active 0 Standby]
690
Expert

Enter this command from the FortiController in chassis 1 slot 2 to show the HA status of the FortiControllers.
Notice that the FortiController in chassis 1 slot 2 is shown first.
mode: a-p
slot: 2
force-state(0:none)
slot: 1
force-state(0:none)

slot: 1
force-state(0:none)

slot: 2
Expert
691
force-state(0:none)

To use SSH:
ssh admin@172.20.120.100 -p2221
get system status
Branch Point: 0024
Hostname: ch2-slot1

this backup FortiController and its
workers.

Blades:
692
Expert

mode: a-p
slot: 1
force-state(0:none)
slot: 1
force-state(0:none)

slot: 2
force-state(0:none)

slot: 2
force-state(0:none)

Expert
To use SSH:
ssh admin@172.20.120.100 -p2222
get system status
693

Branch Point: 0024
Hostname: ch2-slot2

the backup FortiController and its
workers.

Blades:
mode: a-p
slot: 2
694
Expert
force-state(0:none)
slot: 1
force-state(0:none)

slot: 1
force-state(0:none)

slot: 2
force-state(0:none)

Balancing Guide.
Expert
695
This example describes how to setup a dual-mode session-aware load balancing cluster (SLBC) consisting of two
FortiGate-5144C chassis, four FortiController-5903Cs two in each chassis, and six FortiGate-5001Ds acting as
workers, three in each chassis. This SLBC configuration can have up to 8 redundant 40Gbps network
connections. The FortiGate-5144C is required to supply enough power for the FortiController-5903Cs and provide
40Gpbs fabric backplane communication.
In this dual mode configuration, the FortiController in chassis 1 slot 1 is configured to become the primary unit.
Both of the FortiControllers in chassis 1 receive traffic and load balance it to the workers in chassis 1. In dual
mode configuration the front panel interfaces of both FortiControllers are active. All networks have single
connections to the FortiController in slot 1 or the FortiController in slot 2. The front panel F1 to F4 interfaces of the
FortiController in slot 1 are named fctrl1/f1 to fctrl1/f4 and the front panel F1 to F4 interfaces of the FortiController
in slot 2 are named fctrl2/f1 to fctrl2/f4.
The network connections to the FortiControllers in chassis 1 are duplicated with the FortiControllers in chassis 2.
If one of the FortiControllers in chassis 1 fails, the FortiController in chassis 2 slot 1 becomes the primary
FortiController and all traffic fails over to the FortiControllers in chassis 2. If one of the FortiControllers in chassis 2
fails, the remaining FortiController in chassis 2 keeps processing traffic received by its front panel interfaces.
Traffic to and from the failed FortiController is lost.
Heartbeat, base control, base management, and session sync communication is established between the chassis
using the FortiController B1 and B2 interfaces. Connect all of the B1 interfaces together using a 10 Gbps switch.
Expert
696
Collect all of the B2 interfaces together using another 10 Gbps switch. Using the same switch for the B1 and B1
interfaces is not recommended and requires a double VLAN tagging configuration.
The switches must be configured to support the following VLAN tags and subnets used by the traffic on the B1
and B2 interfaces:
l
Heartbeat traffic uses VLAN 999.
Base control traffic on the 10.101.11.0/255.255.255.0 subnet uses VLAN 301.
Base management on the 10.101.10.0/255.255.255.0 subnet uses VLAN 101
Session sync traffic uses VLAN 1900 and 1901.
This example sets the device priority of the FortiController in chassis 1 slot 1 is higher than the device priority of
the other FortiControllers to make sure that the FortiController in chassis 1 slot 1 becomes the primary
FortiController for the cluster. Override is also enabled on the FortiController in chassis 1 slot 1. Override may
cause the cluster to negotiate more often to select the primary unit. This makes it more likely that the unit that you
select to be the primary unit will actually be the primary unit; but enabling override can also cause the cluster to
negotiate more often.
697
Expert
1. Hardware setup
Install two FortiGate-5144C series chassis and connect them to power. Ideally each chassis should be
connected to a separate power circuit. Install FortiControllers in slot 1 and 2 of each chassis. Install the workers
in slots 3, 4, and 5 of each chassis. The workers must be installed in the same slots in both chassis. Power on
both chassis.
Create redundant network connections to FortiController front panel interfaces. In this example, a redundant
connection to the Internet is made to the F1 interface of the FortiController in chassis 1 slot 1 and the F1
interface of the FortiController in chassis 2 slot 1. This becomes the fctl1/f1 interface. As well, a redundant
connection to the internal network is made to the F3 interface of the FortiController in chassis 1 slot 2 and the F3
interface of the FortiController in chassis 2 slot 2. This becomes the fctl2/f3 interface.
Create the heartbeat links by connecting the FortiController B1 interfaces together and the FortiController B2
interfaces together.
Connect the mgmt interfaces of all of the FortiControllers to the internal network or any network from which you
Check the FortiSwitch-ATCA release notes and install the latest supported firmware on the FortiControllers and
product.

This will become the primary FortiController. Connect to the GUI (using HTTPS) or CLI (using SSH) of the
FortiController in chassis 1 slot 1 with the default IP address (https://192.168.1.99) or connect to the
FortiController CLI through the console port (Bits per second: 9600, Data bits: 8, Parity: None, Stop bits: 1, Flow
control: None).
From the Dashboard System Information
widget, set the Host Name to ch1-slot1.
Or enter this command.

end

config admin user

edit admin
end
Expert
698

Management Port widget or enter this
command.

edit mgmt
set ip 172.20.120.151/24
end

command.
config route static

edit 1
end

end
Enable FortiController session sync.

set session-sync enable
end
Configure Dual mode HA. From the

FortiController GUI System Information
widget, beside HA Status select
Configure.
Set Mode to Dual Mode, set the Device
Priority to 250, change the Group ID,
select Enable Override, enable
Chassis Redundancy, set Chassis ID
to 1 and move the b1 and b2 interfaces
to the Selected column and select OK.
config system ha
Enter these commands to use the
FortiController front panel F4 interface for set session-sync-port f4
end
session sync communication.
699
Expert

config system ha
set mode dual
set groupid 25
set priority 250
set override enable
set chassis-id 1
set hbdev b1 b2
end

slot 2.

end

configuration of the FortiController in slot
1. Except, do not select Enable
Override and set the Device Priority to
a lower value (for example, 10).

edit mgmt
set ip 172.20.120.152/24
end

Expert
config system ha
set mode dual
set groupid 25
set priority 10
set chassis-id 1
set hbdev b1 b2
end
700

slot 1.

end


edit mgmt
set ip 172.20.120.251/24
end

config system ha
set mode dual
set groupid 25
set priority 10
set chassis-id 2
set hbdev b1 b2
end

slot 2.

end


edit mgmt
set ip 172.20.120.252/24
end

701
config system ha
set mode dual
set groupid 25
set priority 10
set chassis-id 2
set hbdev b1 b2
end
Expert

After a short time the FortiControllers restart in HA mode and form an active-passive SLBC. All of the
must be connected. If the FortiControllers are unable to form a cluster, check to make sure that they all have the
same HA configuration. Also they can't form a cluster if the heartbeat interfaces (B1 and B2) are not connected.
With the configuration described in the previous steps, the FortiController in chassis 1 slot 1 should become the
primary FortiController and you can log into the cluster using the management IP address that you assigned to
this FortiController.
The other FortiControllers become backup FortiControllers. You cannot log into or manage the backup
FortiControllers until you configure the cluster External Management IP and add workers to the cluster. Once
you do this you can use the External Management IP address and a special port number to manage the backup
FortiControllers. This is described below. (You can also connect to any backup FortiController CLI using their
console port.)
display should show all four of the
Expert
702

Status to see the status of
FortiControllers (both slot icons should
be green because both FortiControllers
process traffic).

configured for SLBC operation their
status will be Down.
IP address to manage and configure all of
the devices in the cluster.

config slots
edit 3
next
edit 4
next
edit 5
end
end
Make sure the FortiController fabric

backplane ports are set to the correct
To change backplane fabric channel interface speeds, from the GUI go to Switch >
Fabric Channel and edit the slot-3, slot-4, and slot-5 interface. Set the Speed to
703
Expert
speed. Since the workers are FortiGate5001Ds and the cluster is using
FortiGate-5144C chassis, the
FortiController fabric backplane interface
speed should be set to 40Gbps full
duplex.
40Gpbs Full-duplex and select OK.

From the CLI enter the following command to change the speed of the slot-4 port.
config switch fabric-channel physical-port
edit slot-3
set speed 40000full
next
edit slot-4
set speed 40000full
next
edit slot-5
set speed 40000full
end
end
You can also enter this command to set the External Management IP and configure management access:
end
between FortiControllers. The CLI
syntax shows setting the default base
management VLAN (101). You can use
this command to change the base
management VLAN.

edit b1
set vlan-id 101
next
edit b2
set vlan-id 101
end
end

FortiControllers. The CLI syntax shows
setting the default base control VLAN
(301). You can use this command to
change the base management VLAN.

edit b1
set vlan-id 301
next
edit b2
set vlan-id 301
end
end
Expert
704

settings.

each worker an IP address and connect
these interfaces to your network. This
step is optional but useful because when
the workers are added to the cluster,
these IP addresses are not
synchronized, so you can connect to and
manage each worker separately.

edit mgmt1
set ip 172.20.120.120
end
Optionally give each worker a different

hostname. The hostname is also not
synchronized and allows you to identify
each worker.

end
Register each worker and apply licenses

to each worker before adding the workers
to the cluster. This includes FortiCloud
activation, FortiClient and FortiToken
licensing, and entering a license key if
you purchased more than 10 Virtual
Domains (VDOMs). You can also install
workers.
705
Expert

operate in FortiController mode. The
worker restarts and joins the cluster.
config system elbc

set mode dual-forticontroller
end
Set the backplane communication speed

of the workers to 40Gbps to match the
FortiController-5903C.

edit elbc-ctrl/1
set speed 40000full
next
edit elbc-ctrl/2
set speed 40000full
end

for updates, web filtering lookups and so on, all originate from the External Management IP.You can use the
external management IP followed by a special port number to manage individual devices in the cluster. The
special port number identifies the protocol and the chassis and slot number of the device you want to connect to.
In fact this is the only way to manage the backup FortiControllers. The special port number begins with the
standard port number for the protocol you are using and is followed by two digits that identify the chassis number
and slot number. The port number is determined using the following formula:
service_port x 100 + (chassis_id - 1) x 20 + slot_id
service_port is the normal port number for the management service (80 for HTTP, 443 for HTTPS, 22 for SSH,
23 for Telnet, 161 for SNMP). chassis_id is the Chassis ID part of the FortiController HA configuration and can
be 1 or 2. slot_id is the number of the chassis slot.
Some examples:
l
Expert
HTTPS, chassis 1 slot 2: 443 x 100 + (1 - 1) x 20 + 2 = 44300 + 0 + 2 = 44302, browse to:

https://172.20.120.100:44302
HTTP, chassis 2, slot 4: 80 x 100 + (2 - 1) x 20 + 4 = 8000 + 20 + 4 = 8024, browse to:
http://172.20.120.100/8024
HTTPS, chassis 1, slot 10: 443 x 100 + (1 - 1) x 20 + 10 = 44300 + 0 + 10 = 44310, browse to
https://172.20.120.100/44330
HTTPS, chassis 2, slot 10: 443 x 100 + (2 - 1) x 20 + 10 = 44300 + 20 + 10 = 44330, browse to
https://172.20.120.100/44330
SNMP query port, chassis 1, slot 4: 161 x 100 + (1 - 1) x (20 + 4) = 16100 + 0 + 4 = 16104
706
Telnet to connect to the CLI of the worker in chassis 2 slot 4: telnet 172.20.120.100 2324
mgmt1 or mgmt2 interfaces if you set them up. However, the only way to manage the backup FortiControllers is
by using its special port number (or a serial connection to the Console port).
On the primary FortiController GUI go to
Load Balance > Status. If the workers
in chassis 1 are configured correctly they
should appear in their appropriate slots
The primary FortiController should be the
FortiController in chassis 1 slot 1. The
primary FortiController status display
includes a Config Master link that you
can use to connect to the primary worker.
Log into a backup FortiController GUI (for

example by browsing to
https://172.20.120.100:44321 to log into
the FortiController in chassis 2 slot 1)
and go to Load Balance > Status. If the
workers in chassis 2 are configured
correctly they should appear in their
appropriate slots.
The backup FortiController Status page
shows the status of the workers in
chassis 2 and does not include the
Config Master link.
707
Expert

(fctrl1/f2 on the worker GUI and CLI) and
front panel interface 6 (fctrl2/f6) you can
access the root VDOM and add a policy
to allow users on the Internal network to
Expert
708
10. Results - Primary FortiController cluster status

Log into the primary FortiController CLI
and enter this command to view the
system status of the primary
FortiController.
For example, you can use SSH to log into the primary FortiController
CLI using the external management IP:
ssh admin@172.20.120.100 -p2201
get system status
Versio: FortiController-5903C v5.0,build0024
14815
Branch Point: 0024
Hostname: ch1-slot1
Current HA mode: dual, master
System time: Mon Sep 15 10:11:48 2014
Enter this command to view the load balance status of the primary FortiController and its workers. The
command output shows the workers in slots 3, 4, and 5, and status information about each one.
Blades:
Ready:
0 [ 0 Active 0 Standby]
Dead:
Total:
Slot 3: Status:Working
Function:Active
Link:
Base: Up
Fabric: Up
Heartbeat: Management: Good
Data: Good
Function:Active
Link:
Base: Up
Fabric: Up
Data: Good
Function:Active
Link:
Base: Up
Fabric: Up
709
Expert

Data: Good
Status Message:"Running"get load-balance status
Blades:
Ready:
Dead:
Total:
Function:Active
Link:
Base: Up
Fabric: Up
Data: Good
Function:Active
Link:
Base: Up
Fabric: Up
Data: Good
Function:Active
Link:
Base: Up
Fabric: Up
Data: Good
Expert
710
Enter this command from the primary FortiController to show the HA status of the FortiControllers. The
command output shows a lot of information about the cluster including the host names and chassis and slot
locations of the FortiControllers, the number of sessions each FortiController is processing (in this case 0 for
each FortiController) the number of failed workers (0 of 3 for each FortiController), the number of FortiController
front panel interfaces that are connected (2 for each FortiController) and so on. The final two lines of output also
show that the B1 interfaces are connected (status=alive) and the B2 interfaces are not (status=dead). The
cluster can still operate with a single heartbeat connection, but redundant heartbeat interfaces are
recommended.
mode: dual
slot: 1
force-state(0:none)
hbdevs: local_interface=
b1 best=yes
local_interface=
b2 best=no
slot: 1
force-state(0:none)
b1 last_hb_
time=82192.16
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead
slot: 2
force-state(0:none)
b1 last_hb_
time=82192.27
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead
711
Expert
slot: 2
force-state(0:none)
time=82192.16
status=alive
local_interface=
b2 last_hb_time=
b1 last_hb_
0.00
status=dead

To use SSH:
ssh admin@172.20.120.100 -p2202
get system status
Version: FortiController-5903C
v5.0,build0024,140815
Branch Point: 0024
Hostname: ch1-slot2
Current HA mode: dual, backup
Enter this command to view the status of this backup FortiController and its workers.
Blades:
Ready:
Dead:
Total:
Function:Active
Link:
Base: Down
Fabric: Up
Data: Good
Function:Active
Link:
Base: Down
Fabric: Up
Expert
712

Data: Good
Function:Active
Link:
Base: Down
Fabric: Up
Data: Good
mode: dual
slot: 2
force-state(0:none)
b1 best=yes
local_interface=
b2 best=no

slot: 1
force-state(0:none)
b1 last_hb_
time=82305.93
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead
slot: 1
force-state(0:none)
b1 last_hb_
time=82305.83
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead
713
Expert

slot: 2
force-state(0:none)
b1 last_hb_
time=82305.93
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead

backup FortiController:
To use SSH:
ssh admin@172.20.120.100 -p2221
get system status
v5.0,build0024,140815
Branch Point: 0024
Hostname: ch2-slot1
Time Zone: (GMT-8:00)Pacific Time(US&Canada))
Enter this command to view the status of this backup FortiController and its workers.
Blades:
Working: 3 [ 3 Active
Ready:
0 [ 0 Active
Dead:
0 [ 0 Active
Total:
3 [ 3 Active
Link:
Base: Up
Heartbeat: Management:
Expert
0
0
0
0
Standby]
Standby]
Standby]
Standby]
Function:Active
Fabric: Up
Good
Data: Good
714
Function:Active
Link:
Base: Up
Fabric: Up
Data: Good
Function:Active
Link:
Base: Up
Fabric: Up
Data: Good
mode: dual
slot: 1
force-state(0:none)
b1 best=yes
local_interface=
b2 best=no
slot: 1
force-state(0:none)
b1 last_hb_
time=79145.95
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead
slot: 2
force-state(0:none)
b1 last_hb_
time=79145.99
status=alive
715
Expert
local_interface=
b2 last_hb_time=
0.00
status=dead

slot: 2
force-state(0:none)
b1 last_hb_
time=79145.86
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead

To use SSH:
ssh admin@172.20.120.100 -p2222
get system status
v5.0,build0024,140815
Branch Point: 0024
Hostname: ch2-slot2
Enter this command to view the status of the backup FortiController and its workers.
Blades:
Working: 3 [ 3 Active
Ready:
0 [ 0 Active
Dead:
0 [ 0 Active
Total:
3 [ 3 Active
Expert
0
0
0
0
Standby]
Standby]
Standby]
Standby]
Function:Active
716
Link:
Base: Down
Fabric: Up
Data: Good
Function:Active
Link:
Base: Down
Fabric: Up
Data: Good
Function:Active
Link:
Base: Down
Fabric: Up
Data: Good
mode: dual
slot: 2
force-state(0:none)
b1 best=yes
local_interface=
b2 best=no
slot: 1
force-state(0:none)
b1 last_hb_
time=78273.86
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead
slot: 1
717
Expert
force-state(0:none)
time=78273.85
status=alive
local_interface=
b2 last_hb_time=
b1 last_hb_
0.00
status=dead

slot: 2
force-state(0:none)
b1 last_hb_
time=78273.72
status=alive
local_interface=
b2 last_hb_time=
0.00
status=dead

Balancing Guide.
Expert
718
This example shows how to create a dynamic IPsec VPN tunnel and allowing BGP peering through it.
Expert
719
1. Configuring IPsec in FortiGate 1

Go to Policy & Objects > Objects > Addresses and select create
new Address.
Then create Address Group.
Go to System > Status to look for CLI Console widget and create
phase 1.
config vpn ipsec phase1interface

edit Dialup
set type dynamic
set interface wan1
set mode aggressive
set peertype one
set mode-cfg enable
set proposal 3dessha1 aes128-sha1
set peerid dial
set assign-ip
disable
set psksecret
next
end
Create phase 2.

edit dial_p2
set phase1name Dialup
set proposal 3des-sha1 aes128sha1
set src-addr-type name
set dst-addr-type name
set src-name all
set dst-name VPN_DST
next
end
Expert
720
2. Configuring BGP in FortiGate 1

Go to System > Network > Interfaces and create a Loopback
interface.
BGP route.
config router bgp

set as 100
set router-id 1.1.1.1
config neighbor
edit 10.10.10.10
set ebgp-enforcemultihop enable
set remote-as 200
set update-source loop
next
end
config redistribute connected
set status enable
end
end
3. Adding policies in FortiGate 1

Go to Policy & Objects > Policy > IPv4 and create a policy allowing
BGP traffic from Dialup to loop interfaces.
BGP traffic from loop to Dialup interfaces.
4. Configuring IPSecin FortiGate 2

phase 1.

edit Dialup
set interface wan1
set mode aggressive
set mode-cfg enable
set proposal 3des-sha1 aes128-sha1
set localid dial
set remote-gw 172.20.120.22
set assign-ip disable
set psksecret
next
end
Create phase 2.
721
Expert
edit dial_p2
set phase1name Dialup
set proposal 3des-sha1 aes128sha1
set keepalive enable
next
end
5. Configuring BGP in FortiGate 2

Go to System > Network > Interfaces and create a Loopback
interface.
BGP route.
config router bgp

set as 200
config neighbor
edit 20.20.20.20
set ebgp-enforcemultihop enable
set remote-as 100
set update-source loop
next
end
config redistribute connected
set status enable
end
end
6.Adding policiesin FortiGate 2

BGP traffic from Dialup to loop interfaces.
BGP traffic from loop to Dialup interfaces.
7.Adding a static routein FortiGate 2

Go to Router > Static > Static Routes and add a route to the remote
Loopback interface via Dialup interface.
8. Verifying tunnel is Up
Expert
722
Go to VPN > Monitor > IPsec Monitor to verify that the tunnel is Up.
9. Results
From FortiGate 1, Go to Router > Monitor > Routing Monitor and
verify that routes from FortiGate 2 were successfully advertised to
FortiGate 1 via BGP.
From FortiGate 1, go to System > Status to look for CLI Console
widget and type this command to verify BGP neighbors.
get router info bgp summary

BGP router identifier 1.1.1.1, local
AS number 100
BGP table version is 8
2 BGP AS-PATH entries
0 BGP community entries
Neighbor V AS MsgRcvd
MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
10.10.10.10 4 200 8257
8237 7 0 0 5d00h01m
4
Total number of neighbors 1
From FortiGate 2, go to Router > Monitor > Routing Monitor and

verify that routes from FortiGate 1 were successfully advertised to
FortiGate 2 via BGP.
723
Expert
From FortiGate 2, go to System > Status to look for CLI Console

widget and type this command to verify BGP neighbors.
get router info bgp summary

BGP router identifier 1.1.1.2, local
AS number 200
BGP table version is 11
2 BGP AS-PATH entries
0 BGP community entries
Neighbor V AS MsgRcvd
MsgSent TblVer InQ OutQ Up/Down
State/PfxRcd
20.20.20.20 4 100 8341
8361 10 0 0 5d01h32m
3
Total number of neighbors 1
For further reading, check out IPsec VPN

and Border Gateway Protocol (BGP) in the
Expert
724
This example shows how to create a dynamic IPsec VPN tunnel and allowing OSPF through it.
Expert
725
1. Configuring IPsec in FortiGate 1

Go to System > Status to look for the
CLI Console widget and create phase 1.

edit "dial-up"
set type dynamic
set interface "wan1"
set mode-cfg enable
set proposal 3des-sha1
set add-route disable
set ipv4-start-ip 10.10.101.0
set ipv4-end-ip 10.10.101.255
set psksecret
next
end
Create phase 2.

edit "dial-up-p2"
set phase1name "dial-up"
next
end
Expert
726
2. Configuring OSPF in FortiGate 1

CLI Console widget and create OSPF
route.
config router ospf

config area
edit 0.0.0.0
next
end
config network
edit 1
set prefix 10.10.101.0 255.255.255.0
next
end
config redistribute "connected"
set status enable
end
config redistribute "static"
set status enable
end
end

and create a policy allowing OSPF traffic
from dial-up to port5.
727
Expert

from port5 to dial-up interfaces.
4. Configuring IPSec in FortiGate 2

CLI Console widget and create phase 1.

edit "dial-up-client"
set interface "wan1"
set mode-cfg enable
set proposal 3des-sha1
set add-route disable
set remote-gw 172.20.120.22
set psksecret
next
end
Create phase 2.

edit "dial-up-client-p2"
set phase1name "dial-up-client"
set auto-negotiate enable
next
end
Expert
728
5. Configuring OSPF in FortiGate 2

CLI Console widget and create OSPF
route.
config router ospf

config area
edit 0.0.0.0
next
end
config network
edit 1
set prefix 10.10.101.0 255.255.255.0
next
end
config redistribute "connected"
set status enable
end
config redistribute "static"
set status enable
end
end

from dial-up-client to port5.
729
Expert

from port5 to dial-up-client interfaces.
8. Verifying tunnel is up
Go to VPN > Monitor > IPsec Monitor
to verify that the tunnel is Up.
9. Results
From FortiGate 1, go to Router >
Monitor > Routing Monitor and verify
that routes from FortiGate 2 were
successfully advertised to FortiGate 1
via OSPF.
From FortiGate 1, go to System > Status get router info ospf neighbor
to look for the CLI Console widget and
OSPF process 0:
type this command to verify OSPF
Neighbor ID Pri State Dead Time Address Interface
neighbors.
172.20.120.25 1 Full/ - 00:00:34 10.10.101.1
dial-up_0
From FortiGate 2, go to Router >
Monitor > Routing Monitor and verify
that routes from FortiGate 1 were
successfully advertised to FortiGate 2
via OSPF.
Expert
730
From FortiGate 2, go to System > Status get router info ospf neighbor
to look for the CLI Console widget and
OSPF process 0:
type this command to verify OSPF
Neighbor ID Pri State Dead Time Address Interface
neighbors.
172.20.120.22 1 Full/ - 00:00:30 10.10.101.2
dial-up-client
For further reading, check out IPsec VPN

and Open Shortest Path First (OSPF) in the
731
Expert
Single Sign-on using LDAPand FSSOagent in

advanced mode
This recipe illustrates FortiGate user authentication with FSSO. In this example, user authentication controls
Internet access and applies different security profiles for different users.
Expert
732
1. Integrating the FortiGate with the LDAP server

> LDAP Servers to configure the LDAP
server.
2. Installing FSSO agent on Windows AD server

Accept the license and follow the
Wizard.
Enter the Windows AD administrator
password.
Expert
733
Select the Advanced Access method.
In the Collector Agent IP address field,

enter the IP address of the Windows AD
server.
734
Expert
Select the domain you wish to monitor.
Next, select the users you do not wish to

monitor.
Expert
735
Under Working Mode, select DC Agent

mode.
Reboot the Domain Controller.
736
Expert
Upon reboot, the collector agent will start

up.
You can choose to Require
authenticated connection from
FortiGate and set a Password.
3. Configuring Single Sign-On on the FortiGate

SSO server.
Under Groups tab, select the user
groups to be monitored. In this example,
"FortiOS Writers" group is used.
4. Creating a user group in the FortiGate

Groups to create a new FSSO user
group.
Under Members, select the "FortiOS_
Writers" group created earlier.
Expert
737
5. Adding a policy in the FortiGate

and create a policy allowing "FortiOS_
writers" to navigate the Internet with
appropriate security profiles.
default Web Filter security profile is
used in this example.
738
Expert
9. Results
Have users log on to the domain, go to
the FSSO agent, and select Show
Logon Users.
From the FortiGate, go to System >

Status to look for the CLI Console
widget and type this command for more
detail about current FSSO logons:
diagnose debug authd fsso list

----FSSO logons---IP: 10.10.20.3 User: ADMINISTRATOR Groups:
CN=FORTIOS WRITERS,CN=USERS,DC=TECHDOC,DC=LOCAL
Workstation: WIN2K8R2.TECHDOC.LOCAL MemberOf:
FortiOS_Writers
IP: 10.10.20.7 User: TELBAR Groups: CN=FORTIOS
WRITERS,CN=USERS,DC=TECHDOC,DC=LOCAL Workstation:
TELBAR-PC7.TECHDOC.LOCAL MemberOf: FortiOS_
Writers
Total number of logons listed: 2, filtered: 0
----end of FSSO logons----
From the FortiGate, go to User & Device

> Monitor > Firewall and verify FSSO
Logons.
Expert
739
Have users go to the Internet and the

security profiles will be applied
accordingly.
Forward Traffic to verify the log.
740
Expert
Single Sign-On using FSSO agent in advanced mode

and FortiAuthenticator
This recipe demonstrates FortiGate user authentication with FSSO and the use of FortiAuthenticator as an LDAP
server. In this example, user authentication controls Internet access and applies different security profiles for
different users.
Expert
741
1. Configuring an LDAP directory on the FortiAuthenticator

Management > Local Users to create a
users list. Make sure to enable Allow
LDAP browsing.
Expert
742

Management > User Groups to create
a user group and add users to it.
"FortiOS_Writers" user group is used in
this example.
Go to Authentication > LDAP Service >

Directory tree and configure the LDAP
directory tree.
743
Expert
2. Integrating the FortiGate with the FortiAuthenticator

> LDAP Servers and configure the
LDAP server.
3. Installing the FSSO agent on the Windows AD server

Accept the license and follow the
Wizard.
Enter the Windows AD administrator
password.
Expert
744
Select the Advanced Access method.
In the Collector Agent IP address field,

enter the IP address of the Windows AD
server.
745
Expert
Select the domain you wish to monitor.
Next, select the users you do not wish to

monitor.
Expert
746
Under Working Mode, select DC Agent

mode.
Reboot the Domain Controller.
747
Expert
Upon reboot, the collector agent will start

up.
You can choose to Require
authenticated connection from
FortiGate and set a Password.
4. Configuring Single Sign-On on the FortiGate

SSO server.
Under Groups tab, select the user
groups to be monitored. In this example,
"FortiOS_Writers" group is used.
5. Creating a user group in the FortiGate

Groups to create new user group. Under
Remote groups, add the remote LDAP
server created earlier in the
FortiAuthenticator (in this example it's
called "FAC_LDAP").
Expert
748

default Web Filter security profile is
749
Expert
7. Results
Have users log on to the domain, go to
the FSSO agent, and select Show
Logon Users.
From the FortiGate, go to System >

Status to look for the CLI Console
widget and type this command for more
detail about current FSSO logons:
Expert
diagnose debug authd fsso list

----FSSO logons---IP: 10.10.20.3 User: ADMINISTRATOR Groups: CN=FORTIOS
WIN2K8R2.TECHDOC.LOCAL MemberOf: FortiOS_Writers
IP: 10.10.20.7 User: TELBAR Groups: CN=FORTIOS
TELBAR-PC7.TECHDOC.LOCAL MemberOf: FortiOS_Writers
Total number of logons listed: 2, filtered: 0
----end of FSSO logons----
750
Have users belonging to the "FortiOS_

Writes" user group navigate the Internet.
An authentication portal is presented to
allow only authorized users. Security
profiles will be applied accordingly.
Upon successful authentication, from the

FortiGate, go to User & Device >
Monitor > Firewall and verify FSSO
Logons.
751
Expert
Expert
752
SSOusing a FortiGate, FortiAuthenticator, and

DCPolling
This recipe demonstrates FortiGate user authentication with the use of a FortiAuthenticator as a Single Sign-On
server. In this example, the FortiAuthenticator is configured to collect the user logon by polling the Domain
Controller logs. User authentication controls Internet access and applies different security profiles for different
users.
Expert
753
1. Configuring the FortiAuthenticator

Go to Fortinet SSO Methods > SSO >
General to configure general settings as
shown in the exhibit.

Domain Controllers and add the
Windows AD to the FortiAuthenticator.
Expert
754
Go to Authentication > Remote Auth.

Servers > LDAP to set the Windows AD
as an LDAP server. This will be useful to
import SSO Filtering Objects from
Windows AD to the FortiAuthenticator.

FortiGate Filtering and create a new
FortiGate Filtering.
Under Fortinet Single Sign-On
(FSSO), enable Forward FSSO
information for users from the
following subset of
users/groups/containers only.
Under SSO Filtering Objects, select
Import, in the Remote LDAP Server
field, select the LDAP server created
earlier in the previous step (WinLDAP in
this example) and select Apply.
Next, select groups or containers to be
imprted, controlled and monitored by the
FortiAuthenticator. In this example the
"FortiOS Writers" user group is selected.
755
Expert
2. Configuring SSO on the FortiGate

SSO server.
In the Type field, select Fortinet SingleSign-On Agent.
When selecting the Users/Groups field,
the SSO user groups initially polled by
the FortiAuthenticator from the Domain
Controller, shows up in the FortiGate.
In this example, only the "FortiOS
writers" group shows up because of the
FortiGate Filtering configured in the
previous step.
Expert
756
3. Creating a user group on the FortiGate

Under Members, select the user group
to be monitored. In this example only
"FortiOS Writers" shows up because of
the FortiGate Filtering configured
earlier.

The default Web Filter security profile is
5. Results from the FortiAuthenticator

Go to Monitor > SSO > Domains to
verify monitored domains. In this
Example "techdoc.local" is monitored by
757
Expert
Have users log on to the domain, and go

to Monitor > SSO > SSO Sessions and
verify SSO sessions.
Go to Logging > Log Access > Logs to

verify logs.
You can also verify results in the User

inventory widget under System >
Dashboard > Status.
Expert
758
6. Results from the FortiGate

Upon successful authentication, go to
User & Device > Monitor > Firewall and
verify FSSO Logons.
Have authenticated user navigate the
Internet. Security profiles will be applied
accordingly.
759
Expert

In this expert cookbook article and an included example recipe, we will explore a scalable approach to setting up a
large number of spoke VPNs by using quick mode selector source definitions on the spoke FortiGates and the
dialup VPN configurations on the hub FortiGates.
We will also explore how redundant spoke VPN tunnels can be configured in order to offer maximum redundancy
for environments with critical availability requirements. We will be authenticating the VPN tunnels using X-Auth in
order to ensure separate credentials for each spoke.
This recipe is based on FortiOS firmware version 5.2, so some of the steps shown may not be the same as with
other versions of the firmware.
Thesample topology for this advanced cookbook article follows:
This topology consists of 2 hub networks and 2 spoke networks, using private IP ranges, separated by a
simulated Internet, with 100.64.0.0/16 representing the Internet. Each FortiGate also has a loopback interface
that is routable across the VPN.
The diagram topology shows the VPN tunnels along with their redundant links:
l
The reddotted line showing the VPN tunnel connection between the primary and backup datacenters; in
this case, our two hubs.
The bluedotted line showing the VPN tunnel connection between the primary datacenter and the branch
offices; the spokes in the scenario.
The orangedotted line shows the VPN tunnel connection between the backup datacenter and the branch
offices.
While the topology shown in the diagram can be built using individual static tunnels between each site, this would
not scale well if addition spokes grow to a significant number. There would also be limited support for dynamically
addressed sites. This strategy put forth by this article offers a solution to these issues by using a single phase 1
dialup definition on the hub FortiGates with additional spoke tunnels being added, without any changes to the hubs
beyond that of adding additional user accounts for each additional spoke.
Spoke authentication is maintained by with X-Auth, which keeps the authentication of the individual tunnels
separate in such a way that the use of a Pre-Shared Key alone is insufficient to authenticate a tunnel. A Public
Key Infrastructure can also be used, provided that separate key-pairs are used for each VPN tunnel to maintain
the segregation of the spokes.
The key points of this design are:
l
Expert
Each hub FortiGate is configured with a dialup interface-mode Phase1 using X-Auth.
760
Each spoke has its own user account on the hub FortiGates. In this example, local accounts are used on
each hub, but a RADIUS or LDAP authentication server could be used on the back end, eliminating the
need to managed the accounts on the FortiGates.
Spoke FortiGates are configured to propagate their local subnets using quick mode selectors (specifically,
a source object).
When a new spoke tunnel is connected, the hub FortiGate validates the shared secret along with the XAuth credentials provided by the spoke FortiGate.
Spokes FortiGates can have dynamically assigned IP addresses such as those given out by DSL or cable
ISPs.
The hub FortiGates each insert a reverse route pointing to newly established tunnel interfaces, for any of
the subnets provided by the spoke FortiGate's source quick mode selectors.
Each spoke FortiGate uses configured static routes to direct traffic that needs to go to the datacenter(s)
through the VPN tunnels destined for the hubs. The static route to the backup hub is set to a higher priority
number value, making it the less preferred route. There is also an option where you can send all of your
traffic from the spokes through the VPN tunnel by default. This can be done by configuring the WAN interface to route all traffic through the public IP address of the hub FortiGate. This is what our example configuration is set to do.
We need to aware of any potential points where asymmetrical routing could occur as it relates to traffic
returning to the spokes (This is essentially the response to a request coming back through a different route
than it took to get there). This can be a potential problem especially when communicating to hosts that are
connected to both data centers and we happen to be redistributing spoke routes using a dynamic routing
protocol with hub sites using OSI Layer 3 networking devices. In this case, we would ensure that the
backup hub's redistributed routes are less preferred than the primary hub's routes. In all cases, it is important to have a clear view of the routing flows between each endpoint and to keep "diag debug flow" in our
toolbox to diagnose those potentialasymmetric routing issues. In our example, we would want to route
traffic destined to resources in each respective hub directly to thathub, rather than have it cross the interdatacenter VPN tunnel, and have default routing flow to the primary hub under normal circumstances.
The Hub FortiGates

Let's look at the relevant configuration points of the hub FortiGates (These will be identical on each hub FortiGate:
While the GUI can be used for these steps, we are going to use the CLI to keep things simple and avoid potential
confusion that may be caused by changes in the GUI's layout.
Create the IPsec tunnel:

edit "SPOKES"
set type dynamic
set interface "port1"
set mode aggressive
set peertype one
761
Expert
set proposal aes256-sha256

set xauthtype auto
set authusrgrp "SPOKE-GRP"
set peerid "SPOKES"
set psksecret SuperSecretSpokeSecret
next
end
edit "SPOKES-P2"
set phase1name "SPOKES"
next
end
Create a user for each of the spokes:

config user local
edit "SPOKE1"
set type password
set passwd Spoke1SuperSecret
next
edit "SPOKE2"
set type password
set passwd Spoke2SuperSecret
next
end
Create a user group and include the spoke members:

config user group
edit "SPOKE-GRP"
set member "SPOKE1" "SPOKE2"
next
end
Expert
762
Create the firewall policies

edit 1
set srcintf "port2" "loop0"
set dstintf "SPOKES"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ALL"
next
edit 2
set srcintf "SPOKES"
set dstintf "port2" "loop0"
set srcaddr "all"
set dstaddr "all"
set action accept
set service "ALL"
next
end
Afew of the above configuration aspects require further explanation:
l
Aggressive mode: We are using this mode in order to ensure that these dialup spokes are terminated on
the right dialup phase1. If the hub unit has other dialup phase1 (for FortiClient VPN users, for instance), the
hub would otherwise be unable to distinguish between each dialup phase1.Afew of the above configuration
aspects require further explanation:
X-Auth: As previously stated, this allows us to authenticate each connecting spoke unit to a local group,
which is defined in the above configuration as currently containing two user accounts (our example has
twospokes). Provisioning additional spokes on the hub would simply involve adding additional user
accounts.
Policies: As usual, we must always configure policies in order for traffic to flow. IPsecPhase1 follows a
special rule in which tunnels will not even attempt to come up unless they have at least one policy referring
to them (this happens to be a good trick to know when you want to disable an IPsec VPN tunnel without
deleting its configuration).
The Spoke FortiGates

With the hub FortiGates configured and ready for incoming connections, the spoke FortiGates can be configured.
Below is the steps for configuring SPOKE1. To configure additional spoke FortiGates change the unit specific
information.
763
Expert
Create the IPsec tunnel

edit "HUB-PRIMARY"
set mode aggressive
set localid "SPOKES"
set xauthtype client
set authusr "SPOKE1"
set authpasswd Spoke1SuperSecret
set mesh-selector-type subnet
set remote-gw100.64.10.2
next
edit "HUB-BACKUP"
set mode aggressive
set localid "SPOKES"
set xauthtype client
set authusr "SPOKE1"
set authpasswd Spoke1SuperSecret
set remote-gw100.64.11.2
next
end
edit "PRIMARY-P2"
set phase1name "HUB-PRIMARY"
set src-name "VPN_SUBNETS"
set dst-name "all"
next
edit "BACKUP-P2"
set phase1name "HUB-BACKUP"
Expert
764
set src-name "VPN_SUBNETS"

set dst-name "all"
next
end
Creating addresses for the subnets

edit "NET_192.168.12.0/24"
set subnet 192.168.12.0 255.255.255.0
next
edit "NET_100.64.254.12/32"
set subnet 100.64.12.254255.255.255.255
next
end
Creating an address group for the subnets

edit "VPN_SUBNETS"
set member "NET_100.64.254.12/32" "NET_192.168.12.0/24"
next
end
Configuring static routes

Use edit 0 to create a route with the next unused number.
config router static
edit 0
set dst 100.64.11.2255.255.255.255
set device "port1"
next
edit 0
set dst100.64.10.2255.255.255.255
set device "port1"
next
edit 0
set device "HUB-PRIMARY"
next
edit 0
set device "HUB-BACKUP"
set priority 20
next
end
765
Expert
Configuringthe firewall policies

Use edit 0 to create a policy with the next unused number.
edit 0
set dstintf "HUB-PRIMARY"
set srcaddr "all"
set dstaddr "all"
set action accept
set service "ALL"
next
edit 0
set srcintf "HUB-PRIMARY"
set srcaddr "all"
set dstaddr "all"
set action accept
set service "ALL"
next
edit 0
set dstintf "HUB-BACKUP"
set srcaddr "all"
set dstaddr "all"
set action accept
set service "ALL"
next
edit 0
set srcintf "HUB-BACKUP"
set srcaddr "all"
set dstaddr "all"
set action accept
set service "ALL"
next
end
Each spoke configuration calls for similar Phase1 parameters, but differs for the rest of the configuration in a few
keys areas:
Expert
766
Aggressive mode: As the hub is validating the inbound ID, we have configured our peer ID to the matching
string "SPOKES".
X-Auth: Our spokes are acting as X-auth clients, and each of our unit is using distinct credentials passed
to the hub device during IKE phase1 negotiation.
Phase 2 quick mode selectors:As the title of this recipe suggests, this is where the spoke provisioning
routing automation happens. We've defined address objects, added them to a group, and performed the configuration found in Phase2. There is however a peculiarity where if we have more than one subnet behind
our spoke unit, the "set mesh-selector-type subnet" command must be configured to ensure multiple
Phase2 SAs are negotiated for each subnet listed in our group.
Routing: As previously expressed, we have configured our default routing to flow through the primary hub
(blue links) and failover routing to the backup hub (orange links, using route priority adjustment). Notice
that we are explicitly routing each hub's public IP through the public Internet to ensure that traffic will not
flow through the VPN tunnel (and result in flapping).
Where the spoke configurations will be different

As explained earlier, the spoke FortiGate configurations will be slightly different on each individual spoke. The
settings will be similar on all of the spoke with the following exceptions:
l
X-Auth:Our spokes are acting as X-auth clients, and each of our unit is using distinct credentials passed to the hub device during IKE
phase1 negotiation.

edit "HUB-PRIMARY"
set authusr (The account will be the one associated with the specific spoke)
set authpasswd (The password will be the one associated with the specific spoke)
next
edit "HUB-BACKUP"
set authusr (The account will be the one associated with the specific spoke)
set authpasswd (The password will be the one associated with the specific spoke)
next
end
l
Phase 2 quick mode selectors:This is where the spokerouting automation happens. We've defined address objects, added
them to a group, and performed the configuration found in Phase2. There is however a peculiarity where if we have more than one
subnet behind our spoke unit, the followingsetting must be used to ensure multiple Phase2 SAs are negotiated for each subnet listed
in our group:

edit <name>
end
end
767
Expert
Routing:This wont necessarily be different between the different spoke FortiGates, but as previously mentioned, in this example
recipe we have configured our default routing to flow through the primary hub and failover routing to the backup hub. Notice that we
are explicitly routing each hub's public IP through the public Internet to ensure that traffic will not flow through the VPN tunnel (and result in flapping).
Results
And this concludes our VPN configuration! But this recipe would not be complete without a very important
verification step. Lets look at the routing table on the hub:
HUB # get router info routing-table all
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default
S* 0.0.0.0/0 [10/0] via 192.168.56.2, port1
S
100.64.254.12/32 [15/0] is directly connected, HUB_0S
100.64.254.13/24 [15/0] is directly connected, HUB_1
C 192.168.11.0/24 is directly connected, port2
S 192.168.12.0/24 [15/0] is directly connected, HUB_0S
192.168.13.0/24 [15/0] is directly connected, HUB_1
As can be seen above, our spoke subnets have been automatically injected into the hub's routing tables. A closer
look at the VPN details of one spoke confirms that the hub received the negotiated subnets during quick mode
negotiation and inserted distinct SAs for each SA.
FGT1 # get vpn ipsec tunnel details
gateway
name: 'HUB_0'
type: route-based
local-gateway: 192.168.56.11:0 (static)
remote-gateway: 192.168.56.12:0 (dynamic)
mode: ike-v1
interface: 'port1' (2)
rx packets: 56 bytes: 8736 errors: 0
tx packets: 41 bytes: 3444 errors: 0
dpd: enabled/negotiated idle: 5000ms retry: 3 count: 0
selectors
name: 'HUB-P2'
auto-negotiate: disable
mode: tunnel
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:192.168.12.0-192.168.12.255:0
--------OUTPUT TRUNCATED-------selectors
name: 'HUB-P2'
auto-negotiate: disable
mode: tunnel
src: 0:0.0.0.0-255.255.255.255:0
dst: 0:100.64.254.12-100.64.254.12:0
Expert
768
--------OUTPUT TRUNCATED-------If you require communication between the spokes, this can be routed through the hub FortiGates. The only change
to the example recipe's configuration is an addition policy on each of the hub FortiGates which defines the both the
Incoming Interface and the Outgoing Interface as the VPN Dialup Interface (in this example, SPOKES)
On the Spoke FortiGates, once the poke tunnels have been established, you can see the default route to the
primary datacenter and the alternate though less preferred route to the backup datacenter by running the
commandget router info routing-table all
FGT-SPOKE-1 # get router info routing-table all
S* 0.0.0.0/0 [10/0] is directly connected,HUB-PRIMARY
[10/0] is
directly connected, HUB-BACKUP, [20/0]
S 100.64.10.2/32 [10/0] is directly connected, port1
C 100.64.254.12/32 is directly connected, lo0
We can test the failover function by shutting down the port1 interface on the primary hub. This will bring down the
VPN between the primary hub and the spokes. Once the DPD detects the fault, traffic switches over to the
backup hub as shown here:
FGT-SPOKE-1 # get router info routing-table all
S* 0.0.0.0/0 [10/0] is directly connected,HUB-BACKUP, [20/0]
C 100.64.254.12/32 is directly connected, lo0C 192.168.12.0/24 is directly
connected, port2
Final notes
l
769
The technique shown here does not involve dynamic routing so this configuration and its very straight forward template can be easily used to scale up the topology to include thousands of spoke sites.
To make it even easier, this configuration can be entirely built and automated with FortiManager, which has
support for provisioning hub-and-spoke dialup topologies.
Expert
Glossary
BGP:
Border Gateway Protocol is primarily used to connect the networks of large organizations that have two or more
ISP connections, or between other autonomous systems. If used in such a situation, a FortiGate can use BGP
for routing.
BYOD:
Bring Your Own Device (also called device management) is the practice of allowing network users to access an
organizations (usually wireless) network with their own computers, smart phones, tablets and other devices.
BYOD has a major impact on networks with large and diverse user bases, such as educational institutions, but
also affects large and small business networks.
CA:
A certificate authority (CA) is an entity that issues digital certificates, which are used to establish secure
connections over a network, typically the Internet. The CA acts as a trusted third-party by verifying the identity of
a certificates owner: for example, the certificate found when you go to https://www.facebook.com is verified as
belonging to Facebook.
Certificates:
In networking, certificates (including public key certificates, digital certificates, and identity certificates) provide
digital signatures for websites or other electronic communication and allow you to verify whether a digital identity
is legitimate.. A FortiGate can use certificates for many things, including SSL inspection and user authentication.
CLI:
The Command Line Interface is a text-based interface used to configure a FortiGate unit. Most steps in the
FortiGate Cookbook use the Graphical User Interface (see GUI), but some configuration options are only
available using the CLI.
DHCP:
Dynamic Host Configuration Protocol is a networking protocol that allows devices to request network
parameters, such as IP addresses, automatically from a DHCP server, reducing the need to assign these
settings manually. A FortiGate can function as a DHCP server for your network and can also receive its own
network parameters from an external DHCP server.
Dial-up/dynamic
VPN:
A dial-up VPN, also called a dynamic VPN, is a type of IPsec VPN where one of the endpoints has a dynamic IP
address.
DMZ:
A Demilitarized Zone is an interface on a FortiGate unit that provides external users with secure access to a
protected subnet on the internal network without giving them access to other parts of the network. This is most
commonly done for subnets containing web servers, which must be accessible from the Internet. The DMZ
interface will only allow traffic that has been explicitly allowed in the FortiGates configuration. FortiGate models
that do not have a DMZ interface can use other interfaces for this purpose.
DNS:
Domain Name System is used by devices connecting to the Internet to locate websites by mapping a domain
name to a websites IP address. For example, a DNS server maps the domain name www.fortinet.com to the IP
address 66.171.121.34. Your FortiGate unit controls which DNS servers the network uses. A FortiGate can also
function as a DNS server.
DSR:
In a typical load balancing scenario, server responses to client requests are routed through a load balancer on
their way back to the client. The load balancer examines the headers of each response and can insert a cookie
before sending the server response on to the client. In a Direct Server Return (DSR) configuration, the server
receiving a client request responds directly to the client IP, bypassing the load balancer. Because the load
balancer only processes incoming requests, load balancing performance is dramatically improved when using
Glossary
770
DSR in high bandwidth applications. In such applications, it is not necessary for the load balancer to receive and
examine the servers responses. So the client makes a request and the server simply streams a large amount of
data to the client.
Dynamic IP
address:
A dynamic IP address is one that can change without the devices user having to do anything. Dynamic IP
addresses allow networks to control the IP addresses of devices that connect to them. This allows you to connect
portable devices to different networks without needing to manually change their IP addresses.
Dynamic IP addresses are set by network protocols, most often DHCP.
ECMP:
Equal Cost Multipath Routing allows next-hop packet forwarding to a single destination to occur over multiple
best paths that have the same value in routing metric calculations. ECMP is used by a FortiGate for a variety of
purposes, including load balancing.
Explicit Proxy:
Explicit proxy is a type of configuration where all clients are configured to allow requests to go through a proxy
server, which is a server used as an intermediary for requests from clients seeking resources from other
servers. When a FortiGate uses explicit proxy, the clients sending traffic are given the IP address and port
number of the proxy server.
FGCP:
FortiGate Clustering Protocol is used for high availability (HA).
FortiAP:
A FortiAP unit is a wireless Access Point that can be managed by a FortiGate. Most FortiAP functions can also
been accomplished using a FortiWiFi unit.
FortiClient:
The FortiClient software provides a variety of features, including antivirus, web filtering, firewall, and parental
controls, to individual computers and mobile devices. It can also be used to connect to a FortiGate using either an
SSL or IPsec VPN.
FortiClient is available for Windows, Mac OSX, iOS, and Android, and can be set up quickly. After being installed,
it automatically updates its virus definition files, does a full system scan once per week, and much more.
FortiClient can be downloaded at www.forticlient.com.
FortiOS:
FortiOS is the operating system used by FortiGate and FortiWiFi units. It is also referred to as firmware.
FTP:
File Transfer Protocol is a standard protocol used to transfer computer files from one host to another host over a
computer network, usually the Internet, using FTP client and server applications.
Gateway:
A gateway is the IP address that traffic is sent to if it needs to reach resources that are not located on the local
subnet. In most FortiGate configurations, a default route using a gateway provided by an Internet service
provider must be set to allow Internet traffic.
GUI:
The Graphical User Interface, also known as the web-based manager, is a graphics-based interface used to
configure a FortiGate unit and is an alternative to using the Command Line Interface (see CLI). You can connect
to the GUI using either a web browser or FortiExplorer. Most steps in the FortiGate Cookbook use the GUI.
HTTP:
Hypertext Transfer Protocol is a protocol used for unencrypted communication over computer networks,
including the Internet, where it is used to access websites. FortiGate units handle more HTTP traffic than any
other protocol.
771
Glossary
HTTPS:
Hypertext Transfer Protocol Secure is a protocol that secures HTTP communications using the Secure Sockets
Layer (SSL) protocol. HTTPS is the most commonly used secure communication protocol on the Internet.
Interfaces:
Interfaces are the points at which communication between two different environments takes place. These points
can be physical, like the Ethernet ports on a FortiGate, or logical, like a VPN portal.
IPaddress:
An Internet Protocol address is a numerical label assigned to each device participating in a computer network
that uses the Internet Protocol for communication. FortiGate units can use IP addresses to filter traffic and
determine whether to allow or deny traffic. Both IP version 4 and IP version 6 (see IPv4 and IPv6) are supported
by your FortiGate.
IPsec:
Internet Protocol Security is used to for securing IP communications by authenticating and encrypting each
packet of a session. A FortiGate primarily uses this protocol to secure virtual private networks (see VPN).
IPv4:
Internet Protocol version 4 is the fourth version of the Internet Protocol (IP), the main protocol used for
communication over the Internet. IPv4 addresses are 32-bit and can be represented in notation by 4 octets of
decimal digits, separated by a period: for example, 172.16.254.1.
IPv6:
Internet Protocol version 6 is the sixth version of the Internet Protocol (IP), the main protocol used for
communication over the Internet (IPv5 never became an official protocol). IPv6 was created in response to the
depletion of available IPv4 addresses. IPv6 addresses are 128-bit and can be represented in notation by 8
octets of hexadecimal digits, separated by a colon: for example, 2001:db8:0000:0000:0000:0000:0000:0000.
IPv6 addresses can be shortened if all the octets are 0000; for example, the previous address can also be
written as 2001:db8::
LAN/internal:
The LAN/internal interface is an interface that some FortiGate models have by default. This interface contains a
number of physical ports that are all treated as a single interface by the FortiGate unit. This allows you to
configure access for the entire Local Area Network at the same time, rather than configuring each port
individually.
LDAP:
Lightweight Directory Access Protocol is a protocol used for accessing and maintaining distributed directory
information services over a network. LDAP servers are commonly used with a FortiGate for user authentication.
MAC address:
A Media Access Control address is a unique identifier assigned to a network interface used for network
communication. A MAC address is assigned to a device by the manufacturer and so this address, unlike an IP
address, is not normally changed. MAC addresses are represented in notation by six groups of two hexadecimal
digits, separated by hyphens or colons: for example, 01:23:45:67:89:ab. Your FortiGate can identify network
devices using MAC addresses.
Multicast:
Multicast is a method of group communication where information is addressed to a group of destinations

simultaneously. A FortiGate can use multicast traffic to allow communication between network devices.
NAT:
Network Address Translation is a process used to modify, or translate, either the source or destination IP
address or port in a packet header. The primary use for NAT is to allow multiple network devices on a private
network to be represented by a single public IP address when they browse the internet. FortiGate also supports
many other uses for NAT.
Netmask
A netmask, or subnet mask, is the part of an IP address that is used to determine if two addresses are on the
same subnet by allowing any network enabled device, such as a FortiGate, to separate the network address and
the host address. This lets the device determine if the traffic needs to be sent through a gateway to an external
network or if it is being sent to host on the local network.
Glossary
772
Packet:
A packet is a unit of data that is transmitted between communicating devices. A packet contains both the
message being sent and control information, such as the source address (the IP address of the device that sent
the packet) and the destination address (the IP address of the device the packet is being sent to).
Ping:
Ping is a utility used to test whether devices are connected over a IP network and to measure how long it takes
for a reply to be received after the message is sent, using a protocol called Internet Control Message Protocol
(ICMP). If ICMP is enabled on the destination interface, you can ping the IP address of a FortiGate interface to
test connectivity between your computer and the FortiGate. You can also use the CLI command execute ping
to test connectivity between your FortiGate and both internal and external devices.
Ports:
See Interfaces and Port Numbers.
Port numbers:
Port numbers are communication endpoints used to allow network communication. Different ports are used for
different application-specific or process-specific purposes; for example, HTTP protocol commonly uses port 80.
Pre-shared key:
In cryptography, a pre-shared key is a character string (like a password) known by two parties, and used by
those parties to identify each other. Pre-shared keys are commonly used for granting access to IPsec VPNs and
WiFi networks.
Pre-shared keys are different from regular passwords because they are not normally associated with a specific
individuals credentials.
RADIUS:
Remote Authentication Dial In User Service is a protocol that provides centralized Authentication, Authorization,
and Accounting (AAA) management for users that connect and use a network service. RADIUS servers are
commonly used with a FortiGate for user authentication, including single-sign on.
RTSP:
The Real Time Streaming Protocol is a media control protocol that is used for controlling streaming audio and
video streams. RTSP has a wide range of uses and is often leveraged by other media-related services such as
SIP. It most commonly uses TCP and UDP port 554 but additional ports are used by the actual media controlled
by RTSP.
FortiOS includes an RSTP session helper that opens the ports used by individual RTSP-controlled streams.
FortiRecorder and FortiCamera use RTSP for video streaming.
SCTP:
The Stream Control Transmission Protocol is a transport layer protocol (protocol number 132) used most often
for sending telephone signalling messages over carrier IP networks.
Session:
A session is the dialogue between two or more communicating devices that include all messages that pass
between the devices; for example, a session is created when a user browses to a specific website on the Internet
for all communication between the users computer and the web server that hosts the site. Sessions are tracked
by a FortiGate unit in order to create logs about the network traffic.
SIP:
Session Initiation Protocol is used for controlling multimedia communication sessions such as voice and video
calls over Internet Protocol networks. FortiGate units use this protocol for voice over IP (see VoIP).
Site-to-site
VPN:
A site-to-site VPN allows two networks that are each behind a VPN gateway (for example, a FortiGate unit), to
establish secure connections with each other over a public network, typically the Internet.
Site-to-site VPNs most often use IPsec and can be established between two FortiGates, or between a FortiGate
and any other IPsec VPN gateway, such as a Cisco ASA or Microsoft Azure.
773
Glossary
SLAAC:
Stateless Address Autoconfiguration is a feature of IPv6 that allows devices on an IPv6 network to automatically
get IPv6 addresses. SLAAC is similar to DHCP except that DHCP requires you to run and configure a DHCP
server. SLAAC is built into IPv6 and requires only minor additional configuration. SLAAC is defined by RFC
2462.
SNMP:
Simple Network Management Protocol is a protocol that monitors hardware on your network. A FortiGate can
use SNMP to monitor events such as high CPU usage, VPN tunnels going down, or hardware becoming
disconnected.
SSH:
Secure Shell is a protocol used for secure network services between two devices, including remote commandline access. SSH can be used to access a FortiGates command line interface (CLI).
SSID:
A Service Set Identifier is the name that a wireless access point broadcasts to wireless users. Wireless users
select this name to join a wireless network.
SSL:
Secure Sockets Layer is a protocol for encrypting information that is transmitted over a network, including the
Internet. SSL can be used for secure communications to a FortiGate, as well as for encrypting Internet traffic
(see HTTPS) and for allowing remote users to access a network using SSL virtual private network (see VPN).
SSLinspection:
Secure Sockets Layer inspection is used by your FortiGate to scan traffic or communication sessions that use
SSL for encryption, including HTTPS protocol.
SSO:
Single Sign-On is a feature that allows a user to login just once and remembers the credentials to re-use them
automatically if additional authentication is required. A FortiGate supports both Fortinet single sign-on (FSSO)
and single sign-on using a RADIUS server (RSSO).
Static IP
address:
Static IP addresses require user intervention to change. Normally a device that always has a wired connection to
an Ethernet network has a static IP address.
Static route:
A static route is a manually-configured routing entry that is fixed and does not change if the network is changed
or reconfigured.
Subnet:
A subnetwork, or subnet, is a segment of the network that is separated physically by routing network devices
and/or logically by the difference in addressing of the nodes of the subnet from other subnets. Dividing the
network into subnets helps performance by isolating traffic from segments of the network where it doesnt need
to go, and it aids in security by isolating access. The addressing scope of a subnet is defined by its IP address and
subnet mask and its connection to other networks is achieve by the use of gateways.
Subnet Mask:
A subnet mask is the part of an IP address that is used to determine if two addresses are on the same subnet by
allowing any network enabled device, such as a FortiGate, to separate the network address and the host
address. This lets the device determine if the traffic needs to be sent through a gateway to an external network
or if it is being sent to host on the local network.
traceroute
traceroute is a diagnostic tool used to display the route of packets across an IP network and measure transit
delays. traceroute can be useful to troubleshoot a connection and determine where an error is occurring.
Transport layer
protocol
A transport layer protocol provides end-to-end communication on top of the network layer (IP) layer for IP
networks. Using a FortiGate, you can create security policies that control the following transport layer protocols:
TCP (protocol number 6), UDP (protocol number 17), ICMP (protocol number 1), and SCTP (protocol number
132).
Glossary
774
URL:
A Uniform Resource Locator is a text string that refers to a network resource. The most common use for URLs is
on the Internet, where they are also known as web addresses.
URLs are used by a FortiGate to locate websites on the Internet and can also be used in web filtering to block
specific sites from being accessed.
VDOM:
Virtual Domains are used to divide a single FortiGate unit into two or more virtual instances of FortiOS that
function separately and can be managed independently.
VLAN:
Virtual Local Area Networks are used to logically divide a single local area network (LAN) into different parts that
function independently. A FortiGate uses VLANs to provide different levels of access to users connecting to the
same LAN.
VoIP:
Voice over Internet Protocol is a protocol that is used to allow voice communications and multimedia sessions
over Internet Protocol sessions, including the Internet. VoIP protocol is used by a FortiGate when traffic needs to
reach a connected VoIP phone or FortiVoice unit.
VPN:
A Virtual Private Network is a private network that acts as a virtual tunnel across a public network, typically the
Internet, and allows remote users to access resources on a private network. There are two main types of VPNs
that can be configured using a FortiGate unit: IPsec VPN (see IPsec) and SSL VPN (see SSL).
WAN/WAN 1:
The WAN or WAN1 port on your FortiGate unit is the interface that is most commonly used to connect the
FortiGate to a Wide Area Network, typically the Internet. Some FortiGate models have a WAN2 port, which is
commonly used for redundant Internet connections.
775
Glossary
The FortiGate Cookbook contains a variety of step-by-step examples of how to integrate a FortiGate
unit into your network and apply features such as security profiles, wireless networking, and VPN.
Using the FortiGate Cookbook, you can go from idea to execution in simple steps, configuring a
secure network for better productivity with reduced risk.
Written for FortiOS 5.2
Fortinet.com

Fortigate Cookbook 52

Uploaded by

Copyright:

Available Formats

Fortigate Cookbook 52

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fortigate Cookbook 52

Uploaded by

Copyright:

Available Formats

FortiOS 5.

The FortiGate Cookbook 5.2

Fortinet Cookbook - http://cookbook.fortinet.com

Choosing your FortiGate's switch mode

Installing a FortiGate in NAT/Route mode

Installing a FortiGate in Transparent mode

Quick installation using DHCP

Redundant Internet connections

Troubleshooting your FortiGate installation

FortiGate registration and basic settings

Updating your FortiGates firmware

Setting up FortiGuard services

Logging FortiGate traffic

Logging with FortiCloud

Troubleshooting FortiGate logging

Creating security policies

Limited access administrator accounts

Port pairing in Transparent mode

How to upgrade one unit in an HA cluster

High Availability with two FortiGates

AirPlay for Apple TV

Protect a web server withDMZ

Traffic shaping for VoIP

Creating an IPv6 interface using SLAAC

Remotely accessing FortiRecorder through a FortiGate

Managing a FortiSwitch with a FortiGate

Excluding users from security scanning

FSSO in Polling mode

Two-factor authentication with FortiToken Mobile

FortiOS AntiVirus inspection modes

AntiVirus with FortiSandbox

Blocking P2P traffic and YouTube applications

Blocking Windows XP traffic

Blocking and monitoring Tor traffic

Controlling access to Apple's App Store

Restricting online gaming to evenings

Preventing data leaks

Prevent credit card numbers from being leaked

Protecting a web server

Logging DNS domain lookups

Why you should use SSL inspection

Preventing certificate warnings

Exempting Google from SSLinspection

Blocking adult/mature content with Google SafeSearch

Web rating overrides

Web filtering using quotas

Blocking Google access for consumer accounts

Overriding a web filter profile

Troubleshooting web filtering

IPsec VPN with FortiClient

IPsec VPNfor iOS devices

IPsec VPN with the native Mac OS client

IPsec VPN with two-factor authentication

IPsec VPNwith external DHCP service

Site-to-site IPsec VPN with two FortiGates

Site-to-site IPsec VPN with overlapping subnets

IPsec VPN to Microsoft Azure

Remote Internet browsing using a VPN

Remote browsing using site-to-site IPsec VPN

SSLVPN for remote users