Fortiget

ADMINISTRAT ION GUIDE
FortiGate™
Version 3.0 MR7
Visit http://support.fortinet.com to register your FortiGate product. By registering you can receive product updates,
technical support, and FortiGuard services.
www.fortinet.com
FortiGate™ Administration Guide
Version 3.0 MR7
12 January 2009
01-30007-0203-20090112
© Copyright 2009 Fortinet, Inc. All rights reserved. No part of this

publication including text, examples, diagrams or illustrations may be
reproduced, transmitted, or translated in any form or by any means,
electronic, mechanical, manual, optical or otherwise, for any purpose,
without prior written permission of Fortinet, Inc.
Trademarks
Fortinet, FortiGate and FortiGuard are registered trademarks and
Dynamic Threat Prevention System (DTPS), APSecure, FortiASIC,
FortiBIOS, FortiBridge, FortiClient, FortiDB, FortiGate, FortiGate Unified
Threat Management System, FortiGuard-Antispam, FortiGuard-Antivirus,
FortiGuard-Intrusion, FortiGuard-Web, FortiLog, FortiAnalyzer,
FortiManager, FortiOS, FortiPartner, FortiProtect, FortiReporter,
FortiResponse, FortiShield, and FortiVoIP, are trademarks of Fortinet, Inc.
in the United States and/or other countries. The names of actual
companies and products mentioned herein may be the trademarks of
their respective owners.
Contents
Contents
What’s new in 3.0 MR7..................................................................... 19
3.0 MR7 new features and changes ............................................................... 21
FSAE........................................................................................................... 21
AMC support ............................................................................................... 21
Dashboard................................................................................................... 22
FortiGuard Analysis and Management Service........................................... 22
Virtual domains ........................................................................................... 22
VDOM and Global icons in documentation ................................................. 23
Modem support ........................................................................................... 23
SNMP.......................................................................................................... 23
Router ......................................................................................................... 23
Authentication ............................................................................................. 24
SSL VPN client tunnel mode for Mac OS and Linux ................................... 24
Standalone SSL VPN client ........................................................................ 24
SSL VPN Virtual Desktop application ......................................................... 24
SSL VPN URL obscuration ......................................................................... 24
Intrusion Protection ..................................................................................... 24
Log messages............................................................................................. 25
Content archiving ........................................................................................ 25
Alert email ................................................................................................... 25
Email archiving ............................................................................................ 26
HA primary unit acts as a router for subordinate unit management traffic .. 26
HA heartbeat IP addresses ......................................................................... 27
Interface display order................................................................................. 28
Introduction ...................................................................................... 29
Introducing the FortiGate units ...................................................................... 29
FortiGate-5000 series chassis .................................................................... 30
About the FortiGate-5000 series boards ..................................................... 31
FortiGate-AMC modules ............................................................................. 32
FortiGate-3810A.......................................................................................... 32
FortiGate-3600A.......................................................................................... 32
FortiGate-3016B.......................................................................................... 33
FortiGate-3600 ............................................................................................ 33
FortiGate-3000 ............................................................................................ 33
FortiGate-1000A/AFA2................................................................................ 34
FortiGate-1000 ............................................................................................ 34
FortiGate-800/800F..................................................................................... 34
FortiGate-500A............................................................................................ 35
FortiGate-500 .............................................................................................. 35
FortiGate-400A............................................................................................ 35
FortiGate-400 .............................................................................................. 35
FortiGate-310B............................................................................................ 36
FortiGate-300A............................................................................................ 36
FortiGate Version 3.0 MR7 Administration Guide

01-30007-0203-20090112 3
Contents
FortiGate-300 .............................................................................................. 36
FortiGate-224B ........................................................................................... 36
FortiGate-200A ........................................................................................... 37
FortiGate-200 .............................................................................................. 37
FortiGate-100A ........................................................................................... 37
FortiGate-100 .............................................................................................. 37
FortiGate-60B ............................................................................................. 38
FortiWiFi-60B .............................................................................................. 38
FortiGate-60/60M/ADSL ............................................................................. 38
FortiWiFi-60/60A/60AM............................................................................... 39
FortiWiFi-50B .............................................................................................. 39
FortiGate-50B ............................................................................................. 39
FortiGate-50A ............................................................................................. 39
Fortinet family of products ............................................................................. 40
FortiGuard Subscription Services ............................................................... 40
FortiAnalyzer............................................................................................... 40
FortiClient.................................................................................................... 40
FortiManager............................................................................................... 41
FortiBridge .................................................................................................. 41
FortiMail ...................................................................................................... 41
About this document....................................................................................... 41
Document conventions ............................................................................... 43
FortiGate documentation ............................................................................... 44
Fortinet Tools and Documentation CD........................................................ 45
Fortinet Knowledge Center ........................................................................ 46
Comments on Fortinet technical documentation ........................................ 46
Customer service and technical support ...................................................... 46
Register your Fortinet product....................................................................... 46
Web-based manager........................................................................ 47
Common web-based manager tasks ............................................................. 48
Connecting to the web-based manager ...................................................... 48
Changing your FortiGate administrator password ...................................... 49
Changing the web-based manager language ............................................. 50
Changing administrative access to your FortiGate unit .............................. 50
Changing the web-based manager idle timeout ......................................... 51
Connecting to the FortiGate CLI from the web-based manager ................. 51
Button bar features ......................................................................................... 52
Contacting Customer Support ....................................................................... 52
Backing up your FortiGate configuration ..................................................... 52
Using FortiGate Online Help........................................................................... 53
Searching the online help ........................................................................... 54
Logging out...................................................................................................... 56

4 01-30007-0203-20090112
Contents
Web-based manager pages ............................................................................ 56

Using the web-based manager menu ......................................................... 57
Using web-based manager lists .................................................................. 57
Adding filters to web-based manager lists .................................................. 58
Using page controls on web-based manager lists ...................................... 61
Using column settings to control the columns displayed............................. 62
Using web-based manager icons ................................................................ 64
System Status .................................................................................. 67

Status page ...................................................................................................... 67
Viewing system status................................................................................. 67
Changing system information ........................................................................ 80
Configuring system time.............................................................................. 80
Changing the FortiGate unit host name ...................................................... 80
Changing the FortiGate firmware................................................................... 81
Upgrading to a new firmware version.......................................................... 82
Reverting to a previous firmware version .................................................... 83
Viewing operational history............................................................................ 84
Manually updating FortiGuard definitions .................................................... 84
Viewing Statistics ............................................................................................ 85
Viewing the session list ............................................................................... 85
Viewing the Content Archive information .................................................... 87
Viewing the Attack Log................................................................................ 88
Topology........................................................................................................... 90
Adding a subnet object................................................................................ 92
Customizing the topology diagram .............................................................. 93
Using virtual domains...................................................................... 95

Virtual domains................................................................................................ 95
VDOM configuration settings ...................................................................... 97
Global configuration settings ....................................................................... 98
Enabling VDOMs............................................................................................ 100
Configuring VDOMs and global settings..................................................... 100
Creating a new VDOM .............................................................................. 101
Working with VDOMs and global settings ................................................. 102
Adding interfaces to a VDOM.................................................................... 103
Inter-VDOM links....................................................................................... 103
Assigning an interface to a VDOM ............................................................ 104
Assigning an administrator to a VDOM ..................................................... 105
Changing the Management VDOM ........................................................... 106

01-30007-0203-20090112 5
Contents
System Network ............................................................................. 107

Interfaces........................................................................................................ 107
Switch Mode ............................................................................................. 111
Interface settings....................................................................................... 112
Configuring an ADSL interface ................................................................. 115
Creating an 802.3ad aggregate interface ................................................. 116
Creating a redundant interface ................................................................. 117
Configuring DHCP on an interface............................................................ 118
Configuring an interface for PPPoE or PPPoA ......................................... 120
Configuring Dynamic DNS on an interface ............................................... 122
Configuring a virtual IPSec interface......................................................... 122
Configuring interfaces with CLI commands .............................................. 123
Additional configuration for interfaces....................................................... 125
Configuring zones ......................................................................................... 128
Configuring the modem interface ................................................................ 129
Configuring modem settings ..................................................................... 130
Redundant mode configuration................................................................. 132
Standalone mode configuration ................................................................ 133
Adding firewall policies for modem connections ....................................... 134
Connecting and disconnecting the modem ............................................... 134
Checking modem status ........................................................................... 134
Configuring Networking Options ................................................................. 135
DNS Servers ............................................................................................. 136
Dead gateway detection ........................................................................... 137
Routing table (Transparent Mode) ............................................................... 137
Transparent mode route settings .............................................................. 138
VLAN overview .............................................................................................. 138
FortiGate units and VLANs ....................................................................... 139
VLANs in NAT/Route mode .......................................................................... 139
Rules for VLAN IDs ................................................................................... 140
Rules for VLAN IP addresses ................................................................... 140
Adding VLAN subinterfaces ...................................................................... 141
VLANs in Transparent mode ........................................................................ 142
Rules for VLAN IDs ................................................................................... 144
Transparent mode virtual domains and VLANs ........................................ 144
Troubleshooting ARP Issues .................................................................... 145
System Wireless ............................................................................ 147

FortiWiFi wireless interfaces........................................................................ 147
Channel assignments ................................................................................... 148
IEEE 802.11a channel numbers ............................................................... 148
IEEE 802.11b channel numbers ............................................................... 149
IEEE 802.11g channel numbers ............................................................... 150

6 01-30007-0203-20090112
Contents
System wireless settings .............................................................................. 150

Adding a wireless interface ....................................................................... 152
FortiWiFi-60 system wireless settings......................................................... 154
Wireless MAC Filter ....................................................................................... 156
Managing the MAC Filter list ..................................................................... 156
FortiWiFi-60 Wireless MAC Filter .............................................................. 157
Wireless Monitor............................................................................................ 159
System DHCP ................................................................................. 161

FortiGate DHCP servers and relays ............................................................. 161
Configuring DHCP services.......................................................................... 162
Configuring an interface as a DHCP relay agent ...................................... 163
Configuring a DHCP server....................................................................... 163
Viewing address leases ................................................................................ 165
Reserving IP addresses for specific clients............................................... 165
System Config ................................................................................ 167

HA.................................................................................................................... 167
HA options................................................................................................. 167
Cluster members list ................................................................................. 171
Viewing HA statistics ................................................................................. 173
Changing subordinate unit host name and device priority ........................ 174
Disconnecting a cluster unit from a cluster ............................................... 175
SNMP .............................................................................................................. 176
Configuring SNMP .................................................................................... 176
Configuring an SNMP community ............................................................. 177
Fortinet MIBs ............................................................................................. 179
FortiGate traps .......................................................................................... 180
Fortinet MIB fields ..................................................................................... 182
Replacement messages ................................................................................ 188
Replacement messages list ...................................................................... 188
Changing replacement messages............................................................. 189
Changing the authentication login page .................................................... 191
Changing the FortiGuard web filtering block override page ...................... 192
Changing the SSL-VPN login message .................................................... 192
Changing the authentication disclaimer page ........................................... 192
Operation mode and VDOM management access...................................... 193
Changing operation mode ......................................................................... 193
Management access ................................................................................. 194

01-30007-0203-20090112 7
Contents
System Administrators.................................................................. 195

Administrators ............................................................................................... 195
Configuring regular (password) authentication for administrators ............ 197
Configuring remote authentication for administrators ............................... 197
Configuring RADIUS authentication for administrators ............................. 198
Configuring LDAP authentication for administrators ................................. 199
Configuring TACACS+ authentication for administrators.......................... 201
Configuring PKI certificate authentication for administrators .................... 203
Viewing the administrators list .................................................................. 204
Configuring an administrator account ....................................................... 205
Access profiles .............................................................................................. 208
Viewing the access profiles list ................................................................. 210
Configuring an access profile.................................................................... 211
Central Management ..................................................................................... 212
Settings .......................................................................................................... 215
Monitoring administrators ............................................................................ 216
FortiGate IPv6 support.................................................................................. 217
System Certificates........................................................................ 219

Local Certificates .......................................................................................... 219
Generating a certificate request................................................................ 221
Downloading and submitting a certificate request .................................... 222
Importing a signed server certificate ......................................................... 223
Importing an exported server certificate and private key .......................... 223
Importing separate server certificate and private key files ........................ 224
Remote Certificates....................................................................................... 224
Importing Remote (OCSP) certificates...................................................... 225
CA Certificates............................................................................................... 226
Importing CA certificates........................................................................... 226
CRL ................................................................................................................. 227
Importing a certificate revocation list......................................................... 228
System Maintenance ..................................................................... 229

Maintenance System Configuration ............................................................ 229
Backup and Restore ................................................................................. 231
Firmware ................................................................................................... 235
Firmware Upgrade .................................................................................... 236
FortiClient.................................................................................................. 236
Advanced .................................................................................................. 237
Revision Control............................................................................................ 238
Scripts ............................................................................................................ 240
Creating script files ................................................................................... 240
Uploading scripts ...................................................................................... 241

8 01-30007-0203-20090112
Contents
FortiGuard ...................................................................................................... 241

FortiGuard Distribution Network ................................................................ 241
FortiGuard Services .................................................................................. 242
Configuring the FortiGate unit for FDN and FortiGuard
subscription services ................................................................................. 243
Troubleshooting FDN connectivity .............................................................. 248
Updating antivirus and attack definitions ................................................... 249
Enabling push updates ................................................................................. 250
Push updates when FortiGate IP addresses changes .............................. 251
Enabling push updates through a NAT device .......................................... 251
License ........................................................................................................... 254
Router Static .................................................................................. 255

Routing concepts ......................................................................................... 255
How the routing table is built .................................................................... 256
How routing decisions are made .............................................................. 256
Multipath routing and determining the best route ...................................... 256
Route priority ............................................................................................ 257
Blackhole Route ........................................................................................ 258
Static Route ................................................................................................... 258
Working with static routes ........................................................................ 258
Default route and default gateway ........................................................... 259
Adding a static route to the routing table .................................................. 262
Policy Route .................................................................................................. 263
Adding a policy route................................................................................. 264
Moving a policy route ................................................................................ 265
Router Dynamic.............................................................................. 267

RIP................................................................................................................... 268
How RIP works.......................................................................................... 268
Viewing and editing basic RIP settings ..................................................... 268
Selecting advanced RIP options ............................................................... 270
Configuring a RIP-enabled interface ......................................................... 272
OSPF ............................................................................................................... 273
How OSPF works ...................................................................................... 273
Defining an OSPF AS—Overview ............................................................. 274
Configuring basic OSPF settings .............................................................. 274
Selecting advanced OSPF options ........................................................... 277
Defining OSPF areas ................................................................................ 278
Specifying OSPF networks ....................................................................... 279
Selecting operating parameters for an OSPF interface ............................ 279
BGP ................................................................................................................. 281
How BGP works ........................................................................................ 281
Viewing and editing BGP settings ............................................................. 282

01-30007-0203-20090112 9
Contents
Multicast ......................................................................................................... 283

How multicast works ................................................................................. 283
Viewing and editing multicast settings ...................................................... 284
Overriding the multicast settings on an interface ...................................... 285
Multicast destination NAT ......................................................................... 285
Bi-directional Forwarding Detection (BFD)................................................. 286
How BFD works ........................................................................................ 286
Configuring BFD ....................................................................................... 286
Router Monitor ............................................................................... 289

Viewing routing information......................................................................... 289
Searching the FortiGate routing table ......................................................... 291
Firewall Policy ................................................................................ 293

How list order affects policy matching........................................................ 293
Moving a policy to a different position in the policy list ............................. 294
Multicast policies........................................................................................... 295
Viewing the firewall policy list...................................................................... 295
Configuring firewall policies ........................................................................ 297
Adding authentication to firewall policies .................................................. 302
Authentication firewall policy options (non-SSL-VPN) .............................. 303
Adding traffic shaping to firewall policies .................................................. 304
IPSec firewall policy options ..................................................................... 306
SSL-VPN firewall policy options................................................................ 307
Options to detect FortiClient on hosts....................................................... 308
Firewall policy examples .............................................................................. 308
Scenario one: SOHO-sized business ....................................................... 309
Scenario two: enterprise-sized business .................................................. 311
Firewall Address ............................................................................ 315

About firewall addresses .............................................................................. 315
Viewing the firewall address list .................................................................. 316
Configuring addresses ................................................................................. 317
Viewing the address group list .................................................................... 318
Configuring address groups ........................................................................ 318
Firewall Service.............................................................................. 321

Viewing the predefined service list.............................................................. 321
Viewing the custom service list ................................................................... 325
Configuring custom services ....................................................................... 325
Viewing the service group list...................................................................... 327
Configuring service groups.......................................................................... 327

10 01-30007-0203-20090112
Contents
Firewall Schedule........................................................................... 329

Viewing the recurring schedule list ............................................................. 329
Configuring recurring schedules ................................................................. 330
Viewing the one-time schedule list .............................................................. 330
Configuring one-time schedules.................................................................. 331
Firewall Virtual IP ........................................................................... 333

How virtual IPs map connections through FortiGate units ....................... 333
Inbound connections ................................................................................. 334
Outbound connections .............................................................................. 336
VIP requirements ...................................................................................... 337
Viewing the virtual IP list .............................................................................. 337
Configuring virtual IPs .................................................................................. 338
Adding a static NAT virtual IP for a single IP address............................... 341
Adding a static NAT virtual IP for an IP address range ............................. 343
Adding static NAT port forwarding for a single IP address and
a single port............................................................................................... 344
Adding static NAT port forwarding for an IP address range and
a port range ............................................................................................... 346
Adding a server load balance virtual IP..................................................... 348
Adding a server load balance port forwarding virtual IP............................ 350
Adding dynamic virtual IPs ........................................................................ 352
Adding a virtual IP with port translation only ............................................. 353
Virtual IP Groups ........................................................................................... 353
Viewing the VIP group list............................................................................. 354
Configuring VIP groups ................................................................................ 354
Health Check Monitor.................................................................................... 355
IP pools........................................................................................................... 356
IP pools and dynamic NAT........................................................................ 356
IP Pools for firewall policies that use fixed ports ....................................... 357
Source IP address and IP pool address matching .................................... 357
Viewing the IP pool list.................................................................................. 358
Configuring IP Pools ..................................................................................... 359
Double NAT: combining IP pools with virtual IPs ...................................... 359
Adding NAT firewall policies in transparent mode..................................... 361
Firewall Protection Profile............................................................. 365

What is a protection profile? ........................................................................ 365
Default protection profiles ............................................................................ 366
Viewing the protection profile list ................................................................ 366

01-30007-0203-20090112 11
Contents
Configuring a protection profile................................................................... 367

Anti-Virus options ...................................................................................... 367
Web Filtering options ................................................................................ 369
FortiGuard Web Filtering options .............................................................. 370
Spam Filtering options .............................................................................. 373
IPS options................................................................................................ 375
Content Archive options............................................................................ 375
IM/P2P options.......................................................................................... 378
VoIP options.............................................................................................. 379
Logging options......................................................................................... 380
Applying a protection profile to a firewall policy ....................................... 381
SIP support..................................................................................... 383

VoIP and SIP .................................................................................................. 383
FortiOS and VoIP security ............................................................................ 384
SIP NAT .................................................................................................... 385
How SIP support works ................................................................................ 388
Configuring SIP ............................................................................................. 388
Enabling SIP support and setting rate limiting .......................................... 388
Enabling SIP logging................................................................................. 389
Viewing SIP statistics................................................................................ 389
Enabling advanced SIP features in a protection profile ............................ 389
VPN IPSEC...................................................................................... 393

Overview of IPSec VPN configuration ......................................................... 393
Policy-based versus route-based VPNs...................................................... 394
Auto Key......................................................................................................... 395
Creating a new phase 1 configuration ...................................................... 396
Defining phase 1 advanced settings ......................................................... 399
Creating a new phase 2 configuration ...................................................... 401
Defining phase 2 advanced settings ......................................................... 401
Manual Key..................................................................................................... 404
Creating a new manual key configuration ................................................ 405
Internet browsing configuration .................................................................. 407
Concentrator ................................................................................................. 407
Defining concentrator options ................................................................... 408
Monitor ........................................................................................................... 409
VPN PPTP ....................................................................................... 411

PPTP Range ................................................................................................... 411
VPN SSL.......................................................................................... 413

ssl.root............................................................................................................ 414

12 01-30007-0203-20090112
Contents
Configuring SSL VPN .................................................................................... 414

Monitoring SSL VPN sessions ..................................................................... 416
SSL VPN bookmarks ..................................................................................... 416
Viewing the SSL VPN bookmark list ......................................................... 416
Configuring SSL VPN bookmarks ............................................................. 417
Viewing the SSL VPN Bookmark Group list .............................................. 418
Configuring SSL VPN bookmark groups ................................................... 419
User Authentication ....................................................................... 421

Configuring user authentication .................................................................. 421
Local user accounts ...................................................................................... 422
Configuring a Local user account.............................................................. 423
Remote authentication .................................................................................. 423
RADIUS servers ............................................................................................. 424
Configuring a RADIUS server ................................................................... 425
LDAP servers ................................................................................................. 426
Configuring an LDAP server ..................................................................... 427
TACACS+ servers.......................................................................................... 429
Configuring TACACS+ servers ................................................................. 430
PKI authentication ......................................................................................... 431
Configuring peer users and peer groups................................................... 432
Directory Service servers ............................................................................. 433
Configuring a Directory Service server ..................................................... 434
User groups.................................................................................................... 435
Firewall user groups .................................................................................. 436
Directory Service user groups ................................................................... 437
SSL VPN user groups ............................................................................... 437
Viewing the User group list ....................................................................... 438
Configuring a user group........................................................................... 438
Configuring FortiGuard override options for a user group
(Firewall or Directory Service) ................................................................... 441
Configuring additional SSL VPN user group options ................................ 442
Authentication settings................................................................................. 445
AntiVirus ......................................................................................... 447

Order of operations ....................................................................................... 447
Antivirus tasks ............................................................................................... 448
FortiGuard antivirus................................................................................... 449
Antivirus settings and controls.................................................................... 449

01-30007-0203-20090112 13
Contents
File Filter......................................................................................................... 450

Built-in patterns and supported file types .................................................. 451
Viewing the file filter list catalog ................................................................ 452
Creating a new file filter list ....................................................................... 453
Viewing the file filter list............................................................................. 453
Configuring the file filter list....................................................................... 454
Quarantine...................................................................................................... 454
Viewing the Quarantined Files list............................................................. 455
Viewing the AutoSubmit list ...................................................................... 456
Configuring the AutoSubmit list................................................................. 457
Configuring quarantine options ................................................................. 457
Viewing the virus list..................................................................................... 458
Viewing and configuring the grayware list ................................................. 459
Antivirus CLI configuration .......................................................................... 461
system global optimize.............................................................................. 461
config antivirus heuristic............................................................................ 461
config antivirus quarantine ........................................................................ 461
config antivirus service <service_name> .................................................. 462
Intrusion Protection....................................................................... 463

About intrusion protection ........................................................................... 463
Intrusion Protection settings and controls ................................................. 464
When to use Intrusion Protection .............................................................. 464
Signatures ...................................................................................................... 465
Viewing the predefined signature list ........................................................ 465
Using display filters ................................................................................... 466
Custom signatures ........................................................................................ 467
Viewing the custom signature list.............................................................. 467
Creating custom signatures ...................................................................... 467
Protocol decoders ......................................................................................... 468
Viewing the protocol decoder list .............................................................. 468
Upgrading the IPS protocol decoder list ................................................... 469
IPS sensors .................................................................................................... 469
Viewing the IPS sensor list ....................................................................... 469
Adding an IPS sensor ............................................................................... 470
Configuring IPS sensors ........................................................................... 470
Configuring filters ...................................................................................... 472
Configuring pre-defined and custom overrides ......................................... 473
DoS sensors................................................................................................... 475
Viewing the DoS sensor list ...................................................................... 475
Configuring DoS sensors .......................................................................... 476
Understanding the anomalies ................................................................... 477

14 01-30007-0203-20090112
Contents
Intrusion protection CLI configuration ........................................................ 478

ips global fail-open .................................................................................... 478
ips global socket-size ................................................................................ 478
Web Filter........................................................................................ 479

Order of web filtering .................................................................................... 479
How web filtering works................................................................................ 480
Web filter controls ......................................................................................... 480
Content block................................................................................................. 482
Viewing the web content block list catalog ................................................ 482
Creating a new web content block list ....................................................... 483
Viewing the web content block list ............................................................ 483
Configuring the web content block list....................................................... 484
Viewing the web content exempt list catalog ............................................ 485
Creating a new web content exempt list ................................................... 485
Viewing the web content exempt list ......................................................... 486
Configuring the web content exempt list ................................................... 487
URL filter......................................................................................................... 487
Viewing the URL filter list catalog.............................................................. 487
Creating a new URL filter list..................................................................... 488
Viewing the URL filter list .......................................................................... 488
Configuring the URL filter list .................................................................... 489
URL formats .............................................................................................. 490
Moving URLs in the URL filter list ............................................................. 491
FortiGuard - Web Filter.................................................................................. 491
Configuring FortiGuard Web Filtering ....................................................... 492
Viewing the override list ............................................................................ 492
Configuring administrative override rules .................................................. 493
Creating local categories........................................................................... 495
Viewing the local ratings list ...................................................................... 495
Configuring local ratings............................................................................ 496
Category block CLI configuration .............................................................. 497
FortiGuard Web Filtering reports............................................................... 497
Antispam......................................................................................... 499
Antispam ........................................................................................................ 499
Order of spam filtering............................................................................... 499
Anti-spam filter controls............................................................................. 500
Banned word .................................................................................................. 502
Viewing the banned word list catalog ........................................................ 502
Creating a new banned word list ............................................................... 503
Viewing the antispam banned word list ..................................................... 503
Adding words to the banned word list ....................................................... 504

01-30007-0203-20090112 15
Contents
Black/White List............................................................................................. 505

Viewing the antispam IP address list catalog............................................ 505
Creating a new antispam IP address list................................................... 506
Viewing the antispam IP address list ........................................................ 506
Adding an antispam IP address ................................................................ 507
Viewing the antispam email address list catalog ...................................... 508
Creating a new antispam email address list ............................................. 508
Viewing the antispam email address list ................................................... 509
Configuring the antispam email address list ............................................. 510
Advanced antispam configuration............................................................... 510
config spamfilter mheader......................................................................... 510
config spamfilter dnsbl .............................................................................. 511
Using wildcards and Perl regular expressions........................................... 511
Regular expression vs. wildcard match pattern ........................................ 511
Word boundary ......................................................................................... 512
Case sensitivity ......................................................................................... 512
Perl regular expression formats ................................................................ 512
Example regular expressions.................................................................... 513
IM, P2P & VoIP................................................................................ 515

Overview......................................................................................................... 515
Configuring IM/P2P/VoIP protocols ............................................................. 517
Configuring IM/P2P/VoIP IPS signatures.................................................. 517
Configuring IPS signatures for unsupported IM/P2P protocols................. 518
Configuring IM/P2P/VoIP options within a protection profile..................... 518
Configuring older versions of IM/P2P applications ................................... 518
Statistics......................................................................................................... 518
Viewing overview statistics ....................................................................... 518
Viewing statistics by protocol .................................................................... 520
User................................................................................................................. 521
Viewing the Current Users list................................................................... 521
Viewing the User List ................................................................................ 522
Adding a new user to the User List ........................................................... 522
Configuring a policy for unknown IM users ............................................... 523
Log&Report .................................................................................... 525

FortiGate logging........................................................................................... 525
FortiGuard Analysis and Management Service .......................................... 526
FortiGuard Analysis and Management Service portal web site ................ 527
Log severity levels ........................................................................................ 527
High Availability cluster logging.................................................................. 528

16 01-30007-0203-20090112
Contents
Storing logs.................................................................................................... 528

Logging to a FortiAnalyzer unit ................................................................. 529
Connecting to FortiAnalyzer using Automatic Discovery .......................... 530
Testing the FortiAnalyzer configuration..................................................... 531
Logging to a FortiGuard Analysis server ................................................... 532
Logging to memory ................................................................................... 533
Logging to a Syslog server........................................................................ 533
Logging to WebTrends.............................................................................. 534
Log types........................................................................................................ 535
Traffic log .................................................................................................. 535
Event log ................................................................................................... 536
Antivirus log............................................................................................... 537
Web filter log ............................................................................................. 537
Spam filter log ........................................................................................... 538
Attack log (IPS) ......................................................................................... 538
IM and P2P log.......................................................................................... 538
VoIP log..................................................................................................... 539
Accessing Logs ............................................................................................. 539
Accessing log messages stored in memory .............................................. 540
Accessing log message stored on the hard disk ....................................... 540
Accessing logs stored on the FortiAnalyzer unit ....................................... 541
Accessing logs stored on the FortiGuard Analysis server......................... 542
Viewing log information ................................................................................ 542
Customizing the display of log messages .................................................. 543
Column settings ........................................................................................ 543
Filtering log messages .............................................................................. 545
Content Archive ............................................................................................. 545
Configuring content archiving.................................................................... 546
Viewing content archives .......................................................................... 546
Alert Email ...................................................................................................... 547
Configuring Alert Email ............................................................................. 547
Reports ........................................................................................................... 549
Viewing basic traffic reports ...................................................................... 549
FortiAnalyzer report schedules ................................................................. 551
Viewing FortiAnalyzer reports ................................................................... 553
Printing your FortiAnalyzer report ............................................................. 554
Managing firmware versions......................................................... 555

Backing up your configuration..................................................................... 556
Testing firmware before upgrading ............................................................. 557
Upgrading your FortiGate unit ..................................................................... 558
Upgrading to FortiOS 3.0 .......................................................................... 559
Verifying the upgrade ................................................................................ 560

01-30007-0203-20090112 17
Contents
Reverting to FortiOS 2.80 MR11................................................................... 561

Backing up your FortiOS 3.0 configuration ............................................... 561
Downgrading to FortiOS 2.80 MR11 using web-based manager ............. 562
Verifying the downgrade ........................................................................... 563
Downgrading to FortiOS 2.80 MR11 using the CLI................................... 563
Restoring your configuration ....................................................................... 564
Restoring your configuration settings using the web-based manager ...... 564
Restoring your configuration settings using the CLI ................................. 564
Upgrading from FortiOS 3.0 MR1 to FortiOS 3.0 MR2................................ 566
Backing up your configuration................................................................... 566
Upgrading to FortiOS 3.0 MR2 ................................................................. 567
Reverting to FortiOS 3.0 MR1....................................................................... 568
Backing up your configuration................................................................... 568
Downgrading to a previous firmware maintenance release ...................... 569
Restoring your previous configuration ...................................................... 570
Restoring your configuration settings using the FortiUSB key .................. 572
Upgrading issues for 3.0 MR7 ...................................................................... 572
Upgrading issues from FortiOS 2.80 MR11 .............................................. 572
Upgrading issues from FortiOS 3.0 MR5 and MR6 .................................. 574
Index................................................................................................ 577

18 01-30007-0203-20090112
What’s new in 3.0 MR7

This section lists and describes some of the new features and changes in FortiOS
3.0 MR7. Additional information about upgrading to FortiOS 3.0 MR7 is included
in the chapter, “Managing firmware versions” on page 555.
This section also highlights several new and changed FortiGate CLI commands.
For more information about changes to the FortiGate CLI, we recommend that
you review the What’s New section in the FortiGate CLI Reference.
New features and changes for FortiOS 3.0 MR7 include changes to the following
parts of the product:
• FSAE – See “FSAE” on page 21.
• AMC support – See “AMC support” on page 21.
• Dashboard – See “Dashboard” on page 22.
• FortiGuard Analysis and Management Service licensing – The license for
the FortiGuard Analysis and Management Service now reflects the changes
made to the service in FortiOS 3.0 MR6. See “FortiGuard Analysis and
Management Service” on page 22.
• DHCP maximum values increase – All FortiGate units now have a maximum
of 200 addresses reserved for DHCP. See the FortiGate Maximum Values
Matrix.
• Virtual Domains – See “Virtual domains” on page 22.
• VDOM and Global icons added to documentation – FortiGate
context-sensitive online help topics and the FortiGate Administration Guide
now include VDOM and Global icons to indicate whether the section of the
FortiGate web-based manager is VDOM-specific or part of the global
configuration. See “Virtual domains” on page 22.
• Network interface status display – A new column, Link Status, has been
added to the Network Interface list, and Status has been renamed
Administration Status. See “Interfaces” on page 107.
• Interface display order – FortiGate units with interfaces numbered port10
and above now sort interface names in the correct numerical order. This
reordering does not interfere with your HA configuration. See “Interface display
order” on page 28.
• Network interface DNS settings– Some of the DNS settings available for
network interfaces in DHCP or PPPoE mode have been changed to reduce the
number of DNS requests the FortiGate unit sends out. Override Internal DNS
is enabled by default to promote the use of learned DNS servers. See
“Configuring DHCP on an interface” on page 118 and “Configuring an interface
for PPPoE or PPPoA” on page 120.
• DNS cache poisoning protection – The FortiGate DNS server has been
updated to protect against DNS cache poisoning. For information about DNS
cache poisoning, see the FortiGuard Center item
BailiWicked.Red.Metasploit.DNS.Spoofing and the US CERT article Multiple
DNS implementations vulnerable to cache poisoning.

01-30007-0203-20090112 19
• Modem – You can connect a USB modem to any FortiGate unit USB port. You
can also disable PPP echo requests for modem interfaces. See “Modem
support” on page 23.
• SNMP – See “SNMP” on page 23.
• IPv6 – IPv6 Phase II has been implemented. This includes more IPv6
functions on the web-based manager and more IPv6 commands in the CLI.
See “FortiGate IPv6 support” on page 217.
• Chassis monitoring removed – System Chassis monitoring has been
removed from both the web-based manager and CLI (get chassis
status). The high temperature and voltage SNMP events are also no longer
available.
• Routing – See “Router” on page 23.
• Authentication – FortiOS 3.0 MR7 now supports more remote authentication
servers and local certificates as well as longer LDAP DNs. See
“Authentication” on page 24.
• Firewall addresses – FortiOS 3.0 MR7 now supports firewall addresses with
wildcard netmasks. See “Firewall Address” on page 315.
• “Child Abuse” FortiGuard Web Filtering category – The Child Abuse
category has been added to the FortiGuard Web Filtering group “Potential
Liable”. You can enable this filter in protection profiles by going to Firewall >
Protection Profile and configuring FortiGuard Web Filtering. See “FortiGuard
Web Filtering options” on page 370 and the FortiGuard Center Web Filtering
Database Categories.
• SIP servers – While most SIP servers use 5060 as the source port in the
register response, some do not follow this rule. You can now configure the
FortiGate unit, through the CLI, to accept a SIP register response with any
source port number, by enabling the config firewall profile config
sip reg-diff-port keyword.
• IPSec interfaces – You can now use an IPSec interface as the source
interface for an IPSec firewall policy, making it possible to allow traffic between
an interface-based VPN and a policy-based VPN. See “Configuring firewall
policies” on page 297 and “IPSec firewall policy options” on page 306
• SSL VPN – See “SSL VPN client tunnel mode for Mac OS and Linux” on
page 24, “Standalone SSL VPN client” on page 24, “SSL VPN Virtual Desktop
application” on page 24, and “SSL VPN URL obscuration” on page 24
• IPS filters – IPS filters now display more information about IPS signatures.
See “Intrusion Protection” on page 24.
• Log messages – There are several new log messages as well as changes to
existing ones. See “Log messages” on page 25.
• Content archiving – You can now enable content archiving of HTTP, FTP,
SMTP, POP3, HTTPS, and IMAP content without having to enable other
features as well. See “Content archiving” on page 25.
• Alert email – You can now define an alternate port for outgoing alert email.
Alert email categories that display in the Log Config menu may not all display
when in VDOMs or Transparent mode. See “Alert email” on page 25.
• Reports – See “Reports” on page 25.
• Email archiving – See “Email archiving” on page 26.
• HA – See “HA primary unit acts as a router for subordinate unit management
traffic” on page 26, “HA heartbeat IP addresses” on page 27 and “Interface
display order” on page 28.

20 01-30007-0203-20090112
What’s new in 3.0 MR7 3.0 MR7 new features and changes
3.0 MR7 new features and changes

The following sections describe new features and changes in FortiOS 3.0 MR7.
FSAE
Using the Fortinet Server Authentication Extension (FSAE), FortiGate units
provide transparent user authentication on Windows networks with an Active
Directory server. In FortiOS 3.0 MR7, FSAE is now also available for Novell
networks eDirectory. Note the following changes in the web-based manager
menu:
• User > Windows AD is now User > Directory Service.
• In User > User Group, the Windows AD user group type is now
Directory Service.
Configuration on the FortiGate unit is the same for Windows AD and Novell
eDirectory.
Using FSAE, FortiGate units can now keep better track of frequently changing
user IP addresses on Windows AD networks.
For information about installing and configuring FSAE on Windows AD and Novell
eDirectory, see the FSAE Administration Guide.
AMC support
AMC module interfaces are now named with upper case letters. For example, a
single width AMC card in slot 2 with four network interfaces would have interfaces
named AMC-SW2/1, AMC-SW2/2, AMC-SW2/3, and AMC-SW2/4.
You can use the new CLI command config system amc to make it easier to
manage your AMC module configuration. You use this command to specify the
type of module inserted into your FortiGate AMC slots. If you have to temporarily
remove the module from the slot, the FortiGate unit keeps the configuration
settings for the module. And when you re-install the module, the FortiGate unit will
recognize it and resume operating with the configuration settings that were in
place before the module was removed.
For example, if you have a FortiGate-ASM-FB4 module installed in AMC slot
SW1, you can enter the following command:
config system amc
set sw1 asm-fb4
end
You can then add configuration settings for the AMC-SW2/1, AMC-SW2/2, AMC-
SW2/3, and AMC-SW2/4 interfaces.
If you shut down your FortiGate unit, remove the FortiGate-ASM-FB4 module, and
re-start the FortiGate unit, the AMC-SW2/1, AMC-SW2/2, AMC-SW2/3, and
AMC-SW2/4 interfaces still appear in web-based manager interface lists, but with
link status down. All configuration settings for these interfaces are also still
available. If you had not entered the above command, the interfaces would have
disappeared from the interface list and the configuration settings would have been
lost.

01-30007-0203-20090112 21
3.0 MR7 new features and changes What’s new in 3.0 MR7
Similarly, if you shut down your FortiGate unit again, reinstall the FortiGate-ASM-
FB4 module (or install a new FortiGate-ASM-FB4 module), and restart the
FortiGate unit the AMC-SW2/1, AMC-SW2/2, AMC-SW2/3, and AMC-SW2/4
interfaces appear in web-based manager interface lists with link status up.
Other options for the config system amc command are described in the
FortiGate CLI Reference.
Dashboard
If you have installed an AMC hard drive, an icon for the drive that displays the
model name appears on the Unit Operation dashboard widget and a disk usage
graph appears on the System Resources widget.
From the System Information widget you can now update firmware from multiple
sources including:
• the system administrators’s local hard drive
• a USB drive connected to the FortiGate unit
• the FortiGuard network (requires a subscription).
For more information see “Upgrading to a new firmware version” on page 82.
The session list available from the Statistics widget now displays the total number
of sessions being processed by the FortiGate unit.
The Top Attacks widget now displays the names of detected attacks, not just the
attack signature number.
FortiGuard Analysis and Management Service

The FortiGuard Analysis and Management Service was integrated into one
FortiGuard service in FortiOS 3.0 MR6; this is now reflected on the License
Information widget.
The FortiGuard Analysis server and the FortiGate unit now communicate using
FCP over HTTPS instead of SSL. This protocol is used by other FortiGuard
services, and also uses port 443.
Virtual domains
FortiOS MR7 includes the following enhancements to Virtual Domains:
• The “Override DNS” feature has been disabled on non-management VDOMs.
• The root domain may not be disabled even if it is not the management VDOM.
• Modems can now be assigned to VDOMs other than the root VDOM, similar to
other interfaces; this means that modems are no longer global.
• FortiAnalyzer report configuration and access is now per-VDOM when VDOMs
are enabled.
• When VDOMs are in both NAT and TP operation modes, some interface fields
will be displayed as “-”. Only the super admin can view all the VDOMs.
• Packets that pass through inter-VDOM links have their inter-VDOM link
counter reset when they are encrypted or decrypted. Previously packets were
limited to a maximum of three passes through inter-VDOM links.
For more information, see “Using virtual domains” on page 95.

22 01-30007-0203-20090112
VDOM and Global icons in documentation

When you select help for a VDOM configuration web-based
manager page, the help display includes the VDOM icon.
When you select help for a Global configuration web-based
manager page, the help display includes the Global icon.
VDOM and global icons also appear in the FortiGate Administration Guide to
indicate whether a chapter or section is part of the VDOM or global configuration.
If you are not operating your FortiGate unit with virtual domains enabled, you can
ignore these icons in the documentation. VDOM and global configuration settings
are only meaningful for a FortiGate unit with virtual domains enabled.
Modem support
You can now connect a supported USB modem to the USB port of any FortiGate
model that includes a USB port. Previously only models with internal modems
supported USB modems. For more information, see “Configuring the modem
interface” on page 129.
Because PPP echo requests are not supported by all ISPs, a flag has been added
to the modem configuration to disable PPP echo requests if required.
You must use the config system modem CLI command to enable a modem
before it will display in the web-based manager interface list.
SNMP
The following commands were added to the CLI to reflect the new events added
to SNMP communities:
• av-bypass
• av-conserve
• av-oversize-blocked
• av-oversize-pass
• ips-pkg-update
• power-supply-failure (FortiGate-3810A and 3016B models support
managed power supplies).
Previously, a trap could be triggered by a transient high CPU spike. This problem
has now been fixed.
You can now view a complete list of SNMP MIBs that FortiOS supports from the
support web site. If you have a subscription to central management services, this
service allows you to generate an HTML file of the complete, current list of MIBs.
Router
The web-based manager checks RIP timer values and will display an error
message if the timers are incorrect. For example, update timer has to be smaller
than the timeout or garbage timers. For more information see “Selecting
advanced RIP options” on page 270.
For the config router bgp command, the router-id field now has a default
value. If the router-id is not set, the highest IP address in this VDOM will be
used.
The maximum number of configurable BGP neighbors is now 1,000.

01-30007-0203-20090112 23
Authentication
The maximum number of remote authentication servers (LDAP, RADIUS, and
TACACS+) has been increased from 6 to 10.
The Distinguished Name (DN) for LDAP has been increased to 512 characters.
For the following FortiGate models, the maximum number of local certificates has
been increased as follows:
• FortiGate-50/60B/100/200 - 200
• FortiGate-300 through FG1000 - 500
• FortiGate-3000 and up - 1,000.
SSL VPN client tunnel mode for Mac OS and Linux

SSL VPN users can now initiate SSL VPN tunnel sessions using the Mac OS and
Linux operating systems.
A SSL VPN Client OS Patch Check feature allows a client with a specific OS patch
to access the SSL VPN service. The current version supports Windows 2000 and
Windows XP.
Standalone SSL VPN client

Standalone SSL VPN tunnel client applications are now available for Windows,
Linux, and MacOS operating systems. System administrators can pre-install one
of these standalone SSL VPN clients on a user's computer. After the SSL VPN
client is installed, any user that can log in to the computer can establish an SSL
VPN tunnel session without downloading the SSL VPN client, as long as that user
can log in to the SSL VPN web portal. The standalone client also allows users to
initiate SSL VPN sessions without keeping a browser window open.
SSL VPN Virtual Desktop application

An SSL VPN Virtual Desktop application is now available for the Windows
operating system. The Virtual Desktop application functions like the standalone
SSL VPN client but includes additional features. For example, the Virtual Desktop
application provides enhanced security by deleting unencrypted cached SSL
session data that can be left behind when an SSL session is terminated
abnormally.
SSL VPN URL obscuration

For the config ssl settings CLI command you can enable url-
obscuration to encrypt the host name of the url in the display (web address) of
the browser for web mode only. See the FortiGate CLI Reference.
Intrusion Protection
Intrusion protection filters contain more information about the type and number of
signatures that are included in the filter. See “Configuring IPS sensors” on
page 470.
A new “Count” column has been added to the filters list. This column displays the
number of signatures are included in the filter.
Each filter also has a View Rules icon that, when selected, displays a complete list
of the included signatures.

24 01-30007-0203-20090112
Log messages
FortiOS 3.0 MR7 includes the following changes to log messages:
• There are three new sub-types for the event log: vip ssl, ldb-monitor and
his-performance.
• Log messages now contain the fields device_id and devname to help identify
HA members.
• The new event log sub-type, his-performance, provides information about
FortiGate system performance.
• A log message about adding/deleting a zone is included in the event log.
• Quote marks are now included in the log message where a field in the
message does not contain any information.
• The severity level of IPSec negotiation logs is now Notification; alert email now
sends any IPSec tunnel error message with a severity of Error or higher.
• When an administrator disables one or more VDOMs, an event log message is
recorded.
• The count field has been added to attack logs to indicate the number of attack
reports on the FortiGate side.
• An event log message is recorded when the connection between the
FortiGuard Analysis server the FortiGate unit goes up or down.
See the FortiGate Logging Technical Note and the FortiGate Log Message
Reference for more information:
Content archiving
Previously, to content archive HTTP, FTP, SMTP, POP3, and IMAP data, you had
to enable virus scanning. To content archive HTTPS data you had to enable Web
URL filtering.
In FortiOS 3.0 MR7, you can now content archive all of these protocols without
enabling these additional features.
Alert email
Depending on your configuration, in FortiOS 3.0 MR7 not all alert email categories
are displayed in Log&Report > Log Config. If you have VDOMs enabled, you will
not see FortiGuard options.
The following alert email categories are also not available:
• Disk usage warning (if your FortiGate unit does not contain a hard disk)
• SSL VPN login failure (if you are using Transparent mode)
• L2TP/PPPTP/PPPoE errors (if you are using Transparent mode).
You can now change the port to use for sending alert email messages by using
the port keyword of the config system global CLI command.
Reports
Because of changes to FortiAnalyzer reports brought about by FortiAnalyzer 3.0
MR7, the FortiGate Report Access and Report Config settings and pages have
changed as well.

01-30007-0203-20090112 25
In Log&Report > Report Config, there is a new tab called Schedule. The
Schedule tab displays all report schedules that have been configured for your
FortiGate unit, both from the FortiGate web-based manager and the FortiAnalyzer
web-based manager. This tab also allows you to configure report schedules,
provided there is a report profile.
After upgrading to FortiOS 3.0 MR7, all previously configured reports are
converted to their equivalent in FortiOS 3.0 MR7. This conversion process splits
previously configured reports into two: one report layout and one schedule. This
split may not contain all the settings previously configured because of the new
settings in FortiOS 3.0 MR7. We recommend that you review all reports carried
forward from FortiOS 3.0 MR6 and familiarize yourself with how reports are now
configured, from both the FortiGate and FortiAnalyzer web-based managers.
For more information about configuring report schedules in FortiOS 3.0 MR7, see
“FortiAnalyzer report schedules” on page 551. For additional information, see the
FortiAnalyzer Administration Guide.
Email archiving
Using the FortiGate internal or AMC hard disk, FortiOS 3.0 MR7 provides
failure-proof email archiving by first storing email archive data on the internal or
AMC hard disk.
If you are using the FortiGuard Analysis and Management Service, the FortiGate
unit uploads and verifies content archived data to the FortiGuard Analysis and
Management Service in small batches to reduce overhead. The data is not
deleted from the internal or AMC hard disk until it has been successfully uploaded
to and verified on the FortiGuard Analysis and Management Service.
A similar approach is taken with archiving to a FortiAnalyzer unit, except that only
the AMC hard disk can be used to store archived data on the FortiGate unit and
archived data is uploaded in batches according to a specified schedule.
HA primary unit acts as a router for subordinate unit management traffic

FortiOS 3.0 MR7 HA improves performance and resolves some known HA issues
by using routing and inter-VDOM links to route subordinate unit management
traffic through the primary unit to the network. Similar to a standalone FortiGate
unit, subordinate units may generate their own management traffic, including:
• DNS queries
• FortiGuard Web Filtering rating requests
• Log messages to be sent to a FortiAnalyzer unit, to a syslog server, or to the
• Log file uploads to a FortiAnalyzer unit
• Quarantine file uploads to a FortiAnalyzer unit
• SNMP traps.
Subordinate units send this management traffic over the HA heartbeat link to the
primary unit. The primary unit forwards the management traffic to its destination.
Previously, the primary unit used an HA proxy for all subordinate unit
management traffic. This proxy design meant that the primary unit acted like an
application-level firewall or proxy server for the subordinate unit. However, this
design has some limitations.

26 01-30007-0203-20090112
Now the primary unit acts like a router for most subordinate unit management
traffic. Instead of sending management traffic to the HA proxy, the subordinate
unit sends traffic to its destination over the HA heartbeat link. The primary unit
uses simple routing to send the traffic through the primary unit and on to its
destination. The primary unit also routes replies back to the subordinate unit in the
same way.
HA uses a hidden VDOM called vsys_ha for HA operations. The vsys_ha VDOM
includes the HA heartbeat interfaces, and all communication over the HA
heartbeat link goes through the vsys_ha VDOM. To provide communication from a
subordinate unit to the network, HA adds hidden inter-VDOM links between the
primary unit management VDOM and the primary unit vsys_ha VDOM. By default,
root is the management VDOM.
Management traffic from the subordinate unit originates in the subordinate unit
vsys_ha VDOM. The vsys_ha VDOM routes the management traffic over the HA
heartbeat link to the primary unit vsys_ha VDOM. This management traffic is then
routed to the primary unit management VDOM and from there out onto the
network.
Note: DNS queries and FortiGuard Web Filtering rating requests are still handled by the HA
proxy so that the primary unit and subordinate units share the same DNS query cache and
the same FortiGuard Web Filtering cache.
Figure 1: Subordinate unit management traffic path
vsys_ha 169.254.0.1 169.254.0.2 vsys_ha
HA link
169.254.0.65
root 169.254.0.66 root

Network
Primary unit Subordinate unit
HA heartbeat IP addresses
Previously, HA heartbeat interfaces were assigned IP addresses in the 10.0.0.x
range. FortiOS 3.0 MR7 uses link-local IP4 addresses (RFC 3927) in the
169.254.0.x range for HA heartbeat interface IP addresses and for inter-VDOM
link interface IP addresses. When a cluster initially starts up, the primary unit
heartbeat interface IP address is 169.254.0.1. Subordinate units are assigned
heartbeat interface IP addresses in the range 169.254.0.2 to 169.254.0.63. HA
inter-VDOM link interfaces on the primary unit are assigned IP addresses
169.254.0.65 and 169.254.0.66.
The ninth line of the following CLI command output shows the HA heartbeat
interface IP address of the primary unit.

01-30007-0203-20090112 27
get system ha status

Model: 5000
Mode: a-p
Group: 0
Debug: 0
ses_pickup: disable
Master:128 5001_slot7 FG50012205400050 0
Slave :100 5001_slot11 FG50012204400045 1
number of vcluster: 1
vcluster 1: work 169.254.0.1
Master:0 FG50012205400050
Slave :1 FG50012204400045
You can also use the execute traceroute command from the subordinate unit
CLI to display HA heartbeat IP addresses and the HA inter-VDOM link IP
addresses. For example, use execute ha manage 1 to connect to the
subordinate unit CLI and then enter the following command to trace the route to
an IP address on your network:
execute traceroute 172.20.20.10
traceroute to 172.20.20.10 (172.20.20.10), 32 hops max, 72 byte packets
1 169.254.0.1 0 ms 0 ms 0 ms
2 169.254.0.66 0 ms 0 ms 0 ms
3 172.20.20.10 0 ms 0 ms 0 ms
Interface display order

FortiOS 3.0 MR7 has changed the order in which the FortiGate web-based
manager displays interface names. The web-based manager now sorts interface
names in alphanumeric order. For example, the new sort order for a FortiGate unit
with 10 interfaces (named port1 through port10) places port10 at the bottom of the
list:
• port1
• port2 through 9
• port10
Previously, interface names were displayed in hash map order, rather than purely
by alphabetic order or purely by interface number value comparisons. As a result,
the list was sorted primarily in alphabetic order by interface name (for example,
base1 is before port1), then secondarily by index numbers:
• port1
• port10
• port2 through port9
Note: This change does not interfere with HA heartbeat interface failover. In FortiOS 3.0
MR7 as well as previous FortiOS versions, HA heartbeat interface failover uses the same
hash map order to select the HA heartbeat interface to use. If more than one HA heartbeat
interface has the highest priority, the interface with the highest priority that is also highest in
the interface hash map order is used for all HA heartbeat communication. If this interface
fails or becomes disconnected, the heartbeat interface with the highest priority that is next
highest in hash map order handles all heartbeat communication. For information about HA
heartbeat interfaces, see “HA options” on page 167.

28 01-30007-0203-20090112
Introduction Introducing the FortiGate units
Introduction
Welcome and thank you for selecting Fortinet products for your real-time network
protection.
FortiGate™ ASIC-accelerated multi-threat security systems improve network
security, reduce network misuse and abuse, and help you use communications
resources more efficiently without compromising the performance of your
network. FortiGate Systems are ICSA-certified for Antivirus, Firewall, IPSec,
SSL-TLS, IPS, Intrusion detection, and AntiSpyware services.
FortiGate Systems are dedicated, easily managed security devices that deliver a
full suite of capabilities including:
• Application-level services such as virus protection, intrusion protection, spam
filtering, web content filtering, IM, P2P, and VoIP filtering
• Network-level services such as firewall, intrusion detection, IPSec and SSL
VPN, and traffic shaping
• Management services such as user authentication, logging, reporting with
FortiAnalyzer, administration profiles, secure web and CLI administrative
access, and SNMP.
The FortiGate security system uses Fortinet’s Dynamic Threat Prevention System
(DTPS™) technology, which leverages breakthroughs in chip design, networking,
security and content analysis. The unique ASIC-accelerated architecture analyzes
content and behavior in real-time, enabling key applications to be deployed right
at the network edge where they are most effective at protecting your networks.
This chapter contains the following sections:
• Introducing the FortiGate units
• Fortinet family of products
• About this document
• FortiGate documentation
• Customer service and technical support
• Register your Fortinet product
Introducing the FortiGate units

All FortiGate Unified Threat Management Systems deliver similar SOHO or
enterprise-class network-based antivirus, content filtering, firewall, VPN, and
network-based intrusion detection/prevention features. In addition to these
features, FortiGate units running FortiOS Carrier also deliver MMS content
processing and GTP protection.

01-30007-0203-20090112 29
Introducing the FortiGate units Introduction
FortiGate-5000 series chassis

The FortiGate-5000 series Security Systems are chassis-based systems that
MSSPs and large enterprises can use to provide subscriber security services
such as firewall, VPN, antivirus protection, spam filtering, web filtering and
intrusion prevention (IPS). The wide variety of system configurations available
with FortiGate-5000 series provide flexibility to meet the changing needs of
growing high performance networks. The FortiGate-5000 series chassis support
multiple hot-swappable FortiGate-5000 series boards and power supplies. This
modular approach provides a scalable, high-performance and failure-proof
solution.
5140SAP SERIAL 1 SERIAL 2 ALARM
5140 T CA
L R R 1 2 3
SE ITI MAJO MINO USER USER USER
RE CR
13 11 9 7 5 3 1 2 4 6 8 10 12 14
CONSOLE USB 1 2 3 4 5 6 7 8
5 PWR ACC STA IPM
PWR ACC
PWR ACC
PWR ACC
PWR ACC
PWR ACC
PWR ACC
PWR ACC
PWR ACC
PWR ACC
PWR ACC
PWR ACC
PWR ACC
MANAGEMENT MANAGEMENT CONSOLE USB 1 2 3 4 5 6 7 8
E E
4
CONSOLE
CONSOLE
CONSOLE
CONSOLE
CONSOLE
CONSOLE
T T
H H PWR ACC STA IPM
O O
CONSOLE
CONSOLE
CONSOLE
CONSOLE
CONSOLE
CONSOLE
CONSOLE USB 1 2 3 4 5 6 7 8
USB
USB
USB
USB
USB
USB
3
USB
USB
USB
USB
USB
USB
SYSTEM SYSTEM PWR ACC STA IPM
CONSOLE CONSOLE
R R
S S
2 2
1
3 3
2 2
HOT SWAP
1
O
H
E
R
MANAGEMENT
E
Z
Z
2
3
2
2
2
FLT
INT
Z Z
OK
E1
SYSTEM
CONSOLE
LED MODE
15
13
RESET
11
R R
1
E E
ZRE
0 0
POWER
14
12
10
E2
CLK
8
EXT
FLT
Z Z
2
R R
5000SM
ETH0 ETH1
E E
1 1
10/100
10/100
link/Act
link/Act
HOT SWAP
O
H
E
R
MANAGEMENT
E
Z
Z
2
3
2
2
1
FLT
INT
OK
E1
SYSTEM
CONSOLE
LED MODE
15
13
RESET
11
Z Z
1
3
3
R R
ZRE
E E
3
2 2 ETH0
Service
14
12
10
E2
CLK
8
EXT
FLT
E2 E1 E2 E1
RESET
14 15 14 15
STATUS
4
12 13 12 13
4
10 11 10 11
5000SM
5050SAP 5000SM
SMC SMC
Hot Swap
Hot Swap
Service
Service
STATUS
STATUS
8 9 8 9
ETH0
ETH0
10/100 10/100
ETH0 ETH1
ETH0 ETH1
Hot Swap
ALARM
RESET
RESET
link/Act SERIAL SERIAL link/Act
2 1
6 7 6 7 10/100
1 2 10/100
link/Act link/Act
5
4 5 4 5
5
2 3 2 3
0 1 0 1
ZRE ZRE
12
6
6
6
CLK OK CLK OK
EXT INT EXT INT
FLT FLT FLT FLT
5000SM
ETH0 ETH1
7
7
7
HOT SWAP HOT SWAP
10/100
10/100
link/Act
link/Act
RESET RESET
8
8
ETH0
LED MODE LED MODE Service
STA IPM
STA IPM
STA IPM
STA IPM
STA IPM
STA IPM
RESET
STA IPM
STA IPM
STA IPM
STA IPM
STA IPM
STA IPM
STATUS
Hot Swap
PSU A
PSU B
FILTER
USB CONSOLE 1 62 53 4 5 6
ALT
RESET ON/OFF
STATUS PWR IPM
USB CONSOLE 1 62 53 4 5 6
ALT
RESET ON/OFF
STATUS PWR IPM
0 FA N T R AY 1 FA N T R AY 2 FA N T R AY
FortiGate-5140 chassis
You can install up to 14 FortiGate-5000 series boards in the 14 slots of the
FortiGate-5140 ATCA chassis. The FortiGate-5140 is a 12U chassis that contains
two redundant hot swappable DC power entry boards that connect to -48 VDC
Data Center DC power. The FortiGate-5140 chassis also includes three hot
swappable cooling fan trays.
You can install up to five FortiGate-5000 series boards in the five slots of the
two redundant DC power connections that connect to -48 VDC Data Center DC
power. The FortiGate-5050 chassis also includes a hot swappable cooling fan
tray.
You can install one or two FortiGate-5000 series boards in the two slots of the
two redundant AC to DC power supplies that connect to AC power. The
FortiGate-5020 chassis also includes an internal cooling fan tray.

30 01-30007-0203-20090112
About the FortiGate-5000 series boards

Each FortiGate-5000 series board is a standalone security system that can also
function as part of an HA cluster. All FortiGate-5000 series boards are also hot
swappable. All FortiGate-5000 series units are high capacity security systems
with multiple gigabit interfaces, multiple virtual domain capacity, and other high
end FortiGate features. FortiOS Carrier runs on FortiGate-5000 series boards.
FortiGate-5001A board
The FortiGate-5001A board is a high-performance ACTA-compliant security
system that contains two front panel gigabit ethernet interfaces, two base
backplane gigabit interfaces, and two fabric backplane gigabit interfaces. The
fabric interfaces are reserved for future 10-gigabit operation but can be used now
for board to board 1-gigabit operation. The FortiGate-5001A-DW front panel also
includes a double-width Advanced Mezzanine Card (AMC) opening. You can
install a supported FortiGate ADM module such as the FortiGate-ADM-XB2 or the
FortiGate-ADM-FB8 in the AMC opening. The FortiGate-ADM-XB2 adds two
accelerated 10-gigabit interfaces to the FortiGate-5001A board and the
FortiGate-ADM-FB8 adds 8 accelerated 1 gigabit interfaces.
The FortiGate-5001A board supports high-end features including 802.1Q VLANs
and multiple virtual domains and FortiOS Carrier MMS content processing, GTP
protection, and SIP extensions.
FortiGate-5005FA2 board
The FortiGate-5001SX board is an independent high-performance
ACTA-compliant security system with eight Gigabit ethernet interfaces; two of
which include Fortinet technology to accelerate small packet performance. The
FortiGate-5005FA2 board also supports high-end features including 802.1Q
VLANs, multiple virtual domains and specialized FortiGate-5000 series features
such as base and fabric backplane switching and FortiOS Carrier MMS content
processing, GTP protection, and SIP extensions.
FortiGate-5001SX board
The FortiGate-5001SX board is an independent high-performance
ACTA-compliant security system with eight Gigabit ethernet interfaces. The
FortiGate-5001SX board supports high-end features including 802.1Q VLANs and
multiple virtual domains and specialized FortiGate-5000 series features such as
base and fabric backplane switching and FortiOS Carrier MMS content
processing, GTP protection, and SIP extensions.
FortiGate-5001FA2 board
The FortiGate-5001FA2 board is an independent high-performance
ACTA-compliant security system with six Gigabit ethernet interfaces. The
FortiGate-5001FA2 board is similar to the FortiGate-5001SX board except that
two of the FortiGate-5001FA2 interfaces include Fortinet technology to accelerate
small packet performance.

01-30007-0203-20090112 31
FortiGate-5002FB2 board
The FortiGate-5002FB2 board is an independent high-performance ACTA
compliant FortiGate security system with a total of 6 Gigabit ethernet interfaces.
Two of the FortiGate-5002FB2 interfaces include Fortinet technology to accelerate
small packet performance.
FortiGate-AMC modules
The FortiGate-AMC modules (including the HS
OOS
FortiGate-ADM-XB2, FortiGate-ADM-FB8, PWR

OT
FortiGate-ASM-FB4, and the FortiGate-ASM-SO8) LINK

1
ACT LINK
2
ACT LINK
3
ACT LINK
4
ACT
add additional capabilities such as accelerated ASM-FB4
interfaces, hard disk space and so on to FortiGate

units, such as the FortiGate-3600A unit, FortiGate-3810unit , and the
FortiGate-5001A board that contain AMC slots.
FortiGate-3810A
The FortiGate-3810A
multi-threat security AMC-SW1 AMC-DW1
appliance is the first -E4
standalone security AMC-SW2 AMC-DW2

USB
1 2 3 4 5 6 7 8 9 10
Esc Enter CONSOLE AUX
STATUS
POWER
appliance offering
optional 10-Gigabit
Ethernet interfaces. Four AMC expansion slots allow the FortiGate-3810A to be
customized for your exact performance needs. Up to 26 Gbps firewall
performance can be achieved in a full configuration with just a single 2U rack-
mount appliance.
The FortiGate-3810A includes:
• Base unit provides eight 10/100/1000 interfaces plus two SFP (fiber) interfaces
• Supports two dual-width and two single-width AMC expansion modules
• Dual-width AMC slots support up to four 10-Gigabit Ethernet XFP interfaces
• Single-width AMC slots support up to eight additional Gigabit Ethernet SFP
interfaces
FortiGate-3600A
The FortiGate-3600A
multi-threat security
appliance establishes
a new level of price- CONSOLE
performance and Esc Enter

PWR
Hi-Temp
1 3 5 7 9
flexibility for multi- 2 4 6 8 10

MODEM USB
gigabit capacity
network security systems. With ten gigabit Ethernet interfaces and up to six Gbps
throughput, the FortiGate-3600A enables a new generation of high performance
protection against blended threats.
The FortiGate-3600A includes
• Multi-Gigabit performance for large enterprises and Managed Security Service
Providers (MSSPs) ensures security and throughput

32 01-30007-0203-20090112
• Provides eight gigabit copper (10/100/1000) interfaces and two gigabit fiber
(SFP) interfaces for greater flexibility and to meet the needs of large enterprise
and service provider networks
• Advanced Mezzanine Card (AMC) slot provides future upgrade possibilities
with either the four interface hardware accelerated SFP expansion module or
the storage expansion module.
FortiGate-3016B
The FortiGate-3016B
multi-threat security
appliance is a carrier- FG-AMC-SW CONSOLE 1 3 5 7 9 11 13 15 17
class device with Esc Enter POWER

STATUS
MODEM 2 4 6 8 10 12 14 16 18
sixteen gigabit
Ethernet interfaces
and a full complement of network protection features. Each interface of the
FortiGate-3016B provides wire-speed firewall performance using Fortinet's
advanced FortiASIC network processor technology. Multiple FortiGate-3016Bs
can be deployed in redundant clusters to ensure failsafe operation.
The FortiGate-3016B is the ideal solution for large enterprises and Managed
Security Service Providers (MSSPs) looking to add new security services.
The highly available architecture and redundant hot-swappable power supplies
ensure failsafe operation, and AMC expansion provide additional connectivity,
performance and storage capacity.
FortiGate-3600
The FortiGate-3600
unit provides carrier- Esc Enter
POWER
Hi-Temp
1
4
2
5/HA
3
INT EXT
class levels of
performance and 1 2 3 4 5/HA INTERNAL EXTERNAL
reliability demanded by
large enterprises and
service providers. The unit uses multiple CPUs and FortiASIC chips to deliver
throughput of 4Gbps, meeting the needs of the most demanding applications. The
FortiGate-3600 unit includes redundant power supplies, which minimize single-
point failures, and supports load-balanced operation. The high-capacity, reliability
and easy management makes the FortiGate-3600 a natural choice for managed
service offerings.
FortiGate-3000
The FortiGate-3000
POWER 1 2 3
unit provides the Esc Enter

Hi-Temp 4/HA INT EXT
carrier-class levels of
1 2 3 4/HA INTERNAL EXTERNAL
performance and
reliability demanded
by large enterprises and service providers. The unit uses multiple CPUs and
FortiASIC chips to deliver a throughput of 3Gbps, meeting the needs of the most
demanding applications. The FortiGate-3000 unit includes redundant power
supplies to minimize single-point failures, including load-balanced operation and
redundant failover with no interruption in service. The high capacity, reliability, and
easy management of the FortiGate-3000 makes it a natural choice for managed
service offerings.

01-30007-0203-20090112 33
FortiGate-1000A/AFA2
The FortiGate-1000A/AFA2 Security System is a high performance solution that
delivers gigabit throughput with exceptional reliability for the most demanding
large enterprise. The FortiGate-1000AFA2 optionally provides 2 additional fiber
interfaces featuring FortiAccel ASIC technology enhancing small packet
performance. The FortiGate-1000A/AFA2 deploys easily in existing networks and
can be used for antivirus and content filtering only or can be deployed as a
complete network protection solution. High Availability (HA) operation and
redundant hot-swappable power supplies ensure non-stop operation in mission-
critical applications.
The FortiGate-1000A
offers 10 tri-speed
10/100/1000 Base-TX
interfaces.
The FortiGate-
1000AFA2 offers 10
tri-speed interfaces + CONSOLE USB
two Small Form-factor A1 A2
Pluggable (SFP)
FortiAccel ASIC
accelerated interfaces for line rate performance of all packet sizes ideal for
applications such as VOIP.
FortiGate-1000
The FortiGate-1000 unit is
designed for larger Esc Enter 1 2 3 4 / HA INTERNAL EXTERNAL
enterprises. The FortiGate-

1000 meets the needs of the most demanding applications, using multiple CPUs
and FortiASIC chips to deliver a throughput of 2Gps. The FortiGate-1000 unit
includes support for redundant power supplies to minimize single-interface
failures, load-balanced operation, and redundant failover with no interruption in
service.
FortiGate-800/800F
The FortiGate-800/800F INTERNAL EXTERNAL DMZ HA 1 2 3 4 CONSOLE USB
Multi-Threat Security 8
Esc Enter
PWR
system provides the

performance, flexibility, and security necessary to protect today's most demanding
large enterprise networks. The FortiGate-800 can be deployed as a high
performance antivirus and web content filtering gateway, or as a complete network
protection solution leveraging firewall, VPN, IPS and antispam capabilities.
The FortiGate-800 Multi- PWR
INTERNAL EXTERNAL DMZ HA 1 2 3 4 CONSOLE USB
Threat Security system 800F

Esc Enter
features four 10/100/1000

tri-speed ethernet interfaces for networks running at gigabit speeds and four user-
definable 10/100 interfaces that provide granular security through multi-zone
capabilities, allowing administrators to segment their network into zones and
create policies between zones.

34 01-30007-0203-20090112
FortiGate-500A
The FortiGate-500A Multi- CONSOLE USB LAN 10/100 10/100/1000
Esc Enter
Threat Security system

L1 L2 L3 L4 1 2 3 4 5 6
provides higher
performance, flexibility, and security necessary to protect today's growing
enterprise networks. The FortiGate-500A platform features two 10/100/1000 tri-
speed ethernet interfaces providing flexibility for networks running at or upgrading
to gigabit speeds, four user-definable 10/100 interfaces for redundant WAN links,
high availability, and multi-zone capabilities that allow administrators a high
degree of flexibility to segment their network into zones for granular control of
network traffic, and an internal 4-port switch for direct connectivity with the
FortiGate-500A.
The FortiGate-500A is ideally suited for enterprise networks, the FortiGate-500A
is unmatched in capabilities, speed, and price/performance.
FortiGate-500
The FortiGate-500 unit is INTERNAL EXTERNAL DMZ HA 1 2 3 4 5 6 7 8
designed for larger Esc Enter
enterprises. The flexibility,

reliability, and easy management makes the FortiGate-500 a natural choice for
managed service offerings. The FortiGate-500 supports high availability (HA).
FortiGate-400A
The FortiGate-400A Multi-
CONSOLE USB 10/100 10/100/1000
Threat Security system A

Esc Enter 1 2 3 4 5 6
provides higher
performance, flexibility, and security necessary to protect today's growing
enterprise networks. The FortiGate-400A platform features two 10/100/1000 tri-
speed ethernet interfaces for networks running at or upgrading to gigabit speeds
and 4 user-definable 10/100 interfaces provide redundant WAN links, high
availability, and multi-zone capabilities, allowing administrators a high degree of
flexibility to segment their network into zones and create policies to control
network traffic between zones.
You can deploy the FortiGate-400A as a high performance antivirus and web
content filtering gateway, or as a complete network protection solution leveraging
firewall, intrusion detection and prevention, spam filtering and VPN capabilities.
FortiGate-400
CONSOLE 1 2 3 4 / HA
designed for larger Esc Enter

400 unit is capable of throughput up to 500Mbps and supports high availability
(HA), which includes automatic failover with no session loss.

01-30007-0203-20090112 35
FortiGate-310B
The FortiGate-310B is NP2 Powered
STATUS
designed to raise the POWER

ALARM
HA
1/2 3/4 5/6 7/8 9/10 USB CONSOLE ASM
expectations of mid-range
security devices. Incorporating FortiASIC network processors for firewall/VPN
acceleration and the FortiASIC Content Processor for content inspection
acceleration, the FortiGate-310B yields unmatched multi-threat performance
metrics. AMC module options offer both flexibility and the highest port density of
any product in its class. The FortiGate-310B's accelerated security throughput and
high port density relieves medium sized organizations of the restraints that have
historically prevented internal network security segmentation.
The FortiGate-310B includes:
• 8 Gbps firewall, 6 Gbps VPN as a base model
• 12 Gbps firewall, 9 Gbps VPN with optional AMC module
• SSL hardware acceleration
• Link aggregation
• Customizable expansion options
• Facilitates LAN security segmentation.
FortiGate-300A
The FortiGate-300A Multi-
CONSOLE USB 10/100 10/100/1000
Threat Security system

Esc Enter 1 2 3 4 5 6
provides performance,
flexibility, and security necessary to protect today's growing small and medium
sized enterprise networks. The FortiGate-300A platform features two 10/100/1000
tri-speed ethernet interfaces for networks running at or upgrading to gigabit
speeds and 4 user-definable 10/100 interfaces.
FortiGate-300
designed for larger
Esc Enter

300 unit features high availability (HA), which includes automatic failover with no
session loss. This feature makes the FortiGate-300 an excellent choice for
mission-critical applications.
FortiGate-224B
The FortiGate-224B converges 1 3 5 7 9 11 13 15 17 19 21 23
25 26 WAN1 WAN2 USB CONSOLE
network and security products 2 4 6 8 10 12 14 16 18 20 22 24
that uniquely integrate multiple

layers of threat protection with granular network access controls. The
FortiGate-224B delivers configurable interface-level access control that combines
traditional FortiOS security technologies with layer 2 switching hardware. The
result is a complete and effective Local Area Network (LAN) security solution.
The FortiGate-224B integrates enhanced network security through the
enforcement of security policy at the interface level. The FortiGate-224B provides
multi-layered protection against intrusion attempts, viruses, worms, denial of
service attacks, spyware and blended threats.

36 01-30007-0203-20090112
FortiGate-200A
The FortiGate-200A Multi- CONSOLE USB INTERNAL DMZ1 DMZ2 WAN1 WAN2
1 2 3 4
Threat Security system is an A

Esc Enter
ideal solution for small to

medium sized businesses. The FortiGate-200A platform features dual WAN link
support for redundant internet connections, and an integrated 4-port switch that
eliminates the need for an external hub or switch, giving networked devices a
direct connection to the FortiGate-200A unit.
The FortiGate-200A delivers high performance for small to mid-sized
organizations that require real-time network security services and features four
routed 10/100 interfaces with a 4-port Internal switch interface.
FortiGate-200
designed for small
businesses, home offices or POWER STATUS INTERNAL EXTERNAL DMZ
CONSOLE INTERNAL EXTERNAL DMZ
even branch office

applications. The FortiGate-
200 unit is an easy-to-deploy and easy-to-administer solution. The FortiGate-200
also supports high availability (HA).
FortiGate-100A
The FortiGate-100A system is an
ideal solution for small offices. The PWR STATUS WAN 1 WAN 2 DMZ 1 DMZ 2 1 2
INTERNAL
3 4
FortiGate-100A features dual WAN A

LINK 100 LINK 100 LINK 100 LINK 100 LINK 100 LINK 100 LINK 100 LINK 100
link support for redundant internet

connections, and an integrated 4-port switch that eliminates the need for an
external hub or switch, giving networked devices a direct connection to the
FortiGate-100A.
The FortiGate-100A has dual DMZ interfaces provide additional network
segmentation for web and mail servers and dual WAN interfaces support
redundant, load-balanced links to multiple ISPs.
FortiGate-100
The FortiGate-100 unit is designed
for SOHO, SMB and branch office
applications.
POWER
INTERNAL EXTERNAL DMZ
STATUS
The FortiGate-100 supports

advanced features such as 802.1Q
VLAN, virtual domains, high availability (HA), and the RIP and OSPF routing
protocols.

01-30007-0203-20090112 37
FortiGate-60B
The FortiGate-60B multi-threat
security solution offers Small and 1
INTERNAL
3 5
Medium Business and B

POWER STATUS HA ALARM WAN 1 WAN 2 DMZ 2 4 6
SOHO/ROBO users enterprise-

class protection against blended
threats targeting 3G broadband, wireless LAN and wired infrastructure. The
FortiGate-60B supports a wide array of wireless broadband PC Cards. The
FortiGate-60B offers enterprise-class security for the SOHO/ROBO users and the
flexibility needed for quick Point of Sales deployment.
FortiGate-60B offers a PC Card slot, dual WAN link support for redundant internet
connections, a DMZ interface and 6 built-in switch interfaces. The FortiGate-60B
also offers an integrated analog modem for dial backup capability.
The FortiGate-60B is ideal for small businesses and enterprise remote offices
where complete security including Firewall, IPSec and SSL VPN, Intrusion
prevention, Antivirus, Web filtering and Antispam are needed.
The FortiGate-60B also supports wide range of 3G wireless PC Cards for instant
Point of Sales deployment.
FortiWiFi-60B
The FortiWiFi-60B multi-threat
security solution offers Small and
Medium Business and SOHO/ROBO
users enterprise-class protection
against blended threats targeting 3G
broadband, wireless LAN and wired
infrastructure. The FortiWiFi-60B 1
INTERNAL
3 5
supports a wide array of wireless POWER STATUS HA ALARM Wifi WAN 1 WAN 2 DMZ 2 4 6
B
broadband PC Cards and optional
built-in 802.11 a/b/g wireless support.
The FortiWiFi-60B offers enterprise-class security for the SOHO/ROBO users and
the flexibility needed for quick Point of Sales deployment.
The FortiWiFi-60B is the only dual wireless enabled platform with supports for
both WiFi and 3G wireless simultaneously. Integrated 802.11a/b/g wireless LAN
access point with a DMZ, Dual WAN and 6 switch interfaces provide ample of
connectivity options for the remote office or small size business.
The FortiWiFi-60B supports a wide range of 3G wireless PC Cards to provide an
ideal wireless broadband and wireless LAN gateway
FortiGate-60/60M/ADSL
The FortiGate-60ADSL offers an
INTERNAL
integrated ADSL modem for Internet PWR STATUS 1 2 3 4 DMZ WAN1 WAN2
connectivity. It supports multiple LINK 100 LINK 100 LINK 100 LINK 100 LINK 100 LINK 100 LINK 100
ADSL standards, including ANSI

T1.413 issue 2, ITU G.dmt and ITU G.lite, as well as support for Annex A.
The FortiGate-60ADSL is a complete security system for remote offices and
teleworker sites that connect to the main office using ADSL.
The FortiGate unit has an integrated 4-port switch that leverages scarce
resources and management overhead by eliminating the need for an external hub
or switch.

38 01-30007-0203-20090112
FortiWiFi-60/60A/60AM
The FortiWiFi-60 model provides a
secure, wireless LAN solution for
wireless connections. It combines
mobility and flexibility with FortiWiFi
Antivirus Firewall features, and can
be upgraded to future radio
technologies. The FortiWiFi-60
serves as the connection point INTERNAL
PWR WLAN 1 2 3 4 DMZ WAN1 WAN2
between wireless and wired networks LINK 100 LINK 100 LINK 100 LINK 100 LINK 100 LINK 100 LINK 100
or the center-point of a standalone

wireless network.
FortiWiFi-50B
The FortiWiFi-50B adds wireless
connectivity by providing standard
802.11 b/g support. The FortiWiFi-
50B can be powered by standard
based Power Over Ethernet (POE)
devices to ease installation and
deployment.
INTERNAL
WAN1
(PoE) WAN2
WLAN LINK / ACT
The FortiWiFi-50B is ideal for remote POWER STATUS

1 2 3
10/100
offices, wireless service providers,

retail stores, broadband telecommuter sites, and many other applications. The
FortiWiFi-50B provides complete real-time network protection for wired and
wireless users through a combination of antivirus, intrusion detection and
prevention, web and email content filtering, firewall and VPN services.
FortiGate-50B
The FortiGate-50B offers dual
WAN interfaces for load WAN1 WAN2
INTERNAL
LINK / ACT
POWER STATUS
balancing or redundant internet 1 2 3

10/100
connections. The FortiGate-50B

provides three integrated switch interfaces for multi-user environments in a small
remote office. It is ideally suited for remote offices, retail stores, broadband
telecommuter sites and many other applications.
The FortiGate-50B provides complete real-time network protection through a
combination of network-based antivirus, web and email content filtering, firewall,
VPN, network-based intrusion detection and prevention, and traffic shaping.
FortiGate-50A
The FortiGate-50A unit is designed for
telecommuters and small remote PWR STATUS
INTERNAL EXTERNAL
A LINK 100 LINK 100
offices with 10 or fewer employees.

The FortiGate-50 unit includes an
external modem interface that can be used as a backup or stand alone connection
to the Internet.

01-30007-0203-20090112 39
Fortinet family of products Introduction
Fortinet family of products

Fortinet offers a family of products that includes both software and hardware
appliances for a complete network security solution including mail, logging,
reporting, network management, and security along with FortiGate Unified Threat
Manager Systems. For more information on the Fortinet product family, go to
www.fortinet.com/products.
FortiGuard Subscription Services

FortiGuard Subscription Services are security services created, updated and
managed by a global team of Fortinet security professionals. They ensure the
latest attacks are detected and blocked before harming your corporate resources
or infecting your end-user computing devices. These services are created with the
latest security technology and designed to operate with the lowest possible
operational costs.
For more information about FortiGuard services, go to the FortiGuard Center at
www.fortiguard.com.
FortiAnalyzer
FortiAnalyzer™ provides network administrators with the information they need to
enable the best protection and security for their networks against attacks and
vulnerabilities. FortiAnalyzer features include:
• collects logs from FortiGate units and syslog devices and FortiClient
• creates hundreds of reports using collected log data
• scans and reports vulnerabilities
• stores files quarantined from a FortiGate unit
The FortiAnalyzer unit can also be configured as a network analyzer to capture
real-time traffic on areas of your network where firewalls are not employed. You
can also use the unit as a storage device where users can access and share files,
including the reports and logs that are saved on the FortiAnalyzer hard disk.
FortiClient
FortiClient™ Host Security software provides a secure computing environment for
both desktop and laptop users running the most popular Microsoft Windows
operating systems. FortiClient offers many features including:
• creating VPN connections to remote networks
• configuring real-time protection against viruses
• guarding against modification of the Windows registry
• virus scanning.
FortiClient also offers a silent installation feature, enabling an administrator to
efficiently distribute FortiClient to several users’ computers with preconfigured
settings.

40 01-30007-0203-20090112
Introduction About this document
FortiManager
FortiManager™ meets the needs of large enterprises (including managed security
service providers) responsible for establishing and maintaining security policies
across many dispersed FortiGate installations. With FortiManager you can
configure multiple FortiGate units and monitor their status. You can also view real-
time and historical logs for FortiGate units. FortiManager emphasizes ease of use,
including easy integration with third party systems.
FortiBridge
FortiBridge™ products are designed to provide enterprise organizations operating
FortiGate units in Transparent mode with continuous network traffic flow in the
event of a power outage or a FortiGate system failure. The FortiBridge unit
bypasses the FortiGate unit to make sure that the network can continue
processing traffic. FortiBridge products are easy to use and deploy, including
providing customizable actions a FortiBridge unit takes in the event of a power
outage or FortiGate system failure.
FortiMail
FortiMail™ provides powerful, flexible heuristic scanning and reporting
capabilities to incoming and outgoing email traffic. The FortiMail unit has reliable,
high performance features for detecting and blocking malicious attachments and
spam, such as FortiGuard Antispam/Antivirus support, heuristic scanning,
greylisting, and Bayesian scanning. Built on Fortinet’s award winning FortiOS and
FortiASIC technology, FortiMail antivirus technology extends full content
inspection capabilities to detect the most advanced email threats.
About this document

This FortiGate Version 3.0 MR7 Administration Guide provides detailed
information about FortiGate™ web-based manager options and how to use them.
This guide also contains some information about the FortiGate CLI.
This administration guide describes web-based manager functions in the same
order as the web-based manager menu. The document begins with a general
description of the FortiGate web-based manager and a description of FortiGate
virtual domains. Following these chapters, each item in the System menu, Router
menu, Firewall menu, and VPN menu gets a separate chapter. Then User,
AntiVirus, Intrusion Protection, Web Filter, AntiSpam, IM/P2P, and Log & Report
are all described in single chapters. The document concludes with a detailed
index.
VDOM and Global icons appear in this administration guide to indicate of a
chapter or the section of a chapter is part of the VDOM configuration or part of the
Global configuration. VDOM and Global configuration settings only apply to a
FortiGate unit operating with virtual domains enabled. No distinction is made
between VDOM and Global configuration settings when virtual domains are not
enabled.

01-30007-0203-20090112 41
About this document Introduction
The most recent version of this document is available from the FortiGate page of
the Fortinet Technical Documentation web site. The information in this document
is also available in a slightly different form as FortiGate web-based manager
online help.
You can find more information about FortiOS v3.0 from the FortiGate page of the
Fortinet Technical Documentation web site as well as from the Fortinet Knowledge
Center.
This administration guide contains the following chapters:
• Web-based manager provides an introduction to the features of the FortiGate
web-based manager, the button bar, and includes information about how to
use the web-based manager online help.
• System Status describes the System Status page, the dashboard of your
FortiGate unit. At a glance you can view the current system status of the
FortiGate unit including serial number, uptime, FortiGuard license information,
system resource usage, alert messages and network statistics. This section
also describes status changes that you can make, including changing the unit
firmware, host name, and system time. Finally this section also describes the
topology viewer that is available on all FortiGate models except those with
model numbers 50 and 60.
• Using virtual domains describes how to use virtual domains to operate your
FortiGate unit as multiple virtual FortiGate units, providing separate firewall
and routing services to multiple networks.
• System Network explains how to configure physical and virtual interfaces and
DNS settings on the FortiGate unit.
• System Wireless describes how to configure the Wireless LAN interface on a
FortiWiFi-60 unit.
• System DHCP provides information about how to configure a FortiGate
interface as a DHCP server or DHCP relay agent.
• System Config contains procedures for configuring HA and virtual clustering,
configuring SNMP and replacement messages, and changing the operation
mode.
• System Certificates explains how to manage X.509 security certificates used
by various FortiGate features such as IPSec VPN and administrator
authentication.
• System Administrators guides you through adding and editing administrator
accounts, defining access profiles for administrators, configuring central
management using the FortiGuard Management Service or FortiManager,
defining general administrative settings such as language, timeouts, and web
administration ports.
• System Maintenance details how to back up and restore the system
configuration using a management computer or a USB disk, use revision
control, enable FortiGuard services and FortiGuard Distribution Network (FDN)
updates, and enter a license key to increase the maximum number of virtual
domains.
• Router Static explains how to define static routes and create route policies. A
static route causes packets to be forwarded to a destination other than the
factory configured default gateway.
• Router Dynamic contains information about how to configure dynamic
protocols to route traffic through large or complex networks.

42 01-30007-0203-20090112
Introduction About this document
• Router Monitor explains how to interpret the Routing Monitor list. The list
displays the entries in the FortiGate routing table.
• Firewall Policy describes how to add firewall policies to control connections
and traffic between FortiGate interfaces, zones, and VLAN subinterfaces.
• Firewall Address describes how to configure addresses and address groups
for firewall policies.
• Firewall Service describes available services and how to configure service
groups for firewall policies.
• Firewall Schedule describes how to configure one-time and recurring
schedules for firewall policies.
• Firewall Virtual IP describes how to configure and use virtual IP addresses and
IP pools.
• Firewall Protection Profile describes how to configure protection profiles for
firewall policies.
• SIP support incudes some high-level information about VoIP and SIP and
describes how FortiOS SIP support works and how to configure the key SIP
features.
• VPN IPSEC provides information about the tunnel-mode and route-based
(interface mode) Internet Protocol Security (IPSec) VPN options available
through the web-based manager.
• VPN PPTP explains how to use the web-based manager to specify a range of
IP addresses for PPTP clients.
• VPN SSL provides information about basic SSL VPN settings.
• User Authentication details how to control access to network resources
through user authentication.
• AntiVirus explains how to enable antivirus options when you create a firewall
protection profile.
• Intrusion Protection explains how to configure IPS options when a firewall
protection profile is created.
• Web Filter explains how to configure web filter options when a firewall
• Antispam explains how to configure spam filter options when a firewall
• IM, P2P & VoIP explains how to configure IM, P2P, and VoIP options when a
firewall protection profile is created. You can view IM, P2P, and VoIP statistics
to gain insight into how the protocols are being used within the network.
• Log&Report describes how to enable logging, view log files, and view the basic
reports available through the web-based manager.
Document conventions
The following document conventions are used in this guide:
• To avoid publication of public IP addresses that belong to Fortinet or any other
organization, the IP addresses used in Fortinet technical documentation are
fictional and follow the documentation guidelines specific to Fortinet. The
addresses used are from the private IP address ranges defined in RFC 1918:
Address Allocation for Private Internets, available at
http://ietf.org/rfc/rfc1918.txt?number-1918.
• Notes and Cautions are used to provide important information:

01-30007-0203-20090112 43
FortiGate documentation Introduction
Note: Highlights useful additional information.
Caution: Warns you about commands or procedures that could have unexpected or
! undesirable results including loss of data or damage to equipment.
Typographic conventions
Fortinet documentation uses the following typographical conventions:
Convention Example
Menu commands Go to VPN > IPSEC > Phase 1 and select Create New.
Keyboard input In the Gateway Name field, type a name for the remote VPN
peer or client (for example, Central_Office_1).
Code examples config sys global
set ips-open enable
end
CLI command syntax config firewall policy
edit id_integer
set http_retry_count <retry_integer>
set natip <address_ipv4mask>
end
Document names FortiGate Administration Guide
File content <HTML><HEAD><TITLE>Firewall
Authentication</TITLE></HEAD>
<BODY><H4>You must authenticate to use this
service.</H4>
Program output Welcome!
Variables <address_ipv4>
The chapter or section contains VDOM configuration settings,
see “VDOM configuration settings” on page 97.
The chapter or section contains Global configuration settings,
see “Global configuration settings” on page 98.
FortiGate documentation
The most up-to-date publications and previous releases of Fortinet product
documentation are available from the Fortinet Technical Documentation web site
at http://docs.forticare.com.
The following FortiGate product documentation is available:
• FortiGate QuickStart Guide
Provides basic information about connecting and installing a FortiGate unit.
• FortiGate Installation Guide
Describes how to install a FortiGate unit. Includes a hardware reference,
default configuration information, installation procedures, connection
procedures, and basic configuration procedures. Choose the guide for your
product model number.

44 01-30007-0203-20090112
Introduction FortiGate documentation
• FortiGate Administration Guide

Provides basic information about how to configure a FortiGate unit, including
how to define FortiGate protection profiles and firewall policies; how to apply
intrusion prevention, antivirus protection, web content filtering, and spam
filtering; and how to configure a VPN.
• FortiGate online help
Provides a context-sensitive and searchable version of the Administration
Guide in HTML format. You can access online help from the web-based
manager as you work.
• FortiGate CLI Reference
Describes how to use the FortiGate CLI and contains a reference to all
FortiGate CLI commands.
• FortiGate Log Message Reference
Available exclusively from the Fortinet Knowledge Center, the FortiGate Log
Message Reference describes the structure of FortiGate log messages and
provides information about the log messages that are generated by FortiGate
units.
• FortiGate High Availability Overview and FortiGate High Availability User
Guide
These documents contain in-depth information about the FortiGate High
Availability (HA) feature and the FortiGate clustering protocol.
• FortiGate IPS User Guide
Describes how to configure the FortiGate Intrusion Prevention System settings
and how the FortiGate IPS deals with some common attacks.
• FortiGate IPSec VPN User Guide
Provides step-by-step instructions for configuring IPSec VPNs using the web-
based manager.
• FortiGate SSL VPN User Guide
Compares FortiGate IPSec VPN and FortiGate SSL VPN technology, and
describes how to configure web-only mode and tunnel-mode SSL VPN access
for remote users through the web-based manager.
• FortiGate PPTP VPN User Guide
Explains how to configure a PPTP VPN using the web-based manager.
• FortiGate Certificate Management User Guide
Contains procedures for managing digital certificates including generating
certificate requests, installing signed certificates, importing CA root certificates
and certificate revocation lists, and backing up and restoring installed
certificates and private keys.
• FortiGate VLANs and VDOMs User Guide
Describes how to configure VLANs and VDOMS in both NAT/Route and
Transparent mode. Includes detailed examples.
Fortinet Tools and Documentation CD

All Fortinet documentation is available from the Fortinet Tools and Documentation
CD shipped with your Fortinet product. The documents on this CD are current for
your product at shipping time. For the latest versions of all Fortinet documentation
visit the Fortinet Technical Documentation web site at http://docs.forticare.com.

01-30007-0203-20090112 45
Customer service and technical support Introduction
Fortinet Knowledge Center

Additional Fortinet technical documentation is available from the Fortinet
Knowledge Center. The knowledge center contains troubleshooting and how-to
articles, FAQs, technical notes, a glossary, and more. Visit the Fortinet Knowledge
Center at http://kc.forticare.com.
Comments on Fortinet technical documentation

Please send information about any errors or omissions in this document, or any
Fortinet technical documentation, to techdoc@fortinet.com.
Customer service and technical support

Fortinet Technical Support provides services designed to make sure that your
Fortinet systems install quickly, configure easily, and operate reliably in your
network.
Please visit the Fortinet Technical Support web site at http://support.fortinet.com
to learn about the technical support services that Fortinet provides.
Register your Fortinet product

Register your Fortinet product to receive Fortinet customer services such as
product updates and technical support. You must also register your product for
FortiGuard services such as FortiGuard Antivirus and Intrusion Prevention
updates and for FortiGuard Web Filtering and AntiSpam.
Register your product by visiting http://support.fortinet.com and selecting Product
Registration.
To register, enter your contact information and the serial numbers of the Fortinet
products that you or your organization have purchased. You can register multiple
Fortinet products in a single session without re-entering your contact information.

46 01-30007-0203-20090112
Web-based manager
Web-based manager
This section describes the features of the user-friendly web-based manager
administrative interface (sometimes referred to as a graphical user interface, or
GUI) of your FortiGate unit.
Using HTTP or a secure HTTPS connection from any management computer
running a web browser, you can connect to the FortiGate web-based manager to
configure and manage the FortiGate unit. The recommended minimum screen
resolution for the management computer is 1280 by 1024.
You can configure the FortiGate unit for HTTP and HTTPS web-based
administration from any FortiGate interface. To connect to the web-based
manager you require a FortiGate administrator account and password. The
web-based manager supports multiple languages, but by default appears in
English on first use.
Figure 2: Example FortiGate-5001SX Web-based manager dashboard (default

configuration)
You can go to System > Status to view detailed information about the status of
your FortiGate unit on the system dashboard. The dashboard displays information
such as the current FortiOS firmware version, antivirus and IPS definition
versions, operation mode, connected interfaces, and system resources. It also
shows whether the FortiGate unit is connected to a FortiAnalyzer unit and a
FortiManager unit or other central management services.

01-30007-0203-20090112 47
Common web-based manager tasks Web-based manager
You can use the web-based manager menus, lists, and configuration pages to
configure most FortiGate settings. Configuration changes made using the
web-based manager take effect immediately without resetting the FortiGate unit or
interrupting service. You can back up your configuration at any time using the
Backup Configuration button on the button bar. The button bar is located in the
upper right corner of the web-based manager. The saved configuration can be
restored at any time.
The web-based manager also includes detailed context-sensitive online help.
Selecting Online Help on the button bar displays help for the current web-based
manager page.
You can use the FortiGate command line interface (CLI) to configure the same
FortiGate settings that you can configure from the web-based manager, as well as
additional CLI-only settings. The system dashboard provides an easy entry point
to the CLI console that you can use without exiting the web-based manager.
This section describes:
• Common web-based manager tasks
• Button bar features
• Contacting Customer Support
• Backing up your FortiGate configuration
• Using FortiGate Online Help
• Logging out
• Web-based manager pages
Common web-based manager tasks

This section describes the following common web-based manager tasks:
• Connecting to the web-based manager
• Changing your FortiGate administrator password
• Changing the web-based manager language
• Changing administrative access to your FortiGate unit
• Changing the web-based manager idle timeout
• Connecting to the FortiGate CLI from the web-based manager
Connecting to the web-based manager

To connect to the web-based manager, you require:
• a FortiGate unit connected to your network according to the instructions in the
QuickStart Guide and Install Guide for your FortiGate unit
• the IP address of a FortiGate interface that you can connect to
• a computer with an Ethernet connection to a network that can connect to the
FortiGate unit
• a supported web browser. See the Knowledge Center articles Supported
Windows web browsers and Using a Macintosh and the web-based manager.

48 01-30007-0203-20090112
Web-based manager Common web-based manager tasks
To connect to the web-based manager

1 Start your web browser and browse to https:// followed by the IP address of the
FortiGate unit interface that you can connect to.
For example, if the IP address is 192.168.1.99, browse to https://192.168.1.99.
(remember to include the “s” in https://).
To support a secure HTTPS authentication method, the FortiGate unit ships with a
self-signed security certificate, which is offered to remote clients whenever they
initiate a HTTPS connection to the FortiGate unit. When you connect, the
FortiGate unit displays two security warnings in a browser.
The first warning prompts you to accept and optionally install the FortiGate unit’s
self-signed security certificate. If you do not accept the certificate, the FortiGate
unit refuses the connection. If you accept the certificate, the FortiGate login page
appears. The credentials entered are encrypted before they are sent to the
FortiGate unit. If you choose to accept the certificate permanently, the warning is
not displayed again.
Just before the FortiGate login page is displayed, a second warning informs you
that the FortiGate certificate distinguished name differs from the original request.
This warning occurs because the FortiGate unit redirects the connection. This is
an informational message. Select OK to continue logging in.
2 Type admin or the name of a configured administrator in the Name field.
3 Type the password for the administrator account in the Password field.
4 Select Login.
Changing your FortiGate administrator password

By default you can log into the web-based manager by using the admin
administrator account and no password. You should add a password to the admin
administrator account to prevent anybody from logging into the FortiGate and
changing configuration options. For improved security you should regularly
change the admin administrator account password and the passwords for any
other administrator accounts that you add.
Note: See the Fortinet Knowledge Center article Recovering lost administrator account
passwords if you forget or lose an administrator account password and cannot log into your
FortiGate unit.
To change an administrator account password

1 Go to System > Admin > Administrators.
This web-based manager page lists the administrator accounts that can log into
the FortiGate unit. The default configuration includes the admin administrator
account.
2 Select the Change Password icon and enter a new password.
3 Select OK.
Note: You can also add new administrator accounts by selecting Create New. For more
information about adding administrators, changing administrator account passwords and
related configuration settings, see “System Administrators” on page 195.

01-30007-0203-20090112 49
Common web-based manager tasks Web-based manager
Changing the web-based manager language

You can change the web-based manager to display language in English,
Simplified Chinese, Japanese, Korean, Spanish, Traditional Chinese, or French.
For best results, you should select the language that the management computer
operating system uses.
To change the web-based manager language

1 Go to System > Admin > Settings.
2 Under display settings, select the web-based manager display language.
3 Select Apply.
The web-based manager displays the dashboard in the selected language. All
web-based manager pages are displayed with the selected language.
Figure 3: System > Admin > Settings displayed in Simplified Chinese
Changing administrative access to your FortiGate unit

Through administrative access an administrator can connect to the FortiGate unit
to view and change configuration settings. The default configuration of your
FortiGate unit allows administrative access to one or more of the interfaces of the
unit as described in your FortiGate unit QuickStart Guide and Install Guide.
You can change administrative access by:
• enabling or disabling administrative access from any FortiGate interface
• enabling or disabling securing HTTPS administrative access to the web-based
manager (recommended)
• enabling or disabling HTTP administrative access to the web-based manager
(not recommended)
• enabling or disabling secure SSH administrative access to the CLI
(recommended)
• enabling or disabling SSH or Telnet administrative access to the CLI (not
recommended).

50 01-30007-0203-20090112
Web-based manager Common web-based manager tasks
To change administrative access to your FortiGate unit

1 Go to System > Network > Interface.
2 Choose an interface for which to change administrative access and select Edit.
3 Select one or more Administrative Access types for the interface.
4 Select OK.
For more information about changing administrative access see “Administrative
access to an interface” on page 125 and “Changing administrative access to your
FortiGate unit” on page 50.
Changing the web-based manager idle timeout

By default, the web-based manager disconnects administrative sessions if no
activity takes place for 5 minutes. This idle timeout is recommended to prevent
someone from using the web-based manager from a PC that is logged into the
web-based manager and then left unattended. However, you can use the
following steps to change this idle timeout.
To change the web-based manager idle timeout

1 Go to System > Admin > Settings.
2 Change the Idle Timeout minutes as required.
3 Select Apply.
Connecting to the FortiGate CLI from the web-based manager

You can connect to the FortiGate CLI from the web-based manager dashboard by
using the CLI console widget. You can use the CLI to configure all configuration
options available from the web-based manager. Some configuration options are
available only from the CLI. As well, you can use the CLI to enter diagnose
commands and perform other advanced operations that are not available from the
web-based manager. For more information about the FortiGate CLI see the
To connect to the FortiGate CLI from the web-based manager

1 Go to System > Status.
2 Locate and select the CLI Console.
Selecting the CLI console logs you into the CLI. For more information, see “CLI
Console” on page 76.

01-30007-0203-20090112 51
Button bar features Web-based manager
Button bar features

The button bar in the upper right corner of the web-based manager provides
access to several important FortiGate features.
Figure 4: Web-based manager button bar
Contact Customer
Support
Online Help
Logout
Back up your FortiGate
Configuration
Contacting Customer Support

The Contact Customer Support button opens the Fortinet Support web page in a
new browser window. From this page you can:
• visit the Fortinet Knowledge Center
• log into Customer Support (Support Login)
• register your Fortinet product (Product Registration)
• view Fortinet Product End of Life information
• find out about Fortinet Training and Certification
• visit the FortiGuard Center.
You must register your Fortinet product to receive product updates, technical
support, and FortiGuard services. To register a Fortinet product, go to Product
Registration and follow the instructions.
Backing up your FortiGate configuration

The Backup Configuration button opens a dialog box for backing up your
FortiGate configuration to:
• the local PC that you are using to manage the FortiGate unit.
• a management station. This can be a FortiManager unit or the FortiGuard
Management Service. This option changes depending on your central
management configuration (see “Central Management” on page 212).
• a USB disk if your FortiGate unit has a USB port and you have connected a
USB disk to it (see “USB Disks” on page 238).
For more information, see “Backup and Restore” on page 231.

52 01-30007-0203-20090112
Web-based manager Using FortiGate Online Help
Figure 5: Backing up your FortiGate configuration
Using FortiGate Online Help

The Online Help button displays context-sensitive online help for the current
web-based manager page. The online help page that is displayed is called a
content pane and contains information and procedures related to the current
web-based manager page. Most help pages also contain hyperlinks to related
topics. The online help system also includes a number of links that you can use to
find additional information.
FortiGate context-sensitive online help topics also include a VDOM or Global icon
to indicate whether the web-based manager page is for VDOM-specific or global
configuration settings. VDOM and Global configuration settings apply only to a
FortiGate unit operating with virtual domains enabled. If you are not operating
your FortiGate unit with virtual domains enabled, you can ignore the VDOM and
Global icons. For more information about virtual domains, see “Using virtual
domains” on page 95.
Figure 6: A context-sensitive online help page (content pane only)
Show Navigation Bookmark

Previous Print
Next Email
Show Open the online help navigation pane. From the navigation pane you can
Navigation use the online help table of contents, index, and search to access all of
the information in the online help. The online help is organized in the
same way as the FortiGate web-based manager and the FortiGate
Administration Guide.
Previous Display the previous page in the online help.
Next Display the next page in the online help.
Email Send an email to Fortinet Technical Documentation at
techdoc@fortinet.com if you have comments on or corrections for the
online help or any other Fortinet technical documentation product.
Print Print the current online help page.

01-30007-0203-20090112 53
Using FortiGate Online Help Web-based manager
Bookmark Add an entry for this online help page to your browser bookmarks or
favorites list to make it easier to find useful online help pages. You
cannot use the Bookmark icon to add an entry to your favorites list if you
are viewing online help from Internet Explorer running on a management
PC with Windows XP and service pack 2 installed.
When you select help for a VDOM configuration settings web-based
manager page the help display includes the VDOM icon. For information
about VDOM configuration settings, see “VDOM configuration settings”
on page 97.
When you select help for a Global configuration settings web-based
manager page the help display includes the Global icon. For information
about Global configuration settings, see “Global configuration settings”
on page 98.
To view the online help table of contents or index, and to use the search feature,
select Online Help in the button bar in the upper right corner of the web-based
manager. From the online help, select Show Navigation.
Figure 7: Online help page with navigation pane and content pane
Contents Index Search Show in Contents
Contents Display the online help table of contents. You can navigate through the
table of contents to find information in the online help. The online help is
organized in the same way as the FortiGate web-based manager and the
FortiGate Administration Guide.
Index Display the online help index. You can use the index to find information in
the online help.
Search Display the online help search. For more information, see “Searching the
online help” on page 54.
Show in If you have used the index, search, or hyperlinks to find information in the
Contents online help, the table of contents may not be visible or the table of
contents may be out of sync with the current help page. You can select
Show in Contents to display the location of the current help page within
the table of contents.
Searching the online help

Using the online help search, you can search for one word or multiple words in the
full text of the FortiGate online help system. Please note the following:
• If you search for multiple words, the search finds only those help pages that
contain all of the words that you entered. The search does not find help pages
that only contain one of the words that you entered.
• The help pages found by the search are ranked in order of relevance. The
higher the ranking, the more likely the help page includes useful or detailed
information about the word or words that you are searching for. Help pages
with the search words in the help page title are ranked highest.

54 01-30007-0203-20090112
Web-based manager Using FortiGate Online Help
• You can use the asterisk (*) as a search wildcard character that is replaced by
any number of characters. For example, if you search for auth* the search
finds help pages containing auth, authenticate, authentication,
authenticates, and so on.
• In some cases the search finds only exact matches. For example, if you
search for windows the search may not find pages containing the word
window. You can work around this using the * wildcard (for example by
searching for window*).
To search in the online help system

1 From any web-based manager page, select the online help button.
2 Select Show Navigation.
3 Select Search.
4 In the search field, enter one or more words to search for and then press the Enter
key on your keyboard or select Go.
The search results pane lists the names of all the online help pages that contain
all the words that you entered. Select a name from the list to display that help
page.
Figure 8: Searching the online help system
Go
Search
Field
Search
Results
Using the keyboard to navigate in the online help

You can use the keyboard shortcuts listed in Table 1 to display and find
information in the online help.
Table 1: Online help navigation keys

Key Function
Alt+1 Display the table of contents.
Alt+2 Display the index.
Alt+3 Display the Search tab.
Alt+4 Go to the previous page.
Alt+5 Go to the next page.
Alt+7 Send an email to Fortinet Technical Documentation at techdoc@fortinet.com if
you have comments on or corrections for the online help or any other Fortinet
technical documentation product.
Alt+8 Print the current online help page.
Alt+9 Add an entry for this online help page to your browser bookmarks or favorites list,
to make it easier to find useful online help pages.

01-30007-0203-20090112 55
Logging out Web-based manager
Logging out
The Logout button immediately logs you out of the web-based manager. Log out
before you close the browser window. If you simply close the browser or leave the
web-based manager, you remain logged in until the idle timeout (default 5
minutes) expires. To change the timeout, see “Changing the web-based manager
idle timeout” on page 51.
Web-based manager pages

The web-based manager interface consists of a menu and pages. Many of the
pages have multiple tabs. When you select a menu item, such as System, the
web-based manager expands to reveal a submenu. When you select one of the
submenu items, the associated page opens at its first tab. To view a different tab,
select the tab.
The procedures in this manual direct you to a page by specifying the menu item,
the submenu item and the tab, for example:
Figure 9: Parts of the web-based manager (shown for the FortiGate-50B)
Tabs Page
Button bar
Menu

56 01-30007-0203-20090112
Web-based manager Web-based manager pages
Using the web-based manager menu

The web-based manager menu provides access to configuration options for all
major FortiGate features.
System Configure system settings, such as network interfaces, virtual domains,

DHCP services, administrators. High Availability (HA), system time and
set system options.
Router Configure FortiGate static and dynamic routing and view the router
monitor.
Firewall Configure firewall policies and protection profiles that apply network
protection features. Also configure virtual IP addresses and IP pools.
VPN Configure IPSec, SSL, and PPTP virtual private networking.
User Configure user accounts for use with firewall policies that require user
authentication. Also configure external authentication servers such as
RADIUS, LDAP, TACACS+, and Windows AD.
AntiVirus Configure antivirus protection.
Intrusion Configure the FortiGate Intrusion Protection System (IPS).
Protection
Web Filter Configure web filtering.
AntiSpam Configure email spam filtering.
IM, P2P & VoIP Configure monitoring and control of internet messaging, peer-to-peer
messaging, and voice over IP (VoIP) traffic.
Log&Report Configure logging and alert email. View log messages and reports.
Using web-based manager lists

Many of the web-based manager pages contain lists. There are lists of network
interfaces, firewall policies, administrators, users, and others.
If you log in as an administrator with an access profile that allows Read-Write
access to a list, depending on the list you will usually be able to:
• select Create New to add a new item to the list
• select the Edit icon for a list item to view and change the settings of the item
• select the Delete icon for a list item to delete the item. The delete icon will not
be available if the item cannot be deleted. Usually items cannot be deleted if
they have been added to another configuration; you must first find the
configuration settings that the item has been added to and remove the item
from them. For example, to delete a user that has been added to a user group
you must first remove the user from the user group (see Figure 10).
Figure 10: A web-based manager list (read-write access)
Delete
Edit
If you log in as an administrator with an access profile that allows Read Only
access to a list, you will only be able to view the items on the list (see Figure 11).

01-30007-0203-20090112 57
Web-based manager pages Web-based manager
Figure 11: A web-based manager list (read only access)
View
For more information, see “Access profiles” on page 208.
Adding filters to web-based manager lists

You can add filters to control the information that is displayed by the following
complex lists:
• Session list (see “Viewing the session list” on page 85)
• Firewall policy and IPv6 policy list (see “Viewing the firewall policy list” on
page 295)
• IPSec VPN Monitor (see “Monitor” on page 409)
• Intrusion protection predefined signatures list (see “Viewing the predefined
signature list” on page 465)
• Log and report log access list (see “Accessing Logs” on page 539).
Filters are useful for reducing the number of entries that are displayed on a list so
that you can focus on the information that is important to you.
For example, you can go to System > Status, and, in the Statistics section, select
Details on the Sessions line to view the communications sessions that the
FortiGate unit is currently processing. A busy FortiGate unit may be processing
hundreds or thousands of communications sessions. You can add filters to make it
easier to find specific sessions. For example, you might be looking for all
communications sessions being accepted by a specific firewall policy. You can
add a Policy ID filter to display only the sessions for a particular Policy ID or range
of Policy IDs.
You add filters to a web-based manager list by selecting any filter icon to display
the Edit Filters window. From the Edit Filters window you can select any column
name to filter, and configure the filter for that column. You can also add filters for
one or more columns at a time. The filter icon remains gray for unfiltered columns
and changes to green for filtered columns.
Figure 12: An intrusion protection predefined signatures list filtered to display all
signatures containing “apache” with logging enabled, action set to drop,
and severity set to high
Filter added to
display names that
include “apache” No filter added
The filter configuration is retained after leaving the web-based manager page and
even after logging out of the web-based manager or rebooting the FortiGate unit.

58 01-30007-0203-20090112
Different filter styles are available depending on the type of information displayed
in individual columns. In all cases, you configure filters by specifying what to filter
on and whether to display information that matches the filter, or by selecting NOT
to display information that does not match the filter.
Note: Filter settings are stored in the FortiGate configuration and will be maintained the
next time that you access any list for which you have added filters.
On firewall policy, IPv6 policy, predefined signature and log and report log access
lists, you can combine filters with column settings to provide even more control of
the information displayed by the list. See “Using filters with column settings” on
page 63 for more information.
Filters for columns that contain numbers

If the column includes numbers (for example, IP addresses, firewall policy IDs, or
port numbers) you can filter by a single number or a range of numbers. For
example, you could configure a source address column to display only entries for
a single IP address or for all addresses in a range of addresses. To specify a
range, separate the top and bottom values of the range with a hyphen, for
example 25-50.
Figure 13 shows a numeric filter configured to control the source addresses that
are displayed on the session list. In this example, a filter is enabled for the Source
Address column. The filter is configured to display only source addresses in the
range of 1.1.1.1-1.1.1.2. To view the session list, go to System > Status. In the
Statistics section, beside Sessions, select Details.
Figure 13: A session list with a numeric filter set to display sessions with source IP
address in the range of 1.1.1.1-1.1.1.2
Filters for columns containing text strings

If the column includes text strings (for example, names and log messages) you
can filter by a text string. You can also filter information that is an exact match for
the text string (equals), that contains the text string, or that does not equal or does
not contain the text string. You can also specify whether to match the
capitalization (case) of the text string.

01-30007-0203-20090112 59
The text string can be blank and it can also be very long. The text string can also
contain special characters such as <, &, > and so on. However, filtering ignores
characters following a < unless the < is followed by a space (for example, filtering
ignores <string but not < string). Filtering also ignores matched opening and
closing < and > characters and any characters inside them (for example, filtering
ignores <string> but does not ignore >string>).
Figure 14: A firewall policy list filter set to display all policies that do not include a
source address with a name that contains “My_Address”
Filters for columns that can contain only specific items

For columns that can contain only specific items (for example, a log message
severity or a pre-defined signature action) you can select a single item from a list.
In this case, you can only filter on a single selected item.
Figure 15: An intrusion protection predefined signature list filter set to display all
signatures with Action set to block
Custom filters
Other custom filters are also available. You can filter log messages according to
date range and time range. You can also set the level filter to display log
messages with multiple severity levels.

60 01-30007-0203-20090112
Figure 16: A log access filter set to display all log messages with level of alert,
critical, error, or warning
Using page controls on web-based manager lists

The web-based manager includes page controls to make it easier to view lists that
contain more items than you can display on a typical browser window. These page
controls are available for the following lists:
• session list (see “Viewing the session list” on page 85)
• Router Monitor (see “Router Monitor” on page 289)
• IPSec VPN Monitor (see “Monitor” on page 409)
• intrusion protection predefined signatures list (see “Viewing the predefined
• web filtering lists (see “Web Filter” on page 479)
• antispam lists (see “Antispam” on page 499)
• log and report log access lists (see “Accessing Logs” on page 539).
Figure 17: Page controls
Previous Page Total Number of Pages

First Page
Last Page
Current Page Next Page

(enter a page number
to display that page)
First Page Display the first page of items in the list.

Previous Page Display the previous page of items in the list.
Current Page The current page number of list items that are displayed. You can enter
a page number and press Enter to display the items on that page. For
example if there are 5 pages of items and you enter 3, page 3 of the
sessions will be displayed.
Total Number of The number of pages of list items that you can view.
Pages

01-30007-0203-20090112 61
Next Page Display the next page of items in the list.

Last Page Display the last page of items in the list.
Using column settings to control the columns displayed

Using column settings, you can format some web-based manager lists so that
information that is important to you is easy to find and less important information is
hidden or less distracting.
On the following web-based manager pages that contain complex lists, you can
change column settings to control the information columns that are displayed for
the list and to control the order in which they are displayed.
• Network interface list (see “Interfaces” on page 107)
• Firewall policy and IPv6 policy (see “Viewing the firewall policy list” on
page 295)
• Intrusion protection predefined signatures list (see “Viewing the predefined
• Log and report log access lists (see “Accessing Logs” on page 539).
Note: Any changes that you make to the column settings of a list are stored in the FortiGate
configuration and will display the next time that you access the list.
To change column settings on a list that supports it, select Column Settings. From
“Available Fields”, select the column headings to be displayed and then select the
Right Arrow to move them to the “Show these fields in this order” list. Similarly, to
hide column headings, use the Left Arrow to move them back to the “Available
fields” list. Use Move up and Move down to change the order in which to display
the columns.
For example, you can change interface list column headings to display only the
IP/Netmask, MAC address, MTU, and interface Type for each interface.
Figure 18: Example of interface list column settings
Left Arrow Right Arrow

62 01-30007-0203-20090112
Figure 19: A FortiGate-5001SX interface list with column settings changed
Using filters with column settings

On firewall policy, IPv6 policy, predefined signature and log and report log access
lists you can combine filters with column settings to provide even more control of
the information displayed by the list.
For example, you can go to Intrusion Protection > Signature > Predefined and
configure the Intrusion Protection predefined signatures list to show only the
names of signatures that protect against vulnerabilities for a selected application.
To do this, set Column Settings to only display Applications and Name. Then
apply a filter to Applications so that only selected applications are listed. In the
pre-defined signatures list you can also sort the list by different columns; you
might want to sort the list by application so that all signatures for each application
are grouped together.
Figure 20: A pre-defined signatures list displaying pre-defined signatures for the
Veritas and Winamp applications
For more information, see “Adding filters to web-based manager lists” on page 58.

01-30007-0203-20090112 63
Using web-based manager icons

The web-based manager has icons in addition to buttons to help you to interact
with your FortiGate unit. There are tooltips to assist you in understanding the
function of most icons. Pause the mouse pointer over the icon to view the tooltip.
Table 2 describes the icons that are available in the web-based manager.
Table 2: web-based manager icons
Icon Name Description
Administrative The administrative status of a FortiGate interface is down

status down and the interface will not accept traffic.
Administrative The administrative status of a FortiGate interface is up and
status up the interface accepts traffic.
Change Change the administrator password. This icon appears in the
Password Administrators list if your access profile enables you to give
write permission to administrators.
Clear Clear all or remove all entries from the current list. For
example, on a URL filter list you can use this icon to remove
all URLs from the current URL filter list.
Delete Delete an item. This icon appears in lists where the item can
be deleted and you have edit permission for the item.
Description The tooltip for this icon displays the Description or
Comments field for this table entry.
Disconnect Disconnect a FortiGate unit from a functioning HA cluster.
from cluster
Download Download information from a FortiGate unit. For example,

you can download certificates and debug logs.
Edit Edit a configuration. This icon appears in lists where you

have write permission for the item.
Enter a VDOM Enter a virtual domain and use the web-based manager to
configure settings for the virtual domain.
Expand Arrow Expand this section to reveal more fields. This icon is used in
(closed) some dialog boxes and lists.
Expand Arrow Close this section to hide some fields. This icon is used in
(open) some dialog boxes and lists.
Filter Set a filter on one or more columns in this table. See “Adding
filters to web-based manager lists” on page 58.
First page View the first page of a list.
Insert before Add a new item to a list so that it precedes the current item.
Used in lists when the order of items in the list is significant,
for example firewall policies, IPS Sensors, and DoS Sensors.
Last page View the last page of a list.
Move to Change the position of an item in a list. Used in lists when the
order of items in the list is significant, for example firewall
policies, IPS Sensors, and DoS Sensors.
Next page View the next page of a list.

64 01-30007-0203-20090112
Table 2: web-based manager icons (Continued)
Icon Name Description
Previous page View the previous page of a list.
Refresh Update the information on this page.
View View a configuration. This icon appears in lists instead of the

Edit icon when you have read-only access to a web-based
manager list.
View details View detailed information about an item. For example, you
can use this icon to view details about certificates.

01-30007-0203-20090112 65

66 01-30007-0203-20090112
System Status Status page
System Status
This section describes the System Status page, the dashboard of your FortiGate
unit. At a glance you can view the current system status of the FortiGate unit
including serial number, uptime, FortiGuard™ license information, system
resource usage, alert messages and network statistics.
Note: Your browser must support Javascript to view the System Status page.
If you enable virtual domains (VDOMs) on the FortiGate unit, the status page is
available globally and system status settings are configured globally for the entire
FortiGate unit. The Topology viewer is not available when VDOMs are enabled.
For details, see “Using virtual domains” on page 95.
• Status page
• Changing system information
• Changing the FortiGate firmware
• Viewing operational history
• Manually updating FortiGuard definitions
• Viewing Statistics
• Topology
Status page
View the System Status page, also known as the system dashboard, for a
snapshot of the current operating status of the FortiGate unit. FortiGate
administrators whose access profiles permit read access to System Configuration
can view system status information.
When the FortiGate unit is part of an HA cluster, the System Status page includes
basic high availability (HA) cluster status such as including the name of the cluster
and the cluster members including their host names. To view more complete
status information for the cluster, go to System > Config > HA. For more
information, see “HA” on page 167. HA is not available on FortiGate 50A, and
50AM models.
FortiGate administrators whose access profiles permit write access to system
configuration can change or update FortiGate unit information. For information on
access profiles, see “Access profiles” on page 208.
Viewing system status

The System Status page displays by default when you log in to the web-based
manager.
Go to System > Status to view the System Status page.

01-30007-0203-20090112 67
Status page System Status
To view this page, your access profile must permit read access to system
configuration. If you also have system configuration write access, you can modify
system information and update FortiGuard - AV and FortiGuard - IPS definitions.
For information on access profiles, see “Access profiles” on page 208.
The System Status page is customizable. You can select which widgets to display,
where they are located on the page, and if they are minimized or maximized. Each
display has an icon associated with it for easy recognition when minimized.
Figure 21: System Status page
Select Add Content to add any of the widgets not currently shown on the System
Status page. Any widgets currently on the System Status page will be greyed out
in the Add Content menu, as you can only have one of each display on the
System Status page. Optionally select Back to Default to restore the historic
System Status page configuration.
Position your mouse over a display’s titlebar to see your available options for that
display. The options vary slightly from display to display.
Figure 22: A minimized display
History
Widget title Edit
Disclosure arrow Refresh
Close
Widget Title Shows the name of the display

Disclosure arrow Select to maximize or minimize the display.

68 01-30007-0203-20090112
History Select to show an expanded set of data.

Not available for all widgets.
Edit Select to change settings for the display.
Refresh Select to update the displayed information.
Close Select to close the display. You will be prompted to confirm the
action.
The available dashboard widgets are:
• System Information
• License Information
• Unit Operation
• System Resources
• Alert Message Console
• Statistics
• CLI Console
• Top Sessions
• Top Viruses
• Top Attacks
• Traffic History
System Information
Go to System > Status to find System Information.
Figure 23: System Information
Serial Number The serial number of the FortiGate unit. The serial number is specific
to the FortiGate unit and does not change with firmware upgrades.
Uptime The time in days, hours, and minutes since the FortiGate unit was
started.
System Time The current date and time according to the FortiGate unit’s internal
clock.
Select Change to change the time or configure the FortiGate unit to
get the time from an NTP server. See “Configuring system time” on
page 80.
HA Status The status of high availability for this unit.
Standalone indicates the unit is not operating in HA mode.
Active-Passive or Active-Active indicate the unit is operating in HA
mode.
Select Configure to configure the HA status for this unit. See “HA” on
page 167.

01-30007-0203-20090112 69
Host Name The host name of the current FortiGate unit.

Select Change to change the host name.
See “Changing the FortiGate unit host name” on page 80.
If the FortiGate unit is in HA mode, this field is not displayed.
Cluster Name The name of the HA cluster for this FortiGate unit. See “HA” on
page 167.
The FortiGate unit must be operating in HA mode to display this field.
Cluster Members The FortiGate units in the HA cluster. Information displayed about
each member includes host name, serial number, and whether the
unit is a primary (master) or subordinate (slave) unit in the cluster.
See “HA” on page 167.
The FortiGate unit must be operating in HA mode with virtual
domains disabled to display this field.
Virtual Cluster 1 The role of each FortiGate unit in virtual cluster 1 and virtual cluster 2.
Virtual Cluster 2 See “HA” on page 167.
The FortiGate unit must be operating in HA mode with virtual
domains enabled to display these fields.
Firmware Version The version of the current firmware installed on the FortiGate unit.
Select Update to change the firmware.
See “Upgrading to a new firmware version” on page 82.
FortiClient Version The currently stored version of FortiClient. Select Update to upload a
FortiClient software image to this FortiGate unit from your
management computer.
This option is available only on FortiGate models that provide a portal
from which hosts can download FortiClient software, such as
FortiGate-3600 and 5005 models.
Operation Mode The operating mode of the current FortiGate unit. A FortiGate unit
can operate in NAT mode or Transparent mode. Select Change to
switch between NAT and Transparent mode. See “Changing
operation mode” on page 193
If virtual domains are enabled, this field shows the operating mode of
the current virtual domain. Each virtual domain can be operating in
either NAT mode or Transparent mode.
Virtual Domain Status of virtual domains on your FortiGate unit. Select enable or
disable to change the status of virtual domains feature.
If you enable or disable virtual domains, your session will be
terminated and you will need to log in again. For more information,
see “Using virtual domains” on page 95.
Current The number of administrators currently logged into the FortiGate unit.
Administrators Select Details to view more information about each administrator that
is currently logged in. The additional information includes user name,
type of connection, IP address from which they are connecting, and
when they logged in.
License Information
License Information displays the status of your technical support contract and
FortiGuard subscriptions. The FortiGate unit updates the license information
status indicators automatically when attempting to connect to the FortiGuard
Distribution Network (FDN). FortiGuard Subscriptions status indicators are green
if the FDN was reachable and the license was valid during the last connection
attempt, grey if the FortiGate unit cannot connect to the FDN, and orange if the
FDN is reachable but the license has expired.
Selecting any of the Configure options will take you to the Maintenance page. For
more information, see “System Maintenance” on page 229.

70 01-30007-0203-20090112
Figure 24: License Information
Support Contract The Fortinet technical support contract number and expiry
date, or registration status.
If Not Registered appears, select Register to register the
unit.
If Expired appears, select Renew for information on
renewing your technical support contract. Contact your local
reseller.
FortiGuard Subscriptions
AntiVirus The FortiGuard Antivirus version, license issue date and
service status. If your license has expired, you can select
Renew two renew the license.
AV Definitions The currently installed version of the FortiGuard Antivirus
definitions. To update the definitions manually, select
Update. For more information, see “To update FortiGuard AV
Definitions manually” on page 84.
Intrusion Protection The FortiGuard Intrusion Prevention System (IPS) license
version, license issue date and service status. If your license
has expired, you can select Renew two renew the license.
IPS Definitions The currently installed version of the IPS attack definitions.
To update the definitions manually, select Update. For more
information, see “To update FortiGuard IPS Definitions
manually” on page 85.
Web Filtering The FortiGuard Web Filtering license, license expiry date
and service status. If your license has expired, you can
select Renew two renew the license.
Antispam The FortiGuard Antispam license type, license expiry date
and service status. If your license has expired, you can
select Renew two renew the license.
Analysis & The FortiGuard Analysis Service and Management Service
Management license, license expiry date and reachability status.
Services
Services Account ID Select “change“ to enter a different Service Account ID. This
ID is used to validate your license for subscription services
such as FortiGuard Management Service and FortiGuard
Analysis Service.
Virtual Domain
VDOMs Allowed The maximum number of virtual domains the unit supports
with the current license.
For FortiGate 3000 models or higher, you can select the
Purchase More link to purchase a license key through
Fortinet technical support to increase the maximum number
of VDOMs. See “License” on page 254.

01-30007-0203-20090112 71
Unit Operation
In the Unit Operation area, an illustration of the FortiGate unit’s front panel shows
the status of the unit’s Ethernet network interfaces. If a network interface is green,
that interface is connected. Pause the mouse pointer over the interface to view the
name, IP address, netmask and current up/down status of the interface.
If you select Reboot or ShutDown, a pop-up window opens allowing you to enter
the reason for the system event.
You can only have one management and one logging/analyzing method displayed
for your FortiGate unit. The graphic for each will change based on which method
you choose. If none are selected, no graphic is shown.
Note: Your reason will be added to the Disk Event Log if disk logging, event logging, and
admin events are enabled. For more information on Event Logging, see “Event log” on
page 536.
Figure 25: Unit Operation (FortiGate-800)
Figure 26: Unit Operation (FortiGate 60)
Figure 27: Unit Operation (FortiGate 3810A)

72 01-30007-0203-20090112
INT / EXT / DMZ / HA / The network interfaces on the FortiGate unit. The names and
1/2/3/4 number of these interfaces vary by model.
The icon below the interface name indicates its up/down status by
color. Green indicates the interface is connected. Grey indicates
there is no connection.
For more information about the configuration and status of an
interface, pause the mouse over the icon for that interface. A
tooltip displays the full name of the interface, its alias if one is
configured, the IP address and netmask, the status of the link, the
speed of the interface, and the number of sent and received
packets.
AMC-SW1/1, ... If your FortiGate unit supports Advanced Mezzanine Card (AMC)
AMC-DW1/1, ... modules and if you have installed an AMC module containing
network interfaces (for example, the FortiGate-ASM-FB4 contains
4 interfaces) these interfaces are added to the interface status
display. The interfaces are named for the module, and the
interface. For example AMC-SW1/3 is the third network interface
on the SW1 module, and AMC-DW2/1 is the first network interface
on the DW2 module.
AMC modules support hard disks as well, such as the ASM-S08
module. When a hard disk is installed, ASM-S08 is visible as well
as a horizontal bar and percentage indicating how full the hard
disk is.
FortiAnalyzer The icon on the link between the FortiGate unit graphic and the
FortiAnalyzer graphic indicates the status of their OFTP
connection. An ‘X’ on a red icon indicates there is no connection.
A check mark on a green icon indicates there is OFTP
communication.
Select the FortiAnalyzer graphic to configure remote logging tot he
FortiAnalyzer unit on your FortiGate unit. See “Logging to a
FortiAnalyzer unit” on page 529.
FortiGuard Analysis The icon on the link between the FortiGate unit graphic and the
Service FortiGuard Analysis Service graphic indicates the status of their
OFTP connection. An ‘X’ on a red icon indicates there is no
connection. A check mark on a green icon indicates there is OFTP
communication.
Select the FortiGuard Analysis Service graphic to configure
remote logging to the FortiGuard Analysis Service. See
“FortiGuard Analysis and Management Service” on page 526.
FortiManager The icon on the link between the FortiGate unit graphic and the
FortiManager graphic indicates the status of the connection. An ‘X’
on a red icon indicates there is no connection. A check mark on a
green icon indicates there is communication between the two
units.
Select the FortiManager graphic to configure central management
on your FortiGate unit. See “Central Management” on page 212.
FortiGuard The icon on the link between the FortiGate unit graphic and the
Management Service FortiGuard Management Service graphic indicates the status of
the connection. An ‘X’ on a red icon indicates there is no
connection. A check mark on a green icon indicates there is
communication.
Select the FortiGuard Management Service graphic to configure
central management on your FortiGate unit. See “Central
Management” on page 212.
Reboot Select to shutdown and restart the FortiGate unit. You will be
prompted to enter a reason for the reboot that will be entered into
the logs.
Shutdown Select to shutdown the FortiGate unit. You will be prompted for
confirmation, and also prompted to enter a reason for the
shutdown that will be entered into the logs.
Reset Select to reset the FortiGate unit to factory default settings. You
will be prompted for confirmation.

01-30007-0203-20090112 73
System Resources
The System Resources widget displays basic FortiGate unit resource usage, such
as CPU and memory (RAM) usage. Any System Resources that are not displayed
on the status page can be viewed as a graph by selecting the History icon.
Figure 28: System Resources
History A graphical representation of the last minute of CPU, memory,

sessions, and network usage. This page also shows the virus and
intrusion detections over the last 20 hours. For more information,
see “Viewing operational history” on page 84.
CPU Usage The current CPU status displayed as a dial gauge and as a
percentage.
The web-based manager displays CPU usage for core processes
only. CPU usage for management processes (for example, for
HTTPS connections to the web-based manager) is excluded.
Memory Usage The current memory (RAM) status displayed as a dial gauge and as
a percentage.
The web-based manager displays memory usage for core
processes only. Memory usage for management processes (for
example, for HTTPS connections to the web-based manager) is
excluded.
FortiAnalyzer Usage The current status of the FortiAnalyzer disk space used by this
FortiGate unit’s quota, displayed as a pie chart and a percentage.
This is available only if you have configured logging to a
FortiAnalyzer unit.
Alert Message Console

Alert messages help you track system events on your FortiGate unit such as
firmware changes, network security events, or virus detection events.
Each message shows the date and time that the event occurred.
Figure 29: Alert Message Console
The following types of messages can appear in the Alert Message Console:
System restart The system restarted. The restart could be due to

operator action or power off/on cycling.
Firmware upgraded by The named administrator upgraded the firmware to a
<admin_name> more recent version on either the active or non-active
partition.

74 01-30007-0203-20090112
Firmware downgraded by The named administrator downgraded the firmware to

<admin_name> an older version on either the active or non-active
partition.
FortiGate has reached The antivirus engine was low on memory for the
connection limit for <n> seconds duration of time shown. Depending on model and
configuration, content can be blocked or pass
unscanned under these conditions.
Found a new FortiAnalyzer Shows that the FortiGate unit has either found or lost
Lost the connection to the connection to a FortiAnalyzer unit. See “Logging
FortiAnalyzer to a FortiAnalyzer unit” on page 529.
New firmware is available from An updated firmware image is available to be
FortiGuard downloaded to this FortiGate unit.
If there is insufficient space for all of the messages within the Alert Message
Console widget, select History to view the entire list in a new window.
To clear alert messages, select the History icon and then select Clear Alert
Messages, which is located at the top of the pop-up window. This will
acknowledge and hide all current alert messages from your FortiGate unit.
Selecting Edit brings up Custom Alert Display options that offers the
customizations for your alert message display:
• Do not display system shutdown and restart.
• Do not display firmware upgrade and downgrade.
• Do not display conserve mode messages
Statistics
The Statistics widget is designed to allow you to see at a glance what is
happening on your FortiGate unit with regards to network traffic and attack
attempts.
You can quickly see the amount and type of traffic as well as any attack attempts
on your system. To investigate an area that draws your attention, select Details for
a detailed list of the most recent activity.
The information displayed in the statistics widget is derived from log messages
that can be saved to a FortiAnalyzer unit, saved locally, or backed up to an
external source such as a syslog server. You can use this data to see trends in
network activity or attacks over time.
Note: The Email statistics are based on email protocols. POP3 traffic is registered as
incoming email, and SMTP is outgoing email. If incoming or outgoing email does not use
these protocols, these statistics will not be accurate.
For detailed procedures involving the Statistics list, see “Viewing Statistics” on
page 85.

01-30007-0203-20090112 75
Figure 30: Statistics
Reset
Since The date and time when the counts were last reset.
Counts are reset when the FortiGate unit reboots, or when you
select Reset.
Reset Reset the Content Archive and Attack Log statistic counts to zero.
Sessions The number of communications sessions being handled by the
FortiGate unit. Select Details for detailed information. See “Viewing
the session list” on page 85.
Content Archive A summary of the HTTP, HTTPS, e-mail, VoIP, and IM/P2P traffic
that has passed through the FortiGate unit, and whose metadata
and/or files or traffic have been content archived.
The Details pages list the last 64 items of the selected type and
provide links to the FortiAnalyzer unit where the archived traffic is
stored. If logging to a FortiAnalyzer unit is not configured, the
Details pages provide a link to Log & Report > Log Config >
Log Settings.
Attack Log A summary of viruses, attacks, spam email messages and blocked
URLs that the FortiGate unit has intercepted. The Details pages list
the most recent 10 items, providing the time, source, destination
and other information.
CLI Console
The System Status page can include a CLI. To use the console, select it to
automatically log in to the admin account you are currently using in the web-based
manager. You can copy (CTRL-C) and paste (CTRL-V) text from or to the CLI
Console.
Figure 31: CLI Console
Customize
The two controls located on the CLI Console widget’s title bar are Customize, and
Detach.

76 01-30007-0203-20090112
Detach moves the CLI Console widget into a pop-up window that you can resize
and reposition. The two controls on the detached CLI Console are Customize and
Attach. Attach moves the CLI console widget back onto the System Status page.
Customize allows you to change the appearance of the console by defining fonts
and colors for the text and background.
Figure 32: Customize CLI Console window
Preview A preview of your changes to the CLI Console’s appearance.

Text Select the current color swatch next to this label, then select a
color from the color palette to the right to change the color of the
text in the CLI Console.
Background Select the current color swatch next to this label, then select a
color from the color palette to the right to change the color of the
background in the CLI Console.
Use external Select to display a command input field below the normal console
command input box emulation area. When this option is enabled, you can enter
commands by typing them into either the console emulation area
or the external command input field.
Console buffer length Enter the number of lines the console buffer keeps in memory.
Valid numbers range from 20 to 9999.
Font Select a font from the list to change the display font of the CLI
Console.
Size Select the size of the font. The default size is 10 points.
Top Sessions
Top Sessions displays a bar graph representing the IP addresses that have the
most sessions open of the FortiGate unit. The sessions are sorted by either their
source or destination IP address. The sort criteria being used is displayed in the
top right corner.

01-30007-0203-20090112 77
The Top Sessions display polls the kernel for session information, and this slightly
impacts the FortiGate unit performance. For this reason when this display is not
shown on the dashboard, it is not collecting data, and not impacting system
performance. When the display is shown, information is only stored in memory
and a reboot will reset the statistics to zero.
The Top Sessions display is not part of the default dashboard display. It can be
displayed by selecting Add Content, and selecting Top Sessions from the drop
down menu.
Selecting edit for Top Sessions allows changes to the:
• refresh interval
• sort criteria to change between source and destination addresses of the
sessions
• number of top sessions to show
Figure 33: Top sessions
Sort Criteria
Number of
active
sessions
Destination
IP address
of sessions
Top Viruses
Top Viruses displays a bar graph representing the virus threats that have been
detected most frequently by the FortiGate unit.
The Top Viruses display is not part of the default dashboard display. It can be
displayed by selecting Add Content, and selecting Top Viruses from the drop
down menu.
Selecting the history icon opens a window that displays up to the 20 most recent
viruses that have been detected with information including the virus name, when it
was last detected, and how many times it was detected. The system stores up to
1024 entries, but only displays up to 20 in the GUI.
Selecting the edit icon for Top Viruses allows changes to the:
• top viruses to show
Top Attacks
Top Attacks displays a bar graph representing the most numerous attacks
detected by the FortiGate unit.

78 01-30007-0203-20090112
The Top Attacks display is not part of the default dashboard display. It can be
displayed by selecting Add Content > Top Attacks from the drop down menu.
Selecting the history icon opens a window that displays up to the 20 most recent
attacks that have been detected with information including the attack name, when
it was last detected, and how many times it was detected. The FortiGate unit
stores up to 1024 entries, but only displays up to 20 in the web-based manager.
Selecting the Edit icon for Top Attacks allows changes to the:
• top attacks to show
Traffic History
The traffic history display shows the traffic on one selected interface over the last
hour, day, and month. This feature can help you locate peaks in traffic that you
need to address as well as their frequency, duration, and other information.
Only one interface at a time can be monitored. You can change the interface
being monitored by selecting Edit, choosing the interface from the drop down
menu, and selecting Apply. Doing this will clear all the traffic history data.
Figure 34: Traffic History
Interface being
monitored
Interface The interface that is being monitored .

kbit/s The units of the traffic graph. The scale varies based on traffic
levels to allow it to show traffic levels no matter how little or how
much traffic there is.
Last 60 Minutes Three graphs showing the traffic monitored on this interface of the
Last 24 Hours FortiGate unit over different periods of time.
Last 30 Days Certain trends may be easier to spot in one graph over the others.
Traffic In The traffic entering the FortiGate unit on this interface is indicated
with a thin red line.
Traffic Out The traffic leaving the FortiGate unit on this interface is indicated
with a dark green line, filled in with light green.

01-30007-0203-20090112 79
Changing system information System Status
Changing system information

FortiGate administrators whose access profiles permit write access to system
configuration can change the system time, host name and the operation mode for
the VDOM.
Configuring system time

2 In the System Information section, select Change on the System Time line.
3 Select the time zone and then either set the date and time manually or configure
synchronization with an NTP server.
Figure 35: Time Settings
System Time The current FortiGate system date and time.

Refresh Update the display of the current FortiGate system date and time.
Time Zone Select the current FortiGate system time zone.
Automatically adjust Select to automatically adjust the FortiGate system clock when your
clock for daylight time zone changes between daylight saving time and standard
saving changes time.
Set Time Select to set the FortiGate system date and time to the values you
set in the Hour, Minute, Second, Year, Month and Day fields.
Synchronize with Select to use an NTP server to automatically set the system date
NTP Server and time. You must specify the server and synchronization interval.
Server Enter the IP address or domain name of an NTP server. To find an
NTP server that you can use, see http://www.ntp.org.
Sync Interval Specify how often the FortiGate unit should synchronize its time
with the NTP server. For example, a setting of 1440 minutes causes
the FortiGate unit to synchronize its time once a day.
Changing the FortiGate unit host name

The FortiGate host name appears on the Status page and in the FortiGate CLI
prompt. The host name is also used as the SNMP system name. For information
about SNMP, see “SNMP” on page 176.
The default host name is the FortiGate unit serial number. For example
FGT8002805030003 would be a FortiGate-800 unit.
Administrators whose access profiles permit system configuration write access
can change the FortiGate unit host name.

80 01-30007-0203-20090112
System Status Changing the FortiGate firmware
To change the FortiGate unit host name
Note: If the FortiGate unit is part of an HA cluster, you should use a unique host name to
distinguish the unit from others in the cluster.
If the host name is longer than 16 characters, it will be displayed as being

truncated and end with a “~”. The full host name will be displayed under System >
Status, but the truncated host name will be displayed on the CLI and other places
it is used.
2 In the Host Name field of the System Information section, select Change.
3 In the New Name field, type a new host name.
4 Select OK.
The new host name is displayed in the Host Name field, and in the CLI prompt,
and is added to the SNMP System Name.
Changing the FortiGate firmware

FortiGate administrators whose access profiles permit maintenance read and
write access can change the FortiGate firmware. Firmware images can be
transferred from a number of sources including a local hard disk, a local USB disk,
or the FortiGuard Network.
Note: To access firmware updates for your FortiGate model, you will need to register your
FortiGate unit with Customer Support. For more information go to
http://support.fortinet.com or contact Customer Support.
For more information about using the USB disk, and the FortiGuard Network see
“System Maintenance” on page 229.
Figure 36: Firmware Upgrade/Downgrade
Upgrade From Select the firmware source from the drop down list of available
sources.
Possible sources include Local Hard Disk, USB, and FortiGuard
Network.
Upgrade File Browse to the location of the firmware image on your local hard
disk.
This field is available for local hard disk and USB only.

01-30007-0203-20090112 81
Changing the FortiGate firmware System Status
Upgrade Partition The number of the partition being updated.

This field is available only if your FortiGate unit has more than one
firmware partition.
more info Select to go to the FortiGuard Center to learn more about firmware
updates through the FortiGuard network.
Firmware changes either upgrade to a newer version or revert to an earlier
version. Follow the appropriate procedure to change your firmware.
For more information about managing firmware, see “Managing firmware
versions” on page 555.
• Upgrading to a new firmware version
• Reverting to a previous firmware version
Upgrading to a new firmware version

Use the following procedure to upgrade the FortiGate unit to a newer firmware
version.
Note: Installing firmware replaces the current antivirus and attack definitions with the
definitions included with the firmware release that you are installing. After you install new
firmware, use the procedure “To update antivirus and attack definitions” on page 249 to
make sure that antivirus and attack definitions are up to date.
To upgrade the firmware using the web-based manager

1 Copy the firmware image file to your management computer.
The firmware images for FortiGate units are available at the Fortinet Technical
Support web site. Log in to the site and go to Firmware Images > FortiGate.
2 Log into the web-based manager as the super admin, or an administrator account
that has system configuration read and write privileges.
4 In the System Information section, select Update on the Firmware Version line.
5 Type the path and filename of the firmware image file, or select Browse and locate
the file.
6 Select OK.
The FortiGate unit uploads the firmware image file, upgrades to the new firmware
version, closes all sessions, restarts, and displays the FortiGate login. This
process takes a few minutes.
7 Log into the web-based manager.
8 Go to System > Status and check the Firmware Version to confirm that the
firmware upgrade is successfully installed.
9 Update antivirus and attack definitions. For information about updating antivirus
and attack definitions, see “FortiGuard” on page 241.

82 01-30007-0203-20090112
System Status Changing the FortiGate firmware
Reverting to a previous firmware version

Use the following procedure to revert your FortiGate unit to a previous firmware
version. This also reverts the FortiGate unit to its factory default configuration and
deletes IPS custom signatures, web content lists, email filtering lists, and changes
to replacement messages. Back up your FortiGate unit configuration to preserve
this information. For information, see “Maintenance System Configuration” on
page 229.
If you are reverting to a previous FortiOS™ version (for example, reverting from
FortiOS v3.0 to FortiOS v2.8), you might not be able to restore the previous
configuration from the backup configuration file.
Note: Installing firmware replaces the current antivirus and attack definitions with the
definitions included with the firmware release that you are installing. After you install new
firmware, use the procedure “To update antivirus and attack definitions” on page 249 to
make sure that antivirus and attack definitions are up to date.
To revert to a previous firmware version using the web-based manager

The firmware images for FortiGate units are available at the Fortinet Technical
Support web site. Log in to the site and go to Firmware Images > FortiGate.
2 Log into the web-based manager as the super admin, or an administrator account
that has system configuration read and write privileges.
4 In the System Information section, select Update on the Firmware Version line.
5 Type the path and filename of the firmware image file, or select Browse and locate
the file.
6 Select OK.
The FortiGate unit uploads the firmware image file, reverts to the old firmware
version, resets the configuration, restarts, and displays the FortiGate login. This
8 Go to System > Status and check the Firmware Version to confirm that the
firmware is successfully installed.
9 Restore your configuration.
For information about restoring your configuration, see “Maintenance System
Configuration” on page 229.
10 Update antivirus and attack definitions.
For information about antivirus and attack definitions, see “To update antivirus and
attack definitions” on page 249.

01-30007-0203-20090112 83
Viewing operational history System Status
Viewing operational history

The System Resource History page displays six graphs representing system
resources and protection activity over time.
2 Select History in the upper right corner of the System Resources section.
Figure 37: Sample system resources history
Time Interval Select the time interval that the graphs show.
CPU Usage History CPU usage for the preceding interval.
Memory Usage History Memory usage for the preceding interval.
Session History Number of sessions over the preceding interval.
Network Utilization History Network utilization for the preceding interval.
Virus History Number of Viruses detected over the preceding interval.
Intrusion History Number of intrusion attempts detected over the preceding
interval.
Manually updating FortiGuard definitions

You can update your FortiGuard - AV and FortiGuard - Intrusion Protection
definitions at any time from the License Information section of the System Status
page.
Note: For information about configuring the FortiGate unit for automatic AV and automatic
IPS (attack) definitions updates, see “FortiGuard” on page 241.
To update FortiGuard AV Definitions manually

1 Download the latest AV definitions update file from Fortinet and copy it to the
computer that you use to connect to the web-based manager.
2 Start the web-based manager and go to System > Status.

84 01-30007-0203-20090112
System Status Viewing Statistics
3 In the License Information section, in the AV Definitions field of the FortiGuard

Subscriptions, select Update.
The Anti-Virus Definitions Update dialog box appears.
4 In the Update File field, type the path and filename for the AV definitions update
file, or select Browse and locate the AV definitions update file.
5 Select OK to copy the AV definitions update file to the FortiGate unit.
The FortiGate unit updates the AV definitions. This takes about 1 minute.
6 Go to System > Status to confirm that the FortiGuard - AV Definitions version
information has updated.
To update FortiGuard IPS Definitions manually

1 Download the latest attack definitions update file from Fortinet and copy it to the
computer that you use to connect to the web-based manager.
2 Start the web-based manager and go to System > Status.
3 In the License Information section, in the IPS Definitions field of the FortiGuard
Subscriptions, select Update.
The Intrusion Prevention System Definitions Update dialog box appears.
4 In the Update File field, type the path and filename for the attack definitions
update file, or select Browse and locate the attack definitions update file.
5 Select OK to copy the attack definitions update file to the FortiGate unit.
The FortiGate unit updates the attack definitions. This takes about 1 minute.
6 Go to System > Status to confirm that the IPS Definitions version information has
updated.
Viewing Statistics
The System Status Statistics provide information about sessions, content
archiving and network protection activity.
Viewing the session list

From the Statistics section of the System Status page, you can view statistics
about HTTP, HTTPS, email, FTP and IM traffic through the FortiGate unit. You can
select the Details link beside each traffic type to view more information.
To view the session list

2 In the Statistics section, select Details on the Sessions line.

01-30007-0203-20090112 85
Viewing Statistics System Status
Figure 38: Session list
Virtual Domain Select a virtual domain to list the sessions being processed by that
virtual domain. Select All to view sessions being processed by all virtual
domains.
This is only available if virtual domains are enabled. For more
information see “Using virtual domains” on page 95.
Refresh Icon Update the session list.
First Page Select to go to the first displayed page of current sessions.
Previous Page Select to go to the page of sessions immediately before the current page
Page Enter the page number of the session to start the displayed session list.
For example if there are 5 pages of sessions and you enter 3, page 3 of
the sessions will be displayed.
The number following the ‘/’ is the number of pages of sessions.
Next Page Select to go to the next page of sessions.
Last Page Select to go to the last displayed page of current sessions.
Total The total number sessions.
Clear All Filters Select to reset any display filters that may have been set.
Filter Icon The icon at the top of all columns except #, and Expiry. When selected it
brings up the Edit Filter dialog allowing you to set the display filters by
column. See “Adding filters to web-based manager lists” on page 58.
Protocol The service protocol of the connection, for example, udp, tcp, or icmp.
Source Address The source IP address of the connection.
Source Port The source port of the connection.
Destination The destination IP address of the connection.
Address
Destination Port The destination port of the connection.
Policy ID The number of the firewall policy allowing this session or blank if the
session involves only one FortiGate interface (admin session, for
example).
Expiry (sec) The time, in seconds, before the connection expires.
Delete icon Stop an active communication session. Your access profile must include
read and write access to System Configuration.

86 01-30007-0203-20090112
Viewing the Content Archive information

about HTTP, email, FTP and IM traffic through the FortiGate unit. You can select
the Details link beside each traffic type to view more information.
You can select Reset on the header of the Statistics section to clear the content
archive and attack log information and reset the counts to zero.
Viewing archived HTTP content information

2 In the Content Archive section, select Details for HTTP.
Date and Time The time when the URL was accessed.
From The IP address from which the URL was accessed.
URL The URL that was accessed.
Viewing archived Email content information

2 In the Content Archive section, select Details for Email.
Date and Time The time that the email passed through the FortiGate unit.
From The sender’s email address.
To The recipient’s email address.
Subject The subject line of the email.

01-30007-0203-20090112 87
Viewing Statistics System Status
Viewing archived FTP content information

2 In the Content Archive section, select Details for FTP.
Date and Time The time of access.

Destination The IP address of the FTP server that was accessed.
User The User ID that logged into the FTP server.
Downloads The names of files that were downloaded.
Uploads The names of files that were uploaded.
Viewing archived IM content information

2 In the Content Archive section, select Details for IM.
Date / Time The time of access.

Protocol The protocol used in this IM session.
Kind The kind of IM traffic this transaction is.
Local The local address for this transaction.
Remote The remote address for this transaction
Direction If the file was sent or received.
Viewing the Attack Log

about the network attacks that the FortiGate unit has stopped. You can select the
Details link beside each attack type to view more information.
You can select Reset on the header of the Statistics section to clear the content
archive and attack log information and reset the counts to zero.
Viewing viruses caught

2 In the Attack Log section, select Details for AV.
Date and Time The time when the virus was detected.
From The sender’s email address or IP address.

88 01-30007-0203-20090112
To The intended recipient’s email address or IP address.

Service The service type, such as POP or HTTP.
Virus The name of the virus that was detected.
Viewing attacks blocked

2 In the Attack Log section, select Details for IPS.
Date and Time The time that the attack was detected.
From The source of the attack.
To The target host of the attack.
Service The service type.
Attack The type of attack that was detected and prevented.
Viewing spam email detected

2 In the Attack Log section, select Details for Spam.
Date and Time The time that the spam was detected.
From->To IP The sender and intended recipient IP addresses.
From->To Email Accounts The sender and intended recipient email addresses.
Service The service type, such as SMTP, POP or IMAP.
SPAM Type The type of spam that was detected.
Viewing URLs blocked

2 In the Attack Log section, select Details for Web.
Date and Time The time that the attempt to access the URL was detected.
From The host that attempted to view the URL.
URL Blocked The URL that was blocked.

01-30007-0203-20090112 89
Topology System Status
Topology
The Topology page provides a way to diagram and document the networks
connected to your FortiGate unit. It is available on all FortiGate models except
FortiGate-50 and FortiGate-60. The Topology viewer is not available if Virtual
Domains (VDOMs) are enabled.
Go to System > Status > Topology to view the system topology. The Topology
page consists of a large canvas upon which you can draw a network topology
diagram of your FortiGate installation.
Figure 39: Topology page
Zoom/Edit controls Text object Subnet object
FortiGate unit object Viewport Viewport

control
Viewport and viewport control

The viewport displays only a portion of the drawing area. The viewport control, at
the bottom right of the topology page, represents the entire drawing area. The
darker rectangle represents the viewport. Drag the viewport rectangle within the
viewport control to determine which part of the drawing area the viewport displays.
The “+” and “-” buttons in the viewport control have the same function as the Zoom
in and Zoom out controls.

90 01-30007-0203-20090112
System Status Topology
Zoom and Edit controls

The toolbar at the top left of the Topology page shows controls for viewing and
editing the topology diagram.
Table 3: Zoom and Edit controls for Topology
Refresh the displayed diagram.
Zoom in. Select to display a smaller portion of the drawing area in

the viewport, making objects appear larger.
Zoom out. Select to display a larger portion of the drawing area in the
viewport, making objects appear smaller.
Select to begin editing the diagram.

This button expands the toolbar to show the editing controls
described below:
Save changes made to the diagram.
Note: If you switch to any other page in the web-based manager
without saving your changes, your changes are lost.
Add a subnet object to the diagram. The subnet object is based on
the firewall address that you select, and is connected by a line to the
interface associated with that address. See “Adding a subnet object”
on page 92.
Insert Text. Select this control and then click on the diagram where
you want to place the text object. Type the text and then click outside
the text box.
Delete. Select the object(s) to delete and then select this control or
press the Delete key.
Customize. Select to change the colors and the thickness of lines

used in the drawing. See “Customizing the topology diagram” on
page 93.
Drag. Select this control and then drag objects in the diagram to
arrange them.
Scroll. Select this control and then drag the drawing area
background to move the viewport within the drawing area. This has
the same effect as moving the viewport rectangle within the viewport
control.
Select. Select this control and then drag to create a selection
rectangle. Objects within the rectangle are selected when you
release the mouse button.
Exit. Select to finish editing the diagram. Save changes first.
The toolbar contracts to show only the Refresh and Zoom controls.
FortiGate unit object

The FortiGate unit is a permanent part of the topology diagram. You can move it,
but not delete it.

01-30007-0203-20090112 91
The FortiGate unit object shows the link status of the unit’s interfaces. Green
indicates the interface is up. Grey indicates the interface is down. Select the
interface to view its IP address and netmask, if assigned.
Adding a subnet object

While editing the topology diagram, you can select the Add Subnet control to
define a subnet object. The object is drawn and connected by a line to the
interface associated with the address.
Figure 40: Adding an existing subnet to the topology diagram
Figure 41: Adding a new subnet to the topology diagram
Select from existing Create a subnet object based on an existing firewall

address/group address. The object has the name of the firewall address
and is connected by a line to the interface associated with
that address. For more information about firewall
addresses, see “Firewall Address” on page 315.
Address Name Enter a name to identify the firewall address. Addresses,
address groups, and virtual IPs must have unique names
to avoid confusion in firewall policies.
Connect to interface Select the interface or zone to associate with this address.
If the field already displays a name, changing the setting
changes the interface or zone associated with this existing
address.
If the address is currently used in a firewall policy, you can
choose only the interface selected in the policy.
New addresses Create a new firewall address and add a subnet object
based on that address to the topology diagram. The
address is associated with the interface you choose.
Address Name Enter a name to identify the firewall address. Addresses,
address groups, and virtual IPs must have unique names
to avoid confusion in firewall policies.
Type Select the type of address: Subnet/IP Range or FQDN.
Subnet / IP Range If Type is Subnet/IP Range, enter the firewall IP address,
followed by a forward slash and then the subnet mask.
Alternatively, enter IP range start address, followed by a
hyphen (-) and the IP range end address.

92 01-30007-0203-20090112
System Status Topology
FQDN If Type is FQDN, enter the fully qualified domain name.

Connect to interface Select the interface or zone to associate with this address.
Customizing the topology diagram

In System > Status > Topology, select the Customize button to open the
Topology Customization window. Modify the settings as needed and select OK
when you are finished.
Figure 42: Topology Customization window
Preview A simulated topology diagram showing the effect of the selected

appearance options.
Canvas Size The size of the drawing in pixels.
Resize to Image If you selected an image as Background, resize the diagram to fit
within the image.
Background One of:
Solid - a solid color selected in Background Color
U.S. Map - a map of the United States.
World Map - a map of the world.
Upload My Image - upload the image from Image Path.
Background Color Select the color of the diagram background.
Image path If you selected Upload My Image for Background, enter the path to
your image, or use the Browse button to find it.
Exterior Color Select the color of the border region outside your diagram.
Line Color Select the color of connecting lines between subnet objects and
interfaces.
Line Width Select the thickness of connecting lines.
Reset to Default Reset all topology diagram settings to default.

01-30007-0203-20090112 93

94 01-30007-0203-20090112
Using virtual domains Virtual domains
Using virtual domains

This section describes virtual domains along with some of their benefits, and how
to use them to operate your FortiGate unit as multiple virtual units.
If you enable virtual domains (VDOMs) on the FortiGate unit, you configure virtual
domains globally for the FortiGate unit.
To get started working with virtual domains, see “Enabling VDOMs” on page 100.
• Virtual domains
• Enabling VDOMs
• Configuring VDOMs and global settings
Virtual domains
Virtual domains (VDOMs) are a method of dividing a FortiGate unit into two or
more virtual units that function as multiple independent units. A single FortiGate
unit is then flexible enough to serve multiple departments of an organization,
separate organizations, or be the basis for a service provider’s managed security
service.
Some benefits of VDOMs are:
• Easier administration
• Maintain Security
• Easy to increase or decrease number of VDOMs
Easier administration
VDOMs provide separate security domains that allow separate zones, user
authentication, firewall policies, routing, and VPN configurations. Using VDOMs
can also simplify administration of complex configurations because you do not
have to manage as many routes or firewall policies at one time. See “VDOM
configuration settings” on page 97.
By default, each FortiGate unit has a VDOM named root. This VDOM includes all
of the FortiGate physical interfaces, modem, VLAN subinterfaces, zones, firewall
policies, routing settings, and VPN settings.
Also you can optionally assign an administrator account restricted to that VDOM.
If the VDOM is created to serve an organization, this feature enables the
organization to manage its own configuration.
Management systems such as SNMP, logging, alert email, FDN-based updates
and NTP-based time setting use addresses and routing in the management
VDOM to communicate with the network. They can connect only to network
resources that communicate with the management virtual domain. The
management VDOM is set to root by default, but can be changed. For more
information see “Changing the Management VDOM” on page 106.

01-30007-0203-20090112 95
Virtual domains Using virtual domains
Maintain Security
When a packet enters a VDOM, it is confined to that VDOM. In a VDOM, you can
create firewall policies for connections between VLAN subinterfaces or zones in
the VDOM. Packets do not cross the virtual domain border internally. To travel
between VDOMs a packet must pass through a firewall on a physical interface.
The packet then arrives at another VDOM on a different interface where it must
pass through another firewall before entering. Both VDOMs are on the same
FortiGate unit. Inter-VDOMs change this in that they are internal interfaces,
however their packets go through all the same security measures as on physical
interfaces.
Without VDOMs, administrators can easily access settings across the FortiGate.
This can lead to security issues or far-reaching configuration errors. However,
administrator permissions are specific to one VDOM. An admin on one VDOM
can't change information on another VDOM. Any configuration changes, and
potential errors, will apply only to that VDOM and limit any potential down time.
The remainder of FortiGate functionality is global - it applies to all VDOMs. This
means there is one intrusion prevention configuration, one antivirus configuration,
one web filter configuration, one protection profile configuration, and so on. As
well, VDOMs share firmware versions, antivirus and attack databases. The
operating mode, NAT/Route or Transparent, is independently selectable for each
VDOM. For a complete list of shared configuration settings, see “Global
Easy to increase or decrease number of VDOMs

To increase the number of physical units, you need to deal with shipping issues,
you need more space and cables to install them, and you will likely need to
change your network to accommodate them.
Increasing VDOMs involves no extra hardware, no shipping, and very few
changes to existing networking. They take no extra physical space - you are only
limited by the size of the license you buy for your VDOMs.
By default, your FortiGate unit supports a maximum of 10 VDOMs in any
combination of NAT/Route and Transparent modes. For FortiGate models
numbered 3000 and higher, you can purchase a license key to increase the
maximum number of VDOMs to 25, 50, 100 or 250. For more information see
“License” on page 254.
Note: When configuring a FortiAnalyzer unit, VDOMs count toward the maximum number
of FortiGate units allowed by the FortiAnalyzer unit’s license. The total number of devices
registered can be seen on the FortiAnalyzer unit’s System Status page under License
Information.
If virtual domain configuration is enabled and you log in as the default super
admin, you can go to System > Status and look at Virtual Domain in the License
Information section to see the maximum number of virtual domains supported on
your FortiGate unit.
For more information on VDOMs, see the FortiGate VLANs and VDOMs Guide.

96 01-30007-0203-20090112
VDOM configuration settings

To configure and use VDOMs, you must enable virtual domain configuration on
the System > Status dashboard, or using config system global, set
vdom-admin in the CLI. See “Enabling VDOMs” on page 100.
You can configure a VDOM by adding VLAN subinterfaces, zones, firewall
policies, routing settings, and VPN settings. You can also move physical
interfaces from the root VDOM to other VDOMs and move VLAN subinterfaces
from one VDOM to another. For more information on VLANs, see “VLAN
overview” on page 138.
The following configuration settings are exclusively part of a virtual domain and
are not shared between virtual domains. A regular administrator for the VDOM
sees only these settings. The default super admin can also access these settings,
but must first select which VDOM to configure.
Table 4: VDOM configuration settings
Configuration Object For more information

System
Zone “Configuring zones” on page 128
Routing Table “Routing table (Transparent Mode)” on page 137
(Transparent mode)
Modem “Configuring the modem interface” on page 129
Wireless MAC Filter “Wireless MAC Filter” on page 156
Wireless Monitor “Wireless Monitor” on page 159
DHCP services “Configuring DHCP services” on page 162
Operation mode “Changing operation mode” on page 193
(NAT/Route or
Transparent)
Management IP “Changing operation mode” on page 193
(Transparent mode)
Router
Static “Router Static” on page 255
Dynamic “Router Dynamic” on page 267
Monitor “Router Monitor” on page 289
Firewall
Policy “Firewall Policy” on page 293
Address “Firewall Address” on page 315
Service “Firewall Service” on page 321
Schedule “Firewall Schedule” on page 329
Virtual IP “Firewall Virtual IP” on page 333
IP pool “IP pools” on page 356
Protection Profile “Firewall Protection Profile” on page 365
VPN
IPSec “VPN IPSEC” on page 393
PPTP “VPN PPTP” on page 411
SSL “VPN SSL” on page 413
User

01-30007-0203-20090112 97
Virtual domains Using virtual domains
Table 4: VDOM configuration settings (Continued)

Local “Local user accounts” on page 422
Remote “Remote authentication” on page 423
Directory Service “Directory Service servers” on page 433
PKI “PKI authentication” on page 431
User Group “User groups” on page 435
Authentication “Authentication settings” on page 445
Antivirus
File Filter “File Filter” on page 450
Intrusion Protection (IPS)
Signature “Signatures” on page 465
IPS Sensor “IPS sensors” on page 469
DoS Sensor “DoS sensors” on page 475
Web Filter
Content Block “Content block” on page 482
URL FIlter “URL filter” on page 487
FortiGuard - Web Filter “FortiGuard - Web Filter” on page 491
AntiSpam
Banned Word “Banned word” on page 502
Black/White List “Black/White List” on page 505
IM, P2P, & VoIP
Statistics “Statistics” on page 518
User “User” on page 521
Log & Report
Logging configuration “FortiGate logging” on page 525
(Memory only)
Alert E-mail “Configuring Alert Email” on page 547
(Send alert email for the following)
Event Log “Event log” on page 536
Log access “Accessing Logs” on page 539
Content Archive “Content Archive” on page 545
Report Config “Reports” on page 549
Report Access “Reports” on page 549
Global configuration settings

The following configuration settings affect all virtual domains. When virtual
domains are enabled, only accounts with the default super admin profile can
access global settings.
Table 5: Global configuration settings

System

98 01-30007-0203-20090112
Table 5: Global configuration settings (Continued)

Physical interfaces and “Interfaces” on page 107 and “VLAN overview” on
VLAN subinterfaces page 138
(You configure interfaces as part of the Global configuration
but each interface and VLAN subinterface belongs to a
VDOM. You add interfaces to VDOMS as part of the global
configuration.)
DNS settings “DNS Servers” on page 136
Host name “Changing the FortiGate unit host name” on page 80
System Time “Configuring system time” on page 80
Firmware version “Upgrading to a new firmware version” on page 82 (System
Status page) or “Managing firmware versions” on page 555.
Idle and authentication “Settings” on page 215 and “Configuring user
timeout authentication” on page 421
Web-based manager “Settings” on page 215
language
LCD panel PIN, where “Settings” on page 215
applicable
Dead gateway “Dead gateway detection” on page 137
detection
Wireless Settings “System wireless settings” on page 150
HA configuration “HA” on page 167
SNMP configuration “SNMP” on page 176
Replacement “Replacement messages” on page 188
messages
Administrators “Administrators” on page 195
(You can add global administrators. You can also add
administrators to VDOMs. VDOM administrators cannot
add or configuration administrator accounts.)
Access profiles “Access profiles” on page 208
Certificates “System Certificates” on page 219
FortiManager and “Central Management” on page 212
Central Management
configuration
Configuration backup “Backup and Restore” on page 231
and restore
Scripts “Scripts” on page 240
FDN update “FortiGuard Distribution Network” on page 241
configuration
Antivirus
Quarantine “Quarantine” on page 454
Configuration “Viewing the virus list” on page 458 and “Viewing and
configuring the grayware list” on page 459
Log & Report
Log Configuration “FortiGate logging” on page 525
(Remote and Syslog)
Alert E-mail “Configuring Alert Email” on page 547
(Alert email account settings.)
Report Config “Reports” on page 549
Report Access “Reports” on page 549

01-30007-0203-20090112 99
Enabling VDOMs Using virtual domains
Enabling VDOMs
Using the default admin administration account, you can enable multiple VDOM
operation on the FortiGate unit.
To enable virtual domains

1 Log in to the web-based manager on a super admin profile account.
3 In System Information, next to Virtual Domain select Enable.
The FortiGate unit logs you off. You can now log in again as admin.
When virtual domains are enabled, the web-based manager and the CLI are
changed as follows:
• Global and per-VDOM configurations are separated.
• A new VDOM entry appears under the System option.
• When you are in a VDOM, there are reduced menu options available, and a
new Global entry appears.
• Only super admin profile accounts can view or configure global options.
• Super admin profile accounts can configure all VDOM configurations.
• One or more administrators can be setup for each VDOM, but can only edit
that VDOM’s settings.
When virtual domains are enabled, you can see what the current virtual domain is
by looking at the bottom left of the screen. It will say Current VDOM: followed by
the name of the virtual domain.
Configuring VDOMs and global settings

A VDOM is not useful unless it contains at least two physical interfaces or virtual
subinterfaces for incoming and outgoing traffic. Only the super admin can assign
interfaces or subinterfaces to VDOMs. However, a regular administrator account
can create a VLAN subinterface on a physical interface within their own VDOM.
Only super_admin profile accounts can configure a VDOM unless you create and
assign a regular administrator to that VDOM. Only super admin profile accounts
can assign an administrator to a VDOM. An administrator account whose access
profile provides read and write access to Admin Users can create additional
administrators in its own VDOM.

100 01-30007-0203-20090112
Using virtual domains Configuring VDOMs and global settings
Table 6: Admin VDOM permissions
Tasks Regular admin with Super admin profile

read/write permission account
Configure global settings no yes
Create or delete VDOMs no yes
Configure multiple VDOMs no yes
Assign interfaces to a VDOM no yes
Create VLANs yes - for 1 VDOM yes - for all VDOMs
Assign an administrator to a VDOM no yes
Create additional admin accounts yes - for 1 VDOM yes - for all VDOMs
Create and edit protection profiles yes - for 1 VDOM yes - for all VDOMs
Creating a new VDOM

By default, every FortiGate unit has a root VDOM that is visible when VDOMs are
enabled. To use additional VDOMs, you must first create them.
Note: The VDOM names vsys_ha and vsys_fgfm are in use by the FortiGate unit. If
you attempt to name a new VDOM vsys_ha or vsys_fgfm it will generate an error.
Figure 43: New Virtual Domain
To create a new VDOM

1 Log in as a super admin profile admin.
2 Ensure VDOMs are enabled.
3 Go to System > VDOM.
4 Select Create New VDOM.
5 Enter a name for the new VDOM, up to a maximum of 11 characters.
The name must not contain any spaces, or special characters. Hyphens (“-”) and
underlines (“_”) are allowed.
6 Optionally enter a comment for the VDOM, up to a maximum of 64 characters.
7 Select Apply.

01-30007-0203-20090112 101
Configuring VDOMs and global settings Using virtual domains
Working with VDOMs and global settings

When you log in as admin and virtual domains are enabled you are automatically
in global configuration, as demonstrated by the VDOM option under System.
Select System > VDOM to work with virtual domains.
Figure 44: VDOM list
Disabled VDOM
Management VDOM
Create New Select to add a new VDOM. Enter the new VDOM name and
select OK.
The VDOM must not have the same name as an existing VDOM,
VLAN or zone. The VDOM name can be a maximum of 11
characters long without spaces.
Management Virtual Change the management VDOM to the selected VDOM in the
Domain drop down list. The management VDOM is indicated in the list of
VDOMs as being greyed out in the Enable column. The default
management VDOM is root.
For more information see “Changing the Management VDOM” on
page 106.
Apply Select Apply to save your changes to the Management VDOM.
Enable There are three states this column can be in.
A green check mark indicates this VDOM is enabled, and you can
select the Enter icon to change to that VDOM.
An empty check box indicates this VDOM is disabled. When
disabled, the configuration of that VDOM is preserved. The Enter
icon is not available.
A greyed out checkbox indicates this VDOM is the management
VDOM. It cannot be deleted or changed to disabled - it is always
active.
Name The name of the VDOM.
Operation Mode The VDOM operation mode, either NAT or Transparent.
Interfaces The interfaces associated with this VDOM, including virtual
interfaces.
Every VDOM includes an SSL VPN virtual interface named for
that VDOM. For the root VDOM this interface is ssl.root.
Comments When you are creating a VDOM you can add comments to
provide custom information about this VDOM.
Delete icon Select to delete the VDOM.
The delete icon appears only when there are no configuration
objects associated with that VDOM. For example you must
remove all referring interfaces, profiles, and so on before you can
delete the VDOM.
If the delete icon does not appear and you do not want to delete
all the referring configuration, you can disable the VDOM instead.

102 01-30007-0203-20090112
Edit icon Select to change the description of the VDOM. The name of the
VDOM can not be changed.
Enter icon Select to enter the selected VDOM.
After entering a VDOM you will only be able to view and change
settings specific to that VDOM.
Adding interfaces to a VDOM

A VDOM must contain at least two interfaces to be useful. These can be physical
or virtual interfaces such as VLAN subinterfaces. By default, all physical
interfaces are in the root virtual domain.
VLAN subinterfaces often need to be in a different VDOM than their physical
interface. To do this, the super admin must first create the VDOM, create the
VLAN subinterface, and then assign the VLAN to the correct VDOM.
System > Network > Interfaces is only available in global settings, and not within
VDOMs. For information on creating VLAN subinterfaces, see “Adding VLAN
subinterfaces” on page 141.
Inter-VDOM links
An inter-VDOM link is a pair of interfaces that enable you to communicate
between 2 VDOMs internally without using a physical interface. Inter-VDOM links
have the same security as physical interfaces, but allow more flexible
configurations that are not limited by the number of physical interfaces on your
FortiGate unit. As with all virtual interfaces, the speed of the link depends on the
CPU load but generally it is faster than physical interfaces. There are no MTU
settings for inter-VDOM links. DHCP support includes inter-VDOM links.
A packet can pass through an inter-VDOM link a maximum of three times. This is
to prevent a loop. When traffic is encrypted or decrypted it changes the content of
the packets and this resets the inter-VDOM counter. However using IPIP or GRE
tunnels do not reset the counter.
In HA mode, inter-VDOM links must have both ends of the link within the same
virtual cluster. DHCP over IPSec is supported for inter-VDOM links, however
regular DHCP services are not available.
On the interface screen, an inter-VDOM link has an entry for the link. This can be
expanded to show the 2 virtual interfaces in that link. The type of interface for the
link is “VDOM link” and each of the virtual interfaces is “pair” type. Each of the
virtual interfaces is named using the inter-VDOM link name with an added “0” or
“1”. So if the inter-VDOM link is called “vlink” the interfaces would be “vlink0” and
“vlink1”.
Note: Inter-VDOM links can not refer to a domain that is in transparent mode.
Figure 45: VDOM link interfaces

01-30007-0203-20090112 103
To create an inter-VDOM link

1 Log in as admin.
3 Select Create > VDOM link.
You will see the New VDOM Link screen.
Figure 46: New VDOM link
4 Enter the name for the new VDOM link, up to a maximum of 11 characters.
The name must not contain any spaces, or special characters. Hyphens (“-”) and
underlines (“_”) are allowed. Remember that the name will have a “0” or “1”
attached to the end for the actual interfaces.
5 Configure VDOM link “0”.
6 Select the VDOM from the menu. This is the VDOM this interface will connect to,
and is different from the VDOM for the other interface in the VDOM link.
7 Enter the IP address and netmask for this interface.
8 Select the administrative access method or methods. Keep in mind that PING,
TELNET, and HTTP are less secure methods.
9 Optionally enter a description for this interface.
10 Repeat steps 6 through 9 for VDOM link “1”.
11 Select OK to save your confrontation and return to the System > Interface
screen.
Assigning an interface to a VDOM

The following procedure describes how to reassign an existing interface from one
virtual domain to another. It assumes VDOMs are enabled and more than one
VDOM exists.
You cannot delete a VDOM if it is used in any configurations, such as having an
interface in that VDOM. You cannot remove an interface from a VDOM if the
interface is included in of any of the following configurations:
• DHCP server
• zone

104 01-30007-0203-20090112
• routing
• firewall policy
• IP pool
• proxy arp (only accessible through the CLI)
Before removing these configurations, it is recommended that you backup your
configuration, so you can restore it if you want to create this VDOM at a later date.
Delete the items in this list or modify them to remove the interface before
proceeding.
Note: An interface or subinterface is available for reassigning or removing once the delete
icon is displayed. Until then, the interface is used in a configuration somewhere.
Instead of deleting a VDOM, you can disable a VDOM. This has the benefit of
preserving your configuration and saving the time to remove and re-configure it
later.
To assign an interface to a VDOM

1 Log in as admin.
3 Select Edit for the interface that you want to reassign.
4 Select the new Virtual Domain for the interface.
5 Configure other settings as required and select OK. For more information on the
other interfaces settings see “Interface settings” on page 112.
The interface is assigned to the VDOM. Existing firewall IP pools and virtual IP
addresses for this interface are deleted. You should manually delete any routes
that include this interface, and create new routes for this interface in the new
VDOM. Otherwise your network traffic will not be properly routed.
Assigning an administrator to a VDOM

If you are creating a VDOM to serve an organization that will be administering its
own resources, you need to create an administrator account for that VDOM.
A VDOM admin can change configuration settings within that VDOM but cannot
make changes that affect other VDOMs on the FortiGate unit.
A regular administrator assigned to a VDOM can log in to the web-based manager
or the CLI only on interfaces that belong to that VDOM. The super admin can
connect to the web-based manager or CLI through any interface on the FortiGate
unit that permits management access. Only the super admin or a regular
administrator of the root domain can log in by connecting to the console interface.
Note: If an admin account is assigned to a VDOM, that VDOM cannot be deleted until that
account is removed, or assigned to another VDOM.
To assign an administrator to a VDOM

1 Log in as the super admin.
Virtual domains must be enabled.
2 Go to System > Admin >Administrators.

01-30007-0203-20090112 105
3 Create and/or configure the new administrator account as required.

For detailed information about configuring an administrator account, see
“Configuring an administrator account” on page 205.
4 While configuring this admin account, select the VDOM this administrator
manages from the Virtual Domain list.
5 Select Apply.
Changing the Management VDOM

The management VDOM on your FortiGate unit is where some default types of traffic
originate. These types of traffic include:
• SNMP
• logging
• alert email
• FDN-based updates
• NTP-based time setting
Before you change the management VDOM, ensure virtual domains are enabled
on the system dashboard screen.
Only one VDOM can be the management VDOM at any given time.
Global events are logged with the VDOM set to the management VDOM.
Note: You cannot change the management VDOM if any administrators are using RADIUS
authentication.
To change the management VDOM

1 Go to System > VDOM.
2 Select the VDOM to be the new management VDOM from the drop down list of
VDOMs.
This drop down list is located to the immediate left of the Apply button.
3 Select Apply to make the change.
You will be prompted to confirm the change.
Management traffic will now originate from the new management VDOM.

106 01-30007-0203-20090112
System Network Interfaces
System Network
This section describes how to configure your FortiGate unit to operate in your
network. Basic network settings include configuring FortiGate interfaces and DNS
settings. More advanced configuration includes adding VLAN subinterfaces and
zones to the FortiGate network configuration.
If you enable virtual domains (VDOMs) on the FortiGate unit, you configure most
system network settings globally for the entire FortiGate unit. For example, all
interface settings, including adding interfaces to VDOMs, are part of the global
configuration. However, zones, the modem interface, and the Transparent mode
routing table are configured separately for each virtual domain. For details, see
“Using virtual domains” on page 95.
• Interfaces
• Configuring zones
• Configuring the modem interface
• Configuring Networking Options
• Routing table (Transparent Mode)
• VLAN overview
• VLANs in NAT/Route mode
• VLANs in Transparent mode
Note: Unless stated otherwise, the term interface can refer to either a physical FortiGate
interface or to a virtual FortiGate VLAN subinterface.
Note: If you can enter both an IP address and a netmask in the same field, you can use the
short form of the netmask. For example, 192.168.1.100/255.255.255.0 can also be entered
as 192.168.1.100/24.
Interfaces
In NAT/Route mode, go to System > Network > Interface to configure FortiGate
interfaces. You can:
• modify the configuration of a physical interface
• add and configure VLAN subinterfaces
• configure an ADSL interface
• aggregate several physical interfaces into an IEEE 802.3ad interface (models
300A, 310B, 400A, 500A, 620B, and 800 or higher)
• combine physical interfaces into a redundant interface
• add wireless interfaces (FortiWiFi models 50B, 60A, 60AM, and 60B) and
service set identifiers (SSIDs) (see “Adding a wireless interface” on page 152)
• add and configure VDOM links (see “Inter-VDOM links” on page 103)

01-30007-0203-20090112 107
Interfaces System Network
• view loopback interfaces

• configure the modem (see “Configuring the modem interface” on page 129)
• change which information about the interfaces is displayed
For information about VLANs, see “FortiGate units and VLANs” on page 139.
Figure 47: Interface list - regular admin view
Figure 48: Interface list - admin view with virtual domains enabled
Create New Select Create New to create a VLAN subinterface.

On models 800 and higher, you can also create an IEEE 802.3ad
aggregated interface.
When VDOMs are enabled, selecting the Create New arrow enables
you to create new Inter-VDOM links. For more information see “Inter-
VDOM links” on page 103.
Switch Mode Select to change between switch mode and interface mode. Switch
mode combines the internal interfaces into one switch with one
address. Interface mode gives each internal interface its own address.
Before switching modes, all configuration settings that point to ‘internal’
interfaces must be removed.
This option is visible only on models 100A and 200A for Rev2.0 and
higher. Switch mode is also visible on the FortiGate-60B and
FortiWiFi-60B. For more information see “Switch Mode” on page 111.
show backplane Select to make the two backplane interfaces visible as port9 and port10.
interfaces Once visible these interfaces can be treated as regular physical
interfaces.
This option is available only on 5000 models.
Column Settings Select to change the which columns of information about the network
interfaces is displayed. For more information, see “Column Settings” on
page 110.

108 01-30007-0203-20090112
Description icon The tooltip for this icon displays the Description field for this interface.
For more information see “Interface settings” on page 112.
Name The names of the physical interfaces on your FortiGate unit. This
includes any alias names that have been configured.
The name, including number, of a physical interface depends on the
model. Some names indicate the default function of the interface such
as Internal, External and DMZ. Other names are generic such as port1.
FortiGate models numbered 50 and 60 provide a modem interface. Also
models with a USB port support a connected modem. See “Configuring
the modem interface” on page 129.
The oob/ha interface is the FortiGate-4000 out of band management
interface. You can connect to this interface to manage the FortiGate
unit. This interface is also available as an HA heartbeat interface.
On FortiGate-60ADSL units, you can configure the ADSL interface. See
“Configuring an ADSL interface” on page 115.
On FortiGate models 300A, 400A, 500A, and 800 or higher, if you
combine several interfaces into an aggregate interface, only the
aggregate interface is listed, not the component interfaces. The same is
true for redundant interfaces. See “Creating an 802.3ad aggregate
interface” on page 116 or “Creating a redundant interface” on page 117.
If you have added VLAN subinterfaces, they also appear in the name
list, below the physical or aggregated interface to which they have been
added. See “VLAN overview” on page 138.
If you have loopback virtual interfaces configured you will be able to
view them. You can only edit these interfaces in the CLI. For more
information on these interfaces see “Configuring interfaces with CLI
commands” on page 123 or the config system interface
command in the FortiGate CLI Reference.
If you have software switch interfaces configured, you will be able to
view them. You can only edit these interfaces in the CLI. for more
information on these interfaces see “Configuring interfaces with CLI
commands” on page 123 or the config system switch-
interface command in the FortiGate CLI Reference.
If virtual domain configuration is enabled, you can view information only
for the interfaces that are in your current virtual domain, unless you are
using the super admin account.
If VDOMs are enabled, you will be able to create, edit, and view inter-
VDOM links. For more information see “Inter-VDOM links” on page 103.
If you have interface mode enabled on a FortiGate model 100A or 200A
Rev2.0 or higher or on the FortiGate-60B and FortiWiFi-60B models,
you will see multiple internal interfaces. If switch mode is enabled, there
will only be one internal interface. For more information see “Switch
Mode” on page 111.
If your FortiGate unit supports AMC modules and if you have installed
an AMC module containing interfaces (for example, the
FortiGate-ASM-FB4 contains 4 interfaces) these interfaces are added
to the interface status display. The interfaces are named AMC-SW1/1,
AMC-DW1/2, and so on. SW1 indicates it is a single width or double
width card respectively in slot 1. The last number “/1” indicates the
interface number on that card - for the ASM-FB4 card there would be
“/1” through “/4”.
IP/Netmask The current IP address/netmask of the interface.
In VDOM mode, when VDOMs are not all in NAT or Transparent mode
some values may not be available for display and will be displayed as “-
” instead.
When IPv6 Support on GUI is enabled, IPv6 addresses may be
displayed in this column.
Access The administrative access configuration for the interface.
See “Additional configuration for interfaces” on page 125.
Administrative The administrative status for the interface.
Status If the administrative status is a green arrow, the interface is up and can
accept network traffic. If the administrative status is a red arrow, the
interface is administratively down and cannot accept traffic. To change
the administrative status, select Bring Down or Bring Up.

01-30007-0203-20090112 109
Link Status The status of physical connection.

The status of a non-physical interface will always be down.
MAC The MAC address of the interface.
Mode Shows the addressing mode of this interface such as manual, DHCP, or
PPPoE.
MTU The maximum number of bytes per transmission unit. Anything over
1500 are jumbo frames. See “Interface MTU packet size” on page 125.
Secondary IP Any secondary IPs for this interface.
Type The type of the interface. Valid types include:
• Physical - a physical network interface, including modem
• VLAN - a virtual network interface
• Aggregate - a group of interfaces
• Redundant - a group of interfaces
• VDOM Link - a pair of virtual interface that join two VDOMs
• Pair - one two interfaces that are joined together, such as 2 VDOM
links
Virtual Domain The virtual domain to which the interface belongs. This column is visible
only to the super admin and only when virtual domain configuration is
enabled.
VLAN ID The identification number of the VLAN.
Non-VLAN interface entries will be blank.
Delete, edit, and Delete, edit, or view an entry.
view icons
Column Settings
Go to System > Network > Column Settings to change which information about
the interfaces is displayed.
The VDOM field is only available for display when VDOMs are enabled.
Figure 49: Column Settings
Available fields The list of fields (columns) not currently being displayed.
Show these fields in The list of fields (columns) currently being displayed.
this order They are displayed in order. Top to bottom of the list will be
displayed left to right on screen respectively.
Right arrow Move selected fields to the Show these fields in this order list.
Left arrow Move selected fields to the Available fields list.

110 01-30007-0203-20090112
Move up Move selected item up in the Show these fields in this order list.
The corresponding column is moved to the left on the network
interface display.
Move down Move selected item down in the Show these fields in this order list.
The corresponding column is moved to the right on the network
interface display.
Switch Mode
The internal interface is a switch with either four or six physical interface
connections, depending on the FortiGate unit model. Normally the internal
interface is configured as a single interface shared by all physical interface
connections - a switch.
The switch mode feature has two states - switch mode and interface mode.
Switch mode is the default mode with only one interface and one address for the
entire internal switch. Interface mode allows you to configure each of the internal
switch physical interface connections separately. This allows you to assign
different subnets and netmasks to each of the internal physical interface
connections.
Note: Interfaces that are part of the switch can not be used for VLANs.
FortiGate unit models 100A and 200A Rev2.0 and higher have four internal
interface connections. The FortiGate-60B and FortiWifi-60B have six internal
interface connections. Consult your release notes for the most current list of
supported models for this feature.
Selecting Switch Mode on the System > Network > Interface screen takes you to
the Switch Mode Management screen.
Caution: Before you are able to change between switch mode and interface mode all
! references to ‘internal’ interfaces must be removed. This includes references such as
firewall policies, routing, DNS forwarding, DHCP services, VDOM interface assignments,
and routing. If they are not removed, you will not be able to switch modes, and you will see
an error message.
Figure 50: Switch Mode Management
Switch Mode Select Switch Mode. Only one internal interface is displayed. This
is the default mode.
Interface Mode Select Interface Mode. All internal interfaces on the switch are
displayed as individually configurable interfaces.
Switch Mode can also be configured using CLI commands. For more information
see the FortiGate CLI Reference.

01-30007-0203-20090112 111
Interface settings
Go to System > Network > Interface and select Create New. Selecting the
Create New arrow enables you to create Inter-VDOM links. For more information
on Inter-VDOM links, see “Inter-VDOM links” on page 103.
Some types of interfaces such as loopback interfaces can only be configured
using CLI commands. For more information see “Configuring interfaces with CLI
commands” on page 123. To be able to configure a DHCP server on an interface,
that interface must have a static IP address.
You cannot create a virtual IPSec interface on this screen, but you can specify its
endpoint addresses, enable administrative access and provide a description if you
are editing an existing interface. For more information, see “Configuring a virtual
IPSec interface” on page 122.
Figure 51: Create New Interface settings
Figure 52: Edit Interface settings

112 01-30007-0203-20090112
Name Enter a name for the interface.

You cannot change the name of an existing interface.
Alias Enter another name for the interface that will easily distinguish this
interface from another. This is available only for physical interfaces
where where you cannot configure the name. The alias can be a
maximum of 15 characters.
The alias name is not part of the interface name, but it will appear in
brackets beside the interface name. It will not appears in logs.
Type The type of the interfaces. When creating a new interface, this is VLAN
by default.
On models 300A, 310B, 400A, 500A, 620B, 800 and higher, you can
create VLAN, 802.3ad Aggregate, and Redundant interfaces.
• On FortiGate 100A and 200A models of Rev2.0 and higher and on
all 60B models, software switch is a valid type. You cannot edit this
type in the GUI.
• On FortiWiFi models 50B, 60A, 60AM, and 60B, you can support up
to four SSIDs by adding up to three wireless interfaces (for a total of
four wireless interfaces).
• On the 60ADSL model, you can configure an ADSL interface.
Other models support creation of VLAN interfaces only and have no
Type field.
You cannot change the type of an existing interface.
Interface Select the name of the physical interface on which to create the VLAN.
Once created, the VLAN subinterface is listed below its physical
interface in the Interface list.
You cannot change the interface of an existing VLAN subinterface.
This field is only displayed when Type is set to VLAN.
VLAN ID Enter the VLAN ID that matches the VLAN ID of the packets to be
received by this VLAN subinterface. You cannot change the VLAN ID of
an existing VLAN subinterface.
The VLAN ID can be any number between 1 and 4094 and must match
the VLAN ID added by the IEEE 802.1Q-compliant router or switch
connected to the VLAN subinterface. See “VLAN overview” on
page 138.
This field is only displayed when Type is set to VLAN.
Virtual Domain Select the virtual domain to which this VLAN subinterface belongs.
Admin accounts with super-admin profile can change the VDOM for a
VLAN when VDOM configuration is enabled. See “Using virtual
Physical This section has two different forms depending on the interface type:
Interface • Software switch interface - this section is a display-only field showing
Members the interfaces that belong to the software switch virtual interface
• 802.3ad aggregate or Redundant interface - this section includes
available interface and selected interface lists to enable adding or
removing interfaces from the interface.
Available Select interfaces from this list to include in the grouped interface - either
Interfaces redundant or aggregate interface. Select the right arrow to add an
interface to the grouped interface.
Selected These interfaces are included in the aggregate or redundant interface.
interfaces Select the left arrow to remove an interface from the grouped interface.
For redundant interfaces, the interfaces will be activated during failover
from the top of the list to the bottom

01-30007-0203-20090112 113
Addressing Select the type of addressing mode as static or one of the available
mode dynamic modes.
To configure a static IP address for the interface, select Manual.
You can also configure the interface for dynamic IP address assignment.
See “Configuring DHCP on an interface” on page 118 or “Configuring an
interface for PPPoE or PPPoA” on page 120.
IP/Netmask Enter the IP address/subnet mask in the IP/Netmask field. The IP
address must be on the same subnet as the network to which the
interface connects.
Two interfaces cannot have IP addresses on the same subnet.
This field is only available when Manual addressing mode is selected.
DDNS Select DDNS to configure a Dynamic DNS service for this interface. See
“Configuring Dynamic DNS on an interface” on page 122.
Ping Server To enable dead gateway detection, enter the IP address of the next hop
router on the network connected to the interface and select Enable. See
“Dead gateway detection” on page 137.
Administrative Select the types of administrative access permitted on this interface.
Access
HTTPS Allow secure HTTPS connections to the web-based manager through
this interface.
PING Interface responds to pings. Use this setting to verify your installation
and for testing.
HTTP Allow HTTP connections to the web-based manager through this
interface. HTTP connections are not secure and can be intercepted by a
third party.
SSH Allow SSH connections to the CLI through this interface.
SNMP Allow a remote SNMP manager to request SNMP information by
connecting to this interface. See “Configuring SNMP” on page 176.
TELNET Allow Telnet connections to the CLI through this interface. Telnet
connections are not secure and can be intercepted by a third party.
MTU To change the MTU, select Override default MTU value (1 500) and
enter the MTU size based on the addressing mode of the interface
• 68 to 1 500 bytes for static mode
• 576 to 1 500 bytes for DHCP mode
• 576 to 1 492 bytes for PPPoE mode
• up to 16 110 bytes for jumbo frames (FortiGate models numbered
3000 and higher)
• NP2-accelerated interfaces support a jumbo frame limit of 16 000
bytes
• FA2-accelerated interfaces do not support jumbo frames
This field is available only on physical interfaces. VLANs inherit the
parent interface MTU size by default.
For more information on MTU and jumbo frames, see “Interface MTU
packet size” on page 125.
Secondary IP Add additional IP addresses to this interface. Select the blue arrow to
Address expand or hide the section. See “Secondary IP Addresses” on
page 126.
Description Enter a description up to 63 characters long.
Administrative Select either up (green arrow) or down (red arrow) as the status of this
Status interface.
Up indicates the interface is active and can accept network traffic.
Down indicates the interface is not active and cannot accept traffic.

114 01-30007-0203-20090112
Note: In Transparent mode, if you change the MTU of an interface, you must change the
MTU of all interfaces to match the new MTU.
To configure a specific type of interface, refer to the appropriate section. To

configure:
• an ADSL interface, see “Configuring an ADSL interface” on page 115.
• an aggregate interface, see “Creating an 802.3ad aggregate interface” on page 116.
• a redundant interface, see “Creating a redundant interface” on page 117.
• a VLAN subinterface, see “FortiGate units and VLANs” on page 139.
• a wireless interface, see “Adding a wireless interface” on page 152.
Configuring an ADSL interface

The information that you need to provide for the ADSL interface depends on the
addressing mode your ISP requires you to use. To use dynamic addressing see
“Configuring DHCP on an interface” on page 118 or “Configuring an interface for
PPPoE or PPPoA” on page 120.
To configure an ADSL interface, your FortiGate unit cannot be in Transparent
mode.
To configure an ADSL interface

ADSL interface addressing mode can be one of:
• IP over ATM (IPoA)
• Ethernet over ATM (EoA) (also known as Bridged mode)
• Dynamic Host Configuration Protocol (DHCP)
• Point-to-Point Protocol over Ethernet (PPPoE)
• Point-to-Point Protocol over ATM (PPPoA).
2 Select Create New or select the Edit icon of an existing interface.
3 In the Addressing mode section, select IPoA or EoA.
Figure 53: Settings for an ADSL interface

01-30007-0203-20090112 115
Addressing mode Select the addressing mode that your ISP specifies.
IPoA Enter the IP address and netmask that your ISP provides.
EoA Enter the IP address and netmask that your ISP provides.
DHCP See “Configuring DHCP on an interface” on
page 118.
PPPoE See “Configuring an interface for PPPoE or PPPoA”
on page 120.
PPPoA See “Configuring an interface for PPPoE or PPPoA”
on page 120.
IP/Netmask The IP address and netmask of this interface.
Gateway Enter the default gateway.
Connect to Server Enable Connect to Server so the interface will attempt to
connect automatically. Do not enable this option if you are
configuring the interface offline.
Virtual Circuit Identification Enter the VPI and VCI values your ISP provides.
MUX Type Select the MUX type: LLC Encap or VC Encap.
Your ISP must provide this information.
Creating an 802.3ad aggregate interface

You can aggregate (combine) two or more physical interfaces to increase
bandwidth and provide some link redundancy. An aggregate interface provides
more bandwidth but also creates more points of failure than redundant interfaces.
The interfaces must connect to the same next-hop routing destination.
Support of the IEEE standard 802.3ad for link aggregation is part of FortiGate
firmware on models 300A, 310B, 400A, 500A, 620B and models 800 and higher.
An interface is available to be an aggregate interface if:
• it is a physical interface, not a VLAN interface
• it is not already part of an aggregate or redundant interface
• it is in the same VDOM as the aggregated interface
• it does not have a IP address and is not configured for DHCP or PPPoE
• it does not have a DHCP server or relay configured on it
• it does not have any VLAN subinterfaces
• it is not referenced in any firewall policy, VIP, IP Pool or multicast policy
• it is not an HA heartbeat interface
• it is not one of the FortiGate 5000 series backplane interfaces
Note: You can add an accelerated interface (FA2 interfaces) to an aggregate link, but you
will lose the acceleration. For example, if you aggregate two accelerated interfaces you will
get slower throughput than if the two interfaces were separate.
Note: FortiGate-5000 backplane interfaces have to be made visible before they can be
added to an aggregate or a redundant interface.
When an interface is included in an aggregate interface, it is not listed on the

System > Network > Interface screen. You cannot configure the interface
individually and it is not available for inclusion in firewall policies, VIPs, IP pools, or
routing.

116 01-30007-0203-20090112
Figure 54: Settings for an 802.3ad aggregate interface
To create an 802.3ad Aggregate interface

2 Select Create New.
3 In the Name field, enter a name for the aggregated interface.
The interface name must be different from any other interface, zone or VDOM.
4 From the Type list, select 802.3ad Aggregate.
5 In the Available Interfaces list, select each interface that you want to include in the
aggregate interface and move it to the Selected Interfaces list.
6 If this interface operates in NAT/Route mode, you need to configure addressing
for it. For information about dynamic addressing, see:
• “Configuring DHCP on an interface” on page 118
• “Configuring an interface for PPPoE or PPPoA” on page 120
7 Configure other interface options as required.
8 Select OK.
Creating a redundant interface

You can combine two or more physical interfaces to provide link redundancy. This
feature allows you to connect to two or more switches to ensure connectivity in the
event one physical interface or the equipment on that interface fails.
In a redundant interface, traffic is only going over one interface at any time. This
differs from an aggregated interface where traffic is going over all interfaces for
increased bandwidth. This difference means redundant interfaces can have more
robust configurations with fewer possible points of failure. This is important in a
fully-meshed HA configuration.
FortiGate firmware on models 800 and higher implements redundant interfaces.
An interface is available to be in a redundant interface if:
• it is a physical interface, not a VLAN interface
• it is not already part of an aggregated or redundant interface
• it is in the same VDOM as the redundant interface
• it has no defined IP address and is not configured for DHCP or PPPoE
• it has no DHCP server or relay configured on it
• it does not have any VLAN subinterfaces

01-30007-0203-20090112 117
• it is not referenced in any firewall policy, VIP, IP Pool or multicast policy

• it is not monitored by HA
• it is not one of the FortiGate 5000 series backplane interfaces
Note: FortiGate-5000 backplane interfaces have to be made visible before they can be
added to an aggregate or a redundant interface.
When an interface is included in a redundant interface, it is not listed on the

System > Network > Interface page. You cannot configure the interface
individually and it is not available for inclusion in firewall policies, VIPs, IP pools, or
routing.
Figure 55: Settings for a redundant interface
To create a redundant interface

3 In the Name field, enter a name for the redundant interface.
The interface name must different from any other interface, zone or VDOM.
4 From the Type list, select Redundant Interface
5 In the Available Interfaces list, select each interface that you want to include in the
redundant interface and move it to the Selected Interfaces list.
In a failover situation, the interface activated will be the next interface down the
Selected Interfaces list.
6 If this interface operates in NAT/Route mode, you need to configure addressing
for it. For information about dynamic addressing, see:
• “Configuring DHCP on an interface” on page 118
• “Configuring an interface for PPPoE or PPPoA” on page 120
7 Configure other interface options as required.
8 Select OK.
Configuring DHCP on an interface

If you configure an interface to use DHCP, the FortiGate unit automatically
broadcasts a DHCP request. The interface is configured with the IP address and
any DNS server addresses and default gateway address that the DHCP server
provides.

118 01-30007-0203-20090112
To configure DHCP on an interface

3 In the Addressing mode section, select DHCP.
Figure 56: Interface DHCP settings
Figure 57: ADSL interface DHCP settings
Status Displays DHCP status messages as the FortiGate unit connects to

the DHCP server and gets addressing information. Select Status
to refresh the addressing mode status message.
Only displayed if you selected Edit.
Status can be one of:
• initializing - No activity.
• connecting - interface attempts to connect to the DHCP
server.
• connected - interface retrieves an IP address, netmask, and
other settings from the DHCP server.
• failed - interface was unable to retrieve an IP address and
other settings from the DHCP server.
Obtained The IP address and netmask leased from the DHCP server.
IP/Netmask Only displayed if Status is connected.
Renew Select to renew the DHCP license for this interface.
Only displayed if Status is connected.
Expiry Date The time and date when the leased IP address and netmask is no
longer valid.
Default The IP address of the gateway defined by the DHCP server.
Gateway Only displayed if Status is connected, and if Receive default
gateway from server is selected,.
Distance Enter the administrative distance for the default gateway retrieved
from the DHCP server. The administrative distance, an integer
from 1-255, specifies the relative priority of a route when there are
multiple routes to the same destination. A lower administrative
distance indicates a more preferred route. The default distance for
the default gateway is 1.

01-30007-0203-20090112 119
Retrieve default Enable Retrieve default gateway from server to retrieve a default
gateway from server gateway IP address from the DHCP server. The default gateway is
added to the static routing table.
Override internal DNS Enable Override internal DNS to use the DNS addresses retrieved
from the DHCP server instead of the DNS server IP addresses on
the DNS page.
On FortiGate models numbered 100 and lower, you should also
enable Obtain DNS server address automatically in System >
Network > Options. See “DNS Servers” on page 136.
When VDOMs are enabled, you can override the internal DNS
only on the management VDOM.
Connect to Server Enable Connect to Server so that the interface automatically
attempts to connect to a DHCP server. Disable this option if you
are configuring the interface offline.
Configuring an interface for PPPoE or PPPoA

If you configure the interface to use PPPoE or PPPoA, the FortiGate unit
automatically broadcasts a PPPoE or PPPoA request. When configuring the
FortiGate unit offline and you do not want the FortiGate unit to send the PPPoE or
PPPoA request, do not enable Connect to Server.
FortiGate units support many PPPoE RFC features (RFC 2516) including
unnumbered IPs, initial discovery timeout and PPPoE Active Discovery Terminate
(PADT).
PPPoA is only available on FortiGate models that support ADSL.
To configure an interface for PPPoE or PPPoA

3 In the Addressing mode section, select PPPoE or PPPoA.
Figure 58: Interface PPPoE settings

120 01-30007-0203-20090112
Figure 59: ADSL interface PPPoE or PPPoA settings
Status Displays PPPoE or PPPoA status messages as the FortiGate unit

connects to the PPPoE or PPPoA server and gets addressing
information. Select Status to refresh the addressing mode status
message.
Only displayed if you selected Edit.
Status can be one of the following 4 messages.
initializing No activity.
connecting The interface is attempting to connect to the PPPoE or PPPoA server.
connected The interface retrieves an IP address, netmask, and other settings
from the PPPoE server.
When the status is connected, PPPoE or PPPoA connection
information is displayed.
failed The interface was unable to retrieve an IP address and other
information from the PPPoE or PPPoA server.
Reconnect Select to reconnect to the PPPoE or PPPoA server.
User Name The PPPoE or PPPoA account user name.
Password The PPPoE or PPPoA account password.
Unnumbered IP Specify the IP address for the interface. If your ISP has assigned you a
block of IP addresses, use one of them. Otherwise, this IP address can
be the same as the IP address of another interface or can be any IP
address.
Initial Disc Enter Initial discovery timeout. Enter the time to wait before starting to
Timeout retry a PPPoE or PPPoA discovery.
Initial PADT Enter Initial PPPoE Active Discovery Terminate (PADT) timeout in
timeout seconds. Use this timeout to shut down the PPPoE or PPPoA session
if it is idle for this number of seconds. PADT must be supported by your
ISP. Set initial PADT timeout to 0 to disable.
Distance Enter the administrative distance for the default gateway retrieved from
the PPPoE or PPPoA server. The administrative distance, an integer
from 1-255, specifies the relative priority of a route when there are
multiple routes to the same destination. A lower administrative
distance indicates a more preferred route. The default distance for the
default gateway is 1.
Retrieve default Enable Retrieve default gateway from server to retrieve a default
gateway from gateway IP address from a PPPoE server. The default gateway is
server added to the static routing table.

01-30007-0203-20090112 121
Override internal Enable Override internal DNS to replace the DNS server IP addresses
DNS on the System DNS page with the DNS addresses retrieved from the
PPPoE or PPPoA server.
When VDOMs are enabled, you can override the internal DNS only on
the management VDOM.
Connect to server Enable Connect to Server so that the interface automatically attempts
to connect to a PPPoE or PPPoA server when you select OK or Apply.
Disable this option if you are configuring the interface offline.
Configuring Dynamic DNS on an interface

When the FortiGate unit has a static domain name and a dynamic public IP
address, you can use a DDNS service to update Internet DNS servers when the
IP address for the domain changes.
Dynamic DNS is available only in NAT/Route mode.
To configure DDNS on an interface

1 Get the DDNS configuration information from your DDNS service.
4 Enable DDNS.
5 Enter DDNS configuration information.
If at any time your Fortigate unit cannot contact the DDNS server, it will retry three
times at one minute intervals and then change to retrying at three minute intervals.
This is to prevent flooding the DDNS server.
Figure 60: DDNS service configuration
Server Select a DDNS server to use. The client software for these services is built
into the FortiGate firmware. The FortiGate unit can connect only to one of
these services.
Domain Enter the fully qualified domain name of the DDNS service.
Username Enter the user name to use when connecting to the DDNS server.
Password Enter the password to use when connecting to the DDNS server.
Configuring a virtual IPSec interface

You create a virtual IPSec interface by selecting IPSec Interface Mode in
VPN > IPSec > Auto Key or VPN > IPSec > Manual Key when you create a
VPN. You also select a physical or VLAN interface from the Local Interface list.
The virtual IPSec interface is listed as a subinterface of that interface in
System > Network > Interface. For more information, see
• “Overview of IPSec VPN configuration” on page 393
• “Auto Key” on page 395 or “Manual Key” on page 404
Go to System > Network > Interface and select Edit on an IPSec interface to:

122 01-30007-0203-20090112
• configure IP addresses for the local and remote endpoints of the IPSec
interface so that you can run dynamic routing over the interface or use ping to
test the tunnel
• enable administrative access through the IPSec interface
• enter a description for the interface
Figure 61: Virtual IPSec interface settings
Name The name of the IPSec interface.

Virtual Domain Select the VDOM of the IPSec interface.
IP If you want to use dynamic routing with the tunnel or be able to ping
Remote IP the tunnel interface, enter IP addresses for the local and remote
ends of the tunnel. These two addresses must not be used
anywhere else in the network.
Administrative Select the types of administrative access permitted on this
Access interface.
HTTPS Allow secure HTTPS connections to the web-based manager
through this interface.
PING Allow the interface to respond to pings. Use this setting to verify
your installation and for testing.
interface. HTTP connections are not secure and can be intercepted
by a third party.
SSH Allow SSH connections to the CLI through this interface.
connecting to this interface. See “Configuring SNMP” on page 176.
TELNET Allow Telnet connections to the CLI through this interface. Telnet
connections are not secure and can be intercepted by a third party.
Description Enter a description of the interface. It can be up to 63 characters.
Configuring interfaces with CLI commands

While nearly all types of interfaces can be configured from the GUI interface, a
few, such as loopback and soft switch interface, can only be configured using CLI
commands.
Virtual interfaces are not connected to any physical devices or cables outside the
FortiGate unit. They allow additional connections inside the FortiGate unit, which
allow for more complex configurations. Virtual interfaces also have the added
benefit of speed. Depending on the CPU load, virtual interfaces are consistently
faster than physical interfaces.

01-30007-0203-20090112 123
• Loopback interface
• Software switch interface
Loopback interface
A loopback interface is an ‘always up’ virtual interface that is not connected to any
other interfaces. Loopback interfaces connect to a Fortigate unit’s interface IP
address without depending on a specific external port.
A loopback interface is not connected to hardware, so it is not affected by
hardware problems. As long as the FortiGate unit is functioning, the loopback
interface is active. This ‘always up’ feature is useful in dynamic routing where the
Fortigate unit relies on remote routers and the local Firewall policies to access to
the loopback interface.
The CLI command to configure a loopback interface called loop1 with an IP
address of 10.0.0.10 is:
config system interface
edit loop1
set type loopback
set ip 10.0.0.10 255.255.255.0
end
For more information, see config system interface in the FortiGate CLI Reference.
Software switch interface

A software switch interface forms a simple bridge between two or more physical or
wireless FortiGate interfaces. The interfaces added to a soft switch interface are
called members. The members of a switch interface cannot be accessed as an
individual interface after being added to a soft switch interface. They are removed
from the system interface table.
Similar to aggregate interfaces, a soft switch interface functions like a normal
interface. A soft switch interface has one IP address. You create firewall policies to
and from soft switch interfaces and soft switch interfaces can be added to zones.
There are some limitations; soft switch interfaces cannot be monitored by HA or
used as HA heartbeat interfaces.
To add interfaces to a software switch group, no configuration settings can refer to
those interfaces. This includes default routes, VLANs, inter-VDOM links, and
policies. You can view available interfaces on the CLI when entering the ‘set
member’ command by using ‘?’ or <TAB> to scroll through the available list.
The CLI command to configure a software switch interface called soft_switch with
port1, external and dmz interfaces is:
config system switch-interface
edit soft_switch
set members port1 external dmz
end
For more information, see config system switch-interface in the FortiGate CLI
Reference.

124 01-30007-0203-20090112
Additional configuration for interfaces

Additional configuration for an interface consists of setting:
• Administrative access to an interface
• Interface MTU packet size
• Secondary IP Addresses
Administrative access to an interface

Administrative access is how an administrator can connect to the FortiGate unit to
view and change configuration settings. Two methods of administrative access
are HTTPS and SSH.
You can allow remote administration of the FortiGate unit running in NAT/Route
mode, but allowing remote administration from the Internet could compromise the
security of the FortiGate unit. You should avoid this unless it is required for your
configuration.
To improve the security of a FortiGate unit that allows remote administration from
the Internet:
• Use secure administrative user passwords.
• Change these passwords regularly.
• Enable secure administrative access to this interface using only HTTPS or
SSH.
• Do not change the system idle timeout from the default value of 5 minutes (see
“Settings” on page 215).
For more information on configuring administrative access in Transparent mode,
see “Operation mode and VDOM management access” on page 193.
To control administrative access to an interface

2 Choose an interface and select Edit.
3 Select the Administrative Access methods for the interface.
4 Select OK.
Interface MTU packet size

To improve network performance, you can change the maximum transmission unit
(MTU) of the packets that the FortiGate unit transmits. Ideally, the MTU should be
the same as the smallest MTU of all the networks between the FortiGate unit and
the destination of the packets. If the packets that the FortiGate unit sends are
larger than the smallest MTU, they are broken up or fragmented, which slows
down transmission. Experiment by lowering the MTU to find an MTU size for
optimum network performance.

01-30007-0203-20090112 125
FortiGate models numbered 3 000 and higher support jumbo frames - frames
larger than the traditional 1 500 bytes. Some models support a jumbo frame limit
of 9 000 bytes while others support 16 110 bytes. NP2-accelerated interfaces
support a jumbo frame limit of 16 000 bytes. FA2-accelerated interfaces do not
support jumbo frames. Jumbo frames are much larger than the maximum
standard Ethernet frames (packets) size of 1 500 bytes. As new Ethernet
standards have been implemented (such as Gigabit Ethernet), 1 500 byte frames
remain in the standard for backward compatibility.
To be able to send jumbo frames over a route, all Ethernet devices on that route
must support jumbo frames, otherwise your jumbo frames are not recognized and
are dropped.
If you have standard ethernet and jumbo frame traffic on the same interface,
routing alone cannot route them to different routes based only on frame size.
However you can use VLANs to make sure the jumbo frame traffic is routed over
network devices that support jumbo frames. VLANs will inherit the MTU size from
the parent interface. You will need to configure the VLAN to include both ends of
the route as well as all switches and routers along the route. For more information
on VLAN configurations, see the VLAN and VDOM guide.
To change the MTU size of the packets leaving an interface

2 Choose a physical interface and select Edit.
3 Below Administrative Access, select Override default MTU value (1 500).
4 Set the MTU size.
If you select an MTU size larger than your FortiGate unit supports, an error
message will indicate this. In this situation, try a smaller MTU size until the value is
supported. Supported maximums are 16 110, 9 000, and 1 500.
Note: If you change the MTU, you need to reboot the FortiGate unit to update the MTU
value of VLAN subinterfaces on the modified interface.
Note: In Transparent mode, if you change the MTU of an interface, you must change the
MTU of all interfaces to match the new MTU.
Secondary IP Addresses
An interface can be assigned more than one IP address. You can create and apply
separate firewall policies for each IP address on an interface. You can also
forward traffic and use RIP or OSPF routing with secondary IP addresses.
There can be up to 32 secondary IP addresses per interface including primary,
secondary, and any other IP addresses assigned to the interface. Primary and
secondary IP addresses can share the same ping generator.
The following restrictions must be in place before you are able to assign a
secondary IP address:
• A primary IP address must be assigned to the interface.
• The interface must use manual addressing mode.
• By default, IP addresses cannot be part of the same subnet. To allow interface
subnet overlap use the CLI command:

126 01-30007-0203-20090112
config system global

(global)# set allow-interface-subnet-overlap enable
(global)#end
You can use the CLI command config system interface to add a
secondary IP address to an interface. For more information, see config
secondaryip under system interface in the FortiGate CLI Reference.
Figure 62: Adding Secondary IP Addresses
IP/Netmask Enter the IP address/subnet mask in the IP/Netmask field.

The Secondary IP address must be on a different subnet than the
Primary IP address.
This field is only available in Manual addressing mode.
Ping Server To enable dead gateway detection, enter the IP address of the
next hop router on the network connected to the interface and
select Enable. See “Dead gateway detection” on page 137.
Multiple addresses can share the same ping server.
Administrative Select the types of administrative access permitted on the
Access secondary IP. These can be different from the primary address.
HTTPS Allow secure HTTPS connections to the web-based manager
through this secondary IP.
PING Allow secondary IP to respond to pings. Use this setting to verify
your installation and for testing.
secondary IP. HTTP connections are not secure and can be
intercepted by a third party.
SSH Allow SSH connections to the CLI through this secondary IP.
connecting to this secondary IP. See “Configuring SNMP” on
page 176.
TELNET Allow Telnet connections to the CLI through this secondary IP.
Telnet connections are not secure and can be intercepted by a
third party.
Add Select Add to add the configured secondary IP address to the
secondary IP table.
Addresses in this table are not added to the interface until you
select OK or Apply.
Secondary IP table A table that displays all the secondary IP addresses that have
been added to this interface.
These addresses are not permanently added to the interface until
you select OK or Apply..
# The identifying number of the secondary IP address.
IP/Netmask The IP address and netmask for the secondary IP.
Ping Server The IP address of the ping server for the address. The ping
server can be shared by multiple addresses.

01-30007-0203-20090112 127
Configuring zones System Network
Enable Indicates if the ping server option is selected.

Access The administrative access methods for this address. They can be
different from the primary IP address.
Delete Icon Select to remove this secondary IP entry.
Note: It is recommended that after adding a secondary IP, you refresh the secondary IP
table and verify your new address is listed. If not, one of the restrictions (have a primary IP
address, use manual addressing mode, more than one IP on the same subnet, more than
32 IP addresses assigned to the interface, etc.) prevented the address from being added.
Configuring zones
Grouping interfaces and VLAN subinterfaces into zones simplifies policy creation.
You can configure policies for connections to and from a zone, but not between
interfaces in a zone.
You can add zones, rename and edit zones, and delete zones from the zone list.
When you add a zone, you select the names of the interfaces and VLAN
subinterfaces to add to the zone.
Zones are configured from virtual domains. If you have added multiple virtual
domains to your FortiGate configuration, make sure you are configuring the
correct virtual domain before adding or editing zones.
Figure 63: Zone list
Create New Select Create New to create a new zone.

Name Names of the zones.
Block intra-zone Displays Yes if traffic between interfaces in the same zone is blocked
traffic and No if traffic between interfaces in the same zone is not blocked.
Interface Members Names of the interfaces added to the zone. Interface names depend
on the FortiGate model.
Edit/View icons Edit or view a zone.
Delete icon Delete a zone.
To configure zone settings

1 Go to System > Network > Zone.
2 Select Create New or select the Edit icon for a zone.
3 Select name, and interfaces.
4 Select OK.

128 01-30007-0203-20090112
System Network Configuring the modem interface
Figure 64: Zone settings
Zone Name Enter the name to identify the zone.

Block intra-zone Select Block intra-zone traffic to block traffic between interfaces or
traffic VLAN subinterfaces in the same zone.
Interface members Select the interfaces that are part of this zone. This list includes
configured VLANs.
Configuring the modem interface

All FortiGate models with a USB interface support USB modems, and FortiGate-
50 series and FortiGate-60 series modules include a serial modem port. In
NAT/Route mode the modem can be in one of two modes:
• In redundant (backup) mode, the modem interface automatically takes over
from a selected ethernet interface when that ethernet interface is unavailable.
• In standalone mode, the modem interface is the connection from the FortiGate
unit to the Internet.
In redundant or standalone mode when connecting to the ISP, you can configure
the FortiGate unit to automatically have the modem dial up to three dialup
accounts until the modem connects to an ISP.
FortiGate models 50AM, 60M have a built-in modem. For these models, you can
configure modem operation in the web-based manager. See “Configuring modem
settings”.
Other models can connect to an external modem through a USB-to-serial
converter. For these models, you must configure modem operation using the CLI.
Initially modem interfaces are disabled, and must be enabled in the CLI to be
visible in the web-based manager. See the system modem command in the
Note: The modem interface is not the AUX port. While the modem and AUX port may
appear similar, the AUX port has no associated interface and is used for remote console
connection. The AUX port is only available on FortiGate models 1000A, 1000AFA2, and
3000A. For more information, see the config system aux command in the FortiGate
CLI Reference.

• Configuring modem settings
• Redundant mode configuration
• Standalone mode configuration

01-30007-0203-20090112 129
Configuring the modem interface System Network
• Adding firewall policies for modem connections

• Connecting and disconnecting the modem
• Checking modem status
Configuring modem settings

Configure modem settings so that the FortiGate unit uses the modem to connect
to your ISP dialup accounts. You can configure up to three dialup accounts, select
standalone or redundant operation, and configure how the modem dials and
disconnects.
If VDOMs are enabled, the modem can be assigned to one of the VDOMs just like
the other interfaces.
If the modem is disabled it will not appear in the interface list, and must be
enabled from the CLI using:
config system modem
set status enable
end
Note: You cannot configure and use the modem in Transparent mode.
Figure 65 shows the only the settings specific to standalone mode. The remaining
settings are common to both standalone and redundant modes and are shown in
Figure 66.
Figure 65: Modem settings (Standalone)

130 01-30007-0203-20090112
Figure 66: Modem settings (Redundant)
Enable Modem Select to enable the FortiGate modem.

Modem status Modem status can be: not active, connecting, connected,
disconnecting, or hung up.
Dial Now/Hang Up (Standalone mode only) Select Dial Now to manually connect to a
dialup account. If the modem is connected, you can select Hang
Up to manually disconnect the modem.
Mode Select Standalone or Redundant mode.
Auto-dial Select to dial the modem automatically if the connection is lost or
(Standalone mode) the FortiGate unit is restarted.
You cannot select Auto-dial if Dial on demand is selected.
Dial on demand Select to dial the modem when packets are routed to the modem
(Standalone mode) interface. The modem disconnects after the idle timeout period if
there is no network activity.
You cannot select Dial on demand if Auto-dial is selected.
Idle timeout Enter the timeout duration in minutes. After this period of inactivity,
(Standalone mode) the modem disconnects.
Redundant for Select the ethernet interface for which the modem provides backup
(Redundant mode) service.
Holddown (Redundant mode only) Enter the time (1-60 seconds) that the
Timer FortiGate unit waits before switching back to the primary interface
(Redundant mode) from the modem interface, after the primary interface has been
restored. The default is 1 second. Configure a higher value if you
find the FortiGate unit switching repeatedly between the primary
interface and the modem interface.

01-30007-0203-20090112 131
Redial Limit The maximum number of times (1-10) that the FortiGate unit
modem attempts to reconnect to the ISP if the connection fails. The
default redial limit is 1. Select None to have no limit on redial
attempts.
Wireless Modem Display a connected wireless modem if available.
Supported Modems Select to view a list of supported modems.
Usage History Display connections made on the modem interface. Information
displayed about connections includes:
• date and time
• duration of the connection in hours, minutes, and
seconds
• IP address connected to
• traffic statistics including received, sent, and total
• current status of the connection
Dialup Account Configure up to three dialup accounts. The FortiGate unit tries
connecting to each account in order until a connection can be
established.
The active dialup account is indicated with a green check mark.
Phone Number The phone number required to connect to the dialup account. Do
not add spaces to the phone number. Make sure to include
standard special characters for pauses, country codes, and other
functions as required by your modem to connect to your dialup
account.
User Name The user name (maximum 63 characters) sent to the ISP.
Password The password sent to the ISP.
To configure the modem in Redundant mode, see “Redundant mode
configuration” on page 132.
To configure the modem in Standalone mode, see “Standalone mode
Redundant mode configuration

In redundant mode the modem interface backs up a selected ethernet interface. If
that ethernet interface disconnects from its network, the modem automatically
dials the configured dialup accounts. When the modem connects to a dialup
account, the FortiGate unit routes IP packets normally destined for the selected
ethernet interface to the modem interface.
The FortiGate unit disconnects the modem interface and switches back to the
ethernet interface when the ethernet interface is able to connect to its network.
You can set a holddown timer that delays the switch back to the ethernet interface
to ensure it is stable and fully active before switching the traffic.
The modem will disconnect after a period of network inactivity set by the value in
idle timeout. This saves money on dialup connection charges.
For the FortiGate unit to be able to switch from an ethernet interface to the
modem, you must select the name of the interface in the modem configuration
and configure a ping server for that interface. You must also configure firewall
policies for connections between the modem interface and other FortiGate
interfaces.
Note: Do not add policies for connections between the modem interface and the ethernet
interface that the modem is backing up.

132 01-30007-0203-20090112
To configure redundant mode

1 Go to System > Network > Modem.
2 Select Redundant mode.
3 Enter the following information:
Redundant for From the list, select the interface to back up.
Holddown timer Enter the number of seconds to continue using the modem after the
network connectivity is restored.
Redial Limit Enter the maximum number of times to retry if the ISP does not
answer.
Dialup Account 1 Enter the ISP phone number, user name and password for up to
Dialup Account 2 three dialup accounts.
Dialup Account 3
4 Select Apply.
5 Configure a ping server for the ethernet interface the modem backs up.
See “To add a ping server to an interface” on page 137.
6 Configure firewall policies for network connectivity through the modem interface.
See “Adding firewall policies for modem connections” on page 134.
Standalone mode configuration

In standalone mode, the modem connects to a dialup account to provide a
connection to the Internet. You can configure the modem to dial when the
FortiGate unit restarts or when there are unrouted packets. You can also hang up
or redial the modem manually.
If the connection to the dialup account fails, the FortiGate unit will redial the
modem. The modem redials the number of times specified by the redial limit, or
until it connects to a dialup account.
The modem will disconnect after a period of network inactivity set by the value in
idle timeout. This saves money on dialup connection charges.
You must configure firewall policies for connections between the modem interface
and other FortiGate interfaces.
You must also go to Router > Static to configure static routes to route traffic to the
modem interface. For example, if the modem interface is acting as the FortiGate
unit external interface you must set the device setting of the FortiGate unit default
route to modem.
To configure standalone mode

2 Select standalone mode.
Auto-dial Select if you want the modem to dial when the FortiGate unit restarts.
Dial on demand Select if you want the modem to connect to its ISP whenever there
are unrouted packets.
Idle timeout Enter the timeout duration in minutes. After this period of inactivity,
the modem disconnects.

01-30007-0203-20090112 133
Redial Limit Enter the maximum number of times to retry if the ISP does not
answer.
Dialup Account 1 Enter the ISP phone number, user name and password for up to
Dialup Account 2 three dialup accounts.
Dialup Account 3
4 Select Apply.
5 Configure firewall policies for network connectivity through the modem interface.
See “Adding firewall policies for modem connections” on page 134.
6 Go to Router > Static and set device to modem to configure static routes to route
traffic to the modem interface.
See “Adding a static route to the routing table” on page 262.
Adding firewall policies for modem connections

The modem interface requires firewall addresses and policies. You can add one or
more addresses to the modem interface. For information about adding addresses,
see “Configuring addresses” on page 317.
You can configure firewall policies to control the flow of packets between the
modem interface and the other interfaces on the FortiGate unit. For information on
configuring firewall policies, see “Configuring firewall policies” on page 297.
Connecting and disconnecting the modem
Note: The modem must be in Standalone mode before connecting or disconnecting from a
dialup account.
To connect to a dialup account

2 Select Enable USB Modem.
3 Verify the information in Dialup Accounts.
4 Select Apply.
5 Select Dial Now.
The FortiGate unit dials into each dialup account in turn until the modem connects
to an ISP.
To disconnect from a dialup account

2 Select Hang Up to disconnect the modem.
Checking modem status

You can determine the connection status of your modem and which dialup
account is active. If the modem is connected to the ISP, you can see the IP
address and netmask.
To check the modem status, go to System > Network > Modem.
Modem status is one of the following:

134 01-30007-0203-20090112
System Network Configuring Networking Options
not active The modem is not connected to the ISP.

connecting The modem is attempting to connect to the ISP.
connected The modem is connected to the ISP.
disconnecting The modem is disconnecting from the ISP.
hung up The modem has disconnected from the ISP. (Standalone mode only)
The modem will not redial unless you select Dial Now.
A green check mark indicates the active dialup account.

The IP address and netmask assigned to the modem interface appears on the
System Network Interface screen of the web-based manager.
Configuring Networking Options

Network options include DNS server and dead gateway detection settings.
To configure network options

1 Go to System > Network > Options
2 Enter primary and secondary DNS servers.
3 Enter local domain name.
4 Enter Dead Gateway Detection settings.
5 Select OK.
Figure 67: Configuring Networking Options - FortiGate models 200 and higher

01-30007-0203-20090112 135
Configuring Networking Options System Network
Figure 68: Configuring Networking Options - FortiGate models 100 and lower
Obtain DNS server address This option applies only to FortiGate models 100 and
automatically lower.
Select to obtain the DNS server IP address when DHCP is
used on an interface, also obtain the DNS server IP
address. Available only in NAT/Route mode. You should
also enable Override internal DNS in the DHCP settings of
the interface. See “Configuring DHCP on an interface” on
page 118.
Use the following DNS server This option applies only to FortiGate models 100 and
addresses lower.
Use the specified Primary and Secondary DNS server
addresses.
Primary DNS Server Enter the primary DNS server IP address.
Secondary DNS Server Enter the secondary DNS server IP address.
Local Domain Name Enter the domain name to append to addresses with no
domain portion when performing DNS lookups.
Enable DNS forwarding from This option applies only to FortiGate models 100 and
lower operating in NAT/Route mode.
Select the interfaces that forward DNS requests they
receive to the DNS servers that you configured.
Dead Gateway Detection Dead gateway detection confirms connectivity using a
ping server added to an interface configuration. For
information about adding a ping server to an interface, see
“Dead gateway detection” on page 137.
Detection Interval Enter a number in seconds to specify how often the
FortiGate unit pings the target.
Fail-over Detection Enter the number of times that the ping test fails before
the FortiGate unit assumes that the gateway is no longer
functioning.
DNS Servers
Several FortiGate functions use DNS, including alert email and URL blocking. You
can specify the IP addresses of the DNS servers to which your FortiGate unit
connects. DNS server IP addresses are usually supplied by your ISP.

136 01-30007-0203-20090112
System Network Routing table (Transparent Mode)
You can configure FortiGate models numbered 100 and lower to obtain DNS
server addresses automatically. To obtain these addresses automatically, at least
one FortiGate unit interface must use the DHCP or PPPoE addressing mode. See
“Configuring DHCP on an interface” on page 118 or “Configuring an interface for
PPPoE or PPPoA” on page 120.
FortiGate models 100 and lower can provide DNS Forwarding on their interfaces.
Hosts on the attached network use the interface IP address as their DNS server.
DNS requests sent to the interface are forwarded to the DNS server addresses
that you configured or that the FortiGate unit obtained automatically.
Dead gateway detection

Dead gateway detection periodically pings a ping server to confirm network
connectivity. Typically, the ping server is the next-hop router that leads to an
external network or the Internet. The ping period (Detection Interval) and the
number of failed pings that is considered to indicate a loss of connectivity (Fail-
over Detection) are set in System > Network > Options.
To apply dead gateway detection to an interface, you must configure a ping server
on it.
To add a ping server to an interface

2 Choose an interface and select Edit.
3 Set Ping Server to the IP address of the next hop router on the network.
4 Select Enable.
5 Select OK.
Routing table (Transparent Mode)

In NAT/Route mode the static routing table is located at System > Routing >
Static, but in Transparent Mode that static routing table is located at System >
Network > Routing Table.
Adding a static route in Transparent Mode

1 Ensure your FortiGate unit is in Transparent mode. For more details see
“Changing operation mode” on page 193.
2 Go to System > Network > Routing Table.
3 Select Create New to add a static route.
Figure 69: Static routing table - Transparent Mode
Create New Add a new static route.

# Position of the route in the routing table.
IP The destination IP address for the route.

01-30007-0203-20090112 137
VLAN overview System Network
Mask The netmask for the route.

Gateway The IP address of the next hop router to which the route directs traffic.
Distance The administration distance or relative preferability of the route. An
administration distance of 1 is most preferred.
Delete icon Remove a route.
View/edit icon Edit or view a route.
Move To icon Change the position of a route in the list.
Transparent mode route settings

Configuring a static route in Transparent mode
1 Go to System > Network > Routing Table
2 Select Create New to add a route.
You can also select the Edit icon of an existing route to modify it.
3 Enter the destination IP and netmask.
4 Enter the gateway.
5 Enter the administrative distance.
6 Select OK.
Figure 70: Transparent mode route settings
Destination IP Enter the destination IP address and netmask for the route.
/Mask To create a default route, set the Destination IP and Mask to 0.0.0.0.
Gateway Enter the IP address of the next hop router to which the route directs
traffic. For an Internet connection, the next hop routing gateway routes
traffic to the Internet.
Distance The administration distance or relative preferability of the route. An
administration distance of 1 is most preferred.
VLAN overview
A VLAN is group of PCs, servers, and other network devices that communicate as
if they were on the same LAN segment, regardless of their location. For example,
the workstations and servers for an accounting department could be scattered
throughout an office or city and connected to numerous network segments, but
still belong to the same VLAN.
A VLAN segregates devices logically instead of physically. Each VLAN is treated
as a broadcast domain. Devices in VLAN 1 can connect with other devices in
VLAN 1, but cannot connect with devices in other VLANs. The communication
among devices on a VLAN is independent of the physical network.

138 01-30007-0203-20090112
System Network VLANs in NAT/Route mode
A VLAN segregates devices by adding 802.1Q VLAN tags to all of the packets
sent and received by the devices in the VLAN. VLAN tags are 4-byte frame
extensions that contain a VLAN identifier as well as other information.
For more information on VLANs, see the FortiGate VLANs and VDOMs Guide.
Figure 71: Basic VLAN topology
Internet
Untagged packets
Router
VL AN 1
VL AN 2
VL AN 1 VL AN 2
VLAN Switch
VL AN 1 Network VL AN 2 Network
FortiGate units and VLANs

In a typical VLAN configuration, 802.1Q-compliant VLAN layer-2 switches or
layer-3 routers or firewalls add VLAN tags to packets. Packets passing between
devices in the same VLAN are normally handled by layer-2 switches but can be
handled by layer-3 devices. Packets passing between devices in different VLANs
must be handled by a layer-3 device such as router, firewall, or layer-3 switch.
Using VLANs, a single FortiGate unit can provide security services and control
connections between multiple security domains. Traffic from each security domain
is given a different VLAN ID. The FortiGate unit can recognize VLAN IDs and
apply security policies to secure network and IPSec VPN traffic between security
domains. The FortiGate unit can also apply policies, protection profiles, and other
firewall features for network and VPN traffic that is allowed to pass between
security domains.
VLANs in NAT/Route mode

Operating in NAT/Route mode, the FortiGate unit functions as a layer-3 device to
control the flow of packets between VLANs. The FortiGate unit can also remove
VLAN tags from incoming VLAN packets and forward untagged packets to other
networks, such as the Internet.

01-30007-0203-20090112 139
VLANs in NAT/Route mode System Network
FortiGate units in NAT/Route mode can use VLANs for constructing VLAN trunks
between an IEEE 802.1Q-compliant switch (or router) and the FortiGate units.
Normally the FortiGate unit internal interface connects to a VLAN trunk on an
internal switch, and the external interface connects to an upstream Internet router.
The FortiGate unit can then apply different policies for traffic on each VLAN that
connects to the internal interface.
When constructing VLAN trunks, you add VLAN subinterfaces that have VLAN
IDs that match the VLAN IDs of packets in the VLAN trunk to the FortiGate internal
interface. If the IDs don’t match, traffic will not be delivered. The FortiGate unit
directs packets with VLAN IDs to subinterfaces with matching VLAN IDs. For
example packets from the sending system VLAN ID#101 are delivered to the
recipient system’s VLAN ID#101.
You can also define VLAN subinterfaces on all FortiGate interfaces. The FortiGate
unit can add VLAN tags to packets leaving a VLAN subinterface or remove VLAN
tags from incoming packets and add different VLAN tags to outgoing packets.
Rules for VLAN IDs

In NAT/Route mode, two VLAN subinterfaces added to the same physical
interface cannot have the same VLAN ID. However, you can add two or more
VLAN subinterfaces with the same VLAN IDs to different physical interfaces.
There is no internal connection or link between two VLAN subinterfaces with same
VLAN ID. Their relationship is the same as the relationship between any two
FortiGate network interfaces.
Rules for VLAN IP addresses

IP addresses of all FortiGate interfaces cannot overlap. That is, the IP addresses
of all interfaces must be on different subnets. This rule applies to both physical
interfaces and to VLAN subinterfaces.
Note: If you are unable to change your existing configurations to prevent IP overlap, enter
the CLI command config system global and set allow-interface-subnet-
overlap enable to allow IP address overlap. If you enter this command, multiple VLAN
interfaces can have an IP address that is part of a subnet used by another interface. This
command is recommended for advanced users only.
Figure 61 shows a simplified NAT/Route mode VLAN configuration. In this

configuration, the FortiGate internal interface connects to a VLAN switch using an
802.1Q trunk and is configured with two VLAN subinterfaces (VLAN 100 and
VLAN 200). The external interface connects to the Internet. The external interface
is not configured with VLAN subinterfaces.
When the VLAN switch receives packets from VLAN 100 and VLAN 200, it applies
VLAN tags and forwards the packets to local ports and across the trunk to the
FortiGate unit. The FortiGate unit is configured with policies that allow traffic to
flow between VLANs and from the VLANs to the external network.

140 01-30007-0203-20090112
System Network VLANs in NAT/Route mode
Figure 72: FortiGate unit in NAT/Route mode
Internet
Untagged packets
External 172.16.21.2
FortiGate unit
Internal 192.168.110.126
802.1Q
trunk
Fa 0/24
Fa 0/3 Fa 0/9
VLAN 100 VLAN Switch VLAN 200
VLAN 100 Network VLAN 200 Network

10.1.1.0 10.1.2.0
Adding VLAN subinterfaces

The VLAN ID of each VLAN subinterface must match the VLAN ID added by the
IEEE 802.1Q-compliant router. The VLAN ID can be any number between 1 and
4094, as 0 and 4095 are reserved. Each VLAN subinterface must also be
configured with its own IP address and netmask.
VLAN subinterfaces to the physical interface that receives VLAN-tagged packets.
Note: A VLAN must not have the same name as a virtual domain or zone. A VLAN can not
be added to a switch interface. See “Switch Mode” on page 111.
To add a VLAN subinterface in NAT/Route mode

2 Select Create New to add a VLAN subinterface.
3 Enter a Name to identify the VLAN subinterface.
4 Select the physical interface that receives the VLAN packets intended for this
VLAN subinterface.
5 Enter the VLAN ID that matches the VLAN ID of the packets to be received by this
VLAN subinterface.
6 If you are an administrator with a super-admin profile, you can create VLAN
subinterfaces for any virtual domain. If not, you can only create VLAN
subinterfaces in your own VDOM.
See “Using virtual domains” on page 95 for information about virtual domains.
7 Configure the VLAN subinterface settings.
See “Interface settings” on page 112.

01-30007-0203-20090112 141
VLANs in Transparent mode System Network
8 Select OK.
The FortiGate unit adds the new VLAN subinterface to the interface that you
selected in step 4.
To add firewall policies for a VLAN subinterface

After you add a VLAN subinterface you can add firewall policies for connections
between a VLAN subinterface or from a VLAN subinterface to a physical interface.
1 Go to Firewall > Address.
2 Select Create New to add firewall addresses that match the source and
destination IP addresses of VLAN packets.
See “About firewall addresses” on page 315.
3 Go to Firewall > Policy.
4 Configure firewall policies as required.
VLANs in Transparent mode

In Transparent mode, the FortiGate unit can apply firewall policies and services,
such as authentication, protection profiles, and other firewall features, to traffic on
an IEEE 802.1 VLAN trunk. You can insert the FortiGate unit into the trunk without
making changes to the network. In a typical configuration, the FortiGate internal
interface accepts VLAN packets on a VLAN trunk from a VLAN switch or router
connected to internal VLANs. The FortiGate external interface forwards tagged
packets through the trunk to an external VLAN switch or router that can be
connected to the Internet. The FortiGate unit can be configured to apply different
policies for traffic on each VLAN in the trunk.
For VLAN traffic to be able to pass between the FortiGate internal and external
interface you add a VLAN subinterface to the internal interface and another VLAN
subinterface to the external interface. If these VLAN subinterfaces have the same
VLAN IDs, the FortiGate unit applies firewall policies to the traffic on this VLAN. If
these VLAN subinterfaces have different VLAN IDs, or if you add more than two
VLAN subinterfaces, you can also use firewall policies to control connections
between VLANs.
If the network uses IEEE 802.1 VLAN tags to segment your network traffic, you
can configure a FortiGate unit to provide security for network traffic passing
between different VLANs. To support VLAN traffic in Transparent mode, you add
virtual domains to the FortiGate unit configuration. A virtual domain consists of two
or more VLAN subinterfaces or zones. In a virtual domain, a zone can contain one
or more VLAN subinterfaces.
When the FortiGate unit receives a VLAN tagged packet at an interface, the
packet is directed to the VLAN subinterface with the matching VLAN ID. The
VLAN subinterface removes the VLAN tag and assigns a destination interface to
the packet based on its destination MAC address. The firewall policies for the
source and destination VLAN subinterface pair are applied to the packet. If the
packet is accepted by the firewall, the FortiGate unit forwards the packet to the
destination VLAN subinterface. The destination VLAN ID is added to the packet by
the FortiGate unit and the packet is sent to the VLAN trunk.

142 01-30007-0203-20090112
System Network VLANs in Transparent mode
Note: There is a maximum of 255 interfaces total allowed per VDOM in Transparent mode.
This includes VLANs. If no other interfaces are configured for a VDOM, you can configure
up to 255 VLANs in that VDOM.
Figure 73 shows a FortiGate unit operating in Transparent mode with 2 virtual

domains and configured with three VLAN subinterfaces.
Figure 73: FortiGate unit with two virtual domains in Transparent mode
FortiGate unit
VLAN1
Internal root virtual domain External
VLAN1 VLAN1
VLAN2 VLAN1 VLAN1 VLAN2
VLAN3 VLAN3 Internet
VLAN2
VLAN New virtual domain VLAN
trunk trunk VLAN Switch
VLAN2 VLAN2 or router
VLAN Switch VLAN3 VLAN3
or router
VLAN3
Figure 74 shows a FortiGate unit operating in Transparent mode and configured

with three VLAN subinterfaces. In this configuration, the FortiGate unit would
provide virus scanning, web content filtering, and other services to each VLAN.
Figure 74: FortiGate unit in Transparent mode
Internet
Router
Untagged packets
VLAN Switch
VL AN 1
VLAN Trunk VL AN 2
VL AN 3
FortiGate unit
in Transparent mode
VL AN 1
VLAN Trunk VL AN 2
VL AN 3
VLAN Switch
VL AN 1 VL AN 2 VL AN 3
VL AN 1 Network VL AN 2 Network VL AN 3 Network

01-30007-0203-20090112 143
Rules for VLAN IDs

In Transparent mode, two VLAN subinterfaces added to the same physical
interface cannot have the same VLAN ID. However, you can add two or more
VLAN subinterfaces with the same VLAN IDs to different physical interfaces.
There is no internal connection or link between two VLAN subinterfaces with the
same VLAN ID. Their relationship is the same as the relationship between any two
FortiGate network interfaces.
Note: There is a maximum of 255 VLANs allowed per interface in Transparent mode.
Transparent mode virtual domains and VLANs

VLAN subinterfaces are added to and associated with virtual domains. By default
the FortiGate configuration includes one virtual domain, named root, and you can
add as many VLAN subinterfaces as you require to this virtual domain.
You can add more virtual domains if you want to separate groups of VLAN
subinterfaces into virtual domains. For information on adding and configuring
virtual domains, see “Using virtual domains” on page 95
Adding a VLAN subinterface in Transparent mode
Note: A VLAN must not have the same name as a virtual domain or zone.

2 Select Create New to add a VLAN subinterface.
3 Enter a Name to identify the VLAN subinterface.
4 Select the physical interface that receives the VLAN packets intended for this
VLAN subinterface.
5 Enter the VLAN ID that matches the VLAN ID of the packets to be received by this
VLAN subinterface.
6 Select which virtual domain to add this VLAN subinterface to.
See “Using virtual domains” on page 95 for information about virtual domains.
7 Configure the administrative access, and log settings.
See “Interface settings” on page 112 for more descriptions of these settings.
8 Select OK.
The FortiGate unit adds the new subinterface to the interface that you selected in
step 4.
9 Select Bring up to activate the VLAN subinterface.

144 01-30007-0203-20090112
System Network VLANs in Transparent mode
To add firewall policies for a VLAN subinterface

After you add a VLAN subinterface, you can add firewall policies for connections
between VLAN subinterfaces or from a VLAN subinterface to a physical interface.
2 Select Create New to add firewall addresses that match the source and
destination IP addresses of VLAN packets.
See “About firewall addresses” on page 315.
4 Add firewall policies as required.
Troubleshooting ARP Issues

Address Resolution Protocol (ARP) traffic is vital to communication on a network
and is enabled on FortiGate interfaces by default. Normally ARP packets to pass
through the FortiGate unit, especially if it is sitting between a client and a server or
between a client and a router.
Duplicate ARP packets

ARP traffic can cause problems such as duplicate ARP packets making the
recipient device think the packets originated from two different device, which is
generally an attempt to hack into the network.
This is true especially in Transparent mode where ARP packets arriving on one
interface are sent to all other interfaces, including VLAN subinterfaces. Some
Layer 2 switches become unstable when they detect the same MAC address
originating on more than one switch interface or from more than one VLAN. This
instability can occur if the Layer 2 switch does not maintain separate MAC
address tables for each VLAN. Unstable switches may reset causing network
traffic to slow down.
ARP Forwarding
One solution to the duplicate ARP packet problem is to enable ARP forwarding.
When ARP forwarding is enabled, the Fortigate unit allows duplicate ARP packets
that resolve the delivery problems caused by duplicate ARP packets. However,
this also opens up your network to potential hacking attempts that spoof packets.
For more secure solutions, see the FortiGate VLANs and VDOMs Guide.

01-30007-0203-20090112 145

146 01-30007-0203-20090112
System Wireless FortiWiFi wireless interfaces
System Wireless
This section describes how to configure the Wireless LAN interfaces on FortiWiFi
units. The majority of this section is applicable to all FortiWiFi units. Where
indicated, some features may not be available on the FortiWiFi-60.
If you enable virtual domains (VDOMs) on the FortiGate unit, MAC filters and
wireless monitor are configured separately for each virtual domain. System
wireless settings are configured globally. For details, see “Using virtual domains”
on page 95.
• FortiWiFi wireless interfaces
• Channel assignments
• System wireless settings
• FortiWiFi-60 system wireless settings
• Wireless MAC Filter
• Wireless Monitor
FortiWiFi wireless interfaces

FortiWiFi units (except the FortiWiFi-60) support up to four wireless interfaces and
four different SSIDs. Each wireless interface should have a different SSID and
each wireless interface can have different security settings. For details on adding
wireless interfaces, see “Adding a wireless interface” on page 152.
You can configure the FortiWiFi unit to:
• Provide an access point that clients with wireless network cards can connect
to. This is called Access Point mode, which is the default mode. All FortiWiFi
units except the FortiWiFi-60 can have up to 4 wireless interfaces.
or
• Connect the FortiWiFi unit to another wireless network. This is called Client
mode. A FortiWiFi unit operating in client mode can also can only have one
wireless interface.
FortiWiFi units support the following wireless network standards:
• IEEE 802.11a (5-GHz Band) (FortiWiFi-60A and FortiWiFi-60B)
• IEEE 802.11b (2.4-GHz Band)
• IEEE 802.11g (2.4-GHz Band)
• WEP64 and WEP128 Wired Equivalent Privacy (WEP)
• Wi-Fi Protected Access (WPA), WPA2 and WPA2 Auto using pre-shared keys
or RADIUS servers

01-30007-0203-20090112 147
Channel assignments System Wireless
Channel assignments
Depending on the wireless protocol selected, you have specific channels available
to you, depending on what region of the world you are in. Set the channel for the
wireless network by going to System > Wireless > Settings. For more
information see “System wireless settings” on page 150.
The following tables list the channel assignments for wireless networks for each
supported wireless protocol.
• IEEE 802.11a channel numbers
• IEEE 802.11b channel numbers
• IEEE 802.11g channel numbers
IEEE 802.11a channel numbers

Table 7 lists IEEE 802.11a channels supported for FortiWiFi products that support
the IEEE 802.11a wireless standard. 802.11a is only available on the
FortiWiFi-60A and FortiWiFi-60B units.
All channels are restricted to indoor usage except the Americas, which allows for
indoor and outdoor use on channels 52 through 64 in the United States.
Table 7: IEEE 802.11a (5-GHz Band) channel numbers
Channel Frequency Regulatory Areas

number (MHz) Americas Europe Taiwan Singapore Japan
34 5170 • •
36 5180 • • •
38 5190 • •
40 5200 • • •
42 5210 • •
44 5220 • • •
46 5230 • •
48 5240 • • •
52 5260 • • •
56 5280 • • •
60 5300 • • •
64 5320 • • •
149 5745
153 5765
157 5785
161 5805

148 01-30007-0203-20090112
System Wireless Channel assignments
IEEE 802.11b channel numbers

Table 8 lists IEEE 802.11b channels. All FortiWiFi units support 802.11b.
Mexico is included in the Americas regulatory domain. Channels 1 through 8 are
for indoor use only. Channels 9 through 11 can be used indoors and outdoors. You
must make sure that the channel number complies with the regulatory standards
of Mexico.
Table 8: IEEE 802.11b (2.4-Ghz Band) channel numbers
Channel Frequency Regulatory Areas

number (MHz) Americas EMEA Israel Japan
1 2412 • • •
2 2417 • • •
3 2422 • • •
4 2427 • • • •
5 2432 • • • •
6 2437 • • • •
7 2442 • • • •
8 2447 • • • •
9 2452 • • • •
10 2457 • • • •
11 2462 • • •
12 2467 • •
13 2472 • •
14 2484 •

01-30007-0203-20090112 149
System wireless settings System Wireless
IEEE 802.11g channel numbers

Table 9 lists IEEE 802.11b channels. All FortiWiFi products support 802.11g.
Table 9: IEEE 802.11g (2.4-GHz Band) channel numbers
Regulatory Areas
Channel Frequency Americas EMEA Israel Japan

number (MHz) CCK ODFM CCK ODFM CCK ODFM CCK ODFM
1 2412 • • • • • •
2 2417 • • • • • •
3 2422 • • • • • •
4 2427 • • • • • •
5 2432 • • • • • • • •
6 2437 • • • • • • • •
7 2442 • • • • • • • •
8 2447 • • • • • • • •
9 2452 • • • • • •
10 2457 • • • • • •
11 2462 • • • • • •
12 2467 • • • •
13 2472 • • • •
14 2484 •
System wireless settings

To configure the wireless settings, go to System > Wireless > Settings.
Note: For a FortiWiFi-60 unit, see “FortiWiFi-60 system wireless settings” on page 154.
By default the FortiWiFi unit includes one wireless interface, called wlan. If you are
operating your FortiWiFi unit in access point mode, you can add up to three more
wireless interfaces. All wireless interfaces use the same wireless parameters.
That is, you configure the wireless settings once, and all wireless interfaces use
those settings. For details on adding more wireless interfaces, see “Adding a
wireless interface” on page 152.
When operating the FortiWiFi in Client mode, wireless settings are not
configurable.

150 01-30007-0203-20090112
System Wireless System wireless settings
Figure 75: FortiWiFi wireless parameters
Operation Mode Select Change to switch operation modes.

Access Point - The FortiWiFi unit acts as an access point for wireless
users to connect to send and receive information over a wireless
network. It enables multiple wireless network users access to the
network without the need to connect to it physically. The FortiWiFi unit
can connect to the internal network and act as a firewall to the Internet.
Client - The FortiWiFi unit is set to receive transmissions from another
access point. This enables you to connect remote users to an existing
network using wireless protocols from a location that does not have a
wired infrastructure. In Client mode, the wireless port is not available to
wireless devices as it is dedicated to connecting to the Access Point.
Band Select the wireless frequency band. Be aware what wireless cards or
devices your users have as it may limit their use of the wireless network.
For example, if you configure the FortiWiFi unit for 802.11g and users
have 802.11b devices, they may not be able to use the wireless network.
Geography Select your country or region. This determines which channels are
available. See “Channel assignments” on page 148 for channel
information.
Channel Select a channel for your wireless network or select Auto. The channels
that you can select depend on the Geography setting. See “Channel
assignments” on page 148 for channel information.
Tx Power Set the transmitter power level. The higher the number, the larger the
area the FortiWiFi will broadcast. If you want to keep the wireless signal
to a small area, enter a smaller number.
Beacon Interval Set the interval between beacon packets. Access Points broadcast
Beacons or Traffic Indication Messages (TIM) to synchronize wireless
networks.
A higher value decreases the number of beacons sent, however it may
delay some wireless clients from connecting if it misses a beacon
packet.
Decreasing the value will increase the number of beacons sent, while
this will make it quicker to find and connect to the wireless network, it
requires more overhead, slowing throughput.
Wireless interface list
Interface The name of the wireless interface. To add more wireless interfaces, see
“Adding a wireless interface” on page 152.
MAC Address The MAC address of the Wireless interface.
SSID The wireless service set identifier (SSID) or network name for the
wireless interface. Clients who want to use the wireless interface must
configure their computers to connect to the network that broadcasts this
network name.

01-30007-0203-20090112 151
System wireless settings System Wireless
SSID Broadcast Green checkmark icon indicates that the wireless interface broadcasts
its SSID. Broadcasting the SSID makes it possible for clients to connect
to your wireless network without first knowing the SSID.
Security Mode Displays information about the security mode for the wireless interface.
Adding a wireless interface

You can add up to three additional wireless interfaces. The additional interfaces
share the same wireless parameters configured for the WLAN interface for Band,
Geography, Channel, Tx Power, and Beacon Interval. Ensure each wireless
interface has a unique SSID.
Note: You cannot add additional wireless interfaces on the FortiGate-60, or when the
FortiWiFi is in Client mode.
To add a wireless interface

3 Complete the following:
Name Enter a name for the wireless interface. The name cannot be the
same as an existing interface, zone or VDOM.
Type Select Wireless.
Address Mode The wireless interface can only be set as a manual address. Enter
a valid IP address and netmask.
If the FortiWiFi is running in Transparent mode, this field does not
appear. The interface will be on the same subnet as the other
interfaces.
Administrative Set the administrative access for the interface.
Access
4 In the Wireless Settings section, complete the following and select OK:
Figure 76: Wireless interface settings (WEP64)
Figure 77: Wireless interface settings (WAP2)

152 01-30007-0203-20090112
System Wireless System wireless settings
SSID Enter the wireless service set identifier (SSID) or network name for this
wireless interface. Users who want to use the wireless network must
network name.
SSID Select to broadcast the SSID. Broadcasting the SSID enables clients to
Broadcast connect to your wireless network without first knowing the SSID. For
better security, do not broadcast the SSID. If the interface is not
broadcast, there is less chance of an unwanted user connecting to your
wireless network. If you choose not to broadcast the SSID, you need to
inform users of the SSID so they can configure their wireless devices.
Security mode Select the security mode for the wireless interface. Wireless users must
use the same security mode to be able to connect to this wireless
interface.
• None has no security. Any wireless user can connect to the wireless
network.
• WEP64 - 64-bit web equivalent privacy (WEP). To use WEP64 you
must enter a Key containing 10 hexadecimal digits (0-9 a-f) and
inform wireless users of the key.
• WEP128 - 128-bit WEP. To use WEP128 you must enter a Key
containing 26 hexadecimal digits (0-9 a-f) and inform wireless users of
the key.
• Wi-Fi protected access (WPA) security. To use WPA you must select
a data encryption method. You must also enter a pre-shared key
containing at least eight characters or select a RADIUS server. If you
select a RADIUS server the wireless clients must have accounts on
the RADIUS server.
• WPA2 provides more security features and is more secure than WPA.
To use WPA2 you must select a data encryption method and enter a
pre-shared key containing at least eight characters or select a
RADIUS server. If you select a RADIUS server the wireless clients
must have accounts on the RADIUS server.
• WPA2 Auto provides the same security features as WPA2. However,
WPA2 Auto also accepts wireless clients using WPA security. To use
WPA2 Auto you must select a data encryption method You must also
enter a pre-shared key containing at least 8 characters or select a
RADIUS server. If you select a RADIUS server the wireless clients
must have accounts on the RADIUS server.
Key Enter the security key. This field appears when selecting WEP64 or
WEP128 security.
Data Select a data encryption method to be used by WPA, WPA2, or WPA
Encryption Auto. Select TKIP to use the Temporal Key Integrity Protocol (TKIP).
Select AES to use advanced encryption standard (AES) encryption. AES
is considered more secure that TKIP. Some implementations of WPA
may not support AES.
Pre-shared Key Enter the pre-shared key. This field appears when selecting WPA,
WPA2, or WPA2 Auto security.
RADIUS Server Select to use a RADIUS server when selecting WPA or WPA2 security.
You can use WPA or WPA2 Radius security to integrate your wireless
network configuration with a RADIUS or Windows AD server. Select a
RADIUS server name from the list. You must configure the Radius server
by going to User > RADIUS. For more information, see “RADIUS
servers” on page 424.

01-30007-0203-20090112 153
FortiWiFi-60 system wireless settings System Wireless
RTS Threshold Set the Request to Send (RTS) threshold.

The RTS threshold is the maximum size, in bytes, of a packet that the
FortiWiFi will accept without sending RTS/CTS packets to the sending
wireless device. In some cases, larger packets being sent may cause
collisions, slowing data transmissions. By changing this value from the
default of 2346, you can configure the FortiWiFi unit to, in effect, have the
sending wireless device ask for clearance before sending larger
transmissions. There can still be risk of smaller packet collisions,
however this is less likely.
A setting of 2346 bytes effectively disables this option.
Fragmentation Set the maximum size of a data packet before it is broken into smaller
Threshold packets, reducing the chance of packet collisions. If the packet is smaller
than the threshold, the FortiWiFi unit will fragment the transmission. If the
packet size larger than the threshold, the FortiWiFi unit will not fragment
the transmission.
FortiWiFi-60 system wireless settings

Go to System > Wireless > Settings to configure wireless settings.
Figure 78: Configuring wireless parameters
MAC Address The MAC address of the Wireless interface.

Operation Mode Select Change to switch operation modes.
Access Point - The FortiWiFi unit acts as an access point for wireless
users to connect to send and receive information over a wireless
network. It enables multiple wireless network users access to the
network without the need to connect to it physically. The FortiWiFi unit
can connect to the internal network and act as a firewall to the Internet.
Client - The FortiWiFi unit is set to receive transmissions from another
access point. This enables you to connect remote users to an existing
network using wireless protocols from a location that does not have a
wired infrastructure. In Client mode, the wireless port is not available to
wireless devices as it is dedicated to connecting to the Access Point.
Geography Select your country or region. This determines which channels are
available.
Channel Select a channel for your wireless network or select Auto. The channels
that you can select depend on the Geography setting. See “Channel
assignments” on page 148 for channel information.

154 01-30007-0203-20090112
System Wireless FortiWiFi-60 system wireless settings
SSID Enter the wireless service set identifier (SSID) or network name for this
wireless interface. Users who want to use the wireless network must
network name.
SSID Broadcast Select to broadcast the SSID. Broadcasting the SSID enables clients to
connect to your wireless network without first knowing the SSID. For
better security, do not broadcast the SSID. If the interface is not
broadcast, there is less chance of an unwanted user connecting to your
wireless network. If you choose not to broadcast the SSID, you need to
inform users of the SSID so they can configure their wireless devices.
Security mode Select the security mode for the wireless interface. Wireless users must
use the same security mode to be able to connect to this wireless
interface.
• None has no security. Any wireless user can connect to the wireless
network.
• WEP64 -64-bit web equivalent privacy (WEP), select. To use WEP64
you must enter a Key containing 10 hexadecimal digits (0-9 a-f) and
inform wireless users of the key.
• WEP128 - 128-bit WEP. To use WEP128 you must enter a Key
containing 26 hexadecimal digits (0-9 a-f) and inform wireless users
of the key.
• Wi-Fi protected access (WPA) security. To use WPA you must select
a data encryption method. You must also enter a pre-shared key
containing at least eight characters or select a RADIUS server. If you
select a RADIUS server the wireless clients must have accounts on
the RADIUS server.
Key Enter the security key. This field appears when selecting WEP64 or
WEP128 security.
Pre-shared Key Enter the pre-shared key. This field appears when selecting WPA
security.
Radius Server Select to use a RADIUS server when selecting WPA security. You can
Name use WPA Radius security to integrate your wireless network
configuration with a RADIUS or Windows AD server. Select a RADIUS
server name from the list. You must configure the Radius server by
going to User > RADIUS. For more information, see “RADIUS servers”
on page 424.
Advanced Open or close the Advanced settings section of the Wireless
Parameters. Change settings if needed to address performance issues.
Default values should work well for most situations. Advanced settings
are available in Access Point mode only.
Tx Power Set the transmitter power level. The higher the number, the larger the
area the FortiWiFi will broadcast. If you want to keep the wireless signal
to a small area, enter a smaller number.
Beacon Interval Set the interval between beacon packets. Access Points broadcast
Beacons or Traffic Indication Messages (TIM) to synchronize wireless
networks.
A higher value decreases the number of beacons sent, however it may
delay some wireless clients from connecting if it misses a beacon
packet.
Decreasing the value will increase the number of beacons sent, while
this will make it quicker to find and connect to the wireless network, it
requires more overhead, slowing throughput.

01-30007-0203-20090112 155
Wireless MAC Filter System Wireless
RTS Threshold Set the Request to Send (RTS) threshold.

The RTS threshold is the maximum size, in bytes, of a packet that the
FortiWiFi will accept without sending RTS/CTS packets to the sending
wireless device. In some cases, larger packets being sent may cause
collisions, slowing data transmissions. By changing this value from the
default of 2347, you can configure the FortiWiFi unit to in effect, have the
sending wireless device ask for clearance before sending larger
transmissions. There can still be risk of smaller packet collisions,
however this is less likely.
Fragmentation Set the maximum size of a data packet before it is broken into smaller
Threshold packets, reducing the chance of packet collisions. If the packet size is
larger than the threshold, the FortiWiFi unit will fragment the
transmission. If the packet is smaller than the threshold, the FortiWiFi
unit will not fragment the transmission.
Wireless MAC Filter

To improve the security of your wireless network, you can enable MAC address
filtering on the FortiWiFi unit. By enabling MAC address filtering, you define the
wireless devices that can access the network based on their system MAC
address. When a user attempts to access the wireless network, the FortiWiFi unit
checks the MAC address of the user to the list you created. If the MAC address is
on the approved list, the user gains access to the network. If the user is not in the
list, the user is rejected.
Alternatively, you can create a deny list. Similar to the allow list, you can configure
the wireless interface to allow all connections except those in the MAC address
list.
Using MAC address filtering makes it more difficult for a hacker using random
MAC addresses or spoofing a MAC address to gain access to your network. Note
you can configure one list per WLAN interface.
To allow or deny wireless access to wireless clients based on the MAC address of
the client wireless cards, go to System > Wireless > MAC Filter.
• Managing the MAC Filter list
• FortiWiFi-60 Wireless MAC Filter
Managing the MAC Filter list

The MAC Filter list enables you to view the MAC addresses you have added to a
wireless interface and their status; either allow or deny. It also enables you to edit
and manage MAC Filter lists.
Note: The FortiWiFi-60 only has one wireless interface.
Figure 79: Wireless MAC filter list

156 01-30007-0203-20090112
System Wireless Wireless MAC Filter
Wireless MAC filter interface list

Interface The name of the wireless interface.
MAC address The list of MAC addresses in the MAC filter list for the wireless
interface.
List Access Allow or deny access to the listed MAC addresses for the wireless
interface.
Enable Select to enable the MAC filtering for the wireless interface. When
not selected MAC filtering options are not applied to the interface.
Edit icon Edit the MAC address list for an interface.
To edit a MAC filter list

1 Go to System > Wireless > MAC Filter.
2 Select Edit for the wireless interface.
Note: For the FortiWiFi-60, see “FortiWiFi-60 Wireless MAC Filter” on page 157.
Figure 80: Wireless interface MAC filter
3 Complete the following and select OK:
Edit the MAC filter list for a wireless interface

List Access Select to allow or deny the addresses in the MAC Address list from
accessing the wireless network.
MAC Address Enter the MAC address to add to the list.
Add Add the entered MAC address to the list.
Remove Select one or more MAC addresses in the list and select Remove to
deleted the MAC addresses from the list.
FortiWiFi-60 Wireless MAC Filter

To edit a MAC filter list
1 Go to System > Wireless > MAC Filter.
2 Select Edit for the wireless interface.

01-30007-0203-20090112 157
Wireless MAC Filter System Wireless
Figure 81: FortiWiFi-60 wireless MAC filter
3 Complete the following and select Apply:
MAC Filter Enable Select to enable the MAC filtering for the wireless interface. When
not selected MAC filtering options are not applied to the interface.
Access for PCs not Select whether to allow or deny access to unlisted MAC addresses.
listed below
MAC Address Enter the MAC address to filter.
Allow or Deny Select whether to allow or deny the MAC Address.
Add Add the MAC address to the Allow or Deny list, as selected.
Allow List List of MAC addresses allowed access to the wireless network.
Deny List List of MAC addresses denied access to the wireless network.
Arrow buttons Move MAC addresses between lists.
Remove (below Remove selected MAC addresses from Allow list.
Allow list)
Remove (below Remove selected MAC addresses from Deny list.
Deny list)

158 01-30007-0203-20090112
System Wireless Wireless Monitor
Wireless Monitor
Go to System > Wireless > Monitor to see who is connected to your wireless
LAN.
Figure 82: FortiWiFi-50B, 60A, 60AM, and 60B wireless monitor
Figure 83: FortiWiFi-60 wireless monitor
Statistics Statistical information about wireless performance for each

wireless interface. Statistics are not available for the
FortiWiFi-60.
AP Name The name of the wireless interface.
Frequency The frequency that the wireless interface is operating with.
Should be around 5-GHz for 802.11a interfaces and
around 2.4-GHz for 802.11b and 802.11g networks.
Signal Strength (dBm) The strength of the signal from the client.
Noise (dBm) The received noise level.
S/N (dB) The signal-to-noise ratio in deciBels calculated from signal
strength and noise level.
Rx (KBytes) The amount of data in kilobytes received this session.
Tx (KBytes) The amount of data in kilobytes sent this session.
Clients Real-time details about what devices are connected to the
FortiWiFi unit. This is a useful way to view the number of
users connected should you need to troubleshoot or
perform maintenance on the unit.
MAC Address The MAC address of the connected wireless client.
IP Address The IP address assigned to the connected wireless client.
AP Name The name of the wireless interface that the client is
connected to. Not available on the FortiWiFi-60.
ID The user ID of the connected client using WPA RADIUS
security mode. This field is blank if the client uses WPA
Pre-Shared Key or WEP security modes.
Available on FortiWiFi-60 units only.

01-30007-0203-20090112 159
Wireless Monitor System Wireless

160 01-30007-0203-20090112
System DHCP FortiGate DHCP servers and relays
System DHCP
This section describes how to use DHCP to provide convenient automatic network
configuration for your clients.
DHCP is not available in Transparent mode. DHCP requests are passed through
the FortiGate unit when it is in Transparent mode.
If you enable virtual domains (VDOMs) on the FortiGate unit, DHCP is configured
separately for each virtual domain. For details, see “Using virtual domains” on
page 95.
• FortiGate DHCP servers and relays
• Configuring DHCP services
• Viewing address leases
FortiGate DHCP servers and relays

The DHCP protocol enables hosts to automatically obtain an IP address from a
DHCP server. Optionally, they can also obtain default gateway and DNS server
settings. A FortiGate interface or VLAN subinterface can provide the following
DHCP services:
• Basic DHCP servers for non-IPSec IP networks
• IPSec DHCP servers for IPSec (VPN) connections
• DHCP relay for regular Ethernet or IPSec (VPN) connections
An interface cannot provide both a server and a relay for connections of the same
type (regular or IPSec).
Note: You can configure a Regular DHCP server on an interface only if the interface has a
static IP address. You can configure an IPSec DHCP server on an interface that has either
a static or a dynamic IP address.
You can configure one or more DHCP servers on any FortiGate interface. A
DHCP server dynamically assigns IP addresses to hosts on the network
connected to the interface. The host computers must be configured to obtain their
IP addresses using DHCP.
If an interface is connected to multiple networks via routers, you can add a DHCP
server for each network. The IP range of each DHCP server must match the
network address range. The routers must be configured for DHCP relay.
To configure a DHCP server, see “Configuring a DHCP server” on page 163.
You can configure a FortiGate interface as a DHCP relay. The interface forwards
DHCP requests from DHCP clients to an external DHCP server and returns the
responses to the DHCP clients. The DHCP server must have appropriate routing
so that its response packets to the DHCP clients arrive at the FortiGate unit.

01-30007-0203-20090112 161
Configuring DHCP services System DHCP
To configure a DHCP relay see “Configuring an interface as a DHCP relay agent”

on page 163.
DHCP services can also be configured through the Command Line Interface
(CLI). See the FortiGate CLI Reference for more information.
Configuring DHCP services

Go to System > DHCP > Service to configure DHCP services. On each FortiGate
interface, you can configure a DHCP relay or add DHCP servers as needed.
On FortiGate 50 and 60 series units, a DHCP server is configured, by default, on
the Internal interface, as follows:
IP Range 192.168.1.110 to 192.168.1.210

Netmask 255.255.255.0
Default gateway 192.168.1.99
Lease time 7 days
DNS Server 1 192.168.1.99
You can disable or change this default DHCP Server configuration.
Note: You can not configure DHCP in Transparent mode. In Transparent mode DHCP
requests pass through the FortiGate unit.
Note: An interface must have a static IP before you configure a DHCP server on it.
These settings are appropriate for the default Internal interface IP address of
192.168.1.99. If you change this address to a different network, you need to
change the DHCP server settings to match.
Figure 84: DHCP service list - FortiGate-200A shown
Edit
Delete
Add DHCP Server

162 01-30007-0203-20090112
System DHCP Configuring DHCP services
Interface List of FortiGate interfaces. Expand each listed interface to view the
Relay and Servers.
Server Name/ Name of FortiGate DHCP server or IP address of DHCP server
Relay IP accessed by relay.
Type Type of DHCP relay or server: Regular or IPSec.
Enable Green check mark icon indicates that server or relay is enabled.
Add DHCP Server Select to configure and add a DHCP server for this interface.
icon
Edit icon Select to edit the DHCP relay or server configuration.
Delete icon Select to delete the DHCP server.
Configuring an interface as a DHCP relay agent

Go to System > DHCP > Service and select an edit icon to view or modify the
DHCP relay configuration for an interface.
Figure 85: Edit DHCP relay settings for an interface
Interface Name The name of the interface.

DHCP Relay Agent Select to enable the DHCP relay agent on this interface.
Type Select the type of DHCP service required as either “Regular” or
IPSEC”.
DHCP Server IP Enter the IP address of the DHCP server that will answer DHCP
requests from computers on the network connected to the interface.
Configuring a DHCP server

The System > DHCP > Service screen gives you access to existing DHCP
servers. It is also where you configure new DHCP servers.
To Configure a DHCP server

1 Go to System > DHCP > Service.
2 Select blue arrow for the interface.
3 Select the select the Add DHCP Server icon to create a new DHCP server, or
select the Edit icon beside an existing DHCP server to change its settings.
4 Configure the DHCP server.
5 Select OK.

01-30007-0203-20090112 163
Configuring DHCP services System DHCP
Figure 86: DHCP Server options
Name Enter a name for the DHCP server.

Enable Enable the DHCP server.
Type Select Regular or IPSEC DHCP server.
You cannot configure a Regular DHCP server on an interface that
has a dynamic IP address.
IP Range Enter the start and end for the range of IP addresses that this DHCP
server assigns to DHCP clients.
Network Mask Enter the netmask of the addresses that the DHCP server assigns.
Default Gateway Enter the IP address of the default gateway that the DHCP server
assigns to DHCP clients.
Domain Enter the domain that the DHCP server assigns to DHCP clients.
Lease Time Select Unlimited for an unlimited lease time or enter the interval in
days, hours, and minutes after which a DHCP client must ask the
DHCP server for new settings. The lease time can range from 5
minutes to 100 days.
Advanced Select to configure advanced options. The remaining options in this
table are advanced options.
DNS Server 1 Enter the IP addresses of up to 3 DNS servers that the DHCP server
DNS Server 2 assigns to DHCP clients.
DNS Server 3
WINS Server 1 Add the IP addresses of one or two WINS servers that the DHCP
WINS Server 2 server assigns to DHCP clients.
Option 1 Enter up to three custom DHCP options that can be sent by the
Option 2 DHCP server. Code is the DHCP option code in the range 1 to 255.
Option 3 Option is an even number of hexadecimal characters and is not
required for some option codes. For detailed information about
DHCP options, see RFC 2132, DHCP Options and BOOTP Vendor
Extensions.

164 01-30007-0203-20090112
System DHCP Viewing address leases
Exclude Ranges
Add Add an range of IP addresses to exclude.
You can add up to 16 exclude ranges of IP addresses that the
DHCP server cannot assign to DHCP clients. No range can exceed
65536 IP addresses.
Starting IP Enter the first IP address of the exclude range.
End IP Enter the last IP address of the exclude range.
Delete icon Delete the exclude range.
Viewing address leases

Go to System > DHCP > Address Leases to view the IP addresses that the
DHCP servers have assigned and the corresponding client MAC addresses.
Figure 87: Address leases list
Interface Select interface for which to list leases.

Refresh Select Refresh to update Address leases list.
IP The assigned IP address.
MAC The MAC address of the device to which the IP address is assigned.
Expire Expiry date and time of the DHCP lease.
Reserving IP addresses for specific clients

You can reserve an IP address for a specific client identified by the client device
MAC address and the connection type, regular Ethernet or IPSec. The DHCP
server always assigns the reserved address to that client. You can assign up to
200 IP addresses as reserved. For more information see the FortiGate Maximum
Values for FortiOS 3.0 article on the Fortinet Knowledge Center.
Use the CLI config system dhcp reserved-address command. For more
information, see the FortiGate CLI Reference.

01-30007-0203-20090112 165
Viewing address leases System DHCP

166 01-30007-0203-20090112
System Config HA
System Config
This section describes the configuration of several non-network features, such as
HA, SNMP, custom replacement messages, and Operation mode.
If you enable virtual domains (VDOMs) on the FortiGate unit, HA, SNMP, and
replacement messages are configured globally for the entire FortiGate unit.
Changing operation mode is configured for each individual VDOM. For details,
• HA
• SNMP
• Replacement messages
• Operation mode and VDOM management access
HA
FortiGate high availability (HA) provides a solution for two key requirements of
critical enterprise networking components: enhanced reliability and increased
performance. This section contains a brief description of HA web-based manager
configuration options, the HA cluster members list, HA statistics, and
disconnecting cluster members.
If you enable virtual domains (VDOMs) on the FortiGate unit, HA is configured
globally for the entire FortiGate unit. For details, see “Using virtual domains” on
page 95.
For complete information about how to configure and operate FortiGate HA
clusters see the FortiGate HA Overview, the FortiGate HA Guide, and the Fortinet
Knowledge Center.
HA is not available on FortiGate models 50Aand 50AM. HA is available on all
other FortiGate models, including the FortiGate-50B.
The following topics are included in this section:
• HA options
• Cluster members list
• Viewing HA statistics
• Changing subordinate unit host name and device priority
• Disconnecting a cluster unit from a cluster
HA options
Configure HA options so that a FortiGate unit can join a cluster or to change the
configuration of an operating cluster or cluster member.
To configure HA options so that a FortiGate unit can join an HA cluster, go to
System > Config > HA.

01-30007-0203-20090112 167
HA System Config
If HA is already enabled, go to System > Config > HA to display the cluster

members list. Select edit for the FortiGate unit with Role of master (also called the
primary unit). When you edit the HA configuration of the primary unit, all changes
are synchronized to the other cluster units.
Figure 88: FortiGate-3810A unit HA configuration
You can configure HA options for a FortiGate unit with virtual domains (VDOMs)
enabled by logging into the web-based manager as the global admin administrator
and then going to System > Config > HA.
Note: If your FortiGate cluster uses virtual domains, you are configuring HA virtual
clustering. Most virtual cluster HA options are the same as normal HA options. However,
virtual clusters include VDOM partitioning options. Other differences between configuration
options for regular HA and for virtual clustering HA are described below and in the
FortiGate HA Overview and the FortiGate HA Guide.

168 01-30007-0203-20090112
System Config HA
Figure 89: FortiGate-5001SX HA virtual cluster configuration
Mode Select an HA mode for the cluster or return the FortiGate units in the
cluster to standalone mode. When configuring a cluster, you must set all
members of the HA cluster to the same HA mode. You can select
Standalone (to disable HA), Active-Passive, or Active-Active. If virtual
domains are enabled you can select Active-Passive or Standalone.
Device Priority Optionally set the device priority of the cluster unit. Each cluster unit can
have a different device priority. During HA negotiation, the unit with the
highest device priority usually becomes the primary unit.
In a virtual cluster configuration, each cluster unit can have two device
priorities, one for each virtual cluster. During HA negotiation, the unit
with the highest device priority in a virtual cluster becomes the primary
unit for that virtual cluster.
Changes to the device priority are not synchronized. You can accept the
default device priority when first configuring a cluster. When the cluster
is operating you can change the device priority for different cluster units
as required.

01-30007-0203-20090112 169
HA System Config
Group Name Enter a name to identify the cluster. The maximum length of the group
name is 32 characters. The group name must be the same for all cluster
units before the cluster units can form a cluster. After a cluster is
operating, you can change the group name. The group name change is
synchronized to all cluster units.
The default group name is FGT-HA. You can accept the default group
name when first configuring a cluster. When the cluster is operating you
can change the group name, if required. Two clusters on the same
network cannot have the same group name.
Password Enter a password to identify the cluster. The maximum password length
is 15 characters. The password must be the same for all cluster units
before the cluster units can form a cluster.
The default is no password. You can accept the default password when
first configuring a cluster. When the cluster is operating, you can add a
password, if required. Two clusters on the same network must have
different passwords.
Enable Session Select to enable session pickup so that if the primary unit fails, all
pickup sessions are picked up by the cluster unit that becomes the new primary
unit.
Session pickup is disabled by default. You can accept the default setting
for session pickup and then chose to enable session pickup after the
cluster is operating.
Port Monitor Select to enable or disable monitoring FortiGate interfaces to verify that
the monitored interfaces are functioning properly and connected to their
networks.
If a monitored interface fails or is disconnected from its network, the
interface leaves the cluster and a link failover occurs. The link failover
causes the cluster to reroute the traffic being processed by that interface
to the same interface of another cluster unit that still has a connection to
the network. This other cluster unit becomes the new primary unit.
Port monitoring (also called interface monitoring) is disabled by default.
Leave port monitoring disabled until the cluster is operating and then
only enable port monitoring for connected interfaces.
You can monitor up to 16 interfaces. This limit only applies to FortiGate
units with more than 16 physical interfaces.

170 01-30007-0203-20090112
System Config HA
Heartbeat Select to enable or disable HA heartbeat communication for each

Interface interface in the cluster and set the heartbeat interface priority. The
heartbeat interface with the highest priority processes all heartbeat
traffic. If two or more heartbeat interfaces have the same priority, the
heartbeat interface with the lowest hash map order value processes all
heartbeat traffic. The web-based manager lists interfaces in
alphanumeric order:
• port1
• port2 through 9
• port10
Hash map order sorts interfaces in the following order:
• port1
• port10
• port2 through port9
The default heartbeat interface configuration is different for each
FortiGate unit. This default configuration usually sets the priority of two
heartbeat interfaces to 50. You can accept the default heartbeat
interface configuration if you connect one or both of the default
heartbeat interfaces together.
The heartbeat interface priority range is 0 to 512. The default priority
when you select a new heartbeat interface is 0.
You must select at least one heartbeat interface. If heartbeat
communication is interrupted, the cluster stops processing traffic. For
more information about configuring heartbeat interfaces, see the
FortiGate HA Overview.
You can select up to 8 heartbeat interfaces. This limit only applies to
FortiGate units with more than 8 physical interfaces.
VDOM If you are configuring virtual clustering, you can set the virtual domains
partitioning to be in virtual cluster 1 and the virtual domains to be in virtual cluster 2.
The root virtual domain must always be in virtual cluster 1. For more
information about configuring VDOM partitioning, see the FortiGate HA
Overview.
Cluster members list

You can display the cluster members list to view the status of an operating cluster
and the status of the FortiGate units in the cluster. The cluster members list shows
the FortiGate units in the cluster and for each FortiGate unit shows interface
connections, the cluster unit and the device priority of the cluster unit. From the
cluster members list you can disconnect a unit from the cluster, edit the HA
configuration of primary unit, change the device priority and host name of
subordinate units, and download a debug log for any cluster unit. You can also
view HA statistics for the cluster.
To display the cluster members list, log into an operating cluster and go to
System > Config > HA.

01-30007-0203-20090112 171
HA System Config
Figure 90: Example FortiGate-5001SX cluster members list
Download Debug Log

Up and Down Edit
Arrows Disconnect from Cluster
If virtual domains are enabled, you can display the cluster members list to view the
status of the operating virtual clusters. The virtual cluster members list shows the
status of both virtual clusters including the virtual domains added to each virtual
cluster.
To display the virtual cluster members list for an operating cluster log in as the
global admin administrator and go to System > Config > HA.
Figure 91: Example FortiGate-5001SX virtual cluster members list

Download Debug Log
Up and Down Edit
Arrows Disconnect from Cluster
View HA Statistics Displays the serial number, status, and monitor information for
each cluster unit. See “Viewing HA statistics” on page 173.
Up and down arrows Changes the order of cluster members in the list. The operation of
the cluster or of the units in the cluster are not affected. All that
changes is the order of the units on the cluster members list.

172 01-30007-0203-20090112
System Config HA
Cluster member Illustrations of the front panels of the cluster units. If the network
jack for an interface is shaded green, the interface is connected.
Pause the mouse pointer over each illustration to view the cluster
unit host name, serial number, how long the unit has been
operating (up time), and the interfaces that are configured for port
monitoring.
Hostname The host name of the FortiGate unit. The default host name of the
FortiGate unit is the FortiGate unit serial number.
• To change the primary unit host name, go to System > Status
and select Change beside the current host name.
• To change a subordinate unit host name, from the cluster
members list select the edit icon for a subordinate unit.
Role The status or role of the cluster unit in the cluster.
• Role is MASTER for the primary (or master) unit
• Role is SLAVE for all subordinate (or backup) cluster units
Priority The device priority of the cluster unit. Each cluster unit can have a
different device priority. During HA negotiation, the unit with the
highest device priority becomes the primary unit.
The device priority range is 0 to 255.
Disconnect from Select to disconnect a selected cluster unit from the cluster. See
cluster “Disconnecting a cluster unit from a cluster” on page 175.
Edit Select to change a cluster unit HA configuration.
• For a primary unit, select Edit to change the cluster HA
configuration (including the device priority) of the primary unit.
• For a primary unit in a virtual cluster, select Edit to change the
virtual cluster HA configuration; including the virtual cluster 1
and virtual cluster 2 device priority of this cluster unit.
• For a subordinate unit, select Edit to change the subordinate
unit host name and device priority. See “Changing subordinate
unit host name and device priority” on page 174.
• For a subordinate unit in a virtual cluster, select Edit to change
the subordinate unit host name and the device priority of the
subordinate unit for the selected virtual cluster. See “Changing
subordinate unit host name and device priority” on page 174.
Download debug log Select to download an encrypted debug log to a file. You can send
this debug log file to Fortinet Technical Support
(http://support.fortinet.com) to help diagnose problems with the
cluster or with individual cluster units.
Viewing HA statistics
From the cluster members list, you can select View HA statistics to display the
serial number, status, and monitor information for each cluster unit. To view HA
statistics, go to System > Config > HA and select View HA Statistics.

01-30007-0203-20090112 173
HA System Config
Figure 92: Example HA statistics (active-passive cluster)
Refresh every Select to control how often the web-based manager updates the HA
statistics display.
Back to HA monitor Select to close the HA statistics list and return to the cluster members
list.
Unit The host name and serial number of the cluster unit.
Status Indicates the status of each cluster unit. A green check mark
indicates that the cluster unit is operating normally. A red X indicates
that the cluster unit cannot communicate with the primary unit.
Up Time The time in days, hours, minutes, and seconds since the cluster unit
was last started.
Monitor Displays system status information for each cluster unit.
CPU Usage The current CPU status of each cluster unit. The web-based
manager displays CPU usage for core processes only. CPU usage
for management processes (for example, for HTTPS connections to
the web-based manager) is excluded.
Memory Usage The current memory status of each cluster unit. The web-based
manager displays memory usage for core processes only. Memory
usage for management processes (for example, for HTTPS
connections to the web-based manager) is excluded.
Active Sessions The number of communications sessions being processed by the
cluster unit.
Total Packets The number of packets that have been processed by the cluster unit
since it last started up.
Virus Detected The number of viruses detected by the cluster unit.
Network Utilization The total network bandwidth being used by all of the cluster unit
interfaces.
Total Bytes The number of bytes that have been processed by the cluster unit
since it last started up.
Intrusion Detected The number of intrusions or attacks detected by Intrusion Protection
running on the cluster unit.
Changing subordinate unit host name and device priority

To change the host name and device priority of a subordinate unit in an operating
cluster, go to System > Config > HA to display the cluster members list. Select
Edit for any slave (subordinate) unit in the cluster members list.

174 01-30007-0203-20090112
System Config HA
To change the host name and device priority of a subordinate unit in an operating
cluster with virtual domains enabled, log in as the global admin administrator and
go to System > Config > HA to display the cluster members list. Select Edit for
any slave (subordinate) unit in the cluster members list.
You can change the host name (Peer) and device priority (Priority) of this
subordinate unit. These changes only affect the configuration of the subordinate
unit.
Figure 93: Changing the subordinate unit host name and device priority
Peer View and optionally change the subordinate unit host name.
Priority View and optionally change the subordinate unit device priority.
The device priority is not synchronized among cluster members. In a functioning
cluster you can change device priority to change the priority of any unit in the
cluster. The next time the cluster negotiates, the cluster unit with the highest
device priority becomes the primary unit.
The device priority range is 0 to 255. The default device priority is 128.
Disconnecting a cluster unit from a cluster

You can disconnect a cluster unit if you need to use the disconnected FortiGate
unit for another purpose, such as to act as a standalone firewall. You can go to
System > Config > HA and select a Disconnect from cluster icon to disconnect a
cluster unit from a functioning cluster without disrupting the operation of the
cluster.
Figure 94: Disconnect a cluster member
Serial Number Displays the serial number of the cluster unit to be disconnected from the
cluster.
Interface Select the interface that you want to configure. You also specify the IP
address and netmask for this interface. When the FortiGate unit is
disconnected, all management access options are enabled for this
interface.
IP/Netmask Specify an IP address and netmask for the interface. You can use this IP
address to connect to this interface to configure the disconnected
FortiGate unit.

01-30007-0203-20090112 175
SNMP System Config
SNMP
Simple Network Management Protocol (SNMP) allows you to monitor hardware
on your network. You can configure the hardware, or FortiGate SNMP agent, to
report system information and send traps (alarms or event messages) to SNMP
managers. An SNMP manager is a computer running an application that can read
the incoming traps from the agent and track the information.
Using an SNMP manager, you can access SNMP traps and data from any
FortiGate interface or VLAN subinterface configured for SNMP management
access.
Note: Part of configuring an SNMP manager is to list it as a host in a community on the
FortiGate unit it will be monitoring. Otherwise the SNMP monitor will not receive any traps
from that FortiGate unit, or be able to query it.
The FortiGate SNMP implementation is read-only. SNMP v1 and v2c compliant

SNMP managers have read-only access to FortiGate system information and can
receive FortiGate traps. To monitor FortiGate system information and receive
FortiGate traps you must compile Fortinet proprietary MIBs as well as Fortinet-
supported standard MIBs into your SNMP manager.
RFC support includes support for most of RFC 2665 (Ethernet-like MIB) and most
of RFC 1213 (MIB II) (for more information, see “Fortinet MIBs” on page 179.
Configuring SNMP
Go to System > Config > SNMP v1/v2c to configure the SNMP agent.
Figure 95: Configuring SNMP
SNMP Agent Enable the FortiGate SNMP agent.

Description Enter descriptive information about the FortiGate unit. The
description can be up to 35 characters long.
Location Enter the physical location of the FortiGate unit. The system location
description can be up to 35 characters long.
Contact Enter the contact information for the person responsible for this
FortiGate unit. The contact information can be up to 35 characters.
Apply Save changes made to the description, location, and contact
information.
Create New Select Create New to add a new SNMP community.
See “Configuring an SNMP community” on page 177.
Communities The list of SNMP communities added to the FortiGate configuration.
You can add up to 3 communities.

176 01-30007-0203-20090112
System Config SNMP
Name The name of the SNMP community.

Queries The status of SNMP queries for each SNMP community. The query
status can be enabled or disabled.
Traps The status of SNMP traps for each SNMP community. The trap
status can be enabled or disabled.
Enable Select Enable to activate an SNMP community.
Delete icon Select Delete to remove an SNMP community.
Edit/View icon Select to view or modify an SNMP community.
Configuring an SNMP community

An SNMP community is a grouping of equipment for network administration
purposes. Add SNMP communities to your FortiGate unit so that SNMP
managers can connect to view system information and receive SNMP traps.
You can add up to three SNMP communities. Each community can have a
different configuration for SNMP queries and traps. Each community can be
configured to monitor the FortiGate unit for a different set of events. You can also
add the IP addresses of up to 8 SNMP managers to each community.
Note: When the FortiGate unit is in virtual domain mode, SNMP traps can only be sent on
interfaces in the management virtual domain. Traps cannot be sent over other interfaces.
Figure 96: SNMP community options (part 1)

01-30007-0203-20090112 177
SNMP System Config
Figure 97: SNMP community options (part 2)
Community Name Enter a name to identify the SNMP community.

Hosts Enter the IP address and Identify the SNMP managers that can use
the settings in this SNMP community to monitor the FortiGate unit.
IP Address The IP address of an SNMP manager than can use the settings in
this SNMP community to monitor the FortiGate unit. You can also set
the IP address to 0.0.0.0 to so that any SNMP manager can use this
SNMP community.
Interface Optionally select the name of the interface that this SNMP manager
uses to connect to the FortiGate unit. You only have to select the
interface if the SNMP manager is not on the same subnet as the
FortiGate unit. This can occur if the SNMP manager is on the
Internet or behind a router.
In virtual domain mode, the interface must belong to the
management VDOM to be able to pass SNMP traps.
Delete Select a Delete icon to remove an SNMP manager.
Add Add a blank line to the Hosts list. You can add up to 8 SNMP
managers to a single community.
Queries Enter the Port number (161 by default) that the SNMP managers in
this community use for SNMP v1 and SNMP v2c queries to receive
configuration information from the FortiGate unit. Select the Enable
check box to activate queries for each SNMP version.
Traps Enter the Local and Remote port numbers (port 162 for each by
default) that the FortiGate unit uses to send SNMP v1 and SNMP
v2c traps to the SNMP managers in this community. Select the
Enable check box to activate traps for each SNMP version.
SNMP Event Enable each SNMP event for which the FortiGate unit should send
traps to the SNMP managers in this community.
“CPU overusage” traps sensitivity is slightly reduced, by spreading
values out over 8 polling cycles. This prevents sharp spikes due to
CPU intensive short-term events such as changing a policy.
“Power Supply Failure” event trap is available only on FortiGate-
3810A, and FortiGate-3016B units.

178 01-30007-0203-20090112
System Config SNMP
To configure SNMP access (NAT/Route mode)

Before a remote SNMP manager can connect to the FortiGate agent, you must
configure one or more FortiGate interfaces to accept SNMP connections.
2 Choose an interface that an SNMP manager connects to and select Edit.
3 In Administrative Access, select SNMP.
4 Select OK.
To configure SNMP access (Transparent mode)

1 Go to System > Config > Operation Mode.
2 Enter the IP address that you want to use for management access and the
netmask in the Management IP/Netmask field.
3 Select Apply.
Fortinet MIBs
The FortiGate SNMP agent supports Fortinet proprietary MIBs as well as standard
RFC 1213 and RFC 2665 MIBs. RFC support includes support for the parts of
RFC 2665 (Ethernet-like MIB) and the parts of RFC 1213 (MIB II) that apply to
FortiGate unit configuration.
The FortiGate MIB is listed in Table 10 along with the two RFC MIBs. You can
obtain these MIB files from Fortinet technical support. To be able to communicate
with the SNMP agent, you must compile all of these MIBs into your SNMP
manager.
Your SNMP manager may already include standard and private MIBs in a
compiled database that is ready to use. You must add the Fortinet proprietary MIB
to this database. If the standard MIBs used by the Fortinet SNMP agent are
already compiled into your SNMP manager you do not have to compile them
again.
Table 10: Fortinet MIBs
MIB file name or RFC Description

FORTIOS-300.mib The proprietary Fortinet MIB includes detailed FortiGate system
configuration information and trap information. Your SNMP
manager requires this information to monitor FortiGate
configuration settings and receive traps from the FortiGate
SNMP agent. See “FortiGate traps” on page 180 and “Fortinet
MIB fields” on page 182.
RFC-1213 (MIB II) The FortiGate SNMP agent supports MIB II groups with the
following exceptions.
• No support for the EGP group from MIB II (RFC 1213, section
3.11 and 6.10).
• Protocol statistics returned for MIB II groups
(IP/ICMP/TCP/UDP/etc.) do not accurately capture all
FortiGate traffic activity. More accurate information can be
obtained from the information reported by the Fortinet MIB.
RFC-2665 (Ethernet- The FortiGate SNMP agent supports Ethernet-like MIB
like MIB) information with the following exception.
• No support for the dot3Tests and dot3Errors groups.

01-30007-0203-20090112 179
SNMP System Config
FortiGate traps
The FortiGate agent can send traps to SNMP managers that you have added to
SNMP communities. To receive traps, you must load and compile the Fortinet 3.0
MIB into the SNMP manager.
FortiManager related traps are only sent if a FortiManager unit is configured to
manage this FortiGate unit.
All traps sent include the trap message as well as the FortiGate unit serial number
and hostname.
Table 11: Generic FortiGate traps
Trap message Description

ColdStart Standard traps as described in RFC 1215.
WarmStart
LinkUp
LinkDown
fnTrapTest This trap is sent for diagnostic purposes.
Table 12: FortiGate system traps

CPU usage high CPU usage exceeds 80%. This threshold can be set in the CLI
(fnTrapCpuHigh) using config system global.
Memory low Memory usage exceeds 90%. This threshold can be set in the
(fnTrapMemLow) CLI using config system global.
Interface IP change Change of IP address on a FortiGate interface. The trap
(fnTrapIpChange) message includes the name of the interface, the new IP
address and the serial number of the FortiGate unit. You can
use this trap to track interface IP address changes for
interfaces with dynamic IP addresses set using DHCP or
PPPoE.
Power Supply Failure Power supply failure detected.
(fnTrapPowerSupplyFail This is available only on models with monitored power
ure) supplies.
(fnTrapBridge) Trap being sent by FortiBridge when detecting a FortiGate
failure.
Table 13: FortiGate VPN traps

VPN tunnel is up An IPSec VPN tunnel started.
(fnTrapVpnTunUp)
VPN tunnel down An IPSec VPN tunnel shuts down.
(fnTrapVpnTunDown)
(fnVpnTrapLocalGateway) Local gateway address of VPN tunnel.
(fnVpnTrapRemoteGateway) Remote gateway address of VPN tunnel.

180 01-30007-0203-20090112
System Config SNMP
Table 14: FortiGate IDS / IPS traps

IDS Port Scan Port scan attack is detected.
(fnTrapIdsPortScan) This is not used in FortiOS MR3.0.
IDS Syn Flood Syn flood attack is detected.
(fnTrapIdsSynFlood) This is not used in FortiOS MR3.0.
IPS Anomaly IPS anomaly detected.
(fnTrapIpsAnomaly)
IPS Signature IPS signature detected.
(fnTrapIpsSignature)
IPS Package Update The IPS signature database has been updated.
(fnTrapIpsPkgUpdate)
(fnIpsTrapSigId) ID of IPS signature identified in trap.
(fnIpsTrapSrcIp) IP Address of the IPS signature trigger.
(fnIpsTrapSigMsg) Message associated with IPS event.
Table 15: FortiGate antivirus traps

Virus detected The FortiGate unit detects a virus and removes the infected
(fnTrapAvVirus) file from an HTTP or FTP download or from an email
message.
Oversize file/email detected The FortiGate unit antivirus scanner detects an oversized
(fnTrapAvOversize) file.
Filename block detected The FortiGate unit antivirus scanner blocks a file that
(fnTrapAvPattern) matches a configured pattern.
Fragmented file detected The FortiGate unit antivirus scanner detects a fragmented
(fnTrapAvFragmented) file or attachment.
(fnTrapAvEnterConserve) AV engine enters conservation mode due to reduced
memory conditions.
(fnTrapAvBypass) AV scanning has been bypassed due to conservation mode.
(fnTrapAvOversizePass) An oversized file has been detected, but has been passed
due to configuration.
(fnTrapAvOversizeBlock) An oversized file has been detected and has been blocked.
(fnAvTrapVirName) Virus name that triggered the event.
Table 16: FortiGate logging traps

Log full On a FortiGate unit with a hard drive, hard drive usage exceeds
(fnTrapLogFull) 90%. On a FortiGate unit without a hard drive, log to memory
usage exceeds 90%.
This threshold can be set in the CLI using config system
global.

01-30007-0203-20090112 181
SNMP System Config
Table 17: FortiGate HA traps

HA switch The primary unit in an HA cluster is replaced with a new
(fnTrapHaSwitch) primary unit.
HA Heartbeat Failure HA monitored interface fails heartbeat.
(fnTrapHaHBFail)
(fnTrapHaMemberDown) An HA member becomes unavailable to the cluster.
(fnTrapHaMemberUp) An HA member becomes available to the cluster.
(fnTrapHaStateChange) An HA member changes state.
(fnHaTrapMemberSerial) Serial number of an HA cluster member. Used to identify the
origin of a trap when a cluster is configured.
Table 18: FortiBridge traps

FortiBridge detects fail A FortiBridge unit detects a FortiGate unit failure.
(fnTrapBridge)
Table 19: FortiManager related traps

(fnFMTrapDeployComplete) Indicates when deployment of a new configuration has
been completed.
Used for verification by FortiManager
(fnFMTrapDeployInProgress) Indicates that a configuration change was not immediate
and that the change is currently in progress.
Used for verification by FortiManager.
(fnFMTrapConfChange) Any configuration changes made to FortiGate unit,
excluding any changes made by a connected
FortiManager unit.
(fnFMTrapIfChange) No message. Interface changes IP. Only sent to
monitoring FortiManager.
Fortinet MIB fields

The Fortinet MIB contains fields reporting current FortiGate unit status
information. The tables below list the names of the MIB fields and describe the
status information available for each one. You can view more details about the
information available from all Fortinet MIB fields by compiling the FORTIOS-
300.mib file into your SNMP manager and browsing the Fortinet MIB fields.
In brackets next to the table titles are the object identifier (OID) number for the
table. The OID is unique for each field, as is the name of the field. OIDs within a
table add their position in the table to the end of the table’s OID, with the first table
position being 0. For example the OID of fnSysVersion is 1.3.6.1.4.1.12356.1.2
- the OID of the table, plus its position in the table.

182 01-30007-0203-20090112
System Config SNMP
Table 20: System MIB fields (OID 1.3.6.1.4.1.12356.1
MIB field Description

fnSysModel FortiGate model number, for example, 400 for the FortiGate-400.
fnSysSerial FortiGate unit serial number.
fnSysVersion The firmware version currently running on the FortiGate unit.
fnSysVersionAv The antivirus definition version installed on the FortiGate unit.
fnSysVersionNids The attack definition version installed on the FortiGate unit.
fnSysHaMode The current High-Availability (HA) mode (standalone, A-A, A-P)
fnSysOpMode The FortiGate unit operation mode (NAT or Transparent).
fnSysCpuUsage The current CPU usage (%).
fnSysMemUsage The current memory utilization (%).
fnSysSesCount The current IP session count.
fnSysDiskCapacity The hard disk capacity (MB)
fnSysDiskUsage The current hard disk usage (MB)
fnSysMemCapacity The physical memory installed (KB).
Table 21: HA MIB fields (OID 1.3.6.1.4.1.12356.1.100)

fnHaGroupId HA cluster group ID.
fnHaPriority HA clustering priority (default - 127).
fnHaOverride Status of a master override flag.
fnHaAutoSync Status of an automatic configuration synchronization.
fnHaGroupName HA cluster group name.
fnHaTrapMember Serial number of an HA cluster member.
Serial
fnHaSchedule Load balancing schedule for A-A mode.
fnHaStatsTable Statistics for the individual FortiGate unit in the HA cluster.
fnHaStatsIndex The index number of the unit in the cluster.
fnHaStatsSerial The FortiGate unit serial number.
fnHaStatsCpuUsage The current FortiGate unit CPU usage (%).
fnHaStatsMemUsage The current unit memory usage (%).
fnHaStatsNetUsage The current unit network utilization (Kbps).
fnHaStatsSesCount The number of active sessions.
fnHaStatsPktCount The number of packets processed.
fnHaStatsByteCount The number of bytes processed by the
FortiGate unit
fnHaStatsIdsCount The number of attacks that the IPS detected
in the last 20 hours.
fnHaStatsAvCount The number of viruses that the antivirus
system detected in the last 20 hours.
fnHaStatsHostname Hostname of HA Cluster's unit.

01-30007-0203-20090112 183
SNMP System Config
Table 22: Administrator accounts (OID 1.3.6.1.4.1.12356.101)

fnAdminNumber The number of administrators on the FortiGate unit.
fnAdminTable Table of administrators.
fnAdminIndex Administrator account index number.
fnAdminName The user name of the administrator account.
fnAdminAddr An address of a trusted host or subnet from
which this administrator account can be used.
fnAdminMask A mask of a subnet where fnAdminAddr can be
used.
Table 23: Local users (OID 1.3.6.1.4.1.12356.102)

fnUserNumber The number of local user accounts on the FortiGate unit.
fnUserTable Table of local users.
fnUserIndex Local user account index number.
fnUserName The user name of the local user account.
fnUserAuth The authentication type for the local user:
local - a password stored on the FortiGate unit
radius-single - a password stored on a RADIUS
server
radius-multiple - any user who can authenticate on
the RADIUS server can log on
ldap - a password stored on an LDAP server
fnUserState Whether the local user is enabled or disabled.
Table 24: Options (OID 1.3.6.1.4.1.12356.103)

fnOptIdleTimeout The idle period in minutes after which the administrator must re-
authenticate.
fnOptAuthTimeout The idle period in minutes after which a user must re-authenticate
with the firewall.
fnOptLanguage The web-based manager language.
fnOptLcdProtection Whether an LCD PIN has been set.
Table 25: Logging (OID 1.3.6.1.4.1.12356.1.104)

fnLogOption Logging preferences.

184 01-30007-0203-20090112
System Config SNMP
Table 26: Custom messages (OID 1.3.6.1.4.1.12356.1.105)

fnMesgNumber The number of custom messages on the FortiGate unit.
Table 27: Hardware sensor (OID 1.3.6.1.4.1.12356.1.110

fnHwSensorCount The number of user accounts in fnHwSensorTable.
fnHwSensorTable A list of local and proxied (Radius server) user accounts.
fnHwSensorEnt Hardware Sensor user account number.
Index
fnHwSensorEnt A name of user account.
Name
fnHwSensorEnt Authentication type of the account.
Value Types can be one of:
• local
• radiusSingle
• radiusMultiple
• ldap
fnHwSensorEnt Status of the user account.
AlarmStatus
Table 28: Virtual domains (OID 1.3.6.1.4.1.12356.2)

fnVdNumber The number of virtual domains on the FortiGate unit.
fnVdMaxVdoms The maximum number of virtual domains allowed on the FortiGate
unit.
fnVdEnabled Whether virtual domains are enabled on this FortiGate unit.
fnVdTable Table of virtual domains.
fnVdIndex Internal virtual domain index number on the
FortiGate unit.
fnVdName The name of the virtual domain.
fnVdSesCount Number of session in this virtual domain.
fnVdOpMode Operation mode of this virtual domain - either NAT
or Transparent.

01-30007-0203-20090112 185
SNMP System Config
Table 29: Active IP sessions (OID 1.3.6.1.4.1.12356.4)

fnIpSessIndex The index number of the active IP session.
fnIpSessProto The IP protocol (TCP, UDP, ICMP, etc.) of the session.
fnIpSessFromAddr The source IP address of the active IP session.
fnIpSessFromPort The source port of the active IP session.
fnIpSessToPort The destination IP address of the active IP session.
fnIpSessToAddr The destination port of the active IP session.
fnIpSessExp The expiry time or time-to-live in seconds for the session.
fnIpSessVdom The virtual domain this session is in.
fnIpSessStatsTable IP Session statistics table for virtual domains.
fnIpSessStatsVdom Index that identifies the virtual domain.
Index
fnIpSessNumber Total sessions on this virtual domain.
Table 30: Firewall policy statistics (OID 1.3.6.1.4.1.12356.8)

fnFwPolicyStats Firewall policy statistics table.
Table fnFwPolicyStats Index that identifies the virtual domain.
VdomIndex
fnFwPolicyID Firewall policy ID.
Only enabled policies are available for querying.
fnFwPolicyPktC Packet counter per policy.
ount
fnFwPolicyByte Byte counter per policy.
Count
Table 31: Dialup VPNs (OID 1.3.6.1.4.1.12356.9)

fnVpnDialupIndex The index of the dialup VPN peer.
fnVpnDialupGateway The remote gateway IP address.
fnVpnDialupLifetime VPN tunnel lifetime in seconds.
fnVpnDialupTimeout Time remaining until the next key exchange (seconds).
fnVpnDialupSrcBegin Remote subnet address.
fnVpnDialupSrcEnd Remote subnet mask.
fnVpnDialupDstAddr Local subnet address.
fnVpnDialupVdom Virtual domain this tunnel belongs to.
fnVpnDialupInOctets Number of bytes received.
fnVpnDialupOutOctets Number of bytes transmitted.

186 01-30007-0203-20090112
System Config SNMP
Table 32: VPN Tunnels (OID 1.3.6.1.4.1.12356.9.4)

fnVpnTunEntIndex The unique index of the VPN tunnel.
fnVpnTunEntPhase1Name The descriptive name of the Phase1 configuration.
fnVpnTunEntPhase2Name The descriptive name of the Phase2 configuration.
fnVpnTunEntRemGwyIp The IP of the remote gateway.
fnVpnTunEntRemGwyPort The port of the remote gateway.
fnVpnTunEntLocGwyIp The IP of the local gateway.
fnVpnTunEntLocGwyPort The port of the local gateway.
fnVpnTunEntSelectorSrcBeginIp Beginning of the address range of a source
selector.
fnVpnTunEntSelectorSrcEndIp Ending of the address range of a source selector.
fnVpnTunEntSelectorSrcPort Source selector port
fnVpnTunEntSelectorDstBeginIp Beginning of the address range of a destination
selector
fnVpnTunEntSelectorDstEndIp Ending of the address range of a destination
selector.
fnVpnTunEntSelectorDstPort Destination selector port.
fnVpnTunEntSelectorProto Protocol number for the selector.
fnVpnTunEntLifeSecs Lifetime of the tunnel in seconds.
fnVpnTunEntLifeBytes Lifetime of the tunnel in bytes.
fnVpnTunEntTimeout Timeout of the tunnel in seconds.
fnVpnTunEntInOctets Number of bytes received on the tunnel.
fnVpnTunEntOutOctets Number of bytes sent out on the tunnel.
fnVpnTunEntStatus Current status of the tunnel - either up or down.
fnVpnTunEntVdom Virtual domain the tunnel belongs to.

01-30007-0203-20090112 187
Replacement messages System Config
Replacement messages
Go to System > Config > Replacement Messages to change replacement
messages and customize alert email and information that the FortiGate unit adds
to content streams such as email messages, web pages, and FTP sessions.
The FortiGate unit adds replacement messages to a variety of content streams.
For example, if a virus is found in an email message, the file is removed from the
email and replaced with a replacement message. The same applies to pages
blocked by web filtering and email blocked by spam filtering.
Note: Disclaimer replacement messages provided by Fortinet are examples only.
Replacement messages list

To view the replacement messages list go to System > Config > Replacement
Messages. You use the replacement messages list to view and customize
replacement messages to your requirements. The list organizes replacement
message into an number of types (for example, Mail, HTTP, and so on). Use the
expand arrow beside each type to display the replacement messages for that
category. Select the Edit icon beside each replacement message to customize
that message for your requirements.
Figure 98: Replacement messages list

188 01-30007-0203-20090112
System Config Replacement messages
Name The type of replacement message. Select the blue triangle to expand or
collapse the category. You can change messages added to
• email with virus-infected attachments
• web pages (http)
• ftp sessions
• alert mail messages
• smtp email blocked as spam
• web pages blocked by web filter category blocking
• instant messaging and peer-to-peer sessions
Also, you can modify
• the login page and rejected login page for user authentication
• disclaimer messages for user and administrator authentication (some
models)
• keep alive page for authentication
• the FortiGuard web filtering block override page
• the login page for the SSL-VPN
Description Description of the replacement message type. The web-based manager
describes where each replacement message is used by the FortiGate unit.
Edit or view Select to edit or view a replacement message.
icon
Note: FortiOS uses HTTP to send the Authentication Disclaimer page for the user to accept
before the firewall policy is in effect. Therefore, the user must initiate an HTTP traffic first in
order to trigger the Authentication Disclaimer page. Once the Disclaimer is accepted, the
user can send whatever traffic is allowed by the firewall policy.
Changing replacement messages

To change a replacement message list go to System > Config > Replacement
Messages. Use the expand arrows to view the replacement message that you
want to change. You can change the content of the replacement message by
editing the text and HTML codes and by working with replacement message tags.
See Table 33 on page 190 for descriptions of all of the replacement message
tags.
Figure 99: Sample HTTP virus replacement message

01-30007-0203-20090112 189
Replacement messages can be text or HTML messages. You can add HTML code
to HTML messages. Allowed Formats shows you which format to use in the
replacement message. There is a limitation of 8192 characters for each
replacement message. The following fields and options are available when editing
a replacement message. Different replacement messages have different sets of
fields and options.
Message Setup The name of the replacement message.

Allowed Formats The type of content that can be included in the replacement
message. Allowed formats can be Text or HTML. You should not
use HTML code in Text messages. You can include replacement
message tags in text and HTML messages.
Size The number of characters allowed in the replacement message.
Usually size is 8192 characters.
Message Text The editable text of the replacement message. The message text
can include text, HTML codes (if HTML is the allowed format) and
replacement message tags.
Replacement messages can include replacement message tags. When users

receive the replacement message, the replacement message tag is replaced with
content relevant to the message. Table 33 lists the replacement message tags
that you can add.
Table 33: Replacement message tags
Tag Description
%%AUTH_LOGOUT%% The URL that will immediately delete the current policy and close
the session. Used on the auth-keepalive page.
%%AUTH_REDIR_URL The auth-keepalive page can prompt the user to open a new
%% window which links to this tag.
%%CATEGORY%% The name of the content category of the web site.
%%DEST_IP%% The IP address of the request destination from which a virus was
received. For email this is the IP address of the email server that
sent the email containing the virus. For HTTP this is the IP
address of web page that sent the virus.
%%EMAIL_FROM%% The email address of the sender of the message from which the
file was removed.
%%EMAIL_TO%% The email address of the intended receiver of the message from
which the file was removed.
%%FAILED_MESSAGE The failed to login message displayed on the auth-login-failed
%% page.
%%FILE%% The name of a file that has been removed from a content stream.
This could be a file that contained a virus or was blocked by
antivirus file blocking. %%FILE%% can be used in virus and file
block messages.
%%FORTIGUARD_WF% The FortiGuard - Web Filtering logo.
%
%%FORTINET%% The Fortinet logo.
%%HTTP_ERR_CODE% The HTTP error code. “404” for example.
%
%%HTTP_ERR_DESC% The HTTP error description.
%
%%NIDSEVENT%% The IPS attack message. %%NIDSEVENT%% is added to alert email
intrusion messages.

190 01-30007-0203-20090112
System Config Replacement messages
Table 33: Replacement message tags (Continued)
Tag Description
%%OVERRIDE%% The link to the FortiGuard Web Filtering override form. This is
visible only if the user belongs to a group that is permitted to
create FortiGuard web filtering overrides.
%%OVRD_FORM%% The FortiGuard web filter block override form. This tag must be
present in the FortiGuard Web Filtering override form and should
not be used in other replacement messages.
%%PROTOCOL%% The protocol (http, ftp, pop3, imap, or smtp) in which a virus was
detected. %%PROTOCOL%% is added to alert email virus messages.
%%QUARFILENAME%% The name of a file that has been removed from a content stream
and added to the quarantine. This could be a file that contained a
virus or was blocked by antivirus file blocking.
%%QUARFILENAME%% can be used in virus and file block
messages. Quarantining is only available on FortiGate units with a
local disk.
%%QUESTION%% Authentication challenge question on auth-challenge page.
Prompt to enter username and password on auth-login page.
%%SERVICE%% The name of the web filtering service.
%%SOURCE_IP%% The IP address of the request originator who would have received
the blocked file. For email this is the IP address of the user’s
computer that attempted to download the message from which the
file was removed.
%%TIMEOUT%% Configured number of seconds between authentication keepalive
connections. Used on the auth-keepalive page.
%%URL%% The URL of a web page. This can be a web page that is blocked
by web filter content or URL blocking. %%URL%% can also be used
in http virus and file block messages to be the URL of the web
page from which a user attempted to download a file that is
blocked.
%%VIRUS%% The name of a virus that was found in a file by the antivirus
system. %%VIRUS%% can be used in virus messages
Changing the authentication login page

Users see the authentication login page when they use a VPN or a firewall policy
that requires authentication. You can customize this page in the same way as you
modify other replacement messages, but there are some unique requirements:
• The login page must be an HTML page containing a form with ACTION="/" and
METHOD="POST"
• The form must contain the following hidden controls:
• <INPUT TYPE="hidden" NAME="%%MAGICID%%"
VALUE="%%MAGICVAL%%">
• <INPUT TYPE="hidden" NAME="%%STATEID%%"
VALUE="%%STATEVAL%%">
• <INPUT TYPE="hidden" NAME="%%REDIRID%%"
VALUE="%%PROTURI%%">
• The form must contain the following visible controls:
• <INPUT TYPE="text" NAME="%%USERNAMEID%%" size=25>
• <INPUT TYPE="password" NAME="%%PASSWORDID%%" size=25>
Example
The following is an example of a simple authentication page that meets the
requirements listed above.

01-30007-0203-20090112 191
<HTML><HEAD><TITLE>Firewall Authentication</TITLE></HEAD>
<BODY><H4>You must authenticate to use this service.</H4>
<FORM ACTION="/" method="post">
<INPUT NAME="%%MAGICID%%" VALUE="%%MAGICVAL%%"
TYPE="hidden">
<TABLE ALIGN="center" BGCOLOR="#00cccc" BORDER="0"
CELLPADDING="15" CELLSPACING="0" WIDTH="320"><TBODY>
<TR><TH>Username:</TH>
<TD><INPUT NAME="%%USERNAMEID%%" SIZE="25" TYPE="text">
</TD></TR>
<TR><TH>Password:</TH>
<TD><INPUT NAME="%%PASSWORDID%%" SIZE="25" TYPE="password">
</TD></TR>
<TR><TD COLSPAN="2" ALIGN="center" BGCOLOR="#00cccc">
<INPUT NAME="%%STATEID%%" VALUE="%%STATEVAL%%"
TYPE="hidden">
<INPUT NAME="%%REDIRID%%" VALUE="%%PROTURI%%" TYPE="hidden">
<INPUT VALUE="Continue" TYPE="submit"> </TD></TR>
</TBODY></TABLE></FORM></BODY></HTML>
Changing the FortiGuard web filtering block override page

The %%OVRD_FORM%% tag provides the form used to initiate an override if
FortiGuard - Web Filtering blocks access to a web page. Do not remove this tag
from the replacement message.
Changing the SSL-VPN login message

The SSL VPN login message presents a web page through which users log in to
the SSL-VPN web portal. The page is linked to FortiGate functionality and you
must construct it according to the following guidelines to ensure that it will work.
• The login page must be an HTML page containing a form with
ACTION="%%SSL_ACT%%" and METHOD="%%SSL_METHOD%%"
• The form must contain the %%SSL_LOGIN%% tag to provide the login form.
• The form must contain the %%SSL_HIDDEN%% tag.
Changing the authentication disclaimer page

The Authentication Disclaimer page, available on some models, makes a
statement about usage policy to which the user must agree before the FortiGate
unit permits access. You enable the disclaimer in the firewall policy. See User
Authentication Disclaimer in “Configuring firewall policies” on page 297. You
should change only the disclaimer text itself, not the HTML form code.

192 01-30007-0203-20090112
System Config Operation mode and VDOM management access
Operation mode and VDOM management access

You can change the operation mode of each VDOM independently of other
VDOMs. This allows any combination of NAT/Route and Transparent operating
modes on the FortiGate unit VDOMs.
Management access to a VDOM can be restricted based on which interfaces and
protocols can be used to connect to the FortiGate unit.
Changing operation mode

You can set the operating mode for your VDOM and perform sufficient network
configuration to ensure that you can connect to the web-based manager in the
new mode.
To switch from NAT/Route to Transparent mode

1 Go to System > Config > Operation Mode or select Change beside Operation
Mode on the System Status page for the virtual domain.
2 From the Operation Mode list, select Transparent.
3 Enter the following information and select Apply.
Management IP/Netmask Enter the management IP address and netmask. This

must be a valid IP address for the network from
which you want to manage the FortiGate unit.
Default Gateway Enter the default gateway required to reach other networks
from the FortiGate unit.
To switch from Transparent to NAT/Route mode

1 Go to System > Config > Operation Mode or select Change beside Operation
Mode on the System Status page for the virtual domain.
2 From the Operation Mode list, select NAT.
3 Enter the following information and select Apply.

01-30007-0203-20090112 193
Operation mode and VDOM management access System Config
Interface IP/Netmask Enter a valid IP address and netmask for the network from
which you want to manage the FortiGate unit.
Device Select the interface to which the Interface IP/Netmask
settings apply.
Default Gateway Enter the default gateway required to reach other networks
Gateway Device Select the interface to which the default gateway is
connected.
Management access
You can configure management access on any interface in your VDOM. See
“Administrative access to an interface” on page 125. In NAT/Route mode, the
interface IP address is used for management access. In Transparent mode, you
configure a single management IP address that applies to all interfaces in your
VDOM that permit management access. The FortiGate also uses this IP address
to connect to the FDN for virus and attack updates (see “FortiGuard” on
page 241).
The system administrator (admin) can access all VDOMs, and create regular
administrator accounts. A regular administrator account can access only the
VDOM to which it belongs. The management computer must connect to an
interface in that VDOM. It does not matter to which VDOM the interface belongs.
In both cases, the management computer must connect to an interface that
permits management access and its IP address must be on the same network.
Management access can be via HTTP, HTTPS, telnet, or SSH sessions if those
services are enabled on the interface. HTTPS and SSH are preferred as they are
more secure.
You can allow remote administration of the FortiGate unit. However, allowing
remote administration from the Internet could compromise the security of the
FortiGate unit. You should avoid this unless it is required for your configuration. To
improve the security of a FortiGate unit that allows remote administration from the
Internet:
• Use secure administrative user passwords.
• Change these passwords regularly.
• Enable secure administrative access to this interface using only HTTPS or
SSH.
• Use Trusted Hosts to limit where the remote access can originate from.
• Do not change the system idle timeout from the default value of 5 minutes (see
“Settings” on page 215).

194 01-30007-0203-20090112
System Administrators Administrators
System Administrators
This section describes how to configure administrator accounts on your FortiGate
unit. Administrators access the FortiGate unit to configure its operation. In its
factory default configuration, the unit has one administrator, admin. After
connecting to the web-based manager or the CLI, you can configure additional
administrators with various levels of access to different parts of the FortiGate unit
configuration.
If you enable virtual domains (VDOMs) on the FortiGate unit, system
administrators are configured globally for the entire FortiGate unit. For details, see
Note: Always end your FortiGate session by logging out, in the CLI or the web-based
manager. If you do not, the session remains open.

• Administrators
• Access profiles
• Central Management
• Settings
• Monitoring administrators
• FortiGate IPv6 support
Administrators
There are two levels of administrator accounts:
Regular An administrator with any access profile other than super_admin. A

administrators regular administrator account has access to configuration options as
determined by its access profile. If virtual domains are enabled, the
regular administrator is assigned to one VDOM and cannot access
global configuration options or the configuration for any other VDOM.
For information about which options are global and which are per-
VDOM, see “VDOM configuration settings” on page 97 and “Global
System Includes the factory default system administrator ‘admin’, any other
administrators administrators assigned to the super_admin profile, and any
administrator that is assigned to the super_admin_readonly profile. Any
administrator assigned to the super_admin access profile, including the
default administrator account ‘admin’, has full access to the FortiGate
unit configuration and general system settings that includes the ability
to:
• enable VDOM configuration
• create VDOMs
• configure VDOMs
• assign regular administrators to VDOMs
• configure global options
The super_admin access profile cannot be changed - it does not
appear in the list of profiles in System > Admin > Access Profile, but it
is one of the selections in the Access Profile drop-down list in System >
Admin New/Edit Administrator dialog box.

01-30007-0203-20090112 195
Administrators System Administrators
Figure 100:Adding a new Administrator
Users assigned to the super_admin profile:

• Cannot delete logged-in users who are also assigned the super_admin profile
• Can delete other users assigned the super_admin profile and/or change the
configured authentication method, password, or access profile, only if the other
users are not logged in
• Can delete the default ‘admin’ account only if the default ‘admin’ user is not
logged in
By default, ‘admin’ has no password. The password should be 32 characters or
less.
Note: The password of users with the super_admin access profile can be reset in the CLI.
If the password of a user who is logged in is changed, they will be logged out and made to
re-authenticate with the new password.
For a user ITAdmin with the access profile super_admin, to set the password to 123456:
config sys admin
edit ITAdmin
set password 123456
end
For a user ITAdmin with the access profile super_admin, to reset the password from
123456 to the default ‘empty’:
config sys admin
edit ITAdmin
unset password 123456
end
There is also an access profile that allows read-only super admin privileges,
super_admin_readonly. The super_admin_readonly profile cannot be deleted or
changed, similar to the super_admin profile. This read-only super-admin profile is
suitable in a situation where it is necessary for a system administrator to
troubleshoot a customer configuration without being able to make changes. Other
than being read-only, the super_admin_readonly profile has full access to the
FortiGate unit configuration.

196 01-30007-0203-20090112
You can authenticate an administrator using a password stored on the FortiGate

unit, a RADIUS, LDAP, or TACACS+ server, or use PKI certificate-based
authentication. The RADIUS server authenticates users and authorizes access to
internal network resources based on the access profile of the user. To
authenticate an administrator with an LDAP or TACACS+ server, you must create
the server, include the server in a user group, and associate the administrator with
the user group. Users authenticated with the PKI-based certificate are permitted
access to internal network resources based on the user group they belong to and
the associated access profile.
A vdom/access profile override feature supports authentication of administrators
via RADIUS. The admin user will be have access depending on which vdom they
are restricted to and their associated access profile. This feature is only available
to wildcard administrators, and can only be set using the FortiGate unit CLI. There
can only be one vdom-override user per system. For more information, see the
Configuring regular (password) authentication for administrators

You can use a password stored on the local FortiGate unit to authenticate an
administrator.
To configure an administrator to authenticate with a password stored on the

FortiGate unit
1 Go to System > Admin.
3 Enter or select the following:
Name A name for the administrator.

Type Regular.
Password Enter a password for the administrator to use to authenticate.
Confirm Re-enter the password entered in Password.
Password
Access Profile Select the access profile to apply to the administrator.
When you select Type > Regular, you will see Local as the entry in the Type
column when you view the list of administrators. For more details, see “Viewing
the administrators list” on page 204.
You may also configure additional features. For more information, see
FortiGate unit.
Configuring remote authentication for administrators

You can authenticate administrators using RADIUS, LDAP, or TACACS+ servers.
In order to do this, you must configure the server, include the server as a user in a
user group, and create the administrator account to include in the user group.

01-30007-0203-20090112 197
Configuring RADIUS authentication for administrators

If you want to use a RADIUS server to authenticate administrators in your VDOM,
you must configure the authentication before you create the administrator
accounts. To do this you need to:
• configure the FortiGate unit to access the RADIUS server
• create a user group with the RADIUS server as its only member
Note: Access to the FortiGate is according to the VDOM associated with the administrator
account.
The following procedures assume that there is a RADIUS server on your network
populated with the names and passwords of your administrators. For information
on how to set up a RADIUS server, see the documentation for your RADIUS
server.
Figure 101:Example RADIUS server list
Create New Add a new RADIUS server.

Name The name that identifies the RADIUS server on the FortiGate unit.
Server Name/IP The domain name or IP address of the RADIUS server.
Delete icon Delete a RADIUS server configuration.
You cannot delete a RADIUS server that has been added to a user
group.
Edit icon Edit a RADIUS server configuration.
To configure the FortiGate unit to access the RADIUS server

1 Go to User > Remote > RADIUS.
Name A name that identifies the RADIUS server. Use this name when you
create the user group.
Primary Server The domain name or IP address of the RADIUS server.
Name/IP
Primary Server The RADIUS server secret. The RADIUS server administrator can
Secret provide this information.
4 Select OK.
You may also provide information regarding a secondary RADIUS server, custom
authentication scheme, and a NAS IP/Called Station ID. In addition, you can
configure the RADIUS server to be included in every user group in the associated
VDOM. For more information, see “Configuring a RADIUS server” on page 425.

198 01-30007-0203-20090112
To create the user group (RADIUS)

1 Go to User > User Group.
3 In the Group Name field, type a name for the administrator group.
4 In the Type field, select Firewall.
5 In the Available Users list, select the RADIUS server name and move it to the
Members list.
6 Select a protection profile.
7 Select OK.
To configure an administrator to authenticate with a RADIUS server

Name A name that identifies the administrator.

Type Remote.
User Group The user group that includes the RADIUS server as a member.
Password The password the administrator uses to authenticate.
Confirm The re-entered password that confirms the original entry in Password.
Password
Access Profile The access profile to apply to the administrator.
Configuring LDAP authentication for administrators

Lightweight Directory Access Protocol (LDAP) is an Internet protocol used to
maintain authentication data that may include departments, people, groups of
people, passwords, email addresses, and printers etc.
If you have configured LDAP support and an administrator is required to
authenticate using an LDAP server, the FortiGate unit contacts the LDAP server
for authentication. If the LDAP server cannot authenticate the administrator, the
connection is refused by the FortiGate unit.
If you want to use an LDAP server to authenticate administrators in your VDOM,
you must configure the authentication before you create the administrator
• configure the LDAP server
• configure the FortiGate unit to access the LDAP server
• create a user group with the LDAP server as a member
Go to User > Remote > LDAP to configure an LDAP server.

01-30007-0203-20090112 199
Figure 102:Example LDAP server list
Create New Add a new LDAP server.

Name The name that identifies the LDAP server on the FortiGate unit.
Server Name/IP The domain name or IP address of the LDAP server.
Port The TCP port used to communicate with the LDAP server.
Common Name The common name identifier for the LDAP server.
Identifier
Distinguished The distinguished name used to look up entries on the LDAP server.
Name
Delete icon Delete the LDAP server configuration.
Edit icon Edit the LDAP server configuration.
To configure the FortiGate unit to access the LDAP server

1 Go to User > Remote > LDAP.
Server Port The TCP port used to communicate with the LDAP server.
Common Name The common name identifier for the LDAP server.
Identifier
Distinguished Name The base distinguished name for the server in the correct X.500 or
LDAP format.
Query icon View the LDAP server Distinguished Name Query tree for the LDAP
server that you are configuring so that you can cross-reference to
the Distinguished Name.
For more information, see “Using Query” on page 429.
Bind Type The type of binding for LDAP authentication.
Filter Filter used for group searching.
User DN Distinguished name of user to be authenticated.
Password Password of user to be authenticated.
Secure Connection Use a secure LDAP server connection for authentication.
Protocol A secure LDAP protocol to use for authentication.
Certificate A certificate to use for authentication.
4 Select OK.
For further information about LDAP authentication, see “Configuring an LDAP
server” on page 427.

200 01-30007-0203-20090112
To create the user group (LDAP)

5 In the Available Users list, select the LDAP server name and move it to the
Members list.
7 Select OK.
To configure an administrator to authenticate with an LDAP server


Type Remote.
User Group The user group that includes the LDAP server as a member.
Password
Configuring TACACS+ authentication for administrators

Terminal Access Controller Access-Control System (TACACS+) is a remote
authentication protocol that provides access control for routers, network access
servers, and other networked computing devices via one or more centralized
servers.
If you have configured TACACS+ support and an administrator is required to
authenticate using a TACACS+ server, the FortiGate unit contacts the TACACS+
server for authentication. If the TACACS+ server cannot authenticate the
administrator, the connection is refused by the FortiGate unit.
If you want to use an TACACS+ server to authenticate administrators in your
VDOM, you must configure the authentication before you create the administrator
• configure the TACACS+ server
• configure the FortiGate unit to access the TACACS+ server
• create a user group with the TACACS+ server as a member
Go to User > Remote > TACACS+ to configure a TACACS+ server.

01-30007-0203-20090112 201
Figure 103:Example TACACS+ server list
Create New Add a new TACACS+ server.

Server The server domain name or IP address of the TACACS+ server.
Authentication Type The supported authentication method. TACACS+ authentication
methods include: Auto, ASCII, PAP, CHAP, and MSCHAP.
Delete icon Delete this TACACS+ server.
Edit icon Edit this TACACS+ server.
To configure the FortiGate unit to access the TACACS+ server

1 Go to User > Remote > TACACS+.
Name The name that identifies the TACACS+ server.

Server Name/IP The server domain name or IP address of the TACACS+ server.
Server Key The key to access the TACACS+ server. The maximum number is
16.
Authentication Type The authentication type to use for the TACACS+ server. Selection
includes: Auto, ASCII, PAP, CHAP, and MSCHAP. Auto
authenticates using PAP, MSCHAP, and CHAP (in that order).
For further information about TACACS+ authentication, see “Configuring

TACACS+ servers” on page 430.
To create the user group (TACACS+)

5 In the Available Users list, select the TACACS+ server name and move it to the
Members list.
7 Select OK.
To configure an administrator to authenticate with a TACACS+ server


Type Remote.
User Group The user group that includes the TACACS+ server as a member.

202 01-30007-0203-20090112

Password
Configuring PKI certificate authentication for administrators

Public Key Infrastructure (PKI) authentication utilizes a certificate authentication
library that takes a list of peers, peer groups, and/or user groups and returns
authentication successful or denied notifications. Users only need a valid
certificate for successful authentication - no username or password are
necessary.
If you want to use PKI authentication for an administrator, you must configure the
authentication before you create the administrator accounts. To do this you need
to:
• configure a PKI administrator to be included in the user group
• create a user group
Go to User > PKI to configure PKI users.
Figure 104:User > PKI user list
Create New Add a new PKI user.

User Name The name of the PKI user.
Subject The text string that appears in the subject field of the certificate of
the authenticating user.
Issuer The CA certificate that is used to authenticate this user.
Delete icon Delete this PKI user.
Edit icon Edit this PKI user.
Note: The following fields in the PKI User List correspond to the noted fields in the PKI
User dialog:
User Name: Name
Subject: Subject
CA: Issuer (CA certificate)
To create the user group (PKI)

5 In the Available Users list, select the PKI user name and move it to the Members
list.

01-30007-0203-20090112 203

7 Select OK.
To configure an administrator to authenticate with a PKI certificate


Type PKI.
User Group The user group that includes the PKI user as a member.
“Configuring an administrator account” on page 205
Viewing the administrators list

Use the default ‘admin’ account, an account with the super_admin access profile,
or an administrator with Access Control Read Write to add new administrator
accounts and control their permission levels. Go to System > Admin >
Administrators. If you log in with an administrator account that does not have the
super_admin access profile, the Administrators list will show only the
administrators for the current virtual domain.
Figure 105:Administrators list
Create New Add an administrator account.

Name The login name for an administrator account.
Trusted hosts The IP address and netmask of trusted hosts from which the
administrator can log in. For more information, see “Using trusted
hosts” on page 207.
Profile The access profile for the administrator.
Type The type of authentication for this administrator, one of:
Local - authentication of an account with a local password stored on
the FortiGate unit
Remote - authentication of a specific account on a RADIUS, LDAP, or
TACACS+ server
Remote+Wildcard - authentication of any account on a RADIUS,
LDAP, or TACACS+ server.
PKI - PKI-based certificate authentication of an account.

204 01-30007-0203-20090112
Delete icon Delete the administrator account.

You cannot delete the original ‘admin’ account until you create
another user with the super_admin profile, log out of the ‘admin’
account, and log in with the alternate user that has the super_admin
profile.
Edit or View icon Edit or view the administrator account.
Change Password Change the password for the administrator account.
icon
To change an administrator password

2 Select the Change Password icon next to the administrator account you want to
change the password for.
3 Enter and confirm the new password.
4 Select OK.
Configuring an administrator account

Use the default ‘admin’ account, an account with the super_admin access profile,
or an administrator with Access Control Read Write to create a new administrator.
Go to System > Admin > Administrators and select Create New.
Figure 106:Administrator account configuration - Regular (local) authentication
Figure 107:Administrator account configuration - Remote authentication

01-30007-0203-20090112 205
Figure 108:Administrator account configuration - PKI authentication
Administrator Enter the login name for the administrator account.

The name of the administrator should not contain the characters
<>()#"'. Using these characters in the administrator account name can
result in a cross site scripting (XSS) vulnerability.
Type Select the type of administrator account:
• Regular: Select to create a Local administrator account.
• Remote: Select to authenticate the administrator using a RADIUS,
LDAP, or TACACS+ server. Server authentication for administrators
must be configured first. See “Configuring remote authentication for
administrators” on page 197.
• PKI: Select to enable certificate-based authentication for the
administrator. Only one administrator can be logged in with PKI
authentication enabled.
User Group If you are using Remote or PKI certificate-based authentication, select
the administrator user group that includes the Remote server/PKI (peer)
users as members of the User Group. The administrator user group
cannot be deleted once the group is selected for authentication.
Wildcard Select to allow all accounts on the RADIUS, LDAP, or TACACS+ server
to be administrators.
This is available only if Remote is selected. Only one wildcard user
permitted per VDOM.
Password Enter a password for the administrator account. For improved security,
the password should be at least 6 characters long.
This is not available if Wildcard is selected. Not available when PKI
authentication is selected.
See the Fortinet Knowledge Center article Recovering lost administrator
account passwords if you forget or lose an administrator account
password and cannot log into your FortiGate unit.
Confirm Type the password for the administrator account a second time to
Password confirm that you have typed it correctly.
This is not available if Wildcard is selected. Not available when PKI
authentication is selected.
Trusted Host #1 Optionally, type the trusted host IP address and netmask that
Trusted Host #2 administrator login is restricted to on the FortiGate unit. You can specify
Trusted Host #3 up to three trusted hosts. These addresses all default to 0.0.0.0/0.
Setting trusted hosts for all of your administrators can enhance the
security of your system. For more information, see “Using trusted hosts”
on page 207.
Access Profile Select the access profile for the administrator. The pre-configured
super_admin profile provides full access to the FortiGate unit. You can
also select Create New to create a new access profile. For more
information on access profiles, see “Configuring an access profile” on
page 211.

206 01-30007-0203-20090112
To configure an administrator account

2 Select Create New to add an administrator account.
3 In the Administrator field, type a login name for the administrator account.
If you are using RADIUS authentication for this administrator but not using the
wildcard option, the administrator name must match an account on the RADIUS
server.
4 Select the type of authentication:
If you are using local authentication for this administrator:
• Select Regular.
• Type and confirm the password for the administrator account.
FortiGate unit.
If you are using remote authentication for this administrator (RADIUS, LDAP, or
TACACS+):
• Select Remote.
• Select Wildcard if you want all accounts on the RADIUS, LDAP, or TACACS+
server to be administrators of this FortiGate unit.
• Type and confirm the password for the administrator account. This step does
not apply if you are using Remote Wildcard or PKI certificate-based
authentication.
• Select the administrators user group from the User Group list.
If you are using PKI certificate-based authentication for this administrator:
• Select PKI.
• Select the administrators user group from the User Group list.
5 If required, type Trusted Host IP address(es) and netmask(s) from which the
administrator can log into the web-based manager.
6 Select the access profile for the administrator.
7 Select OK.
Using trusted hosts

Setting trusted hosts for all of your administrators increases the security of your
network by further restricting administrative access. In addition to knowing the
password, an administrator must connect only through the subnet or subnets you
specify. You can even restrict an administrator to a single IP address if you define
only one trusted host IP address with a netmask of 255.255.255.255.
When you set trusted hosts for all administrators, the FortiGate unit does not
respond to administrative access attempts from any other hosts. This provides the
highest security. If you leave even one administrator unrestricted, the unit accepts
administrative access attempts on any interface that has administrative access
enabled, potentially exposing the unit to attempts to gain unauthorized access.
The trusted hosts you define apply both to the web-based manager and to the CLI
when accessed through telnet or SSH. CLI access through the console connector
is not affected.

01-30007-0203-20090112 207
Access profiles System Administrators
The trusted host addresses all default to 0.0.0.0/0. If you set one of the 0.0.0.0/0
addresses to a non-zero address, the other 0.0.0.0/0 will be ignored. The only way
to use a wildcard entry is to leave the trusted hosts at 0.0.0.0/0. However, this
configuration is less secure.
Access profiles
Each administrator account belongs to an access profile. The access profile
separates FortiGate features into access control categories for which you can
enable none (deny), read only, or read/write access. The following table lists the
web-based manager pages to which each category provides access:
Table 34: Access profile control of access to Web-based manager pages
Access control Affected web-based manager pages

Admin Users System > Admin
System > Admin > FortiManager
System > Admin > Settings
Antivirus Configuration AntiVirus
Auth Users User
Firewall Configuration Firewall
FortiGuard Update System > Maintenance > FortiGuard Center
IM, P2P & VoIP Configuration IM, P2P & VoIP > Statistics
IM, P2P & VoIP > User > Current Users
IM, P2P & VoIP > User > User List
IM, P2P & VoIP > User > Config
IPS Configuration Intrusion Protection
Log & Report Log & Report
Maintenance System > Maintenance
Network Configuration System > Network > Interface
System > Network > Zone
System > DHCP
Router Configuration Router
Spamfilter Configuration AntiSpam
System Configuration System > Status, including Session info
System > Config
System > Hostname
System > Network > Options
System > Admin > FortiManager
System > Admin > Settings
System > Status > System Time
VPN Configuration VPN
Webfilter Configuration Web Filter
Read-only access enables the administrator to view the web-based manager

page. The administrator needs write access to change the settings on the page.

208 01-30007-0203-20090112
System Administrators Access profiles
You can now expand the firewall configuration access control to enable more
granular control of access to the firewall functionality. You can control
administrator access to policy, address, service, schedule, profile, and other (VIP)
configurations.
Note: When Virtual Domain Configuration is enabled (see “Settings” on page 215), only the
administrators with the access profile super_admin have access to global settings. When
Virtual Domain Configuration is enabled, other administrator accounts are assigned to one
VDOM and cannot access global configuration options or the configuration for any other
VDOM.
For information about which settings are global, see “VDOM configuration settings” on
page 97.
The access profile has a similar effect on administrator access to CLI commands.
The following table shows which command types are available in each access
control category. You can access “get” and “show” commands with read access.
Access to “config” commands requires write access.
Table 35: Access profile control of access to CLI commands
Access control Available CLI commands

Admin Users (admingrp) system admin
system accprofile
Antivirus Configuration (avgrp) antivirus
Auth Users (authgrp) user
Firewall Configuration (fwgrp) firewall
Use the set fwgrp custom and config
fwgrp-permission commands to set some
firewall permissions individually. Selections can
be made for policy, address, service, schedule,
profile, and other (VIP) configurations. For more
information, see FortiGate CLI Reference.
FortiProtect Update (updategrp) system autoupdate
execute update-av
execute update-ips
execute update-now
IM, P2P & VoIP Configuration imp2p
IPS Configuration (ipsgrp) ips
Log & Report (loggrp) alertemail
log
system fortianalyzer
execute log
Maintenance (mntgrp) execute formatlogdisk
execute restore
execute backup
execute batch
execute usb-disk
Network Configuration (netgrp) system arp-table
system dhcp
system interface
system zone
execute dhcp lease-clear
execute dhcp lease-list
execute clear system arp table
execute interface

01-30007-0203-20090112 209
Access profiles System Administrators
Table 35: Access profile control of access to CLI commands (Continued)
Access control Available CLI commands

Router Configuration (routegrp) router
execute router
execute mrouter
Spamfilter Configuration (spamgrp) spamfilter
System Configuration (sysgrp) system except accprofile, admin,
arp-table, autoupdate, fortianalyzer,
interface, and zone.
execute date
execute ha
execute ping
execute ping-options
execute ping6
execute time
execute traceroute
execute cfg
execute factoryreset
execute reboot
execute shutdown
execute deploy
execute set-next-reboot
execute ssh
execute telnet
execute disconnect-admin-session
execute usb
VPN Configuration (vpngrp) vpn
execute vpn
Webfilter Configuration (webgrp) webfilter
Go to System > Admin > Access Profile to add access profiles for FortiGate
administrators. Each administrator account belongs to an access profile. You can
create access profiles that deny access to, allow read-only, or allow both read-
and write-access to FortiGate features.
When an administrator has read-only access to a feature, the administrator can
access the web-based manager page for that feature but cannot make changes to
the configuration. There are no Create or Apply buttons and lists display only the
View ( ) icon instead of icons for Edit, Delete or other modification commands.
Viewing the access profiles list

Use the admin account or an account with Admin Users read and write access to
create or edit access profiles. Go to System > Admin > Access Profile.
Figure 109:Access profile list
Create New Add a new access profile.

Profile Name The name of the access profile.

210 01-30007-0203-20090112
System Administrators Access profiles
Delete icon Select to delete the access profile.

You cannot delete an access profile that has administrators assigned to it.
Edit icon Select to modify the access profile.
Configuring an access profile

Use the admin account or an account with Admin Users read and write access to
edit an access profile. Go to System > Admin > Access Profile and select
Create New.
Figure 110:Access profile option
Profile Name Enter the name of the access profile.

Access Control Access Control lists the items that can customized access control
settings configured.
None Select to deny access to all Access Control categories.
Read Only Select to enable Read access in all Access Control categories.
Read-Write Select to allow read/write access in all Access Control categories.
Access Control Make specific control selections as required. For detailed
categories information about the access control categories, see “Access
profiles” on page 208.

01-30007-0203-20090112 211
Central Management System Administrators
Central Management
The Central Management tab provides the option of remotely managing your
FortiGate unit by either a FortiManager unit or the FortiGuard Analysis and
Management Service.
From System > Admin > Central Management, you can configure your
FortiGate unit to back up or restore configuration settings automatically to the
specified central management server. The central management server is the type
of service you enable, either a FortiManager unit or the FortiGuard Analysis and
Management Service. If you have a subscription for FortiGuard Analysis and
Management Service, you can also remotely upgrade the firmware on the
FortiGate unit.
Figure 111:Central Management configurations - FortiManager and FortiGuard

Analysis and Management Service
Enable Central Management Enables the Central Management feature on the

FortiGate unit.
Type FortiManager: Select to use FortiManager as the central
management service for the FortiGate unit. Enter the IP
address in the IP field.

212 01-30007-0203-20090112
System Administrators Central Management
FortiGuard Management Service: Select to use the

FortiGuard Analysis and Management Service as the
central management service for the FortiGate unit.
Enter the Account ID in the Account ID field. If you do not
have an account ID, register for the FortiGuard Analysis
and Management Service on the Fortinet support
website.
Select “Change” to go directly to System > Maintenance
> FortiGuard. Under “Analysis & Management Service
Options”, enter the account ID in the Account ID field.
Allow automatic backup of Enable to automatically have the current configuration
configuration on backed up to the management server, when either the
logout/timeout administrator logs out or the admin timeout is reached.
Allow configuration updates Enable to allow the management server to automatically

initiated by the management update the configuration.
server
Allow script updates initiated Enable to allow the management server to automatically
by the management server update scripts.
Allow firmware upgrades Enable to upgrade the firmware on the FortiGate unit by
initiated by the management the management server. This option is available only to
server (FortiGuard Analysis the FortiGuard Analysis and Management Service.
and Management Service
only)
Figure 112:Management and Analysis Service Options on the FortiGuard page
The Revision Control tab, which is part of Central Management, displays a list of
the backed up configuration files. The list displays only when your FortiGate unit is
managed by a central management server.
From the Revision Control tab, you can download a backed up configuration file,
revert to a selected revision, or compare two revisions.
Figure 113:Configuration back ups on the Revision Control page
Current Page
Diff
Revert
Download

01-30007-0203-20090112 213
Central Management System Administrators
Current Page By default, the first page of the list of items is displayed. The total
number of pages appears after the current page number. For
example, if 3/54 appears, you are currently viewing page 3 of 54
pages.
To view pages, select the left and right arrows to display the first,
previous, next, or last page.
To view a specific page, enter the page number in the field and
then press Enter.
For more information, see “Using page controls on web-based
manager lists” on page 61.
Revision An incremental number indicating the order the configurations
were saved. These may not be consecutive numbers if one or
more configurations are deleted.
The most recent, which is also the largest number, is first in the
list.
Date/Time Displays the date and time when this configuration was saved on
the FortiGate unit.
Administrator Displays the administrator account that was used to back up this
revision.
Comments Any relevant description or notes that were saved with the
revision.
This is a good place to include information about why the revision
was saved, who saved it, and if there is a date when it can be
deleted to free up space.
Diff icon Select the diff icon to compare two revisions.
This will display a window that lets you compare the selected
revision to one of:
• the current configuration
• a selected revision from the displayed list including revision
history and templates
• a specified revision number
Download icon Select the download icon to download this revision to your local
PC.
Revert icon Select to go back to the selected revision. You will be prompted to
confirm this action.
For more information about system maintenance, FortiGuard, and configuration

backup and restore, see “Maintenance System Configuration” on page 229.
Note: The FortiGuard-FortiManager protocol is a protocol designed to provide better

communication when a FortiGate unit is connected to a FortiManager unit or when a
FortiGate unit is connected to the FortiGuard Analysis and Management Service. This
protocol resolves the FortiGate-behind-NAT issue and supports passive mode on the
FortiGate Analysis and Management Service.
This protocol runs over SSL using IPv4/TCP port 541 and includes the following functions:
• detects FortiGate unit dead or alive status
• detects management service dead/alive status
• notifies the FortiGate units about configuration changes, AV/IPS database update and
firewall changes.

214 01-30007-0203-20090112
System Administrators Settings
Settings
Go to System > Admin > Settings to set the following options:
• Ports for HTTP/HTTPS administrative access and SSL VPN login
• The idle timeout setting
• Display settings that include the language of the web-based manager and the
number of lines displayed in generated reports
• PIN protection for LCD and control buttons (LCD-equipped models only)
• Enable SCP capability for users logged in via SSH
• Configure Gi Gatekeeper settings for GTP traffic inspection
• Enable IPv6 support on GUI (default configuration only available in CLI)
Figure 114:Administrators Settings
Web Administration Ports

HTTP Enter the TCP port to be used for administrative HTTP
access. The default is 80.
HTTPS Enter the TCP port to be used for administrative HTTPS
SSLVPN Login Port Enter a different HTTPS port number for remote client
web browsers to connect to the FortiGate unit. The
default port number is 10443.
Telnet Port Enter the TCP port to be used for administrative telnet
SSH Port Enter the TCP port to be used for administrative SSH
Enable v1 Select to enable compatibility with SSH v1 in addition to
compatibility v2. (Optional)
Timeout Settings

01-30007-0203-20090112 215
Monitoring administrators System Administrators
Idle Timeout Enter the number of minutes that an administrative

connection can be idle before the administrator must log
in again. The maximum is 480 minutes (8 hours). To
improve security, keep the idle timeout at the default
value of 5 minutes.
Display Settings
Language Select a language for the web-based manager to use.
Choose from English, Simplified Chinese, Japanese,
Korean, Spanish, Traditional Chinese or French.
You should select the language that the management
computer operating system uses.
Lines per Page Set the number of lines per page to display in table lists.
The default is 50. Range is from 20 - 1000.
IPv6 Support on GUI Enable if you want to configure IPv6 options from the GUI
(Firewall policy, route, address and address group).
Default allows configuration from CLI only.
LCD Panel (LCD-equipped models only)
PIN Protection Select the PIN Protection check box and type a 6-digit
PIN.
Administrators must enter the PIN to use the control
buttons and LCD.
Enable SCP Enable if you want users logged in through the SSH to be
able to use the SCP to copy the configuration file.
Note: If you make a change to the default port number for HTTP, HTTPS, telnet, or SSH,
ensure that the port number is unique.
Monitoring administrators
To see the number of logged-in administrators, go to System > Status. Under
System Information, you will see Current Administrators. Click on Details to view
information about the administrators currently logged in to the FortiGate unit.
Figure 115:System Information > Current Administrators
Figure 116:Administrators logged in monitor window

216 01-30007-0203-20090112
System Administrators FortiGate IPv6 support
Disconnect Select to disconnect the selected administrators. This is available only if

your access profile gives you System Configuration write permission.
Refresh Select to update the list.
Close Select to close the window.
check box Select and then select Disconnect to log off this administrator. This is
available only if your access profile gives you System Configuration
write access. You cannot log off the default ‘admin’ user.
User Name The administrator account name.
Type The type of access: http, https, jsconsole, sshv2.
From If Type is jsconsole, the value in From is N/A.
Otherwise, Type contains the administrator’s IP address.
Time The date and time that the administrator logged on.
FortiGate IPv6 support

IPv6 is version 6 of the Internet Protocol. It can provide billions more unique IP
addresses than the previous standard, IPv4. The internet is currently in transition
from IPv4 to IPv6 addressing. IPv6 hosts and routers maintain interoperability with
the existing IPv4 infrastructure in two ways:
• implementing dual IP layers to support both IPv6 and IPv4
• using IPv6 over IPv4 tunneling to encapsulate IPv6 packets within IPv4
headers to carry them over IPv4 infrastructure.
FortiGate units are dual IP layer IPv6/IPv4 nodes. They support IPv6 overIPv4
tunneling, routing, firewall policies and IPSec VPN. You can assign both an IPv4
and an IPv6 address to any interface on a FortiGate unit - the interface functions
as two interfaces, one for IPv4-addressed packets and another for IPv6-
addressed packets.
For more information, see the FortiGate IPv6 Support Technical Note available
from the Fortinet Knowledge Center.
Before you can work with IPv6 on the web-based manager, you must enable IPv6
support.
To enable IPv6 support, go to System > Admin > Settings, then under Display
Settings, select IPv6 Support on GUI.
After you enable IPv6 support in the web-based manager, you can:
• create IPv6 static routes (see Router Static)
• monitor IPv6 routes (see Router Monitor)
• create IPv6 firewall addresses (see Firewall Address)
• create IPv6 firewall address groups (see Firewall Address)
• create IPv6 firewall policies (see Firewall Policy)
• create VPNs that use IPv6 addressing (see VPN IPSEC)
Once IPv6 support is enabled, you can configure the IPv6 options using the web-
based manager or the CLI.
See the FortiGate CLI Reference for information on configuring IPv6 support
using the CLI.

01-30007-0203-20090112 217
FortiGate IPv6 support System Administrators

218 01-30007-0203-20090112
System Certificates Local Certificates
System Certificates
This section explains how to manage X.509 security certificates using the
FortiGate web-based manager. Certificate authentication allows administrators to
generate certificate requests, install signed certificates, import CA root certificates
and certificate revocation lists, and back up and restore installed certificates and
private keys.
Authentication is the process of determining if a remote host can be trusted, which
ultimately controls remote access to network resources. To establish its
trustworthiness, the remote host must provide an acceptable authentication
certificate by obtaining a certificate from a certification authority (CA). The
application can accept or reject any certificate. The FortiGate device can use
certificate authentication to allow administrative access via HTTPS, and to
authenticate IPSec VPN peers or clients and SSL VPN user groups or clients.
If you enable virtual domains (VDOMs) on the FortiGate unit, system certificates
are configured globally for the entire FortiGate unit. For details, see “Using virtual
For additional background information on certificates, see the FortiGate
Certificate Management User Guide.
• Local Certificates
• Remote Certificates
• CA Certificates
• CRL
Local Certificates
Certificate requests and installed server certificates are displayed in the Local
Certificates list. After you submit the request to a CA, the CA will verify the
information and register the contact information on a digital certificate that
contains a serial number, an expiration date, and the public key of the CA. The CA
will then sign and send the signed certificate to you to install on the FortiGate unit.
To view certificate requests and/or import signed server certificates, go to System
> Certificates > Local Certificates. To view certificate details, select the View
Certificate Detail icon in the row that corresponds to the certificate.

01-30007-0203-20090112 219
Local Certificates System Certificates
Figure 117:Local Certificates list
Download
View Certificate Detail
Delete
Generate Generate a local certificate request. See “Generating a certificate

request” on page 221.
Import Import a signed local certificate. See “Importing a signed server
certificate” on page 223.
Name The names of existing local certificates and pending certificate
requests.
Subject The Distinguished Names (DNs) of local signed certificates.
Comments Enter a description of the certificate.
Status The status of the local certificate. PENDING designates a certificate
request that needs to be downloaded and signed.
View Certificate Display certificate details such as the certificate name, issuer, subject,
Detail icon and valid certificate dates. See Figure 118.
Delete icon Delete the selected certificate request or installed server certificate
from the FortiGate configuration. This is available only if the certificate
can be deleted (has PENDING status).
Download icon Save a copy of the certificate request to a local computer. Send the
request to your CA to obtain a signed server certificate for the
FortiGate unit.
Figure 118:Certificate Detail Information
For detailed information and step-by-step procedures related to obtaining and

installing digital certificates, see the FortiGate Certificate Management User
Guide.

220 01-30007-0203-20090112
Generating a certificate request

The FortiGate unit generates a certificate request based on the information you
enter to identify the FortiGate unit. Generated requests are displayed in the Local
Certificates list with a status of PENDING. After you generate a certificate request,
you can download the request to a computer that has management access to the
FortiGate unit and then forward the request to a CA.
To fill out a certificate request, go to System > Certificates > Local Certificates
and select Generate. To download and send the certificate request to a CA, see
“Downloading and submitting a certificate request” on page 222.
Figure 119:Generate Certificate Signing Request
Remove/Add OU
Certification Name Type a certificate name. Typically, this would be the

name of the FortiGate unit. To enable the export of a
signed certificate as a PKCS12 file later on if required, do
not include spaces in the name.
Subject Information Enter the information needed to identify the FortiGate
unit:
Host IP If the FortiGate unit has a static IP address, select Host
IP and enter the public IP address of the FortiGate unit. If
the FortiGate unit does not have a public IP address, use
an email address (or domain name if available) instead.

01-30007-0203-20090112 221
Local Certificates System Certificates
Domain Name If the FortiGate unit has a static IP address and

subscribes to a dynamic DNS service, use a domain
name if available to identify the FortiGate unit. If you
select Domain Name, enter the fully qualified domain
name of the FortiGate unit. Do not include the protocol
specification (http://) or any port number or path names. If
a domain name is not available and the FortiGate unit
subscribes to a dynamic DNS service, an “unable to
verify certificate” type message may be displayed in the
user’s browser whenever the public IP address of the
FortiGate unit changes.
E-Mail If you select E-mail, enter the email address of the owner
of the FortiGate unit.
Optional Information All fields under Optional Information are not required.
Organization Unit Type the name of your department (s). You can enter a
maximum of 5 Organization Units. To add or remove a
unit, use the plus (+) or minus (-) icon.
Organization Type the legal name of your company or organization.
Locality (City) Type the name of the city or town where the FortiGate
unit is installed.
State/Province Type the name of the state or province where the
FortiGate unit is installed.
Country Select the country where the FortiGate unit is installed.
e-mail Type the contact email address.
Key Type Only RSA is supported.
Key Size Select 1024 Bit, 1536 Bit or 2048 Bit. Larger keys are
slower to generate but they provide better security.
Enrollment Method
File Based Select File Based to generate the certificate request.
Online SCEP Select Online SCEP to obtain a signed SCEP-based
certificate automatically over the network.
CA Server URL: Enter the URL of the SCEP server from
which to retrieve the CA certificate.
Challenge Password: Enter the CA server challenge
password.
Downloading and submitting a certificate request

You have to fill out a certificate request and generate the request before you can
submit the results to a CA. For more information, see “Generating a certificate
request” on page 221.
To download and submit a certificate request

1 Go to System > Certificates > Local Certificates.
2 In the Local Certificates list, select the Download icon in the row that corresponds
to the generated certificate request.
3 In the File Download dialog box, select Save to Disk.
4 Name the file and save it to the local file system.

222 01-30007-0203-20090112
5 Submit the request to your CA as follows:

• Using the web browser on the management computer, browse to the CA web
site.
• Follow the CA instructions to place a base-64 encoded PKCS#12 certificate
request and upload your certificate request.
• Follow the CA instructions to download their root certificate and Certificate
Revocation List (CRL), and then install the root certificate and CRL on each
remote client (refer to the browser documentation).
6 When you receive the signed certificate from the CA, install the certificate on the
FortiGate unit. See “Importing a signed server certificate” on page 223.
Importing a signed server certificate

Your CA will provide you with a signed server certificate to install on the FortiGate
unit. When you receive the signed certificate from the CA, save the certificate on a
computer that has management access to the FortiGate unit.
To install the signed server certificate, go to System > Certificates > Local
Certificates and select Import. Install the signed certificate through the Upload
Local Certificate dialog box at the top of the page. The certificate file can be in
either PEM or DER format. The other dialog boxes are for importing previously
exported certificates and private keys.
Figure 120:Upload Local Certificate
Certificate File Enter the full path to and file name of the signed server certificate.
Browse Alternatively, browse to the location on the management computer
where the certificate has been saved, select the certificate, and
then select OK.
Importing an exported server certificate and private key

The server certificate and private key to import must have been exported
previously as a single PKCS12 file through the execute vpn certificate
key export CLI command. The file is associated with a password, which you
will need to know in order to import the file. Before you begin, save a copy of the
file on a computer that has management access to the FortiGate unit. For more
information, see the FortiGate Certificate Management User Guide.
To import the PKCS12 file, go to System > Certificates > Local Certificates and
select Import.
Figure 121:Upload PKCS12 Certificate

01-30007-0203-20090112 223
Remote Certificates System Certificates
Certificate with key Enter the full path to and file name of the previously exported
file PKCS12 file.
Browse Alternatively, browse to the location on the management computer
where the PKCS12 file has been saved, select the file, and then
select OK.
Password Type the password needed to upload the PKCS12 file.
Importing separate server certificate and private key files

Use the Upload Certificate dialog box to import a server certificate and the
associated private key file when the server certificate request and private key
were not generated by the FortiGate unit. The two files to import must be available
on the management computer.
Figure 122:Upload Certificate
Certificate file Enter the full path to and file name of the previously exported
certificate file.
Key file Enter the full path to and file name of the previously exported key
file.
Browse Browse to the location of the previously exported certificate
file/key file, select the file, and then select OK.
Password If a password is required to upload and open the files, type the
password.
Remote Certificates
Note: The certificate file must not use 40-bit RC2-CBC encryption.
For dynamic certificate revocation, an OCSP (Online Certificate Status Protocol)

server is used. Remote certificates are public certificates without a private key.
The OCSP is configured in the CLI only. For more information, see the FortiGate
CLI Reference.
Note: There is one OCSP per vdom.

224 01-30007-0203-20090112
System Certificates Remote Certificates
Figure 123:Remote certificate list
Installed Remote (OCSP) certificates are displayed in the Remote Certificates list.
To view installed Remote (OCSP) certificates or import a Remote (OCSP)
certificate, go to System > Certificates > Remote. To view certificate details,
select the View Certificate Detail icon in the row that corresponds to the certificate.
Import Import a public OCSP certificate. See “Importing CA certificates” on

page 226.
Name The names of existing Remote (OCSP) certificates. The FortiGate unit
assigns unique names (REMOTE_Cert_1, REMOTE_Cert_2,
REMOTE_Cert_3, and so on) to the Remote (OCSP) certificates when
they are imported.
Subject Information about the Remote (OCSP) certificate.
Delete icon Delete a Remote (OCSP) certificate from the FortiGate configuration.
View Certificate Display certificate details.
Detail icon
Download icon Save a copy of the Remote (OCSP) certificate to a local computer.
Importing Remote (OCSP) certificates

To import a Remote (OCSP) certificate, go to System > Certificates > Remote
and select Import.
Figure 124:Upload Remote Certificate
Local PC Use a management PC to upload a public certificate. Enter the

location, or select Browse to navigate to the location of the
certificate.
Browse Browse to the location on the management computer where the
certificate has been saved, select the certificate, and then select
OK.
The system assigns a unique name to each Remote (OCSP) certificate. The
names are numbered consecutively (REMOTE_Cert_1, REMOTE_Cert_2,
REMOTE_Cert_3, and so on).

01-30007-0203-20090112 225
CA Certificates System Certificates
CA Certificates
When you apply for a signed personal or group certificate to install on remote
clients, you must obtain the corresponding root certificate and CRL from the
issuing CA.
When you receive the signed personal or group certificate, install the signed
certificate on the remote client(s) according to the browser documentation. Install
the corresponding root certificate and CRL from the issuing CA on the FortiGate
unit.
Installed CA certificates are displayed in the CA Certificates list. You cannot delete
the Fortinet_CA certificate. To view installed CA root certificates or import a CA
root certificate, go to System > Certificates > CA Certificates. To view root
certificate details, select the View Certificate Detail icon in the row that
corresponds to the certificate.
Figure 125:CA Certificates list

Download
Import Import a CA root certificate. See “Importing CA certificates” on

page 226.
Name The names of existing CA root certificates. The FortiGate unit assigns
unique names (CA_Cert_1, CA_Cert_2, CA_Cert_3, and so on) to
the CA certificates when they are imported.
Subject Information about the issuing CA.
Delete icon Delete a CA root certificate from the FortiGate configuration.
View Certificate Display certificate details.
Detail icon
Download icon Save a copy of the CA root certificate to a local computer.
For detailed information and step-by-step procedures related to obtaining and

installing digital certificates, see the FortiGate Certificate Management User
Guide.
Importing CA certificates
After you download the root certificate of the CA, save the certificate on a PC that
has management access to the FortiGate unit.
To import a CA root certificate, go to System > Certificates > CA Certificates
and select Import.

226 01-30007-0203-20090112
System Certificates CRL
Figure 126:Import CA Certificate
SCEP Select to use an SCEP server to access CA certificate for user

authentication. Enter the URL of the SCEP server from which to
retrieve the CA certificate. Optionally, enter identifying information
of the CA, such as the file name. Select OK.
Local PC Select to use a local administrator’s PC to upload a public
certificate. Enter the location, or browse to the location on the
management computer where the certificate has been saved,
select the certificate, and then select OK.
When you select OK and you have elected to import a certificate via the SCEP
server, the system starts the retrieval process immediately.
The system assigns a unique name to each CA certificate. The names are
numbered consecutively (CA_Cert_1, CA_Cert_2, CA_Cert_3, and so on).
CRL
A Certificate Revocation List (CRL) is a list of CA certificate subscribers paired
with certificate status information. Installed CRLs are displayed in the CRL list.
The FortiGate unit uses CRLs to ensure that the certificates belonging to CAs and
remote clients are valid.
To view installed CRLs, go to System > Certificates > CRL.
Figure 127:Certificate revocation list

Download
Import Import a CRL. See “Importing a certificate revocation list” on page 228.
Name The names of existing certificate revocation lists. The FortiGate unit
assigns unique names (CRL_1, CRL_2, CRL_3, and so on) to
certificate revocation lists when they are imported.
Subject Information about the certificate revocation lists.
Delete icon Delete the selected CRL from the FortiGate configuration.
View Certificate Display CRL details such as the issuer name and CRL update dates.
Detail icon See example Figure 128.
Download icon Save a copy of the CRL to a local computer.

01-30007-0203-20090112 227
CRL System Certificates
Figure 128:CRL Certificate Detail
Importing a certificate revocation list

Certificate revocation lists from CA web sites must be kept updated on a regular
basis to ensure that clients having revoked certificates cannot establish a
connection with the FortiGate unit. After you download a CRL from the CA web
site, save the CRL on a computer that has management access to the FortiGate
unit.
Note: When the CRL is configured with an LDAP, HTTP, and/or SCEP server, the latest
version of the CRL is retrieved automatically from the server when the FortiGate unit does
not have a copy of it or when the current copy expires.
To import a certificate revocation list, go to System > Certificates > CRL and
select Import.
Figure 129:Import CRL
HTTP Select to use an HTTP server to retrieve the CRL. Enter the URL
of the HTTP server.
LDAP Select to use an LDAP server to retrieve the CRL. Select the
LDAP server from the drop-down list.
SCEP Select to use an SCEP server to retrieve the CRL. Select the
Local Certificate from the drop-down list. Enter the URL of the
SCEP server from which the CRL can be retrieved.
Local PC Select to use a local administrator’s PC to upload a public
certificate. Enter the location, or browse to the location on the
management computer where the certificate has been saved,
select the certificate, and then select OK.
The system assigns a unique name to each CRL. The names are numbered
consecutively (CRL_1, CRL_2, CRL_3, and so on).

228 01-30007-0203-20090112
System Maintenance Maintenance System Configuration
System Maintenance
This section describes how to maintain your system configuration as well as
information about enabling and updating FDN services. This section also explains
the types of FDN services that are available for your FortiGate unit.
If you enable virtual domains (VDOMs) on the FortiGate unit, system maintenance
is configured globally for the entire FortiGate unit. For more information, see
This section includes the following topics:
• Maintenance System Configuration
• Revision Control
• Scripts
• FortiGuard
• Troubleshooting FDN connectivity
• Updating antivirus and attack definitions
• Enabling push updates
• License
Maintenance System Configuration

In System > Maintenance > Backup & Restore, you can easily manage your
system configuration by performing backups, remotely upgrade firmware, and
store FortiClient software for users to download and install.
The Maintenance menu is comprised of the following tabs:
• Backup and Restore – provides the ability to back up and restore your system
configuration file, remotely upgrade firmware, and import CLI commands.
• Revision Control – displays all system configuration backups with the date and
time of when they were backed up. This tab displays only if the FortiGuard
Analysis and Management Service is enabled.
• FortiGuard – displays all FDN subscription services, such as antivirus and IPS
definitions as well as the FortiGuard Analysis and Management Service. The
FortiGuard tab also provides configuration for antivirus, IPS, web filtering, and
antispam services.
• Scripts – displays script history execution and provides a way to upload script
files to the FortiGuard Analysis and Management Service portal web site
• License – only displays on FortiGate-3000 units and higher; enables you to
increase the maximum number of VDOMs.
When backing up the system configuration, web content files and spam filtering
files are also included. You can save the configuration to the management
computer or to a USB disk if your FortiGate unit includes a USB port (see “USB
Disks” on page 238). You can also restore the system configuration from
previously downloaded backup files in the Backup and Restore menu.

01-30007-0203-20090112 229
Maintenance System Configuration System Maintenance
When virtual domain configuration is enabled, the content of the backup file
depends on the administrator account that created it. A backup of the system
configuration from the super admin account contains global settings and the
settings included in each VDOM. Only the super admin can restore the
configuration from this file. When you back up the system configuration from a
regular administrator account, the backup file contains the global settings and the
settings for the VDOM that the regular administrator belongs to. A regular
administrator is the only user account that can restore the configuration from this
file.
Some FortiGate models support FortiClient by storing a FortiClient image that
users can download. The FortiClient section of Backup and Restore is available if
your FortiGate model supports FortiClient. This feature is currently available on
FortiGate-1000A, 3600A, and 5005FA2 models.
Figure 130:Backup and Restore page on a FortiGate-3000 unit
The following each explains their corresponding part or section of the Backup &
Restore page. For example, “Backup and Restore” on page 231 contains detailed
information about that part of the Backup and Restore page, such as what
locations you can choose to back up and restore a configuration file to.
These sections are:
• Backup and Restore
• Firmware
• FortiClient
• Advanced
Note: The Firmware Section is available only on FortiGate-100A units and higher. If you
have a FortiGate-100 unit or lower, you can upgrade or downgrade the firmware by going to
System > Status and selecting Update for Firmware Version.

230 01-30007-0203-20090112
Backup and Restore

The Backup and Restore section is where you backup and restore system
configuration.
This section allows you to back up and restore your FortiGate configuration to
your management PC, a central management server, or a USB disk. You can
backup and restore your configuration to a USB disk if the FortiGate unit includes
a USB port and if you have connected a USB disk to the USB port. FortiGate units
support most USB disks including USB keys and external USB hard disks (see
“USB Disks” on page 238). The central management server is referred to remote
management service the FortiGate unit is connected to. For example, if the
current configuration on a FortiGate-60 is backed up to a FortiManager unit, the
central management server would be the FortiManager unit.
You must configure central management in System > Admin > Central
Management before these options are available in the Backup and Restore
section. For more information, see “Central Management” on page 212.
Figure 131:Backup and Restore local options with FortiGuard Analysis and
Management Service enabled
System Displays the date and time of the last local or remote backup.
Configuration If you backed up the configuration file using a USB disk, only the date
(Last Backup:) displays. Time is not saved when backing up using a USB disk.
Backup Displays the options available for backing up your current configuration.
Backup configuration to: Select one of the displayed options:

Local PC Always displays regardless of whether a USB disk is
available, FortiGuard Analysis and Management
Service is enabled, or the FortiGate unit is connected
to a FortiManager unit. This option backs up the
configuration to the management computer the
FortiGate unit is connected to.
USB Disk Displays only if the FortiGate unit includes a USB port.
You must connect a USB disk to the FortiGate unit
USB port to backup your configuration to a USB disk. If
you do not connect a USB disk this option is grayed
out. See “USB Disks” on page 238.
FortiGuard Displays if FortiGuard Analysis and Management

Service is enabled. If FortiGuard Management
Services is not enabled, this option does not display
and instead displays Management Station.
FortiManager Displays if the FortiGate unit is connected to a

FortiManager unit. If the FortiGate unit is not
connected to a FortiManager unit, this option does not
display.

01-30007-0203-20090112 231
Encrypt Select to encrypt the backup file.

configuration Encryption must be enabled to save VPN certificates
file with the configuration.
This option is not available for FortiManager backup
option.
Password Enter a password to encrypt the configuration file. You

will need this password to restore the configuration file.
Confirm Enter the password again to confirm the password.
Filename Enter the name of the backup file or select Browse to

locate the file.
The Filename field is only available when you connect
a USB disk to a FortiGate unit’s USB port.
Backup Select to back up the configuration.
If you are backing up to a FortiManager device, a
confirmation message displays after successfully
completing the backup.
Restore Restore the configuration from a file.
Restore configuration from: Select one of the displayed options:
Local PC Always displays regardless of whether a USB disk is

available, FortiGuard Analysis and Management
Service is enabled, or the FortiGate unit is connected
to a FortiManager unit. This option backs up the
configuration to the management computer the
FortiGate unit is connected to.
USB Disk Displays only if the FortiGate unit includes a USB port.
You must connect a USB disk to the FortiGate unit
USB port to restore your configuration from a USB
disk. If you do not connect a USB disk this option is
grayed out See “USB Disks” on page 238.
FortiGuard Displays if FortiGuard Analysis and Management

Service is enabled. If FortiGuard Analysis and
Management Service is not enabled, this option does
not display.
FortiManager Displays if the FortiGate unit is connected to a

FortiManager unit. If the FortiGate unit is not
connected to a FortiManager unit, this option does not
display.
Filename Select the configuration file name from the Browse list
if you are restoring the configuration from a USB disk.
Enter the configuration file name or use the Browse
button if you are restoring the configuration from a file
on the management computer.
Password Enter the password you entered when backing up the

configuration file.
Restore Select to restore the configuration.
Note: The radio button, Management Station, appears when the FortiGuard Analysis and
Management Service is disabled. The FortiGuard radio button appears when FortiGuard
Analysis and Management Service is enabled.

232 01-30007-0203-20090112
Remote FortiManager Options

Your FortiGate unit has the option of being remotely managed by a FortiManager
unit. The FortiGate unit connects through a VPN IPSec tunnel to the FortiManager
unit where a FortiManager administrator adds the FortiGate unit to the
FortiManager database. After successfully connecting to the FortiManager, you
can then back up your configuration to the FortiManager unit. You can also restore
your configuration.
The automatic back up of the configuration is available only in local mode on the
FortiManager unit.
A list of revisions displays when restoring the configuration from a remote
location. The list enables you to choose the specific configuration to restore.
Figure 132:Backup and Restore local options with FortiManager enabled

\
Backup Displays the options available for backing up your current configuration to a
FortiManager unit.
Backup Select the FortiManager option to upload the configuration to
configuration the FortiManager unit.
to: The Local PC option is always available.
Comments: Enter a description or information about the file in the
Comments field. This is optional.
Backup Select to back up the configuration file to the FortiManager
unit.
A confirmation message displays after successfully
Restore Displays the options for restoring a configuration file.
Restore Select the FortiManager option to download the configuration
configuration file from the FortiManager unit.
from:
Please Select: Select the configuration file you want to restore from the list.
This list includes the comments you included in the Comment
field before it was uploaded to the FortiManager unit.
The list is in numerical order, with the recent uploaded
configuration first.
Restore Select to restore the configuration from the FortiManager unit.

01-30007-0203-20090112 233

FortiGate unit is connected to the FortiGuard Analysis and Management Service. This new
FortiGate Analysis and Management Service.
firewall changes.
Remote Management Options

Your FortiGate unit can be remotely managed by a central management server,
which is available when you register for the FortiGuard Analysis and Management
Service. The FortiGuard Analysis and Management Service is a subscription-
based service and is purchased by contacting support. Additional information,
including how to register you FortiGate unit for the FortiGuard Analysis and
Management Service, is available in the FortiGuard Analysis and Management
Service Administration Guide, located at http://kc.forticare.com.
After registering, you can back up your configuration or restore your configuration.
The FortiGuard Analysis and Management Service is useful when administering
multiple FortiGate units without having a FortiManager unit.
You can also upgrade the firmware on your FortiGate unit using the FortiGuard
Analysis and Management Service. Upgrading the firmware is available in the
Firmware Upgrade section of the Backup and Restore menu. See “Firmware
Upgrade” on page 236 for more information about upgrading firmware from the
Backup and Restore menu.
When restoring the configuration from a remote location, a list of revisions
displays so that you can choose the configuration file to restore.
Figure 133:Backup and Restore Central Management options
Backup Displays the options available for backing up your current configuration to the
FortiGuard Analysis and Management Service server.
Backup configuration Select the FortiGuard option to upload the
to: configuration to the FortiGuard Analysis and
Management Service server.
The Local PC option is always available.
Comments: Enter a description or note in the Comments field.
Backup Select to back up the configuration file to the
FortiGuard Analysis and Management Service.
A confirmation message displays after successfully
Restore Displays the options for restoring a configuration file.

234 01-30007-0203-20090112
Restore configuration Select the FortiManager option to download the

from: configuration file from the FortiManager unit.
Please Select: Select the configuration file you want to restore from
the list. The list includes the comments you included in
the Comment field before uploading to the FortiGuard
Analysis Management Service server.
The list is in numerical order, with the recent uploaded
configuration first.
Restore Select to restore the configuration from the FortiGuard
Management Services server.

FortiGate unit is connected to the FortiGuard Analysis and Management Service. This new
firewall changes.
Firmware
The Firmware section displays the current version of firmware installed on your
FortiGate unit, and also displays the firmware version currently in use if there is
more than one firmware image saved on the FortiGate unit.
Figure 134:Two firmware images displaying on a FortiGate-1000A unit in the

Firmware section on the Backup and Restore page
Partition A partition can contain one version of the firmware and the
system configuration. FortiGate-100A units and higher have two
partitions. One partition is active and the other is used as a
backup.
Active A green check mark indicates the partition currently in use.
Last Upgrade The date and time of the last update to this partition.
Firmware Version The version and build number of the FortiGate firmware. If your
FortiGate model has a backup partition, you can:
• Select Upload to replace with firmware from the management
computer or a USB disk. The USB disk must be connected to
the FortiGate unit USB port. See “USB Disks” on page 238.
• Select Upload and Reboot to replace the firmware and make
this the active partition.
Boot alternate Restart the FortiGate unit using the backup firmware.
firmware This is only available for FortiGate-100 units or higher.

01-30007-0203-20090112 235
Firmware Upgrade
The Firmware Upgrade section of the Backup and Restore page displays options
for upgrading to a new version using the FortiGuard Analysis and Management
Service if that option is available to you. Using the FortiGuard Analysis and
Management Service to upgrade the firmware on your FortiGate unit is only
available on certain FortiGate units. You must register for the service by
contacting customer support.
Detailed firmware version information is provided if you have subscribed for the
Figure 135:Firmware Upgrade section of the Backup and Restore page
Upgrade method Select to upgrade from the FortiGuard Analysis and Management
Service. You can also choose to upgrade by file if a current
firmware version is stored on your management computer.
[Please Select] Select one of the available firmware versions. The list contains the
following information for each available firmware release:
• continent (for example, North America)
• maintenance release number
• patch release number
• build number
For example, if you are upgrading to FortiOS 3.0 MR6 and the
FortiGate unit is located in North America, the firmware version
available is v3.0 MR6-NA (build 0700).
Allow firmware Select to be able to install older versions than the one currently
downgrade installed.
This is useful if the current version changed functionality you need
and you have to revert to the previous image.
Upgrade by File Select Browse to select a file on your local PC to upload to the
FortiGate unit.
OK Select OK to enable your selection.
FortiClient
If your FortiGate unit supports the host check function, you can view version
information for the FortiClient application stored on the unit, including uploading a
current firmware version of the FortiClient application.
Some FortiGate units provide a host check function that can determine whether
users’ computers have FortiClient Host Security software installed. Users who fail
the host check are redirected to a web portal where they can download the
FortiClient application. For more information, see “Options to detect FortiClient on
hosts” on page 308.

236 01-30007-0203-20090112
Figure 136:FortiClient section of the Backup & Restore page
Software Image The current FortiClient image on this FortiGate unit.

Select Upload to upload a new FortiClient image from your
management computer.
The name of the uploaded file must begin with “FortiClientSetup_”
followed by the version number, for example, “3.0.526”. Fortinet
provides reduced-size installer files, with “_FG” in the name,
specifically for upload to FortiGate units.
Antivirus The current version of the FortiGuard antivirus database on this
Database FortiGate unit. For more information, see “Configuring the FortiGate
unit for FDN and FortiGuard subscription services” on page 243.
Antivirus Engine The current version of the FortiGuard antivirus engine on this
FortiGate unit. For more information, see “Configuring the FortiGate
unit for FDN and FortiGuard subscription services” on page 243.
Web Portal Port Select the port for the web portal where users are redirected if they
fail the FortiClient host check. Select Save after changing the port
number to commit the change.
The default port number is 8009. Change the port number only if it
causes a conflict on your network.
Advanced
The Advanced section on the Backup and Restore page includes the USB Auto
Install feature and the debug log.
Figure 137:Options available in the Advanced section

01-30007-0203-20090112 237
Revision Control System Maintenance
Advanced (USB This section is only available if the FortiGate unit includes a USB port.
Auto-Install, You must connect a USB disk to the FortiGate unit USB port to use the
Download Debug USB auto-install feature. See “USB Disks” on page 238.
Log) Select the options as required and restart the FortiGate unit.
If you select both configuration and firmware update, both occur on the
same reboot. The FortiGate unit will not reload a firmware or
configuration file that is already loaded.
On system restart, Automatically update the configuration on

automatically restart. Ensure that the Default configuration file
update FortiGate name matches the configuration file name on
the USB disk.
configuration
If the configuration file name on the disk
matches the specified file name, the FortiGate
unit skips the update FortiGate configuration
process.
On system restart, Automatically update the firmware on restart.

automatically Ensure that the Default image name matches
update FortiGate the firmware file name on the USB disk.
firmware If the firmware image name on the disk matches
the specified firmware image name, the
FortiGate unit skips the update FortiGate
firmware process.
Apply Select to have the selected image and

configuration file automatically install
Download Debug Download an encrypted debug log to a file. You can send this debug
Log log to Fortinet Technical Support to help diagnose problems with your
FortiGate unit.
USB Disks
FortiGate units with USB port(s) support USB disks for backing up and restoring
configurations.
FortiUSB and generic USB disks are supported, but the generic USB disk must be
formatted as a FAT16 disk. No other partition type is supported.
There are two ways that you can format the USB disk, either by using the CLI or a
Windows system. You can format the USB disk in the CLI using the command
syntax, exe usb-disk format. When using a Windows system to format the
disk, at the DOS command prompt or similar prompt type, “format
<drive_letter>: /FS:FAT /V:<drive_label>” where <drive_letter> is
the letter of the connected USB drive you want to format, and <drive_label> is the
name you want to give the USB drive for identification.
Note: Formatting the USB disk deletes all information on the disk. Back up the information
on the USB disk before formatting to ensure all information on the disk is recoverable.
Revision Control
The Revision Control tab enables you to manage multiple versions of
configuration files and appears only after registering and configuring the
FortiGuard Analysis and Management Service. Revision Control requires a
configured central management server. This server can either be a FortiManager
unit or the FortiGuard Analysis and Management Service.

238 01-30007-0203-20090112
System Maintenance Revision Control
If central management is not configured on your FortiGate unit, a message

displays telling you to do one of the following:
• enable Central Management, see “Central Management” on page 212
• obtain a valid license
When Revision Control is enabled on your FortiGate unit, and configurations were
backed up, a list of saved revisions of those backed up configurations display.
Figure 138:Revision Control page displaying system configuration back ups

Current Page
Diff
Download
Revert
number of pages appears after the current page number. For example,
if 3/54 appears, you are currently viewing page 3 of 54 pages.
To view a specific page, enter the page number in the field and then
press Enter.
Revision An incremental number indicating the order the configurations were
saved. These may not be consecutive numbers if one or more
configurations are deleted.
The most recent, also the largest number, is first in the list.
Date/Time Displays the date and time when this configuration was saved on the
FortiGate unit.
Administrator Displays the administrator account that was used to back up this
revision.
Comments Any relevant information saved with the revision.
A description provides information about why the revision was saved,
who saved it, and if there is a date when it can be deleted to free up
space.
Diff icon Select to compare two revisions.
A window appears after selecting the diff icon, enabling you to view
and compare the selected revision to one of:
• the current configuration
• a selected revision from the displayed list including revision history
and templates
• a specified revision number
Download icon Select to download this revision to your local PC.
Revert icon Select to go to the previous selected revision. You will be prompted to
confirm this action.

01-30007-0203-20090112 239
Scripts System Maintenance
Scripts
If you have FortiGuard Analysis and Management Service enabled, you can
configure and manage scripts. Scripts are files that are comprised of command
text and are usually composed in a plain text editor.
From the Script tab, you can upload bulk CLI command files and view what files
were uploaded or executed to the FortiGate unit. The uploaded script files appear
on the FortiGuard Analysis and Management Service portal web site.
After executing scripts, you can view script execution history on the Script page.
The past ten executed scripts display.
Figure 139:Script execution history in System > Maintenance > Script
Execute Script from Select Browse to location the script file and then select Apply to
[Upload Bulk CLI upload the file to the FortiGuard Analysis and Management
Command File] Service portal web site.
Script Execution Displays the past 10 scripts that were uploaded to the FortiGuard
History (past 10 Analysis and Management Service portal web site, which includes
scripts) their status, name, type, and time when they were uploaded.
Name The name of the script file that was uploaded to the
FortiGuard Analysis and Management Service web
site.
Type The type of upload that occurred either from the
management computer or the FortiGuard Analysis
and Management Service portal web site.
Time The time of when the file was uploaded in the format,
yyyy-mm-dd hh:mm:ss.
Status The status of the uploaded script file, if it succeeded
or failed.
Delete icon Select to delete the script file entry.
Creating script files

You will need a TFTP or FTP server for the following procedure, or if your
FortiGate unit supports USB, a USB key (see “USB Disks” on page 238). If you
have configured FortiGuard Analysis and Management Service, you can upload
the file to the management server.
Script files do not need to be saved as text files before being uploaded to the
management server.

240 01-30007-0203-20090112
System Maintenance FortiGuard
To create a script file

1 If you are using a TFTP or FTP server, start the server now.
2 Log into the CLI.
3 Enter the following to back up the configuration file:
execute backup config [tftp | ftp | management-station |
usb] <file_name> <ipv4> <password>
4 If you want, you can enter a password for accessing the file.
The FortiGate unit reboots. This may take a few minutes.
After creating the script file, you can then upload it to the FortiGuard Analysis and
Management Service portal web site.
Uploading scripts
After you have created a script file, you can then upload the script file in System >
Maintenance > Script. After the script uploads, you can view or configure to run
the script on the FortiGuard Analysis and Management portal web site.
All script files that are uploaded in System > Maintenance > Script are uploaded
to the FortiGuard Analysis and Management Service portal web site.
To execute a script
1 Go to System > Maintenance > Scripts.
2 Verify that the radio button is selected for Upload Bulk CLI Command File.
3 Select Browse to locate the script file.
4 Select Apply.
The following message appears:
Settings successfully uploaded. Please wait while the system restarts.
5 The FortiGate unit restarts and reboots. This may take a few minutes.
You can view the script or run the script from the FortiGuard Analysis and
Management Service portal web site. For more information about viewing or
running an uploaded script on the portal web site, see the FortiGuard Analysis
and Management Service Administration Guide.
FortiGuard
The FortiGuard tab enables you to configure your FortiGate unit to use the
FortiGuard Distribution Network (FDN) and FortiGuard Services. The FDN
provides updates to antivirus and IPS attack definitions. FortiGuard Services
provides online IP address black list, URL black list, and other spam filtering tools.
FortiGuard Distribution Network

The FDN is a world-wide network of FortiGuard Distribution Servers (FDS). The
FDN provides updates to antivirus (including grayware) and IPS attack definitions.
When the FortiGate unit connects to the FDN, it connects to the nearest FDS
based on the current time zone setting.
The FortiGate unit supports the following update options:

01-30007-0203-20090112 241
FortiGuard System Maintenance
• User-initiated updates from the FDN,

• Hourly, daily, or weekly scheduled antivirus and attack definition updates from
the FDN,
• Push updates from the FDN,
• Update status including version numbers, expiry dates, and update dates and
times,
• Push updates through a NAT device.
Registering your FortiGate unit on the Fortinet Support web page provides a valid
license contract and connection to the FDN. On the Fortinet Support web page, go
to Product Registration and follow the instructions.
The FortiGate unit must be able to connect to the FDN using HTTPS on port 443
to receive scheduled updates. For information about configuring scheduled
updates, see “To enable scheduled updates” on page 249.
You can also configure the FortiGate unit to receive push updates. When the
FortiGate unit is receiving push updates, the FDN must be able to route packets to
the FortiGate unit using UDP port 9443. For information about configuring push
updates, see “Enabling push updates” on page 250. If the FortiGate unit is behind
a NAT device, see “Enabling push updates through a NAT device” on page 251.
FortiGuard Services
Worldwide coverage of FortiGuard services are provided by FortiGuard Service
Points. When the FortiGate unit is connecting to the FDN, it is connecting to the
closest FortiGuard Service Point. Fortinet adds new Service Points as required.
By default, the FortiGate unit communicates with the closest Service Point. If the
Service Point becomes unreachable for any reason, the FortiGate unit contacts
another Service Point and information is available within seconds. By default, the
FortiGate unit communicates with the Service Point via UDP on port 53.
Alternately, the UDP port used for Service Point communication can be switched
to port 8888 by going to System > Maintenance > FortiGuard.
If you need to change the default FortiGuard Service Point host name, use the
hostname keyword in the system fortiguard CLI command. You cannot
change the FortiGuard Service Point name using the web-based manager.
For more information about FortiGuard services, see the FortiGuard Center web
page.
FortiGuard Antispam Service

FortiGuard Antispam is an antispam system from Fortinet that includes an IP
address black list, a URL black list, and spam filtering tools. The IP address black
list contains IP addresses of email servers known to generate spam. The URL
black list contains URLs that are found in spam email.
FortiGuard Antispam processes are completely automated and configured by
Fortinet. With constant monitoring and dynamic updates, FortiGuard Antispam is
always current. You can either enable or disable FortiGuard Antispam in the
Firewall menu in a protection profile. For more information, see “Spam Filtering
options” on page 373.

242 01-30007-0203-20090112
Every FortiGate unit comes with a free 30-day FortiGuard Antispam trial license.
FortiGuard Antispam license management is performed by Fortinet servers; there
is no need to enter a license number. The FortiGate unit automatically contacts a
FortiGuard Antispam Service Point when enabling FortiGuard Antispam. Contact
Fortinet Technical support to renew the FortiGuard Antispam license after the free
trial expires.
You can globally enable FortiGuard Antispam in System > Maintenance >
FortiGuard and then configure Spam Filtering options in each firewall protection
profile in Firewall > Protection Profile. For more information, see “Spam Filtering
FortiGuard Web Filtering Service

FortiGuard Web Filtering is a managed web filtering solution provided by Fortinet.
FortiGuard Web Filtering sorts hundreds of millions of web pages into a wide
range of categories users can allow, block, or monitor. The FortiGate unit
accesses the nearest FortiGuard Web Filtering Service Point to determine the
category of a requested web page, then follows the firewall policy configured for
that user or interface.
Every FortiGate unit comes with a free 30-day FortiGuard Web Filtering trial
license. FortiGuard license management is performed by Fortinet servers. There
is no need to enter a license number. The FortiGate unit automatically contacts a
FortiGuard Service Point when enabling FortiGuard category blocking. Contact
Fortinet Technical Support to renew a FortiGuard license after the free trial.
You can globally enable FortiGuard Web Filtering in System > Maintenance >
FortiGuard Center and then configure FortiGuard Web Filtering options for each
profile in Firewall > Protection Profiles. For more information, see “FortiGuard
Web Filtering options” on page 370.

FortiGuard Analysis and Management Service is a subscription-based service
that provides remote management services, including logging and reporting
capabilities for all FortiGate units. These services were previously only available
on FortiAnalyzer and FortiManager units.
The subscription-based service is available from the FortiGuard Analysis and
Management Service portal web site, which provides a central location for
configuring logging and reporting and remote management, including viewing
subscription contract information, such as daily quota and the expiry date of the
service.
Configuring the FortiGate unit for FDN and FortiGuard subscription services
FDN updates, as well as FortiGuard services, are configured in System >
Maintenance > FortiGuard. The FDN page contains four sections of FortiGuard
services.
The four sections are:
• Support Contract and FortiGuard Subscription Services
• AntiVirus and IPS Downloads
• Web Filtering and AntiSpam Options
• Management and Analysis Service Options

01-30007-0203-20090112 243
Support Contract and FortiGuard Subscription Services

The Support Contract and FortiGuard Subscription Services sections are
displayed in abbreviated form on the System Status page. See “Viewing system
status” on page 67.
Figure 140:Support Contract and FortiGuard Subscription Services section
Support Contract The availability or status of your FortiGate unit support contract. The
status displays can be one of the following: Unreachable, Not
Registered or Valid Contract.
If Valid Contract is shown, the FortiOS firmware version and contract
expiry date displays. A green checkmark also displays.
[Register] Select to register your FortiGate unit support contract.
This displays only when the support contract is not
registered.
FortiGuard Availability and status information for each of the FortiGuard
Subscription subscription services including:
Services • AntiVirus
AV Definitions
• Intrusion Protection
IPS Definitions
• Web Filtering
• AntiSpam
• Management Service
• Analysis Service
[Availability] The availability of this service on this FortiGate unit,
dependent on your service subscription. The status can
be one of the following:
• Unreachable
• Not Registered
• Valid License
• Valid Contract
The option Subscribe displays if Availability is Not
Registered.
The option Renew displays if Availability has expired.
[Update] Select to manually update this service on your FortiGate
unit. This will prompt you to download the update file
from your local computer. Select Update Now to
immediately download current updates from FDN directly.
[Register] Select to register the service. This displays in
Management Service and Analysis Service.

244 01-30007-0203-20090112
[Renew] Select to renew the service. This displays in

Management Service and Analysis Service.
Status Icon Indicates the status of the subscription service. The icon
corresponds to the availability description.
• Grey (Unreachable) – FortiGate unit is not able to
connect to service
• Orange (Not Registered) – FortiGate unit can
connect, but has no subscription registered for this
service
• Yellow (Expired) – FortiGate unit had a valid license
that expired
• Green (Valid license) – FortiGate unit can connect to
FDN and has a registered support contract
If the Status Icon is green, the expiry date displays.
[Version] The version number of the definition file currently
installed on the FortiGate unit for this service.
[Last update The date of the last update and method used for last
date and attempt to download definition updates for this service.
method]
[Date] Local system date when the FortiGate unit last checked
for updates for this service.
AntiVirus and IPS Downloads

The Antivirus and IPS Options section enables you to schedule antivirus and IPS
updates, configure an override server, or allow push updates. You can access
these options by selecting the Expand Arrow.
The SETUP message that the FortiGate unit sends when you enable push
updates includes the IP address of the FortiGate interface that the FDN connects
to. The “Use override push IP” option is used when your FortiGate unit is behind a
NAT device. The FortiGate unit sends the FDS the IP and port numbers of the
NAT device to the FDS. The NAT device must also be configured to forward the
FDS traffic to the FortiGate unit on port 9443.
For more information, see “Enabling push updates through a NAT device” on
page 251.
Figure 141:AntiVirus and IPS Options section

Expand Arrow

01-30007-0203-20090112 245
Use override server Select to configure an override server if you cannot connect to the
address FDN or if your organization provides updates using their own
FortiGuard server.
When selected, enter the IP address or domain name of a
FortiGuard server and select Apply. If the FDN Status still indicates
no connection to the FDN, see “Troubleshooting FDN connectivity”
on page 248.
Allow Push Update Select to allow push updates. Updates are sent to your FortiGate
unit when they are available, without having to check if they are
available.
Push Update Status Icon shows the status of the push update
service.
Allow Push The status of the FortiGate unit for receiving push
Update status updates:
icon • Grey (Unreachable) - FortiGate unit is not able
to connect to push update service
• Yellow (Not Available) - push update service is
not available with current support license
• Green (Available) - push update service is
allowed. See “” on page 251.
If the icon is either grey or yellow, see
“Troubleshooting FDN connectivity” on page 248.
Use override Available only if both “Use override server address”
push IP and “Allow Push Update” are enabled.
Select to allow you to create a forwarding policy
that redirects incoming FDS push updates to your
FortiGate unit.
Enter the IP address of the NAT device in front of
your FortiGate unit. FDS will connect to this device
when attempting to reach the FortiGate unit.
The NAT device must be configured to forward the
FDS traffic to the FortiGate unit on UDP port 9443.
See “Enabling push updates through a NAT
device” on page 251.
Port Select the port on the NAT device that will receive
the FDS push updates. This port must be
forwarded to UDP port 9443 on the FortiGate unit.
Available only if “Use override push” is enabled.
Schedule Updates Select this check box to enable scheduled updates.
Every Attempt to update once every 1 to 23 hours. Select
the number of hours between each update
request.
Daily Attempt to update once a day. You can specify the
hour of the day to check for updates. The update
attempt occurs at a randomly determined time
within the selected hour.
Weekly Attempt to update once a week. You can specify
the day of the week and the hour of the day to
check for updates. The update attempt occurs at a
randomly determined time within the selected hour.
Update Now Select Update Now to manually initiate an FDN update.
Submit attack Fortinet recommends that you select this check box. It helps to
characteristics … improve the quality of IPS signature.
(recommended)

246 01-30007-0203-20090112
Web Filtering and AntiSpam Options

You can access this section by selecting the Expand Arrow to view the Web
Filtering and AntiSpam Options options.
Figure 142:Web Filtering and AntiSpam Options section
Enable Select to enable FortiGuard Web Filter service.

Web Filter
Enable Cache Select to enable caching of web filter queries.
This improves performance by reducing FortiGate unit
requests to the FortiGuard server. The cache uses 6 percent of
the FortiGate memory. When the cache is full, the least
recently used IP address or URL is deleted.
The Enable Cache is only available if Enable Web Filter is
selected.
TTL Time to live. The number of seconds to store blocked IP
addresses and URLs in the cache before contacting the server
again.
Available only if both Enable Web Filter and Enable Cache are
selected.
Enable Select to enable FortiGuard AnitSpam service.
AntiSpam
Enable Cache Select to enable caching of antispam queries.
This improves performance by reducing FortiGate unit
requests to the FortiGuard server. The cache uses 6 percent of
the FortiGate memory. When the cache is full, the least
recently used IP address or URL is deleted.
Available only if Enable Anti Spam is selected.
TTL Time to live. The number of seconds to store blocked IP
addresses and URLs in the cache before contacting the server
again.
Port Select one of the following ports for your web filtering and antispam
Section requirements:
Use Default Select to use port 53 for transmitting with FortiGuard Antispam
Port (53) servers.
Use Alternate Select to use port 8888 for transmitting with FortiGuard
Port (8888) Antispam servers.
Test Select to test the connection to the servers. Results are shown below the
Availability button and on the Status indicators.
please Select to re-evaluate a URL’s category rating on the FortiGuard Web Filter
click here service.

01-30007-0203-20090112 247
Troubleshooting FDN connectivity System Maintenance
Management and Analysis Service Options

The Management and Analysis Service Options section contains the Account ID
and other options regarding the FortiGuard Analysis and Management Service.
You can access this section by selecting the Expand Arrow to view the
Management and Analysis Service Options.
Figure 143:FortiGuard Management and Analysis Service options
Account ID Enter the name for the Management and Analysis Services that
identifies the account.
The account ID that you entered in the Account ID field when
registering is used in this field.
To launch the service Select to go directly to the FortiGuard Analysis and Management
portal, please click Service portal web site to either view logs or configuration. You
here can also select this to register your FortiGate unit with the
To configure...please Select the link, please click here, to configure and enable logging
click here. to the FortiGuard Analysis server. The link redirects you to
Log&Report > Log Config > Log Setting.
This displays only after registering for the service.
To purge...please Select the number of months from the list that will remove those
click here. logs from the FortiGuard Analysis server and select the link,
please click here. For example, if you select 2 months, the logs
from the past two months will be removed from the server.
You can also use this option to remove logs that may appear on a
current report.
This displays only after logging is enabled and log messages are
sent to the FortiGuard Analysis server.
Troubleshooting FDN connectivity

If your FortiGate unit is unable to connect to the FDN, check your configuration.
For example, you may need to add routes to the FortiGate routing table or
configure your network to allow the FortiGate unit to use HTTPS on port 443 to
connect to the Internet.
You might have to connect to an override FortiGuard server to receive updates.
For more information, see “To add an override server” on page 250. If this is not
successful, check your configuration to make sure you can connect to the override
FortiGuard server from the FortiGate unit.
Push updates might be unavailable if:
• you have not registered the FortiGate unit (Go to Product Registration and
follow the instructions on the web site if you have not already registered your
FortiGate unit).
• there is a NAT device installed between the FortiGate unit and the FDN (see
“Enabling push updates through a NAT device” on page 251).
• your FortiGate unit connects to the Internet using a proxy server (see “To
enable scheduled updates through a proxy server” on page 250).

248 01-30007-0203-20090112
System Maintenance Updating antivirus and attack definitions
Updating antivirus and attack definitions

Use the following procedures to configure the FortiGate unit to connect to the
FDN to update the antivirus (including grayware) definitions and IPS attack
definitions.
Updating antivirus and IPS attack definitions can cause a very short disruption in
traffic scanning while the FortiGate unit applies the new signature definitions.
Fortinet recommends scheduling updates when traffic is light to minimize
disruption.
To make sure the FortiGate unit can connect to the FDN

1 Go to System > Status and select “Change” on the System Time line in the
System Information section.
Verify that the time zone is set correctly for the region where your FortiGate unit is
located.
2 Go to System > Maintenance > FortiGuard.
3 Select the Expand Arrow beside Web Filtering and AntiSpam Options to reveal
the available options.
4 Select Test Availability.
The FortiGate unit tests its connection to the FDN. The test results displays at the
top of the FortiGuard page.
To update antivirus and attack definitions

2 Select the Expand Arrow beside Antivirus and IPS Options to reveal the available
options.
3 Select Update Now to update the antivirus and attack definitions.
If the connection to the FDN or override server is successful, the web-based
manager displays a message similar to the following:
Your update request has been sent. Your database will be
updated in a few minutes. Please check your update page for
the status of the update.
After a few minutes, if an update is available, the FortiGuard page lists new
version information for antivirus definitions and IPS attack definitions. The page
also displays new dates and version numbers for the updated definitions and
engines. Messages are recorded to the event log, indicating whether the update
was successful or not.
To enable scheduled updates

2 Select the Expand Arrow beside AntiVirus and IPS Options to reveal the available
options.
3 Select the Scheduled Update check box.
4 Select one of the following:

01-30007-0203-20090112 249
Enabling push updates System Maintenance
Every Once every 1 to 23 hours. Select the number of hours and minutes between
each update request.
Daily Once a day. You can specify the time of day to check for updates.
Weekly Once a week. You can specify the day of the week and the time of day to
check for updates.
5 Select Apply.
The FortiGate unit starts the next scheduled update according to the new update
schedule.
Whenever the FortiGate unit runs a scheduled update, the event is recorded in the
FortiGate event log.
If you cannot connect to the FDN, or if your organization provides antivirus and
IPS attack updates using their own FortiGuard server, you can use the following
procedure to add the IP address of an override FortiGuard server.
To add an override server

2 Select the Use override server address check box.
3 Type the fully qualified domain name or IP address of the FortiGuard server.
4 Select Apply.
The FortiGate unit tests the connection to the override server.
If the FortiGuard Distribution Network availability icon changes from gray to green,
the FortiGate unit has successfully connected to the override server.
If the FortiGuard Distribution Network availability icon stays gray, the FortiGate
unit cannot connect to the override server. Check the FortiGate configuration and
network configuration for settings that would prevent the FortiGate unit from
connecting to the override FortiGuard server.
To enable scheduled updates through a proxy server

If your FortiGate unit must connect to the Internet through a proxy server, you can
use the config system autoupdate tunneling command syntax to allow
the FortiGate unit to connect (or tunnel) to the FDN using the proxy server. For
more information, see the FortiGate CLI Reference.
Enabling push updates

The FDN can push updates to FortiGate units to provide the fastest possible
response to critical situations. You must register the FortiGate unit before it can
receive push updates. Register your FortiGate unit by going to the Fortinet
Support web site, Product Registration, and follow the instructions.
When you configure a FortiGate unit to allow push updates, the FortiGate unit
sends a SETUP message to the FDN. The next time new antivirus or IPS attack
definitions are released, the FDN notifies all FortiGate units that are configured for
push updates, that a new update is available. Within 60 seconds of receiving a
push notification, the FortiGate unit requests the update from the FDN.

250 01-30007-0203-20090112
System Maintenance Enabling push updates
When the network configuration permits, configuring push updates is

recommended in addition to configuring scheduled updates. On average the
FortiGate unit receives new updates sooner through push updates than if the
FortiGate unit receives only scheduled updates. Scheduled updates ensures that
the FortiGate unit receives current updates.
Enabling push updates is not recommended as the only method for obtaining
updates. The FortiGate unit might not receive the push notification. When the
FortiGate unit receives a push notification, it makes only one attempt to connect to
the FDN and download updates.
Push updates when FortiGate IP addresses changes

The SETUP message that the FortiGate unit sends when you enable push
updates includes the IP address of the FortiGate interface that the FDN connects
to. The interface used for push updates is the interface configured in the default
route of the static routing table.
The FortiGate unit sends the SETUP message if you:
• change the IP address of this interface manually
• have set the interface addressing mode to DHCP or PPPoE and your DHCP or
PPPoE server changes the IP address.
The FDN must be able to connect to this IP address for your FortiGate unit to be
able to receive push update messages. If your FortiGate unit is behind a NAT
device, see “Enabling push updates through a NAT device” on page 251.
If you have redundant connections to the Internet, the FortiGate unit also sends
the SETUP message when one Internet connection goes down and the FortiGate
unit fails over to another Internet connection.
In Transparent mode, if you change the management IP address, the FortiGate
unit also sends the SETUP message to notify the FDN of the address change.
Enabling push updates through a NAT device

If the FDN connects only to the FortiGate unit through a NAT device, you must
configure port forwarding on the NAT device and add the port forwarding
information to the push update configuration. Port forwarding enables the FDN to
connect to the FortiGate unit using UDP on either port 9443 or an override push
port that you specify.
If the external IP address of the NAT device is dynamic (PPPoE or DHCP), the
FortiGate unit is unable to receive push updates through a NAT device.
The following procedures configure the FortiGate unit to push updates through a
NAT Device. These procedures also include adding port forwarding virtual IP and
a firewall policy to the NAT device.
Figure 144:Example network: Push updates through a NAT device
Virtual IP
172.16.35.144 10.20.6.135
(external interface) (external interface)
Internet
FDN
Internal Network Server
FortiGate unit NAT Device

01-30007-0203-20090112 251
Enabling push updates System Maintenance
The procedure, General procedure, configures both the FortiGate unit and NAT
device so that they FortiGate unit can receive push updates.
General procedure
1 Register the FortiGate unit on the internal network so that it has a current support
license and can receive push updates.
2 Configure the following FortiGuard options on the FortiGate unit on the internal
network.
• Allow push updates
• Add an override push update IP. Usually this would be the IP address of the
external interface of the NAT device
• If required, change the override push update port
3 Add a port forwarding virtual IP to the NAT device.
• Set the external IP address of the virtual IP to match the override push update
IP. Usually this would be the IP address of the external interface of the NAT
device.
4 Add a firewall policy to the FortiGate NAT device that includes the port forwarding
virtual IP.
Note: Push updates are not supported if the FortiGate unit must use a proxy server to
connect to the FDN. See “To enable scheduled updates through a proxy server” on
page 250 for more information.
To configure FortiGuard options on the FortiGate unit on the internal

network
2 Select the Expand Arrow beside AntiVirus and IPS Options to reveal the available
options.
3 Select the Allow Push Update check box.
4 Select the Use override push IP check box.
5 Enter the IP address of the external interface of the NAT device.
UDP port 9943 is changed only if it is blocked or in use.
6 Select Apply.
You can add changes to the Use override push configuration if the external IP
address of the external service port changes; select Apply to update the push
information on the FDN.
The FortiGate unit sends the override push IP address and port to the FDN. The
FDN now uses this IP address and port for push updates to the FortiGate unit on
the internal network. Push updates will not actually work until a virtual IP is added
to the NAT device so that the NAT device accepts push update packets and
forwards them to the FortiGate unit on the internal network.
The following procedure, To add a port forwarding virtual IP to the FortiGate NAT
device, enables you to configure the NAT device to use port forwarding to push
update connections from the FDN to the FortiGate unit on the internal network.

252 01-30007-0203-20090112
System Maintenance Enabling push updates
To add a port forwarding virtual IP to the FortiGate NAT device

1 Go to Firewall > Virtual IP.
3 Enter the appropriate information for the following:
Name Enter a name for the Virtual IP.

External Select an external interface from the list. This is the interface on the
Interface NAT device that connects to the Internet.
Type Select Static NAT. If you select Server Load Balance, additional
options display. For more information, see “Firewall Virtual IP” on
page 333.
External IP Enter the IP address and/or range. This is the IP address that the FDN
Address/Range connects to send push updates to the FortiGate unit on the internal
network. This would usually be the IP address of the external interface
of the NAT device. This IP address must be the same as the IP in
“User override push update” for the FortiGate unit on the internal
network.
Mapped IP Enter the IP address and/or range of the FortiGate unit on the Internal
Address/Range network.
Port Forwarding Select Port Forwarding. When you select Port Forwarding, the options
Protocol, External Services Port and Map to Port appear.
Protocol Select UDP.
External Service Enter the external service port. The external service port is the port
Port that the FDN connects to. The external service port for push updates
is usually 9443. If you changed the push update port in the FortiGuard
configuration of the FortiGate unit on the internal network, you must
set the external service port to the changed push update port.
Map to Port Select HTTP Multiplexing to enable the FortiGate unit to use its HTTP
proxy to multiplex multiple client connections destined for the web
server into fewer connections, improving performance.
Preserve Client IP is available only when HTTP Multiplexing is
selected. This preserves the IP address of the client in the X-
Forwarded-For HTTP header.
4 Select OK.
To add a firewall policy to the FortiGate NAT device

3 Configure the external to internal firewall policy.
4 Select OK.
Verify that push updates to the FortiGate unit on the internal network are working
by going to System > Maintenance > FortiGuard and select Test Availability.
The Push Update indicator should change to green.

01-30007-0203-20090112 253
License System Maintenance
License
If you have a FortiGate-3000 unit or higher, you can purchase a license key from
Fortinet to increase the maximum number of VDOMs to 25, 50, 100 or 250. By
default, FortiGate units support a maximum of 10 VDOMs.
The license key is a 32-character string supplied by Fortinet. Fortinet requires the
serial number of the FortiGate unit to generate the license key.
The license key is entered in System > Maintenance > License in the Input
License Key field. This appears only on the FortiGate-3000 unit and higher. The
following does not appear on any other FortiGate unit.
Figure 145:License key for additional VDOMs
Current License The current maximum number of Virtual Domains.

Input License Key Enter the license key supplied by Fortinet and select Apply.
Note: VDOMs created on a registered FortiGate unit are considered real devices by the
FortiAnalyzer unit and it includes VDOMs in the total number of registered devices. For
example, three FortiGate units are registered on the FortiAnalyzer unit and contain four
VDOMs: the total number of registered FortiGate units on the FortiAnalyzer unit is seven.
For more information, see the FortiAnalyzer Administration Guide.

254 01-30007-0203-20090112
Router Static Routing concepts
Router Static
This section explains some general routing concepts, and how to define static
routes and route policies.
A route provides the FortiGate unit with the information it needs to forward a
packet to a particular destination on the network. A static route causes packets to
be forwarded to a destination other than the factory configured default gateway.
The factory configured static default route provides you with a starting point to
configure the default gateway. You must either edit the factory configured static
default route to specify a different default gateway for the FortiGate unit, or delete
the factory configured route and specify your own static default route that points to
the default gateway for the FortiGate unit. See “Default route and default gateway”
on page 259.
You define static routes manually. Static routes control traffic exiting the FortiGate
unit—you can specify through which interface the packet will leave and to which
device the packet should be routed.
As an option, you can define route policies. Route policies specify additional
criteria for examining the properties of incoming packets. Using route policies, you
can configure the FortiGate unit to route packets based on the IP source and
destination addresses in packet headers and other criteria such as on which
interface the packet was received and which protocol (service) and port are being
used to transport the packet.
If you enable virtual domains (VDOMs) on the FortiGate unit, static routing is
configured separately for each virtual domain. For details, see “Using virtual
• Routing concepts
• Static Route
• Policy Route
Routing concepts
The FortiGate unit works as a security device on a network and packets must
pass through it. You need to understand a number of basic routing concepts in
order to configure the FortiGate unit appropriately.
Whether you administer a small or large network, this module will help you
understand how the FortiGate unit performs routing functions.
The following topics are covered in this section:
• How the routing table is built
• How routing decisions are made
• Multipath routing and determining the best routeRoute priority
• Route priority
• Blackhole Route

01-30007-0203-20090112 255
Routing concepts Router Static
How the routing table is built

In the factory default configuration, the FortiGate routing table contains a single
static default route. You can add routing information to the routing table by defining
additional static routes. The table may include several different routes to the same
destination—the IP addresses of the next-hop router specified in those routes or
the FortiGate interfaces associated with those routes may vary.
The FortiGate unit selects the “best” route for a packet by evaluating the
information in the routing table. The best route to a destination is typically
associated with the shortest distance between the FortiGate unit and the closest
next-hop router. In some cases, the next best route may be selected if the best
route is unavailable. The FortiGate unit installs the best available routes in the
unit’s forwarding table, which is a subset of the unit’s routing table. Packets are
forwarded according to the information in the forwarding table.
How routing decisions are made

Whenever a packet arrives at one of the FortiGate unit’s interfaces, the unit
determines whether the packet was received on a legitimate interface by doing a
reverse lookup using the source IP address in the packet header. If the FortiGate
unit cannot communicate with the computer at the source IP address through the
interface on which the packet was received, the FortiGate unit drops the packet as
it is likely a hacking attempt.
If the destination address can be matched to a local address (and the local
configuration permits delivery), the FortiGate unit delivers the packet to the local
network. If the packet is destined for another network, the FortiGate unit forwards
the packet to a next-hop router according to a policy route and the information
stored in the FortiGate forwarding table. See “Policy Route” on page 263.
Multipath routing and determining the best route

Multipath routing occurs when more than one entry to the same destination is
present in the routing table. When multipath routing happens, the FortiGate unit
may have several possible destinations for an incoming packet, forcing the
FortiGate unit to decide which next-hop is the best one.
Two methods to manually resolve multiple routes to the same destination are to
lower the administrative distance of one route or to set the priority of both routes.
For the FortiGate unit to select a primary (preferred) route, manually lower the
administrative distance associated with one of the possible routes.
Administrative distance is based on the expected reliability of a given route. It is
determined through a combination of the number of hops from the source and the
protocol used. More hops from the source means more possible points of failure.
The administrative distance can be from 1 to 255, with lower numbers being
preferred. A distance of 255 is seen as infinite and will not be installed in the
routing table. Here is an example to illustrate how administration distance works—
if there are two possible routes traffic can take between 2 destinations with
administration distances of 5 (always up) and 31 (sometimes not available), the
traffic will use the route with an administrative distance of 5. Different routing
protocols have different default administrative distances. The default
administrative distances for any of these routing protocols are configurable.

256 01-30007-0203-20090112
Router Static Routing concepts
Table 36: Default administrative distances for routing protocols
Routing protocol Default administrative distance

Direct physical connection 1
Static 10
EBGP 20
RIP 120
OSPF 110
IBGP 200
Another method is to manually change the priority of both of the routes. If the
next-hop administrative distances of two routes on the FortiGate unit are equal, it
may not be clear which route the packet will take. Configuring the priority for each
of those routes will make it clear which next-hop will be used in the case of a tie.
You can set the priority for a route only from the CLI. Lower priorities are
preferred. For more information see the FortiGate CLI Reference.
All entries in the routing table are associated with an administrative distance. If the
routing table contains several entries that point to the same destination (the
entries may have different gateways or interface associations), the FortiGate unit
compares the administrative distances of those entries, selects the entries having
the lowest distances, and installs them as routes in the FortiGate forwarding table.
As a result, the FortiGate forwarding table contains only those routes having the
lowest distances to every possible destination. For information about how to
change the administrative distance associated with a static route, see “Adding a
static route to the routing table” on page 262.
Route priority
After the FortiGate unit selects static routes for the forwarding table based on their
administrative distances, the priority field of those routes determines routing
preference.
You configure the priority field through the CLI. The route with the lowest value in
the priority field is considered the best route, and it is also the primary route. The
command to set the priority field is: set priority <integer> under the
config route static command. For more information, see the FortiGate CLI
Reference.
In summary, because you can use the CLI to specify which sequence numbers or
priority field settings to use when defining static routes, you can prioritize routes to
the same destination according to their priority field settings. For a static route to
be the preferred route, you must create the route using the config router
static CLI command and specify a low priority for the route. If two routes have
the same administrative distance and the same priority, then they are equal cost
multipath (ECMP) routes.
Since this means there is more than one route to the same destination, it can be
confusing which route or routes to install and use. However, if you have enabled
load balancing with ECMP routes, then different sessions will resolve this problem
by using different routes to the same address. For more information, see load
balancing in “Configuring virtual IPs” on page 338.

01-30007-0203-20090112 257
Static Route Router Static
Blackhole Route
A blackhole route is a route that drops all traffic sent to it. It is very much like
/dev/null in Linux programming.
Blackhole routes are used to dispose of packets instead of responding to
suspicious inquiries. This provides added security since the originator will not
discover any information from the target network.
Blackhole routes can also limit traffic on a subnet. If some subnet addresses are
not in use, traffic to those addresses (traffic which may be valid or malicious) can
be directed to a blackhole for added security and to reduce traffic on the subnet.
The loopback interface, a virtual interface that does not forward traffic, was added
to enable easier configuration of blackhole routing. Similar to a normal interface,
this loopback interface has fewer parameters to configure, and all traffic sent to it
stops there. Since it cannot have hardware connection or link status problems, it is
always available, making it useful for other dynamic routing roles. Once
configured, you can use a loopback interface in firewall policies, routing, and other
places that refer to interfaces. You configure this feature only from the CLI. For
more information see the system chapter of the FortiGate CLI Reference.
Static Route
You configure static routes by defining the destination IP address and netmask of
packets that you intend the FortiGate unit to intercept, and by specifying a
(gateway) IP address for those packets. The gateway address specifies the next-
hop router to which traffic will be routed.
Note: You can use the config router static6 CLI command to add, edit, or delete
static routes for IPv6 traffic. For more information, see the “router” chapter of the FortiGate
CLI Reference.
Working with static routes

The Static Route list displays information that the FortiGate unit compares to
packet headers in order to route packets. Initially, the list contains the factory
configured static default route. See “Default route and default gateway” on
page 259. You can add new entries manually.
When you add a static route to the Static Route list, the FortiGate unit performs a
check to determine whether a matching route and destination already exist in the
FortiGate routing table. If no match is found, the FortiGate unit adds the route to
the routing table.
When IPv6 is enabled in the GUI, IPv6 routes are visible on the Static Route list.
Otherwise, IPv6 routes are not displayed. For more information on IPv6 see
“FortiGate IPv6 support” on page 217.
Note: Unless otherwise specified, static route examples and procedures are for IPv4 static
routes.
To view the static route list, go to Router > Static > Static Route.

258 01-30007-0203-20090112
Router Static Static Route
Figure 146 shows the static route list belonging to a FortiGate unit that has
interfaces named “port1” and “port2”. The names of the interfaces on your
FortiGate unit may be different.
Figure 146:Static Route list when IPv6 is enabled in the GUI
Expand
Arrow
Delete
Edit
Create New Add a static route to the Static Route list. For more information, see
“Adding a static route to the routing table” on page 262.
Select the down arrow to create an IPv6 static Route.
Route Select the Expand Arrow to display or hide the IPv4 static routes. By
default these routes are displayed.
This is displayed only when IPv6 is enabled in the GUI.
IPv6 Route Select the Expand Arrow to display or hide the IPv6 static routes. By
default these routes are hidden.
This is displayed only when IPv6 is enabled in the GUI.
IP/Mask The destination IP addresses and network masks of packets that the
FortiGate unit intercepts.
Gateway The IP addresses of the next-hop routers to which intercepted packets
are forwarded.
Device The names of the FortiGate interfaces through which intercepted
packets are received and sent.
Distance The administrative distances associated with each route. The values
represent distances to next-hop routers.
Delete and Edit Delete or edit an entry in the list.
icons
Default route and default gateway

In the factory default configuration, entry number 1 in the Static Route list is
associated with a destination address of 0.0.0.0/0.0.0.0, which means any/all
destinations. This route is called the “static default route”. If no other routes are
present in the routing table and a packet needs to be forwarded beyond the
FortiGate unit, the factory configured static default route causes the FortiGate unit
to forward the packet to the default gateway.
To prevent this you must either edit the factory configured static default route to
specify a different default gateway for the FortiGate unit, or delete the factory
configured route and specify your own static default route that points to the default
gateway for the FortiGate unit.
Note: For network traffic to pass, even with the correct routes configured, you must have
the appropriate firewall policies. For details, see “Configuring firewall policies” on page 297.

01-30007-0203-20090112 259
For example, Figure 147 shows a FortiGate unit connected to a router. To ensure
that all outbound packets destined to any network beyond the router are routed to
the correct destination, you must edit the factory default configuration and make
the router the default gateway for the FortiGate unit.
Figure 147:Making a router the default gateway
Internet
Gateway
Router
192.168.10.1
external
FortiGate_1
internal
Internal network
192.168.20.0/24
To route outbound packets from the internal network to destinations that are not
on network 192.168.20.0/24, you would edit the default route and include the
following settings:
• Destination IP/mask: 0.0.0.0/0.0.0.0
• Gateway: 192.168.10.1
• Device: Name of the interface connected to network 192.168.10.0/24
(for example “external”).
• Distance: 10
The Gateway setting specifies the IP address of the next-hop router interface to
the FortiGate external interface. The interface behind the router (192.168.10.1) is
the default gateway for FortiGate_1.
In some cases, there may be routers behind the FortiGate unit. If the destination
IP address of a packet is not on the local network but is on a network behind one
of those routers, the FortiGate routing table must include a static route to that
network. For example, in Figure 148, the FortiGate unit must be configured with
static routes to interfaces 192.168.10.1 and 192.168.11.1 in order to forward
packets to Network_1 and Network_2 respectively.

260 01-30007-0203-20090112
Router Static Static Route
Figure 148:Destinations on networks behind internal routers
Internet
FortiGate_1
internal dmz
Gateway / Router_1 Gateway / Router_2
192.168.10.1 192.168.11.1
Network_1 Network_2
192.168.20.0/24 192.168.30.0/24
To route packets from Network_1 to Network_2, Router_1 must be configured to

use the FortiGate internal interface as its default gateway. On the FortiGate unit,
you would create a new static route with these settings:
Destination IP/mask: 192.168.30.0/24
Gateway: 192.168.11.1
Device: dmz
Distance: 10
To route packets from Network_2 to Network_1, Router_2 must be configured to
use the FortiGate dmz interface as its default gateway. On the FortiGate unit, you
would create a new static route with these settings:
Destination IP/mask: 192.168.20.0/24
Gateway: 192.168.10.1
Device: internal
Distance: 10
Changing the gateway for the default route

The default gateway determines where packets matching the default route will be
forwarded.
Note: If you are using DHCP or PPPoE FortiGate over a modem interface on your
FortiGate unit, you may have problems configuring a static route. After trying to either
Renew your DHCP license, or Reconnect the PPPoE connection, go to the CLI and enable
dynamic-gateway under config system interface for the modem interface. Doing
this will remove the need to specify a gateway for this interface’s route. For more
information see FortiGate CLI Reference.

01-30007-0203-20090112 261
To change the gateway for the default route

1 Go to Router > Static > Static Route.
2 Select the Edit icon in row 1.
3 If the FortiGate unit reaches the next-hop router through an interface other than
the interface that is currently selected in the Device field, select the name of the
interface from the Device field.
4 In the Gateway field, type the IP address of the next-hop router to which outbound
traffic may be directed.
5 In the Distance field, optionally adjust the administrative distance value.
6 Select OK.
Adding a static route to the routing table

A route provides the FortiGate unit with the information it needs to forward a
packet to a particular destination. A static route causes packets to be forwarded to
a destination other than the default gateway.
You define static routes manually. Static routes control traffic exiting the FortiGate
unit—you can specify through which interface the packet will leave and to which
device the packet should be routed.
To add a static route entry

1 Go to Router > Static > Static Route.
3 Enter the IP address and netmask. For example, 172.1.2.0/255.255.255.0 would
be a route for all addresses on the subnet 172.1.2.x .
4 Enter the FortiGate unit interface closest to this subnet, or connected to it.
5 Enter the gateway IP address. Continuing with the example 172.1.2.3 would be a
valid address.
6 Enter the administrative distance of this route.
The administrative distance allows you to weight one route to be preferred over
another. This is useful when one route is unreliable. For example, if route A has an
administrative distance of 30 and route B has an administrative distance of 10, the
preferred route is route A with the smaller administrative distance of 10. If you
discover that route A is unreliable, you can change the administrative distance for
route A from 10 to 40, which will make the route B the preferred route.
7 Select OK to confirm and save your new static route.
When you add a static route through the web-based manager, the FortiGate unit
assigns the next unassigned sequence number to the route automatically and
adds the entry to the Static Route list.
Figure 149 shows the Edit Static Route dialog box belonging to a FortiGate unit
that has an interface named “internal”. The names of the interfaces on your

262 01-30007-0203-20090112
Router Static Policy Route
Figure 149:Edit Static Route
Destination Type the destination IP address and network mask of packets that the
IP/Mask FortiGate unit has to intercept. The value 0.0.0.0/0.0.0.0 is reserved
for the default route.
Gateway Type the IP address of the next-hop router to which the FortiGate unit will
forward intercepted packets.
Device Select the name of the FortiGate interface through which the intercepted
packets may be routed to the next-hop router.
Distance Type an administrative distance from 1 to 255 for the route. The distance
value is arbitrary and should reflect the distance to the next-hop router. A
lower value indicates a more preferred route.
Policy Route
A routing policy allows you to redirect traffic away from a static route. This can be
useful if you want to route certain types of network traffic differently. You can use
incoming traffic’s protocol, source address or interface, destination address, or
port number to determine where to send the traffic. For example, generally
network traffic would go to the router of a subnet, but you might want to direct
SMTP or POP3 traffic addressed to that subnet directly to the mail server.
If you have configured the FortiGate unit with routing policies and a packet arrives
at the FortiGate unit, the FortiGate unit starts at the top of the Policy Route list and
attempts to match the packet with a policy. If a match is found and the policy
contains enough information to route the packet (a minimum of the IP address of
the next-hop router and the FortiGate interface for forwarding packets to it), the
FortiGate unit routes the packet using the information in the policy. If no policy
route matches the packet, the FortiGate unit routes the packet using the routing
table.
Note: Most policy settings are optional, so a matching policy alone might not provide
enough information for forwarding the packet. The FortiGate unit may refer to the routing
table in an attempt to match the information in the packet header with a route in the routing
table. For example, if the outgoing interface is the only item in the policy, the FortiGate unit
looks up the IP address of the next-hop router in the routing table. This situation could
happen when the interfaces are dynamic (such as DHCP or PPPoE) and you do not want
or are unable to specify the IP address of the next-hop router.
Policy route options define which attributes of a incoming packet cause policy
routing to occur. If the attributes of a packet match all the specified conditions, the
FortiGate unit routes the packet through the specified interface to the specified
gateway.
Figure 150 shows the policy route list belonging to a FortiGate unit that has
interfaces named “external” and “internal”. The names of the interfaces on your

01-30007-0203-20090112 263
Policy Route Router Static
To edit an existing policy route, see “Adding a policy route” on page 264.
Figure 150:Policy Route list
Delete
Edit
Move To
Create New Add a policy route. See “Adding a policy route” on page 264.
# The ID numbers of configured route policies. These numbers are sequential
unless policies have been moved within the table.
Incoming The interfaces on which packets subjected to route policies are received.
Outgoing The interfaces through which policy routed packets are routed.
Source The IP source addresses and network masks that cause policy routing to
occur.
Destination The IP destination addresses and network masks that cause policy routing to
occur.
Delete icon Delete a policy route.
Edit icon Edit a policy route.
Move To After selecting this icon, enter the destination position in the window that
icon appears, and select OK.
For more information, see “Moving a policy route” on page 265.
Adding a policy route

To add a policy route, go to Router > Static > Policy Route and select Create
New.
Figure 151 shows the New Routing Policy dialog box belonging to a FortiGate unit
that has interfaces named “external” and “internal”. The names of the interfaces
on your FortiGate unit may be different.
Figure 151:New Routing Policy
Protocol To perform policy routing based on the value in the protocol field of
the packet, enter the protocol number to match. The Internet
Protocol Number is found in the IP packet header, and RFC 5237
includes a list of the assigned protocol numbers. The range is from 0
to 255. A value of 0 disables the feature.

264 01-30007-0203-20090112
Router Static Policy Route
Incoming Interface Select the name of the interface through which incoming packets
subjected to the policy are received.
Source Address / To perform policy routing based on the IP source address of the
Mask packet, type the source address and network mask to match. A value
of 0.0.0.0/0.0.0.0 disables the feature.
Destination To perform policy routing based on the IP destination address of the
Address / Mask packet, type the destination address and network mask to match. A
value of 0.0.0.0/0.0.0.0 disables the feature.
Destination Ports To perform policy routing based on the port on which the packet is
received, type the same port number in the From and To fields. To
apply policy routing to a range of ports, type the starting port number
in the From field and the ending port number in the To field. A value
of 0 disables this feature.
The Destination Ports fields are only used for TCP and UDP
protocols. The ports are skipped over for all other protocols.
Type of Service Use a two digit hexadecimal bit pattern to match to define the
service, or use a two digit hexadecimal bit mask to mask out.
For example if you want the policy to apply to service 14 you would
use a bit pattern of 0E. If you wanted to ignore all odd numbered
services you would use a bit mask of 01.
Outgoing Interface Select the name of the interface through which packets affected by
the policy will be routed.
Gateway Address Type the IP address of the next-hop router that the FortiGate unit can
access through the specified interface. A value of 0.0.0.0 is not
valid.
Moving a policy route

A routing policy is added to the bottom of the routing table when it is created. If
you prefer to use one policy over another, you may want to move it to a different
location in the routing policy table.
The option to use one of two routes happens when both routes are a match, for
example 172.20.0.0/255.255.0.0 and 172.20.120.0/255.255.255.0. If both of
these routes are in the policy table, both can match a route to 172.20.120.112 but
you consider the second one as a better match. In that case the best match route
should be positioned before the other route in the policy table.
In the case of two matches in the routing table, alternating sessions will use both
routes in a load balancing configuration. You can also manually assign priorities to
routes. For two matches in the routing table, the priority will determine which route
is used. This feature is available only through the CLI. For details, see FortiGate
CLI Reference.
To change the position of a policy route in the table, go to Router > Static >
Policy Route and select Move To for the policy route you want to move.
Figure 152:Moving a policy route
Before/After Select Before to place the selected Policy Route before the
indicated route. Select After to place it following the indicated
route.
Policy route ID Enter the Policy route ID of the route in the Policy route table to
move the selected route before or after.

01-30007-0203-20090112 265
Policy Route Router Static

266 01-30007-0203-20090112
Router Dynamic
Router Dynamic
This section explains how to configure dynamic protocols to route traffic through
large or complex networks. Dynamic routing protocols enable the FortiGate unit to
automatically share information about routes with neighboring routers and learn
about routes and networks advertised by them. The FortiGate unit supports these
dynamic routing protocols:
• Routing Information Protocol (RIP)
• Open Shortest Path First (OSPF)
• Border Gateway Protocol (BGP).
Note: You can configure basic RIP, OSPF, and BGP routing options through the web-based
manager. Many additional options are available but only through the CLI. For complete
descriptions and examples of how to use CLI commands to configure RIP, OSPF, and BGP
settings, see the “config router” chapter of FortiGate CLI Reference.
The FortiGate unit selects routes and updates its routing table dynamically based
on the rules you specify. Given a set of rules, the unit can determine the best route
or path for sending packets to a destination. You can also define rules to suppress
the advertising of routes to neighboring routers and change FortiGate routing
information before it is advertised.
If you enable virtual domains (VDOMs) on the FortiGate unit, dynamic routing is
Note: A FortiGate unit can operate as a Protocol Independent Multicast (PIM) version 2
router in the root virtual domain. FortiGate units support PIM sparse mode and dense mode
and can service multicast servers or receivers on the network segment to which a FortiGate
interface is connected. PIM can use static routes, RIP, OSPF, or BGP to forward multicast
packets to their destinations.
Bi-Directional Forwarding (BFD) is a protocol that works with BGP and OSPF to
quickly discover routers on the network that cannot be contacted, and to re-route
traffic accordingly until those routers can be contacted.
• RIP
• OSPF
• BGP
• Multicast
• Bi-directional Forwarding Detection (BFD)

01-30007-0203-20090112 267
RIP Router Dynamic
RIP
Routing Information Protocol (RIP) is a distance-vector routing protocol intended
for small, relatively homogeneous networks. The FortiGate implementation of RIP
supports RIP version 1 (see RFC 1058) and RIP version 2 (see RFC 2453).
How RIP works

When RIP is enabled, the FortiGate unit broadcasts requests for RIP updates
from each of its RIP-enabled interfaces. Neighboring routers respond with
information from their routing tables. The FortiGate unit adds routes from
neighbors to its own routing table only if those routes are not already recorded in
the routing table. When a route already exists in the routing table, the unit
compares the advertised route to the recorded route and chooses the shortest
route for the routing table.
RIP uses hop count as the metric for choosing the best route. A hop count of 1
represents a network that is connected directly to the unit, while a hop count of 16
represents a network that the FortiGate unit cannot reach. Each network that a
packet travels through to reach its destination usually counts as one hop. When
the FortiGate unit compares two routes to the same destination, it adds the route
having the lowest hop count to the routing table.
Similarly, when RIP is enabled on an interface, the FortiGate unit sends RIP
responses to neighboring routers on a regular basis. The updates provide
information about the routes in the FortiGate routing table, subject to the rules that
you specify for advertising those routes. You can specify how often the FortiGate
unit sends updates, how long a route can be kept in the routing table without being
updated, and, for routes that are not updated regularly, how long the unit
advertises the route as unreachable before it is removed from the routing table.
Viewing and editing basic RIP settings

When you configure RIP settings, you have to specify the networks that are
running RIP and specify any additional settings needed to adjust RIP operation on
the FortiGate interfaces that are connected to the RIP-enabled network.
To view and edit RIP settings go to Router > Dynamic > RIP.
Figure 153 shows the basic RIP settings on a FortiGate unit that has interfaces
named “dmz” and “external”. The names of the interfaces on your FortiGate unit
may be different.

268 01-30007-0203-20090112
Router Dynamic RIP
Figure 153:Basic RIP settings
Expand
Arrow
Delete
Edit
RIP Version Select the level of RIP compatibility needed at the FortiGate unit. You can
enable global RIP settings on all FortiGate interfaces connected to RIP-
enabled networks:
• Select 1 to send and receive RIP version 1 packets.
• Select 2 to send and receive RIP version 2 packets.
You can override the global settings for a specific FortiGate interface if
required. For more information, see “Configuring a RIP-enabled interface”
on page 272.
Advanced Select the Expand Arrow to view or hide advanced RIP options. For more
Options information, see “Selecting advanced RIP options” on page 270.
Networks The IP addresses and network masks of the major networks (connected to
the FortiGate unit) that run RIP. When you add a network to the Networks
list, the FortiGate interfaces that are part of the network are advertised in
RIP updates. You can enable RIP on all FortiGate interfaces whose IP
addresses match the RIP network address space.
IP/Netmask Enter the IP address and netmask that defines the RIP-
enabled network.
Add Select to add the network information to the Networks
list.

01-30007-0203-20090112 269
RIP Router Dynamic
Interfaces Any additional settings needed to adjust RIP operation on a FortiGate

interface.
Create New Add new RIP operating parameters for an interface.
These parameters will override the global RIP settings
for that interface. For more information, see
“Configuring a RIP-enabled interface” on page 272.
Interface The name of the unit RIP interface.
Send Version The version of RIP used to send updates through each
interface: 1, 2, or both.
Receive Version The versions of RIP used to listen for updates on each
interface: 1, 2, or both.
Authentication The type of authentication used on this interface: None,
Text or MD5.
Passive Permissions for RIP broadcasts on this interface. A
green checkmark means the RIP broadcasts are
blocked.
Delete and Delete or edit a RIP network entry or a RIP interface definition.
Edit icons
Selecting advanced RIP options

With advanced RIP options, you can specify settings for RIP timers and define
metrics for redistributing routes that the FortiGate unit learns through some means
other than RIP updates. For example, if the unit is connected to an OSPF or BGP
network or you add a static route to the FortiGate routing table manually, you can
configure the unit to advertise those routes on RIP-enabled interfaces.
To select advanced RIP options, go to Router > Dynamic > RIP and expand
Advanced Options. After you select the options, select Apply.
Note: You can configure additional advanced options through the CLI. For example, you
can filter incoming or outgoing updates by using a route map, an access list, or a prefix list.
The FortiGate unit also supports offset lists, which add the specified offset to the metric of a
route. For more information, see the “router” chapter of the FortiGate CLI Reference.
Figure 154:Advanced Options (RIP)
Expand
Arrow
Rip Version Select the version of RIP packets to send and receive.
Advanced Options Select the Expand Arrow to view or hide advanced options.

270 01-30007-0203-20090112
Router Dynamic RIP
Default Metric Enter the default hop count that the FortiGate unit should assign
to routes that are added to the FortiGate routing table. The range
is from 1 to 16. This metric is the hop count, with 1 being best or
shortest.
This value also applies to Redistribute unless otherwise specified.
Default-information- Select to generate and advertise a default route into the FortiGate
originate unit’s RIP-enabled networks. The generated route may be based
on routes learned through a dynamic routing protocol, routes in
the routing table, or both.
RIP Timers Enter new values to override the default RIP timer settings. The
default settings are effective in most configurations — if you
change these settings, ensure that the new settings are
compatible with local routers and access servers.
If the Update timer is smaller than Timeout or Garbage timers,
you will get an error.
Update Enter the amount of time (in seconds) that the
FortiGate unit will wait between sending RIP
updates.
Timeout Enter the maximum amount of time (in seconds)
that a route is considered reachable while no
updates are received for the route. This is the
maximum time the FortiGate unit will keep a
reachable route in the routing table while no
updates for that route are received. If the FortiGate
unit receives an update for the route before the
timeout period expires, the timer is restarted.
The Timeout period should be at least three times
longer than the Update period.
Garbage Enter the amount of time (in seconds) that the
FortiGate unit will advertise a route as being
unreachable before deleting the route from the
routing table. The value determines how long an
unreachable route is kept in the routing table.
Redistribute Select one or more of the options to redistribute RIP updates
about routes that were not learned through RIP. The FortiGate
unit can use RIP to redistribute routes learned from directly
connected networks, static routes, OSPF, and BGP.
Connected Select to redistribute routes learned from directly
connected networks. To specify a hop count for
those routes, select Metric, and enter the hop count
in the Metric field. The valid hop count range is from
1 to 16.
Static Select to redistribute routes learned from static
routes. To specify a hop count for those routes,
select Metric, and enter the hop count in the Metric
field. The range is from 1 to 16.
OSPF Select to redistribute routes learned through OSPF.
To specify a hop count for those routes, select
Metric, and enter the hop count in the Metric field.
The range is from 1 to 16.
BGP Select to redistribute routes learned through BGP.
To specify a hop count for those routes, select
Metric, and enter the hop count in the Metric field.
The range is from 1 to 16.

01-30007-0203-20090112 271
RIP Router Dynamic
Configuring a RIP-enabled interface

You can use RIP interface options to override the global RIP settings that apply to
all FortiGate unit interfaces connected to RIP-enabled networks. For example, if
you want to suppress RIP advertising on an interface that is connected to a subnet
of a RIP-enabled network, you can set the interface to operate passively. Passive
interfaces listen for RIP updates but do not respond to RIP requests.
If RIP version 2 is enabled on the interface, you can optionally choose password
authentication to ensure that the FortiGate unit authenticates a neighboring router
before accepting updates from that router. The unit and the neighboring router
must both be configured with the same password. Authentication guarantees the
authenticity of the update packet, not the confidentiality of the routing information
in the packet.
To set specific RIP operating parameters for a RIP-enabled interface, go to
Router > Dynamic > RIP and select Create New.
Note: Additional options such as split-horizon and key-chains can be configured per
interface through the CLI. For more information, see the “router” chapter of the FortiGate
CLI Reference or the Fortinet Knowledge Center.
Figure 155 shows the New/Edit RIP Interface dialog box belonging to a FortiGate
unit that has an interface named “internal”. The names of the interfaces on your
Figure 155:New/Edit RIP Interface
Interface Select the name of the FortiGate interface to which these settings
apply. The interface must be connected to a RIP-enabled network.
The interface can be a virtual IPSec or GRE interface.
Send Version, Select to override the default RIP-compatibility setting for sending
Receive Version and receiving updates through the interface: RIP version 1, version 2
or Both.
Authentication Select an authentication method for RIP exchanges on the specified
interface:
• Select None to disable authentication.
• If the interface is connected to a network that runs RIP version 2,
optionally select Text and type a password (up to 35 characters)
in the Password field. The FortiGate unit and the RIP updates
router must both be configured with the same password. The
password is sent in clear text over the network.
• Select MD5 to authenticate the exchange using MD5.
Passive Interface Select to suppress the advertising of FortiGate unit routing
information over the specified interface. Clear the check box to allow
the interface to respond normally to RIP requests.

272 01-30007-0203-20090112
Router Dynamic OSPF
OSPF
Open Shortest Path First (OSPF) is a link-state routing protocol that is most often
used in large heterogeneous networks to share routing information among routers
in the same Autonomous System (AS). FortiGate units support OSPF version 2
(see RFC 2328).
The main benefit of OSPF is that it advertises routes only when neighbors change
state instead of at timed intervals, so routing overhead is reduced.
How OSPF works

An OSPF network consists of one or more Autonomous Systems (ASes). An
OSPF AS is typically divided into logical areas linked by Area Border Routers. A
group of contiguous networks form an area. An Area Border Router (ABR) links
one or more ASes to the OSPF network backbone (area ID 0). For information on
configuring an OSPF AS, see “Defining an OSPF AS—Overview” on page 274.
When a FortiGate unit interface is connected to an OSPF area, that unit can
participate in OSPF communications. FortiGate units use the OSPF Hello protocol
to acquire neighbors in an area. A neighbor is any router that directly connected to
the same area as the FortiGate unit. After initial contact, the FortiGate unit
exchanges Hello packets with its OSPF neighbors regularly to confirm that the
neighbors can be reached.
OSPF-enabled routers generate Link-State Advertisements (LSA) and send them
to their neighbors whenever the status of a neighbor changes or a new neighbor
comes online. As long as the OSPF network is stable, LSAs between OSPF
neighbors do not occur. An LSA identifies the interfaces of all OSPF-enabled
routers in an area, and provides information that enables OSPF-enabled routers
to select the shortest path to a destination. All LSA exchanges between OSPF-
enabled routers are authenticated.
The FortiGate unit maintains a database of link-state information based on the
advertisements that it receives from OSPF-enabled routers. To calculate the best
route (shortest path) to a destination, the FortiGate unit applies the Shortest Path
First (SPF) algorithm to the accumulated link-state information. OSPF uses
relative path cost metric for choosing the best route. The path cost can be any
metric, but is typically the speed of the path—how fast traffic will get from one
point to another. The path cost, similar to “distance” for RIP, imposes a penalty on
the outgoing direction of a FortiGate interface. The path cost of a route is
calculated by adding together all of the costs associated with the outgoing
interfaces along the path to a destination. The lowest overall path cost indicates
the best route, and generally the fastest route.
Note: The inter-area routes may not be calculated when a Cisco type ABR has no fully
adjacent neighbor in the backbone area. In this situation, the router considers summary-
LSAs from all Actively summary-LSAs from all Actively Attached areas (RFC 3509).
The FortiGate unit dynamically updates its routing table based on the results of
the SPF calculation to ensure that an OSPF packet will be routed using the
shortest path to its destination. Depending on the network topology, the entries in
the FortiGate routing table may include:
• the addresses of networks in the local OSPF area (to which packets are sent
directly)

01-30007-0203-20090112 273
OSPF Router Dynamic
• routes to OSPF area border routers (to which packets destined for another
area are sent)
• if the network contains OSPF areas and non-OSPF domains, routes to AS
boundary routers, which reside on the OSPF network backbone and are
configured to forward packets to destinations outside the OSPF AS.
The number of routes that a FortiGate unit can learn through OSPF depends on
the network topology. A single unit can support tens of thousands of routes if the
OSPF network is configured properly.
Defining an OSPF AS—Overview

Defining an OSPF Autonomous System (AS), involves:
• defining the characteristics of one or more OSPF areas
• creating associations between the OSPF areas that you defined and the local
networks to include in the OSPF AS
• if required, adjusting the settings of OSPF-enabled interfaces.
If you are using the web-based manager to perform these tasks, follow the
procedures summarized below.
To define an OSPF AS
1 Go to Router > Dynamic > OSPF.
2 Under Areas, select Create New.
3 Define the characteristics of one or more OSPF areas. See “Defining OSPF
areas” on page 278.
4 Under Networks, select Create New.
5 Create associations between the OSPF areas that you defined and the local
networks to include in the OSPF AS. See “Specifying OSPF networks” on
page 279.
6 If you need to adjust the default settings of an OSPF-enabled interface, select
Create New under Interfaces.
7 Select the OSPF operating parameters for the interface. See “Selecting operating
parameters for an OSPF interface” on page 279.
Repeat steps 6 and 7 for any additional OSPF-enabled interfaces.
8 Optionally select advanced OSPF options for the OSPF AS. See “Selecting
advanced OSPF options” on page 277.
9 Select Apply.
Configuring basic OSPF settings

When you configure OSPF settings, you have to define the AS in which OSPF is
enabled and specify which of the FortiGate interfaces participate in the AS. As
part of the AS definition, you specify the AS areas and specify which networks to
include those areas. You may optionally adjust the settings associated with OSPF
operation on the FortiGate interfaces.
To view and edit OSPF settings, go to Router > Dynamic > OSPF.
Figure 156 shows the basic OSPF settings on a FortiGate unit that has an
interface named “port1”. The names of the interfaces on your FortiGate unit may
be different.

274 01-30007-0203-20090112
Router Dynamic OSPF
Figure 156:Basic OSPF settings
Expand
Arrow
Router ID Enter a unique router ID to identify the FortiGate unit to other OSPF routers.
By convention, the router ID is the numerically highest IP address assigned
to any of the FortiGate interfaces in the OSPF AS.
If you change the router ID while OSPF is configured on an interface, all
connections to OSPF neighbors will be broken temporarily. The connections
will re-establish themselves.
If Router ID is not explicitly set, the highest IP address of the VDOM or unit
will be used.
Advanced Select the Expand Arrow to view or hide advanced OSPF settings. For more
Options information, see “Selecting advanced OSPF options” on page 277.

01-30007-0203-20090112 275
OSPF Router Dynamic
Areas Information about the areas making up an OSPF AS. The header of an
OSPF packet contains an area ID, which helps to identify the origination of a
packet inside the AS.
Create New Define and add a new OSPF area to the Areas list. For
more information, see “Defining OSPF areas” on page 278.
Area The unique 32-bit identifiers of areas in the AS, in dotted-
decimal notation. Area ID 0.0.0.0 references the backbone
of the AS and cannot be changed or deleted.
Type The types of areas in the AS:
• Regular - a normal OSPF area
• NSSA - a not so stubby area
• Stub - a stub area.
For more information, see “Defining OSPF areas” on
page 278.
Authentication The methods for authenticating OSPF packets sent and
received through all FortiGate interfaces linked to each
area:
• None - authentication is disabled
• Text - text-based authentication is enabled
• MD5 - MD5 authentication is enabled.
A different authentication setting may apply to some of the
interfaces in an area, as displayed under Interfaces. For
example, if an area employs simple passwords for
authentication, you can configure a different password for
one or more of the networks in that area.
Networks The networks in the OSPF AS and their area IDs. When you add a network
to the Networks list, all FortiGate interfaces that are part of the network are
advertised in OSPF link-state advertisements. You can enable OSPF on all
FortiGate interfaces whose IP addresses match the OSPF network address
space. For more information, see “Specifying OSPF networks” on page 279.
Create New Add a network to the AS, specify its area ID, and add the
definition to the Networks list.
Network The IP addresses and network masks of networks in the AS
on which OSPF runs. The FortiGate unit may have physical
or VLAN interfaces connected to the network.
Area The area IDs that have been assigned to the OSPF network
address space.
Interfaces Any additional settings needed to adjust OSPF operation on a FortiGate
interface. For more information, see “Selecting operating parameters for an
OSPF interface” on page 279.
Create New Create additional/different OSPF operating parameters for a
unit interface and add the configuration to the Interfaces list.
Name The names of OSPF interface definitions.
Interface The names of FortiGate physical or VLAN interfaces having
OSPF settings that differ from the default values assigned to
all other interfaces in the same area.
IP The IP addresses of the OSPF-enabled interfaces having
additional/different settings.
Authentication The methods for authenticating LSA exchanges sent and
received on specific OSPF-enabled interfaces. These
settings override the area Authentication settings.
Delete and Delete or edit an OSPF area entry, network entry, or interface definition.
Edit icons Icons are visible only when there are entries in Areas, Networks, and
Interfaces sections.

276 01-30007-0203-20090112
Router Dynamic OSPF
Selecting advanced OSPF options

By selecting advanced OSPF options, you can specify metrics for redistributing
routes that the FortiGate unit learns through some means other than OSPF link-
state advertisements. For example, if the FortiGate unit is connected to a RIP or
BGP network or you add a static route to the FortiGate routing table manually, you
can configure the unit to advertise those routes on OSPF-enabled interfaces.
To select advanced RIP options, go to Router > Dynamic > RIP and expand
Advanced Options. After you select the options, select Apply.
Figure 157:Advanced Options (OSPF)
Expand
Arrow
Router ID Enter a unique router ID to identify the FortiGate unit to other OSPF
routers.
Expand Arrow Select to view or hide Advanced Options.
Default Generate and advertise a default (external) route to the OSPF AS. You
Information may base the generated route on routes learned through a dynamic
routing protocol, routes in the routing table, or both.
None Prevent the generation of a default route.
Regular Generate a default route into the OSPF AS and advertise the
route to neighboring autonomous systems only if the route is
stored in the FortiGate routing table.
Always Generate a default route into the OSPF AS and advertise the
route to neighboring autonomous systems unconditionally,
even if the route is not stored in the FortiGate routing table.
Redistribute Select one or more of the options listed to redistribute OSPF link-state
advertisements about routes that were not learned through OSPF. The
FortiGate unit can use OSPF to redistribute routes learned from directly
connected networks, static routes, RIP, and BGP.
Connected Select to redistribute routes learned from directly connected
networks.
Enter a cost for those routes in the Metric field. The range is
from 1 to 16 777 214.
Static Select to redistribute routes learned from static routes.
from 1 to 16 777 214.
RIP Select to redistribute routes learned through RIP.
from 1 to 16 777 214.
BGP Select to redistribute routes learned through BGP.
from 1 to 16 777 214.
Note: You can configure many additional advanced OSPF options through the CLI. For
details, see the “router” chapter of the FortiGate CLI Reference.

01-30007-0203-20090112 277
OSPF Router Dynamic
Defining OSPF areas

An area logically defines part of the OSPF AS. Each area is identified by a 32-bit
area ID expressed in dotted-decimal notation, for example 192.168.0.1. Area ID
0.0.0.0 is reserved for the OSPF network backbone. You can classify the
remaining areas of an AS as regular, stub, or NSSA.
A regular area contains more than one router, each having at least one OSPF-
enabled interface to the area.
To reach the OSPF backbone, the routers in a stub area must send packets to an
area border router. Routes leading to non-OSPF domains are not advertised to
the routers in stub areas. The area border router advertises to the OSPF AS a
single default route (destination 0.0.0.0) into the stub area, which ensures that any
OSPF packet that cannot be matched to a specific route will match the default
route. Any router connected to a stub area is considered part of the stub area.
In a Not-So-Stubby Area (NSSA), routes that lead out of the area into a non-OSPF
domain are made known to OSPF AS. However, the area itself continues to be
treated like a stub area by the rest of the AS.
Regular areas and stub areas (including not-so-stubby areas) are connected to
the OSPF backbone through area border routers.
To define an OSPF area, go to Router > Dynamic > OSPF, and then under
Areas, select Create New. To edit the attributes of an OSPF area, go to Router >
Dynamic > OSPF and select the Edit icon in the row that corresponds to the area.
Note: If required, you can define a virtual link to an area that has lost its physical
connection to the OSPF backbone. Virtual links can be set up only between two FortiGate
units that act as area border routers. For more information on virtual links, see the
Figure 158:New/Edit OSPF Area
Area Type a 32-bit identifier for the area. The value must resemble an IP
address in dotted-decimal notation. Once you have created the OSPF
area, the area IP value cannot be changed; you must delete the area
and restart.
Type Select an area type to classify the characteristics of the network that will
be assigned to the area:
• Regular - If the area contains more than one router, each having at
least one OSPF-enabled interface to the area.
• NSSA - If you want routes to external non-OSPF domains made
known to OSPF AS and you want the area to be treated like a stub
area by the rest of the AS.
• STUB - If the routers in the area must send packets to an area border
router in order to reach the backbone and you do not want routes to
non-OSPF domains to be advertised to the routers in the area.

278 01-30007-0203-20090112
Router Dynamic OSPF
Authentication Select the method for authenticating OSPF packets sent and received
through all interfaces in the area:
• None - Disable authentication.
• Text - Enables text-based password authentication. to authenticate
LSA exchanges using a plain-text password. The password is sent in
clear text over the network.
• MD5 - Enable MD5-based authentication using an MD5
cryptographic hash (RFC 1321).
If required, you can override this setting for one or more of the interfaces
in the area. For more information, see “Selecting operating parameters
for an OSPF interface” on page 279.
Note: To assign a network to the area, see “Specifying OSPF networks” on page 279.
Specifying OSPF networks

OSPF areas group a number of contiguous networks together. When you assign
an area ID to a network address space, the attributes of the area are associated
with the network.
To assign an OSPF area ID to a network, go to Router > Dynamic > OSPF, and
then under Networks, select Create New. To change the OSPF area ID assigned
to a network, go to Router > Dynamic > OSPF and select the Edit icon in the row
that corresponds to the network.
Figure 159:New/Edit OSPF Network
IP/Netmask Enter the IP address and network mask of the local network that you want
to assign to an OSPF area.
Area Select an area ID for the network. The attributes of the area must match
the characteristics and topology of the specified network. You must define
the area before you can select the area ID. For more information, see
“Defining OSPF areas” on page 278.
Selecting operating parameters for an OSPF interface

An OSPF interface definition contains specific operating parameters for a
FortiGate OSPF-enabled interface. The definition includes the name of the
interface (for example, external or VLAN_1), the IP address assigned to the
interface, the method for authenticating LSA exchanges through the interface,
and timer settings for sending and receiving OSPF Hello and dead-interval
packets.
You can enable OSPF on all FortiGate interfaces whose IP addresses match the
OSPF-enabled network space. For example, define an area of 0.0.0.0 and the
OSPF network as 10.0.0.0/16. Then define vlan1 as 10.0.1.1/24, vlan2 as
10.0.2.1/24 and vlan3 as 10.0.3.1/24. All three VLANs can run OSPF in area
0.0.0.0. To enable all interfaces, you would create an OSPF network 0.0.0.0/0 .

01-30007-0203-20090112 279
OSPF Router Dynamic
You can configure different OSPF parameters for the same FortiGate interface
when more than one IP address has been assigned to the interface. For example,
the same FortiGate interface could be connected to two neighbors through
different subnets. You could configure an OSPF interface definition containing one
set of Hello and dead-interval parameters for compatibility with one neighbor’s
settings, and a second OSPF interface definition for the same interface to ensure
compatibility with the second neighbor’s settings.
To select OSPF operating parameters for a FortiGate interface, go to Router >
Dynamic > OSPF, and then under Interfaces, select Create New. To edit the
operating parameters of an OSPF-enabled interface, go to Router > Dynamic >
OSPF and select the Edit icon in the row that corresponds to the OSPF-enabled
interface.
Figure 160 shows the New/Edit OSPF Interface dialog box belonging to a
FortiGate unit that has an interface named “port1”. The interface names on your
FortiGate unit may differ.
Figure 160:New/Edit OSPF Interface
Add
Name Enter a name to identify the OSPF interface definition. For example, the
name could indicate to which OSPF area the interface will be linked.
Interface Select the name of the FortiGate interface to associate with this OSPF
interface definition (for example, port1, external, or VLAN_1). The
FortiGate unit can have physical, VLAN, virtual IPSec or GRE interfaces
connected to the OSPF-enabled network.
IP Enter the IP address that has been assigned to the OSPF-enabled
interface. The interface becomes OSPF-enabled because its IP address
matches the OSPF network address space.
For example, if you defined an OSPF network of 172.20.120.0/24 and
port1 has been assigned the IP address 172.20.120.140, type
172.20.120.140.
Authentication Select an authentication method for LSA exchanges on the specified
interface:
• None - Disable authentication.
• Text - Authenticate LSA exchanges using a plain-text password. The
password can be up to 35 characters, and is sent in clear text over the
network.
• MD5 - Use one or more keys to generate an MD5 cryptographic hash.
Password Enter the plain-text password. Enter an alphanumeric value of up to 15
characters. The OSPF neighbors that send link-state advertisements to
this FortiGate interface must be configured with an identical password.
This field is available only if you selected plain-text authentication.

280 01-30007-0203-20090112
Router Dynamic BGP
MD5 Keys Enter the key identifier for the (first) password in the ID field (the range is
from 1 to 255) and then type the associated password in the Key field.
The password is a 128-bit hash, represented by an alphanumeric string of
up to 16 characters.
The OSPF neighbors that send link-state advertisements to this FortiGate
interface must be configured with an identical MD5 key. If the OSPF
neighbor uses more than one password to generate MD5 hash, select the
Add icon to add additional MD5 keys to the list.
This field is available only if you selected MD5 authentication.
Hello Interval Optionally, set the Hello Interval to be compatible with Hello Interval
settings on all OSPF neighbors.
This setting defines the period of time (in seconds) that the FortiGate unit
waits between sending Hello packets through this interface.
Dead Interval Optionally, set the Dead Interval to be compatible with Dead Interval
settings on all OSPF neighbors.
This setting defines the period of time (in seconds) that the FortiGate unit
waits to receive a Hello packet from an OSPF neighbor through the
interface. If the FortiGate unit does not receive a Hello packet within the
specified amount of time, the FortiGate unit declares the neighbor
inaccessible.
By convention, the Dead Interval value is usually four times greater than
the Hello Interval value.
BGP
Border Gateway Protocol (BGP) is an Internet routing protocol typically used by
ISPs to exchange routing information between different ISP networks. For
example, BGP enables the sharing of network paths between the ISP network
and an autonomous system (AS) that uses RIP, OSPF, or both to route packets
within the AS. The FortiGate implementation of BGP supports BGP-4 and
complies with RFC 1771.
How BGP works

When BGP is enabled on an interface, the FortiGate unit sends routing table
updates to neighboring autonomous systems connected to that interface
whenever any part of the FortiGate routing table changes. Each AS to which the
unit belongs is associated with an AS number. The AS number references a
particular destination network.
BGP updates advertise the best path to a destination network. When the
FortiGate unit receives a BGP update, the FortiGate unit examines the Multi-Exit
Discriminator (MED) attributes of potential routes to determine the best path to a
destination network before recording the path in the FortiGate unit routing table.
BGP has the capability to gracefully restart. This capability limits the effects of
software problems by allowing forwarding to continue when the control plane of
the router fails. It also reduces routing flaps by stabilizing the network.
Note: You can configure graceful restarting and other advanced settings only through CLI
commands. For more information on advanced BGP settings, see the “router” chapter of
the FortiGate CLI Reference.

01-30007-0203-20090112 281
BGP Router Dynamic
Viewing and editing BGP settings

When you configure BGP settings, you need to specify the AS to which the
FortiGate unit belongs and enter a router ID to identify this unit to other BGP
routers. You must also identify the FortiGate unit’s BGP neighbors and specify
which of the networks local to the FortiGate unit should be advertised to BGP
neighbors.
To view and edit BGP settings, go to Router > Dynamic > BGP. The web-based
manager offers a simplified user interface to configure basic BGP options. You
can also configure many advanced BGP options through the CLI. For more
information, see the “router” chapter of the FortiGate CLI Reference.
Figure 161:Basic BGP options
Delete
Local AS Enter the number of the local AS to which the FortiGate unit belongs.
Router ID Enter a unique router ID to identify the FortiGate unit to other BGP
routers. The router ID is an IP address written in dotted-decimal format,
for example 192.168.0.1.
If you change the router ID while BGP is configured on an interface, all
connections to BGP peers will be broken temporarily. The connections
will re-establish themselves.
If Router ID is not explicitly set, the highest IP address of the VDOM will
be used.
Neighbors The IP addresses and AS numbers of BGP peers in neighboring
autonomous systems.
IP Enter the IP address of the neighbor interface to the BGP-
enabled network.
Remote AS Enter the number of the AS that the neighbor belongs to.
Add/Edit Add the neighbor information to the Neighbors list, or edit
an entry in the list.
Neighbor The IP addresses of BGP peers.
Remote AS The numbers of the autonomous systems associated with
the BGP peers.
Delete icon Delete a BGP neighbor entry.

282 01-30007-0203-20090112
Router Dynamic Multicast
Networks The IP addresses and network masks of networks to advertise to BGP

peers. The FortiGate unit may have a physical or VLAN interface
connected to those networks.
IP/Netmask Enter the IP address and netmask of the network to be
advertised.
Add Add the network information to the Networks list.
Network The IP addresses and network masks of major networks
that are advertised to BGP peers.
Delete icon Delete a BGP network definition.
Multicast
A FortiGate unit can operate as a Protocol Independent Multicast (PIM) version 2
router in the root virtual domain. FortiGate units support PIM sparse mode (RFC
2362) and PIM dense mode (RFC 3973) and can service multicast servers or
receivers on the network segment to which a FortiGate interface is connected.
How multicast works

Multicast server applications use a (Class D) multicast address to send one copy
of a packet to a group of receivers. The PIM routers throughout the network
ensure that only one copy of the packet is forwarded through the network until it
reaches an end-point destination. At the end-point destination, copies of the
packet are made only when required to deliver the information to multicast client
applications that request traffic destined for the multicast address.
Note: To support PIM communications, the sending/receiving applications and all

connecting PIM routers in between must be enabled with PIM version 2. PIM can use static
routes, RIP, OSPF, or BGP to forward multicast packets to their destinations. To support
source-to-destination packet delivery, either sparse mode or dense mode must be enabled
on all the PIM-router interfaces. Sparse mode routers cannot send multicast messages to
dense mode routers. In addition, if a FortiGate unit is located between a source and a PIM
router, or between two PIM routers, or is connected directly to a receiver, you must create a
firewall policy manually to pass encapsulated (multicast) packets or decapsulated data (IP
traffic) between the source and destination.
A PIM domain is a logical area comprising a number of contiguous networks. The

domain contains at least one Boot Strap Router (BSR). If sparse mode is enabled,
the domain also contains a number of Rendezvous Points (RPs) and Designated
Routers (DRs). When you enable PIM on a FortiGate unit, the FortiGate unit can
perform any of these functions at any time as configured. If required for sparse
mode operation, you can define static RPs.
Note: You can configure basic options through the web-based manager. Many additional
options are available, but only through the CLI. For complete descriptions and examples of
how to use CLI commands to configure PIM settings, see multicast in the “router”
chapter of the FortiGate CLI Reference.
Note: For more information about FortiGate multicast support, see the FortiGate Multicast
Technical Note.

01-30007-0203-20090112 283
Multicast Router Dynamic
Viewing and editing multicast settings

When multicast (PIM) routing is enabled, you can configure sparse mode or dense
mode operation on any FortiGate interface.
To view and edit PIM settings, go to Router > Dynamic > Multicast. The web-
based manager offers a simplified user interface to configure basic PIM options.
You can also configure advanced PIM options through the CLI. For more
information, see the “router” chapter of the FortiGate CLI Reference.
Figure 162:Basic Multicast options
Add Static RP
Delete
Edit
Enable Multicast Select to enable PIM version 2 routing. A firewall policy must be
Routing created on PIM-enabled interfaces to pass encapsulated packets
and decapsulated data between the source and destination,
Add Static RP If required for sparse mode operation, enter the IP address of a
Rendezvous Point (RP) that may be used as the root of a packet
distribution tree for a multicast group. Join messages from the
multicast group are sent to the RP, and data from the source is
sent to the RP.
If an RP for the specified IP’s multicast group is already known to
the Boot Strap Router (BSR), the RP known to the BSR is used
and the static RP address that you specify is ignored.
Apply Save the specified static RP addresses.
Create New Create a new multicast entry for an interface.
You can use the new entry to fine-tune PIM operation on a specific
FortiGate interface or override the global PIM settings on a
particular interface. For more information, see “Overriding the
multicast settings on an interface” on page 285.
Interface The names of FortiGate interfaces having specific PIM settings.
Mode The mode of PIM operation (Sparse or Dense) on that interface.
Status The status of parse-mode RP candidacy on the interface.
To change the status of RP candidacy on an interface, select the
Edit icon in the row that corresponds to the interface.
Priority The priority number assigned to RP candidacy on that interface.
Available only when RP candidacy is enabled.
DR Priority The priority number assigned to Designated Router (DR)
candidacy on the interface. Available only when sparse mode is
enabled.
Delete and Edit icons Delete or edit the PIM settings on the interface.

284 01-30007-0203-20090112
Router Dynamic Multicast
Overriding the multicast settings on an interface

You use multicast (PIM) interface options to set operating parameters for
FortiGate interfaces connected to PIM domains. For example, you can enable
dense mode on an interface that is connected to a PIM-enabled network segment.
When sparse mode is enabled, you can adjust the priority number that is used to
advertise Rendezvous Point (RP) and/or Designated Router (DR) candidacy on
the interface.
Figure 163:Multicast interface settings
Interface Select the name of the root VDOM FortiGate interface to which
these settings apply. The interface must be connected to a PIM
version 2 enabled network segment.
PIM Mode Select the mode of operation: Sparse Mode or Dense Mode. All
PIM routers connected to the same network segment must be
running the same mode of operation. If you select Sparse Mode,
adjust the remaining options as described below.
DR Priority Enter the priority number for advertising DR candidacy on the
FortiGate unit’s interface. The range is from 1 to 4 294 967 295.
The unit compares this value to the DR interfaces of all other PIM
routers on the same network segment, and selects the router
having the highest DR priority to be the DR.
RP Candidate Enable RP candidacy on the interface.
RP Candidate Priority Enter the priority number for advertising RP candidacy on the
FortiGate interface. The range is from 1 to 255.
Multicast destination NAT

Multicast destination NAT (DNAT) allows you translate externally received
multicast destination addresses to addresses that conform to an organization's
internal addressing policy.
By using this feature that is available only in the CLI, you can avoid redistributing
routes at the translation boundary into their network infrastructure for Reverse
Path Forwarding (RPF) to work properly. They can also receive identical feeds
from two ingress points in the network and route them independently.
Configure multicast DNAT in the CLI by using the following command:
config firewall multicast-policy
edit p1
set dnat <dnatted-multicast-group>
set ...
next
end
For more information, see the “firewall” chapter of the FortiGate CLI Reference.

01-30007-0203-20090112 285
Bi-directional Forwarding Detection (BFD) Router Dynamic
Bi-directional Forwarding Detection (BFD)

The bi-directional Forwarding Detection (BFD) protocol is designed to deal with
dynamic routing protocols' lack of a fine granularity for detecting device failures on
the network and re-routing around those failures. BFD can more quickly react to
these failures, since it detects them on a millisecond timer, where other dynamic
routing protocols can only detect them on a second timer.
Your unit supports BFD as part of OSPF and BGP dynamic networking.
Note: You can configure BFD only from the CLI.
How BFD works

When you enable BFD on your FortiGate unit, BFD starts trying to connect to
other routers on the network. You can limit where BFD looks for routers by
enabling one interface only, and by enabling BFD for specific neighboring routers
on the network.
Once the connection has been made, BFD will continue to send periodic packets
to the router to make sure it is still operational. These small packets are sent
frequently.
If there is no response from the neighboring router within the set period of time,
BFD on your unit reports that router down and changes routing accordingly. BFD
continues to try to reestablish a connection with the non-responsive router.
Once that connection is reestablished, routes are reset to include the router once
again.
Configuring BFD
BFD is intended for networks that use BGP or OSPF routing protocols. This
generally excludes smaller networks.
BFD configuration on your FortiGate unit is very flexible. You can enable BFD for
the whole unit, and turn it off for one or two interfaces. Alternatively you can
specifically enable BFD for each neighbor router, or interface. Which method you
choose will be determined by the amount of configuring required for your network
The timeout period determines how long the unit waits before labeling a
connection as down. The length of the timeout period is important—if it is too short
connections will be labeled down prematurely, and if it is too long time will be
wasted waiting for a reply from a connection that is down. There is no easy
number, as it varies for each network and unit. High end FortiGate models will
respond very quickly unless loaded down with traffic. Also the size of the network
will slow down the response time—packets need to make more hops than on a
smaller network. Those two factors (CPU load and network traversal time) affect
how long the timeout you select should be. With too short a timeout period, BFD
will not connect to the network device but it will keep trying. This state generates
unnecessary network traffic, and leaves the device unmonitored. If this happens,
you should try setting a longer timeout period to allow BFD more time to discover
the device on the network.

286 01-30007-0203-20090112
Router Dynamic Bi-directional Forwarding Detection (BFD)
Configuring BFD on your FortiGate unit

For this example, BFD is enabled on the FortiGate unit using the default values.
This means that once a connection is established, your unit will wait for up to 150
milliseconds for a reply from a BFD router before declaring that router down and
rerouting traffic—a 50 millisecond minimum transmit interval multiplied by a
detection multiplier of 3. The port that BFD traffic originates from will be checked
for security purposes as indicated by disabling bfd-dont-enforce-src-port.
config system settings
set bfd enable
set bfd-desired-min-tx 50
set bfd-required-min-rx 50
set bfd-detect-mult 3
set bfd-dont-enforce-src-port disable
end
Note: The minimum receive interval (bfd-required-min-rx) and the detection

multiplier (bfd-detect-mult) combine to determine how long a period your unit will wait
for a reply before declaring the neighbor down. The correct value for your situation will vary
based on the size of your network and the speed of your unit’s CPU. The numbers used in
this example may not work for your network.
Disabling BFD for a specific interface

The previous example enables BFD for your entire FortiGate unit. If an interface is
not connected to any BFD enabled routers, you can reduce network traffic by
disabling BFD for that interface. For this example, BFD is disabled for the internal
interface using CLI commands.
config system interface
edit <interface>
set bfd disable
end
Configuring BFD on BGP

Configuring BFD on a BGP network involves only one step— enable BFD globally
and then disable it for each neighbor that is running the protocol.
set bfd enable
end
config router bgp

config neighbor
edit <ip_address>
set bfd disable
end
end

01-30007-0203-20090112 287
Bi-directional Forwarding Detection (BFD) Router Dynamic
Configuring BFD on OSPF

Configuring BFD on an OSPF network is very much like enabling BFD on your
unit—you can enable it globally for OSPF, and you can override the global settings
at the interface level.
To enable BFD on OSPF:
configure routing OSPF
set bfd enable
end
To override BFD on an interface:
configure routing OSPF
configure ospf-interface
edit <interface_name>
set bfd disable
end
end

288 01-30007-0203-20090112
Router Monitor Viewing routing information
Router Monitor
This section explains how to interpret the Routing Monitor list. The list displays the
entries in the FortiGate routing table.
If you enable virtual domains (VDOMs) on the FortiGate unit, router monitoring is
available separately for each virtual domain. For details, see “Using virtual
• Viewing routing information
• Searching the FortiGate routing table
Viewing routing information

By default, all routes are displayed in the Routing Monitor list. The default static
route is defined as 0.0.0.0/0, which matches the destination IP address of “any/all”
packets.
To display the routes in the routing table, go to Router > Monitor.
Figure 164 shows the Routing Monitor list belonging to a FortiGate unit that has
interfaces named “port1”, “port4”, and “lan”. The names of the interfaces on your
Figure 164:Routing Monitor list

01-30007-0203-20090112 289
Viewing routing information Router Monitor
IP version Select IPv4 or IPv6 routes.

Type Select one of the following route types to search the routing table and display
routes of the selected type only:
• All - all routes recorded in the routing table.
• Connected - all routes associated with direct connections to FortiGate
interfaces.
• Static - the static routes that have been added to the routing table
manually. For more information see “Static Route” on page 258.
• RIP - all routes learned through RIP. For more information see “RIP” on
page 268.
• OSPF - all routes learned through OSPF. For more information see
“OSPF” on page 273.
• BGP - all routes learned through BGP. For more information see “BGP” on
page 281
• HA - RIP, OSPF, and BGP routes synchronized between the primary unit
and the subordinate units of a high availability (HA) cluster. HA routes are
maintained on subordinate units and are visible only if you are viewing the
router monitor from a virtual domain that is configured as a subordinate
virtual domain in a virtual cluster. For details about HA routing
synchronization, see the FortiGate High Availability User Guide.
Network Enter an IP address and netmask (for example, 172.16.14.0/24) to
search the routing table and display routes that match the specified network.
Gateway Enter an IP address and netmask (for example, 192.168.12.1/32) to
search the routing table and display routes that match the specified gateway.
Apply Filter Select to search the entries in the routing table based on the specified search
criteria and display any matching routes.
Type The type values assigned to FortiGate routes (Static, Connected, RIP, OSPF,
or BGP).
Subtype If applicable, the subtype classification assigned to OSPF routes.
• An empty string implies an intra-area route. The destination is in an area
to which the FortiGate unit is connected.
• OSPF inter area - the destination is in the OSPF AS, but the FortiGate
unit is not connected to that area.
• External 1 - the destination is outside the OSPF AS. The metric of a
redistributed route is calculated by adding the external cost and the OSPF
cost together.
• External 2 - the destination is outside the OSPF AS. In this case, the
metric of the redistributed route is equivalent to the external cost only,
expressed as an OSPF cost.
• OSPF NSSA 1 - same as External 1, but the route was received through a
not-so-stubby area (NSSA).
• OSPF NSSA 2 - same as External 2, but the route was received through a
not-so-stubby area.
Network The IP addresses and network masks of destination networks that the
FortiGate unit can reach.
Distance The administrative distance associated with the route. A value of 0 means the
route is preferable compared to routes to the same destination.
To modify the administrative distance assigned to static routes, see “Adding a
static route to the routing table” on page 262. To modify this distance for
dynamic routes, see FortiGate CLI Reference.

290 01-30007-0203-20090112
Router Monitor Searching the FortiGate routing table
Metric The metric associated with the route type. The metric of a route influences
how the FortiGate unit dynamically adds it to the routing table. The following
are types of metrics and when they are applied.
• Hop count - routes learned through RIP.
• Relative cost - routes learned through OSPF.
• Multi-Exit Discriminator (MED) - routes learned through BGP. However,
several attributes in addition to MED determine the best path to a
destination network.
Gateway The IP addresses of gateways to the destination networks.
Interface The interface through which packets are forwarded to the gateway of the
destination network.
Up Time The total accumulated amount of time that a route learned through RIP,
OSPF, or BGP has been reachable.
Searching the FortiGate routing table

You can apply a filter to search the routing table and display certain routes only.
For example, you can display one or more static routes, connected routes, routes
learned through RIP, OSPF, or BGP, and routes associated with the network or
gateway that you specify.
If you want to search the routing table by route type and further limit the display
according to network or gateway, all of the values that you specify as search
criteria must match corresponding values in the same routing table entry in order
for that entry to be displayed (an implicit AND condition is applied to all of the
search parameters you specify).
For example, if the FortiGate unit is connected to network 172.16.14.0/24 and you
want to display all directly connected routes to network 172.16.14.0/24, you must
select Connected from the Type list, type 172.16.14.0/24 in the Network field,
and then select Apply Filter to display the associated routing table entry or entries.
Any entry that contains the word “Connected” in its Type field and the specified
value in the Gateway field will be displayed.
To search the FortiGate routing table

1 Go to Router > Monitor > Routing Monitor.
2 From the Type list, select the type of route to display. For example, select
Connected to display all connected routes, or select RIP to display all routes
learned through RIP.
3 If you want to display routes to a specific network, type the IP address and
netmask of the network in the Networks field.
4 If you want to display routes to a specific gateway, type the IP address of the
gateway in the Gateway field.
5 Select Apply Filter.
Note: All of the values that you specify as search criteria must match corresponding values
in the same routing table entry in order for that entry to be displayed.

01-30007-0203-20090112 291
Searching the FortiGate routing table Router Monitor

292 01-30007-0203-20090112
Firewall Policy How list order affects policy matching
Firewall Policy
Firewall policies control all traffic attempting to pass through the FortiGate unit,
between FortiGate interfaces, zones, and VLAN subinterfaces.
Firewall policies are instructions the FortiGate unit uses to decide connection
acceptance and packet processing for traffic attempting to pass through. When
the firewall receives a connection packet, it analyzes the packet’s source address,
destination address, and service (by port number), and attempts to locate a
firewall policy matching the packet.
Firewall policies can contain many instructions for the FortiGate unit to follow
when it receives matching packets. Some instructions are required, such as
whether to drop or accept and process the packets, while other instructions, such
as logging and authentication, are optional.
Policy instructions may include network address translation (NAT), or port address
translation (PAT), by using virtual IPs or IP pools to translate source and
destination IP addresses and port numbers. For details on using virtual IPs and IP
pools, see “Firewall Virtual IP” on page 333.
Policy instructions may also include protection profiles, which can specify
application-layer inspection and other protocol-specific protection and logging. For
details on using protection profiles, see “Firewall Protection Profile” on page 365.
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall policies are
configured separately for each virtual domain, and you must first enter the virtual
domain to configure its firewall policies. For details, see “Using virtual domains” on
page 95.
• How list order affects policy matching
• Multicast policies
• Viewing the firewall policy list
• Configuring firewall policies
• Firewall policy examples
How list order affects policy matching

Each time a FortiGate unit receives a connection attempting to pass through one
of its interfaces, the unit searches its firewall policy list for a matching firewall
policy.
The search begins at the top of the policy list and progresses in order towards the
bottom. The FortiGate unit evaluates each policy in the firewall policy list for a
match until a match is found. When the FortiGate unit finds the first matching
policy, it applies the matching policy’s specified actions to the packet, and
disregards subsequent firewall policies. Matching firewall policies are determined
by comparing the firewall policy and the packet’s:
• source and destination interfaces

01-30007-0203-20090112 293
How list order affects policy matching Firewall Policy
• source and destination firewall addresses

• services
• time/schedule.
If no policy matches, the connection is dropped.
As a general rule, you should order the firewall policy list from most specific to
most general because of the order in which policies are evaluated for a match,
and because only the first matching firewall policy is applied to a connection.
Subsequent possible matches are not considered or applied. Ordering policies
from most specific to most general prevents policies that match a wide range of
traffic from superseding and effectively masking policies that match exceptions.
For example, you might have a general policy that allows all connections from the
internal network to the Internet, but want to make an exception that blocks FTP. In
this case, you would add a policy that denies FTP connections above the general
policy.
Figure 165:Example: Blocking FTP — Correct policy order
}Exception
}General
FTP connections would immediately match the deny policy, blocking the
connection. Other kinds of services do not match the FTP policy, and so policy
evaluation would continue until reaching the matching general policy. This policy
order has the intended effect. But if you reversed the order of the two policies,
positioning the general policy before the policy to block FTP, all connections,
including FTP, would immediately match the general policy, and the policy to block
FTP would never be applied. This policy order would not have the intended effect.
Figure 166:Example: Blocking FTP — Incorrect policy order
}General
}Exception
Similarly, if specific traffic requires authentication, IPSec VPN, or SSL VPN, you
would position those policies above other potential matches in the policy list.
Otherwise, the other matching policies could always take precedence, and the
required authentication, IPSec VPN, or SSL VPN might never occur.
Note: A default firewall policy may exist which accepts all connections. You can move,
disable or delete it. If you move the default policy to the bottom of the firewall policy list and
no other policy matches the packet, the connection will be accepted. If you disable or delete
the default policy and no other policy matches the packet, the connection will be dropped.
Moving a policy to a different position in the policy list

You can arrange the firewall policy list to influence the order in which policies are
evaluated for matches with incoming traffic. When more than one policy has been
defined for the same interface pair, the first matching firewall policy will be applied
to the traffic session. For more information, see “How list order affects policy
matching” on page 293.
Moving a policy in the firewall policy list does not change its ID, which only
indicates the order in which the policy was created.

294 01-30007-0203-20090112
Firewall Policy Multicast policies
Figure 167:Move Policy
To move a firewall policy in the firewall policy list

2 In the firewall policy list, note the ID of a firewall policy that is before or after your
intended destination.
3 In the row corresponding to the firewall policy that you want to move, select the
Move To icon.
4 Select Before or After, and enter the ID of the firewall policy that is before or after
your intended destination. This specifies the policy’s new position in the firewall
policy list.
5 Select OK.
Multicast policies
FortiGate units support multicast policies. You can configure and create multicast
policies using the following CLI command:
config firewall multicast-policy
For more information, see the FortiOS CLI Reference and the FortiGate Multicast
Technical Note.
Viewing the firewall policy list

The firewall policy list displays firewall policies in their order of matching
precedence for each source and destination interface pair.
If virtual domains are enabled on the FortiGate unit, firewall policies are
configured separately for each virtual domain; you must access the VDOM before
you can configure its policies. To access a VDOM, go to System > VDOM, and in
the row corresponding to the VDOM whose policies you want to configure, select
Enter.
You can add, delete, edit, and re-order policies in the policy list. Firewall policy
order affects policy matching. For details about arranging policies in a policy list,
see “How list order affects policy matching” on page 293 and “Moving a policy to a
different position in the policy list”.
To view the policy list, go to Firewall > Policy.

01-30007-0203-20090112 295
Viewing the firewall policy list Firewall Policy
Figure 168:Firewall policy list
Filter
Delete
Edit
Insert Policy before
Move To
Create New Add a firewall policy. Select the down arrow beside Create
New to add a firewall policy or firewall policy section. A
firewall policy section visually groups firewall policies. For
more information, see “Configuring firewall policies” on
page 297.
Column Settings Customize the table view. You can select the columns to hide
or display and specify the column displaying order in the
table.
Filter icon Edit the column filters to filter or sort the policy list according
to the criteria you specify. For more information, see “Adding
filters to web-based manager lists” on page 58.
ID The policy identifier. Policies are numbered in the order they
are added to the policy list.
Source The source address or address group to which the policy
applies. For more information, see “Firewall Address” on
page 315.
Destination The destination address or address group to which the policy
applies. For more information, see “Firewall Address” on
page 315.
Schedule The schedule that controls when the policy should be active.
For more information, see “Firewall Schedule” on page 329.
Service The service to which the policy applies. For more information,
see “Firewall Service” on page 321.
Profile The protection profile that is associated with the policy.
Action The response to make when the policy matches a connection
attempt.
Status Either enabled or disabled.
From The source interface.
To The destination interface.
VPN Tunnel The VPN tunnel the VPN policy uses.
Authentication The user authentication method the policy uses.
Comments Comments entered when creating or editing the policy.
Log A green check mark indicates traffic logging is enabled for the
policy; a grey cross mark indicates traffic logging is disabled
for the policy.

296 01-30007-0203-20090112
Firewall Policy Configuring firewall policies
Count The FortiGate unit counts the number of packets and bytes
that hit the firewall policy.
For example, 5/50B means that five packets and 50 bytes in
total have hit the policy.
The counter is reset when the FortiGate unit is restarted or
the policy is deleted and re-configured.
Delete icon Delete the policy from the list.
Edit icon Edit the policy.
Insert Policy Before icon Add a new policy above the corresponding policy (the New
Policy screen appears).
Move To icon Move the corresponding policy before or after another policy
in the list. For more information, see “Moving a policy to a
different position in the policy list” on page 294.
Configuring firewall policies

You can configure firewall policies to define which sessions will match the policy
and what actions the FortiGate unit will perform with packets from matching
sessions.
Sessions are matched to a firewall policy by considering these features of both
the packet and policy:
• Source Interface/Zone
• Source Address
• Destination Interface/Zone
• Destination Address
• schedule and time of the session’s initiation
• service and the packet’s port numbers.
If the initial packet matches the firewall policy, the FortiGate unit performs the
configured Action and any other configured options on all packets in the session.
Packet handling actions can be ACCEPT, DENY, IPSEC or SSL-VPN.
• ACCEPT policy actions permit communication sessions, and may optionally
include other packet processing instructions, such as requiring authentication
to use the policy, or specifying a protection profile to apply features such as
virus scanning to packets in the session. An ACCEPT policy can also apply
interface-mode IPSec VPN traffic if either the selected source or destination
interface is an IPSec virtual interface. For more information, see “Overview of
IPSec VPN configuration” on page 393.
• DENY policy actions block communication sessions, and may optionally log
the denied traffic.
• IPSEC and SSL-VPN policy actions apply a tunnel mode IPSec VPN or SSL
VPN tunnel, respectively, and may optionally apply NAT and allow traffic for
one or both directions. If permitted by the firewall encryption policy, a tunnel
may be initiated automatically whenever a packet matching the policy arrives
on the specified network interface, destined for the local private network. For
more information, see “IPSec firewall policy options” on page 306 and “SSL-
VPN firewall policy options” on page 307.

01-30007-0203-20090112 297
Configuring firewall policies Firewall Policy
To add or edit a firewall policy, go to Firewall > Policy. Select Create New to add
a policy or select the edit icon beside an existing firewall policy. Configure the
settings as described in the following table and in the references to specific
features for IPSec, SSL VPN and other specialized settings, and then select OK.
Alternatively, if you want to use IPv6 firewall addresses in your firewall policy, first
go to System > Admin > Settings. Select “IPv6 Support on GUI”. Then go to
Firewall > Policy > IPv6 Policy, and configure the settings according to the
following table.
Firewall policy order affects policy matching. Each time that you create or edit a
policy, make sure that you position it in the correct location in the list. You can
create a new policy and position it right away before an existing one in the firewall
policy list, by selecting Insert Policy before (see “Viewing the firewall policy list” on
page 295).
Note: You can configure differentiated services (DSCP) firewall policy options through the
CLI. See the “firewall” chapter of the FortiGate CLI Reference.
Figure 169:Firewall Policy options

298 01-30007-0203-20090112
Source Select the name of the FortiGate network interface, virtual domain
Interface/Zone (VDOM) link, or zone on which IP packets are received. Interfaces and
zones are configured on the System Network page. For more
information, see “Interfaces” on page 107 and “Configuring zones” on
page 128.
If Action is set to IPSEC, the interface is associated with the local
private network.
If Action is set to SSL-VPN, the interface is associated with connections
from remote SSL VPN clients.
Source Address Select the name of a firewall address to associate with the Source
Interface/Zone. Only packets whose header contains an IP address
matching the selected firewall address will be subject to this policy.
You can also create firewall addresses by selecting Create New from
this list. For more information, see “Configuring addresses” on
page 317.
If you want to associate multiple firewall addresses or address groups
with the Source Interface/Zone, from Source Address, select Multiple. In
the dialog box, move the firewall addresses or address groups from the
Available Addresses section to the Members section, then select OK.
If Action is set to IPSEC, the address is the private IP address of the
host, server, or network behind the FortiGate unit.
If Action is set to SSL-VPN and the policy is for web-only mode clients,
select all.
If Action is set to SSL-VPN and the policy is for tunnel mode clients,
select the name of the address that you reserved for tunnel mode
clients.
Destination Select the name of the FortiGate network interface, virtual domain
Interface/Zone (VDOM) link, or zone to which IP packets are forwarded. Interfaces and
zones are configured on the System Network page. For more
information, see “Interfaces” on page 107 and “Configuring zones” on
page 128.
If Action is set to IPSEC, the interface is associated with the entrance to
the VPN tunnel.
If Action is set to SSL-VPN, the interface is associated with the local
private network.
Destination Select the name of a firewall address to associate with the Destination
Address Interface/Zone. Only packets whose header contains an IP address
matching the selected firewall address will be subject to this policy.
You can also create firewall addresses by selecting Create New from
this list. For more information, see “Configuring addresses” on
page 317.
If you want to associate multiple firewall addresses or address groups
with the Destination Interface/Zone, from Destination Address, select
Multiple. In the dialog box, move the firewall addresses or address
groups from the Available Addresses section to the Members section,
then select OK.
If you select a virtual IP, the FortiGate unit applies NAT or PAT. The
applied translation varies by the settings specified in the virtual IP, and
whether you select NAT (below). For more information on using virtual
IPs, see “Firewall Virtual IP” on page 333.
If Action is set to IPSEC, the address is the private IP address to which
packets may be delivered at the remote end of the VPN tunnel.
If Action is set to SSL-VPN, select the name of the IP address that
corresponds to the host, server, or network that remote clients need to
access behind the FortiGate unit.
Schedule Select a one-time or recurring schedule that controls when the policy is
in effect.
You can also create schedules by selecting Create New from this list.
For more information, see “Firewall Schedule” on page 329.

01-30007-0203-20090112 299
Service Select the name of a firewall service or service group that packets must
match to trigger this policy.
You can select from a wide range of predefined firewall services, or you
can create a custom service or service group by selecting Create New
from this list. For more information, see “Configuring custom services”
on page 325 and “Configuring service groups” on page 327.
By selecting the Multiple button beside Service, you can select multiple
services or service groups.
Action Select how you want the firewall to respond when a packet matches the
conditions of the policy. The options available will vary widely depending
on this selection.
ACCEPT Accept traffic matched by the policy. You can configure NAT, protection
profiles, log traffic, shape traffic, set authentication options, or add a
comment to the policy.
DENY Reject traffic matched by the policy. The only other configurable policy
options are Log Violation Traffic to log the connections denied by this
policy and adding a Comment.
IPSEC You can configure an IPSec firewall encryption policy to process IPSec
VPN packets, as well as configure protection profiles, log traffic, shape
traffic or add a comment to the policy. See “IPSec firewall policy options”
on page 306.
SSL-VPN You can configure an SSL-VPN firewall encryption policy to accept SSL
VPN traffic. This option is available only after you have added a SSL-
VPN user group. You can also configure NAT and protection profiles,
log traffic, shape traffic or add a comment to the policy. See “SSL-VPN
firewall policy options” on page 307.
NAT Available only if Action is set to ACCEPT or SSL-VPN. Enable or disable
Network Address Translation (NAT) of the source address and port of
packets accepted by the policy. When NAT is enabled, you can also
configure Dynamic IP Pool and Fixed Port.
If you select a virtual IP as the Destination Address, but do not select the
NAT option, the FortiGate unit performs destination NAT (DNAT) rather
than full NAT. Source NAT (SNAT) is not performed.
Dynamic IP Select the check box, then select an IP pool to translate the source
Pool address to an IP address randomly selected from addresses in the IP
Pool.
IP Pool cannot be selected if the destination interface, VLAN
subinterface, or one of the interfaces or VLAN subinterfaces in the
destination zone is configured using DHCP or PPPoE, or if you have
selected a Destination Interface to which no IP Pools are bound.
You cannot use IP pools when using zones. An IP pool can only be
associated with an interface.
For details, see “IP pools” on page 356.
Fixed Port Select Fixed Port to prevent NAT from translating the source port.
Some applications do not function correctly if the source port is
translated. In most cases, if Fixed Port is selected, Dynamic IP pool is
also selected. If Dynamic IP pool is not selected, a policy with Fixed Port
selected can allow only one connection to that service at a time.
Protection Select a protection profile to apply antivirus, web filtering, web category
Profile filtering, spam filtering, IPS, content archiving, and logging to a firewall
policy. You can also create a protection profile by selecting Create New
from this list. For more information, see “Firewall Protection Profile” on
page 365.
If you intend to apply authentication to this policy, do not make a
Protection Profile selection. The user group you choose for
authentication is already linked to a protection profile. For more
information, see “Adding authentication to firewall policies” on page 302.

300 01-30007-0203-20090112
Log Allowed Select to record messages to the traffic log whenever the policy
Traffic processes a connection. You must also enable traffic log for a logging
location (syslog, WebTrends, local disk if available, memory, or
FortiAnalyzer) and set the logging severity level to Notification or lower
using the Log and Report screen. For more information see
“Log&Report” on page 525.
Log Violation Available only if Action is set to DENY. Select Log Violation Traffic, for
Traffic Deny policies, to record messages to the traffic log whenever the policy
processes a connection. You must also enable traffic log for a logging
location (syslog, WebTrends, local disk if available, memory, or
FortiAnalyzer) and set the logging severity level to Notification or lower
using the Log and Report screen. For more information, see
“Log&Report” on page 525.
Authentication Available only if Action is set to ACCEPT or SSL-VPN. Select to require
authentication for using this firewall policy, then specify the valid
authentication methods, group names, and certificate. If FSAE
authentication is selected, also specify a protection profile for Guest
accounts.
Before using this option, you need to add users and a firewall protection
profile to a user group. For more information, see “User groups” on
page 435. For detailed information about configuring authentication
settings, see “Authentication firewall policy options (non-SSL-VPN)” on
page 303 and “SSL-VPN firewall policy options” on page 307.
Check Firewall policies can deny access for hosts that do not have FortiClient
FortiClient is Host Security software installed and operating. For more information,
Installed and see “Options to detect FortiClient on hosts” on page 308.
Running This option appears only on FortiGate-1000A, FortiGate-3600A, and
FortiGate-5005FA2 models.
Traffic Shaping Traffic Shaping controls the bandwidth available to, and sets the priority
of the traffic processed by, the policy.
Note: To ensure that traffic shaping is working at its best, make sure that
the interface ethernet statistics show no errors, collisions, or buffer
overruns. If any of these problems do appear, then FortiGate and switch
settings may require adjusting.
Also, do not set both Guaranteed Bandwidth and Maximum Bandwidth
to 0 (zero), or the policy will not allow any traffic.
For information about traffic shaping, see “Adding traffic shaping to
firewall policies” on page 304 and “Traffic shaping considerations” on
page 305.
Guaranteed Select a value to ensure there is enough bandwidth available for a high-
Bandwidth priority service. Be sure that the sum of all Guaranteed Bandwidth in all
firewall policies is significantly less than the bandwidth capacity of the
interface.
Maximum Select to limit bandwidth in order to keep less important services from
Bandwidth using bandwidth needed for more important ones.
Traffic Select High, Medium, or Low. Select Traffic Priority so the FortiGate unit
Priority manages the relative priorities of different types of traffic. For example, a
policy for connecting to a secure web server needed to support
e-commerce traffic should be assigned a high traffic priority. Less
important services should be assigned a low priority. The firewall
provides bandwidth to low-priority connections only when bandwidth is
not needed for high-priority connections.
Be sure to enable traffic shaping on all firewall policies. If you do not
apply any traffic shaping rule to a policy, the policy is set to high priority
by default.
Distribute firewall policies over all three priority queues.
User Available only on some models and only if Action is set to ACCEPT.
Authentication Select this option to display the Authentication Disclaimer page (a
Disclaimer replacement message) to the user. The user must accept the disclaimer
to connect to the destination. You can use the disclaimer together with
authentication or a protection profile.

01-30007-0203-20090112 301
Redirect URL Available only on some models and only if Action is set to ACCEPT. If
you enter a URL, the user is redirected to the URL after authenticating
and/or accepting the user authentication disclaimer.
Comments Add information about the policy. The maximum length is 63 characters.
Adding authentication to firewall policies

If you enable Authentication in a firewall policy, network users must send traffic
involving a supported firewall authentication protocol to trigger the firewall
authentication challenge, and successfully authenticate, before the FortiGate unit
will allow any other traffic matching the firewall policy.
User authentication can occur through any of the following supported protocols:
• HTTP
• HTTPS
• FTP
• Telnet.
The authentication style depends on which of these supported protocols you have
included in the selected firewall services group and which of those enabled
protocols the network user applies to trigger the authentication challenge. The
authentication style will be one of two types. For certificate-based (HTTPS or
HTTP redirected to HTTPS only) authentication, you must install customized
certificates on the FortiGate unit and on the browsers of network users, which the
FortiGate unit matches. For user name and password-based (HTTP, FTP, and
Telnet) authentication, the FortiGate unit prompts network users to input their
firewall user name and password.
For example, if you want to require HTTPS certificate-based authentication before
allowing SMTP and POP3 traffic, you must select a firewall service (in the firewall
policy) that includes SMTP, POP3 and HTTPS services. Prior to using either
POP3 or SMTP, the network user would send traffic using the HTTPS service,
which the FortiGate unit would use to verify the network user’s certificate; upon
successful certificate-based authentication, the network user would then be able
to access his or her email.
In most cases, you should ensure that users can use DNS through the FortiGate
unit without authentication. If DNS is not available, users will not be able to use a
domain name when using a supported authentication protocol to trigger the
FortiGate unit’s authentication challenge.
Note: If you do not install certificates on the network user’s web browser, the network users
may see an SSL certificate warning message and have to manually accept the default
FortiGate certificate, which the network users’ web browsers may then deem as invalid. For
information on installing certificates, see “System Certificates” on page 219.
Note: When you use certificate authentication, if you do not specify any certificate when
you create a firewall policy, the FortiGate unit will use the default certificate from the global
settings will be used. If you specify a certificate, the per-policy setting will override the
global setting. For information on global authentication settings, see “Authentication
settings” on page 445.

302 01-30007-0203-20090112
Authentication requires that Action is ACCEPT or SSL-VPN, and that you first
create users, assign them to a firewall user group, and assign a protection profile
to that user group. For information on configuring user groups, see “User groups”
on page 435. For information on configuring authentication settings, see
“Authentication firewall policy options (non-SSL-VPN)” on page 303 and “SSL-
VPN firewall policy options” on page 307.
Authentication firewall policy options (non-SSL-VPN)

For non-SSL-VPN authentication that allows network users to use a firewall
policy, you need to add user groups to the policy. For information about
configuring user groups, see “User groups” on page 435.
To configure authentication, go to Firewall > Policy, select Create New to add a
firewall policy, or, in the row corresponding to an existing firewall policy, select
Edit. Make sure that Action is set to ACCEPT. Enter the information in the
following table and select OK.
Figure 170:Selecting user groups for authentication
Right Arrow
Left Arrow
Authentication Select the check box then one or more authentication server
types. When a network user attempts to authenticate, options
selected in the Authentication screen indicate which local or
remote authentication servers the FortiGate unit will consult to
verify the user’s credentials. Available only if Action is set to
ACCEPT or SSL-VPN.
Firewall Include firewall user groups defined locally on the FortiGate unit,
as well as on any connected LDAP and RADIUS servers.
Directory Service Include Directory Service groups defined in User > User Group.
(FSAE) The groups are authenticated through a domain controller using
Fortinet Server Authentication Extensions (FSAE). If you select
this option, you must install the FSAE on the Directory Service
domain controller. For information about FSAE, see the FSAE
Technical Note. For information about configuring user groups,
see “User groups” on page 435.
NTLM Authentication Include Directory Service groups defined in User > User Group.
If you select this option, you must use Directory Service groups
as the members of the authentication group for NTLM. For
information about configuring user groups, see “User groups” on
page 435.

01-30007-0203-20090112 303
Available Groups From Available Groups, select one or more user groups that
must authenticate to be allowed to use this policy. Select the
Right Arrow to move the selected user groups to Allowed.
Allowed To prioritize the allowed user group definitions, select an Allowed
group, then select Move Up or Move Down. User groups located
at the top of the Allowed list have higher priority. If a user is a
member of more than one group, group priority determines which
user group, and therefore which protection profile, will be applied
to the authenticating user’s traffic. Select the Left Arrow to
remove allowed user groups.
Guest Profile Directory Service (FSAE) only. Select the protection profile that
guest accounts will use.
Certificate Certificate-based authentication only. Select the protection profile
that guest accounts will use. Note: In order to implement
certificate-based authentication, you must select a firewall
service group that includes one of the supported authentication
protocols that use certificate-based authentication. You should
also install the certificate on the network user’s web browser. For
more information, see “Adding authentication to firewall policies”
on page 302.
Adding traffic shaping to firewall policies

Traffic Shaping controls the bandwidth available to, and sets the priority of the
traffic processed by, the policy. Traffic Shaping makes it possible to control which
policies have the highest priority when large amounts of data are moving through
the FortiGate unit. For example, the policy for the corporate web server might be
given higher priority than the policies for most employees’ computers. An
employee who needs extra high-speed Internet access could have a special
outgoing policy set up with higher bandwidth.
Traffic shaping is available for firewall policies whose Action is ACCEPT, IPSEC,
or SSL-VPN. It is also available for all supported services, including H.323, TCP,
UDP, ICMP, and ESP.
Guaranteed and maximum bandwidth in combination with queuing ensures
minimum and maximum bandwidth is available for traffic.
Traffic shaping cannot increase the total amount of bandwidth available, but you
can use it to improve the quality of bandwidth-intensive and sensitive traffic.
Note: For more information about traffic shaping you can also see the FortiGate Traffic
Shaping Technical Note.
Guaranteed bandwidth and maximum bandwidth

When you enter a value in the Guaranteed Bandwidth field of a firewall policy, you
guarantee the amount of bandwidth available for selected network traffic (in
Kbytes/sec). For example, you may want to give a higher guaranteed bandwidth
to your e-commerce traffic.
When you enter a value in the Maximum Bandwidth field of a firewall policy you
limit the amount of bandwidth available for selected network traffic (in Kbytes/sec).
For example, you may want to limit the bandwidth of IM traffic usage, to save
some bandwidth for the more important e-commerce traffic.

304 01-30007-0203-20090112
The bandwidth available for traffic controlled by a policy is used for both the
control and data sessions and for traffic in both directions. For example, if
guaranteed bandwidth is applied to an internal and an external FTP policy, and a
user on an internal network uses FTP to put and get files, both the put and get
sessions share the bandwidth available to the traffic controlled by the policy.
The guaranteed and maximum bandwidth available for a policy is the total
bandwidth available to all traffic controlled by the policy. If multiple users start
multiple communications session using the same policy, all of these
communications sessions must share from the bandwidth available for the policy.
However, bandwidth availability is not shared between multiple instances of using
the same service if these multiple instances are controlled by different policies.
For example, you can create one FTP policy to limit the amount of bandwidth
available for FTP for one network address and create another FTP policy with a
different bandwidth availability for another network address.
Note: If you set both guaranteed bandwidth and maximum bandwidth to 0 (zero),
the policy does not allow any traffic.
Traffic Priority
You can set traffic priority to manage the relative priorities of different types of
traffic. Important and latency-sensitive traffic should be assigned a high priority.
Less important and less sensitive traffic should be assigned a low priority.
The FortiGate unit provides bandwidth to low-priority connections only when
bandwidth is not needed for high-priority connections.
For example, you can add policies to guarantee bandwidth for voice and
e-commerce traffic. Then you can assign a high priority to the policy that controls
voice traffic and a medium priority to the policy that controls e-commerce traffic.
During a busy time, if both voice and e-commerce traffic are competing for
bandwidth, the higher priority voice traffic will be transmitted before the
e-commerce traffic.
Traffic shaping considerations

Traffic shaping attempts to “normalize” traffic peaks/bursts to prioritize certain
flows over others. But there is a physical limitation to the amount of data which
can be buffered and to the length of time. Once these thresholds have been
surpassed, frames and packets will be dropped, and sessions will be affected in
other ways. For example, incorrect traffic shaping configurations may actually
further degrade certain network flows, since the excessive discarding of packets
can create additional overhead at the upper layers that may be attempting to
recover from these errors.
A basic traffic shaping approach is to prioritize certain traffic flows over other
traffic whose potential discarding is less advantageous. This would mean that you
accept sacrificing certain performance and stability on low-priority traffic, in order
to increase or guarantee performance and stability to high-priority traffic.
If, for example, you are applying bandwidth limitations to certain flows, you must
accept the fact that these sessions can be limited and therefore negatively
impacted.

01-30007-0203-20090112 305
Traffic shaping applied to a firewall policy is enforced for traffic which may flow in
either direction. Therefore a session which may be set up by an internal host to an
external one, through an Internal-to-External policy, will have traffic shaping
applied even if the data stream flows external to internal. One example may be an
FTP “get” or a SMTP server connecting to an external one, in order to retrieve
email.
Note that traffic shaping is effective for normal IP traffic at normal traffic rates.
Traffic shaping is not effective during periods when traffic exceeds the capacity of
the FortiGate unit. Since packets must be received by the FortiGate unit before
they are subject to traffic shaping, if the FortiGate unit cannot process all of the
traffic it receives, then dropped packets, delays, and latency are likely to occur.
To ensure that traffic shaping is working at its best, make sure that the interface
ethernet statistics show no errors, collisions or buffer overruns. If any of these
problems do appear, then FortiGate and switch settings may require adjusting.
For more information, see the FortiGate Traffic Shaping Technical Note.
IPSec firewall policy options

In a firewall policy (see “Configuring firewall policies” on page 297), the following
encryption options are available for IPSec. To configure these options, go to
Firewall > Policy, select Create New to add a firewall policy, or in the row
corresponding to an existing firewall policy, select Edit. Make sure that Action is
set to IPSEC. Enter the information in the following table and select OK.
Figure 171:IPSEC encryption policy
VPN Tunnel Select the VPN tunnel name defined in the phase 1 configuration. The
specified tunnel will be subject to this firewall encryption policy.
Allow Inbound Select to enable traffic from a dialup client or computers on the remote
private network to initiate the tunnel.
Allow outbound Select to enable traffic from computers on the local private network to
initiate the tunnel.
Inbound NAT Select to translate the source IP addresses of inbound decrypted
packets into the IP address of the FortiGate interface to the local
private network.
Outbound NAT Select only in combination with a natip CLI value to translate the
source addresses of outbound cleartext packets into the IP address
that you specify. When a natip value is specified, the source
addresses of outbound IP packets are replaced before the packets
are sent through the tunnel. For more information, see the “firewall”
chapter of the FortiGate CLI Reference.
Note: For a route-based (interface mode) VPN, you do not configure an IPSec firewall
policy. Instead, you configure two regular ACCEPT firewall policies, one for each direction
of communication, with the IPSec virtual interface as the source or destination interface as
appropriate.
For more information, see the “Defining firewall policies” chapter of the FortiGate
IPSec VPN User Guide.

306 01-30007-0203-20090112
SSL-VPN firewall policy options

In a firewall policy (see “Configuring firewall policies” on page 297), the following
options are available for SSL VPN. To configure these options, go to Firewall >
Policy, select Create New to add a firewall policy, or in the row corresponding to
an existing firewall policy, select Edit. Make sure that Action is set to SSL-VPN.
Enter the information in the following table and select OK.
Note: The SSL-VPN option is available from the Action list after one or more SSL VPN user
groups have been created. For more information, see “Configuring additional SSL VPN
user group options” on page 442.
Figure 172:SSL-VPN encryption policy
Right Arrow
Left Arrow
SSL Client Certificate Allow traffic generated by holders of a (shared) group

Restrictive certificate. The holders of the group certificate must be
members of an SSL VPN user group, and the name of that user
group must be present in the Allowed field.
Cipher Strength Select the bit level of SSL encryption. The web browser on the
remote client must be capable of matching the level that you
select: Any, High >= 164, or Medium >= 128.
User Authentication Select one of the following options:
Method
Local For a local user group that will be bound to this firewall policy.
RADIUS For remote clients that will be authenticated by an external
RADIUS server.
LDAP For remote clients that will be authenticated by an external
LDAP server.
Any For all of the above authentication methods. Local is attempted
first, then RADIUS, then LDAP.
Available Groups Select the name of the user group requiring SSL VPN access,
and then select the Right Arrow. Do not select more than one
user group unless all members of the selected user groups
have identical access requirements.
For information about how to create a firewall encryption policy for SSL VPN
users, see the “SSL VPN administration tasks” chapter of the FortiGate SSL VPN
User Guide.
If you select NAT (above, in the same dialog box), the IP address of the outgoing
interface of the FortiGate unit is used as the source address for new sessions
started by SSL VPN.
The traffic shaping option can be used to traffic shape tunnel-mode SSL VPN
traffic, but has no effect on web-mode SSL VPN traffic.

01-30007-0203-20090112 307
Firewall policy examples Firewall Policy
Options to detect FortiClient on hosts

Some FortiGate models, (including models 620B, 1000A, 3600A, 3016B, 3810A,
5005FA2, and 5001A) provide FortiClient checking as a firewall policy option. A
firewall policy can deny access to hosts that do not have FortiClient Host Security
software installed and operating. This feature can detect FortiClient software
version 3.0 MR2 or later.
To configure FortiClient detection, go to Firewall > Policy, select Create New to
add a firewall policy, or in the row corresponding to an existing firewall policy,
select Edit. Enter the information in the following table and select OK.
Figure 173:FortiClient Host Security check options
Check FortiClient Installed Select to check that the source host is running FortiClient
and Running Host Security software. Select the following reasons to
deny access as needed:
• FortiClient is Not Installed
• FortiClient is Not Licensed
• AV/IPS Database Out-of-Date
• AV Disabled
• Firewall Disabled
• Web Filter Disabled
To use AV/IPS Database Out-of-Date you must also select
AV Disabled.
Redirect Restricted Users to Select to redirect denied users to the internal web portal
FortiGate Download Portal which displays to the user the reason for denial. From the
web portal, the user can download FortiClient Host
Security software.
To upload FortiClient software to your FortiGate unit, go to
System > Status or go to System > Maintenance >
Backup & Restore. For more information, see
“FortiClient” on page 236.
Firewall policy examples

FortiGate units are capable of meeting various network requirements from home
use to SOHO, large enterprises and ISPs. The following two scenarios
demonstrate practical applications of firewall policies in the SOHO and large
enterprise environments.

308 01-30007-0203-20090112
Firewall Policy Firewall policy examples
Scenario one: SOHO-sized business

Company A is a small software company performing development and providing
customer support. In addition to their internal network of 15 computers, they also
have several employees who work from home all or some of the time.
With their current network topography, all 15 of the internal computers are behind
a router and must go to an external source to access the IPS mail and web
servers. All home-based employees access the router through open/non-secured
connections.
Figure 174:Example SOHO network before FortiGate installation
Internet
IPS Mail ISP Web Home-based Workers

Server Server (no secure connection)
172.16.10.3
192.168.100.1
Finance Help Engineering

Department Desk Department
Internal Network
Company A requires secure connections for home-based workers. Like many

companies, they rely heavily on email and Internet access to conduct business.
They want a comprehensive security solution to detect and prevent network
attacks, block viruses, and decrease spam. They want to apply different protection
settings for different departments. They also want to integrate web and email
servers into the security solution.
To deal with their first requirement, Company A configures specific policies for
each home-based worker to ensure secure communication between the home-
based worker and the internal network.
2 Select Create New and enter or select the following settings for Home_User_1:

01-30007-0203-20090112 309
Interface / Zone Source: internal Destination: wan1

Address Source: Destination: Home_User_1
CompanyA_Network
Schedule Always
Service ANY
Action IPSEC
VPN Tunnel Home1
Allow Inbound yes
Allow outbound yes
Inbound NAT yes
Outbound NAT no
Protection Profile Select the check mark and select standard_profile
3 Select OK.
4 Select Create New and enter or select the following settings for Home_User_2:
Interface / Zone Source: internal Destination: wan1

Address Source: Destination: All
CompanyA_network
Schedule Always
Service ANY
Action IPSEC
VPN Tunnel Home2_Tunnel
Allow Inbound yes
Allow outbound yes
Inbound NAT yes
Outbound NAT no
Protection Profile Select the check mark and select standard_profile
5 Select OK.

310 01-30007-0203-20090112
Figure 175:SOHO network topology with FortiGate-100
VPN Tunnel Internet VPN Tunnel
Home User 1 Home User 2

172.20.100.6 172.25.106.99
External
172.30.120.8
DMZ
FortiGate 10.10.10.1
100A
Email Server
Internal
10.10.10.2
192.168.100.1
Finance Users Engineering Users

192.168.100.10- 192.168.100.51-
Web Server
192.168.100.20 192.168.100.100 10.10.10.3
Help Desk Users
192.168.100.21-
192.168.100.50
The proposed network is based around a ForitGate 100A unit. The 15 internal
computers are behind the FortiGate unit. They now access the email and web
servers in a DMZ, which is also behind the FortiGate unit. All home-based
employees now access the office network through the FortiGate unit via VPN
tunnels.
Scenario two: enterprise-sized business

Located in a large city, the library system is anchored by a main downtown
location serving most of the population, with more than a dozen branches spread
throughout the city. Each branch is wired to the Internet but none are linked with
each other by dedicated connections.
The current network topography at the main location consists of three user
groups. The main branch staff and public terminals access the servers in the DMZ
behind the firewall. The catalog access terminals directly access the catalog
server without first going through the firewall.
The topography at the branch office has all three users accessing the servers at
the main branch through non-secured internet connections.

01-30007-0203-20090112 311
Figure 176:The library system’s current network topology
The library must be able to set different access levels for patrons and staff
members.
The first firewall policy for main office staff members allows full access to the
Internet at all times. A second policy will allow direct access to the DMZ for staff
members. A second pair of policies is required to allow branch staff members the
same access.
The staff firewall policies will all use a protection profile configured specifically for
staff access. Enabled features include virus scanning, spam filtering, IPS, and
blocking of all P2P traffic. FortiGuard web filtering is also used to block
advertising, malware, and spyware sites.
A few users may need special web and catalog server access to update
information on those servers, depending on how they are configured. Special
access can be allowed based on IP address or user.
The proposed topography has the main branch staff and the catalog access
terminals going through a FortiGate HA cluster to the servers in a DMZ. The public
access terminals first go through a FortiWiFi unit, where additional policies can be
applied, to the HA Cluster and finally to the servers.
The branch office has all three users routed through a FortiWiFi unit to the main
branch via VPN tunnels.

312 01-30007-0203-20090112
Figure 177:Proposed library system network topology
Policies are configured in Firewall > Policy. Protection Profiles are configured in
Firewall > Protection Profile.
Main office “staff to Internet” policy:
Source Interface Internal

Source Address All
Destination Interface External
Destination Address All
Schedule Always
Action Accept
Main office “staff to DMZ” policy:
Source Interface Internal

Source Address All
Destination Interface DMZ
Destination Address Servers
Schedule Always
Action Accept

01-30007-0203-20090112 313
Branches “staff to Internet” policy:
Source Interface Branches

Source Address Branch Staff
Destination Interface External
Destination Address All
Schedule Always
Action Accept
Branches “staff to DMZ” policy:
Source Interface Branches

Source Address Branch Staff
Destination Interface DMZ
Destination Address Servers
Schedule Always
Action Accept
For more information about these examples, see:

• SOHO and SMB Configuration Example Guide
• FortiGate Enterprise Configuration Example

314 01-30007-0203-20090112
Firewall Address About firewall addresses
Firewall Address
Firewall addresses and address groups define network addresses that you can
use when configuring firewall policies’ source and destination address fields. The
FortiGate unit compares the IP addresses contained in packet headers with
firewall policy source and destination addresses to determine if the firewall policy
matches the traffic.
You can organize related addresses into address groups to simplify your firewall
policy list.
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall addresses
are configured separately for each virtual domain, and you must first enter the
virtual domain to configure its firewall addresses. For details, see “Using virtual
• About firewall addresses
• Viewing the firewall address list
• Configuring addresses
• Viewing the address group list
• Configuring address groups
About firewall addresses

A firewall address can contain one or more network addresses. Network
addresses can be represented by an IP address with a netmask, an IP address
range, or a fully qualified domain name (FQDN).
When representing hosts by an IP address with a netmask, the IP address can
represent one or more hosts. For example, a firewall address can be:
• a single computer, such as 192.45.46.45
• a subnetwork, such as 192.168.1.0 for a class C subnet
• 0.0.0.0, which matches any IP address
The netmask corresponds to the subnet class of the address being added, and
can be represented in either dotted decimal or CIDR format. The FortiGate unit
automatically converts CIDR formatted netmasks to dotted decimal format. For
example, the netmask can be a:
• netmask for a single computer: 255.255.255.255, or /32
• netmask for a class A subnet: 255.0.0.0, or /8
• netmask for a class B subnet: 255.255.0.0, or /16
• netmask for a class C subnet: 255.255.255.0, or /24
• netmask including all IP addresses: 0.0.0.0
Valid IP address and netmask formats include:
• x.x.x.x/x.x.x.x, such as 192.168.1.0/255.255.255.0
• x.x.x.x/x, such as 192.168.1.0/24
Note: IP address 0.0.0.0 with netmask 255.255.255.255 is not a valid firewall

address.

01-30007-0203-20090112 315
Viewing the firewall address list Firewall Address
When representing hosts by an IP Range, the range indicates hosts with

continuous IP addresses in a subnet, such as 192.168.1.[2-10], or
192.168.1.* to indicate the complete range of hosts on that subnet. Valid IP
Range formats include:
• x.x.x.x-x.x.x.x, such as 192.168.110.100-192.168.110.120
• x.x.x.[x-x], such as 192.168.110.[100-120]
• x.x.x.*, such as 192.168.110.*
When representing hosts by a FQDN, the domain name can be a subdomain,
such as mail.example.com. A single FQDN firewall address may be used to apply
a firewall policy to multiple hosts, such as in load balancing and high availability
(HA) configurations. FortiGate units automatically resolves and maintains a record
of all addresses to which the FQDN resolves. Valid FQDN formats include:
• <host_name>.<second_level_domain_name>.<top_level_domain_name>,
such as mail.example.com
• <host_name>.<top_level_domain_name>
Caution: Be cautious if employing FQDN firewall addresses. Using a fully qualified domain
name in a firewall policy, while convenient, does present some security risks, because
policy matching then relies on a trusted DNS server. Should the DNS server be
compromised, firewall policies requiring domain name resolution may no longer function
properly.
Note: By default, IPv6 firewall addresses are configurable only in the CLI. For information
on enabling configuration of IPv6 firewall addresses in the web-based manager, see
“Settings” on page 215.
Viewing the firewall address list

Firewall addresses in the list are grouped by type: IP/Mask, IP Range, or FQDN.
FortiGate unit default configurations include the all address, which represents
any IP address on any network.
To view the address list, go to Firewall > Address.
Figure 178:Firewall address list
Delete
Edit

316 01-30007-0203-20090112
Firewall Address Configuring addresses
Create New Select to add a firewall address.

If IPv6 Support on GUI is enabled, you can alternatively select the down
arrow located in the Create New button, then select IPv6 Address, to
configure an IPv6 firewall address. For details, see “Settings” on
page 215.
Name The name of the firewall address.
Address/FQDN The IP address and mask, IP address range, or fully qualified domain
name.
Interface The interface, zone, or virtual domain (VDOM) to which you bind the IP
address.
Delete icon Select to remove the address. The Delete icon only appears if the
address is not currently being used by a firewall policy or address
group.
Edit icon Select to edit the address.
Configuring addresses
You can use one of three methods to represent hosts in firewall addresses:
IP/Mask, IP Range, or FQDN.
Caution: Be cautious if employing FQDN firewall addresses. Using a fully qualified domain
name in a firewall policy, while convenient, does present some security risks, because
policy matching then relies on a trusted DNS server. Should the DNS server be
compromised, firewall policies requiring domain name resolution may no longer function
properly.
Note: By default, IPv6 firewall addresses are configurable only in the CLI. For information
on enabling configuration of IPv6 firewall addresses in the web-based manager, see
“Settings” on page 215.
To add a firewall address

If IPv6 GUI support is enabled, you can alternatively select the down arrow
located in the Create New button, then select IPv6 Address, to configure an IPv6
firewall address. For information on enabling configuration of IPv6 firewall
addresses in the web-based manager, see “Settings” on page 215.
You can also create firewall addresses during firewall policy configuration by
selecting Create New from the Address drop-down menu.
Figure 179:New address or IP range options

01-30007-0203-20090112 317
Viewing the address group list Firewall Address
Address Name Enter a name to identify the firewall address. Addresses, address
groups, and virtual IPs must have unique names.
Type Select the type of address: Subnet/IP Range or FQDN. The Subnet/IP
Range type allows you to enter either an IP Range or an IP address with
subnet mask.
Subnet/IP Range Enter the firewall IP address, followed by a forward slash (/), then
subnet mask, or enter an IP address range separated by a hyphen.
Interface Select the interface, zone, or virtual domain (VDOM) link to which you
want to bind the IP address. Select Any if you want to bind the IP
address with the interface/zone when you create a firewall policy.
4 Select OK.
Viewing the address group list

You can organize multiple firewall addresses into an address group to simplify
your firewall policy list. For example, instead of having five identical policies for
five different but related firewall addresses, you might combine the five addresses
into a single address group, which is used by a single firewall policy.
To view the address group list, go to Firewall > Address > Group.
Figure 180:Firewall address group list
Delete
Edit
Create New Select to add an address group.

Group Name The name of the address group.
Members The addresses in the address group.
Delete icon Select to remove the address group. The Delete icon only appears if the
address group is not currently being used by a firewall policy.
Edit icon Select to edit the address group.
Configuring address groups

You can organize multiple firewall addresses into an address group to simplify
your firewall policy list. For example, instead of having five identical policies for
five different but related firewall addresses, you might combine the five addresses
into a single address group, which is used by a single firewall policy.

318 01-30007-0203-20090112
Firewall Address Configuring address groups
Because firewall policies require addresses with homogenous network interfaces,

address groups should contain only addresses bound to the same network
interface, or to Any — addresses whose selected Interface is Any are bound to a
network interface during creation of a firewall policy, rather than during creation of
the firewall address. For example, if address A1 is associated with port1, and
address A2 is associated with port2, they cannot be grouped. However, if A1 and
A2 have an Interface of Any, they can be grouped, even if the addresses involve
different networks.
To organize addresses into an address group

1 Go to Firewall > Address > Group.
You can also create firewall address groups during firewall policy configuration by
selecting Create New from the Address drop-down menu.
Figure 181:Address group options
Group Name Enter a name to identify the address group. Addresses, address
groups, and virtual IPs must have unique names.
Available The list of all configured and default firewall addresses. Use the arrows
Addresses to move selected addresses between the lists of available and member
addresses.
Members The list of addresses included in the address group. Use the arrows to
move selected addresses between the lists of available and member
addresses.
4 Select OK.

01-30007-0203-20090112 319
Configuring address groups Firewall Address

320 01-30007-0203-20090112
Firewall Service Viewing the predefined service list
Firewall Service
Firewall services define one or more protocols and port numbers associated with
each service. Service definitions are used by firewall policies to match session
types.
You can organize related services into service groups to simplify your firewall
policy list.
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall services are
• Viewing the predefined service list
• Viewing the custom service list
• Configuring custom services
• Viewing the service group list
• Configuring service groups
Viewing the predefined service list

Many well-known traffic types have been predefined in firewall services. These
predefined services are defaults, and cannot be edited or removed. If you require
service definitions that are different from the predefined services, you can add
them using custom services. For details, see “Configuring custom services” on
page 325.
To view the predefined service list, go to Firewall > Service.
Figure 182:Predefined service list (partial list shown)
Name The name of the predefined service.

Detail The protocol and port number of the predefined service.

01-30007-0203-20090112 321
Viewing the predefined service list Firewall Service
Table 37: Predefined services
Service name Description IP Protocol Port

AH Authentication Header. AH provides 51
source host authentication and data
integrity, but not secrecy. This protocol is
used for authentication by IPSec remote
gateways set to aggressive mode.
ANY Matches connections using any protocol all all
over IP.
AOL AOL Instant Message protocol. TCP 5190-5194
BGP Border Gateway Protocol. BGP is an TCP 179
interior/exterior routing protocol.
DCE-RPC Distributed Computing Environment / TCP 135
Remote Procedure Calls. Applications
using DCE-RPC can call procedures from UDP 135
another application without having to know
on which host the other application is
running.
DHCP Dynamic Host Configuration Protocol. UDP 67
DHCP allocates network addresses and 68
delivers configuration parameters from
DHCP servers to hosts.
DNS Domain Name Service. DNS resolves TCP 53
domain names into IP addresses.
UDP 53
ESP Encapsulating Security Payload. ESP is 50
used by manual key and AutoIKE IPSec
VPN tunnels for communicating encrypted
data. AutoIKE VPN tunnels use ESP after
establishing the tunnel by IKE.
FINGER A network service providing information TCP 79
about users.
FTP File Transfer Protocol. TCP 21
FTP_GET File Transfer Protocol. This service is for TCP 21
FTP connections which upload files.
FTP_PUT File Transfer Protocol. This service is for TCP 21
FTP connections which download files.
GOPHER Gopher organizes and displays Internet TCP 70
server contents as a hierarchically
structured list of files.
GRE Generic Routing Encapsulation.GRE 47
allows an arbitrary network protocol to be
transmitted over any other arbitrary
network protocol, by encapsulating the
packets of the protocol within GRE
packets.
H323 H.323 multimedia protocol. H.323 is a TCP 1720, 1503
standard approved by the International
Telecommunication Union (ITU) defining
how audiovisual conferencing data can be
transmitted across networks. For more
information, see the FortiGate Support for
H.323 Technical Note.
HTTP Hypertext Transfer Protocol. HTTP is used TCP 80
to browse web pages on the World Wide
Web.
HTTPS HTTP with secure socket layer (SSL) for TCP 443
secure communication with web servers.

322 01-30007-0203-20090112
Firewall Service Viewing the predefined service list
Table 37: Predefined services (Continued)

ICMP_ANY Internet Control Message Protocol. ICMP ICMP N/A
allows control messages and error
reporting between a host and gateway
(Internet).
IKE Internet Key Exchange. IKE obtains UDP 500
authenticated keying material for use with
ISAKMP for IPSEC.
IMAP Internet Message Access Protocol. IMAP TCP 143
retrieves email messages.
INFO_ADDRESS ICMP information request messages. ICMP 17
INFO_REQUEST ICMP address mask request messages. ICMP 15
IRC Internet Relay Chat. IRC allows users to TCP 6660-6669
join chat channels.
Internet- Internet Locator Service. ILS includes TCP 389
Locator-Service LDAP, User Locator Service, and LDAP
over TLS/SSL.
L2TP Layer 2 Tunneling Protocol. L2TP is a TCP 1701
PPP-based tunnel protocol for remote
access.
LDAP Lightweight Directory Access Protocol. TCP 389
LDAP is used to access information
directories.
MGCP Media Gateway Control Protocol. MGCP is UDP 2427, 2727
used by call agents and media gateways
in distributed Voice over IP (VoIP)
systems.
NFS Network File System. NFS allows network TCP 111, 2049
users to mount shared files.
NNTP Network News Transport Protocol. NNTP TCP 119
is used to post, distribute, and retrieve
Usenet messages.
NTP Network Time Protocol. NTP synchronizes TCP 123
a host’s time with a time server.
NetMeeting NetMeeting allows users to teleconference TCP 1720
using the Internet as the transmission
medium.
OSPF Open Shortest Path First. OSPF is a 89
common link state routing protocol.
PC-Anywhere PC-Anywhere is a remote control and file UDP 5632
transfer protocol.
PING Ping sends ICMP echo request/reply to ICMP 8
test connectivity to other hosts.
PING6 Ping6 sends ICMPv6 echo request/replies 58
to network hosts to test IPv6 connectivity
to other hosts.
POP3 Post Office Protocol v3. POP retrieves TCP 110
email messages.
PPTP Point-to-Point Tunneling Protocol. PPTP is TCP 1723
used to tunnel connections between
private network hosts over the Internet.
Note: Also requires IP protocol 47.

01-30007-0203-20090112 323
Viewing the predefined service list Firewall Service

QUAKE Quake multi-player computer game traffic. UDP 26000,
27000,
27910,
27960
RAUDIO RealAudio multimedia traffic. UDP 7070
REXEC Rexec traffic allows specified commands TCP 512
to be executed on a remote host running
the rexecd service (daemon).
RIP Routing Information Protocol. RIP is a UDP 520
common distance vector routing protocol.
This service matches RIP v1.
RLOGIN Remote login traffic. TCP 513
RSH Remote Shell traffic allows specified TCP 514
commands to be executed on a remote
host running the rshd service (daemon).
SAMBA Server Message Block. SMB allows clients TCP 139
to use file and print shares from enabled
hosts. This is primarily used for Microsoft
Windows hosts, but may be used with
operating systems running the Samba
daemon.
SCCP Skinny Client Control Protocol. SCCP is a TCP 2000
Cisco proprietary standard for terminal
control for use with voice over IP (VoIP).
SIP Session Initiation Protocol. SIP allows UDP 5060
audiovisual conferencing data to be
transmitted across networks. For more
information, see the FortiGate SIP Support
Technical Note.
SIP- Session Initiation Protocol used by TCP 1863
MSNmessenger Microsoft Messenger to initiate an
interactive, possibly multimedia session.
SMTP Simple Mail Transfer Protocol. SMTP is TCP 25
sends email messages.
SNMP Simple Network Management Protocol. TCP 161-162
SNMP can be used to monitor and
manage complex networks. UDP 161-162
SSH Secure Shell. SSH allows secure remote TCP 22

management and tunneling.
UDP 22
SYSLOG Syslog service for remote logging. UDP 514
TALK Talk allows conversations between two or UDP 517-518
more users.
TCP Matches connections using any TCP port. TCP 0-65535
TELNET Telnet allows plain text remote TCP 23
management.
TFTP Trivial File Transfer Protocol. TFTP is UDP 69
similar to FTP, but without security
features such as authentication.
TIMESTAMP ICMP timestamp request messages. ICMP 13
UDP Matches connections using any UDP port. UDP 0-65535
UUCP Unix to Unix Copy Protocol. UUCP UDP 540
provides simple file copying.
VDOLIVE VDO Live streaming multimedia traffic. TCP 7000-7010

324 01-30007-0203-20090112
Firewall Service Viewing the custom service list

WAIS Wide Area Information Server. WAIS is an TCP 210
Internet search protocol which may be
used in conjunction with Gopher.
WINFRAME WinFrame provides communications TCP 1494
between computers running Windows NT,
or Citrix WinFrame/MetaFrame.
X-WINDOWS X Window System (also known as X11) TCP 6000-6063
can forward the graphical shell from an X
Window server to X Window client.
Viewing the custom service list

If you need to create a firewall policy for a service that is not in the predefined
service list, you can add a custom service.
To view the custom service list, go to Firewall > Service > Custom.
Figure 183:Custom service list
Delete
Edit
Create New Select Create New to add a custom service.

Service Name The name of the custom service.
Detail The protocol and port numbers for each custom service.
Delete icon Select to remove the custom service. The Delete icon only appears if
the service is not currently being used by a firewall policy.
Edit icon Select to edit the custom service.
Configuring custom services

If you need to create a firewall policy for a service that is not in the predefined
service list, you can add a custom service. You can also create custom services
during firewall policy configuration by selecting Create New from the Service drop-
down menu.
To add a custom TCP or UDP service

1 Go to Firewall > Service > Custom.
3 Set Protocol Type to TCP/UDP.
4 Configure the following.

01-30007-0203-20090112 325
Configuring custom services Firewall Service
Figure 184:New Custom Service - TCP/UDP
Delete
Name Enter a name for the custom service.

Protocol Type Select TCP/UDP.
Protocol Select TCP or UDP as the protocol of the port range being added.
Source Port Specify the Source Port number range for the service by entering the
low and high port numbers. If the service uses one port number, enter
this number in both the Low and High fields. The default values allow
the use of any source port.
Destination Port Specify the Destination Port number range for the service by entering
the low and high port numbers. If the service uses one port number,
enter this number in both the Low and High fields.
Add If the custom service being created requires more than one port range,
select Add to allow more source and destination ranges.
Delete Icon Select to remove the entry from the list.
To add a custom ICMP service

3 Set Protocol Type to ICMP.
Figure 185:New Custom Service - ICMP
Name Enter the name of the ICMP custom service.

Protocol Type Select ICMP.
Type Enter the ICMP type number for the service.
Code If required, enter the ICMP code number for the service.
To add a custom IP service


326 01-30007-0203-20090112
Firewall Service Viewing the service group list
3 Set Protocol Type to IP.

Figure 186:New Custom Service - IP
Name Enter the name of the IP custom service.

Protocol Type Select IP.
Protocol Number The IP protocol number for the service.
Viewing the service group list

You can organize multiple firewall services into a service group to simplify your
firewall policy list. For example, instead of having five identical policies for five
different but related firewall services, you might combine the five services into a
single address group, which is used by a single firewall policy.
Service groups can contain both predefined and custom services. Service groups
cannot contain other service groups.
To view the service group list, go to Firewall > Service > Group.
Figure 187:Sample service group list
Delete
Edit
Create New Select to add a service group.

Group Name The name to identify the service group.
Members The services added to the service group.
Delete icon Select to remove the entry from the list. The Delete icon only appears if
the service group is not selected in a firewall policy.
Edit icon Select to edit the following information: Group Name and Members.
Configuring service groups

You can organize multiple firewall services into a service group to simplify your
firewall policy list. For example, instead of having five identical policies for five
different but related firewall services, you might combine the five services into a
single address group, which is used by a single firewall policy.

01-30007-0203-20090112 327
Configuring service groups Firewall Service
Service groups can contain both predefined and custom services. Service groups
cannot contain other service groups.
To organize services into a service group, go to Firewall > Service > Group.
Service groups can also be created during firewall policy configuration by
selecting Create New from the Service drop-down menu.
Figure 188:Service Group
Group Name Enter a name to identify the service group.

Available The list of configured and predefined services. Use the arrows to move
Services selected services between the lists of available and member services.
Members The list of services in the group. Use the arrows to move selected
services between the lists of available and member services.

328 01-30007-0203-20090112
Firewall Schedule Viewing the recurring schedule list
Firewall Schedule
Firewall schedules control when policies are in effect. You can create one-time
schedules or recurring schedules. One-time schedules are in effect only once for
the period of time specified in the schedule. Recurring schedules are in effect
repeatedly at specified times of the day on specified days of the week.
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall schedules
are configured separately for each virtual domain. For details, see “Using virtual
• Viewing the recurring schedule list
• Configuring recurring schedules
• Viewing the one-time schedule list
• Configuring one-time schedules
Viewing the recurring schedule list

You can create a recurring schedule that activates a policy during a specified
period of time. For example, you might prevent game play during office hours by
creating a recurring schedule.
Note: A recurring schedule with a stop time that occurs before the start time starts at the
start time and finishes at the stop time on the next day. You can use this technique to
create recurring schedules that run from one day to the next. To create a recurring
schedule that runs for 24 hours, set the start and stop times to the same time.
To view the recurring schedule list, go to Firewall > Schedule > Recurring.
Figure 189:Recurring schedule list
Delete
Edit
Create New Select to add a recurring schedule.
Name The name of the recurring schedule.
Day The initials of the days of the week on which the schedule is active.
Start The start time of the recurring schedule.
Stop The stop time of the recurring schedule.
Delete icon Select to remove the schedule from the list. The Delete icon only
appears if the schedule is not being used in a firewall policy.
Edit icon Select to edit the schedule.

01-30007-0203-20090112 329
Configuring recurring schedules Firewall Schedule
Configuring recurring schedules

To add a recurring schedule, go to Firewall > Schedule > Recurring. You can
also create recurring schedules during firewall policy configuration by selecting
Create New from the Schedule drop-down list.
To put a policy into effect for an entire day, set schedule start and stop time to 00.
Figure 190:New Recurring Schedule
Name Enter the name to identify the recurring schedule.

Select Select the days of the week for the schedule to be active.
Start Select the start time for the recurring schedule.
Stop Select the stop time for the recurring schedule.
Viewing the one-time schedule list

You can create a one-time schedule that activates a policy during a specified
period of time. For example, a firewall might be configured with a default policy
that allows access to all services on the Internet at all times, but you could add a
one-time schedule to block access to the Internet during a holiday.
To view the one-time schedule list, go to Firewall > Schedule > One-time.
Figure 191:One-time schedule list
Delete
Edit
Create New Select to add a one-time schedule.

Name The name of the one-time schedule.
Start The start date and time for the schedule.
Stop The stop date and time for the schedule.
Delete icon Select to remove the schedule from the list. The Delete icon only
appears if the schedule is not being used in a firewall policy.
Edit icon Select to edit the schedule.

330 01-30007-0203-20090112
Firewall Schedule Configuring one-time schedules
Configuring one-time schedules

To add a one-time schedule, go to Firewall > Schedule > One-time. You can also
create one-time during firewall policy configuration by selecting Create New from
the Schedule drop-down list.
To put a policy into effect for an entire day, set schedule start and stop time to 00.
Figure 192:New One-time Schedule
Name Enter the name to identify the one-time schedule.

Start Select the start date and time for the schedule.
Stop Select the stop date and time for the schedule.

01-30007-0203-20090112 331
Configuring one-time schedules Firewall Schedule

332 01-30007-0203-20090112
Firewall Virtual IP How virtual IPs map connections through FortiGate units
Firewall Virtual IP
Virtual IP addresses (VIPs) can be used when configuring firewall policies to
translate IP addresses and ports of packets received by a network interface,
including a modem interface.
When the FortiGate unit receives inbound packets matching a firewall policy
whose Destination Address field is a virtual IP, the FortiGate unit applies NAT,
replacing packets’ IP addresses with the virtual IP’s mapped IP address.
IP pools, similarly to virtual IPs, can be used to configure aspects of NAT;
however, IP pools configure dynamic translation of packets’ IP addresses based
on the Destination Interface/Zone, whereas virtual IPs configure dynamic or static
translation of a packets’ IP addresses based upon the Source Interface/Zone.
To implement the translation configured in the virtual IP or IP pool, you must add it
to a NAT firewall policy. For details, see “Configuring virtual IPs” on page 338.
Note: In Transparent mode from the FortiGate CLI you can configure NAT firewall policies
that include Virtual IPs and IP pools. See “Adding NAT firewall policies in transparent mode”
on page 361.
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall virtual IPs
are configured separately for each virtual domain. For details, see “Using virtual
• How virtual IPs map connections through FortiGate units
• Viewing the virtual IP list
• Configuring virtual IPs
• Virtual IP Groups
• Viewing the VIP group list
• Configuring VIP groups
• Health Check Monitor
• IP pools
• Viewing the IP pool list
• Configuring IP Pools
• Double NAT: combining IP pools with virtual IPs
• Adding NAT firewall policies in transparent mode
How virtual IPs map connections through FortiGate units

Virtual IPs can specify translations of packets’ port numbers and/or IP addresses
for both inbound and outbound connections. In Transparent mode, virtual IPs are
available from the FortiGate CLI.

01-30007-0203-20090112 333
How virtual IPs map connections through FortiGate units Firewall Virtual IP
Inbound connections
Virtual IPs can be used in conjunction with firewall policies whose Action is not
DENY to apply bidirectional NAT, also known as inbound NAT.
When comparing packets with the firewall policy list to locate a matching policy, if
a firewall policy’s Destination Address is a virtual IP, FortiGate units compares
packets’ destination address to the virtual IP’s external IP address. If they match,
the FortiGate unit applies the virtual IP’s inbound NAT mapping, which specifies
how the FortiGate unit translates network addresses and/or port numbers of
packets from the receiving (external) network interface to the network interface
connected to the destination (mapped) IP address or IP address range.
In addition to specifying IP address and port mappings between interfaces, virtual
IP configurations can optionally bind an additional IP address or IP address range
to the receiving network interface. By binding an additional IP address, you can
configure a separate set of mappings that the FortiGate unit can apply to packets
whose destination matches that bound IP address, rather than the IP address
already configured for the network interface.
Depending on your configuration of the virtual IP, its mapping may involve port
address translation (PAT), also known as port forwarding or network address port
translation (NAPT), and/or network address translation (NAT) of IP addresses.
If you configure NAT in the virtual IP and firewall policy, the NAT behavior varies
by your selection of:
• static vs. dynamic NAT mapping
• the dynamic NAT’s load balancing style, if using dynamic NAT mapping
• full NAT vs. destination NAT (DNAT)
The following table describes combinations of PAT and/or NAT that are possible
when configuring a firewall policy with a virtual IP.
Static NAT Static, one-to-one NAT mapping: an external IP address is always

translated to the same mapped IP address.
If using IP address ranges, the external IP address range corresponds
to a mapped IP address range containing an equal number of IP
addresses, and each IP address in the external range is always
translated to the same IP address in the mapped range.
Static NAT with Static, one-to-one NAT mapping with port forwarding: an external IP
Port Forwarding address is always translated to the same mapped IP address, and an
external port number is always translated to the same mapped port
number.
If using IP address ranges, the external IP address range corresponds
to a mapped IP address range containing an equal number of IP
addresses, and each IP address in the external range is always
translated to the same IP address in the mapped range. If using port
number ranges, the external port number range corresponds to a
mapped port number range containing an equal number of port
numbers, and each port number in the external range is always
translated to the same port number in the mapped range.

334 01-30007-0203-20090112
Firewall Virtual IP How virtual IPs map connections through FortiGate units
Server Load Dynamic, one-to-many NAT mapping: an external IP address is

Balancing translated to one of the mapped IP addresses, as determined by the
selected load balancing algorithm for more even traffic distribution. The
external IP address is not always translated to the same mapped IP
address.
Server load balancing requires that you configure at least one “real”
server, but can use up to eight. Real servers can be configured with
health check monitors. Health check monitors can be used to gauge
server responsiveness before forwarding packets.
Server Load Dynamic, one-to-many NAT mapping with port forwarding: an external
Balancing with IP address is translated to one of the mapped IP addresses, as
Port Forwarding determined by the selected load balancing algorithm for more even
traffic distribution. The external IP address is not always translated to
the same mapped IP address.
Server load balancing requires that you configure at least one “real”
server, but can use up to eight. Real servers can be configured with
health check monitors. Health check monitors can be used to gauge
server responsiveness before forwarding packets.
Note: If the NAT check box is not selected when building the firewall policy, the resulting
policy does not perform full (source and destination) NAT; instead, it performs destination
network address translation (DNAT).
For inbound traffic, DNAT translates packets’ destination address to the mapped private IP
address, but does not translate the source address. The private network is aware of the
source’s public IP address. For reply traffic, the FortiGate unit translates packets’ private
network source IP address to match the destination address of the originating packets,
which is maintained in the session table.
A typical example of static NAT is to allow client access from a public network to a
web server on a private network that is protected by a FortiGate unit. Reduced to
its essence, this example involves only three hosts, as shown in Figure 193: the
web server on a private network, the client computer on another network, such as
the Internet, and the FortiGate unit connecting the two networks.
When a client computer attempts to contact the web server, it uses the virtual IP
on the FortiGate unit’s external interface. The FortiGate unit receives the packets.
The addresses in the packets are translated to private network IP addresses, and
the packet is forwarded to the web server on the private network.
Figure 193:A simple static NAT virtual IP example
The packets sent from the client computer have a source IP of 192.168.37.55 and
a destination IP of 192.168.37.4. The FortiGate unit receives these packets at its
external interface, and matches them to a firewall policy for the virtual IP. The
virtual IP settings map 192.168.37.4 to 10.10.10.42, so the FortiGate unit changes
the packets’ addresses. The source address is changed to 10.10.10.2 and the
destination is changed to 10.10.10.42. The FortiGate unit makes a note of this
translation in the firewall session table it maintains internally. The packets are then
sent on to the web server.

01-30007-0203-20090112 335
How virtual IPs map connections through FortiGate units Firewall Virtual IP
Figure 194:Example of packet address remapping during NAT from client to server
Note that the client computer’s address does not appear in the packets the server
receives. After the FortiGate unit translates the network addresses, there is no
reference to the client computer’s IP address, except in its session table. The web
server has no indication that another network exists. As far as the server can tell,
all packets are sent by the FortiGate unit.
When the web server replies to the client computer, address translation works
similarly, but in the opposite direction. The web server sends its response packets
having a source IP address of 10.10.10.42 and a destination IP address of
10.10.10.2. The FortiGate unit receives these packets on its internal interface.
This time, however, the session table is used to recall the client computer’s IP
address as the destination address for the address translation. In the reply
packets, the source address is changed to 192.168.37.4 and the destination is
changed to 192.168.37.55. The packets are then sent on to the client computer.
The web server’s private IP address does not appear in the packets the client
receives. After the FortiGate unit translates the network addresses, there is no
reference to the web server’s network. The client has no indication that the web
server’s IP address is not the virtual IP. As far as the client is concerned, the
FortiGate unit’s virtual IP is the web server.
Figure 195:Example of packet address remapping during NAT from server to client
In the previous example, the NAT check box is checked when configuring the
firewall policy. If the NAT check box is not selected when building the firewall
policy, the resulting policy does not perform full NAT; instead, it performs
destination network address translation (DNAT).
For inbound traffic, DNAT translates packets’ destination address to the mapped
private IP address, but does not translate the source address. The web server
would be aware of the client’s IP address. For reply traffic, the FortiGate unit
translates packets’ private network source IP address to match the destination
address of the originating packets, which is maintained in the session table.
Outbound connections
Virtual IPs can also affect outbound NAT, even though they are not selected in an
outbound firewall policy. If no virtual IPs are configured, FortiGate units apply
traditional outbound NAT to connections outbound from private network IP
addresses to public network IP addresses. However, if virtual IP configurations
exist, FortiGate units use virtual IPs’ inbound NAT mappings in reverse to apply
outbound NAT, causing IP address mappings for both inbound and outbound
traffic to be symmetric.

336 01-30007-0203-20090112
Firewall Virtual IP Viewing the virtual IP list
For example, if a network interface’s IP address is 10.10.10.1, and its bound

virtual IP’s external IP is 10.10.10.2, mapping inbound traffic to the private
network IP address 192.168.2.1, traffic outbound from 192.168.2.1 will be
translated to 10.10.10.2, not 10.10.10.1
VIP requirements
Virtual IPs have the following requirements.
• The Mapped IP Address/Range cannot be 0.0.0.0 or 255.255.255.255.
• The Mapped IP Address/Range must not include any interface IP
addresses.
• If the virtual IP is mapped to a range of IP addresses and its type is Static
NAT, the External IP Address/Range cannot be 0.0.0.0.
• When port forwarding, the External IP Address/Range cannot include any
other interface IP addresses.
• When port forwarding, the count of mapped port numbers and external port
numbers must be the same, and the last port number in the range must not
exceed 65535.
• Virtual IP names must be different from address or address group names.
• A physical external IP address can be used as the external VIP IP address.
• Duplicate entries or overlapping ranges are not permitted.
Viewing the virtual IP list

To view the virtual IP list, go to Firewall > Virtual IP > Virtual IP.
Figure 196:Virtual IP list
Delete
Edit
Create New Select to add a virtual IP.

Name The name of the virtual IP.
IP The bound network interface and external IP address or IP address,
separated by a slash (/).
Service Port The external port number or port number range. This field is empty if the
virtual IP does not specify port forwarding.
Map to IP/IP The mapped to IP address or address range on the destination network.
Range
Map to Port The mapped to port number or port number range. This field is empty if
the virtual IP does not specify port forwarding.
Delete icon Remove the virtual IP from the list. The Delete icon only appears if the
virtual IP is not selected in a firewall policy.
Edit icon Edit the virtual IP to change any virtual IP option including the virtual IP
name.

01-30007-0203-20090112 337
Configuring virtual IPs Firewall Virtual IP
Configuring virtual IPs

A virtual IP’s external IP address can be a single IP address or an IP address
range, and is bound to a FortiGate unit interface. When you bind the virtual IP’s
external IP address to a FortiGate unit interface, by default, the network interface
responds to ARP requests for the bound IP address or IP address range. Virtual
IPs use proxy ARP, as defined in RFC 1027, so that the FortiGate unit can
respond to ARP requests on a network for a server that is actually installed on
another network. To disable ARP replies, see the FortiGate CLI Reference.
A virtual IP’s mapped IP address can be a single IP address, IP address range, or
set of defined servers for load balancing.
When the FortiGate unit receives packets matching a firewall policy whose
Destination Address field is a virtual IP, the FortiGate unit applies NAT, replacing
the packet’s destination IP address with the virtual IP’s mapped IP address.
To implement the translation configured in the virtual IP or IP pool, you must add it
to a NAT firewall policy. For example, to add a firewall policy that maps public
network addresses to a private network, add an external to internal firewall policy
whose Destination Address field is a virtual IP.
Figure 197:Creating a Virtual IP
Name Enter or change the name to identify the virtual IP. To avoid
confusion, addresses, address groups, and virtual IPs cannot have
the same names.
External Interface Select the virtual IP external interface from the list. The external
interface is connected to the source network and receives the packets
to be forwarded to the destination network. You can select any
FortiGate interface, VLAN subinterface, VPN interface, or modem
interface.
Type Select Static NAT or Server Load Balance. For details about VIP
types, see “How virtual IPs map connections through FortiGate units”
on page 333.
External IP Enter the external IP address that you want to map to an address on
Address/Range the destination network.
To configure a dynamic virtual IP that accepts connections for any IP
address, set the external IP address to 0.0.0.0. For a static NAT
dynamic virtual IP you can only add one mapped IP address. For a
load balance dynamic virtual IP you can specify a single mapped
address or a mapped address range.

338 01-30007-0203-20090112
Firewall Virtual IP Configuring virtual IPs
Mapped IP Enter the real IP address on the destination network to which the
Address/Range external IP address is mapped.
You can also enter an address range to forward packets to multiple IP
addresses on the destination network.
For a static NAT virtual IP, if you add a mapped IP address range the
FortiGate unit calculates the external IP address range and adds the
IP address range to the External IP Address/Range field.
This option appears only if Type is Static NAT.
Method If you select Server Load Balance, you can select one of the following
load balancing methods.
• Static: The traffic load is spread evenly across all servers, no
additional server is required.
• Round Robin: Directs request to the next server, and treats all
servers as equals regardless of response time or number of
connections. Dead servers or non responsive servers are avoided.
A separate server is required.
• Weighted: Servers with a higher weight value will receive a larger
percentage of connections. Set the server weight when adding a
server.
This option appears only if Type is Server Load Balance.
Port Forwarding Select to perform port address translation (PAT).
Protocol Select the protocol of the forwarded packets.
This option appears only if Port Forwarding is enabled.
External Service Enter the external interface port number for which you want to
Port configure port forwarding.
Map to Port Enter the port number on the destination network to which the
external port number is mapped.
You can also enter a port number range to forward packets to multiple
ports on the destination network.
For a virtual IP with static NAT, if you add a map to port range the
FortiGate unit calculates the external port number range and adds the
port number range to the External Service port field.
Real Servers If you select Server Load Balancing for the Type, enter the real server
IP addresses. At least one IP address is required, but you can enter
up to eight (8) real server IP addresses per virtual IP (VIP).
To enter a server IP address, select Add under Real Servers and
enter the following information:
• IP: Enter the IP address of the server.
• Port: If you enable port forwarding, enter the port number on the
destination network to which the external port number is mapped.
• Weight: Determines the weight value of a specific server. The
higher the weight value, the higher the percentage of connections
the server will handle. A range of 1-255 can be used. This option is
available only if Method is Weighted.
• Health Check: Enable this option to use ping detection to check
the status of the server before forwarding the session.
• Monitors: If Health Check is selected, select which health check
monitor method will be used to perform the health check. For
details on configuring a health check monitor, see “Health Check
Monitor” on page 355.
This option appears only if Type is Server Load Balance.

01-30007-0203-20090112 339
HTTP Multiplexing Select to use the FortiGate unit’s HTTP proxy to multiplex multiple
client connections destined for the web server into a few connections
between the FortiGate unit and the web server. This can improve
performance by reducing server overhead associated with
establishing multiple connections. The server must be HTTP/1.1
compliant.
This option appears only if Port Forwarding is selected.
Note: Additional HTTP Multiplexing options are available in the CLI.
For details, see the FortiGate CLI Reference.
Preserve Client IP Select to preserve the IP address of the client in the X-Forwarded-
For HTTP header. This can be useful if you require logging on the
server of the client’s original IP address. If this option is not selected,
the header will contain the IP address of the FortiGate unit.
This option appears only if Port Forwarding is selected, and is
available only if HTTP Multiplexing is selected.
SSL Offloading Select to accelerate clients’ SSL connections to the server by using
the FortiGate unit to perform SSL operations, then select which
segments of the connection will receive SSL offloading.
• Client <-> FortiGate
Select to apply hardware accelerated SSL only to the part of the
connection between the client and the FortiGate unit. The segment
between the FortiGate unit and the server will use clear text
communications. This results in best performance, but cannot be
used in failover configurations where the failover path does not
have an SSL accelerator.
• Client <-> FortiGate <-> Server
Select to apply hardware accelerated SSL to both parts of the
connection: the segment between client and the FortiGate unit,
and the segment between the FortiGate unit and the server. The
segment between the FortiGate unit and the server will use
encrypted communications, but the handshakes will be
abbreviated. This results in performance which is less than the
other option, but still improved over communications without SSL
acceleration, and can be used in failover configurations where the
failover path does not have an SSL accelerator. If the server is
already configured to use SSL, this also enables SSL acceleration
without requiring changes to the server’s configuration.
SSL 3.0, TLS 1.0, and TLS 1.1 are supported.
This option appears only if Port Forwarding is selected, and only on
FortiGate models whose hardware support SSL acceleration, such as
FortiGate-3600A.
Note: Additional SSL Offloading options are available in the CLI. For
details, see the FortiGate CLI Reference.
Certificate Select which SSL certificate to use with SSL Offloading.
This option appears only if Port Forwarding is selected, and is
available only if SSL Offloading is selected.
To configure a virtual IP
1 Go to Firewall > Virtual IP > Virtual IP.

340 01-30007-0203-20090112
3 Configure the virtual IP by entering the virtual IP address, if any, that will be bound
to the network interface, and selecting the mapping type and mapped IP
address(es) and/or port(s). For configuration examples of each type, see:
• “Adding a static NAT virtual IP for a single IP address” on page 341
• “Adding a static NAT virtual IP for an IP address range” on page 343
• “Adding static NAT port forwarding for a single IP address and a single port” on
page 344
• “Adding static NAT port forwarding for an IP address range and a port range”
on page 346
• “Adding a server load balance virtual IP” on page 348
• “Adding a server load balance port forwarding virtual IP” on page 350
• “Adding dynamic virtual IPs” on page 352
• “Adding a virtual IP with port translation only” on page 353
4 Select OK.
The virtual IP appears in the virtual IP list.
5 To implement the virtual IP, select the virtual IP in a firewall policy.
For example, to add a firewall policy that maps public network addresses to a
private network, you might add an external to internal firewall policy and select the
Source Interface/Zone to which a virtual IP is bound, then select the virtual IP in
the Destination Address field of the policy. For details, see “Configuring firewall
policies” on page 297.
Adding a static NAT virtual IP for a single IP address

The IP address 192.168.37.4 on the Internet is mapped to 10.10.10.42 on a
private network. Attempts to communicate with 192.168.37.4 from the Internet are
translated and sent to 10.10.10.42 by the FortiGate unit. The computers on the
Internet are unaware of this translation and see a single computer at 192.168.37.4
rather than a FortiGate unit with a private network behind it.
Figure 198:Static NAT virtual IP for a single IP address example
To add a static NAT virtual IP for a single IP address


01-30007-0203-20090112 341
3 Use the following procedure to add a virtual IP that allows users on the Internet to
connect to a web server on the DMZ network. In our example, the wan1 interface
of the FortiGate unit is connected to the Internet and the dmz1 interface is
connected to the DMZ network.
Figure 199:Virtual IP options: static NAT virtual IP for a single IP address
Name static_NAT
External Interface wan1
Type Static NAT
External IP The Internet IP address of the web server.
Address/Range The external IP address is usually a static IP address obtained from
your ISP for your web server. This address must be a unique IP
address that is not used by another host and cannot be the same as
the IP address of the external interface the virtual IP will be using.
However, the external IP address must be routed to the selected
interface. The virtual IP address and the external IP address can be
on different subnets. When you add the virtual IP, the external
interface responds to ARP requests for the external IP address.
Map to IP/IP Range The IP address of the server on the internal network. Since there is
only one IP address, leave the second field blank.
4 Select OK.
To add a static NAT virtual IP for a single IP address to a firewall policy

Add a external to dmz1 firewall policy that uses the virtual IP so that when users
on the Internet attempt to connect to the web server IP address packets pass
through the FortiGate unit from the external interface to the dmz1 interface. The
virtual IP translates the destination address of these packets from the external IP
to the DMZ network IP address of the web server.
1 Go to Firewall > Policy and select Create New.
2 Configure the firewall policy:
Source Interface/Zone external

Source Address All (or a more specific address)
Destination Interface/Zone dmz1
Destination Address simple_static_nat
Schedule always
Service HTTP
Action ACCEPT
3 Select NAT.
4 Select OK.

342 01-30007-0203-20090112
Adding a static NAT virtual IP for an IP address range

The IP address range 192.168.37.4-192.168.37.6 on the Internet is mapped to
10.10.10.42-10.10.123.44 on a private network. Packets from Internet computers
communicating with 192.168.37.4 are translated and sent to 10.10.10.42 by the
FortiGate unit. Similarly, packets destined for 192.168.37.5 are translated and
sent to 10.10.10.43, and packets destined for 192.168.37.6 are translated and
sent to 10.10.10.44. The computers on the Internet are unaware of this translation
and see three computers with individual IP addresses rather than a FortiGate unit
with a private network behind it.
Figure 200:Static NAT virtual IP for an IP address range example
To add a static NAT virtual IP for an IP address range

connect to three individual web servers on the DMZ network. In this example, the
wan1 interface of the FortiGate unit is connected to the Internet and the dmz1
interface is connected to the DMZ network.
Figure 201:Virtual IP options: static NAT virtual IP with an IP address range

01-30007-0203-20090112 343
Name static_NAT_range
Type Static NAT
External IP Address/Range The Internet IP address range of the web servers.
The external IP addresses are usually static IP addresses
obtained from your ISP for your web server. These
addresses must be unique IP addresses that are not used by
another host and cannot be the same as the IP addresses of
the external interface the virtual IP will be using. However,
the external IP addresses must be routed to the selected
interface. The virtual IP addresses and the external IP
address can be on different subnets. When you add the
virtual IP, the external interface responds to ARP requests
for the external IP addresses.
Map to IP/IP Range The IP address range of the servers on the internal network.
Define the range by entering the first address of the range in
the first field and the last address of the range in the second
field.
4 Select OK.
To add a static NAT virtual IP with an IP address range to a firewall policy

Add a wan1 to dmz1 firewall policy that uses the virtual IP so that when users on
the Internet attempt to connect to the server IP addresses, packets pass through
the FortiGate unit from the wan1 interface to the dmz1 interface. The virtual IP
translates the destination addresses of these packets from the wan1 IP to the
DMZ network IP addresses of the servers.
Source Interface/Zone wan1

Destination Address static_NAT_range
Schedule always
Service HTTP
Action ACCEPT
3 Select NAT.
4 Select OK.
Adding static NAT port forwarding for a single IP address and a single port
The IP address 192.168.37.4, port 80 on the Internet is mapped to 10.10.10.42,
port 8000 on a private network. Attempts to communicate with 192.168.37.4,
port 80 from the Internet are translated and sent to 10.10.10.42, port 8000 by the
FortiGate unit. The computers on the Internet are unaware of this translation and
see a single computer at 192.168.37.4, port 80 rather than a FortiGate unit with a
private network behind it.

344 01-30007-0203-20090112
Figure 202:Static NAT virtual IP port forwarding for a single IP address and a single
port example
To add static NAT virtual IP port forwarding for a single IP address and a
single port
connect to a web server on the DMZ network. In our example, the wan1 interface
Figure 203:Virtual IP options: Static NAT port forwarding virtual IP for a single IP
address and a single port
Name Port_fwd_NAT_VIP
Type Static NAT
External IP Address/Range The Internet IP address of the web server.
The external IP address is usually a static IP address
obtained from your ISP for your web server. This address
must be a unique IP address that is not used by another host
and cannot be the same as the IP address of the external
interface the virtual IP will be using. However, the external IP
address must be routed to the selected interface. The virtual
IP address and the external IP address can be on different
subnets. When you add the virtual IP, the external interface
responds to ARP requests for the external IP address.

01-30007-0203-20090112 345
Map to IP/IP Range The IP address of the server on the internal network. Since
there is only one IP address, leave the second field blank.
Port Forwarding Selected
Protocol TCP
External Service Port The port traffic from the Internet will use. For a web server,
this will typically be port 80.
Map Port The port on which the server expects traffic. Since there is
only one port, leave the second field blank.
4 Select OK.
To add static NAT virtual IP port forwarding for a single IP address and a
single port to a firewall policy
the Internet attempt to connect to the web server IP addresses, packets pass
through the FortiGate unit from the wan1 interface to the dmz1 interface. The
virtual IP translates the destination addresses and ports of these packets from the
external IP to the dmz network IP addresses of the web servers.

Destination Address Port_fwd_NAT_VIP
Schedule always
Service HTTP
Action ACCEPT
3 Select NAT.
4 Select OK.
Adding static NAT port forwarding for an IP address range and a port range
Ports 80 to 83 of addresses 192.168.37.4 to 192.168.37.7 on the Internet are
mapped to ports 8000 to 8003 of addresses 10.10.10.42 to 10.10.10.44 on a
private network. Attempts to communicate with 192.168.37.5, port 82 from the
Internet, for example, are translated and sent to 10.10.10.43, port 8002 by the
see a single computer at 192.168.37.5 rather than a FortiGate unit with a private
network behind it.

346 01-30007-0203-20090112
Figure 204:Static NAT virtual IP port forwarding for an IP address range and a port
range example
To add static NAT virtual IP port forwarding for an IP address range and a
port range
connect to a web server on the DMZ network. In this example, the external
interface of the FortiGate unit is connected to the Internet and the dmz1 interface
is connected to the DMZ network.
Name Port_fwd_NAT_VIP_port_range
External Interface external
Type Static NAT
External IP Address/Range The external IP addresses are usually static IP addresses
obtained from your ISP. This addresses must be unique, not
used by another host, and cannot be the same as the IP
address of the external interface the virtual IP will be using.
However, the external IP addresses must be routed to the
selected interface. The virtual IP addresses and the external
IP address can be on different subnets. When you add the
virtual IP, the external interface responds to ARP requests
for the external IP addresses.
Map to IP/IP Range The IP addresses of the server on the internal network.
Define the range by entering the first address of the range in
the first field and the last address of the range in the second
field.
Protocol TCP
External Service Port The ports that traffic from the Internet will use. For a web
server, this will typically be port 80.
Map Port The ports on which the server expects traffic. Define the
range by entering the first port of the range in the first field
and the last port of the range in the second field. If there is
only one port, leave the second field blank.
4 Select OK.

01-30007-0203-20090112 347
To add static NAT virtual IP port forwarding for an IP address range and a
port range to a firewall policy
Add a external to dmz1 firewall policy that uses the virtual IP so that when users
on the Internet attempt to connect to the web server IP addresses, packets pass
through the FortiGate unit from the external interface to the dmz1 interface. The
virtual IP translates the destination addresses and ports of these packets from the
external IP to the dmz network IP addresses of the web servers.
Source Interface/Zone external

Destination Address Port_fwd_NAT_VIP_port_range
Schedule always
Service HTTP
Action ACCEPT
3 Select NAT.
4 Select OK.
Adding a server load balance virtual IP

In this example the IP address 192.168.37.4 on the Internet, is mapped to the
following servers behind the fortiGate unit, 10.10.123.42, 10.10.123.43, and
10.10.123.44. The IP address mapping is determined by the FortiGate unit’s load
balancing algorithm. Attempts to communicate with 192.168.37.4 from the Internet
are translated and sent to 10.10.10.42, 10.10.10.43, or 10.10.10.44 by the
see a single computer at 192.168.37.4 rather than a FortiGate unit with a private
network behind it.
Note: Server load balancing maps a single IP on one network to up to eight real server IPs
on another network. At least one real address must be added to use this feature
Figure 205:Server Load balance virtual IP

348 01-30007-0203-20090112
To add a server load balance virtual IP

connect to a web server on the DMZ network. In this example, the wan1 interface
Figure 206:Virtual IP options: server load balancing virtual IP
Name Load_Bal_VIP
Type Server Load Balance
External IP address/Range The public IP addresses of the web servers.
and cannot be the same as the IP address of the external
Method Select one of the load balance methods. For details, see
“Configuring virtual IPs” on page 338.
Real Servers If you select Server Load Balancing for the VIP type, enter
the real server IP addresses. For details about real server
settings, see “Configuring virtual IPs” on page 338.
4 Select OK.
To add a server load balance virtual IP to a firewall policy

the Internet attempt to connect to the web server’s IP address, packets pass
through the FortiGate unit from the wan1 interface to the dmz1 interface. The
virtual IP translates the destination address of these packets from the external IP
to the dmz network IP addresses of the web servers.

01-30007-0203-20090112 349

Destination Address Server_Load_Bal_VIP
Schedule always
Service HTTP
Action ACCEPT
3 Select NAT.
4 Select OK.
Adding a server load balance port forwarding virtual IP

In this example, connections to 192.168.37.4 on the Internet are mapped to
10.10.10.42, 10.10.10.43, and 10.10.10.44 on a private network. The IP address
mapping is determined by the FortiGate unit load balancing algorithm. The
external service port on 192.168.37.4 is mapped to specified ports in conjunction
with the specified IP addresses. The computers on the Internet are unaware of
this translation and see a single computer at 192.168.37.4 rather than a FortiGate
unit with a private network behind it.
Figure 207:Server load balance virtual IP port forwarding
To add a server load balance port forwarding virtual IP

connect to a web server on the DMZ network. In this example, the wan1 interface

350 01-30007-0203-20090112
Figure 208:Server load balanced port forwarding
Name Load_Bal_VIP_port_forward
Type Server Load Balance
External IP Address/Range The public IP addresses of the web servers.
and cannot be the same as the IP address of the wan1
Method Select one of the load balance methods. For details, see
“Configuring virtual IPs” on page 338.
Real Servers If you select Server Load Balancing for the VIP type, enter
the real server IP addresses. For details about real server
settings, see “Configuring virtual IPs” on page 338.
Protocol TCP
External Service Port The ports that traffic from the Internet will use. For a web
server, this will typically be port 80.
4 Select OK.

01-30007-0203-20090112 351
To add a server load balance virtual IP to a firewall policy

the Internet attempt to connect to the web server IP address packets pass through
the FortiGate unit from the wan1 interface to the dmz1 interface. The virtual IP
translates the destination address of these packets from the wan1 IP to the dmz
network IP addresses of the web servers.

Destination Address Load_Bal_VIP_port_forward
Schedule always
Service HTTP
Action ACCEPT
3 Select NAT.
4 Select OK.
Adding dynamic virtual IPs

Adding a dynamic virtual IP is similar to adding a virtual IP. The difference is that
the External IP address must be set to 0.0.0.0 so the External IP address matches
any IP address.
To add a dynamic virtual IP

3 Enter a name for the dynamic virtual IP.
4 Select the virtual IP External Interface from the list.
The external interface is connected to the source network and receives the
packets to be forwarded to the destination network.
Select any firewall interface or a VLAN subinterface.
5 Set the External IP Address to 0.0.0.0.
The 0.0.0.0 External IP Address matches any IP address.
6 Enter the Map to IP address to which to map the external IP address. For
example, the IP address of a PPTP server on an internal network.
7 Select Port Forwarding.
8 For Protocol, select TCP.
9 Enter the External Service Port number for which to configure dynamic port
forwarding.
The external service port number must match the destination port of the packets
to be forwarded. For example, if the virtual IP provides PPTP passthrough access
from the Internet to a PPTP server, the external service port number should be
1723 (the PPTP port).

352 01-30007-0203-20090112
Firewall Virtual IP Virtual IP Groups
10 Enter the Map to Port number to be added to packets when they are forwarded.
Enter the same number as the External Service Port if the port is not to be
translated.
11 Select OK.
Adding a virtual IP with port translation only

When adding a virtual IP, if you enter a virtual IP address that is the same as the
mapped IP address and apply port forwarding, the destination IP address will be
unchanged, but the port number will be translated.
Note: To apply port forwarding to the external interface without binding a virtual IP address
to it, enter the IP address of the network interface instead of a virtual IP address, then
configure port forwarding as usual.
To add a virtual IP with port translation only

3 Enter a name for the dynamic virtual IP.
4 Select the virtual IP External Interface from the list.
The external interface is connected to the source network and receives the
packets to be forwarded to the destination network.
Select any firewall interface or a VLAN subinterface.
5 Set the External IP Address as the mapped IP address.
6 Enter the Map to IP address to which to map the external IP address. For
example, the IP address of a PPTP server on an internal network.
7 Select Port Forwarding.
8 For Protocol, select TCP.
9 Enter the External Service Port number for which to configure dynamic port
forwarding.
The external service port number must match the destination port of the packets
to be forwarded. For example, if the virtual IP provides PPTP passthrough access
from the Internet to a PPTP server, the external service port number should be
1723 (the PPTP port).
10 Enter the Map to Port number to be added to packets when they are forwarded.
11 Select OK.
Virtual IP Groups
You can organize multiple virtual IPs into a virtual IP group to simplify your firewall
policy list. For example, instead of having five identical policies for five different
but related virtual IPs located on the same network interface, you might combine
the five virtual IPs into a single virtual IP group, which is used by a single firewall
policy.
Firewall policies using VIP Groups are matched by comparing both the member
VIP IP address(es) and port number(s).

01-30007-0203-20090112 353
Viewing the VIP group list Firewall Virtual IP
Viewing the VIP group list

To view the virtual IP group list, go to Firewall > Virtual IP > VIP Group.
Figure 209:VIP Group list
Delete
Edit
Create New Select to add a new VIP group. See “Configuring VIP groups” on
page 354.
Group Name The name of the virtual IP group.
Members Lists the group members.
Interface Displays the interface that the VIP group belongs to.
Delete icon Remove the VIP group from the list. The Delete icon only appears if the
VIP group is not being used in a firewall policy.
Edit icon Edit the VIP group information, including the group name and
membership.
Configuring VIP groups

To add a VIP group, go to Firewall > Virtual IP > VIP Group and select Create
new. To edit a VIP group, go to Firewall > Virtual IP > VIP Group and select the
Edit icon for the VIP group to edit.
Figure 210:Editing a VIP group
Configure the following settings and select OK:

354 01-30007-0203-20090112
Firewall Virtual IP Health Check Monitor
Group Name Enter or modify the group name.

Interface Select the interface for which you want to create the VIP
group. If you are editing the group, the Interface box is
grayed out.
Available VIPs and Select the up or down arrow to move virtual IPs between
Members Available VIPs and Members. Members contains virtual IPs
that are a part of this virtual IP group.
Health Check Monitor

When Health Check is enabled for virtual IPs of the server load balancing type,
you can specify which health check monitor configuration to use when polling to
determine a server’s connectivity status.
Health check monitor configurations can specify TCP, HTTP or ICMP PING. A
health check occurs every number of seconds indicated by the interval. If a reply
is not received within the timeout period, and you have configured the health
check to retry, it will attempt a health check again; otherwise, the server is
deemed unresponsive, and load balancing will compensate by disabling traffic to
that server until it becomes responsive again.
Health check monitor configurations are not active until used by a VIP. For
information on enabling health checks for a VIP and specifying which health check
monitor configuration a VIP will use, see “Configuring virtual IPs” on page 338.
Figure 211:Health Check Monitor
Delete
Edit
Create New Select to add a health check monitor configuration.

Name The name of the health check monitor configuration.
Details The details of the health check monitor configuration, which vary by
the type of the health check monitor, and do not include the interval,
timeout, or retry, which are settings common to all types.
This field is empty if the type of the health check monitor is PING.
Select Delete to remove the health check monitor configuration. This
option appears only if the health check monitor configuration is not
currently being used by a VIP configuration.
Select Edit to change the health check monitor configuration.
To create a health check monitor configuration

1 Go to Firewall > Virtual IP > Health Check Monitor.

01-30007-0203-20090112 355
IP pools Firewall Virtual IP
Name Enter the name of the health check monitor configuration.

Type Select the protocol used to perform the health check.
• TCP
• HTTP
• PING
Port Enter the port number used to perform the health check.
This option does not appear if the Type is PING.
URL Enter the URL that will receive the HTTP request.
This option appears only if Type is HTTP.
Matched Content Enter the HTTP reply content that must be present to indicate proper
server connectivity.
This option appears only if Type is HTTP.
Interval Enter the number of seconds between each server health check.
Timeout Enter the number of seconds which must pass after the server health
check to indicate a failed health check.
Retry Enter the number of times, if any, a failed health check will be retried
before the server is determined to be inaccessible.
4 Select OK.
IP pools
Use IP pools to add NAT policies that translate source addresses to addresses
randomly selected from the IP pool, rather than the IP address assigned to that
FortiGate unit interface. In Transparent mode, IP pools are available from the
FortiGate CLI.
An IP pool defines an address or a range of IP addresses, all of which respond to
ARP requests on the interface to which the IP pool is added.
Select Enable Dynamic IP Pool in a firewall policy to translate the source address
of outgoing packets to an address randomly selected from the IP pool. An IP pool
list appears when the policy destination interface is the same as the IP pool
interface.
With an IP pool added to the internal interface, you can select Dynamic IP pool for
policies with the internal interface as the destination.
Add multiple IP pools to any interface and select the IP pool to use when
configuring a firewall policy.
A single IP address is entered normally. For example, 192.168.110.100 is a
valid IP pool address. If an IP address range is required, use either of the
following formats.
• x.x.x.x-x.x.x.x, for example 192.168.110.100-192.168.110.120
• x.x.x.[x-x], for example 192.168.110.[100-120]
IP pools and dynamic NAT

Use IP pools for dynamic NAT. For example, an organization might have
purchased a range of Internet addresses but has only one Internet connection on
the external interface of the FortiGate unit.

356 01-30007-0203-20090112
Firewall Virtual IP IP pools
Assign one of the organization’s Internet IP addresses to the external interface of

the FortiGate unit. If the FortiGate unit is operating in NAT/Route mode, all
connections from the network to the Internet appear to come from this IP address.
For connections to originate from all the Internet IP addresses, add this address
range to an IP pool for the external interface. Then select Dynamic IP Pool for all
policies with the external interface as the destination. For each connection, the
firewall dynamically selects an IP address from the IP pool to be the source
address for the connection. As a result, connections to the Internet appear to be
originating from any of the IP addresses in the IP pool.
IP Pools for firewall policies that use fixed ports

Some network configurations do not operate correctly if a NAT policy translates
the source port of packets used by the connection. NAT translates source ports to
keep track of connections for a particular service. Select fixed port for NAT
policies to prevent source port translation. However, selecting fixed port means
that only one connection can be supported through the firewall for this service. To
be able to support multiple connections, add an IP pool to the destination
interface, and then select dynamic IP pool in the policy. The firewall randomly
selects an IP address from the IP pool and assigns it to each connection. In this
case the number of connections that the firewall can support is limited by the
number of IP addresses in the IP pool.
Source IP address and IP pool address matching

When the source addresses are translated to the IP pool addresses, one of the
following three cases may occur:
Scenario 1: The number of source addresses equals that of IP pool

addresses
In this case, the FortiGate unit will always match the IP addressed one to one.
If you use fixed port in such a case, the FortiGate unit will preserve the original
source port. However, this may cause conflicts if more than one firewall policy
uses the same IP pool, or the same IP addresses are used in more than one IP
pool.
Original address Change to

192.168.1.1 172.16.30.1
192.168.1.2 172.16.30.2
...... ......
192.168.1.254 172.16.30.254
Scenario 2: The number of source addresses is more than that of IP pool

addresses
In this case, the FortiGate unit translates IP addresses using a wrap-around
mechanism.
If you use fixed port in such a case, the FortiGate unit preserves the original
source port. But conflicts may occur since users may have different sessions
using the same TCP 5 tuples.

01-30007-0203-20090112 357
Viewing the IP pool list Firewall Virtual IP

192.168.1.1 172.16.30.10
192.168.1.2 172.16.30.11
...... ......
192.168.1.10 172.16.30.19
192.168.1.11 172.16.30.10
192.168.1.12 172.16.30.11
192.168.1.13 172.16.30.12
...... ......
Scenario 3: The number of source addresses is fewer than that of IP pool

addresses
In this case, some of the IP pool addresses will used and the rest of them will not
be used.

192.168.1.1 172.16.30.10
192.168.1.2 172.16.30.11
192.168.1.3 172.16.30.12
No more source addresses 172.16.30.13 and other
addresses will not be used
Viewing the IP pool list

If virtual domains are enabled on the FortiGate unit, IP pools are created
separately for each virtual domain. To access IP pools, select a virtual domain
from the list on the main menu.
To view the IP pool list go to Firewall > Virtual IP > IP Pool.
Figure 212:IP pool list
Delete
Edit
Create New Select to add an IP pool.
Name Enter the name of the IP pool.
Start IP Enter the start IP defines the start of an address range.
End IP Enter the end IP defines the end of an address range.

358 01-30007-0203-20090112
Firewall Virtual IP Configuring IP Pools
Delete icon Select to remove the entry from the list. The Delete icon only appears if
the IP pool is not being used in a firewall policy.
Edit icon Select to edit the following information: Name, Interface, IP
Range/Subnet.
Configuring IP Pools
To add an IP pool, go to Firewall > Virtual IP > IP Pool.
Figure 213:New Dynamic IP Pool
Name Enter the name of the IP pool.

Interface Select the interface to which to add an IP pool.
IP Range/Subnet Enter the IP address range for the IP pool. The IP range defines the
start and end of an address range. The start of the range must be lower
than the end of the range. The start and end of the IP range does not
have to be on the same subnet as the IP address of the interface to
which you are adding the IP pool.
Double NAT: combining IP pools with virtual IPs

When creating a firewall policy, you can use both IP pool and virtual IP for double
IP and/or port translation.
For example, in the following network topology:
• Users in the 10.1.1.0/24 subnet use port 8080 to access server 172.16.1.1.
• The server’s listening port is 80.
• Fixed ports must be used.

01-30007-0203-20090112 359
Double NAT: combining IP pools with virtual IPs Firewall Virtual IP
Figure 214:Double NAT
To allow the local users to access the server, you can use fixed port and IP pool to
allow more than one user connection while using virtual IP to translate the
destination port from 8080 to 80.
To create an IP pool
1 Go to Firewall > Virtual IP > IP Pool.
3 Enter the following information and select OK.
Name pool-1
Interface DMZ
IP Range/Subnet 10.1.3.1-10.1.3.254
To create a Virtual IP with port translation only

3 Enter the following information and select OK.
Name server-1
External Internal
Interface
Type Static NAT
External IP 172.16.1.1
Address/Range Note this address is the same as the server address.
Mapped IP 172.16.1.1.
Address/Range
Port Forwarding Enable
Protocol TCP

360 01-30007-0203-20090112
Firewall Virtual IP Adding NAT firewall policies in transparent mode
External Service 8080

Port
Map to Port 80
To create a firewall policy

Add an internal to dmz firewall policy that uses the virtual IP to translate the
destination port number and the IP pool to translate the source addresses.
Source Interface/Zone internal

Source Address 10.1.1.0/24
Destination Interface/Zone dmz
Destination Address server-1
Schedule always
Service HTTP
Action ACCEPT
4 Select NAT.
5 Select OK.
Adding NAT firewall policies in transparent mode

Similar to operating in NAT/Route mode, when operating a FortiGate unit in
Transparent mode you can add firewall policies and:
• Enable NAT to translate the source addresses of packets as they pass through
the FortiGate unit.
• Add virtual IPs to translate destination addresses of packets as they pass
through the FortiGate unit.
• Add IP pools as required for source address translation
For NAT firewall policies to work in NAT/Route mode you must have two
interfaces on two different networks with two different subnet addresses. Then
you can create firewall policies to translate source or destination addresses for
packets as they are relayed by the FortiGate unit from one interface to the other.
A FortiGate unit operating in Transparent mode normally has only one IP address,
the management IP. To support NAT in Transparent mode you can add a second
management IP. These two management IPs must be on different subnets. When
you add two management IP addresses, all FortiGate unit network interfaces will
respond to connections to both of these IP addresses.
In the example network shown in Figure 215, all of the PCs on the internal
network (subnet address 192.168.1.0/24) are configured with 192.168.1.99 as
their default route. One of the management IPs of the FortiGate unit is set to
192.168.1.99. This configuration results in a typical NAT mode firewall. When a
PC on the internal network attempts to connect to the Internet, the PC's default
route sends packets destined for the Internet to the FortiGate unit internal
interface.

01-30007-0203-20090112 361
Adding NAT firewall policies in transparent mode Firewall Virtual IP
Similarly on the DMZ network (subnet address 10.1.1.0/24) all of the PCs have a
default route of 10.1.1.99.
The example describes adding an internal to wan1 firewall policy to relay these
packets from the internal interface out the wan1 interface to the Internet. Because
the wan1 interface does not have an IP address of its own, you must add an IP
pool to the wan1 interface that translates the source addresses of the outgoing
packets to an IP address on the network connected to the wan1 interface.
The example describes adding an IP pool with a single IP address of 10.1.1.201.
So all packets sent by a PC on the internal network that are accepted by the
internal to wan1 policy leave the wan1 interface with their source address
translated to 10.1.1.201. These packets can now travel across the Internet to their
destination. Reply packets return to the wan1 interface because they have a
destination address of 10.1.1.201. The internal to wan1 NAT policy translates the
destination address of these return packets to the IP address of the originating PC
and sends them out the internal interface to the originating PC.
Use the following steps to configure NAT in Transparent mode
• Adding two management IPs
• Adding an IP pool to the wan1 interface
• Adding an internal to wan1 firewall policy
Figure 215:Example NAT in Transparent mode configuration
Internet
Internal network
Transparent mode 192.168.1.0/24
Management IPs:
Router 10.1.1.99
192.168.1.99
10.1.1.0/24 WAN 1 Internal
DMZ
DMZ network
10.1.1.0/24
To add a source address translation NAT policy in Transparent mode

1 Enter the following command to add two management IPs.
The second management IP is the default gateway for the internal network.
set manageip 10.1.1.99/24 192.168.1.99/24
end

362 01-30007-0203-20090112
Firewall Virtual IP Adding NAT firewall policies in transparent mode
2 Enter the following command to add an IP pool to the wan1 interface:

config firewall ippool
edit nat-out
set interface "wan1"
set startip 10.1.1.201
set endip 10.1.1.201
end
3 Enter the following command to add an internal to wan1 firewall policy with NAT
enabled that also includes an IP pool:
config firewall policy
edit 1
set srcintf "internal"
set dstintf "wan1"
set scraddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "ANY"
set nat enable
set ippool enable
set poolname nat-out
end
Note: You can add the firewall policy from the web-based manager and then use the CLI to
enable NAT and add the IP Pool.

01-30007-0203-20090112 363
Adding NAT firewall policies in transparent mode Firewall Virtual IP

364 01-30007-0203-20090112
Firewall Protection Profile What is a protection profile?
Firewall Protection Profile

Protection profiles contain settings for many application layer and other types of
protection, such as antivirus, web filtering, and logging, that you can apply to a
firewall policy. Protection profiles can also contain settings for protocol-specific
firewall actions, such as rate limiting for voice over IP (VoIP).
If you enable virtual domains (VDOMs) on the FortiGate unit, firewall protection
profiles are configured separately for each virtual domain. For more information,
• What is a protection profile?
• Default protection profiles
• Viewing the protection profile list
• Configuring a protection profile
• Applying a protection profile to a firewall policy
What is a protection profile?

A protection profile is a group of settings that you can apply to one or more firewall
policies.
Because protection profiles can be used by more than one firewall policy, you can
configure one protection profile for the traffic types handled by a set of firewall
policies requiring identical protection levels and types, rather than repeatedly
configuring those same protection profile settings for each individual firewall
policy.
For example, while traffic between trusted and untrusted networks might need
strict protection, traffic between trusted internal addresses might need moderate
protection. To provide the different levels of protection, you might configure two
separate protection profiles: one for traffic between trusted networks, and one for
traffic between trusted and untrusted networks.
Note: If the firewall policy requires authentication, do not select the protection profile in the
firewall policy. The protection profile is specific to the authenticating user group. For details
on configuring the protection profile associated with the user group, see “Configuring a user
group” on page 438.
You can use protection profiles to configure:

• antivirus protection
• web filtering
• FortiGuard Web Filtering
• spam filtering
• IPS
• content archiving

01-30007-0203-20090112 365
Default protection profiles Firewall Protection Profile
• IM filtering and access control

• P2P access and bandwidth control
• logging for traffic which violates the protection profile
• rate limiting for VoIP protocols (SIP and SCCP)
Default protection profiles

FortiGate units have four default protection profiles. You can use these default
protection profiles as bases for creating your own.
Strict Apply maximum protection to HTTP, FTP, IMAP, POP3, and SMTP
traffic. The strict protection profile may not be useful under normal
circumstances, but it is available when maximum protection is required.
Scan Apply virus scanning to HTTP, FTP, IMAP, POP3, and SMTP traffic.
Quarantine is also selected for all content services. On FortiGate models
with a hard drive, if antivirus scanning finds a virus in a file, the file is
quarantined on the FortiGate hard disk. If a FortiAnalyzer unit is
configured, files are quarantined remotely. Quarantine permits system
administrators to inspect, recover, or submit quarantined files to Fortinet
for analysis.
Web Apply virus scanning and web content blocking to HTTP traffic. Add this
protection profile to firewall policies that control HTTP traffic.
Unfiltered Apply no scanning, blocking or IPS. Use the unfiltered content profile if
no content protection for content traffic is required. Add this protection
profile to firewall policies for connections between highly trusted or highly
secure networks where content does not need to be protected.
Note: Content archiving is disabled by default with the unfiltered
protection profile.
Viewing the protection profile list

Both default and customized protection profiles appear in the protection profile list.
To view the protection profile list, go to Firewall > Protection Profile.
Figure 216:Default protection profiles
Delete
Edit
Create New Add a protection profile.

Name The name of the protection profile.
Delete icon Delete a protection profile from the list. The Delete icon appears only if
the protection profile is not currently selected in a firewall policy or user
group.
Edit icon Modify a protection profile.

366 01-30007-0203-20090112
Firewall Protection Profile Configuring a protection profile
Configuring a protection profile

If the default protection profiles do not provide the settings required, you can
create custom protection profiles.
To add a protection profile, go to Firewall > Protection Profile and select Create
New.
Note: If both Virus Scan and File Block are enabled, the FortiGate unit blocks files
matching enabled file patterns before scanning files for viruses.
Figure 217:New Protection Profile
Profile Name Enter a name for the protection profile.

Comments Enter a description of the profile. The maximum length is 63
characters.
AntiVirus See “Anti-Virus options” on page 367.
Web Filtering See “Web Filtering options” on page 369.
FortiGuard Web Filtering See “FortiGuard Web Filtering options” on page 370.
Spam Filtering See “Spam Filtering options” on page 373.
IPS See “IPS options” on page 375.
Content Archive See “Content Archive options” on page 375.
IM & P2P See “IM/P2P options” on page 378.
VoIP See “VoIP options” on page 379.
Logging See “Logging options” on page 380.
Anti-Virus options
You can apply antivirus scanning options through a protection profile.
In general, client comforting provides a visual display of progress for web page
loading or file downloads. Without client comforting, users have no indication that
the download has started until the FortiGate unit has completely buffered and
scanned the download, and they may cancel or repeatedly retry the transfer,
thinking it has failed. The appearance of a client comforting message (for
example, a progress bar) is browser-dependent. In some instances, there will be
no visual client comforting cue.

01-30007-0203-20090112 367
Configuring a protection profile Firewall Protection Profile
For email scanning, the oversize threshold refers to the final size of the email after
encoding by the email client, including attachments. Email clients can use a
variety of encoding types; some result in larger file sizes than the original
attachment. The most common encoding, base64, translates 3 bytes of binary
data into 4 bytes of base64 data. As a result, a file may be blocked or logged as
oversized even if the attachment is several megabytes smaller than the configured
oversize threshold.
To configure antivirus options, go to Firewall > Protection Profile. Select Create
New to add a protection profile, or the Edit icon beside an existing protection
profile. Then select the Expand Arrow beside Anti-Virus, enter the information as
described below, and select OK. For more antivirus configuration options, see
“AntiVirus” on page 447.
Figure 218:Protection Profile Anti-Virus options
Virus Scan Select virus scanning for each protocol (HTTP, FTP, IMAP, POP3,
SMTP, IM). Virus Scan includes grayware, as well as heuristic
scanning. However, by default neither is enabled. To enable
specific grayware, go to AntiVirus > Config > Grayware. To
enable heuristic scanning, see the config antivirus
heuristic command in the FortiGate CLI Reference.
Note: When you enable virus scanning, scanning by splice, also
called streaming mode, is enabled automatically. When scanning
by splice, the FortiGate unit simultaneously scans and streams
traffic to the destination, terminating the stream to the destination
if a virus is detected. For details on configuring splicing, see the
splice option for each protocol in the config firewall
profile command in the FortiGate CLI Reference. For details on
splicing behavior for each protocol, see the Knowledge Center
article FortiGate Proxy Splice and Client Comforting Technical
Note.
Extended AV Select to scan for viruses that have not been recently observed in
Database the wild.
In addition to the FortiGuard Antivirus wild list database, which
contains viruses currently being detected in the wild, some
FortiGate models are also equipped with an extended antivirus
database that contains viruses not recently observed in the wild.
This option appears only on models with more than one partition,
such as the FortiGate-3810A.
File Filter Select to filter files, then under Options, specify a file filter, which
can consist of file name patterns and file types. For more
information, see “File Filter” on page 450.

368 01-30007-0203-20090112
Quarantine Select for each protocol to quarantine suspect files for later
inspection or submission to Fortinet for analysis.
This option appears only if the FortiGate unit has a hard drive or a
configured FortiAnalyzer unit, and will take effect only if you have
first enabled and configured the quarantine. For more information,
see “Quarantine” on page 454.
Pass Fragmented Select to allow fragmented email for mail protocols (IMAP, POP3,
Emails and SMTP). Fragmented email cannot be scanned for viruses.
Comfort Clients Select client comforting for each protocol.
Interval The time in seconds before client comforting starts after the
download has begun, and the time between subsequent intervals.
Amount The number of bytes sent at each interval.
Oversized File/Email Select Block or Pass for files and email messages exceeding
configured thresholds for each protocol.
Threshold If the file is larger than the threshold value in megabytes, the file is
passed or blocked. The maximum threshold for scanning in
memory is 10% of the FortiGate unit’s RAM.
Add signature to Create and enable a signature to append to outgoing email (SMTP
outgoing emails only).
Web Filtering options

Web filtering sorts millions of web pages into a wide range of categories that you
can allow, block or monitor. Content block uses words and patterns to block web
pages containing the words or patterns, URL filtering uses URLs and URL
patterns to exempt or block web pages from specific sources, and FortiGuard web
filter provides many additional categories by which to filter web traffic. In some
instances, users may require access to web sites that are blocked by a policy. An
administrator can give the user the ability to override the block for a specified
period of time. For more information about overrides, see “Web Filter” on
page 479.
Filters defined in the web filtering settings are turned on through a protection
profile. To configure web filtering options, go to Firewall > Protection Profile.
Select Create New to add a protection profile, or the Edit icon beside an existing
protection profile. Then select the Expand Arrow beside Web Filtering, enter the
information as described below, and select OK.
Figure 219:Protection Profile Web Filtering options
Web Content Block Select the checkbox to block HTTP traffic based on the
words or patterns in the content block filter.
Web content block list Select which content block filter will be used with this
protection profile.
Threshold Enter a score threshold.

01-30007-0203-20090112 369
Web Content Exempt Select the check box to enable the override of web content
block based on the content exempt patterns in the content
exempt list.
Web content exempt list Select which content exemptions will be used with this
protection profile.
Web URL Filter Select the check box to block HTTP and HTTPS traffic
based on the URL list.
Web URL filter list Select which web URL filter list will be used with this
protection profile.
ActiveX Filter Select to block ActiveX controls.
Cookie Filter Select to block cookies.
Java Applet Filter Select to block Java applets.
Web Resume Download Select to block downloading parts of a file that have already
Block been downloaded. Enabling this option will prevent the
unintentional download of virus files hidden in fragmented
files. Note that some types of files, such as PDFs, are
fragmented to increase download speed, and that selecting
this option can cause download interruptions with these
types.
Block Invalid URLs Select to block web sites whose SSL certificate’s CN field
does not contain a valid domain name.
FortiGate units always validate the CN field, regardless of
whether this option is enabled. However, if this option is not
selected, the following behavior occurs:
• If the request is made directly to the web server, rather
than a web server proxy, the FortiGate unit queries for
FortiGuard Web Filtering category or class ratings using
the IP address only, not the domain name.
• If the request is to a web server proxy, the real IP
address of the web server is not known. Therefore, rating
queries by either or both the IP address and the domain
name is not reliable. In this case, the FortiGate unit does
not perform FortiGuard Web Filtering.
Blocked pages are replaced with a message indicating that the page is not
accessible according to the Internet usage policy.
If the combined scores of the content block patterns appearing on a web page
exceed the threshold value, the page will be blocked. For details, see “Viewing the
web content block list” on page 483.
For more information on web filter configuration options, see “Web Filter” on
page 479. For details on how web URL filter lists are used with HTTP and HTTPS
URLs, see “URL formats” on page 490.
FortiGuard Web Filtering options

You can enable and apply FortiGuard Web Filtering options by using a protection
profile.
If you have blocked a pattern using the FortiGuard Web Filter, but want certain
users to have access to URLs within the pattern, you can use the override feature
within the FortiGuard Web Filter.
For more category blocking configuration options, see “FortiGuard - Web Filter” on
page 491.

370 01-30007-0203-20090112
To configure FortiGuard Web Filtering options, go to Firewall > Protection

Profile. Select Create New to add a protection profile, or the Edit icon beside an
existing protection profile. Then select the Expand Arrow beside FortiGuard Web
Filtering, enter the information as described below, and select OK.
Figure 220:Protection Profile FortiGuard Web Filtering options
Enable FortiGuard Web Select to enable FortiGuard Web Filtering.

Filtering
Enable FortiGuard Web Select to enable category overrides. For more
Filtering Overrides information, see “Viewing the override list” on page 492
and “Configuring administrative override rules” on
page 493.
Provide details for blocked Display a replacement message for 400 and 500-series
HTTP 4xx and 5xx errors HTTP errors. If the error is allowed through, malicious or
objectionable sites can use these common error pages to
circumvent web filtering.
Rate images by URL (blocked Block images that have been rated by FortiGuard.
images will be replaced with Blocked images are replaced on the originating web
blanks) pages with blanks. Rated image file types include GIF,
JPEG, PNG, BMP, and TIFF.
Allow websites when a rating Allow web pages that return a rating error from the web
error occurs filtering service.

01-30007-0203-20090112 371
Strict Blocking This option is enabled by default. Strict Blocking only has
an effect when either a URL fits into a protection profile
Category and Classification or “Rate URLs by domain
and IP address” is enabled. With “Rate URLs by domain
and IP address” enabled, all URLs have two categories
and up to two classifications (one set for the domain and
one set for the IP address). All URLs belong to at least
one category (Unrated is a category) and may also
belong to a classification.
If you enable Strict Blocking, a site is blocked if it is in at
least one blocked category or classification and only
allowed if all categories or classifications it falls under are
allowed.
If you do not enable Strict Blocking, a site is allowed if it
belongs to at least one allowed category or classification
and only blocked if all categories or classifications it falls
under are allowed.
For example, suppose a protection profile blocks “Search
Engines” but allows “Image Search” and the URL
“images.example.com” falls into the General Interests
Search Engines category and the Image Search
classification.
With Strict Blocking enabled, this URL is blocked
because it belongs to the Search Engines category,
which is blocked.
With Strict Blocking disabled, the URL is allowed because
it is classified as Image Search, which is allowed. It would
only be blocked if both the Search Engines category and
Image Search classification were blocked.
Rate URLs by domain and IP Select to send both the URL and the IP address of the
address requested site for checking, and thus provide additional
security against attempts to bypass the FortiGuard
system.
However, because IP rating is not updated as quickly as
URL rating, some false ratings may occur.
Block HTTP redirects by Enable to block HTTP redirects.
rating Many web sites use HTTP redirects legitimately;
however, in some cases, redirects may be designed
specifically to circumvent web filtering, as the initial web
page could have a different rating than the destination
web page of the redirect.
Category FortiGuard Web Filtering provides many content
categories by which to filter web traffic. Categories reflect
the subject matter of the content.
For each category, select to Allow or Block, and, if the
category is blocked, whether or not to Allow Override to
permit users to override the filter if they successfully
authenticate. You can also select to log each traffic
occurrence of the category.
Classification In addition to content categories, FortiGuard Web
Filtering provides functional classifications that block
whole classes of web sites based upon their functionality,
media type, or source, rather than the web site’s subject
matter.
Using classifications, you can block web sites that host
cached content or that facilitate image, audio, or video
searches, or web sites from spam URLs. Classification is
in addition to, and can be configured separately from, the
category.
For each class, select to Allow or Block, and, if the class
is blocked, whether or not to Allow Override to permit
users to override the filter if they successfully
authenticate. You can also select to log each traffic
occurrence of the class.

372 01-30007-0203-20090112
Spam Filtering options

Several spam filters can be configured in the protection profile. With the IP
address filter, FortiGuard AntiSpam extracts the email server source address and
sends the IP address to a FortiGuard Antispam server to check if this IP address
matches the list of known spammers. If the IP address is found, FortiGuard
Antispam terminates the session. If FortiGuard Antispam does not find a match,
the email server sends the email to the recipient. With the URL filter, FortiGuard
Antispam checks the body of email messages to extract any URL links. These
URL links are sent to a FortiGuard Antispam server to determine if any are listed.
Spam messages often contain URL links to advertisements (also called
spamvertizing). If a URL match is found, FortiGuard Antispam terminates the
session. If FortiGuard Antispam does not find a match, the email server sends the
email to the recipient. The email checksum filter calculates the checksum of an
email message and sends this checksum to the FortiGuard servers to determine if
the checksum is in the blacklist. The FortiGate unit then passes or marks/blocks
the email message according to the server response.
For more information about this service, see “FortiGuard Antispam Service” on
page 242.You can apply spam filtering options through a protection profile.
For more spam filter configuration options, see “Antispam” on page 499. To
configure the FortiGuard Anti-spam service, see “Configuring the FortiGate unit
for FDN and FortiGuard subscription services” on page 243.
Note: Some popular email clients cannot filter messages based on the MIME header. For
these clients, select to tag email message subject lines instead.
Figure 221:Protection Profile Spam Filtering options
FortiGuard AntiSpam Select one or more check boxes to enable protocols (IMAP,
POP3, SMTP), then apply the options that you need:
IP address check Select to enable the FortiGuard AntiSpam filtering IP address
blacklist.
URL check Select to enable the FortiGuard AntiSpam spam filtering URL
blacklist.
E-mail checksum Select to enable the FortiGuard Antispam email message
check checksum blacklist.

01-30007-0203-20090112 373
Spam submission Select to enable all email messages marked as spam to

have a link added to the message body. If an email message
is not spam, simply select the link in the message to inform
FortiGuard about the false positive.
IP address BWL check Black/white list check. Select to check incoming IP
addresses against the configured spam filter IP address list.
IP address BWL check Select which IP address black/white list will be used with this
list protection profile.
HELO DNS lookup Select to enable the look up of the source domain name
(from the SMTP HELO command) in the Domain Name
Server.
E-mail address BWL check Select to enable the checking of incoming email addresses
against the configured spam filter email address list.
E-mail address BWL list Select which email address black/white list will be used with
this protection profile.
Return e-mail DNS check Select to enable checking that the domain specified in the
reply-to or from address has an A or MX record.
Banned word check Select to enable checking source email against the
configured spam filter banned word list.
Banned word list Select which banned word list will be used with this
protection profile.
Threshold If the combined scores of the banned word patterns
appearing in an email message exceed the threshold value,
the message will be processed according to the Spam Action
setting. For details, see “Viewing the antispam banned word
list” on page 503.
Spam Action Select to either tag or discard email that the FortiGate unit
determines to be spam. Tagging affixes custom text to the
subject line or header of email identified as spam.
For SMTP, if you enable virus scanning in the Anti-Virus
options section of the Protection Profile (which is
automatically implemented as a spliced stream), you will only
be able to discard spam email if a virus is detected.
Discarding immediately drops the connection. If virus
scanning is not enabled, you can choose to either tag or
discard SMTP spam.
Tag Location Select to affix the tag to the subject or MIME header of the
email identified as spam.
If you select to affix the tag to the subject line, the FortiGate
unit will convert the entire subject line, including tag, to
UTF-8 by default. This improves display for some email
clients that cannot properly display subject lines that use
more than one encoding. For details on preventing
conversion of subject line to UTF-8, see the “System
Settings” chapter of the FortiGate CLI Reference.
To affix the tag to the MIME header, you must enable
spamhdrcheck in the CLI for each protocol (IMAP, SMTP,
and POP3). For more information see “profile” in the

374 01-30007-0203-20090112
Tag Format Enter a word or phrase (tag) to affix to email identified as

spam.
When typing a tag, use the same language as the FortiGate
unit’s current administrator language setting. Tag text using
other encodings may not be accepted. For example, when
entering a spam tag that uses Japanese characters, first
verify that the administrator language setting is Japanese;
the FortiGate unit will not accept a spam tag written in
Japanese characters while the administrator language
setting is English. For details on changing the language
setting, see “Settings” on page 215.
Tags must not exceed 64 bytes. The number of characters
constituting 64 bytes of data varies by text encoding, which
may vary by the FortiGate administrator language setting.
IPS options
You can apply IPS sensor options through a protection profile.
To configure IPS options, go to Firewall > Protection Profile. Select Create New
to add a protection profile, or the Edit icon beside an existing protection profile.
Then select the Expand Arrow beside IPS, enter the information as described
below, and select OK.
For more information on IPS, see “Intrusion Protection” on page 463.
Figure 222:Protection profile IPS options
IPS Select to enable and use the specified IPS sensor.

You cannot select denial of service (DoS) sensors through this
option. For information on configuring DoS sensors, see “DoS
sensors” on page 475.
Content Archive options

You can apply content archive options through a protection profile.
Content archives consist of either logged metadata (summary), or logged
metadata with a copy of the associated file or message (full).
that provides logging and reporting solutions for all FortiGate units as well as
providing remote management services. The FortiGuard Analysis and
Management Service is available on all FortiGate units running FortiOS 3.0 MR6
and higher. The FortiGuard Analysis and Management Service Administration
Guide contains detailed information about registering and remotely managing
your FortiGate unit, as well as enabling and configuring logging and reporting.
The level (full or summary) of content archiving and even the availability of
content archiving vary by your selected protocols. For more information, see
“Content archiving requirements and behavior” on page 377.
Content archive summaries may be displayed in multiple locations, such as
Log&Report, in the Statistics section of the dashboard, and in a FortiAnalyzer unit
or FortiGuard Analysis and Management Service. Locations vary by the options
you select in the protection profile, and your configuration of a FortiAnalyzer unit
or FortiGuard Analysis and Management Service.

01-30007-0203-20090112 375
The FortiGate unit only allows one sixteenth of its memory for transferring content
archive files. For example, for FortiGate units with 128RAM, only 8MB of memory
is used when transferring content archive files. It is recommended not to enable
full content archiving if antivirus scanning is also configured because of these
memory constraints.
You can store content archives locally, if your FortiGate unit has a hard drive, or
remotely, on a FortiAnalyzer unit or FortiGuard Analysis and Management
Service, provided that the FortiAnalyzer unit or FortiGuard Analysis and
Management Service is first configured. For instructions on configuring and
viewing remotely stored content archives, see “Logging to a FortiAnalyzer unit” on
page 529 and “Content Archive” on page 545.
To configure Content Archive options, go to Firewall > Protection Profile. Select
Create New to add a protection profile, or the Edit icon beside an existing
protection profile. Then select the Expand Arrow beside Content Archive, enter
the information as described below, and select OK.
Figure 223:Protection Profile Content Archive options
Email Protocols
IM Protocols
Display content meta- For each protocol, select whether or not to display the
information on the system content archive summary in the Statistics section of the
dashboard (Email) dashboard.
For details on the dashboard display, see “Statistics” on
page 75.
Archive to For each protocol, select to send a full or partial content

FortiAnalyzer/FortiGuard archive to the FortiAnalyzer unit or FortiGuard Analysis and
Management Service, or to not send content archives.
In some cases, the FortiGate unit may not archive content,
or may not make a full content archive, regardless of your
selected option. This behavior varies by prerequisites for
each protocol. For more information, see “Content archiving
requirements and behavior” on page 377.
You can select this option only if a FortiAnalyzer unit or
FortiGuard Analysis and Management Service is
configured. For more information, see “Logging to a
None Do not send content archives.
Summary Content archive metadata only. Content metadata includes
information such as date and time, source and destination,
request and response size, and scan result.
Full Content archive both metadata and copies of files or
messages.

376 01-30007-0203-20090112
Archive SPAMed emails to For each email protocol, select to include spam email
FortiAnalyzer/FortiGuard messages in content archives sent to the FortiAnalyzer unit
or FortiGuard Analysis and Management Service.
By default, the FortiGate unit sends content archives of
non-spam email messages only, omitting spam.
Display content meta- For each protocol, select whether or not to display the
information on the system content archive summary in the Statistics section of the
dashboard (IM protocols) dashboard. Note that you need to enable inspection of the
IM protocols by selecting them in the IM/P2P options before
selecting them in the content archive options.
Archive to For each protocol, select to send a full or partial content
FortiAnalyzer/FortiGuard archive to the FortiAnalyzer unit or FortiGuard Analysis and
Management Service, or to not send content archives.
In some cases, the FortiGate unit may not archive content,
or may not make a full content archive, regardless of your
selected option. This behavior varies by prerequisites for
each protocol. For more information, see “Content archiving
requirements and behavior” on page 377.
You can select this option only if a FortiAnalyzer unit or
FortiGuard Analysis and Management Service is
configured. For more information, see “Logging to a
None Do not send content archives.
Summary Content archive metadata only. Content metadata includes
information such as date and time, source and destination,
request and response size, and scan result.
Full Content archive both metadata and copies of files or
messages.
Archive IM to For each IM protocol, select to include IM messages in
FortiAnalyzer/FortiGuard content archives sent to the FortiAnalyzer unit or
Content archiving requirements and behavior

Steps required to implement content archiving, whether summary (summary log
only) or full (summary log plus a copy of the file or message) content archiving,
vary by protocol.
In all cases (except spam email if you have enabled Archive SPAMed emails to
FortiAnalyzer/FortiGuard), FortiGate units form content archives only if two
conditions are in effect: You have enabled, elsewhere in the FortiGate unit, the
specific traffic that you want to content archive, and you have enabled content
archiving in the firewall protection profile. If you have selected content archiving
but neither summary nor full content archives are being formed, verify that the
traffic is not being blocked due to configurations in other areas, such as web
filtering and antispam banned words or blocked IM/P2P user names. For details
on configuring protocol-specific blocking, see the chapters specific to those areas
of the configuration, such as “Configuring a policy for unknown IM users” on
page 523.
Most email protocols require only that you allow the traffic and select either
Summary or Full content archiving. Exceptions include:
• HTTPS: Full content archives cannot be formed. Because HTTPS content is
encrypted, archived copies of files transferred by HTTPS would not be
viewable except by the requesting client.

01-30007-0203-20090112 377
• Protocols with an Oversize File / Message action and Threshold in the

Antivirus options section of the protection profile. If you select Pass, the
FortiGate proxy will not scan the content of oversized files, and therefore will
not form a copy of the file or message. In that case, even if you have selected
Full content archiving, the FortiGate unit can only form a summary content
archive.
IM/P2P options
You can apply IM and P2P options through a protection profile.
Any changes to IM protection profile options made while IM users are logged in
will take effect only upon their next login. For example, you cannot use Block
Login to disconnect currently logged-in users.
For more IM configuration options, see “IM, P2P & VoIP” on page 515.
To configure IM/P2P options, go to Firewall > Protection Profile. Select Create
profile. Then select the Expand Arrow beside IM / P2P, enter the information as
described below, and select OK.
Figure 224:Protection Profile IM/P2P options
Block Login Select to prevent instant message users from logging in to

AIM, ICQ, MSN, Yahoo, and Session Initiation Protocol for
Instant Messaging and Presence Leveraging Extensions
(SIMPLE) services.
Block File Transfers Select to block file transfers for AIM, ICQ, MSN, and Yahoo
protocols.
Block Audio Select to block audio for AIM, ICQ, MSN, and Yahoo
protocols.
Inspect Non-standard Port Enable inspection of non-standard ports for IM traffic.
The FortiGate unit will perform content inspection of the
selected protocol on any port that is not used by a FortiGate
proxy, such as protocols being scanned for viruses or
filtered URLs. Exceptions to this rule include the AIM
protocol, which can be inspected on any port number,
regardless of proxy use.
Action Pass, block, or rate limit P2P transfers for BitTorrent,
eDonkey, Gnutella, Kazaa, and WinNY protocols. Skype
transfers can be passed or blocked, but not rate limited.
Limit (KBytes/s) If Action is set to Rate Limit, specify the bandwidth limit for
BitTorrent, eDonkey, Gnutella, Kazaa, and WinNY
protocols.
The bandwidth limit can be applied separately for each
firewall policy that uses the protection profile, or shared by
all firewall policies that use the protection profile. By default,
the limit is applied separately to each firewall policy. For
information on configuring per policy or per protection
profile P2P bandwidth limiting, see the imp2p chapter in the
For details on P2P bandwidth usage statistics, see
“Statistics” on page 518.

378 01-30007-0203-20090112
VoIP options
You can apply VoIP options through a protection profile. FortiGate units support
rate limiting for the following types of VoIP traffic:
• Session Initiation Protocol (SIP)
• Skinny Call Control Protocol (SCCP)
• Session Initiation Protocol for Instant Messaging and Presence Leveraging
Extensions (SIMPLE)
Rate limiting of these VoIP protocols can be used to protect the FortiGate unit and
your network from SIP and SCCP Denial of Service (DoS) attacks. Rate limiting
protects against SIP DoS attacks by limiting the number of SIP register and invite
requests that the FortiGate unit receives per second. Rate limiting protects
against SCCP DoS attacks by limiting the number of SCCP call setup messages
that the FortiGate unit receives per minute.
When VoIP rate limiting is enabled, if the FortiGate unit receives more messages
per second (or minute) than the configured rate, the extra messages are dropped.
If you are experiencing denial of service attacks from traffic using these VoIP
protocols you can enable VoIP rate limiting and limit the rates for your network.
Limits the rates depending on the amount of SIP and SCCP traffic that you expect
the FortiGate unit to be handling. You can adjust the settings if some calls are lost
or if the amount of SIP or SCCP traffic is affecting FortiGate unit performance.
From the CLI you can configure additional SIP, SCCP, as well as SIMPLE
extensions. For more information, see the description of the config sip,
config sccp, and config simple subcommands of the firewall profile
command in the FortiGate CLI Reference. You can also block SIMPLE sessions
by enabling block login for the SIMPLE IM/P2P protection profile option. See
“IM/P2P options” on page 378.
For more information about FortiGate SIP support see “SIP support” on page 383.
To configure VoIP options, go to Firewall > Protection Profile. Select Create
profile. Then select the Expand Arrow beside VoIP, enter the information as
Figure 225:Protection Profile VoIP options
SIP Select to rate limit SIP traffic. Use SIP rate limiting to
prevent SIP DoS attacks by limiting the number of SIP
events accepted by the FortiGate unit.
SCCP Select to enable rate limiting for SCCP traffic.
Limit REGISTER Request Enter a rate limit for SIP REGISTER requests (per second,
(SIP only) per policy). If this option is set to zero (0), requests are not
limited.

01-30007-0203-20090112 379
Limit INVITE Request (SIP Enter a rate limit for SIP INVITE requests (per second, per
only) policy). If this option is set to zero (0), requests are not
limited.
Limit Call Setup (SCCP Enter a rate limit to SCCP call setup (calls per minute, per
only) client) between call clients and the call manager. If this
option is set to zero (0), setups are not limited.
Logging options
You can enable Logging options in a protection profile to write event log messages
when the options that you have enabled in this protection profile perform an
action. For example, if you enable Antivirus protection you could also enable the
Anti-virus > Viruses protection profile logging options to write an event log
message every time a virus is detected by this protection profile.
For more information about enabling and configuring event logs, see “Event log”
on page 536.
To configure Logging options, go to Firewall > Protection Profile. Select Create
profile. Then select the Expand Arrow beside Logging, enter the information as
Figure 226:Protection Profile Logging options
Antivirus Viruses Select to log detected viruses.

Blocked Files Select to log blocked files.
Oversized Files / Select to log oversize files and email
E-mails messages.
Web Filtering Content Block Select to log content blocking events.
URL Filter Select to log blocked and exempted URLs.
ActiveX Filter Select to log blocked Active X plugins.
Cookie Filter Select to log blocked cookies.
Java Applet Filter Select to log blocked Java applets.

380 01-30007-0203-20090112
Firewall Protection Profile Applying a protection profile to a firewall policy
FortiGuard Web Rating Errors Select to log rating errors.

Filtering (HTTP only)
Spam Filtering Log Spam Select to log detected spam.
IPS Log Intrusions Select to log IPS signature and anomaly
events.
IM and P2P Log IM Activity Select to log IM events.
Log P2P Activity Select to log P2P events.
VoIP Log VoIP Activity Select to log VoIP events.
Applying a protection profile to a firewall policy

Protection profiles are used when specified in one or more firewall policies whose
Action is set to ACCEPT, IPSEC, or SSL VPN.
For example, if you create a protection profile containing SMTP antivirus settings
that you want to apply to all incoming SMTP connections, you might select that
protection profile in all external-to-internal firewall policies whose service group
contain the SMTP service.
In order to enable IPv6 support, go to System > Admin > Settings and select IPv6
Support on GUI. Once IPv6 support is enabled, IPv6 firewall policies can be
configured and protection profiles applied to the firewall policies.
Protection profiles can contain settings relevant to many different services. Each
firewall policy uses the subset of the protection profile settings which apply to its
specified Service. In this way, you might define one protection profile that can be
used by many firewall policies, each policy using a different or overlapping subset
of the protection profile.
To apply a protection profile to a firewall policy

1 Go to Firewall > Policy. Alternatively, go to Firewall > IPv6 Policy if you require
a protection profile for a firewall to support IPv6.
If virtual domains are enabled on the FortiGate unit, protection profiles are applied
separately in firewall policies for each virtual domain (VDOM). To access firewall
policies, first select a virtual domain from the main menu.
2 Select Create New to add a policy, or select Edit for the policy to which you want
to apply the protection profile.
For example, if you want to apply a protection profile containing HTTP antivirus
scanning, select policies whose Service is a service or service group containing
HTTP.
3 Select the Protection Profile that you want to apply.
The firewall policy will use settings from the protection profile that apply to its
Service.
4 If you are creating a new firewall policy, configure other required policy options.
For more information, see “Configuring firewall policies” on page 297.
5 Select OK.

01-30007-0203-20090112 381
Applying a protection profile to a firewall policy Firewall Protection Profile

382 01-30007-0203-20090112
SIP support VoIP and SIP
SIP support
The Session Initiation Protocol (SIP) is a signaling protocol used for establishing
and conducting multiuser calls over TCP/IP networks using any media. Due to the
complexity of the call setup, not every firewall can handle SIP calls correctly, even
if the firewall is stateful. The FortiGate unit SIP pre-defined service tracks and
scans SIP calls. The FortiGate unit can make all necessary adjustments, to both
the firewall state and call data, to ensure a seamless call is established through
the FortiGate unit regardless of its operation mode, NAT, route, or transparent.
You can use protection profiles to control the SIP protocol and SIP call activity.
A statistical summary of SIP protocol activity is also available and makes
managing SIP use easy.
This section includes some high-level information about VoIP and SIP. It also
describes how FortiOS SIP support works and how to configure the key SIP
features. For more configuration information, see FortiGate CLI Reference.
The FortiGate unit supports the following SIP features:
• Stateful SIP tracking
• RTP Pinholing
• Request control
• Rate limiting
• Events logging
• Communication archiving
• NAT IP preservation
• Client connection control
• Register response acceptance
• Application Layer Gateway (ALG) control
Note: Some of the features described in this chapter are available for FortiOS Carrier only.
VoIP and SIP

SIP is an IETF protocol for establishing VoIP connections. Many VoIP networks
choose SIP to handle multimedia sessions between endpoints. This lightweight,
text-based signaling protocol is transported over either Transmission Control
Protocol (TCP) or User Datagram Protocol (UDP). SIP uses invitations to create
Session Description Protocol (SDP) messages that allow participants to agree on
a set of compatible media types.
SIP applications are based on client-server structure and support user mobility
with two operating modes: proxy and redirect.
In proxy mode (shown in Figure 227), SIP clients send requests to the proxy
server. The proxy server either handles the requests or forwards them to other
SIP servers. Proxy servers can insulate and hide SIP users by proxying the
signaling messages. To the other users on the VoIP network, the signaling
invitations look as if they come from the SIP proxy server.

01-30007-0203-20090112 383
SIP support
Figure 227:SIP in proxy mode

SIP Proxy Server
2. Client A dials Client B 3. Proxy server looks up phone number
and a request is sent to the SIP proxy server or URL of destination client (Client B) and sends
invite to Client B
IP Network 4. Client B is
notified of incoming
RTP Session
call by proxy server
– phone rings
SIP Client A 5. RTP session opens when SIP Client B

(a@example.com) Client B answers (b@example.com)
1. SIP clients register with SIP server
When the SIP server operates in redirect mode (shown in Figure 228), the SIP
client sends its signaling request to a SIP server, which then looks up the
destination address. The SIP server returns the destination address to the
originator of the call, who uses it to signal the destination SIP client.
Figure 228:SIP in redirect mode

SIP Redirect Server
2. Client A dials Client B and 3. Redirect server looks up phone number
request is sent to SIP redirect server or URL of destination client (Client B) and sends
address back to the caller (Client A)
4. Client A sends invitation

to Client B
IP Network 5. Client B is
notified of incoming
RTP Session call by redirect server
– phone rings
SIP Client A 6. RTP session opens when SIP Client B

(a@example.com) Client B answers (b@example.com)
1. SIP clients register with SIP server
FortiOS and VoIP security

Like data networks, VoIP networks are vulnerable to many of the same security
risks, including denial of service (DoS) attacks, service theft, tampering, and fraud.
Many conventional firewalls cannot protect VoIP networks from attacks because
VoIP is implemented at both the signaling and media layers. VoIP calls cannot go
through these firewalls unless a range of ports are opened – which exposes the
network for unauthorized access.

384 01-30007-0203-20090112
SIP support FortiOS and VoIP security
The FortiGate unit can effectively secure VoIP solutions since it supports VoIP
protocols such as SIP, MGCP, and H.323, and associates state at the signaling
layer with packet flows at the media layer. Using SIP ALG controls, the FortiGate
unit understands the VoIP signaling protocols used in the network and can
dynamically open and close ports (pinholes) for each specific VoIP call to maintain
security.
The FortiGate Intrusion-prevention system (IPS) provides another strategic line of
defense, particularly against VoIP network predators. With its deep-packet
inspection capabilities, the FortiGate IPS can provide continuous surveillance
across multiple network sectors simultaneously, recognizing network traffic
expected within each and alerting network managers to malicious packets and
other protocol anomalies.
SIP NAT
The FortiGate unit supports network address translation (NAT) of SIP because the
FortiGate ALG can modify the SIP headers correctly.
Because of its complexity, this section uses scenarios to explain the FortiGate SIP
NAT support.
Source NAT (SIP and RTP)

In the source NAT scenario, a SIP phone connects to the Internet through a
FortiGate unit with PPPoE. The FortiGate ALG translates all private IPs in the SIP
contact header into public IPs.
You need to configure an internal to external UDP firewall policy with NAT
checked and a SIP-enabled protection profile. For more information about firewall
policies, see “Firewall Policy” on page 293.
Figure 229:SIP source NAT

217.10.79.9 217.10.69.11
SIP Server RTP Server
SIP service provider has a SIP server

and a separate RTP server
217.233.122.132
Internet
10.72.0.57
Destination NAT (SIP and RTP)

In the destination NAT scenario, a SIP phone can connect to a local IP using a
FortiOS VIP. The FortiGate unit translates the SIP contact header to the IP of the
real SIP server located outside.

01-30007-0203-20090112 385
SIP support
Figure 230:SIP destination NAT

217.10.79.9 217.10.69.11
SIP Server RTP Server
SIP service provider has a SIP server

and a separate RTP server
10.72.0.60 217.233.122.132
Internet
10.72.0.57
In this scenario, the SIP phone connects to a VIP (10.72.0.60). The FortiGate SIP
ALG translates the SIP contact header to 217.10.79.9. The FortiGate ALG will
open the RTP pinholes and manage NAT.
The FortiGate unit also supports a variation of this scenario - the RTP server hides
its real address.
Figure 231:SIP destination NAT-RTP server hidden

219.29.81.21
192.168.200.99
RTP Server
10.0.0.60
217.233.90.60
Internet
SIP Server
In this scenario, a SIP phone connects to the Internet. The VoIP service provider
only publishes a single public IP (a VIP). The SIP phone would connect to the
FortiGate unit (217.233.90.60) and the FortiGate unit would translate the SIP
contact header to the SIP server (10.0.0.60). The SIP server would change the
SIP/SDP connection information (which tells the SIP phone which RTP IP it
should contact) also to 217.233.90.60.
Source NAT with IP pool

You can choose NAT with the Dynamic IP Pool option when configuring a firewall
policy if the source IP of the SIP packets is different from the interface IP. The
FortiGate ALG understands this configuration and translates the SIP header
accordingly.

386 01-30007-0203-20090112
SIP support FortiOS and VoIP security
This configuration also applies to destination NAT.
Different source and destination NAT for SIP and RTP

This is a more complex scenario that a SIP service provider may use. It can also
be deployed in large scale SIP environments where RTP has to be processed by
the FortiGate unit and the RTP server IP has to be translated differently than the
SIP server IP.
Figure 232:Different source and destination NAT for SIP and RTP
RTP Servers
192.168.0.21 - 192.168.0.23 219.29.81.10 219.29.81.20
RTP Server
10.0.0.60
RTP-1: 217.233.90.65
RTP-2: 217.233.90.70
Internet
SIP: 217.233.90.60
SIP Server
In this scenario, assuming there is a SIP server and a separate media gateway.
The SIP server is configured in such a way that the SIP phone (219.29.81.20) will
connect to 217.233.90.60. The media gateway (RTP server: 219.29.81.10) will
connect to 217.233.90.65.
What happens is as follows:
1 The SIP phone connects to the SIP VIP. The FortiGate ALG translates the SIP
contact header to the SIP server: 219.29.81.20 > 217.233.90.60 (> 10.0.0.60).
2 The SIP server agrees to carry out RTP to 217.233.90.65.
3 The FortiGate ALG opens pinholes, assuming that it knows the ports to be
opened.
You need to create a SIP triggering firewall policy (also called a ‘dummy’ policy)
for RTP so that the FortiGate ALG knows the ports to be opened. This requires
that RTP VIPs must be created, and firewall policies need to be created using
those VIPs.
4 RTP is sent to the RTP-VIP (217.233.90.65.) The FortiGate ALG translates the
SIP contact header to 192.168.0.21.

01-30007-0203-20090112 387
SIP support
How SIP support works

The FortiGate unit uses firewall policies to protect communications between
servers and VoIP end devices. These policies restrict VoIP communication based
on authorized end devices or traffic sourced or destined for a particular IP address
or interface. The FortiGate unit segments the VoIP network, separating the voice
traffic from other traffic to ensure appropriate priority and policies are applied.
The workflow of the FortiOS SIP support is as following:
1 Create a firewall protection profile that enables SIP (see “Enabling SIP support
and setting rate limiting” on page 388).
Once the profile is included in a policy, the ALG will parse the SIP traffic and open
the RTP ports for each specific VoIP call.
When creating a protection profile, you configure SIP features using the web-
based manager and CLI. You then apply the profile to a firewall policy. You can
apply a profile to multiple policies.
2 Create a firewall policy that allows SIP and includes a SIP-enabled protection
profile. Specifically, select the “SIP” or “Any” pre-defined service for the policy.
When the FortiGate unit receives a SIP packet, it checks the packet against the
firewall policies. If the packet matches a policy, the FortiGate firewall inspects and
processes the packet according to the SIP profile applied to the policy.
For more information about firewall policies, see “Firewall Policy” on page 293.
3 Configure advanced SIP features as required (see “Configuring SIP” on
page 388).
Configuring SIP
You configure most SIP features through the CLI. You can also enable SIP
support, set two rate limits, enable SIP logging, and view SIP statistics using the
web-based manager.
Enabling SIP support and setting rate limiting

You need to enable SIP in the protection profile to configure other SIP settings
both through the CLI and the web-based manager.
For more information about rate limiting, see “VoIP options” on page 379.
To Enable SIP and set rate limiting

1 Go to Firewall > Protection Profile.
2 If you want to Enable SIP for an existing profile, select the Edit icon. Otherwise,
select Create New.
3 Expand VoIP.
Figure 233:Enabling SIP and setting rate limit

388 01-30007-0203-20090112
SIP support Configuring SIP
SIP Select to enable SIP support and set rate limiting for SIP and SIMPLE
traffic.
Rate limit for SIP and SIMPLE traffic is useful to protect a SIP server
within a company. Most SIP servers do not have integrated controls and
it is very easy to flood the servers with INVITES or REGISTER requests
to exhaust their resources.
Limit REGISTER Enter a rate limit for SIP REGISTER requests (per second, per policy).
Request If this option is set to zero (0), requests are not limited.
Limit INVITE Enter a rate limit for SIP INVITE requests (per second, per policy). If this
Request option is set to zero (0), requests are not limited.
In CLI, you can enable rate limiting for a more extensive range of SIP requests,
including ACK, INFO, NOTIFY, OPTIONS, PRACK, REFER, SUBSCRIBE, and
UPDATE. For more information, see FortiGate CLI Reference.
4 Select OK.
Enabling SIP logging

You can log SIP events. For more information about enabling and configuring
logging, see “Log&Report” on page 525.
Go to Firewall > Protection Profile. Open an existing profile or select Create
New to create a new profile. Expand Logging.
Figure 234:Logging SIP events
Log VoIP Select to log VoIP events.

Activity
Viewing SIP statistics

You can view the VoIP statistics to gain insight into how the protocol is being used
within the network.
For more information, see “Statistics” on page 518.
Enabling advanced SIP features in a protection profile

You can configure advanced SIP features for a protection profile.
For more information, see FortiGate CLI Reference.
Turning on SIP tracking

The FortiGate SIP ALG (Application Level Gateway) tracks the SIP session over
its life span. A SIP session (or SIP dialog) is normally established after the SIP
INVITE procedure. The ALG then tracks this call as a SIP session. A session can
end by regular BYE procedure, such as callers hanging up the phone, or by an
unexpected signalling or transport error.
With FortiOS, you can continue tracking a SIP session for a specified period of
time even when RTP (Real-time Transport Protocol) is lost.
In CLI, type the following commands:
config firewall profile

01-30007-0203-20090112 389
SIP support
edit <profile_name>
config sip
set status enable
set call-keepalive <integer>
end
end
Managing RTP pinholing

Once you create a firewall policy that allows SIP, the FortiGate ALG will
automatically open the respective RTP ports as long as the SIP session is alive.
You can also manually close RTP ports. This may be useful in cases where the
FortiGate unit only acts as a signalling firewall while RTP is bypassed. Therefore,
no pinholes need to be created.
edit <profile_name>
config sip
set status enable
set rtp disable
end
end
Blocking SIP requests

Since SIP requests can be transmitted via UDP, broadcast attacks are possible.
To prevent your site from being used as an intermediary in an attack, you can
block various SIP requests including ACK, INVITE, INFO, PRACK, and so on
directed to broadcast addresses at your router.
For example, you can type the following commands to block INVITE requests:
edit <profile_name>
config sip
set status enable
set block-invite enable
end
end
Archiving SIP communication

You can content archive SIP call metadata. Depending on your log configuration,
you can view the archived information. For more information, see “Log&Report”
on page 525.
edit <profile_name>
config sip
set status enable
set archive-summary enable
end
end

390 01-30007-0203-20090112
SIP support Configuring SIP
Preserving NAT IP
In NAT operation mode, you can preserve the original source IP address in the
SDP i line. This allows the SIP server to parse this IP for billing purposes.
edit <profile_name>
config sip
set status enable
set nat-trace enable
end
end
In addition, you can overwrite or append the SDP i line:
edit <profile_name>
config sip
set status enable
set preserve-override {enable | disable}
end
end
where selecting enable removes the original source IP address from the SDP i
line and disable appends the address.
Controlling SIP client connection

You can control the SIP client to only connect to the registrar itself. This can avoid
VoIP spoofing.
edit <profile_name>
config sip
set status enable
set strict-register enable
end
end

01-30007-0203-20090112 391
SIP support
Accepting SIP register response

Enable reg-diff-port to accept a SIP register response from a SIP server
even if the source port of the register response is different from the destination
port of the register request.
Most SIP servers use 5060 as the source port in the SIP register response. Some
SIP servers; however, may use a different source port. If your SIP server uses a
different source port, you can enable reg-diff-port and the FortiGate SIP
ALG will create a temporary pinhole when receiving a register request from a SIP
client. As a result, the FortiGate unit will accept a register response with any
source port number from the SIP server.
edit <name>
config sip
set reg-diff-port enable
end
end
Controlling the SIP ALG

Enable contact-fixup so that the FortiGate ALG performs normal SIP NAT
translation to SIP contact headers as SIP sessions pass through the FortiGate
unit.
Disable contact-fixup if you do not want the FortiGate ALG to perform normal
SIP NAT translation of the SIP contact header if a Record-Route header is also
available. If contact-fixup is disabled, the FortiGate ALG does the following with
contact headers:
• For Contact in Requests, if a Record-Route header is present and the request
comes from the external network, the SIP Contact header is not translated.
• For Contact in Responses, if a Record-Route header is present and the
response comes from the external network, the SIP Contact header is not
translated.
If contact-fixup is disabled, the FortiGate ALG must be able to identify the
external network. To identify the external network, you must use the config
system interface command to set the external keyword to enable for the
interface that is connected to the external network.
edit <profile_name>
config sip
set contact-fixup {enable | disable}
end
end

392 01-30007-0203-20090112
VPN IPSEC Overview of IPSec VPN configuration
VPN IPSEC
This section provides information about Internet Protocol Security (IPSec) VPN
configuration options available through the web-based manager. FortiGate units
support both policy-based (tunnel-mode) and route-based (interface mode) VPNs.
Note: For information about how to configure an IPSec VPN, see the FortiGate IPSec VPN
User Guide.
If you enable virtual domains (VDOMs) on the FortiGate unit, VPN IPSec is
• Overview of IPSec VPN configuration
• Policy-based versus route-based VPNs
• Auto Key
• Manual Key
• Internet browsing configuration
• Concentrator
• Monitor
Overview of IPSec VPN configuration

FortiGate units implement the Encapsulated Security Payload (ESP) protocol. The
encrypted packets look like ordinary packets that can be routed through any IP
network. Internet Key Exchange (IKE) is performed automatically based on pre-
shared keys or X.509 digital certificates. As an option, you can specify manual
keys. Interface mode, supported in NAT/Route mode only, creates a virtual
interface for the local end of a VPN tunnel.
Use the following configuration procedures for all IPSec VPNs:
1 Define the phase 1 parameters that the FortiGate unit needs to authenticate
remote peers or clients and establish a secure a connection. See “Creating a new
phase 1 configuration” on page 396.
2 Define the phase 2 parameters that the FortiGate unit needs to create a VPN
tunnel with a remote peer or dialup client. See “Creating a new phase 2
Note: You must use steps 1 and 2 if you want the FortiGate unit to generate unique IPSec
encryption and authentication keys automatically. If a remote VPN peer or client requires a
specific IPSec encryption or authentication key, you must configure the FortiGate unit to use
manual keys instead. For more information, see “Manual Key” on page 404.

01-30007-0203-20090112 393
Policy-based versus route-based VPNs VPN IPSEC
3 Create a firewall policy to permit communication between your private network

and the VPN. For a policy-based VPN, the firewall policy action is IPSEC. For an
interface-based VPN, the firewall policy action is ACCEPT. See “Configuring
firewall policies” on page 297.
For more information about configuring IPSec VPNs, see the FortiGate IPSec
VPN User Guide.
Policy-based versus route-based VPNs

FortiGate units support both policy-based and route-based VPNs. Generally, you
can configure route-based VPNs more easily than policy-based VPNs. However,
the two types have different requirements that limit where you can use them, as
shown in Table 38.
Table 38: Comparison of policy-based and route-based VPNs
Policy-based Route-based
Available in NAT/Route or Transparent Available only in NAT/Route mode
mode
Requires a firewall policy with IPSEC Requires only a simple firewall policy with
action that specifies the VPN tunnel. One ACCEPT action. A separate policy is required
policy controls connections in both for connections in each direction.
directions.
Supports DHCP over IPSec Does not support DHCP over IPSec
You create a policy-based VPN by defining an IPSEC firewall policy between two
network interfaces and associating it with the VPN tunnel (phase 1 or manual key)
configuration. You need only one firewall policy, even if either end of the VPN can
initiate a connection.
You create a route-based VPN by enabling IPSec interface mode when you create
the VPN phase 1 or manual key configuration. This creates a virtual IPSec
interface that is bound to the local interface you selected. You then define an
ACCEPT firewall policy to permit traffic to flow between the virtual IPSec interface
and another network interface. If either end of the VPN can initiate the connection,
you need two firewall policies, one for each direction.
Virtual IPSec interface bindings are shown on the network interfaces page. (Go to
System > Network > Interface.) The names of all tunnels bound to physical,
aggregate, VLAN, inter-VDOM link or wireless interfaces are displayed under their
associated interface names in the Name column. For more information, see
“Interfaces” on page 107. As with other interfaces, you can include a virtual IPSec
interface in a zone.
Hub-and-spoke configurations
To function as the hub of a hub-and-spoke VPN, the FortiGate unit provides a
concentrator function. This is available only for policy-based VPNs, but you can
create the equivalent function for a route-based VPN in any of the following ways:
• Define a firewall policy between each pair of IPSec interfaces that you want to
concentrate. This can be time-consuming to maintain if you have many site-to-
site connections, since the number of policies required increases rapidly as the
number of spokes increases.

394 01-30007-0203-20090112
VPN IPSEC Auto Key
• Put all the IPSec interfaces into a zone and then define a single zone-to-zone
policy.
• Put all the IPSec interfaces in a zone and enable intra-zone traffic. There must
be more than one IPSec interface in the zone.
For more information and an example, see the FortiGate IPSec VPN User Guide.
Redundant configurations
Route-based VPNs help to simplify the implementation of VPN tunnel
redundancy. You can configure several routes for the same IP traffic with different
route metrics. You can also configure the exchange of dynamic (RIP, OSPF, or
BGP) routing information through VPN tunnels. If the primary VPN connection
fails or the priority of a route changes through dynamic routing, an alternative
route will be selected to forward traffic through the redundant connection.
A simple way to provide failover redundancy is to create a backup IPSec
interface. You can do this in the CLI. For more information, including an example
configuration, see the monitor-phase1 keyword for the ipsec vpn phase1-
interface command in the FortiGate CLI Reference.
Routing
Optionally, through the CLI, you can define a specific default route for a virtual
IPSec interface. For more information, see the default-gw keyword for the
vpn ipsec phase1-interface command in the FortiGate CLI Reference.
Auto Key
You can configure two VPN peers (or a FortiGate dialup server and a VPN client)
to generate unique Internet Key Exchange (IKE) keys automatically during the
IPSec phase 1 and phase 2 exchanges.
When you define phase 2 parameters, you can choose any set of phase 1
parameters to set up a secure connection for the tunnel and authenticate the
remote peer.
Auto Key configuration applies to both tunnel-mode and interface-mode VPNs.
To configure an Auto Key VPN, go to VPN > IPSEC > Auto Key (IKE).
Figure 235:Auto Key list
Edit
Delete
Create Phase 1 Create a new phase 1 tunnel configuration. For more information,
see “Creating a new phase 1 configuration” on page 396.
Create Phase 2 Create a new phase 2 configuration. For more information, see
“Creating a new phase 2 configuration” on page 401.

01-30007-0203-20090112 395
Auto Key VPN IPSEC
Phase 1 The names of existing phase 1 tunnel configurations.

Phase 2 The names of existing phase 2 configurations.
Interface Binding The names of the local interfaces to which IPSec tunnels are
bound. These can be physical, aggregate, VLAN, inter-VDOM link
or wireless interfaces.
Delete and Edit icons Delete or edit a phase 1 configuration.
Creating a new phase 1 configuration

In phase 1, two VPN peers (or a FortiGate dialup server and a VPN client)
authenticate each other and exchange keys to establish a secure communication
channel between them. The basic phase 1 settings associate IPSec phase 1
parameters with a remote gateway and determine:
• whether the various phase 1 parameters will be exchanged in multiple rounds
with encrypted authentication information (main mode) or in a single message
with authentication information that is not encrypted (Aggressive mode)
• whether a pre-shared key or digital certificates will be used to authenticate the
identities of the two VPN peers (or a VPN server and its client)
• whether a special identifier, certificate distinguished name, or group name will
be used to identify the remote VPN peer or client when a connection attempt is
made.
To define basic IPSec phase 1 parameters, go to VPN > IPSEC > Auto Key (IKE)
and select Create Phase 1. For information about how to choose the correct
phase 1 settings for your particular situation, see the FortiGate IPSec VPN User
Guide.
Figure 236:New Phase 1

396 01-30007-0203-20090112
VPN IPSEC Auto Key
Name Type a name to represent the phase 1 definition. The maximum

name length is 15 characters for an interface mode VPN, 35
characters for a policy-based VPN. If Remote Gateway is Dialup
User, the maximum name length is further reduced depending on the
number of dialup tunnels that can be established: by 2 for up to 9
tunnels, by 3 for up to 99 tunnels, 4 for up to 999 tunnels, and so on.
For a tunnel mode VPN, the name should reflect where the remote
connection originates. For a route-based tunnel, the FortiGate unit
also uses the name for the virtual IPSec interface that it creates
automatically.
Remote Gateway Select the category of the remote connection:
• Static IP Address - If the remote peer has a static IP address.
• Dialup User - If one or more FortiClient or FortiGate dialup clients
with dynamic IP addresses will connect to the FortiGate unit.
• Dynamic DNS - If a remote peer that has a domain name and
subscribes to a dynamic DNS service will connect to the
FortiGate unit.
IP Address If you selected Static IP Address, type the IP address of the remote
peer.
Dynamic DNS If you selected Dynamic DNS, type the domain name of the remote
peer.
Local Interface This option is available in NAT/Route mode only. Select the name of
the interface through which remote peers or dialup clients connect to
the FortiGate unit.
By default, the local VPN gateway IP address is the IP address of
the interface that you selected. Optionally, you can specify a unique
IP address for the VPN gateway in the Advanced settings. For more
information, see “Local Gateway IP” on page 399.
Mode Select Main or Aggressive:
• In Main mode, the phase 1 parameters are exchanged in multiple
rounds with encrypted authentication information.
• In Aggressive mode, the phase 1 parameters are exchanged in
single message with authentication information that is not
encrypted.
When the remote VPN peer has a dynamic IP address and is
authenticated by a pre-shared key, you must select Aggressive
mode if there is more than one dialup phase1 configuration for the
interface IP address.
When the remote VPN peer has a dynamic IP address and is
authenticated by a certificate, you must select Aggressive mode if
there is more than one phase 1 configuration for the interface IP
address and these phase 1 configurations use different proposals.
Peer Options settings may require a particular mode. See Peer
Options, below.
Authentication Select Preshared Key or RSA Signature.
Method
Pre-shared Key If you selected Pre-shared Key, type the pre-shared key that the
FortiGate unit will use to authenticate itself to the remote peer or
dialup client during phase 1 negotiations. You must define the same
value at the remote peer or client. The key must contain at least 6
printable characters and should be known only by network
administrators. For optimum protection against currently known
attacks, the key should consist of a minimum of 16 randomly chosen
alphanumeric characters.
Certificate Name If you selected RSA Signature, select the name of the server
certificate that the FortiGate unit will use to authenticate itself to the
remote peer or dialup client during phase 1 negotiations. For
information about obtaining and loading the required server
certificate, see the FortiGate Certificate Management User Guide.

01-30007-0203-20090112 397
Auto Key VPN IPSEC
Peer Options One or more of the following options are available to authenticate
VPN peers or clients, depending on the Remote Gateway and
Authentication Method settings.
Accept any Accept the local ID of any remote VPN peer or client. The FortiGate
peer ID unit does not check identifiers (local IDs). You can set Mode to
Aggressive or Main.
You can use this option with RSA Signature authentication. But, for
highest security, you should configure a PKI user/group for the peer
and set Peer Options to Accept this peer certificate only.
Accept this This option is available only if the remote peer has a dynamic IP
peer ID address. Enter the identifier that is used to authenticate the remote
peer. This identifier must match the identifier that the remote peer’s
administrator has configured.
If the remote peer is a FortiGate unit, the identifier is specified in the
Local ID field of the phase 1 configuration.
If the remote peer is a FortiClient dialup client, the identifier is
specified in the Local ID field, accessed by selecting Config in the
Policy section of the VPN connection’s Advanced Settings.
Accept peer ID Authenticate multiple FortiGate or FortiClient dialup clients that use
in dialup group unique identifiers and unique pre-shared keys (or unique pre-shared
keys only) through the same VPN tunnel.
You must create a dialup user group for authentication purposes.
(For more information, see “User groups” on page 435.) Select the
group from the list next to the Accept peer ID in dialup group option.
For more information about configuring FortiGate dialup clients, see
the FortiGate IPSec VPN User Guide. For more information about
configuring FortiClient dialup clients, see the Authenticating
FortiClient Dialup Clients Technical Note.
You must set Mode to Aggressive when the dialup clients use unique
identifiers and unique pre-shared keys. If the dialup clients use
unique pre-shared keys only, you can set Mode to Main if there is
only one dialup phase 1 configuration for this interface IP address.
Accept this This option is available when Authentication Method is set to RSA
peer certificate Signature.
only Authenticate remote peers or dialup clients that use a security
certificate. Select the certificate from the list next to the option.
You must add peer certificates to the FortiGate configuration before
you can select them here. For more information, see “PKI
authentication” on page 431.
Accept this This option is available when Authentication Method is set to RSA
peer certificate Signature and Remote Gateway is set to Dialup User.
group only Use a certificate group to authenticate dialup clients that have
dynamic IP addresses and use unique certificates.
Select the name of the peer group from the list. You must first create
the group through the config user peergrp CLI command
before you can select it. For more information, see the “user” chapter
of the FortiGate CLI Reference. Members of the peer group must be
certificates added by using the config user peer CLI command.
You can also add peer certificates using the web-based manager.
For more information, see “PKI authentication” on page 431.
Advanced Define advanced phase 1 parameters. For more information, see
“Defining phase 1 advanced settings” on page 399.

398 01-30007-0203-20090112
VPN IPSEC Auto Key
Defining phase 1 advanced settings

You use the advanced P1 Proposal parameters to select the encryption and
authentication algorithms that the FortiGate unit uses to generate keys for the IKE
exchange. You can also select these advanced settings to ensure the smooth
operation of phase 1 negotiations.
To modify IPSec phase 1 advanced parameters, go to VPN > IPSEC >
Auto Key (IKE), select Create Phase 1, and then select Advanced. For
information about how to choose the correct advanced phase 1 settings for your
particular situation, see the FortiGate IPSec VPN User Guide.
Figure 237:Phase 1 advanced settings
Add
Delete
Enable IPSec This is available in NAT/Route mode only.

Interface Mode Create a virtual interface for the local end of the VPN tunnel. Select
this option to create a route-based VPN, clear it to create a policy-
based VPN.
IPv6 Version Select if you want to use IPv6 addresses for the remote gateway and
interface IP addresses. This is available only when Enable IPSec
Interface Mode is enabled.
Local Gateway IP If you selected Enable IPSec Interface Mode, specify an IP address
for the local end of the VPN tunnel. Select one of the following:
• Main Interface IP - The FortiGate unit obtains the IP address of
the interface from the network interface settings. For more
information, see “Interfaces” on page 107.
• Specify - You can specify a secondary address of the interface
selected in the phase 1 Local Interface field. For more information,
see “Local Interface” on page 397.
You cannot configure Interface mode in a Transparent mode VDOM.
P1 Proposal Select the encryption and authentication algorithms used to generate
keys for protecting negotiations.
Add or delete encryption and authentication algorithms as required.
Select a minimum of one and a maximum of three combinations. The
remote peer or client must be configured to use at least one of the
proposals that you define.

01-30007-0203-20090112 399
Auto Key VPN IPSEC
Select one of the following symmetric-key algorithms:

• DES - Digital Encryption Standard, a 64-bit block algorithm that
uses a 56-bit key.
• 3DES - Triple-DES, in which plain text is encrypted three times by
three keys.
• AES128 - a 128-bit block Cipher Block Chaining (CBC) algorithm
that uses a 128-bit key.
Select either of the following message digests to check the
authenticity of messages during phase 1 negotiations:
• MD5-Message Digest 5, the hash algorithm developed by RSA
Data Security.
• SHA1-Secure Hash Algorithm 1, which produces a 160-bit
message digest.
To specify a third combination, use the Add button beside the fields
for the second combination.
DH Group Select one or more Diffie-Hellman groups from DH group 1, 2, and 5.
At least one of the DH Group settings on the remote peer or client
must match one the selections on the FortiGate unit.
Keylife Type the time (in seconds) that must pass before the IKE encryption
key expires. When the key expires, a new key is generated without
interrupting service. The keylife can be from 120 to 172800 seconds.
Local ID If the FortiGate unit will act as a VPN client and you are using peer
IDs for authentication purposes, enter the identifier that the FortiGate
unit will supply to the VPN server during the phase 1 exchange.
If the FortiGate unit will act as a VPN client and you are using security
certificates for authentication, select the distinguished name (DN) of
the local server certificate that the FortiGate unit will use for
authentication purposes.
If the FortiGate unit is a dialup client and will not be sharing a tunnel
with other dialup clients (that is, the tunnel will be dedicated to this
FortiGate dialup client), set Mode to Aggressive.
XAuth This option supports the authentication of dialup clients.
Disable - Select if you do not use XAuth.
Enable as Client - If the FortiGate unit is a dialup client, type the user
name and password that the FortiGate unit will need to authenticate
itself to the remote XAuth server.
Enable as Server - This is available only if Remote Gateway is set to
Dialup User. Dialup clients authenticate as members of a dialup user
group. You must first create a user group for the dialup clients that
need access to the network behind the FortiGate unit. For more
information, see “Configuring a user group” on page 438.
You must also configure the FortiGate unit to forward authentication
requests to an external RADIUS or LDAP authentication server. For
information about these topics, see “Configuring a RADIUS server”
on page 425 or “Configuring an LDAP server” on page 427.
Select a Server Type setting to determine the type of encryption
method to use between the FortiGate unit, the XAuth client and the
external authentication server, and then select the user group from
the User Group list.
Nat-traversal Select the check box if a NAT device exists between the local
FortiGate unit and the VPN peer or client. The local FortiGate unit
and the VPN peer or client must have the same NAT traversal setting
(both selected or both cleared) to connect reliably.

400 01-30007-0203-20090112
VPN IPSEC Auto Key
Keepalive If you enabled NAT-traversal, enter a keepalive frequency setting.

Frequency The value represents an interval ranging from 10 to 900 seconds.
Dead Peer Select this check box to reestablish VPN tunnels on idle connections
Detection and clean up dead IKE peers if required. You can use this option to
receive notification whenever a tunnel goes up or down, or to keep
the tunnel connection open when no traffic is being generated inside
the tunnel. (For example, in scenarios where a dialup client or
dynamic DNS peer connects from an IP address that changes
periodically, traffic may be suspended while the IP address changes).
With Dead Peer Detection selected, you can use the config vpn
ipsec phase1 (tunnel mode) or config vpn ipsec phase1-
interface (interface mode) CLI command to optionally specify a
retry count and a retry interval. For more information, see the
Creating a new phase 2 configuration

After IPSec phase 1 negotiations end successfully, you begin phase 2. You
configure the phase 2 parameters to define the algorithms that the FortiGate unit
may use to encrypt and transfer data for the remainder of the session. During
phase 2, you select specific IPSec security associations needed to implement
security services and establish a tunnel.
The basic phase 2 settings associate IPSec phase 2 parameters with the phase 1
configuration that specifies the remote end point of the VPN tunnel. In most
cases, you need to configure only basic phase 2 settings.
To configure phase 2 settings, go to VPN > IPSEC > Auto Key (IKE) and select
Create Phase 2. For information about how to choose the correct phase 2 settings
for your particular situation, see the FortiGate IPSec VPN User Guide.
Figure 238:New Phase 2
Name Type a name to identify the phase 2 configuration.

Phase 1 Select the phase 1 tunnel configuration. For more information, see
“Creating a new phase 1 configuration” on page 396. The phase 1
configuration describes how remote VPN peers or clients will be
authenticated on this tunnel, and how the connection to the remote peer
or client will be secured.
Advanced Define advanced phase 2 parameters. For more information, see
“Defining phase 2 advanced settings” on page 401.
Defining phase 2 advanced settings

In phase 2, the FortiGate unit and the VPN peer or client exchange keys again to
establish a secure communication channel between them. You select the
encryption and authentication algorithms needed to generate keys for protecting
the implementation details of Security Associations (SAs). These are called P2
Proposal parameters. The keys are generated automatically using a Diffie-
Hellman algorithm.

01-30007-0203-20090112 401
Auto Key VPN IPSEC
You can use a number of additional advanced phase 2 settings to enhance the
operation of the tunnel. To modify IPSec phase 2 advanced parameters, go to
VPN > IPSEC Auto Key (IKE), select Create Phase 2, and then select Advanced.
For information about how to choose the correct advanced phase 2 settings for
your particular situation, see the FortiGate IPSec VPN User Guide.
Figure 239:Phase 2 advanced settings
Add
Delete
P2 Proposal Select the encryption and authentication algorithms that will be

proposed to the remote VPN peer. You can specify up to three
proposals. To establish a VPN connection, at least one of the
proposals that you specify must match configuration on the remote
peer.
Initially there are two proposals. Add and Delete icons are next to
the second Authentication field. To specify only one proposal,
select Delete to remove the second proposal. To specify a third
proposal, select Add.
It is invalid to set both Encryption and Authentication to NULL.
Encryption Select one of the following symmetric-key algorithms:
• NULL - Do not use an encryption algorithm.
• DES - Digital Encryption Standard, a 64-bit block algorithm that
uses a 56-bit key.
• 3DES - Triple-DES, in which plain text is encrypted three times
by three keys.
• AES128 - a 128-bit block Cipher Block Chaining (CBC)
algorithm that uses a 128-bit key.
Authentication Select one of the following message digests to check the
authenticity of messages during an encrypted session:
• NULL - Do not use a message digest.
• MD5 - Message Digest 5, the hash algorithm developed by
RSA Data Security.
• SHA1 - Secure Hash Algorithm 1, which produces a 160-bit
message digest.

402 01-30007-0203-20090112
VPN IPSEC Auto Key
Enable replay Optionally enable or disable replay detection. Replay attacks occur
detection when an unauthorized party intercepts a series of IPSec packets
and replays them back into the tunnel.
Enable perfect Enable or disable PFS. Perfect forward secrecy (PFS) improves
forward secrecy security by forcing a new Diffie-Hellman exchange whenever
(PFS) keylife expires.
DH Group Select one Diffie-Hellman group (1, 2, or 5). This must match the
DH Group that the remote peer or dialup client uses.
Keylife Select the method for determining when the phase 2 key expires:
Seconds, KBytes, or Both. If you select Both, the key expires when
either the time has passed or the number of KB have been
processed. The range is from 120 to 172800 seconds, or from
5120 to 2147483648 KB.
Autokey Keep Alive Select the check box if you want the tunnel to remain active when
no data is being processed.
DHCP-IPSec This is available only for tunnel mode phase 2 configurations
associated with a dialup phase 1 configuration.
Select the check box if the FortiGate unit acts as a dialup server
and will use FortiGate DHCP relay to assign VIP addresses to
FortiClient dialup clients. You must configure the DHCP relay
parameters separately. For more information, see “System DHCP”
on page 161.
If the FortiGate unit acts as a dialup server and you manually
assigned FortiClient dialup clients VIP addresses that match the
network behind the dialup server, selecting the check box will
cause the FortiGate unit to act as a proxy for the dialup clients.
Note: You can configure settings so that VPN users can browse the Internet through the
FortiGate unit. For more information, see “Internet browsing configuration” on page 407.
Quick Mode Optionally specify the source and destination IP addresses to be used as
Selector selectors for IKE negotiations. If the FortiGate unit is a dialup server, you
should keep the default value 0.0.0.0/0 unless you need to circumvent
problems caused by ambiguous IP addresses between one or more of
the private networks making up the VPN. You can specify a single host IP
address, an IP address range, or a network address. You may optionally
specify source and destination port numbers and a protocol number.
If you are editing an existing phase 2 configuration, the Source address
and Destination address fields are unavailable if the tunnel has been
configured to use firewall addresses as selectors. This option exists only
in the CLI. For more information, see the dst-addr-type, dst-name,
src-addr-type and src-name keywords for the vpn ipsec
phase2 command in the FortiGate CLI Reference.
Source address If the FortiGate unit is a dialup server, type the
source IP address that corresponds to the local
senders or network behind the local VPN peer (for
example, 172.16.5.0/24 or
172.16.5.0/255.255.255.0 for a subnet, or
172.16.5.1/32 or
172.16.5.1/255.255.255.255 for a server or
host, or 192.168.10.[80-100] or
192.168.10.80-192.168.10.100 for an
address range). A value of 0.0.0.0/0 means all IP
addresses behind the local VPN peer.
If the FortiGate unit is a dialup client, source address
must refer to the private network behind the
FortiGate dialup client.
Source port Type the port number that the local VPN peer uses to
transport traffic related to the specified service
(protocol number). The range is from 0 to 65535. To
specify all ports, type 0.

01-30007-0203-20090112 403
Manual Key VPN IPSEC
Destination Type the destination IP address that corresponds to

address the recipients or network behind the remote VPN
peer (for example, 192.168.20.0/24 for a subnet,
or 172.16.5.1/32 for a server or host, or
192.168.10.[80-100] for an address range). A
value of 0.0.0.0/0 means all IP addresses behind
the remote VPN peer.
Destination port Type the port number that the remote VPN peer uses
to transport traffic related to the specified service
(protocol number). The range is from 0 to 65535. To
specify all ports, type 0.
Protocol Type the IP protocol number of the service. The
range is from 0 to 255. To specify all services, type
0.
Manual Key
If required, you can manually define cryptographic keys for establishing an IPSec
VPN tunnel. You would define manual keys in situations where:
• You require prior knowledge of the encryption or authentication key (that is,
one of the VPN peers requires a specific IPSec encryption or authentication
key).
• You need to disable encryption and authentication.
In both cases, you do not specify IPSec phase 1 and phase 2 parameters; you
define manual keys by going to VPN > IPSEC > Manual Key instead.
Note: You should use manual keys only if it is unavoidable. There are potential difficulties in
keeping keys confidential and in propagating changed keys to remote VPN peers in a
secure manner.
For general information about how to configure an IPSec VPN, see the FortiGate
IPSec VPN User Guide.
Figure 240:Manual Key list
Delete
Edit
Create New Create a new manual key configuration. See “Creating a new
manual key configuration” on page 405.
Tunnel Name The names of existing manual key configurations.
Remote Gateway The IP addresses of remote peers or dialup clients.
Encryption The names of the encryption algorithms specified in the manual key
Algorithm configurations.
Authentication The names of the authentication algorithms specified in the manual
Algorithm key configurations.
Delete and Edit Delete or edit a manual key configuration.
icons

404 01-30007-0203-20090112
VPN IPSEC Manual Key
Creating a new manual key configuration

If one of the VPN devices is manually keyed, the other VPN device must also be
manually keyed with the identical authentication and encryption keys. In addition,
it is essential that both VPN devices be configured with complementary Security
Parameter Index (SPI) settings. The administrators of the devices need to
cooperate to achieve this.
Each SPI identifies a Security Association (SA). The value is placed in ESP
datagrams to link the datagrams to the SA. When an ESP datagram is received,
the recipient refers to the SPI to determine which SA applies to the datagram. You
must manually specify an SPI for each SA. There is an SA for each direction, so
for each VPN you must specify two SPIs, a local SPI and a remote SPI, to cover
bidirectional communications between two VPN devices.
Caution: If you are not familiar with the security policies, SAs, selectors, and SA databases
! for your particular installation, do not attempt the following procedure without qualified
assistance.
To specify manual keys for creating a tunnel, go to VPN > IPSEC > Manual Key
and select Create New.
Figure 241:New Manual Key
Name Type a name for the VPN tunnel. The maximum name length is 15
characters for an interface mode VPN, 35 characters for a policy-
based VPN.
Local SPI Type a hexadecimal number (up to 8 characters, 0-9, a-f) that
represents the SA that handles outbound traffic on the local
FortiGate unit. The valid range is from 0x100 to 0xffffffff. This
value must match the Remote SPI value in the manual key
configuration at the remote peer.
Remote SPI Type a hexadecimal number (up to 8 characters, 0-9, a-f) that
represents the SA that handles inbound traffic on the local FortiGate
unit. The valid range is from 0x100 to 0xffffffff. This value must
match the Local SPI value in the manual key configuration at the
remote peer.
Remote Gateway Type the IP address of the public interface to the remote peer. The
address identifies the recipient of ESP datagrams.

01-30007-0203-20090112 405
Manual Key VPN IPSEC
Local Interface This option is available in NAT/Route mode only. Select the name of
the interface to which the IPSec tunnel will be bound. The FortiGate
unit obtains the IP address of the interface from the network interface
settings. For more information, see “Interfaces” on page 107.
Encryption Select one of the following symmetric-key encryption algorithms:
Algorithm • DES - Digital Encryption Standard, a 64-bit block algorithm that
uses a 56-bit key.
• 3DES - Triple-DES, in which plain text is encrypted three times by
three keys.
Note: The algorithms for encryption and authentication cannot both
be NULL.
Encryption Key If you selected:

• DES, type a 16-character hexadecimal number (0-9, a-f).
• 3DES, type a 48-character hexadecimal number (0-9, a-f)
separated into three segments of 16 characters.
• AES128, type a 32-character hexadecimal number (0-9, a-f)
separated into two segments of 16 characters.
separated into three segments of 16 characters.
separated into four segments of 16 characters.
Authentication Select one of the following message digests:
Algorithm • MD5-Message Digest 5 algorithm, which produces a 128-bit
message digest.
• SHA1-Secure Hash Algorithm 1, which produces a 160-bit
message digest.
Note: The Algorithms for encryption and authentication cannot both
be NULL.
Authentication If you selected:
Key • MD5, type a 32-character hexadecimal number (0-9, a-f)
separated into two segments of 16 characters.
• SHA1, type 40-character hexadecimal number (0-9, a-f)
separated into one segment of 16 characters and a second
segment of 24 characters.
IPSec Interface Create a virtual interface for the local end of the VPN tunnel. Select
Mode this check box to create a route-based VPN, clear it to create a policy-
based VPN.
This is available only in NAT/Route mode.

406 01-30007-0203-20090112
VPN IPSEC Internet browsing configuration
Internet browsing configuration

By using appropriate firewall policies, you can enable VPN users to browse the
Internet through the FortiGate unit. The required policies are different for policy-
based and route-based VPNs. For more information, see “Configuring firewall
To create a policy-based VPN Internet browsing configuration

2 Select Create New and enter the following information
Source Interface/Zone Select the FortiGate unit public interface.

Source Address Name Select All.
Destination Interface/Zone Select the FortiGate unit public interface.
Destination Address Name Select the remote network address name.
Action Select IPSEC.
VPN Tunnel Select the tunnel that provides access to the private
network behind the FortiGate unit.
Inbound NAT Select the check box.
3 Configure other settings as required.

4 Select OK.
To configure a route-based VPN Internet browsing configuration

2 Select Create New and enter the following information.
Source Interface/Zone Select the IPSec interface.

Source Address Name Select All.
Destination Interface/Zone Select the FortiGate unit public interface.
Destination Address Name Select All.
Action Select ACCEPT.
NAT Select the check box.
3 Configure other settings as required.

4 Select OK.
Concentrator
In a hub-and-spoke configuration, policy-based VPN connections to a number of
remote peers radiate from a single, central FortiGate unit. Site-to-site connections
between the remote peers do not exist; however, You can establish VPN tunnels
between any two of the remote peers through the FortiGate unit “hub”.
In a hub-and-spoke network, all VPN tunnels terminate at the hub. The peers that
connect to the hub are known as “spokes”. The hub functions as a concentrator
on the network, managing all VPN connections between the spokes. VPN traffic
passes from one tunnel to the other through the hub.
You define a concentrator to include spokes in the hub-and-spoke configuration.

01-30007-0203-20090112 407
Concentrator VPN IPSEC
To define a concentrator, go to VPN > IPSEC > Concentrator. For detailed

information and step-by-step procedures about how to set up a hub-and-spoke
configuration, see the FortiGate IPSec VPN User Guide.
Figure 242:Concentrator list
Delete
Edit
Create New Define a new concentrator for an IPSec hub-and-spoke

configuration. For more information, see “Defining concentrator
Concentrator Name The names of existing IPSec VPN concentrators.
Members The tunnels that are associated with the concentrators.
Delete and Edit Delete or edit a concentrator.
icons
Defining concentrator options

A concentrator configuration specifies which spokes to include in an IPSec hub-
and-spoke configuration.
To specify the spokes of an IPSec hub-and-spoke configuration, go to VPN >
IPSEC > Concentrator and select Create New.
Figure 243:New VPN Concentrator
Right Arrow
Left Arrow
Concentrator Name Type a name for the concentrator.

Available Tunnels A list of defined IPSec VPN tunnels. Select a tunnel from the list and
then select the right arrow. Repeat these steps until all of the tunnels
associated with the spokes are included in the concentrator.
Members A list of tunnels that are members of the concentrator. To remove a
tunnel from the concentrator, select the tunnel and select the left
arrow.

408 01-30007-0203-20090112
VPN IPSEC Monitor
Monitor
You can use the monitor to view activity on IPSec VPN tunnels and start or stop
those tunnels. The display provides a list of addresses, proxy IDs, and timeout
information for all active tunnels, including tunnel mode and route-based
(interface mode) tunnels.
You can use filters control the information displayed in the list. For more
information, see “Adding filters to web-based manager lists” on page 58.
To view active tunnels, go to VPN > IPSEC > Monitor.
Figure 244:Monitor list
Current Page
Type Select the types of VPN to display: “All”, “Dialup”, or “Static IP or

Dynamic DNS”.
Clear All Filters Select to clear any column display filters you might have applied.
Current Page The current page number of list items that are displayed. Select the
left and right arrows to display the first, previous, next or last page of
monitored VPNs.
Name The name of the phase 1 configuration for the VPN.
Remote Gateway The public IP address of the remote host device, or if a NAT device
exists in front of the remote host, the public IP address of the NAT
device.
Remote Port The UDP port of the remote host device, or if a NAT device exists in
front of the remote host, the UDP port of the NAT device. Zero (0)
indicates that any port can be used.
Proxy ID Source The IP addresses of the hosts, servers, or private networks behind
the FortiGate unit. The page may display a network range if the
source address in the firewall encryption policy was expressed as a
range of IP addresses.
Proxy ID When a FortiClient dialup client establishes a tunnel:
Destination • If VIP addresses are not used, the Proxy ID Destination field
displays the public IP address of the remote host Network
Interface Card (NIC).
• If VIP addresses were configured (manually or through FortiGate
DHCP relay), the Proxy ID Destination field displays either the
VIP address belonging to the FortiClient dialup client, or the
subnet address from which VIP addresses were assigned.
When a FortiGate dialup client establishes a tunnel, the Proxy ID
Destination field displays the IP address of the remote private
network.
Tunnel up or tunnel A green arrow means the tunnel is currently processing traffic.
down icon Select to bring down the tunnel.
A red arrow means the tunnel is not processing traffic. Select to
bring up the tunnel.
For Dialup VPNs, the list provides status information about the VPN tunnels
established by dialup clients, including their IP addresses. The number of tunnels
shown in the list can change as dialup clients connect and disconnect.
For Static IP or dynamic DNS VPNs, the list provides status and IP addressing
information about VPN tunnels, active or not, to remote peers that have static IP
addresses or domain names. You can also start and stop individual tunnels from
the list.

01-30007-0203-20090112 409
Monitor VPN IPSEC

410 01-30007-0203-20090112
VPN PPTP PPTP Range
VPN PPTP
FortiGate units support PPTP to tunnel PPP traffic between two VPN peers.
Windows or Linux PPTP clients can establish a PPTP tunnel with a FortiGate unit
that has been configured to act as a PPTP server. As an alternative, you can
configure the FortiGate unit to forward PPTP packets to a PPTP server on the
network behind the FortiGate unit.
PPTP VPN is available only in NAT/Route mode. The current maximum number of
PPTP sessions is 254.
This section explains how to use the web-based manager to specify a range of IP
addresses for PPTP clients. For information about how to perform other related
PPTP VPN setup tasks, see the FortiGate PPTP VPN User Guide.
If you enable virtual domains (VDOMs) on the FortiGate unit, VPN PPTP is
PPTP Range
The PPTP address range is the range of addresses reserved for remote PPTP
clients. When the remote PPTP client establishes a connection, the FortiGate unit
assigns an IP address from a reserved range of IP addresses to the client PPTP
interface. The PPTP client uses the assigned IP address as its source address for
the duration of the connection.
To enable PPTP and specify the PPTP address range, go to VPN > PPTP >
PPTP Range, select the required options, and then select Apply.
Note: The start and end IPs in the PPTP address range must be in the same 24-bit subnet,
e.g. 192.168.1.1 - 192.168.1.254.
Figure 245:Edit PPTP range
Enable PPTP Select to enable PPTP. You must add a user group before you can
select the option. See “User groups” on page 435.
Starting IP Type the starting address in the range of reserved IP addresses.
Ending IP Type the ending address in the range of reserved IP addresses.
User Group Select the name of the PPTP user group that you defined.
Disable PPTP Select the option to disable PPTP support.

01-30007-0203-20090112 411
PPTP Range VPN PPTP

412 01-30007-0203-20090112
VPN SSL
VPN SSL
An SSL VPN (Secure Sockets Layer virtual private network) is a form of VPN that
can be used with a standard Web browser. SSL VPN does not require the
installation of specialized client software on end users’ computers, and is ideal for
applications including web-based email, business and government directories, file
sharing, remote backup, remote system management, and consumer-level
electronic commerce.
The two modes of SSL VPN operation (supported in NAT/Route mode only) are:
• web-only mode, for thin remote clients equipped with a web-browser only.
• tunnel mode, for remote computers that run a variety of client and server
applications.
When the FortiGate unit provides services in web-only mode, a secure connection
between the remote client and the FortiGate unit is established through the SSL
VPN security in the FortiGate unit and the SSL security in the web browser. After
the connection has been established, the FortiGate unit provides access to
selected services and network resources through a web portal.
When users have complete administrative rights over their computers and use a
variety of applications, tunnel mode allows remote clients to access the local
internal network as if they were connected to the network directly.
This section provides information about the features of SSL VPN available for
configuration in the web-based manager. Only FortiGate units that run in
NAT/Route mode support the SSL VPN feature.
If you enable virtual domains (VDOMs) on the FortiGate unit, VPN SSL is
Note: For detailed instructions about how to configure web-only mode or tunnel-mode
operation, see the FortiGate SSL VPN User Guide.

• Configuring SSL VPN
• Monitoring SSL VPN sessions
• SSL VPN bookmarks
• Viewing the SSL VPN bookmark list
• Configuring SSL VPN bookmarks
• Viewing the SSL VPN Bookmark Group list
• Configuring SSL VPN bookmark groups

01-30007-0203-20090112 413
ssl.root VPN SSL
ssl.root
The FortiGate unit has a virtual SSL VPN interface called ssl.<vdom_name>. The
root VDOM, called ssl.root, appears in the firewall policy interface lists and static
route interface lists. You can use the ssl-root interface to allow access to
additional networks and facilitate a connected user’s ability to browse the Internet
through the FortiGate unit.
The SSL VPN tunnel-mode access requires the following firewall policies:
• External > Internal, with the action set to SSL, with an SSL user group
• ssl.root > Internal, with the action set to Accept
• Internal > ssl.root, with the action set to Accept.
Access also requires a new static route: Destination network - <ssl tunnel mode
assigned range> interface ssl.root.
If you are configuring Internet access through an SSL VPN tunnel, you must add
the following configuration: ssl.root > External, with the action set to Accept, NAT
enabled.
Configuring SSL VPN

You can configure basic SSL VPN settings including timeout values and SSL
encryption preferences. If required, you can also enable the use of digital
certificates for authenticating remote clients.
Note: If required, you can enable SSL version 2 encryption (for compatibility with older
browsers) through a FortiGate CLI command. For more information, see the ssl
settings command in the “vpn” chapter of the FortiGate CLI Reference.
To enable and configure SSL VPN, go to VPN > SSL > Config.
Figure 246:SSL-VPN Settings

414 01-30007-0203-20090112
VPN SSL Configuring SSL VPN
Enable SSL VPN Select to enable SSL VPN connections.

Tunnel IP Range Specify the range of IP addresses reserved for tunnel-
mode SSL VPN clients. Type the starting and ending
address that defines the range of reserved IP
addresses.
Server Certificate Select the signed server certificate to use for
authentication purposes. If you leave the default setting
(Self-Signed), the FortiGate unit offers its factory
installed (self-signed) certificate from Fortinet to remote
clients when they connect.
Require Client Certificate If you want to enable the use of group certificates for
authenticating remote clients, select the check box.
Afterward, when the remote client initiates a connection,
the FortiGate unit prompts the client for its client-side
certificate as part of the authentication process.
Encryption Key Algorithm Select the algorithm for creating a secure SSL
connection between the remote client web browser and
the FortiGate unit.
Default - RC4(128 If the web browser on the remote client can match a
bits) and higher cipher suite greater than or equal to 128 bits, select this
option.
High - AES(128/256 If the web browser on the remote client can match a high
bits) and 3DES level of SSL encryption, select this option to enable
cipher suites that use more than 128 bits to encrypt data.
Low - RC4(64 bits), If you are not sure which level of SSL encryption the
DES and higher remote client web browser supports, select this option to
enable a cipher suite greater than or equal to 64 bits.
Idle Timeout Type the period of time (in seconds) to control how long
the connection can remain idle before the system forces
the user to log in again. The range is from 10 to 28800
seconds. You can also set the value to 0 to have no idle
connection timeout. This setting applies to the SSL VPN
session. The interface does not time out when web
application sessions or tunnels are up.
Portal Message If you want to display a custom caption at the top of the
web portal home page, type the message.
Advanced (DNS and WINS Servers)
DNS Server #1 Enter up to two DNS Servers to be provided for the use
DNS Server #2 of clients.
WINS Server #1 Enter up to two WINS Servers to be provided for the use
WINS Server #2 of clients.
Apply Select to save and apply settings.

01-30007-0203-20090112 415
Monitoring SSL VPN sessions VPN SSL
Monitoring SSL VPN sessions

You can view a list of all active SSL VPN sessions. The list displays the user name
of the remote user, the IP address of the remote client, and the time the
connection was made. You can also see which services are being provided, and
delete an active web session from the FortiGate unit.
To view the list of active SLS VPN sessions, go to VPN > SSL > Monitor.
Figure 247:Monitor list
Delete
No. The connection identifiers.

User The user names of all connected remote users.
Source IP The IP addresses of the host devices connected to the FortiGate unit.
Begin Time The starting time of each connection.
Description Information about the services provided by an SSL VPN tunnel session.
Subsession
Tunnel IP: IP address that the FortiGate unit assigned to the remote
client.
Delete icon: Delete current subsession.
Action Delete a web session.
SSL VPN bookmarks

If you create a user account that permits web-only mode access, you can create
hyperlinks to frequently accessed server applications that the user can select to
start any session from his or her home page. The FortiGate unit forwards client
requests to servers on the Internet or internal network. To use the web-portal
applications, you add the URL, IP address, or name of the server application to
the Bookmarks list. The bookmarks are available when the user starts an active
SSL VPN session.
Viewing the SSL VPN bookmark list

You can view a list of all SSL VPN bookmarks that were created previously. For
more information, see “Configuring SSL VPN bookmarks” on page 417. The list
details the name of the bookmark, type of bookmark, and the link details.
To view the list of existing SSL VPN bookmarks, go to VPN > SSL > Bookmark.

416 01-30007-0203-20090112
VPN SSL SSL VPN bookmarks
Figure 248:Bookmark list
Delete Edit
Bookmark Name The types and names of links to remote server applications and
network services.
Link The URL, host, or folder of the bookmark link.
icons
Configuring SSL VPN bookmarks

To create hyperlinks to frequently accessed server applications, go to VPN > SSL
> Bookmark and select Create New.
Figure 249:Create New Bookmark
Bookmark Name Type the text to display in the hyperlink. The name is displayed in the
Bookmarks list.

01-30007-0203-20090112 417
SSL VPN bookmarks VPN SSL
Application Type Select the abbreviated name of the server application or network
service from the drop-down list:
• Web
• Telnet
• FTP
• SMB/CIFS
• VNC
• RDP
• SSH
URL/Host/Folder Type the information that the FortiGate unit needs to forward client
requests to the correct server application or network service:
• If the application type is Web, type the URL of the web server (for
example, www.example.com).
• If the application type is Telnet, type the IP address of the telnet
host (for example, 10.10.10.10).
• If the application type is FTP, type the IP address of the FTP host
as a root directory/folder (for example, //server/folder/).
• If the application type is SMB/CIFS, type the IP address of the SMB
host and the root directory/folder associated with your account (for
example, //server/folder/).
• If the application type is VNC, type the IP address of the VNC host
(for example, 10.10.10.10).
• If the application type is RDP, type the IP address of the RDP host
(for example, 10.10.10.10).
• If the application type is SSH, type the IP address of the SSH host
(for example, 10.10.10.10).
Viewing the SSL VPN Bookmark Group list

You can create a group of specific bookmarks to include in the configuration of an
SSL VPN user group. For details about SSL VPN user groups, see “Configuring
additional SSL VPN user group options” on page 442.
To view a list of bookmark groups, go to VPN > SSL > Bookmark Group.
Figure 250:Bookmark Group list

Delete Edit
Group Name Name of bookmark group.

Bookmarks List of bookmarks that are available to the group of users defined in
Group Name.
icons

418 01-30007-0203-20090112
VPN SSL SSL VPN bookmarks
Configuring SSL VPN bookmark groups

To create a group of selected bookmarks, go to VPN > SSL > Bookmark Group
Figure 251:Create New Bookmark Group
Right Arrow
Left Arrow
Name Type the name of the bookmark group. The name will be displayed in
the Bookmark Group list.
Available The list of bookmarks available for inclusion in the bookmark group.
Bookmarks Lists bookmarks under the appropriate category (FTP, RDP, SMB,
Telnet, VNC, Web, or SSH).
Used Bookmarks The list of bookmarks that belong to the bookmark group.
Right Arrow Add a bookmark to the Used Bookmarks list.
Select a bookmark in the Available Bookmarks list and then select the
Right Arrow to move it to the Used Bookmarks list.
Left Arrow Remove a bookmark from the Used Bookmarks list.
Select a bookmark in the Used Bookmarks list and then select the Left
Arrow to move it to the Available Bookmarks list.
Create New Select to create a new bookmark for inclusion in the Available
Bookmarks list.

01-30007-0203-20090112 419
SSL VPN bookmarks VPN SSL

420 01-30007-0203-20090112
User Authentication Configuring user authentication
User Authentication
This section explains how to set up user accounts, user groups, and external
authentication servers. You can use these components of user authentication to
control access to network resources.
If you enable virtual domains (VDOMs) on the FortiGate unit, user authentication
is configured separately for each virtual domain. For details, see “Using virtual
• Configuring user authentication
• Local user accounts
• Remote authentication
• RADIUS servers
• LDAP servers
• TACACS+ servers
• PKI authentication
• Directory Service servers
• User groups
• Authentication settings
Configuring user authentication

FortiGate authentication controls access by user group, but you need to complete
one or more of the following tasks prior to configuring the user groups.
• Configure local user accounts. For each user, you can choose whether the
password is verified by the FortiGate unit, by a RADIUS server, by an LDAP
server, or by a TACACS+ server. See “Local user accounts” on page 422.
• Configure your FortiGate unit to authenticate users by using your RADIUS,
LDAP, or TACACS+ servers. See “RADIUS servers” on page 424, “LDAP
servers” on page 426, and “TACACS+ servers” on page 429.
• Configure access to the FortiGate unit if you use a Directory Service server for
authentication. See “Configuring a Directory Service server” on page 434.
• Configure for certificate-based authentication for administrative access
(HTTPS web-based manager), IPSec, SSL-VPN, and web-based firewall
authentication. See “PKI authentication” on page 431.
You can configure your FortiGate unit to authenticate system administrators with
your FortiGate unit, using RADIUS, LDAP and TACACS+ servers and with
certificate-based authentication using PKI. See “System Administrators” on
page 195. You can change the authentication timeout value or select the protocol
supported for Firewall authentication. See “Authentication settings” on page 445.

01-30007-0203-20090112 421
Local user accounts User Authentication
For each network resource that requires authentication, you specify which user
groups are permitted access to the network. There are three types of user groups:
Firewall, Directory Service, and SSL VPN. See “Firewall user groups” on
page 436, “Directory Service user groups” on page 437, and “SSL VPN user
groups” on page 437.
Local user accounts

A local user is a user configured on a FortiGate unit. The user can be
authenticated with a password stored on the FortiGate unit (the user name and
password must match a user account stored on the FortiGate unit) or with a
password stored on an authentication server (the user name must match a user
account stored on the FortiGate unit and the user name and password must
match a user account stored on the authentication server associated with the
user).
To view the local user list, go to User > Local.
Figure 252:Example Local user list
Delete
Edit
Create New Add a new local user account.

User Name The local user name.
Type The authentication type to use for this user. The authentication types
are Local (user and password stored on FortiGate unit), LDAP,
RADIUS, and TACACS+ (user and password matches a user account
stored on the authentication server).
Delete icon Delete the user.
The delete icon is not available if the user belongs to a user group.
Edit icon Edit the user account.
Note: Deleting the user name deletes the authentication configured for the user.

422 01-30007-0203-20090112
User Authentication Remote authentication
Configuring a Local user account

You can block a user with a valid local user account from authenticating at all, or
configure the FortiGate unit to allow a user to authenticate with a user name and
password stored on the FortiGate unit, or with an account stored on a specific
server (LDAP, RADIUS, or TACACS+).
To add a local user, go to User > Local and select Create New.
Figure 253:Local user
User Name Enter a name that identifies the user.

Disable Select Disable to prevent this user from authenticating.
Password To authenticate this user using a password stored on the FortiGate unit,
select Password and enter the password. The password should be at
least six characters.
LDAP Select LDAP to authenticate this user using a password stored on an
LDAP server. Select the LDAP server from the list.
You can select only an LDAP server that has been added to the
FortiGate LDAP configuration. See “LDAP servers” on page 426.
RADIUS Select RADIUS to authenticate this user using a password stored on a
RADIUS server. Select the RADIUS server from the list.
You can select only a RADIUS server that has been added to the
FortiGate RADIUS configuration. See “RADIUS servers” on page 424.
TACACS+ Select TACACS+ to authenticate this user using a password stored on
a TACACS server. Select the TACACS+ server from the list.
You can select only a TACACS server that has been added to the
FortiGate TACACS configuration. See “TACACS+ servers” on
page 429.
Remote authentication
Remote authentication is generally used to ensure that employees working offsite
can remotely access their corporate network with appropriate security measures
in place. In general terms, authentication is the process of attempting to verify the
(digital) identity of the sender of a communication such as a login request. The
sender may be someone using a computer, the computer itself, or a computer
program. Since a computer system should be used only by those who are
authorized to do so, there must be a measure in place to detect and exclude any
unauthorized access.

01-30007-0203-20090112 423
RADIUS servers User Authentication
On a FortiGate unit, you can control access to network resources by defining lists
of authorized users, called user groups. To use a particular resource, such as a
network or VPN tunnel, the user must:
• belong to one of the user groups that is allowed access
• correctly enter a user name and password to prove his or her identity, if asked
to do so.
RADIUS servers
Remote Authentication and Dial-in User Service (RADIUS) servers provide
authentication, authorization, and accounting functions. FortiGate units use the
authentication function of the RADIUS server.To use the RADIUS server for
authentication, you must configure the server before you configure the FortiGate
users or user groups that will need it.
If you have configured RADIUS support and a user is required to authenticate
using a RADIUS server, the FortiGate unit sends the user’s credentials to the
RADIUS server for authentication. If the RADIUS server can authenticate the
user, the user is successfully authenticated with the FortiGate unit. If the RADIUS
server cannot authenticate the user, the FortiGate unit refuses the connection.
You can override the default authentication scheme by selecting a specific
authentication protocol or changing the default port for RADIUS traffic.
Note: The default port for RADIUS traffic is 1812. If your RADIUS server is using port 1645,
use the CLI to change the default RADIUS port. For more information, see the config
system global command in the FortiGate CLI Reference.
To view the list of RADIUS servers, go to User > Remote > RADIUS.
Figure 254:Example RADIUS server list
Delete
Edit
Create New Add a new RADIUS server. The maximum number is 10.
Name The name that identifies the RADIUS server on the FortiGate unit.
Server Name/IP The domain name or IP address of the RADIUS server.
Delete icon Delete a RADIUS server configuration.
You cannot delete a RADIUS server that has been added to a user
group.
Edit icon Edit a RADIUS server configuration.

424 01-30007-0203-20090112
User Authentication RADIUS servers
Configuring a RADIUS server

The RADIUS server uses a “shared secret” key to encrypt information passed
between it and clients such as the FortiGate unit. When you configure a RADIUS
server, you can also configure a secondary RADIUS server. The FortiGate unit
attempts authentication with the primary server first, and if there is no response,
uses the secondary server. You can include the RADIUS server in every user
group without including it specifically in user group configurations. The RADIUS
server can use several different authentication protocols during the authentication
process:
• MS-CHAP-V2 is the Microsoft challenge-handshake authentication protocol v2
• MS-CHAP is the Microsoft challenge-handshake authentication protocol v1
• CHAP (challenge-handshake authentication protocol) provides the same
functionality as PAP, but does not send the password and other user
information over the network to a security server
• PAP (password authentication protocol) is used to authenticate PPP
connections. PAP transmits passwords and other user information in clear text
(unencrypted).
If you have not selected a protocol, the default protocol configuration uses PAP,
MS-CHAPv2, and CHAP, in that order.
To add a new RADIUS server, go to User > Remote > RADIUS and select Create
New.
Figure 255:RADIUS server configuration
Name Enter the name that is used to identify the RADIUS server
on the FortiGate unit.
Primary Server Name/IP Enter the domain name or IP address of the primary
RADIUS server.
Primary Server Secret Enter the RADIUS server secret key for the primary
RADIUS server. The primary server secret key should be a
maximum of 16 characters in length.
Secondary Server Name/IP Enter the domain name or IP address of the secondary
RADIUS server, if you have one.

01-30007-0203-20090112 425
LDAP servers User Authentication
Secondary Server Secret Enter the RADIUS server secret key for the secondary
RADIUS server. The secondary server secret key should be
a maximum of 16 characters in length.
Authentication Scheme Select Use Default Authentication Scheme to authenticate
with the default method. The default authentication scheme
uses PAP, MS-CHAP-V2, and CHAP, in that order.
Select Specify Authentication Protocol to override the
default authentication method, and choose the protocol
from the list: MS-CHAP-V2, MS-CHAP, CHAP, or PAP,
depending on what your RADIUS server needs.
NAS IP/Called Station ID Enter the NAS IP address and Called Station ID (for more
information about RADIUS Attribute 31, see
RFC 2548 Microsoft Vendor-specific RADIUS Attributes). If
you do not enter an IP address, the IP address that the
FortiGate interface uses to communicate with the RADIUS
server will be applied.
Include in every User Group Select to have the RADIUS server automatically included in
all user groups.
LDAP servers
Lightweight Directory Access Protocol (LDAP) is an Internet protocol used to
maintain authentication data that may include departments, people, groups of
people, passwords, email addresses, and printers. An LDAP consists of a data-
representation scheme, a set of defined operations, and a request/response
network.
If you have configured LDAP support and require a user to authenticate using an
LDAP server, the FortiGate unit contacts the LDAP server for authentication. To
authenticate with the FortiGate unit, the user enters a user name and password.
The FortiGate unit sends this user name and password to the LDAP server. If the
LDAP server can authenticate the user, the FortiGate unit successfully
authenticates the user. If the LDAP server cannot authenticate the user, the
FortiGate unit refuses the connection.
The FortiGate unit supports LDAP protocol functionality defined in
RFC 2251: Lightweight Directory Access Protocol v3, for looking up and validating
user names and passwords. FortiGate LDAP supports all LDAP servers compliant
with LDAP v3. In addition, FortiGate LDAP supports LDAP over SSL/TLS. To
configure SSL/TLS authentication, refer to the FortiGate CLI Reference.
FortiGate LDAP support does not extend to proprietary functionality, such as
notification of password expiration, that is available from some LDAP servers. Nor
does the FortiGate LDAP supply information to the user about why authentication
failed.
To view the list of LDAP servers, go to User > Remote > LDAP.
Figure 256:Example LDAP server list
Delete
Edit

426 01-30007-0203-20090112
User Authentication LDAP servers
Create New Add a new LDAP server. The maximum number is 10.
Port The TCP port used to communicate with the LDAP server.
Common Name The common name identifier for the LDAP server. Most LDAP servers
Identifier use cn. However, some servers use other common name identifiers
such as uid.
Distinguished The distinguished name used to look up entries on the LDAP servers
Name use. The distinguished name reflects the hierarchy of LDAP database
object classes above the common name identifier.
Delete icon Delete the LDAP server configuration.
Edit icon Edit the LDAP server configuration.
Configuring an LDAP server

A directory is a set of objects with similar attributes organized in a logical and
hierarchical way. Generally, an LDAP directory tree reflects geographic or
organizational boundaries, with the Domain Name System (DNS) names at the
top level of the hierarchy. The common name identifier for most LDAP servers is
cn; however some servers use other common name identifiers such as uid.
For example, you could use the following base distinguished name:
ou=marketing,dc=fortinet,dc=com
where ou is organization unit and dc is a domain component.
You can also specify multiple instances of the same field in the distinguished
name, for example, to specify multiple organization units:
ou=accounts,ou=marketing,dc=fortinet,dc=com
Binding is said to occur when the LDAP server successfully authenticates the user
and allows the user access to the LDAP server based on his or her permissions.
You can configure the FortiGate unit to use one of three types of binding:
• anonymous - bind using anonymous user search
• regular - bind using user name/password and then search
• simple - bind using a simple password authentication without a search.
You can use simple authentication if the user records all fall under one dn. If the
users are under more than one dn, use the anonymous or regular type, which can
search the entire LDAP database for the required user name.
If your LDAP server requires authentication to perform searches, use the regular
type and provide values for user name and password.

01-30007-0203-20090112 427
LDAP servers User Authentication
To add an LDAP server, go to User > Remote > LDAP and select Create New.
Enter the information below and select OK.
Figure 257:LDAP server configuration
Query
Name Enter the name that identifies the LDAP server on the FortiGate
unit.
Server Name/IP Enter the domain name or IP address of the LDAP server.
Server Port Enter the TCP port used to communicate with the LDAP server.
By default, LDAP uses port 389.
If you use a secure LDAP server, the default port changes when
you select Secure Connection.
Common Name Enter the common name identifier for the LDAP server. The
Identifier maximum number of characters is 20.
Distinguished Name Enter the base distinguished name for the server using the
correct X.500 or LDAP format. The FortiGate unit passes this
distinguished name unchanged to the server. The maximum
number of characters is 512.
Query icon View the LDAP server Distinguished Name Query tree for the
LDAP server that you are configuring so that you can cross-
reference to the Distinguished Name.
For more information, see “Using Query”.
Bind Type Select the type of binding for LDAP authentication.
Regular Connect to the LDAP server directly with user name/password,
then receive accept or reject based on search of given values.
Anonymous Connect as an anonymous user on the LDAP server, then
retrieve the user name/password and compare them to given
values.
Simple Connect directly to the LDAP server with user name/password
authentication.
Filter Enter the filter to use for group searching. Available if Bind Type
is Regular or Anonymous.

428 01-30007-0203-20090112
User Authentication TACACS+ servers
User DN Enter the Distinguished name of the user to be authenticated.

Available if Bind Type is Regular.
Password Enter the password of the user to be authenticated. Available if
Bind Type is Regular.
Secure Connection Select to use a secure LDAP server connection for
authentication.
Protocol Select a secure LDAP protocol to use for authentication.
Depending on your selection, the value in Server Port will
change to the default port for the selected protocol. Available
only if Secure Connection is selected.
LDAPS: port 636
STARTTLS: port 389
Certificate Select a certificate to use for authentication from the list. The
certificate list comes from CA certificates at System >
Certificates > CA Certificates.
Using Query
The LDAP Distinguished Name Query list displays the LDAP Server IP address,
and all the distinguished names associated with the Common Name Identifier for
the LDAP server. The tree helps you to determine the appropriate entry for the DN
field. To see the distinguished name associated with the Common Name identifier,
select the Expand Arrow beside the CN identifier and then select the DN from the
list. The DN you select is displayed in the Distinguished Name field. Select OK to
save your selection in the Distinguished Name field of the LDAP Server
configuration.
To see the users within the LDAP Server user group for the selected
Distinguished Name, select the Expand arrow beside the Distinguished Name in
the LDAP Distinguished Name Query tree.
Figure 258:Example LDAP server Distinguished Name Query tree
Common Name Identifier (CN)
Distinguished Name (DN)

Expand Arrow
TACACS+ servers
In recent years, remote network access has shifted from terminal access to LAN
access. Users connect to their corporate network (using notebooks or home PCs)
with computers that use complete network connections and have the same level
of access to the corporate network resources as if they were physically in the
office. These connections are made through a remote access server. As remote
access technology has evolved, the need for network access security has
become increasingly important.

01-30007-0203-20090112 429
TACACS+ servers User Authentication
Terminal Access Controller Access-Control System (TACACS+) is a remote

authentication protocol that provides access control for routers, network access
servers, and other networked computing devices via one or more centralized
servers. TACACS+ allows a client to accept a user name and password and send
a query to a TACACS+ authentication server. The server host determines whether
to accept or deny the request and sends a response back that allows or denies
network access to the user. The default TCP port for a TACACS+ server is 49.
To view the list of TACACS+ servers, go to User > Remote > TACACS+.
Figure 259:Example TACACS+ server list
Delete
Edit
Create New Add a new TACACS+ server. The maximum number is 10.
Server The server domain name or IP address of the TACACS+ server.
Authentication Type The supported authentication method. TACACS+ authentication
methods include: Auto, ASCII, PAP, CHAP, and MSCHAP.
Delete icon Delete this TACACS+ server.
Edit icon Edit this TACACS+ server.
Configuring TACACS+ servers

There are several different authentication protocols that TACACS+ can use during
the authentication process:
• ASCII
Machine-independent technique that uses representations of English
characters. Requires user to type a user name and password that are sent in
clear text (unencrypted) and matched with an entry in the user database stored
in ASCII format.
• PAP (password authentication protocol)
Used to authenticate PPP connections. Transmits passwords and other user
information in clear text.
• CHAP (challenge-handshake authentication protocol)
Provides the same functionality as PAP, but more secure as it does not send
the password and other user information over the network to the security
server.
• MS-CHAP (Microsoft challenge-handshake authentication protocol v1)
Microsoft-specific version of CHAP.
The default protocol configuration, Auto, uses PAP, MS-CHAP, and CHAP, in that
order.
To add a new TACACS+ server, go to User > Remote > TACACS+ and select
Create New.

430 01-30007-0203-20090112
User Authentication PKI authentication
Figure 260:TACACS+ server configuration
Name Enter the name of the TACACS+ server.

Server Name/IP Enter the server domain name or IP address of the TACACS+
server.
Server Key Enter the key to access the TACACS+ server. The maximum
number is 16.
Authentication Type Select the authentication type to use for the TACACS+ server.
Selection includes: Auto, ASCII, PAP, CHAP, and MSCHAP. Auto
authenticates using PAP, MSCHAP, and CHAP (in that order).
PKI authentication
Public Key Infrastructure (PKI) authentication utilizes a certificate authentication
library that takes a list of peers, peer groups, and/or user groups and returns
authentication successful or denied notifications. Users only need a valid
certificate for successful authentication—no user name or password are
necessary. Firewall and SSL VPN are the only user groups that can use PKI
authentication.
For more information about certificate authentication, see the FortiGate Certificate
Management User Guide. For information about the detailed PKI configuration
settings available only through the CLI, see the FortiGate CLI Reference.
To view the list of PKI users, go to User > PKI.
Figure 261:Example PKI User list

Delete
Edit

01-30007-0203-20090112 431
PKI authentication User Authentication
Name The name of the PKI user.

Subject The text string that appears in the subject field of the certificate of
the authenticating user.
CA The CA certificate that is used to authenticate this user.
Delete icon Delete this PKI user.
The delete icon is not available if the peer user belongs to a user
group. Remove it from the user group first.
Edit icon Edit this PKI user.
Configuring peer users and peer groups

You can define peer users and peer groups used for authentication in some VPN
configurations and for PKI certificate authentication in firewall policies.
A peer user is a digital certificate holder that can use PKI authentication. Before
using PKI authentication, you must define peer users to include in the user group
that is incorporated into the firewall authentication policy.
To define a peer user, you need:
• a peer user name
• the text from the subject field of the certificate of the authenticating peer user,
or the CA certificate used to authenticate the peer user.
You can add or modify other configuration settings for PKI authentication. For
information about them, see the FortiGate CLI Reference.
Caution: If you use the CLI to create a peer user, Fortinet recommends that you enter a
! value for either subject or ca. If you do not do so, and then open the user record in the web-
based manager, you will be prompted to enter a subject or ca value before you can
continue.
To create a peer user for PKI authentication, go to User > PKI and select Create
New.
Figure 262:PKI user
Name Enter the name of the PKI user.

Subject Enter the text string that appears in the subject field of the
certificate of the authenticating user. This field is optional.
CA Enter the CA certificate that must be used to authenticate this
user. This field is optional.
Note: You must enter a value for at least one of Subject or CA.

432 01-30007-0203-20090112
User Authentication Directory Service servers
You can configure peer user groups only through the CLI. For more information,
see the FortiGate CLI Reference.
Directory Service servers

Windows Active Directory (AD) and Novell eDirectory provide central
authentication services by storing information about network resources across a
domain (a logical group of computers running versions of an operating system) in
a central directory database. Each person who uses computers within a domain
receives his or her own unique account/user name. This account can be assigned
access to resources within the domain. In a domain, the directory resides on
computers that are configured as domain controllers. A domain controller is a
server that manages all security-related features that affect the user/domain
interactions, security centralization, and administrative functions.
FortiGate units use firewall policies to control access to resources based on user
groups configured in the policies. Each FortiGate user group is associated with
one or more Directory Service user groups. When a user logs in to the Windows
or Novell domain, a Fortinet Server Authentication Extension (FSAE) sends the
FortiGate unit the user’s IP address and the names of the Directory Service user
groups to which the user belongs.
The FSAE has two components that you must install on your network:
• The domain controller (DC) agent must be installed on every domain controller
to monitor user logins and send information about them to the collector agent.
• The collector agent must be installed on at least one domain controller to send
the information received from the DC agents to the FortiGate unit.
The FortiGate unit uses this information to maintain a copy of the domain
controller user group database. Because the domain controller authenticates
users, the FortiGate unit does not perform authentication. It recognizes group
members by their IP address.
You must install the Fortinet Server Authentication Extensions (FSAE) on the
network and configure the FortiGate unit to retrieve information from the Directory
Service server. For more information about FSAE, see the FSAE Technical Note.

01-30007-0203-20090112 433
Directory Service servers User Authentication
To view the list of Directory Service servers, go to User > Directory Service.
Figure 263:Example Directory Service server list
Delete
Edit User/Group
Expand Arrow (Directory Service server) Edit

Add User/Group
Domain and groups
Create New Add a new Directory Service server.

Name You can select the Expand arrow beside the server/domain/group
name to display Directory Service domain and group information.
AD Server The name defined for the Directory Service
server.
Domain Domain name imported from the Directory
Service server.
Groups The group names imported from the Directory
Service server.
FSAE Collector IP The IP addresses and TCP ports of up to five FSAE collector
agents that send Directory Service server login information to the
FortiGate unit.
Delete icon Delete this Directory Service server.
Edit icon Edit this Directory Service server.
Add User/Group Add a user or group to the list. You must know the distinguished
name for the user or group.
Edit Users/Group Select users and groups to add to the list.
Configuring a Directory Service server

You need to configure the FortiGate unit to access at least one FSAE collector
agent. You can specify up to five Directory Service servers on which you have
installed a collector agent. If your FSAE collector agent requires authenticated
access, you enter a password for the server. The server name appears in the list
of Directory Service servers when you create user groups. You can also retrieve
Directory Service information directly through an LDAP server instead of through
the FSAE agent.
Note: You can create a redundant configuration on your FortiGate unit if you install a
collector agent on two or more domain controllers. If the current (or first) collector agent
fails, the FortiGate unit switches to the next one in its list of up to five collector agents.

434 01-30007-0203-20090112
User Authentication User groups
To add a new Directory Service server, go to User > Directory Service and select
Create New. You can enter information for up to five collector agents.
Figure 264:Directory Service server configuration
Name Enter the name of the Directory Service server. This name appears in
the list of Directory Service servers when you create user groups.
FSAE Collector Enter the IP address or name of the Directory Service server where
IP/Name this collector agent is installed. The maximum number of characters is
63.
Port Enter the TCP port used for Directory Service. This must be the same
as the FortiGate listening port specified in the FSAE collector agent
configuration.
Password Enter the password for the collector agent. This is required only if you
configured your FSAE collector agent to require authenticated access.
LDAP Server Select the check box and select an LDAP server to access the
Directory Service.
User groups
A user group is a list of user identities. An identity can be:
• a local user account (user name and password) stored on the FortiGate unit
• a local user account with a password stored on a RADIUS, LDAP, or
TACACS+ server
• a RADIUS, LDAP, or TACACS+ server (all identities on the server can
authenticate)
• a user or user group defined on a Directory Service server.
Each user group belongs to one of three types: Firewall, Directory Service or
SSL VPN. For information about each type, see “Firewall user groups” on
page 436, “Directory Service user groups” on page 437, and “SSL VPN user
groups” on page 437. For information on configuring each type of user group, see
“Configuring a user group” on page 438.
In most cases, the FortiGate unit authenticates users by requesting each user
name and password. The FortiGate unit checks local user accounts first. If the unit
does not find a match, it checks the RADIUS, LDAP, or TACACS+ servers that
belong to the user group. Authentication succeeds when the FortiGate unit finds a
matching user name and password.

01-30007-0203-20090112 435
User groups User Authentication
For a Directory Service user group, the Directory Service server authenticates users
when they log in to the network. The FortiGate unit receives the user’s name and
IP address from the FSAE collector agent. For more information about FSAE, see
the FSAE Technical Note.
You can configure user groups to provide authenticated access to:
• Firewall policies that require authentication
See “Adding authentication to firewall policies” on page 302.
• SSL VPNs on the FortiGate unit
See “SSL-VPN firewall policy options” on page 307.
• IPSec VPN Phase 1 configurations for dialup users
See “Creating a new phase 1 configuration” on page 396.
• XAuth for IPSec VPN Phase 1 configurations
See XAUTH in “Defining phase 1 advanced settings” on page 399.
• FortiGate PPTP configuration
See “PPTP Range” on page 411.
• FortiGate L2TP configuration
You can configure this only by using the config vpn l2tp CLI command.
See the FortiGate CLI Reference.
• Administrator login with RADIUS authentication
See “Configuring RADIUS authentication for administrators” on page 198.
• FortiGuard Web Filtering override groups
See “FortiGuard - Web Filter” on page 491.
For each resource that requires authentication, you specify which user groups are
permitted access. You need to determine the number and membership of user
groups appropriate to your authentication needs.
Firewall user groups

A firewall user group provides access to a firewall policy that requires
authentication and lists the user group as one of the allowed groups. The
FortiGate unit requests the group member’s user name and password when the
user attempts to access the resource that the policy protects.
You can also authenticate a user by certificate if you have selected this method.
For more information, see “Adding authentication to firewall policies” on page 302.
A firewall user group can also provide access to an IPSec VPN for dialup users. In
this case, the IPSec VPN phase 1 configuration uses the Accept peer ID in dialup
group peer option. The user’s VPN client is configured with the user name as peer
ID and the password as pre-shared key. The user can connect successfully to the
IPSec VPN only if the user name is a member of the allowed user group and the
password matches the one stored on the FortiGate unit.
Note: A user group cannot be a dialup group if any member is authenticated using a
RADIUS or LDAP server.
For more information, see “Creating a new phase 1 configuration” on page 396.
For information about configuring a Firewall user group, see “Configuring a user
group” on page 438.

436 01-30007-0203-20090112
You can also use a firewall user group to provide override privileges for
FortiGuard web filtering. For more information, see “Configuring FortiGuard
override options for a user group (Firewall or Directory Service)” on page 441. For
detailed information about FortiGuard Web Filter, including the override feature,
see “FortiGuard - Web Filter” on page 491.
Directory Service user groups

On a network, you can configure the FortiGate unit to allow access to members of
Directory Service server user groups who have been authenticated on the
network. The Fortinet Server Authentication Extensions (FSAE) must be installed
on the network domain controllers.
Note: You cannot use Directory Service user groups directly in FortiGate firewall policies.
You must add Directory Service groups to FortiGate user groups. A Directory Service group
should belong to only one FortiGate user group. If you assign it to multiple FortiGate user
groups, the FortiGate unit recognizes only the last user group assignment.
A Directory Service user group provides access to a firewall policy that requires
Directory Service type authentication and lists the user group as one of the
allowed groups. The members of the user group are Directory Service users or
groups that you select from a list that the FortiGate unit receives from the
Directory Service servers that you have configured. See “Directory Service
servers” on page 433.
Note: A Directory Service user group cannot have SSL VPN access.
You can also use a Directory Service user group to provide override privileges for
FortiGuard web filtering. For more information, see “Configuring FortiGuard
override options for a user group (Firewall or Directory Service)” on page 441. For
detailed information about FortiGuard Web Filter, including the override feature,
see “FortiGuard - Web Filter” on page 491.
For information on configuring user groups, see “Configuring a user group” on
page 438.
SSL VPN user groups

An SSL VPN user group provides access to a firewall policy that requires
SSL VPN type authentication and lists the user group as one of the allowed
groups. Local user accounts, LDAP, and RADIUS servers can be members of an
SSL VPN user group. The FortiGate unit requests the user’s user name and
password when the user accesses the SSL VPN web portal. The user group
settings include options for SSL VPN features.
An SSL VPN user group can also provide access to an IPSec VPN for dialup
users. In this case, the IPSec VPN phase 1 configuration uses the Accept peer ID
in dialup group peer option. You configure the user’s VPN client with the user
name as peer ID and the password as pre-shared key. The user can connect
successfully to the IPSec VPN only if the user name is a member of the allowed
user group and the password matches the one stored on the FortiGate unit. For
more information about configuring user groups for IPSec VPN, see “Creating a
new phase 1 configuration” on page 396.

01-30007-0203-20090112 437
Note: A user group cannot be an IPSec dialup group if any member is authenticated using
a RADIUS or LDAP server.
For information on configuring user groups, see “Configuring a user group” on

page 438. For information on configuring additional SSL VPN user group options,
see “Configuring additional SSL VPN user group options” on page 442.
Viewing the User group list

To view the User group list, go to User > User Group.
Figure 265:Example User group list
Delete
Edit
Expand Arrow
Create New Add a new user group.

Group Name The name of the user group. User group names are listed by type of
user group: Firewall, Directory Service and SSL VPN. For more
information, see “Firewall user groups” on page 436, “Directory
Service user groups” on page 437, and “SSL VPN user groups” on
page 437.
Members The Local users, RADIUS servers, LDAP servers, TACACS+ servers,
Directory Service users/user groups or PKI users found in the user
group.
Protection Profile The protection profile associated with this user group.
Delete icon Delete the user group.
You cannot delete a user group that is included in a firewall policy, a
dialup user phase 1 configuration, or a PPTP or L2TP configuration.
Edit icon Edit the membership and options of the group.
Configuring a user group

To add a new user group, go to User > User Group and select Create New.
Note: By default, the FortiGate web-based manager displays Firewall options. The
following figures show the variations that display for each of the user group types: Firewall,
Directory Service, and SSL VPN.
Note: If you try to add LDAP servers or local users to a group configured for administrator
authentication, an “Entry not found” error occurs.

438 01-30007-0203-20090112
Figure 266:User group configuration - Firewall
Right Arrow
Left Arrow
Expand Arrow
Figure 267:User group configuration - Directory Service
Right Arrow
Left Arrow
Expand Arrow

01-30007-0203-20090112 439
Figure 268:User group configuration - SSL VPN
Right Arrow
Left Arrow
Expand Arrow
Name Type or enter the name of the user group.

Type Select the user group type:
Firewall Select this group in any firewall policy that
requires Firewall authentication. See
“Adding authentication to firewall policies”
on page 302 and “Configuring FortiGuard
override options for a user group (Firewall or
Directory Service)” on page 441.
Directory Service Select this group in any firewall policy that
requires Directory Service authentication.
See “Adding authentication to firewall
SSL VPN Select this group in any firewall policy with
Action set to SSL VPN.
Not available in Transparent mode.
See “SSL-VPN firewall policy options” on
page 307.
Protection Profile Available only if Type is Firewall or Directory Service.
Select a protection profile for this user group from the list. To
create a new protection profile, select Create New from this list.
Enter the appropriate information and select OK. For more
information, see “Firewall Protection Profile” on page 365]
Available The list of Local users, RADIUS servers, LDAP servers,
Users/Groups or TACACS+ servers, Directory Service users/user groups, or PKI
Available Members* users that can be added to the user group. To add a member to
this list, select the name and then select the Right Arrow.
* Available Members if user group type is Directory Service.
Members The list of Local users, RADIUS servers, LDAP servers,
TACACS+ servers, Directory Service users/user groups, or PKI
users that belong to the user group. To remove a member, select
the name and then select the Left Arrow.
FortiGuard Web Available only if Type is Firewall or Directory Service.
Filtering Override Configure Web Filtering override capabilities for this group.
See “Configuring FortiGuard override options for a user group
(Firewall or Directory Service)” on page 441.
SSL-VPN User Group Available only if Type is SSL VPN. See “Configuring additional
Options SSL VPN user group options” on page 442.

440 01-30007-0203-20090112
Configuring FortiGuard override options for a user group (Firewall or

Directory Service)
FortiGuard Web Filtering is a managed web filtering solution that sorts hundreds
of millions of web pages into a wide range of categories that users can allow,
block, or monitor. The FortiGate unit accesses the nearest FortiGuard Web
Filtering Service Point to determine the category of a requested web page and
then follows the firewall policy configured for the user or interface. The FortiGuard
Web Filtering override option is available only if the user group is Firewall or
Directory Service.
To configure FortiGuard Web Filtering Override, go to User > User Group and
select the Edit icon for a Firewall or Directory Service user group. Select the
Expand Arrow beside FortiGuard Web Filtering Override. Enter the following
information and select OK.
Figure 269:FortiGuard Web Filtering Override configuration
Expand Arrow
Allow to create Select to allow members of this group to request an override on the
FortiGuard Web FortiGuard Web Filtering Block page. The firewall protection profile
Filtering overrides governing the connection must have FortiGuard overrides enabled.
The protection profile may have more than one user group as an
override group. Members of an override group can authenticate on
the FortiGuard Web Filter Block Override page to access the
blocked site.
For more information, see “FortiGuard - Web Filter” on page 491.
Override Scope The override can apply to just the user who requested the override,
or include others. Select one of the following from the list:
User Only the user.
User Group The user group to which the user belongs.
IP Any user at the user’s IP address.
Profile Any user with the specified protection profile of the
user group.
Ask Authenticating user, who chooses the override
scope.

01-30007-0203-20090112 441
Override Type Select from the list to allow access to:

Directory Only the lowest level directory in the URL.
Domain The entire website domain.
Categories The FortiGuard category.
Ask Authenticating user, who chooses the override
type.
Off-site URLs Select one of the following from the list to set permissions for users
linking to sites off the blocked site:
Allow User can follow links to other sites.
Deny User can follow links only to destinations as
defined by Override Type.
Ask Authenticating user, who chooses whether to
allow use of off-site links.
Override Time Select to set the duration of the override:
Constant Select to set the duration of override in days,
hours, minutes.
Ask Authenticating user, who determines the duration
of override. The duration set is the maximum.
Protection Profiles One protection profile can have several user groups with override
Available permissions. Verification of the user group occurs once the user
name and password are entered. The overrides can still be enabled
or not enabled on a profile-wide basis regardless of the user groups
that have permissions to override the profile.
Permission Granted The list of defined protection profiles applied to user groups that
For have override privileges.
Configuring additional SSL VPN user group options

For detailed instructions about how to configure SSL VPN web-only mode or
tunnel mode operation, see the FortiGate SSL VPN User Guide.
To configure SSL VPN user group options, go to User > User Group and select
the Edit icon for the specific user group. Select the Expand Arrow beside SSL-
VPN User Group Options, enter the information below and select OK.

442 01-30007-0203-20090112
Figure 270:SSL-VPN user group options
Expand Arrow
Enable SSL-VPN Tunnel Select to allow users in this group to connect to the network
Service behind the FortiGate unit using the SSL VPN tunnel.
Allow Split Tunneling Select to allow split tunneling for this group. Split tunneling
ensures that only the traffic for the private network is sent to
the SSL VPN gateway. Internet traffic is sent through the
usual unencrypted route. Not selected as default.
Restrict tunnel IP Type the starting and ending IP address range for this group
range for this group if you want to override a previously defined Tunnel IP range.
For more information, see the FortiGate SSL VPN User
Guide.
Enable Web Application Select the check box to enable the web portal to provide
access to web applications and then select each of the
applications that users in this group are permitted to access.
Host Check
Check FortiClient AV Select to allow the client to connect only if it is running
Installed and Running FortiClient with virus scanning enabled. For more
information about this software, see the Fortinet Technical
Documentation web site.
Check FortiClient FW Select to allow the client to connect only if it is running
Installed and Running FortiClient Host Security FW software. For more information
about this software, see the Fortinet Technical
Documentation web site.
Check for Third Party Select to allow the client to connect only if it running
AV Software FortiClient with firewall enabled. For information about
supported products for Windows XP SP2, see Table 39 on
page 444. For all other Microsoft Windows versions, Norton
(Symantec) AntiVirus or McAfee VirusScan software is
supported.

01-30007-0203-20090112 443
Check for Third Party Select to allow the client to connect only if it has supported
Firewall Software firewall software installed. The software must be installed
and enabled (running).
See Table 39 on page 444 for supported products for
Windows XP SP2. For all other Microsoft Windows versions,
Norton (Symantec) AntiVirus or McAfee VirusScan software
is supported.
Require Virtual Select to allow the user to set up a SSL VPN tunnel-mode
Desktop Connection session using the Virtual Desktop client only. If the user
attempts to use another method, the connection is refused.
Enable Cache Clean Select to remove all temporary Internet files created on the
client computer between user login and logout. This is
executed with a downloaded ActiveX control for Internet
Explorer, and a plugin for Firefox with Windows 2000/
Windows XP.
If the client’s browser cannot install and run the cache
cleaner, the user is denied access to the SSL VPN portal.
Bookmarks Select to allow the SSL VPN user group to use the pre-
configured bookmark group that you select from the list. For
more information, see the FortiGate SSL VPN User Guide.
Redirect URL Select to open a second browser window at this URL when
the SSL VPN web portal page opens. The web server for
this URL must reside on the private network behind the
FortiGate unit.
You can modify the SSL VPN web portal login page. For
more information, see “Changing the SSL-VPN login
message” on page 192.
Customize portal message Type or edit a custom web portal home page caption for this
for this group group.
Table 39: AV/Firewall supported product detection

Product AV Firewall
Norton Internet Security 2006 Y Y
Trend Micro PC-cillin Y Y
McAfee Y Y
Sophos Anti-Virus Y N
Panda Platinum 2006 Internet Y Y

Security
F-Secure Y Y
Secure Resolutions Y Y
Cat Computer services Y Y
AhnLab Y Y
Kaspersky Y Y
ZoneAlarm Y Y

444 01-30007-0203-20090112
User Authentication Authentication settings
Authentication settings
You can define settings for user authentication, including authentication timeout,
supported protocols, and authentication certificates.
Authentication timeout controls how long an authenticated firewall connection can
be idle before the user must authenticate again.
When user authentication is enabled on a firewall policy, the authentication
challenge is normally issued for any of the four protocols (depending on the
connection protocol):
• HTTP (can also be set to redirect to HTTPS)
• HTTPS
• FTP
• Telnet.
The selections made in the Protocol Support list of the Authentication Settings
screen control which protocols support the authentication challenge. Users must
connect with a supported protocol first so they can subsequently connect with
other protocols. If HTTPS is selected as a method of protocol support, it allows the
user to authenticate with a customized Local certificate.
When you enable user authentication on a firewall policy, the firewall policy user
will be challenged to authenticate. For user ID and password authentication, users
must provide their user names and passwords. For certificate authentication
(HTTPS or HTTP redirected to HTTPS only), you can install customized
certificates on the FortiGate unit and the users can also have customized
certificates installed on their browsers. Otherwise, users will see a warning
message and have to accept a default FortiGate certificate.
Note: When you use certificate authentication, if you do not specify any certificate when
you create the firewall policy, the global settings will be used. If you specify a certificate, the
per-policy setting will overwrite the global setting. For information about how to use
certificate authentication, see FortiGate Certificate Management User Guide.
To configure authentication settings, go to User > Authentication.
Figure 271:Authentication Settings
Authentication Timeout Enter a length of time in minutes, from 1 to 480.

Authentication Timeout controls how long an authenticated
firewall connection can be idle before the user must
authenticate again. The default value is 30.
Protocol Support Select the protocols to challenge during firewall user
authentication.

01-30007-0203-20090112 445
Authentication settings User Authentication
Certificate If using HTTPS protocol support, select the Local certificate

to use for authentication. Available only if HTTPS protocol
support is selected.
Apply Apply selections for user Authentication Settings.

446 01-30007-0203-20090112
AntiVirus Order of operations
AntiVirus
This section describes how to configure the antivirus options associated with
firewall protection profiles.
If you enable virtual domains (VDOMs) on the FortiGate unit, most antivirus
options are configured separately for each virtual domain. However, the
quarantine, the virus list and the grayware list are part of the global configuration.
Only administrators with global access can configure and manage the quarantine,
view the virus list, and configure the grayware list. For details, see “Using virtual
• Order of operations
• Antivirus tasks
• Antivirus settings and controls
• File Filter
• Quarantine
• Viewing the virus list
• Viewing and configuring the grayware list
• Antivirus CLI configuration
Order of operations
Antivirus scanning function includes various modules and engines that perform
separate tasks. The FortiGate unit performs antivirus processing in the following
order:
• File size
• File filter
• Virus scan
• Grayware
• Heuristics
If a file fails any of the tasks of the antivirus scan, no further scans are performed.
For example, if the file “fakefile.EXE” is recognized as a blocked pattern, the
FortiGate unit will send the end user a replacement message and the file will be
deleted or quarantined. The virus scan, grayware, heuristics, and file type scans
will not be performed as the file is already been determined to be a threat and has
been dealt with.
Note: File filter includes file pattern and file type scans which are applied at different stages
in the antivirus process.

01-30007-0203-20090112 447
Antivirus tasks AntiVirus
Figure 272:Order of operation

Protection profile > Oversize file/Email = Pass
Pass Block
FTP/NNTTP/SMTP/POP3/IMAP
after Web Filter spam checking
Oversize:
Buffered File Pattern: Virus Scan:
Size bigger
contents Blocked file? Infected?
than threshold?
Protection profile > Oversize file/Email = Block
Block Grayware?
Further checking decided

by MIME type detection Heuristic scan
Content File Type:
Pass (enable through
Inspection Blocked file type?
HTTP only CLI)
Antivirus tasks
The antivirus tasks work in sequence to efficiently scan incoming files and offer
your network unparalleled antivirus protection. The first four tasks have specific
functions, the fourth, the heuristics, is to cover any new, previously unknown, virus
threats. To ensure that your system is providing the most protection available, all
virus definitions and signatures are updated regularly through the FortiGuard
antivirus services. The tasks will be discussed in the order that they are applied
followed by FortiGuard antivirus.
File size
This task checks if files and email messages exceed configured thresholds. It is
enabled by setting the Oversized File/Email option under Firewall > Protection
Profile > Antivirus to Pass.
For more information, see “Anti-Virus options” on page 367.
File pattern
Once a file is accepted, the FortiGate unit applies the file pattern recognition filter.
The FortiGate unit will check the file against the file pattern setting you have
configured. If the file is a blocked pattern, “.EXE” for example, then it is stopped
and a replacement message is sent to the end user. No other levels of protections
are applied. If the file is not a blocked pattern the next level of protection is
applied.
Virus scan
If the file passes the file pattern scan, it will have a virus scan applied to it. The
virus definitions are keep up to date through the FortiNet Distribution Network.
The list is updated on a regular basis so you do not have to wait for a firmware
upgrade. For more information on updating virus definitions, see “FortiGuard
antivirus” on page 449.

448 01-30007-0203-20090112
AntiVirus Antivirus settings and controls
Grayware
Once past the virus scan, the incoming file will be checked for grayware.
Grayware configurations can be turned on and off as required and are kept up to
date in the same manner as the antivirus definitions. For more information on
configuring grayware please see “Viewing and configuring the grayware list” on
page 459.
Heuristics
After an incoming file has passed the grayware scan, it is subjected to the
heuristics scan. The FortiGate heuristic antivirus engine, if enabled, performs
tests on the file to detect virus-like behavior or known virus indicators. In this way,
heuristic scanning may detect new viruses, but may also produce some false
positive results.
Note: Heuristics is configurable only through the CLI. See the FortiGate CLI Reference.
File type
Once a file passes the heuristic scan, the FortiGate unit applies the file type
recognition filter. The FortiGate unit will check the file against the file type setting
you have configured. If the file is a blocked type, then it is stopped and a
replacement message is sent to the end user. No other levels of protections are
applied. If the file is not a blocked type, the next level of protection is applied.
FortiGuard antivirus
FortiGuard antivirus services are an excellent resource and include automatic
updates of virus and IPS (attack) engines and definitions, as well as the local
spam DNSBL, through the FortiGuard Distribution Network (FDN). The
FortiGuard Center also provides the FortiGuard antivirus virus and attack
encyclopedia and the FortiGuard Bulletin. Visit the Fortinet Knowledge Center for
details and a link to the FortiGuard Center.
The connection between the FortiGate unit and FortiGuard Center is configured in
System > Maintenance > FortiGuard Center. See “Configuring the FortiGate
unit for FDN and FortiGuard subscription services” on page 243 for more
information.
Antivirus settings and controls

While antivirus settings are configured for system-wide use, specific settings can
be implemented on a per profile basis. Table 40 compares antivirus options in
protection profiles and the antivirus menu.
Note: If virtual domains are enabled, you configure antivirus file filtering and antivirus
settings in protection profiles separately for each virtual domain. Antivirus quarantine and
grayware settings are part of the global configuration.

01-30007-0203-20090112 449
File Filter AntiVirus
Table 40: Antivirus and Protection Profile antivirus configuration
Protection Profile antivirus options Antivirus setting

Virus Scan AntiVirus > Config > Virus List
Enable or disable virus scanning for each View a read-only list of current viruses.
protocol (HTTP, FTP, IMAP, POP3, SMTP,
IM).
File Filter AntiVirus > File Filter
Enable or disable file pattern and file type Configure file patterns and types to block
handling for each protocol. or allow files. Patterns and types can also
be individually enabled or disabled.
Quarantine AntiVirus > Quarantine
Enable or disable quarantining for each View and sort the list of quarantined files,
protocol. Quarantine is only available on units configure file patterns to upload
with a local disk, or with a configured automatically to Fortinet for analysis, and
FortiAnalyzer unit. configure quarantining options in
AntiVirus.
Pass fragmented email messages.
Enable or disable passing fragmented email
messages. Fragmented email messages
cannot be scanned for viruses.
Comfort Clients
Enable or disable for HTTP and FTP traffic.
Set the interval and byte amount to trigger
client comforting.
Oversized file/email
Configure the FortiGate unit to block or pass
oversized files and email messages for each
protocol. Set the size thresholds for files and
email messages for each protocol in
AntiVirus.
AntiVirus > Config > Grayware
Enable or disable blocking of Grayware
by category.
Add signature to outgoing email messages
Create and enable a signature to append to
outgoing email messages (SMTP only).
File Filter
Configure the FortiGate file filter to block files by:
• File pattern: Files can be blocked by name, extension, or any other pattern.
File pattern blocking provides the flexibility to block potentially harmful content.
File pattern entries are not case sensitive. For example, adding *.exe to the
file pattern list also blocks any files ending in .EXE.
In addition to the built-in patterns, you can specify more file patterns to block.
For details, see “Configuring the file filter list” on page 454.

450 01-30007-0203-20090112
AntiVirus File Filter
• File type: In addition to file pattern (file name) checking, you can also configure
the FortiGate unit to analyze the file and determine the file type of the files,
regardless of the file name. For details about supported file types, see “Built-in
patterns and supported file types” on page 451.
For standard operation, you can choose to disable File Filter in the Protection
Profile, and enable it temporarily to block specific threats as they occur.
The FortiGate unit can take any of the following three actions towards the files that
match a configured file pattern or type:
• Allow: the file will be allowed to pass.
• Block: the file will be blocked and a replacement messages will be sent to the
user. If both File Filter and Virus Scan are enabled, the FortiGate unit blocks
files that match enabled file filter and does not scan these files for viruses.
The FortiGate unit also writes a message to the virus log and sends an alert email
message if configured to do so.
Files are compared to the enabled file patterns and then the file types from top to
bottom. If a file does not match any specified patterns or types, it is passed along
to antivirus scanning (if enabled). In effect, files are passed if not explicitly
blocked.
Using the allow action, this behavior can be reversed with all files being blocked
unless explicitly passed. Simply enter all the file patterns or types to be passed
with the allow attribute. At the end of the list, add an all-inclusive wildcard (*.*) with
a block action. Allowed files continue to antivirus scanning (if enabled) while files
not matching any allowed patterns are blocked by the wildcard at the end.
Built-in patterns and supported file types

The FortiGate unit is preconfigured with a default list of file patterns:
• executable files (*.bat, *.com, and *.exe)
• compressed or archive files (*.gz, *.rar, *.tar, *.tgz, and *.zip)
• dynamic link libraries (*.dll)
• HTML application (*.hta)
• Microsoft Office files (*.doc, *.ppt, *.xl?)
• Microsoft Works files (*.wps)
• Visual Basic files (*.vb?)
• screen saver files (*.scr)
• program information files (*.pif)
• control panel files (*.cpl)

01-30007-0203-20090112 451
File Filter AntiVirus
The FortiGate unit can take actions against the following file types:
Table 41: Supported file types
exe bat mime javascript html hta msoffice elf

gzip rar tar lzh upx zip cab bzip2
bzip activemime hlp arj base64 binhex uue fsg
aspack jad class cod msc petite sis prc
unknown ignored
Note: The “unknown” type is any file type that is not listed in the table. The “ignored” type is
the traffic the FortiGate unit typically does not scan. This includes primarily streaming audio
and video.
Viewing the file filter list catalog

You can add multiple file filter lists and then select the best file filter list for each
protection profile. To view the file filter list catalog, go to AntiVirus > File Filter. To
view any individual file filter list, select the edit icon for the list you want to see.
Figure 273:Sample file pattern list catalog
Note: The default file pattern list catalog is called builtin-patterns.
Create New Select Create New to add a new file filter list to the catalog.
Name The available file filter lists.
# Entries The number of file patterns or file types in each file filter list.
Profiles The protection profiles each file filter list has been applied to.
Comments Optional description of each file filter list.
Delete icon Select to remove the file filter list from the catalog. The delete icon is
only available if the file filter list is not selected in any protection
profiles.
Edit icon Select to edit the file filter, its name and comment.
The file filter list will be used in protection profiles. For more information, see “Anti-
Virus options” on page 367.

452 01-30007-0203-20090112
AntiVirus File Filter
Creating a new file filter list

To add a file pattern list to the file pattern list catalog, go to AntiVirus > File Filter
Figure 274:New File Filter List dialog box
Name Enter the name of the new list.

Comment Enter a comment to describe the list, if required.
Viewing the file filter list

To view the file filter list, go to AntiVirus > File Filter and select the edit icon of
the file filter list you want to view.
Figure 275:Sample file filter list
The file filter list has the following icons and features:
Name File filter list name. To change the name, edit text in the name field
and select OK.
Comment Optional comment. To add or edit comment, enter text in comment
field and select OK.
OK If you make changes to the list name or comments, select OK to save
the changes.
Create New Select Create New to add a new file pattern or type to the file filter list.
Filter The current list of file patterns and types.
Action Files matching the file patterns and types can be set to block, allow, or
intercept. For information about actions, see “File Filter” on page 450.
Enable Clear the checkbox to disable the file pattern or type.
Delete icon Select to remove the file pattern or type from the list.
Edit icon Select to edit the file pattern/type and action.
Move To icon Select to move the file pattern or type to any position in the list.

01-30007-0203-20090112 453
Quarantine AntiVirus
Configuring the file filter list

For file patterns, you can add a maximum of 5000 patterns to a list. For file types,
you can only select from the supported types.
Figure 276:New file filter
To add a file pattern or type go to AntiVirus > File Filter. Select the Edit icon for a
file filter catalog. Select Create New.
Filter Type Select File Name Pattern if you want to add a file pattern; select
File Type and then select a file type from the supported file type
list.
Pattern Enter the file pattern. The file pattern can be an exact file name or
can include wildcards. The file pattern can be 80 characters long.
File Type Select a file type from the list. For information about supported file
types, see “Built-in patterns and supported file types” on
page 451.
Action Select an action from the drop down list: Block, Allow, or Intercept.
For more information about actions, see “File Filter” on page 450.
Enable Select to enable the pattern.
Quarantine
FortiGate units with a local disk can quarantine blocked and infected files. View
the file name and status information about the file in the quarantined file list.
Submit specific files and add file patterns to the AutoSubmit list so they will
automatically be uploaded to Fortinet for analysis.
FortiGate units without a local disk can quarantine blocked and infected files to a
FortiAnalyzer unit. Files stored on the FortiAnalyzer can be retrieved for viewing.
To configure the FortiAnalyzer unit, go to Log & Report > Log Config > Log
Setting.
File quarantine configuration involves several steps.
To configure and enable file quarantine

1 Go to AntiVirus > Quarantine > Config to configure the quarantine service and
destination. For details, see “Configuring quarantine options” on page 457.
2 Go to Firewall > Protection Profile to enable quarantine for required protocols in
the protection profiles. For details, see “Configuring a protection profile” on
page 367.
3 Go to Firewall > Policy and use the protection profile in a policy.

454 01-30007-0203-20090112
AntiVirus Quarantine
Viewing the Quarantined Files list

The Quarantined Files list displays information about each file quarantined
because of virus infection or file blocking. Sort the files by file name, date, service,
status, duplicate count (DC), or time to live (TTL). Filter the list to view only
quarantined files with a specific status or from a specific service.
To view the Quarantined Files list, go to AntiVirus > Quarantine > Quarantined
Files.
Figure 277:Quarantined files list
The quarantined files list has the following features and displays the following
information about each quarantined file:
Source Either FortiAnalyzer or Local disk, depending where you configure to

store the quarantined files.
Sort by Sort the list. Choose from: status, service, file name, date, TTL, or
duplicate count. Select Apply to complete the sort.
Filter Filter the list. Choose from status (infected, blocked, or heuristics) or
service (IMAP, POP3, SMTP, FTP, HTTP, IM, or NNTP). See “Antivirus
CLI configuration” on page 461.
Apply Select to apply the sorting and filtering selections to the quarantined
files list.
Delete Select to delete the selected files.
Page Controls Use the controls to page through the list. For details, see “Using page
controls on web-based manager lists” on page 61.
Remove All Removes all quarantined files from the local hard disk.
Entries This icon only appears when the files are quarantined to the hard disk.
File Name The processed file name of the quarantined file. When a file is
quarantined, all spaces are removed from the file name, and a 32-bit
checksum is performed on the file. The checksum appears in the
replacement message but not in the quarantined file. The file is stored
on the FortiGate hard disk with the following naming convention:
<32bit_CRC>.<processed_filename>
For example, a file named Over Size.exe is stored as
3fc155d2.oversize.exe.
Date The date and time the file was quarantined, in the format dd/mm/yyyy
hh:mm. This value indicates the time that the first file was quarantined
if the duplicate count increases.

01-30007-0203-20090112 455
Quarantine AntiVirus
Service The service from which the file was quarantined (HTTP, FTP, IMAP,
POP3, SMTP, IM, or NNTP).
Status The reason the file was quarantined: infected, heuristics, or blocked.
Status Specific information related to the status, for example, “File is infected
Description with “W32/Klez.h”” or “File was stopped by file block pattern.”
DC Duplicate count. A count of how many duplicates of the same file were
quarantined. A rapidly increasing number can indicate a virus outbreak.
TTL Time to live in the format hh:mm. When the TTL elapses, the FortiGate
unit labels the file as EXP under the TTL heading. In the case of
duplicate files, each duplicate found refreshes the TTL.
The TTL information is not available if the files are quarantined on a
FortiAnalyzer unit.
Upload status Y indicates the file has been uploaded to Fortinet for analysis, N
indicates the file has not been uploaded.
This option is available only if the FortiGate unit has a local hard disk.
Download icon Select to download the corresponding file in its original format.
Submit icon Select to upload a suspicious file to Fortinet for analysis.
Note: Duplicates of files (based on the checksum) are not stored, only counted. The TTL
value and the duplicate count are updated each time a duplicate of a file is found.
Viewing the AutoSubmit list

If the FortiGate unit has a local hard disk, you can configure the FortiGate unit to
upload suspicious files automatically to Fortinet for analysis. You can add file
patterns to the AutoSubmit list using wildcard characters (* or ?). File patterns are
applied for AutoSubmit regardless of file blocking settings.
Upload files to Fortinet based on status (blocked or heuristics), or submit
individual files directly from the quarantined files list. The FortiGate unit uses
encrypted email to autosubmit files to an SMTP server through port 25.
To view the AutoSubmit list, go to AntiVirus > Quarantine > AutoSubmit.
The autosubmit feature is not available on the FortiGate models without a local
hard disk.
Figure 278:Sample AutoSubmit list
AutoSubmit list has the following icons and features:
Create New Select to add a new file pattern to the AutoSubmit list.
File Pattern The current list of file patterns that will be automatically uploaded.
Create a pattern by using ? or * wildcard characters. Enable the
check box to enable all file patterns in the list.
Delete icon Select to remove the entry from the list.
Edit icon Select to edit the following information: File Pattern and Enable.

456 01-30007-0203-20090112
AntiVirus Quarantine
Configuring the AutoSubmit list

To add a file pattern to the AutoSubmit list, go to AntiVirus > Quarantine >
AutoSubmit. Note that the autosubmit feature is available only if your FortiGate
unit has a local hard disk.
Figure 279:New File Pattern dialog box
File Pattern Enter the file pattern or file name to be upload automatically to
Fortinet.
Enable Select to enable the file pattern
Note: To enable automatic uploading of the configured file patterns, go to AntiVirus >
Quarantine > Config, select Enable AutoSubmit, and select Use File Pattern.
Configuring quarantine options

Go to AntiVirus > Quarantine > Config to set quarantine configuration options,
such as whether to quarantine blocked or infected files and from which service.
Figure 280:Quarantine Configuration (FortiGate unit with local disk)

01-30007-0203-20090112 457
Viewing the virus list AntiVirus
Quarantine configuration has the following options:
Options Quarantine Infected Files: Select the protocols from which to quarantine
infected files identified by antivirus scanning.
Quarantine Suspicious Files: Select the protocols from which to
quarantine suspicious files identified by heuristics.
Quarantine Blocked Files. Select the protocols from which to quarantine
blocked files identified by antivirus file filtering. The Quarantine Blocked
Files option is not available for IM because a file name is blocked before
downloading and cannot be quarantined.
Age limit The time limit in hours for which to keep files in quarantine. The age limit
is used to formulate the value in the TTL column of the quarantined files
list. When the limit is reached, the TTL column displays EXP. and the file
is deleted (although a record is maintained in the quarantined files list).
Entering an age limit of 0 (zero) means files are stored on disk
indefinitely, depending on low disk space action.
Max filesize to The maximum size of quarantined files in MB. Setting the maximum file
quarantine size too large may affect performance.
Low disk space Select the action to take when the local disk is full: overwrite the oldest
file or drop the newest file.
FortiAnalyzer Select to enable storage of blocked and quarantined files on a
FortiAnalyzer unit. See “Log&Report” on page 525 for more information
about configuring a FortiAnalyzer unit.
Enable Enable AutoSubmit: enables the AutoSubmit feature. Select one or both
AutoSubmit of the options below.
Use file pattern: Enables the automatic upload of files matching the file
patterns in the AutoSubmit list.
Use file status: Enables the automatic upload of quarantined files based
on their status. Select either Heuristics or Block Pattern.
Heuristics is configurable through the CLI only. See “Antivirus CLI
Apply Select to save the configuration.
Viewing the virus list

The virus list displays an alphabetical list of the current FortiGuard virus definitions
(also called AV definitions) installed on the FortiGate unit. The FortiGate unit uses
the virus definitions to detect and remove viruses, worms, trojans, and other
threats from content as it passes through the FortiGate unit. View the entire list or
parts of the list by selecting the number or alphabet ranges.
To view the virus list, go to AntiVirus > Config > Virus List.
The FortiGuard virus definitions list is updated every time the FortiGate unit
receives a new version of the FortiGuard AV definitions.
The FortiGuard Center Virus Encyclopedia contains detailed descriptions of the
viruses, worms, trojans, and other threats that can be detected and removed by
your FortiGate unit using the information in the FortiGuard virus definitions.

458 01-30007-0203-20090112
AntiVirus Viewing and configuring the grayware list
Figure 281:Virus list (partial)
Usually the FortiGuard AV definitions are updated automatically from the

FortiGuard Distribution Network (FDN). Go to System > Maintenance >
FortiGuard Center to configure automatic AV definition updates from the FDN.
You can also update the AV definitions manually from the system dashboard (go
to System > Status).
In addition to the wildlist AV database, which contains actively spreading viruses,
some newer FortiGate models are also equipped with an extended AV database,
which contains viruses that are not considered to be actively spreading. If
required, you can enable this feature to allow the FortiGate unit to scan for non-
active viruses. For details, see “Anti-Virus options” on page 367.
Viewing and configuring the grayware list

Grayware programs are unsolicited commercial software programs that get
installed on computers, often without the user’s consent or knowledge. Grayware
programs are generally considered an annoyance, but these programs can cause
system performance problems or be used for malicious ends.
The FortiGate unit scans for known grayware executable programs in each
enabled category. The category list and contents are added or updated whenever
the FortiGate unit receives a virus update package. New categories may be
added at any time and will be loaded with the virus updates. By default, all new
categories are disabled. Grayware is enabled in a protection profile when Virus
Scan is enabled.
Grayware categories are populated with known executable files. Each time the
FortiGate unit receives a virus and attack definitions update, the grayware
categories and contents are updated.
To view the grayware list, go to AntiVirus > Config > Grayware.

01-30007-0203-20090112 459
Viewing and configuring the grayware list AntiVirus
Figure 282:Sample grayware options
Enabling a grayware category blocks all files listed in the category. The categories
may change or expand when the FortiGate unit receives updates. You can choose
to enable the following grayware categories:
Adware Block adware programs. Adware is usually embedded in freeware

programs and causes ads to pop up whenever the program is
opened or used.
BHO Block browser helper objects. BHOs are DLL files that are often
installed as part of a software package so the software can control
the behavior of Internet Explorer 4.x and later. Not all BHOs are
malicious, but the potential exists to track surfing habits and gather
other information.
Dial Block dialer programs. Dialers allow others to use the PC modem
to call premium numbers or make long distance calls.
Download Block download programs. Download components are usually run
at Windows startup and are designed to install or download other
software, especially advertising and dial software.
Game Block games. Games are usually joke or nuisance games that you
may want to block from network users.
HackerTool Block hacker tools.
Hijacker Block browser hijacking programs. Browser hijacking occurs when
a ‘spyware’ type program changes web browser settings, including
favorites or bookmarks, start pages, and menu options.
Joke Block joke programs. Joke programs can include custom cursors
and programs that appear to affect the system.
Keylog Block keylogger programs. Keylogger programs can record every
keystroke made on a keyboard including passwords, chat, and
instant messages.
Misc Block any programs included in the miscellaneous grayware
category.
NMT Block network management tools. Network management tools can
be installed and used maliciously to change settings and disrupt
network security.
P2P Block peer to peer communications programs. P2P, while a
legitimate protocol, is synonymous with file sharing programs that
are used to swap music, movies, and other files, often illegally.

460 01-30007-0203-20090112
AntiVirus Antivirus CLI configuration
Plugin Block browser plugins. Browser plugins can often be harmless

Internet browsing tools that are installed and operate directly from
the browser window. Some toolbars and plugins can attempt to
control or record and send browsing preferences.
RAT Block remote administration tools. Remote administration tools
allow outside users to remotely change and monitor a computer on
a network.
Spy Block spyware programs. Spyware, like adware, is often included
with freeware. Spyware is a tracking and analysis program that can
report your activities, such as web browsing habits, to the
advertiser’s web site where it may be recorded and analyzed.
Toolbar Block custom toolbars. While some toolbars are harmless,
spyware developers can use these toolbars to monitor web habits
and send information back to the developer.
Antivirus CLI configuration

This section describes the CLI commands that extend features available through
the web-based manager. For complete descriptions and examples of how to
enable additional features through CLI commands, see the FortiGate CLI
Reference.
system global optimize

The optimize feature configures CPU settings to ensure efficient operation of the
FortiGate unit for either antivirus scanning or straight throughput traffic. When
optimize is set to antivirus, the FortiGate unit uses symmetric multiprocessing to
spread the antivirus tasks to several CPUs, making scanning faster.
This feature is available on models numbered 1000 and higher.
For more information, see the Antivirus failopen and optimization Fortinet
Knowledge Center article.
config antivirus heuristic

The FortiGate heuristic antivirus engine performs tests on files to detect virus-like
behavior or known virus indicators. Heuristic scanning is performed last, after file
blocking and virus scanning have found no matches. In this way, heuristic
scanning may detect new viruses, but may also produce some false positive
results.
The heuristic engine is disabled by default. You need to enable it to pass
suspected files to the recipient and send a copy to quarantine. Once enabled in
the CLI, heuristic scanning is enabled in a protection profile when Virus Scan is
enabled.
Use the heuristic command to change the heuristic scanning mode.
config antivirus quarantine

The quarantine command also allows configuration of heuristic related settings.
This feature is available on models numbered 200 and higher.

01-30007-0203-20090112 461
Antivirus CLI configuration AntiVirus
config antivirus service <service_name>

Use this command to configure how the FortiGate unit handles antivirus scanning
of large files in HTTP, FTP, IM, POP3, IMAP, or SMTP traffic, and what ports the
FortiGate unit scans for the service.

462 01-30007-0203-20090112
Intrusion Protection About intrusion protection
Intrusion Protection
The FortiGate Intrusion Protection system combines signature and anomaly
detection and prevention with low latency and excellent reliability. With intrusion
Protection, you can create multiple IPS sensors, each containing a complete
configuration based on signatures. Then, you can apply any IPS sensor to each
protection profile. You can also create DoS sensors to examine traffic for
anomaly-based attacks.
This section describes how to configure the FortiGate Intrusion Protection
settings. For more information about Intrusion Protection, see the FortiGate
Intrusion Protection System (IPS) Guide.
If you enable virtual domains (VDOMs) on the FortiGate unit, intrusion protection
is configured separately for each virtual domain. For details, see “Using virtual
• About intrusion protection
• Signatures
• Custom signatures
• Protocol decoders
• IPS sensors
• DoS sensors
• Intrusion protection CLI configuration
About intrusion protection

The FortiGate unit can log suspicious traffic, send alert email messages to system
administrators, and log, pass, or block suspicious packets or sessions. You can
adjust the DoS sensor anomaly thresholds to work best with the normal traffic on
the protected networks. You can also create custom signatures to tailor the
FortiGate Intrusion Protection system to your network environment.
The FortiGate Intrusion Protection system matches network traffic against
patterns contained in attack signatures. Attack signatures reliably protect your
network from known attacks. Fortinet’s FortiGuard infrastructure ensures the rapid
identification of new threats and the development of new attack signatures.
FortiGuard services provide automatic updates of virus and intrusion protection
(attack) engines and definitions to FortiGate customers through the FortiGuard
Distribution Network (FDN). The FortiGuard Center also provides the FortiGuard
virus and attack encyclopedia and the FortiGuard Bulletin. Visit the Fortinet
Knowledge Center for details and a link to the FortiGuard Center.
For more information about configuring the connection between the FortiGate unit
and FortiGuard see “Configuring the FortiGate unit for FDN and FortiGuard
subscription services” on page 243.

01-30007-0203-20090112 463
About intrusion protection Intrusion Protection
Using Intrusion Protection, you can configure the FortiGate unit to check for and
automatically download updated attack definition files containing the latest
signatures, or download the updated attack definition file manually. Alternately,
you can configure the FortiGate unit to allow push updates of the latest attack
definition files as soon as they are available from the FortiGuard Distribution
Network.
You can also create custom attack signatures for the FortiGate unit to use in
addition to an extensive list of predefined attack signatures.
Whenever the Intrusion Protection system detects or prevents an attack, it
generates an attack log message. You can configure the FortiGate unit to add the
message to the attack log and send an alert email to administrators, as well as
schedule how often it should send this alert email. You can also reduce the
number of log messages and alerts by disabling signatures for attacks that will not
affect your network. For example, you do not need to enable signatures to detect
web attacks when there is no web server to protect.
You can also use the packet logging feature to analyze packets for forensics and
false positive detection.
For more information about FortiGate logging and alert email, see “Log&Report”
on page 525.
Intrusion Protection settings and controls

You can configure the Intrusion Protection system and then select IPS sensors in
individual firewall protection profiles.
For information about creating IPS sensors, see “Configuring IPS sensors” on
page 470. For information about accessing and modifying the protection profile
IPS sensor selection, see “IPS options” on page 375. For information about
creating DoS Sensors, see “DoS sensors” on page 475.
Note: If virtual domains are enabled on the FortiGate unit, the Intrusion Protection settings
are configured separately in each VDOM. All sensors and custom signatures will appear
only in the VDOM in which they were created.
When to use Intrusion Protection

Intrusion Protection is best for large networks or for networks protecting highly
sensitive information. Using IPS effectively requires monitoring and analysis of the
attack logs to determine the nature and threat level of an attack. An administrator
can adjust the threshold levels to ensure a balance between performance and
intrusion prevention.
Small businesses and home offices without network administrators may be
overrun with attack log messages and not have the networking background
required to configure the thresholds and other IPS settings.
However, the other protection features in the FortiGate unit, such as antivirus
(including grayware), spam filters, and web filters offer excellent protection for all
networks.

464 01-30007-0203-20090112
Intrusion Protection Signatures
Signatures
The FortiGate Intrusion Protection system can use signatures once you have
grouped the required ones in an IPS sensor, and then selected the IPS sensor in
the protection profile. If required, you can override the default settings of the
signatures specified in an IPS sensor. The FortiGate unit provides a number of
pre-built IPS sensors, but you should check their settings before using them, to
ensure they meet your network requirements.
By using only the signatures you require, you can improve system performance
and reduce the number of log messages and alert email messages the IPS
sensor generates. For example, if the FortiGate unit is not protecting a web
server, do not include any web server signatures.
Note: Some default protection profiles include IPS Sensors that use all the available
signatures. By using these default settings, you may be slowing down the overall
performance of the FortiGate unit. By creating IPS sensors with only the signatures your
network requires, you can ensure maximum performance as well as maximum protection.
Viewing the predefined signature list

The predefined signature list displays the characteristics of each signature. Use
these characteristics to define which signatures are included in your IPS sensors.
The signature list also displays the default action, the default logging status, and
whether the signature is enabled by default.
To view the predefined signature list, go to Intrusion Protection > Signature >
Predefined. You can also use filters to display the signatures you want to view.
For more information, see “Using display filters” on page 466.
Figure 283:Predefined signature list

Current page Filter
By default, the signatures are sorted by name. To sort the table by another
column, select the header of the column to sort by.
Current Page The current page number of list items that are displayed. Select the left
and right arrows to display the first, previous, next or last page of
signatures.
Column Select to customize the signature information displayed in the table. You
Settings can also readjust the column order.

01-30007-0203-20090112 465
Signatures Intrusion Protection
Clear All Filters If you have applied filtering to the predefined signature list display, select
this option to clear all filters and display all the signatures.
Name The name of the signature, linked to the FortiGuard Center web page
about the signature.
Severity The severity rating of the signature. The severity levels, from lowest to
highest, are Information, Low, Medium, High, and Critical.
Target The target of the signature: servers, clients, or both.
Protocols The protocol the signature applies to.
OS The operating system the signature applies to.
Applications The applications the signature applies to.
Enable The default status of the signature. A green circle indicates the signature
is enabled. A gray circle indicates the signature is not enabled.
Action The default action for the signature:
• Pass allows the traffic to continue without any modification.
• Drop prevents the traffic with detected signatures from reaching its
destination.
If Logging is enabled, the action appears in the status field of the log
message generated by the signature.
ID A unique numeric identifier for the signature.
Logging The default logging behavior of the signature. A green circle indicates
logging is enabled. A gray circle indicates logging is disabled.
Group A functional group that is assigned to that signature. This group is only
for reference and cannot be used to define filters.
Packet Log The default packet log status of the signature. A green circle indicates
that the packet log is enabled. A gray circle indicates that the packet log
is not enabled.
Revision The revision level of the signature. If the signature is updated, the
revision number will be incremented.
Note: To determine what effect IPS protection would have on your network traffic, you can
enable the required signatures, set the action to pass, and enable logging. Traffic will not be
interrupted, but you will be able to examine in detail which signatures were detected.
Using display filters

By default, all the predefined signatures are displayed. You can apply filters to
display only the signatures you want to view. For example, if you want to view only
the Windows signatures, you can use the OS status filter. For more information,
see “Adding filters to web-based manager lists” on page 58.
To apply filters to the predefined signature list

1 Go to Intrusion Protection > Signature > Predefined.
2 Select the filter icon beside any column name in the signature table.
3 In Edit Filters, specify the filtering criteria. The criteria will vary depending on the
column name.
4 Select the Enable check box.
5 Select OK.

466 01-30007-0203-20090112
Intrusion Protection Custom signatures
Custom signatures
Custom signatures provide the power and flexibility to customize the FortiGate
Intrusion Protection system for diverse network environments. The FortiGate
predefined signatures represent common attacks. If you use an unusual or
specialized application or an uncommon platform, you can add custom signatures
based on the security alerts released by the application and platform vendors.
You can also create custom signatures to help you block P2P protocols.
After creation, you need to specify custom signatures in IPS sensors created to
scan traffic. For more information about creating IPS sensors, see “Adding an IPS
sensor” on page 470.
For more information about custom signatures, see the FortiGate Intrusion
Protection System (IPS) Guide.
Viewing the custom signature list

To view the custom signature list, go to Intrusion Protection > Signature >
Custom.
Figure 284:The custom signature list
Edit
Delete
Create New Select to create a new custom signature.

Name The custom signature name.
Signature The signature syntax.
Delete and Edit Delete or edit the custom signature.
icons
Creating custom signatures

Use custom signatures to block or allow specific traffic. For example, to block
traffic containing profanity, add custom signatures similar to the following:
set signature 'F-SBID (--protocol tcp; --flow bi_direction;
--pattern "bad words"; --no_case)'
For more information on custom signature syntax, see the FortiGate Intrusion
Note: Custom signatures are an advanced feature. This document assumes the user has
previous experience creating intrusion detection signatures.
Note: Custom signatures must be added to a signature override in an IPS filter to have any
effect. Creating a custom signature is a necessary step, but a custom signature does not
affect traffic simply by being created.

01-30007-0203-20090112 467
Protocol decoders Intrusion Protection
To create a custom signature, go to Intrusion Protection > Signature > Custom.
Figure 285:Edit Custom Signature
Name Enter a name for the custom signature.

Signature Enter the custom signature, using the appropriate syntax. For more
information, see “Custom signature syntax” in the FortiGate Intrusion
Protocol decoders
The FortiGate Intrusion Protection system uses protocol decoders to identify the
abnormal traffic patterns that do not meet the protocol requirements and
standards. For example, the HTTP decoder monitors traffic to identify any HTTP
packets that do not meet the HTTP protocol standards.
Viewing the protocol decoder list

To view the decoders and the port numbers that the protocol decoders monitor, go
to Intrusion Protection > Signature > Protocol Decoder. The decoder list is
provided for your reference and can be configured using the CLI. For more
Figure 286:The protocol decoder list
Protocols The protocol decoder name.

Ports The port number or numbers that the decoder monitors.

468 01-30007-0203-20090112
Intrusion Protection IPS sensors
Upgrading the IPS protocol decoder list

The Intrusion Protection system protocol decoders are upgraded automatically
through the FortiGuard Distribution Network (FDN) if existing decoders are
modified or new decoders added. The FDN keeps the protocol decoder list up-to-
date with protection against new threats such as the latest versions of existing
IM/P2P as well as against new applications.
IPS sensors
You can group signatures into IPS sensors for easy selection in protection
profiles. You can define signatures for specific types of traffic in separate IPS
sensors, and then select those sensors in profiles designed to handle that type of
traffic. For example, you can specify all of the web-server related signatures in an
IPS sensor, and the sensor can then be used by a protection profile in a policy
that controls all of the traffic to and from a web server protected by the FortiGate
unit.
The FortiGuard Service periodically updates the pre-defined signatures, with
signatures added to counter new threats. Because the signatures included in
filters are defined by specifying signature attributes, new signatures matching
existing filter specifications will automatically be included in those filters. For
example, if you have a filter that includes all signatures for the Windows operating
system, your filter will automatically incorporate new Windows signatures as they
are added.
Viewing the IPS sensor list

To view the IPS sensors, go to Intrusion Protection > IPS Sensor.
Figure 287:IPS Sensor list showing the default sensors
Edit
Delete
Create New Add a new IPS sensor. For more information, see “Adding an
IPS sensor” on page 470.
Name The name of each IPS sensor.
Comments An optional description of the IPS sensor.
Delete and Edit icons Delete or edit an IPS sensor.
Five default IPS sensors are provided with the default configuration.
all_default Includes all signatures. The sensor is set to use the default
enable status and action of each signature.
all_default_pass Includes all signatures. The sensor is set to use the default
enable status of each signature, but the action is set to pass.

01-30007-0203-20090112 469
IPS sensors Intrusion Protection
protect_client Includes only the signatures designed to detect attacks

against clients; uses the default enable status and action of
each signature.
protect_email_server Includes only the signatures designed to detect attacks
against servers and the SMTP, POP3, or IMAP protocols;
uses the default enable status and action of each signature.
protect_http_server Includes only the signatures designed to detect attacks
against servers and the HTTP protocol; uses the default
enable status and action of each signature.
Adding an IPS sensor

An IPS sensor must be created before it can be configured by adding filters and
overrides. To create an IPS sensor, go to Intrusion Protection > IPS Sensor and
select Create New.
Figure 288:New IPS sensor
Name Enter the name of the new IPS sensor.

Comment Enter an optional comment to display in the IPS sensor list.
Configuring IPS sensors

Each IPS sensor consists of two parts: filters and overrides. Overrides are always
checked before filters.
Each filter consists of a number of signatures attributes. All of the signatures with
those attributes, and only those attributes, are checked against traffic when the
filter is run. If multiple filters are defined in an IPS Sensor, they are checked
against the traffic one at a time, from top to bottom. If a match is found, the
FortiGate unit takes the appropriate action and stops further checking.
A signature override can modify the behavior of a signature specified in a filter. A
signature override can also add a signature not specified in the sensor’s filters.
Custom signatures are included in an IPS sensor using overrides.
The signatures in the overrides are first compared to network traffic. If the IPS
sensor does not find any matches, it then compares the signatures in each filter to
network traffic, one filter at a time, from top to bottom. If no signature matches are
found, the IPS sensor allows the network traffic.

470 01-30007-0203-20090112
To view an IPS sensor, go to Intrusion Protection > IPS Sensor and select the
Edit icon of any IPS sensor. The Edit IPS Sensor window is divided into three
parts: the sensor attributes, the filters, and the overrides.
Figure 289:Edit IPS sensor

Insert
Edit Move To
Signature attributes Delete View Rules
IPS sensor attributes:
Name The name of the IPS sensor. You can change it at any time.
Comments An optional comment describing the IPS sensor. You can change it at
any time.
OK Select to save changes to Name or Comments
IPS sensor filters:
Add Filter Add a new filter to the end of the filter list. For more information, see
“Configuring filters” on page 472.
# Current position of each filter in the list.
Name The name of the filter.
Signature Signature attributes specify the type of network traffic the signature
attributes applies to.
Severity The severity of the included signatures.
Target The type of system targeted by the attack. The targets
are client and server.
Protocol The protocols to which the signatures apply. Examples
include HTTP, POP3, H323, and DNS.
OS The operating systems to which the signatures apply.
Application The applications to which the signatures apply.
Enable The status of the signatures included in the filter. The signatures can be
set to enabled, disabled, or default. The default setting uses the default
status of each individual signature as displayed in the signature list.
Logging The logging status of the signatures included in the filter. Logging can
be set to enabled, disabled, or default. The default setting uses the
default status of each individual signature as displayed in the signature
list.
Action The action of the signatures included in the filter. The action can be set
to pass all, block all, reset all, or default. The default setting uses the
action of each individual signature as displayed in the signature list.
Count The number of signatures included in the filter. Overrides are not
included in this total.
Delete icon Delete the filter.

01-30007-0203-20090112 471
Edit icon Edit the filter.

Insert icon Create a new filter and insert it above the current filter.
Move to icon After selecting this icon, enter the destination position in the window
that appears, and select OK.
View Rules icon Open a window listing all of the signatures included in the filter.
IPS sensor overrides:
Add Pre-defined Select to create an override based on a pre-defined signature.

Override
Add Custom Select to create an override based on a custom signature.
Override
# Current position of each override in the list.
Name The name of the signature.
Enable The status of the override. A green circle indicates the override is
enabled. A gray circle indicates the override is not enabled.
Logging The logging status of the override. A green circle indicates logging is
enabled. A gray circle indicates logging is not enabled.
Action The action set for the override. The action can be set to pass, block, or
reset.
Delete and Edit Delete or edit the filter.
icons
Configuring filters
To configure a filter, go to Intrusion Protection > IPS Sensor. Select the Edit icon
of the IPS sensor containing the filter you want to edit. When the sensor window
opens, select the Edit icon of the filter you want to change, or select Add Filter to
create a new filter. Enter the information as described below and select OK.
Figure 290:Edit IPS Filter
Right Arrow
Left Arrow

472 01-30007-0203-20090112
Name Enter or change the name of the IPS filter.

Severity Select All, or select Specify and then one or more severity ratings.
Severity defines the relative importance of each signature. Signatures
rated critical detect the most dangerous attacks while those rated as
info pose a much smaller threat.
Target Select All, or select Specify and then the type of systems targeted by the
attack. The choices are server or client.
OS Select All, or Select Specify and then select one or more operating
systems that are vulnerable to the attack.
Signatures with an OS attribute of All affect all operating systems.
These signatures will be automatically included in any filter regardless
of whether a single, multiple, or all operating systems are specified.
Protocol Select All, or select Specify to list what network protocols are used by
the attack. Use the Right Arrow to move the ones you want to include in
the filter from the Available to the Selected list, or the Left Arrow to
remove previously selected protocols from the filter.
Application Select All, or select Specify to list the applications or application suites
vulnerable to the attack. Use the Right Arrow to move the ones you
want to include in the filter from the Available to the Selected list, or the
Left Arrow to remove previously selected protocols from the filter.
Enable Select from the options to specify what the FortiGate unit will do with the
signatures included in the filter: enable all, disable all, or enable or
disable each according to the individual default values shown in the
signature list.
Logging Select from the options to specify whether the FortiGate unit will create
log entries for the signatures included in the filter: enable all, disable all,
or enable or disable logging for each according to the individual default
values shown in the signature list.
Action Select from the options to specify what the FortiGate unit will do with
traffic containing a signature match: pass all, block all, reset all, or block
or pass traffic according to the individual default values shown in the
signature list.
The signatures included in the filter are only those matching every attribute specified.
When created, a new filter has every attribute set to “all” which causes every signature
to be included in the filter. If the severity is changed to high, and the target is changed
to server, the filter includes only signatures checking for high priority attacks targeted
at servers.
Configuring pre-defined and custom overrides

Pre-defined and custom overrides are configured and work mainly in the same way as
filters. Unlike filters, each override defines the behavior of one signature.
Overrides can be used in two ways:
• To change the behavior of a signature already included in a filter. For example, to
protect a web server, you could create a filter that includes and enables all
signatures related to servers. If you wanted to disable one of those signatures, the
simplest way would be to create an override and mark the signature as disabled.
• To add an individual signature, not included in any filters, to an IPS sensor. This is
the only way to add custom signatures to IPS sensors.
When a pre-defined signature is specified in an override, the default status and action
attributes have no effect. These settings must be explicitly set when creating the
override.

01-30007-0203-20090112 473
Note: Before an override can affect network traffic, you must add it to a filter, and you must
select the filter in a protection profile applied to a policy. An override does not have the
ability to affect network traffic until these steps are taken.
To edit a pre-defined or custom override, go to Intrusion Protection >

IPS Sensor and select the Edit icon of the IPS sensor containing the override you
want to edit. When the sensor window opens, select the Edit icon of the override
you want to change.
Figure 291:Configure IPS override
Signature Select the browse icon to view the list of available signatures. From this
list, select a signature the override will apply to and then select OK.
Enable Select to enable the signature override.
Action Select one of Pass, Block or Reset. When the override is enabled, the
action determines what the FortiGate will do with traffic containing the
specified signature.
Logging Select to enable creation of a log entry if the signature is discovered in
network traffic.
Packet Log Select to save packets that trigger the override to the FortiGate hard
drive for later examination. This option is only valid on FortiGate units
with an internal hard drive.
Exempt IP: Enter IP addresses to exclude from the override. The override will then
apply to all IP addresses except those defined as exempt. The exempt
IP addresses are defined in pairs, with a source and destination, and
traffic moving from the source to the destination is exempt from the
override.
Source The exempt source IP address. Enter 0.0.0.0/0 to
include all source IP addresses.
Destination: The exempt destination IP address. Enter 0.0.0.0/0 to
include all destination IP addresses.

474 01-30007-0203-20090112
Intrusion Protection DoS sensors
DoS sensors
The FortiGate IPS uses a traffic anomaly detection feature to identify network
traffic that does not fit known or common traffic patterns and behavior. For
example, one type of flooding is the denial of service (DoS) attack that occurs
when an attacking system starts an abnormally large number of sessions with a
target system. The large number of sessions slows down or disables the target
system so legitimate users can no longer use it. This type of attack gives the DoS
sensor its name, although it is capable of detecting and protecting against a
number of anomaly attacks.
You can enable or disable logging for each traffic anomaly, and configure the
detection threshold and action to take when the detection threshold is exceeded.
You can create multiple DoS sensors. Each sensor consists of 12 anomaly types
that you can configure. Each sensor examines the network traffic in sequence,
from top to bottom. When a sensor detects an anomaly, it applies the configured
action. Multiple sensors allow great granularity in detecting anomalies because
each sensor can be configured to examine traffic from a specific address, to a
specific address, on a specific port, in any combination.
When arranging the DoS sensors, place the most specific sensors at the top and
the most general at the bottom. For example, a sensor with one protected address
table entry that includes all source addresses, all destination addresses, and all
ports will match all traffic. If this sensor is at the top of the list, no subsequent
sensors will ever execute.
The traffic anomaly detection list can be updated only when the FortiGate
firmware image is upgraded.
must be configured separately in each VDOM. All sensors and custom signatures will
appear only in the VDOM in which they were created.
Viewing the DoS sensor list

To view the anomaly list, go to Intrusion Protection > DoS Sensor.
Figure 292:The DoS sensor list

Delete
Edit
Insert DoS Sensor before

Move To
Create New Add a new DoS sensor to the bottom of the list.
ID A unique identifier for each DoS sensor. The ID does not indicate the
sequence in which the sensors examine network traffic.
Status Select to enable the DoS sensor.
Name The DoS sensor name.
Comments An optional description of the DoS sensor.

01-30007-0203-20090112 475
DoS sensors Intrusion Protection
Delete Delete the DoS sensor.

Edit icon Edit the following information: Action, Severity, and Threshold.
Insert DoS Sensor Create a new DoS sensor before the current sensor.
before icon
Move To icon Move the current DoS sensor to another position in the list. After
selecting this icon, enter the destination position in the window that
appears, and select OK.
Configuring DoS sensors

Because an improperly configured DoS sensor can interfere with network traffic,
no DoS sensors are present on a factory default FortiGate unit. You must create
your own and then enable them before they will take effect. Thresholds for newly
created sensors are preset with recommended values that you can adjust to meet
the needs of your network.
Note: It is important to know normal and expected network traffic before changing the
default anomaly thresholds. Setting the thresholds too low could cause false positives, and
setting the thresholds too high could allow otherwise avoidable attacks.
To configure DoS sensors, go to Intrusion Protection > DoS Sensor. Select the
Edit icon of an existing DoS sensor, or select Create New to create a new DoS
sensor.
Figure 293:Edit DoS Sensor
DoS sensor attributes

Name Enter or change the DoS sensor name.
Comments Enter or change an optional description of the DoS sensor. This description
will appear in the DoS sensor list.

476 01-30007-0203-20090112
Intrusion Protection DoS sensors
Anomaly configuration
Name The name of the anomaly.
Enable Select the check box to enable the DoS sensor to detect when the
specified anomaly occurs. Selecting the check box in the header row will
enable sensing of all anomalies.
Logging Select the check box to enable the DoS sensor to log when the anomaly
occurs. Selecting the check box in the header row will enable logging for all
anomalies. Anomalies that are not enabled are not logged.
Action Select Pass to allow anomalous traffic to pass when the FortiGate unit
detects it, or set Block to prevent the traffic from passing.
Threshold Displays the number of sessions/packets that must show the anomalous
behavior before the FortiGate unit triggers the anomaly action (pass or
block). If required, change the number. For more information about how
these settings affect specific anomalies, see Table 42 on page 477.
Protected addresses
Each entry in the protected address table includes a source and destination IP
address as well as a destination port. The DoS sensor will be applied to traffic
matching the three attributes in any table entry.
Note: A new DoS sensor has no protected address table entries. If no addresses are
entered, the DoS sensor cannot match any traffic and will not function.
Destination The IP address of the traffic destination. 0.0.0.0/0 matches all addresses. If
the FortiGate unit is running in transparent mode, 0.0.0.0/0 also includes
the management IP address.
Destination The destination port of the traffic. 0 matches any port.
Port
Source The IP address of the traffic source. 0.0.0.0/0 matches all addresses.
Add After entering the required destination address, destination port, and
source address, select Add to add protected address to the Protected
Addresses list. The DoS sensor will be invoked only on traffic matching all
three of the entered values. If no addresses appear in the list, the sensor
will not be applied to any traffic.
Understanding the anomalies

For each of the TCP, UDP, and ICMP protocols, DoS sensors offer four statistical
anomaly types. The result is twelve configurable anomalies.
Table 42: The twelve individually configurable anomalies
Anomaly Description
tcp_syn_flood If the SYN packet rate, including retransmission, to one destination
IP address exceeds the configured threshold value, the action is
executed. The threshold is expressed in packets per second.
tcp_port_scan If the SYN packets rate, including retransmission, from one source
tcp_src_session If the number of concurrent TCP connections from one source IP
address exceeds the configured threshold value, the action is
executed.

01-30007-0203-20090112 477
Intrusion protection CLI configuration Intrusion Protection
Table 42: The twelve individually configurable anomalies (Continued)
Anomaly Description
tcp_dst_session If the number of concurrent TCP connections to one destination IP
executed.
udp_flood If the UDP traffic to one destination IP address exceeds the
configured threshold value, the action is executed. The threshold is
expressed in packets per second.
udp_scan If the number of UDP sessions originating from one source IP
udp_src_session If the number of concurrent UDP connections from one source IP
executed.
udp_dst_session If the number of concurrent UDP connections to one destination IP
executed.
icmp_flood If the number of ICMP packets sent to one destination IP address
exceeds the configured threshold value, the action is executed.
The threshold is expressed in packets per second.
icmp_sweep If the number of ICMP packets originating from one source IP
icmp_src_session If the number of concurrent ICMP connections from one source IP
executed.
icmp_dst_session If the number of concurrent ICMP connections to one destination
executed.
Intrusion protection CLI configuration

This section describes the CLI commands that extend features available through
the web-based manager. For complete descriptions and examples of how to
enable additional features through CLI commands, see the FortiGate CLI
Reference.
ips global fail-open

If for any reason the IPS should cease to function, it will fail open by default. This
means crucial network traffic will not be blocked, and the FortiGate unit will
continue to operate while the problem is being resolved.
ips global socket-size

Set the size of the IPS buffer.

478 01-30007-0203-20090112
Web Filter Order of web filtering
Web Filter
The three main sections of the web filtering function, the Web Filter Content
Block, the URL Filter, and the FortiGuard Web filter, interact with each other in
such a way as to provide maximum control and protection for the Internet users.
If you enable virtual domains (VDOMs) on the FortiGate unit, web filtering is
• Order of web filtering
• How web filtering works
• Web filter controls
• Content block
• URL filter
• FortiGuard - Web Filter
Order of web filtering

Web filters are applied in a specific order:
1 URL Exempt (Web Exempt List)
2 URL Block (Web URL Block)
3 URL Block (Web Pattern Block)
4 FortiGuard Web Filtering (Also called Category Block)
5 Content Block (Web Content Block)
6 Script Filter (Web Script Filter)
7 Antivirus scanning
The URL filter list is processed in order from top to bottom. (In FortiOS v2.80 the
URL filter is processed as an unordered list.) An exempt match stops all further
checking including AV scanning. An allow match exits the URL filter list and
checks the other web filters.
Local ratings are checked prior to other FortiGuard Web Filtering categories.
The FortiGate unit applies the rules in this order and failure to comply with a rule
will automatically block a site despite what the setting for later filters might be.

01-30007-0203-20090112 479
How web filtering works Web Filter
How web filtering works

The following information shows how the filters interact with each other and how
to use them to your advantage.
The first section, the URL exempt and block filters, will allow you to decide what
action to take for specific addresses. For example, if you want to exempt
www.google.com from being scanned, you can add it to the URL exempt list. Then
no web filtering or virus scanning will be taken to this web site.
If you have blocked a pattern but want certain users to have access to URLs
within that pattern, you can use the Override within the FortiGuard Web Filter. This
will allow you to specify which users have access to which blocked URLs and how
long they have that access. For example, you want User1 to be able to access
www.fakeLAND.com for 1 hour. You can use this section to set up the exemption.
Any user listed in an override must fill out an online authentication form before the
FortiGuard unit will grant access to the blocked URL.
FortiGuard Web Filter also lets you create local categories to block groups of
URLs. Once you have created the category, you can use the local rating to add
specific sites to the local category you have created. You then use the Firewall >
Protection Profile to tell the FortiGuard Unit what action to take with the Local
category. The local ratings overwrite the FortiGuard ratings.
Finally the FortiGuard unit applies script filtering for ActiveX, Cookie, and Java
applet, which can be configured in Firewall > Protection Profile > Web Filtering.
Once you have finished configuring all of these settings, you still have to turn them
all on in the Firewall > Protection Profile > Web filtering and Firewall >
Protection Profile >FortiGuard Web Filtering. By enabling them here, you are
telling the FortiGate unit to start using the filters as you have configured them.
This section describes how to configure web filtering options. Web filtering
functions must be enabled in the active protection profile for the corresponding
settings in this section to have any effect.
Web filter controls

As a general rule you go to Web Filter to configure the web filtering settings and to
enable the filters for use in a protection profile. To actually activate the enabled
filters you go to Firewall> Protection Profile.
Note: Enabled means that the filter will be used when you turn on web filtering. It does not
mean that the filter is turned on. To turn on all enabled filters you must go to Firewall>
Protection Profile.
FortiGuard - Web Filter is described in detail in“FortiGuard Web Filtering options”

on page 370. Rating corrections as well as suggesting ratings for new pages can
be submitted on the FortiGuard Center web page. Visit the Fortinet Knowledge
Center for details and a link to the FortiGuard Center.
The following tables compare web filtering options in protection profiles and the
web filter menu.

480 01-30007-0203-20090112
Web Filter Web filter controls
Table 43: Web filter and Protection Profile web content block configuration
Protection Profile web filtering options Web Filter setting

Web Content Block Web Filter > Content Block
Enable or disable web page blocking based Add words and patterns to block web
on the banned words and patterns in the pages containing those words or
content block list for HTTP traffic. patterns.
Table 44: Web filter and Protection Profile web URL filtering configuration

Web URL Filter Web Filter > URL Filter
Enable or disable web page filtering for HTTP Add URLs and URL patterns to exempt
traffic based on the URL filter list. or block web pages from specific
sources.
Table 45: Web filter and Protection Profile web script filtering and download
configuration

Active X Filter, Cookie Filter, Java Applet Filter n/a
Enable or disable blocking scripts from web
pages for HTTP traffic.
Web resume Download Block n/a
Enable to block downloading the remainder of
a file that has already been partially
downloaded. Enabling this option prevents the
unintentional download of virus files, but can
cause download interruptions.
Table 46: Web filter and Protection Profile web category filtering configuration

Enable FortiGuard Web Filtering (HTTP only). FortiGuard Web Filter > Configuration
Enable FortiGuard Web Filtering Overrides FortiGuard Web Filtering > Overrides
(HTTP only).
Provide details for blocked HTTP 4xx and 5xx
errors (HTTP only.)
Rate images by URL (Blocked images will be
replaced with blanks) (HTTP only).
Allow web sites when a rating error occurs
(HTTP only).
Strict Blocking (HTTP only)
Category / Action
FortiGuard Web Filtering service provides
many categories by which to filter web traffic.
Set the action to take on web pages for each
category. Choose from allow, block, log, or
allow override.
Local Categories can be configured to best FortiGuard Web Filtering > Local
suit local requirements. Categories | Local Ratings

01-30007-0203-20090112 481
Content block Web Filter
Table 46: Web filter and Protection Profile web category filtering configuration

Classification/Action
When selected, users can access web sites
that provide content cache, and provide
searches for image, audio, and video files.
Choose from allow, block, log, or allow
override.
To access protection profile web filter options

2 Select edit or Create New.
3 Select Web Filtering or Web Category Filtering.
Note: If virtual domains are enabled on the FortiGate unit, web filtering features are
configured globally. To access these features, select Global Configuration on the main
menu.
Content block
Control web content by blocking specific words or patterns. If enabled in the
protection profile, the FortiGate unit searches for words or patterns on requested
web pages. If matches are found, values assigned to the words are totalled. If a
user-defined threshold value is exceeded, the web page is blocked.
Use Perl regular expressions or wildcards to add banned word patterns to the list.
See “Using wildcards and Perl regular expressions” on page 511.
Note: Perl regular expression patterns are case sensitive for Web Filter content block. To
make a word or phrase case insensitive, use the regular expression /i. For example,
/bad language/i blocks all instances of bad language regardless of case. Wildcard
patterns are not case sensitive.
Viewing the web content block list catalog

You can add multiple web content block lists and then select the best web content
block list for each protection profile. To view the web content block list catalog, go
to Web Filter > Content Block. To view any individual web content block list,
select the edit icon for the list you want to see.
Figure 294:Sample web content block list catalog
The web content block list catalogue has the following icons and features:
Create New Select Create New to add a new web content block list to the catalog.
Name The available web content block lists.
# Entries The number of content patterns in each web content block list.

482 01-30007-0203-20090112
Web Filter Content block
Profiles The protection profiles each web content block list has been applied
to.
Comment Optional description of each web content block list. The comment text
must be less than 63 characters long. Otherwise, it will be truncated.
Spaces will also be replaced by the plus sign ( + ).
Delete icon Select to remove the web content block list from the catalog. The
delete icon is only available if the web content block list is not
selected in any protection profiles.
Edit icon Select to edit the web content block list, list name, or list comment.
Select web content block lists in protection profiles. For more information, see
“Web Filtering options” on page 369.
Creating a new web content block list

To add a web content block list to the web content block list catalog go to
Web Filter > Content Block. Select Create New.
Figure 295:New Web Content Block list dialog box

Viewing the web content block list

With web content block enabled, every requested web page is checked against
the content block list. The score value of each pattern appearing on the page is
added, and if the total is greater than the threshold value set in the protection
profile, the page is blocked. The score for a pattern is applied only once even if it
appears on the page multiple times.
To view the web content block list go to Web Filter > Content Block and select
the Edit icon of the web content block list you want to view.
Figure 296:Sample web content block list
Note: Enable Web Filtering > Web Content Block in a firewall Protection Profile to activate
the content block settings.
The web content block list has the following icons and features:

01-30007-0203-20090112 483
Name Web content block list name. To change the name, edit text in the name
Comment Optional comment. To add or edit comment, enter text in comment field
and select OK.
Create new Select to add a pattern to the web content block list.
Total The number of patterns in the web content block list.
Page up icon Select to view the previous page.
Page down icon Select to view the next page.
Remove All Select to clear the table.
Entries icon
Banned word The current list of patterns. Select the check box to enable all the
patterns in the list.
Pattern type The pattern type used in the pattern list entry. Choose from wildcard or
regular expression. See “Using wildcards and Perl regular expressions”
on page 511.
Language The character set to which the pattern belongs: Simplified Chinese,
Traditional Chinese, French, Japanese, Korean, Thai, or Western.
Score A numerical weighting applied to the pattern. The score values of all the
matching patterns appearing on a page are added, and if the total is
greater than the threshold value set in the protection profile, the page is
blocked.
Delete icon Select to delete an entry from the list.
Edit icon Select to edit the following information: Banned Word, Pattern Type,
Language, and Enable.
Configuring the web content block list

Web content patterns can be one word or a text string up to 80 characters long.
The maximum number of banned words in the list is 5000.
To add or edit a content block pattern go to Web Filter > Content Block and
select Create New or select the edit icon of the web content block list you want to
view.
Figure 297:New content block pattern
Banned Word Enter the content block pattern. For a single word, the FortiGate
checks all web pages for that word. For a phrase, the FortiGate
checks all web pages for any word in the phrase. For a phrase in
quotation marks, the FortiGate unit checks all web pages for the
entire phrase.
Pattern Type Select a pattern type from the dropdown list: Wildcard or regular
Expression.
Language Select a language from the dropdown list.
Score Enter a score for the pattern.

484 01-30007-0203-20090112
Web Filter Content block
Viewing the web content exempt list catalog

You can add multiple web content exempt lists and then select the best web
content exempt list for each protection profile.
To view the web content block list catalog go to Web Filter > Content Block >
Web Content Exempt.
To view any individual web content exempt list, select the Edit icon for the list you
want to see.
Figure 298:Sample web content exempt list catalog
The web content exempt list catalogue has the following icons and features:
Create New Select Create New to add a new web content exempt list to the catalog.
Name The available web content block lists.
# Entries The number of content patterns in each web content block list.
Profiles The protection profiles each web content block list has been applied to.
Comment Optional description of each web content block list.
Delete icon Select to remove the web content block list from the catalog. The delete
icon is only available if the web content block list is not selected in any
protection profiles.
Edit icon Select to edit the web content block list, list name, or list comment.
Select web content block lists in protection profiles. For more information, see
“Web Filtering options” on page 369.
Creating a new web content exempt list

To add a web content exempt list to the web content exempt list catalog go to Web
Filter > Content Block > Web Content Exempt. Select Create New.
Figure 299:New Web Content Exempt list dialog box


01-30007-0203-20090112 485
Viewing the web content exempt list

Web content exempt allows overriding of the web content block feature. If any
patterns defined in the web content exempt list appear on a web page, the page will
not be blocked even if the web content block feature would otherwise block it.
To view the web content exempt list go to Web Filter > Content Block > Web
Content Exempt. Select the Edit icon of the web content block list you want to view.
Figure 300:Sample web content exempt list
Note: Enable Web Filtering > Web Content Exempt in a firewall Protection Profile to
activate the content exempt settings.
The web content exempt list has the following icons and features:
Name Web content exempt list name. To change the name, edit text in the
name field and select OK.
Comment Optional comment. To add or edit comment, enter text in comment field
and select OK.
Create new Select to add a pattern to the web content exempt list.
Total The number of patterns in the web content exempt list.
Remove All Select to clear the table.
Entries icon
Pattern The current list of patterns. Select the check box to enable all the
patterns in the list.
Pattern type The pattern type used in the pattern list entry. Choose from wildcard or
regular expression. See “Using wildcards and Perl regular expressions”
on page 511.
Language The character set to which the pattern belongs: Simplified Chinese,
Traditional Chinese, French, Japanese, Korean, Thai, or Western.
Delete icon Select to delete an entry from the list.
Edit icon Select to edit the following information: Pattern, Pattern Type, Language,
and Enable.

486 01-30007-0203-20090112
Web Filter URL filter
Configuring the web content exempt list

Web content patterns can be one word or a text string up to 80 characters long.
The maximum number of banned words in the list is 5000.
To add or edit a content block pattern go to Web Filter > Content Block > Web
Content Exempt. Select Create New or select the Edit icon of the web content
block pattern you want to view.
Figure 301:New content exempt pattern
Pattern Word Enter the content exempt pattern. For a single word, the FortiGate
checks all web pages for that word. For a phrase, the FortiGate
checks all web pages for any word in the phrase. For a phrase in
quotation marks, the FortiGate unit checks all web pages for the
entire phrase.
Pattern Type Select a pattern type from the dropdown list: Wildcard or regular
Expression.
Language Select a language from the dropdown list.
URL filter
Allow or block access to specific URLs by adding them to the URL filter list. Add
patterns using text and regular expressions (or wildcard characters) to allow or
block URLs. The FortiGate unit allows or blocks web pages matching any
specified URLs or patterns and displays a replacement message instead.
Note: Enable Web filtering > Web URL Filter in a firewall Protection Profile to activate the
URL filter settings.
Note: URL blocking does not block access to other services that users can access with a
web browser. For example, URL blocking does not block access to
ftp://ftp.example.com. Instead, use firewall policies to deny FTP connections.
Viewing the URL filter list catalog

You can add multiple URL filter lists and then select the best URL filter list for each
protection profile.
To view the URL filter list catalog go to Web Filter > URL Filter.
To view any individual URL filter list go to Web Filter > URL Filter. Select the Edit
icon for the list you want to see.

01-30007-0203-20090112 487
URL filter Web Filter
Figure 302:Sample URL filter list catalog
The URL filter list catalogue has the following icons and features:
Create New Select Create New to add a new web content URL list to the catalog.
Name The available URL filter lists.
# Entries The number of URL patterns in each URL filter list.
Profiles The protection profiles each URL filter list has been applied to.
Comment Optional description of each URL filter list.
Delete icon Select to remove the URL filter list from the catalog. The delete icon
is only available if the URL filter list is not selected in any protection
profiles.
Edit icon Select to edit the URL filter list, list name, or list comment.
Select URL filter lists in protection profiles. For more information, see “Web
Filtering options” on page 369.
Creating a new URL filter list

Different FortiGate models support different maximum numbers of URL filter lists.
For details, see the FortiGate Maximum Values Matrix in Fortinet’s Knowledge
Center web site http://kc.forticare.com.
To add a URL filter list to the URL filter list catalog go to Web Filter > URL Filter.
Select Create New.
Figure 303:New URL Filter list dialog box

Viewing the URL filter list

Add specific URLs to block or exempt. Add the following items to the URL filter list:
• complete URLs
• IP addresses
• partial URLs to allow or block all sub-domains
To view the URL filter list go to Web Filter > URL Filter. Select the edit icon of the
URL filter list you want to view.

488 01-30007-0203-20090112
Web Filter URL filter
Figure 304:URL filter list
The URL filter list has the following icons and features:
Name URL filter list name. To change the name, edit text in the name field
and select OK.
Comment Optional comment. To add or edit comment, enter text in comment
Create New Select to add a URL to the URL block list.
Clear All URL Select to clear the table.
Filters icon
URL The current list of blocked/exempt URLs. Select the check box to
enable all the URLs in the list.
Type The type of URL: Simple or Regex (regular expression).
Action The action taken when the URL matches: Allow, Block, or Exempt.
An allow match exits the URL filter list and checks the other
web filters.
An exempt match stops all further checking including AV
scanning.
A block match blocks the URL and no further checking will be
done.
Delete icon Select to remove an entry from the list.
Edit icon Select to edit the following information: URL, Type, Action, and
Enable.
Move icon Select to open the Move URL Filter dialog box.
Configuring the URL filter list

Each URL filter list can have up to 5000 entries.
Note: Type a top-level domain suffix (for example, “com” without the leading period) to
block access to all URLs with this suffix.
To add a URL to the URL filter list go to Web Filter > URL Filter. Select Create
New or edit an existing list.

01-30007-0203-20090112 489
URL filter Web Filter
Figure 305:New URL Filter
URL Enter the URL. Do not include http://. For details about URL
formats, see “URL formats” on page 490.
Type Select a type from the dropdown list: Simple or Regex (regular
expression).
Action Select an action from the dropdown list: Allow, Block, or Exempt.
An allow match exits the URL filter list and checks the other web
filters.
An exempt match stops all further checking including AV
scanning.
A block match blocks the URL and no further checking will be
done.
Enable Select to enable the URL.
URL formats
When adding a URL to the URL filter list (see “Configuring the URL filter list” on
page 489), follow these rules:
HTTPs URL formats

Type a top level domain name for HTTPs URL filtering, for example,
www.example.com. HTTPs URL filtering works by extracting the CN from the
server certificate during the SSL negotiation. Because the CN only contains the
domain name of the site being accessed, HTTPS web filtering can only filter by
domain names.
HTTP URL formats

• Type a top-level URL or IP address to control access to all pages on a web
site. For example, www.example.com or 192.168.144.155 controls access
to all pages at this web site.
• Enter a top-level URL followed by the path and filename to control access to a
single page on a web site. For example, www.example.com/news.html or
192.168.144.155/news.html controls the news page on this web site.
• To control access to all pages with a URL that ends with example.com, add
example.com to the filter list. For example, adding example.com controls
access to www.example.com, mail.example.com,
www.finance.example.com, and so on.
• Control access to all URLs that match patterns created using text and regular
expressions (or wildcard characters). For example, example.* matches
example.com, example.org, example.net and so on.
FortiGate web pattern blocking supports standard regular expressions.

490 01-30007-0203-20090112
Web Filter FortiGuard - Web Filter
Note: URLs with an action set to exempt are not scanned for viruses. If users on
the network download files through the FortiGate unit from trusted website, add the
URL of this website to the URL filter list with an action set to exempt so the
FortiGate unit does not virus scan files downloaded from this URL.
Note: Enable Web Filtering > Web URL Filter > HTTP or HTTPS in a firewall Protection
Profile to activate the web URL filter settings for HTTP and/or HTTPS traffic.
Moving URLs in the URL filter list

To make the URL filter list easier to use, the entries can be moved to different
positions in the list.
To move a URL in the URL filter list

1 Go to Web Filter > URL Filter.
2 Select the Edit icon for the URL list.
3 Drag and drop a URL or select the Move icon to the right of the URL to be moved.
4 Specify the location for the URL.
5 Select OK.
Figure 306:Move URL Filter
Move to Select the location in the list to place the URL.

(URL) Enter the URL before or after which the new URL is to be located
in the list.
FortiGuard - Web Filter

FortiGuard Web Filtering is a managed web filtering solution provided by Fortinet.
FortiGuard Web Filtering sorts hundreds of millions of web pages into a wide
range of categories users can allow, block, or monitor. The FortiGate unit
accesses the nearest FortiGuard Web Filtering Service Point to determine the
category of a requested web page then follows the firewall policy configured for
that user or interface.
FortiGuard Web Filtering includes over 60 million individual ratings of web sites
applying to hundreds of millions of pages. Pages are sorted and rated into 56
categories users can allow, block, or monitor. Categories may be added to, or
updated, as the Internet evolves. To make configuration simpler, users can also
choose to allow, block, or monitor entire groups of categories. Blocked pages are
replaced with a message indicating that the page is not accessible according to
the Internet usage policy.

01-30007-0203-20090112 491
FortiGuard - Web Filter Web Filter
FortiGuard Web Filtering ratings are performed by a combination of proprietary

methods including text analysis, exploitation of the Web structure, and human
raters. Users can notify the FortiGuard Web Filtering Service Points if they feel a
web page is not categorized correctly, and new sites are quickly rated as required.
Use the procedure “FortiGuard Web Filtering options” on page 370 to configure
FortiGuard category blocking in a protection profile. To configure the
FortiGuard Web service, see “Configuring the FortiGate unit for FDN and
FortiGuard subscription services” on page 243.
Configuring FortiGuard Web Filtering

To configure the FortiGuard Web Filtering service go to System > Maintenance >
FortiGuard. See “Configuring the FortiGate unit for FDN and FortiGuard
subscription services” on page 243.
Viewing the override list

Users may require access to web sites that are blocked by a policy. In this case,
an administrator can give the user the ability to override the block for a specified
period of time.
When a user attempts to access a blocked site, if override is enabled, a link
appears on the block page directing the user to an authentication form. The user
must provide a correct user name and password or the web site remains blocked.
Authentication is based on user groups and can be performed for local, RADIUS,
and LDAP users. For more information about authentication and configuring user
groups, see “User groups” on page 435.
Administrative overrides vs. user overrides

In FortiOS v3.0 MR5 and older releases, the URL overrides has an expiry date
and would be automatically deleted when this date is reached.
In FortiOS v3.0 MR6 and newer releases, the URL overrides are split into two
categories: administrative overrides and user overrides.
The administrative overrides are backed up with the main configuration and
managed by the FortiManager system. The administrative overrides are not
cleaned up when they expire and you can reuse these override entries by
extending their expiry dates. You can create administrative overrides using both
the CLI and the web-based manager.
The user overrides are not backed up as part of the main configuration and are not
managed by the FortiManager system. These overrides are also purged when
they expire. You can only view and delete the user overrides entries. Users create
user overrides using the authentication form opened from the block page when
they attempt to access a blocked site, if override is enabled.
To view the override list go to Web Filter > FortiGuard - Web Filter > Override.
Select the Edit icon for Administrative Overrides or User Overrides.
Figure 307:Override list
The override list has the following icons and features:

492 01-30007-0203-20090112
Create New Select to add a new override rule to the list.

This button is not available under User Overrides.
Return Select to return to the override category page.
Clear All icon Select to clear the table.
URL/Category The URL or category to which the override applies.
Scope The user or user group who may use the override.
Off-site URLs A green check mark indicates that the off-site URL option is set to
Allow, which means that the overwrite web page will display the
contents from off-site domains. A gray cross indicates that the off-
site URL option is set to Block, which means that the overwrite
web page will not display the contents from off-site domains. For
details, see “Configuring administrative override rules” on
page 493.
Initiator The creator of the override rule.
Expiry Date The expiry date of the override rule.
Edit icon Select to edit the following information: Type, URL, Scope, User,
Off-site URLs, and Override Duration.
Configuring administrative override rules

Administrative override rules can be configured to allow access to blocked web
sites based on directory, domain name, or category.
To create an override rule for a directory or domain go to Web Filter > FortiGuard
- Web Filter > Override. Select the Edit icon for Administrative Overrides.
Figure 308:New Override Rule - Directory or Domain
Type Select Directory or Domain.

URL Enter the URL or the domain name of the website.
Scope Select one of the following: User, User Group, IP, or Profile.
Depending on the option selected, a different option appears
below Scope.
User Enter the name of the user selected in Scope.
User Group Select a user group from the dropdown list. User groups must be
configured before FortiGuard Web Filtering configuration. For
more information, see “User groups” on page 435.

01-30007-0203-20090112 493
Off-site URLs This option defines whether the override web page will display the
images and other contents from the blocked offsite URLs.
For example, all FortiGuard categories are blocked, and you want
to visit a site whose images are served from a different domain.
You can create a directory override for the site and view the page.
If the offsite feature was set to deny, all the images on the page
will appear broken because they come from a different domain for
which the existing override rule does not apply. If you set the
offsite feature to allow, the images on the page will then show up.
Only users that apply under the scope for the page override can
see the images from the temporary overrides. The users will not
be able to view any pages on the sites where the images come
from (unless the pages are served from the same directory as the
images themselves) without having to create a new override rule.
Override End Time Specify when the override rule will end.
To create an override for categories, go to Web Filter > FortiGuard - Web Filter >
Override.
Figure 309:New Override Rule - Categories
Type Select Categories.

Categories Select the categories to which the override applies. A category
group or a subcategory can be selected. Local categories are also
displayed.
Classifications Select the classifications to which the override applies. When
selected, users can access web sites that provide content cache,
and provide searches for image, audio, and video files.

494 01-30007-0203-20090112
Scope Select one of the following: User, User Group, IP, or Profile.
Depending on the option selected, a different option appears
below Scope.
User Enter the name of the user selected in Scope.
User Group Select a user group from the dropdown list.
IP Enter the IP address of the computer initiating the override.
Profile Select a protection profile from the dropdown list.
Off-site URLs Select Allow or Block. See the previous table for details about off-
site URLs.
Override End Time Specify when the override rule will end.
Creating local categories

User-defined categories can be created to allow users to block groups of URLs on
a per-profile basis. The categories defined here appear in the global URL
category list when configuring a protection profile. Users can rate URLs based on
the local categories.
Figure 310:Local categories list
Add Enter the name of the category then select Add.

Viewing the local ratings list

To view the local ratings list go to Web Filter > FortiGuard - Web Filter >
Local Ratings.
Figure 311:Local ratings list
The local ratings list has the following icons and features:
Create New Select to add a rating to the list.

Search Enter search criteria to filter the list.
1 - 3 of 3 The total number of local ratings in the list.
Clear All icon Select to clear the table.
URL The rated URL. Select the green arrow to sort the list by URL.

01-30007-0203-20090112 495
Category The category or classification in which the URL has been placed.
If the URL is rated in more than one category or classification,
trailing dots appear. Select the gray funnel to open the Category
Filter dialog box. When the list has been filtered, the funnel
changes to green.
Edit icon Select to edit the following information: URL, Category Rating, and
Classification Rating.
Figure 312:Category Filter
Clear Filter Select to remove all filters.

Category Name Select the blue arrow to expand the category.
Enable Filter Select to enable the filter for the category or the individual sub-
category.
Classification Name The classifications that can be filtered.
Enable Filter Select to enable the classification filter.
Configuring local ratings

Users can create user-defined categories then specify the URLs that belong to the
category. This allows users to block groups of web sites on a per profile basis. The
ratings are included in the global URL list with associated categories and
compared in the same way the URL block list is processed.
The local ratings override the FortiGuard server ratings and appear in reports as
“Local Category”.
To create a local rating go to Web Filter > FortiGuard - Web Filter > Local
Ratings.

496 01-30007-0203-20090112
Figure 313:New Local Rating
URL Enter the URL to be rated.

Category Name Select the blue arrow to expand the category.
Enable Filter Select to enable the filter for the category or the individual sub-
category.
Classification Name The classifications that can be filtered.
Enable Filter Select to enable the classification filter.
Category block CLI configuration

Use the hostname keyword for the webfilter fortiguard command to
change the default host name (URL) for the FortiGuard Web Filtering Service
Point. The FortiGuard Web Filtering Service Point name cannot be changed using
the web-based manager. Configure all FortiGuard Web Filtering settings using the
CLI. For more information, see the FortiGate CLI Reference for descriptions of the
webfilter fortiguard keywords.
FortiGuard Web Filtering reports
Note: FortiGuard Web Filtering reports are only available on FortiGate units with a hard
disk.
Generate a text and pie chart format report on FortiGuard Web Filtering for any
protection profile. The FortiGate unit maintains statistics for allowed, blocked, and
monitored web pages for each category. View reports for a range of hours or days,
or view a complete report of all activity.
To create a web filter report go to Web Filter > FortiGuard - Web Filter >
Reports.

01-30007-0203-20090112 497
Figure 314:Sample FortiGuard Web Filtering report
The following table describes the options for generating reports:
Profile Select the protection profile for which to generate a report.

Report Type Select the time frame for the report. Choose from hour, day, or all
historical statistics.
Report Range Select the time range (24 hour clock) or day range (from six days ago to
today) for the report. For example, for an ‘hour’ report type with a range
of 13 to 16, the result is a category block report for 1 pm to 4 pm today.
For a ‘day’ report type with a range of 0 to 3, the result is a category
block report for 3 days ago to today.
Get Report Select to generate the report.
A generated report includes a pie chart and the following information:
Category The category for which the statistic was generated.

Allowed The number of allowed web addresses accessed in the selected time
frame.
Blocked The number of blocked web addresses accessed in the selected time
frame.
Monitored The number of monitored web addresses accessed in the selected time
frame.

498 01-30007-0203-20090112
Antispam Antispam
Antispam
This section explains how to configure the spam filtering options associated with a
firewall protection profile.
If you enable virtual domains (VDOMs) on the FortiGate unit, Antispam is
• Antispam
• Banned word
• Black/White List
• Advanced antispam configuration
• Using wildcards and Perl regular expressions
Antispam
You can configure the FortiGate unit to manage unsolicited commercial email by
detecting and identifying spam transmissions from known or suspected spam
servers.
The FortiGuard Antispam service from Fortinet is designed to manage spam. This
service includes an IP address black list, a URL black list, and spam filtering tools.
The FortiGuard Center accepts submission of spam email messages as well as
reports of false positives. For more information on the FortGuard Center, visit the
FortiGuard Center website at www.fortiguardcenter.com.
Order of spam filtering

The FortiGate unit checks for spam using various filtering techniques. The order
the FortiGate unit uses these filters depends on the mail protocol used.
Filters requiring a query to a server and a reply (FortiGuard Antispam Service and
DNSBL/ORDBL) are run simultaneously. To avoid delays, queries are sent while
other filters are running. The first reply to trigger a spam action takes effect as
soon as the reply is received.
Each spam filter passes the email to the next if no matches or problems are found.
If the action in the filter is Mark as Spam, the FortiGate unit tags or discards
(SMTP only) the email according to the settings in the protection profile. If the
action in the filter is Mark as Clear, the email is exempt from any remaining filters.
If the action in the filter is Mark as Reject, the email session is dropped. Rejected
SMTP email messages are substituted with a configurable replacement message.

01-30007-0203-20090112 499
Antispam Antispam
Order of SMTP spam filtering

1 IP address BWL check on last hop IP.
2 DNSBL & ORDBL check on last hop IP, FortiGuard Antispam IP check on last hop
IP, HELO DNS lookup.
3 MIME headers check, E-mail address BWL check.
4 Banned word check on email subject.
5 IP address BWL check (for IPs extracted from “Received” headers).
6 Banned word check on email body.
7 Return e-mail DNS check, FortiGuard Anti Spam check, DNSBL & ORDBL check
on public IP extracted from header.
Order of POP3 and IMAP spam filtering

1 MIME headers check, E-mail address BWL check.
2 Banned word check on email subject.
3 IP BWL check.
4 Banned word check on email body.
5 Return e-mail DNS check, FortiGuard AntiSpam check, DNSBL & ORDBL check.
Anti-spam filter controls

Spam filters are configured for system-wide use, but enabled on a per profile
basis. Table 47 describes the Antispam settings and where to configure and
access them.
To access protection profile Antispam options, go to Firewall > Protection
Profile, select the edit icon beside an existing profile, or select Create New. Select
Spam Filtering.
Table 47: AntiSpam and Protection Profile spam filtering configuration
Protection Profile spam filtering options AntiSpam setting

IP address FortiGuard Antispam check System > Maintenance > FortiGuard
Configure the FortiGuard Antispam service. Enable FortiGuard Antispam, check the
Fortinet has its own DNSBL server for status of the FortiGuard Antispam server,
FortiGuard Antispam that provides spam IP view the license type and expiry date, and
address and URL blacklists. Fortinet keeps configure the cache. For more information,
the FortiGuard Antispam IP and URLs up-to- see “Configuring the FortiGate unit for
date as new spam sources are found. FDN and FortiGuard subscription services”
on page 243
IP address BWL check AntiSpam > Black/White List > IP Address
Black/white list check. Configure the Add to and edit IP addresses to the list.
checking of incoming IP addresses against You can configure the action to take as
the configured spam filter IP address list. spam, clear, or reject for each IP address.
(SMTP only.) You can place an IP address anywhere in
the list. The filter checks each IP address
in sequence. (SMTP only.)
DNSBL & ORDBL check Command line only

500 01-30007-0203-20090112
Antispam Antispam
Table 47: AntiSpam and Protection Profile spam filtering configuration (Continued)

Enable or disable checking email traffic Add or remove DNSBL and ORDBL
against configured DNS Blackhole List servers to and from the list. You can
(DNSBL) and Open Relay Database List configure the action to take as spam or
(ORDBL) servers. reject for email identified as spam from
each server (SMTP only).
DNSBL and ORDBL configuration can only
be changed using the command line
interface. For more information, see the
HELO DNS lookup n/a
Enable or disable checking the source
domain name against the registered IP
address in the Domain Name Server. If the
source domain name does not match the IP
address the email is marked as spam and
the action selected in the protection profile is
taken.
E-mail address BWL check AntiSpam > Black/White List > E-mail
Address
Enable or disable checking incoming email Add to and edit email addresses to the list,
addresses against the configured spam filter with the option of using wildcards and
email address list. regular expressions. You can configure the
action as spam or clear for each email
address. You can place an email address
anywhere in the list. The filter checks each
email address in sequence.
Return e-mail DNS check n/a
Enable or disable checking incoming email
return address domain against the registered
IP address in the Domain Name Server. If
the return address domain name does not
match the IP address the email is marked as
spam and the action selected in the
protection profile is taken.
MIME headers check Command line only
Enable or disable checking source MIME Add to and edit MIME headers, with the
headers against the configured spam filter option of using wildcards and regular
MIME header list. expressions. You can configure the action
for each MIME header as spam or clear.
DNSBL and ORDBL configuration can only
be changed using the command line
interface. For more information, see the
Banned word check AntiSpam > Banned Word
Enable or disable checking source email Add to and edit banned words to the list,
against the configured spam filter banned with the option of using wildcards and
word list. regular expressions. You can configure the
language and whether to search the email
body, subject, or both. You can configure
the action to take as spam or clear for each
word.
Spam Action n/a

01-30007-0203-20090112 501
Banned word Antispam
Table 47: AntiSpam and Protection Profile spam filtering configuration (Continued)

The action to take on email identified as
spam. POP3 and IMAP messages are
tagged. Choose Tagged or Discard for SMTP
messages. You can append a custom word
or phrase to the subject or MIME header of
tagged email. You can choose to log any
spam action in the event log.
For IMAP, spam email may be tagged only
after the user downloads the entire message
by opening the email, since the some IMAP
email clients download the envelope portion
of the email message initially. For details,
see “Spam Filtering options” on page 373.
Tag location: Affix the tag to the subject or
MIME header of the email identified as
spam.
Tag format: Enter a word or phrase (tag) to
affix to email identified as spam.
Add event into the system log
Enable or disable logging of spam actions to
the event log.
Banned word
Control spam by blocking email messages containing specific words or patterns. If
enabled in the protection profile, the FortiGate unit searches for words or patterns
in email messages. If matches are found, values assigned to the words are
totalled. If a user-defined threshold value is exceeded, the message is marked as
spam. If no match is found, the email message is passed along to the next filter.
Use Perl regular expressions or wildcards to add banned word patterns to the list.
Note: Perl regular expression patterns are case sensitive for antispam banned words. To
make a word or phrase case insensitive, use the regular expression /i. For example,
/bad language/i will block all instances of bad language regardless of case. Wildcard
patterns are not case sensitive.
Viewing the banned word list catalog

You can add a maximum of two antispam banned word lists and then select the
best antispam banned word list for each protection profile. To view the antispam
banned word list catalog, go to AntiSpam > Banned Word. To view any individual
antispam banned word list, select the edit icon for the list you want to see.

502 01-30007-0203-20090112
Antispam Banned word
Figure 315:Sample antispam banned word list catalog
Edit
Delete
Create New Add a new list to the catalog. For more information, see “Creating a
new banned word list” on page 503.
Name The available antispam banned word lists.
# Entries The number of entries in each antispam banned word list.
Profiles The protection profiles each antispam banned word list has been
applied to.
Comments Optional description of each antispam banned word list.
Delete icon Remove the antispam banned word list from the catalog. The delete
icon is available only if the antispam banned word list is not selected
in any protection profiles.
Edit icon Modify the antispam banned word list, list name, or list comment.
To use the banned word list, select antispam banned word lists in protection
profiles. For more information, see “Spam Filtering options” on page 373.
Creating a new banned word list

To add an antispam banned word list to the antispam banned word list catalog, go
to AntiSpam > Banned Word and select Create New.
Figure 316:New AntiSpam Banned Word list dialog box

Comments Enter a comment to describe the list, if required.
Viewing the antispam banned word list

The FortiGate unit checks each email message against the antispam banned
word list. The FortiGate unit can sort email messages containing those banned
words in the subject, body, or both. The score value of each banned word
appearing in the message is added, and if the total is greater than the threshold
value set in the protection profile, the FortiGate unit processes the message
according to the Spam Action setting in the protection profile. The score for a
pattern is applied only once even if the word appears in the message multiple
times.

01-30007-0203-20090112 503
Banned word Antispam
To view the banned word list, go to AntiSpam > Banned Word and select the edit
icon of the banned word list you want to view.
Figure 317:Sample banned word List
Remove All Entries

Edit
Delete
Current Page
Name Banned word list name. To change the name, edit text in the name field
and select OK.
Comments Optional comment. To add or edit comment, enter text in comment field
and select OK.
Create New Select to add a word or phrase to the banned word list.
Current Page The current page number of list items that are displayed. Select the left
and right arrows to display the first, previous, next or last page of the
banned word list.
Remove All Clear the table.
Entries icon
Pattern The list of banned words. Select the check box to enable all the banned
words in the list.
Pattern Type The pattern type used in the banned word list entry. Choose from
wildcard or regular expression. For more information, see “Using
wildcards and Perl regular expressions” on page 511.
Language The character set to which the banned word belongs.
Where The location where the FortiGate unit searches for the banned word:
Subject, Body, or All.
Score A numerical weighting applied to the banned word. The score values of
all the matching words appearing in an email message are added, and if
the total is greater than the Banned word check value set in the
protection profile, the email is processed according to whether the spam
action is set to Discard or Tagged in the protection profile. The score for
a banned word is counted once even if the word appears multiple times
on the web page in the email. For more information, see “Configuring a
protection profile” on page 367.
Delete and Edit Delete or edit the banned word.
icons
Adding words to the banned word list

For a single word, the FortiGate unit blocks all email containing the word. For a
phrase, the FortiGate unit blocks all email containing the exact phrase. To block
any word in a phrase, use Perl regular expressions.

504 01-30007-0203-20090112
Antispam Black/White List
To add a banned word list name

1 Go to AntiSpam > Banned Word.
3 Enter the banned word list name.
4 Optionally, enter any comments about the name.
5 Select OK.
To add a banned word

1 Go to AntiSpam > Banned Word.
2 For the banned word list name to which you want to add a banned word, select
Edit.
Pattern Enter the word or phrase you want to include in the banned word list.
Pattern Type Select the pattern type for the banned word. Choose from wildcard or
regular expression. For more information, see “Using wildcards and Perl
regular expressions” on page 511.
Language Select the character set for the banned word.
Where Select where the FortiGate unit should search for the banned word:
Subject, Body, or All.
Score A numerical weighting applied to the banned word. The score values of
all the matching words appearing in an email message are added, and if
the total is greater than the Banned word check value set in the
protection profile, the email is processed according to whether the spam
action is set to Discard or Tagged in the protection profile. The score for
a banned word is counted once even if the word appears multiple times
on the web page in the email. For more information, see “Configuring a
protection profile” on page 367.
Enable Select to enable scanning for the banned word.
4 Select OK.
Black/White List
The FortiGate unit uses both an IP address list and an email address list to filter
incoming email, if enabled in the protection profile.
When performing an IP address list check, the FortiGate unit compares the IP
address of the message sender to the IP address list in sequence. When
performing an email list check, the FortiGate unit compares the email address of
the message sender to the email address list in sequence. If a match is found, the
action associated with the IP address or email address is taken. If no match is
found, the message is passed to the next enabled spam filter.
Viewing the antispam IP address list catalog

You can add a maximum of two antispam IP address lists and then select the best
one for each protection profile. To view the antispam IP address list catalog, go to
AntiSpam > Black/White List > IP Address. To view any individual antispam IP
address list, select the edit icon for the list you want to see.

01-30007-0203-20090112 505
Black/White List Antispam
Figure 318:Sample antispam IP address list catalog
Edit
Delete
Create New Add a new IP address list to the catalog.

Name The available name of the antispam IP address lists.
# Entries The number of entries in each antispam IP address list.
Profiles The protection profiles each antispam IP address list has been
applied to.
Comments Optional description of each antispam IP address list.
Delete icon Remove the antispam IP address list from the catalog. The delete
icon is available only if the antispam IP address list is not selected in
any protection profiles.
Edit icon Edit the antispam IP address list, list name, or list comment.
Creating a new antispam IP address list

To add an antispam IP address list to the antispam IP address list catalog, go to
AntiSpam > Black/White List and select Create New.
Figure 319:New AntiSpam IP Address list dialog box

Comments Enter a comment to describe the list, if required.
Viewing the antispam IP address list

Configure the FortiGate unit to filter email from specific IP addresses. The
FortiGate unit compares the IP address of the sender to the check list in
sequence. Mark each IP address as clear, spam, or reject. Filter single IP
addresses or a range of addresses at the network level by configuring an address
and mask.

506 01-30007-0203-20090112
To view the antispam IP address list, go to AntiSpam > Black/White List > IP
Address and select the edit icon of the antispam IP address list you want to view.
Figure 320:Sample IP address list

Remove All Entries
Current Page
Move To
Edit
Delete
Name Antispam IP address list name. To change the name, edit text in the
name field and select OK.
Comments Optional comment. To add or edit a comment, enter text in the
comments field and select OK.
Create New Add an IP address to the antispam IP address list.
the IP address list.
Remove All Entries Clear the table.
icon
IP address/Mask The list of IP addresses.
Action The action to take on email from the configured IP address. Actions
are: Spam to apply the configured spam action, Clear to bypass this
and remaining spam filters, or Reject (SMTP only) to drop the
session.
If an IP address is set to reject but mail is delivered from that IP
address via using POP3 or IMAP, the email messages will be marked
as spam.
Delete icon Remove the address from the list.
Edit icon Edit address information.
Move To icon Select to move the entry to a different position in the list.
The firewall policy executes the list from top to bottom. For example, if
you have IP address 192.168.100.1 listed as spam and
192.168.100.2 listed as clear, you must put 192.168.100.1 above
192.168.100.2 for 192.168.100.1 to take effect.
Adding an antispam IP address

After creating an IP address list, you can add IP addresses to the list.
Enter an IP address or a pair of IP address and mask in the following formats:
• x.x.x.x, for example, 192.168.69.100.
• x.x.x.x/x.x.x.x, for example, 192.168.69.100/255.255.255.0
• x.x.x.x/x, for example, 192.168.69.100/24

01-30007-0203-20090112 507
Black/White List Antispam
To add an IP address go to AntiSpam > Black/White List > IP Address. For the IP
address list name to which you want to add an IP address, select Edit. Then select
Create New.
IP Address/Mask Enter the IP address or the IP address/mask pair.

Action Select: Mark as Spam to apply the spam action configured in the
protection profile, Mark as Clear to bypass this and remaining spam
filters, or Mark as Reject (SMTP only) to drop the session.
Enable Select to enable the address.
Viewing the antispam email address list catalog

You can add a maximum of two antispam email address lists and then select the best
one for each protection profile. To view the antispam email address list catalog, go to
AntiSpam > Black/White List > E-mail Address. To view any individual antispam
email address list, select the edit icon for the list you want to see.
Figure 321:Sample antispam email address list catalog
Edit
Delete
Create New Create a new antispam address list.

Name Antispam email address lists.
# Entries The number of entries in each antispam email address list.
Profiles The protection profiles each antispam email address list has been
applied to.
Comments Optional description of each antispam email address list.
Delete icon Remove the antispam email address list from the catalog. The delete
icon is only available if the antispam email address list is not selected
in any protection profiles.
Edit icon Edit the antispam email address list, list name, or list comment.
You enable antispam email addresses in protection profiles. For more information, see
“Spam Filtering options” on page 373.
Creating a new antispam email address list

To add an antispam email address list to the antispam email address list catalog, go to
AntiSpam > Black/White List > E-mail Address and select Create New.
Figure 322:New AntiSpam E-mail Address list dialog box

508 01-30007-0203-20090112

Viewing the antispam email address list

The FortiGate unit can filter email from specific senders or all email from a domain
(such as example.net).
To view the antispam email address list, go to AntiSpam > Black/White List >
E-mail Address and select the edit icon of the antispam email address list you
want to view.
Figure 323:Sample email address list

Current Page
Delete
Edit
Move To
Remove All Entries
Name Antispam email address list name. To change the name, edit text in
the name field and select OK.
Comments Optional comment. To add or edit comment, enter text in comment
Create New Add an email address to the email address list.
the IP address list.
Remove All Entries Clear the table.
icon
Email address The list of email addresses.
Pattern Type The pattern type used in the email address entry.
Action The action to take on email from the configured address. Actions are:
Spam to apply the spam action configured in the protection profile, or
Clear to let the email message bypass this and remaining spam
filters.
Delete icon Remove the email address from the list.
Edit icon Edit the address information.
Move To icon Move the entry to a different position in the list.
The firewall policy executes the list from top to bottom. For example,
if you have abc@example.com listed as clear and *@example.com
as spam, you must put abc@example.com above *@example.com
for abc@example.com to take effect.

01-30007-0203-20090112 509
Advanced antispam configuration Antispam
Configuring the antispam email address list

To add an email address or domain to a list, go to AntiSpam > Black/White List >
E-mail Address. Select the Edit icon beside the list you want to add the address
to. Select Create New, enter the information below and select OK.
Figure 324:Add E-mail Address
E-Mail Address Enter the email address.

Pattern Type Select a pattern type: Wildcard or Regular Expression. For more
information, see “Using wildcards and Perl regular expressions” on
page 511.
Action Select: Mark as Spam to apply the spam action configured in the
protection profile, or Mark as Clear to bypass this and remaining
spam filters.
Enable Select to enable the email address for spam checking.
Advanced antispam configuration

Advanced antispam configuration covers only command line interface (CLI)
commands not represented in the web-based manager. For complete descriptions
and examples of how to use CLI commands, see the FortiGate CLI Reference.
config spamfilter mheader

Use this command to configure email filtering based on the MIME (Multipurpose
Internet Mail Extensions) header. MIME header filtering is enabled within each
protection profile.
The FortiGate unit compares the MIME header key-value pair of incoming email to
the list pair in sequence. If a match is found, the corresponding action is taken. If
no match is found, the email is passed on to the next spam filter.
MIME headers are added to email to describe content type and content encoding,
such as the type of text in the email body or the program that generated the email.
Some examples of MIME headers include:
• X-mailer: outgluck
• X-Distribution: bulk
• Content_Type: text/html
• Content_Type: image/jpg
The first part of the MIME header is called the header or header key. The second
part is called the value. Spammers often insert comments into header values or
leave them blank. These malformed headers can fool some spam and virus filters.
Use the MIME headers list to mark email from certain bulk mail programs or with
certain types of content that are common in spam messages. Mark the email as
spam or clear for each header configured.

510 01-30007-0203-20090112
Antispam Using wildcards and Perl regular expressions
config spamfilter dnsbl

Use this command to configure email filtering using DNS-based Blackhole List
(DNSBL), and Open Relay Database List (ORDBL) servers. DNSBL and ORDBL
filtering is enabled within each protection profile.
The FortiGate unit compares the IP address or domain name of the sender to any
database lists configured, in sequence. If a match is found, the corresponding
action is taken. If no match is found, the email is passed on to the next spam filter.
Some spammers use unsecured third party SMTP servers to send unsolicited
bulk email. Using DNSBLs and ORDBLs is an effective way to tag or reject spam
as it enters the network. These lists act as domain name servers that match the
domain of incoming email to a list of IP addresses known to send spam or allow
spam to pass through.
There are several free and subscription servers available that provide reliable
access to continually updated DNSBLs and ORDBLs. Check with the service you
are using to confirm the correct domain name for connecting to the server.
Note: Because the FortiGate unit uses the server domain name to connect to the DNSBL
or ORDBL server, it must be able to look up this name on the DNS server. For information
on configuring DNS, see “Configuring Networking Options” on page 135.
Using wildcards and Perl regular expressions

Email address list, MIME headers list, and banned word list entries can include
wildcards or Perl regular expressions.
See http://perldoc.perl.org/perlretut.html for detailed information about using Perl
regular expressions.
Regular expression vs. wildcard match pattern

A wildcard character is a special character that represents one or more other
characters. The most commonly used wildcard characters are the asterisk (*),
which typically represents zero or more characters in a string of characters, and
the question mark (?), which typically represents any one character.
In Perl regular expressions, the ‘.’ character refers to any single character. It is
similar to the ‘?’ character in wildcard match pattern. As a result:
• fortinet.com not only matches fortinet.com but also fortinetacom, fortinetbcom,
fortinetccom, and so on.
To match a special character such as '.' and ‘*’ use the escape character ‘\’. For
example:
• To match fortinet.com, the regular expression should be: fortinet\.com
In Perl regular expressions, ‘*’ means match 0 or more times of the character
before it, not 0 or more times of any character. For example:
• forti*.com matches fortiiii.com but does not match fortinet.com
To match any character 0 or more times, use ‘.*’ where ‘.’ means any character
and the ‘*’ means 0 or more times. For example, the wildcard match pattern
forti*.com should therefore be fort.*\.com.

01-30007-0203-20090112 511
Using wildcards and Perl regular expressions Antispam
Word boundary
In Perl regular expressions, the pattern does not have an implicit word boundary.
For example, the regular expression “test” not only matches the word “test” but
also any word that contains “test” such as “atest”, “mytest”, “testimony”, “atestb”.
The notation “\b” specifies the word boundary. To match exactly the word “test”,
the expression should be \btest\b.
Case sensitivity
Regular expression pattern matching is case sensitive in the web and antispam
filters. To make a word or phrase case insensitive, use the regular expression /i.
For example, /bad language/i will block all instances of “bad language”,
regardless of case.
Perl regular expression formats

Table 48 lists and describes some example Perl regular expression formats.
Table 48: Perl regular expression formats
Expression Matches
abc “abc” (the exact character sequence, but anywhere in the string)
âbc “abc” at the beginning of the string
abc$ “abc” at the end of the string
a|b Either of “a” and “b”
âbc|abc$ The string “abc” at the beginning or at the end of the string
ab{2,4}c “a” followed by two, three or four “b”s followed by a “c”
ab{2,}c “a” followed by at least two “b”s followed by a “c”
ab*c “a” followed by any number (zero or more) of “b”s followed by a “c”
ab+c “a” followed by one or more b's followed by a c
ab?c “a” followed by an optional “b” followed by a” c”; that is, either “abc” or”
ac”
a.c “a” followed by any single character (not newline) followed by a” c “
a\.c “a.c” exactly
[abc] Any one of “a”, “b” and “c”
[Aa]bc Either of “Abc” and “abc”
[abc]+ Any (nonempty) string of “a”s, “b”s and “c”s (such as “a”, “abba”,
”acbabcacaa”)
[âbc]+ Any (nonempty) string which does not contain any of “a”, “b”, and “c”
(such as “defg”)
\d\d Any two decimal digits, such as 42; same as \d{2}
/i Makes the pattern case insensitive. For example, /bad language/i
blocks any instance of bad language regardless of case.
\w+ A “word”: A nonempty sequence of alphanumeric characters and low
lines (underscores), such as foo and 12bar8 and foo_1
100\s*mk The strings “100” and “mk” optionally separated by any amount of white
space (spaces, tabs, newlines)

512 01-30007-0203-20090112
Antispam Using wildcards and Perl regular expressions
Table 48: Perl regular expression formats (Continued)

abc\b “abc” when followed by a word boundary (for example, in “abc!” but not in
“abcd”)
perl\B “perl” when not followed by a word boundary (for example, in “perlert” but
not in “perl stuff”)
\x Tells the regular expression parser to ignore white space that is neither
preceded by a backslash character nor within a character class. Use this
to break up a regular expression into (slightly) more readable parts.
/x Used to add regular expressions within other text. If the first character in
a pattern is forward slash '/', the '/' is treated as the delimiter. The pattern
must contain a second '/'. The pattern between ‘/’ will be taken as a
regular expressions, and anything after the second ‘/’ will be parsed as a
list of regular expression options ('i', 'x', etc). An error occurs if the
second '/' is missing. In regular expressions, the leading and trailing
space is treated as part of the regular expression.
Example regular expressions
Block any word in a phrase

/block|any|word/
Block purposely misspelled words

Spammers often insert other characters between the letters of a word to fool spam
blocking software.
/^.*v.*i.*a.*g.*r.*o.*$/i
/cr[eéèêë][\+\-
\*=<>\.\,;!\?%&§@\^°\$£€\{\}()\[\]\|\\_01]dit/i
Block common spam phrases

The following phrases are some examples of common phrases found in spam
messages.
/try it for free/i
/student loans/i
/you’re already approved/i
/special[\+\-
\*=<>\.\,;!\?%&~#§@\^°\$£€\{\}()\[\]\|\\_1]offer/i

01-30007-0203-20090112 513
Using wildcards and Perl regular expressions Antispam

514 01-30007-0203-20090112
IM, P2P & VoIP Overview
IM, P2P & VoIP

The IM, P2P & VoIP menu provides IM user management tools and statistics for
network IM, P2P, and VoIP usage.
IM/P2P/VoIP management settings are configured per firewall profile. IM, P2P,
and VoIP protocols must be enabled in the active protection profile for the settings
in this section to have any effect.
If you enable virtual domains (VDOMs) on the FortiGate unit, IM, P2P, and VoIP is
available separately for each virtual domain. For details, see “Using virtual
FortiOS uses IPS signatures to detect IM/P2P/VoIP sessions. See the following
sections for details.
• Overview
• Configuring IM/P2P/VoIP protocols
• Statistics
• User
Overview
Instant Messenger (IM), Peer to Peer (P2P), and Voice over Internet Protocol
(VoIP) protocols are gaining in popularity as an essential way to communicate
between two or more individuals in real time. Some companies even rely on IM
protocols for critical business applications such as Customer/Technical Support.
The most common IM protocols in use today include AOL Instant Messenger,
Yahoo Instant Messenger, MSN messenger, and ICQ. Although these are the
most popular ones, there are always new protocols being developed as well as
newer versions of older ones.
P2P protocols are most commonly used to transfer files from one user to another
and can use large amounts of bandwidth.
VoIP is increasingly being used by businesses to cut down on the cost of long
distance voice communications.
Some organizations need to control or limit the use of IM/P2P and VoIP protocols
in order to more effectively manage bandwidth use.
With FortiOS firmware, you can control and monitor the usage of IM/P2P
applications and VoIP protocols.
FortiOS supports two VoIP protocols: Session Initiation Protocol (SIP) and Skinny
Client Control Protocol (SCCP).
Fortinet Inc. recognizes that IM/P2P applications are becoming part of doing
business but also, if abused, can seriously decrease productivity and network
performance.

01-30007-0203-20090112 515
Overview IM, P2P & VoIP
FortiGate units allow you to set up user lists that either allow or block the use of
applications, to determine which applications are allowed and how much
bandwidth can be used by the applications.
By combining comprehensive protection policies and easy-to-view statistical
reports, you can see which applications are being used and for what purpose,
making it easy to control IM/P2P applications and to maximize productivity.
The FortiOS system comes with an impressive list of supported IM/P2P protocols
and can be kept up-to-date with upgrades available for download from the Fortinet
Distribution Network. There is no need to wait for firmware upgrade to stay ahead
of the latest protocols.
FortiOS also provides ways for you to deal with unknown protocols even before
upgrades are available. For details, see “Configuring IPS signatures for
unsupported IM/P2P protocols” on page 518.
FortiOS uses IPS signatures to detect IM/P2P/VoIP sessions. Table 49 on
page 516 lists the IM/P2P/VoIP applications that are currently recognized by
FortiOS. The table includes the IPS signatures, the applications associated with
the signatures, and the locations of the signatures
Note: Applications in Table 49 on page 516 marked as bold can connect to multiple P2P
networks. Turning on IM and P2P signatures will help improve IPS performance. For
example, if you want to use IPS, but you do not want to block IM or P2P applications, you
should leave IM/P2P signatures enabled. Normally, if you turn off other signatures, the
performance will be better, but for IM/P2P, it is the opposite.
Table 49: IM/P2P applications covered by FortiOS 3.0
IPS Applications
Instant Messaging
AIM (Firewall > Protection Profile > IM/P2P) AIM, AIM Triton
ICQ (Firewall > Protection Profile > IM/P2P) ICQ
MSN (Firewall > Protection Profile > IM/P2P) MSN Messenger
SIMPLE (Firewall > Protection Profile > IM/P2P) SIMPLE
qq (Intrusion Protection > Signature > Predefined > qq) QQ
Yahoo! (Firewall > Protection Profile > IM/P2P) Yahoo Messenger
msn_web_messenger (Intrusion Protection > Signature > MSN web Messenger
Predefined > msn_web_messenger)
google_talk (Intrusion Protection > Signature > Google Instant Messenger
Predefined > google_talk)
rediff (Intrusion Protection > Signature > Predefined > Rediff Instant Messenger
rediff)
P2P
BitComet
Bitspirit
BitTorrent (Firewall > Protection Profile > IM/P2P)
Azureus
Shareaza
eMule
Overnet
Edonkey2K
eDonkey (Firewall > Protection Profile > IM/P2P) Shareaza
BearShare
MLdonkey
iMesh

516 01-30007-0203-20090112
IM, P2P & VoIP Configuring IM/P2P/VoIP protocols
Table 49: IM/P2P applications covered by FortiOS 3.0

BearShare
Shareaza
LimeWire
Xolox
Swapper
iMesh
MLdonkey
Gnucleus
Gnutella (Firewall > Protection Profile > IM/P2P)
Morpheus
Openext
Mutella
Qtella
Qcquisition
Acquisition
NapShare
gtk-gnutella
KaZaA (Firewall > Protection Profile > IM/P2P) KaZaA
Skype (Firewall > Protection Profile > IM/P2P) Skype
WinNY (Firewall > Protection Profile > IM/P2P) WinNY
ares (Intrusion Protection > Signature > Predefined > Ares Galaxy
Ares.Connect.Detection and Ares.Search.Detection)
VoIP
SIP (Firewall > Protection Profile > VoIP) SIP
SCCP (Firewall > Protection Profile > VoIP) SCCP
Configuring IM/P2P/VoIP protocols

There are several places and steps you can configure the IM/P2P/VoIP protocols.
• Go to Intrusion Protection > IPS Sensor to configure the IM/P2P/VoIP
signatures. See “Configuring IM/P2P/VoIP IPS signatures” on page 517.
• Go to Intrusion Protection > Signature > Custom to create custom
signatures for any unsupported protocols. See “Configuring IPS signatures for
unsupported IM/P2P protocols” on page 518.
• Go to IM, P2P & VoIP > User > Config to configure IM settings for unknown
users. See “Configuring a policy for unknown IM users” on page 523.
• Go to Firewall > Protection Profile to configure the IM/P2P/VoIP settings.
See “Configuring IM/P2P/VoIP options within a protection profile” on page 518.
• Finally, go to Firewall > Policy to create policies to use all the settings. See
“Configuring firewall policies” on page 297.
Configuring IM/P2P/VoIP IPS signatures

Since FortiOS uses IPS signatures to detect the IM/P2P/VoIP sessions, you can
configure the IPS sensors and apply the sensors to the protections profiles to
meet your requirements.
Use the filters in the IPS sensor to find the relevant signatures you want to
configure. See details, see “Configuring IPS sensors” on page 470.

01-30007-0203-20090112 517
Statistics IM, P2P & VoIP
Configuring IPS signatures for unsupported IM/P2P protocols

If you find a protocol that is not supported, ensure that the IPS package is up to
date. If the IPS package is up to date and the protocol is still not supported, you
can use the custom signature.
To create a custom signature

1 Go to Intrusion Protection > Signature > Custom > Create New.
2 Enter a name for the signature.
3 Enter the signature.
4 Select OK.
Note: To detect new IM/P2P applications or new versions of the existing

applications, you only need to update the IPS package, available through the
FortiNet Distribution Network (FDN). No firmware upgrade is needed.
Configuring IM/P2P/VoIP options within a protection profile

There are several areas within a protection profile where you can configure the
IM/P2P/VoIP settings. For more detailed information, see the Firewall Profile
chapter of this guide and the IP, P2P and VoIP Technical Note.
Configuring older versions of IM/P2P applications

Some older versions of IM protocols are able to bypass file blocking because the
message types are not recognized.
Supported IM protocols include:
• MSN 6.0 and above
• ICQ 4.0 and above
• AIM 5.0 and above
• Yahoo 6.0 and above
If you want to block a protocol that is older than the ones listed above, use the CLI
command: For details see the FortiGate CLI Reference.
config imp2p old-version.
Statistics
You can view the IM, P2P and VoIP statistics to gain insight into how the protocols
are being used within the network. Overview statistics are provided for all
supported IM, P2P and VoIP protocols. Detailed individual statistics are provided
for each IM protocol.
Viewing overview statistics

The Summary tab provides a summary of statistics for all IM, P2P and VoIP
protocols.
To view IM/P2P statistics, go to IM/P2P&VoIP > Statistics > Summary.

518 01-30007-0203-20090112
IM, P2P & VoIP Statistics
Figure 325:IM, P2P and VoIP statistics summary
The Summary tab has the following icons and features:
Automatic Refresh Select the automatic refresh interval for statistics. Set the interval
Interval from none to 30 seconds.
Refresh Click to refresh the page with the latest statistics.
Reset Stats Click to reset the statistics to zero.
Users For each IM protocol, the following user information is listed:
• Current Users
• (Users) Since Last Reset
• (Users) Blocked.
Chat For each IM protocol, the following chat information is listed:
• Total Chat Sessions
• Total Messages.
File Transfers For each IM protocol, the following file transfer information is
listed:
(File transfers) Since Last Reset and (File transfers) Blocked.
Voice Chat For each IM protocol, the following voice chat information is listed:
• (Voice chats) Since Last Reset
• (Voice chats) Blocked.

01-30007-0203-20090112 519
Statistics IM, P2P & VoIP
P2P Usage For each P2P protocol, the following usage information is listed:
• Total Bytes transferred
• Average Bandwidth.
When configuring the IM/P2P settings in a protection profile (see
“IM/P2P options” on page 378), you can select Block, Pass, or
Rate limit for the P2P protocols.
If the action for a protocol is set to Block, the statistics will be zero.
If the action for a protocol is set to pass, the statistics will display
the total usage of the P2P application by all the firewall policies.
If the action for a protocol is set to Rate Limit, the statistics will
display the total P2P usage either by all policies or a protection
profile, depending on whether your P2P rate limit settings are per
policy or per profile.
The bandwidth limit can be applied separately for each firewall
policy that uses the protection profile, or shared by all firewall
policies that use the protection profile. By default, the limit is
applied separately to each firewall policy. For information on
configuring per policy or per protection profile P2P bandwidth
limiting, see P2P rate limiting option in the FortiGate CLI
Reference.
VoIP Usage For SIP and SCCP protocol, the following information is listed:
• Active Sessions (phones connected)
• Total calls (since last reset)
• Calls failed/Dropped
• Calls Succeeded
Viewing statistics by protocol

The protocol tab provides detailed statistics for individual IM protocols.
To view protocol statistics, go to IM, P2P & VoIP > Statistics > Protocol.
You can log IM chat information and the limitations placed on it, by enabling
Archive full IM chat info to FortiAnalyzer in the protection profile.
Figure 326:IM statistics by Protocol
The IM/P2P Protocol tab has the following icons and features:

520 01-30007-0203-20090112
IM, P2P & VoIP User
Automatic Refresh Select the automatic refresh interval for statistics. Set the interval
Interval from none to 30 seconds.
Protocol Select the protocol for which statistics are to be displayed: AIM,
ICQ, MSN, or Yahoo.
Users For the selected protocol, the following user information is
displayed: Current Users, (Users) Since Last Reset, and (Users)
Blocked.
Chat For the selected protocol, the following chat information is
displayed: Total Chat Sessions, Server-based Chat, Group Chat,
and Direct/Private Chat.
Messages For the selected protocol, the following message information is
displayed: Total Messages, (Messages) Sent, and (Messages)
Received.
File Transfers For the selected protocol, the following file transfer information is
displayed: (File transfers) Since Last Reset, (File transfers) Sent,
(File transfers) Received, and (File transfers) Blocked.
Voice Chat For the selected protocol, the following voice chat information is
displayed: (Voice chats) Since Last Reset and (Voice chats)
Blocked.
User
After IM users connect through the firewall, the FortiGate unit displays which
users are connected in the Current Users list. You can analyze the list and decide
which users to allow or block. A policy can be configured to deal with unknown
users.
Note: If virtual domains are enabled on the FortiGate unit, IM features are configured
globally. To access these features, select Global Configuration on the main menu.
Viewing the Current Users list

The Current User list displays information about instant messaging users who are
currently connected. The list can be filtered by protocol.
To view current users, go to IM, P2P & VoIP > Users > Current User.
Figure 327:Current Users list
The Current Users list has the following features:
Protocol Filter the list by selecting the protocol for which to display current
users: AIM, ICQ, MSN, or Yahoo. All current users can also be
displayed.
Protocol The protocol being used.
User Name The name selected by the user when registering with an IM
protocol. The same user name can be used for multiple IM
protocols. Each user name/protocol pair appears separately in the
list.
Source IP The Address from which the user initiated the IM session.

01-30007-0203-20090112 521
User IM, P2P & VoIP
Last Login The last time the current user used the protocol.
Block Select to add the user name to the permanent black list. Each
user name/protocol pair must be explicitly blocked by the
administrator.
Viewing the User List

The User List displays information about users who have been allowed access to
(white list) or have been blocked from (black list) instant messaging services.
Users can be added using Create New or from the temporary users list.
To view the User List, go to IM, P2P & VoIP > Users > User List.
Figure 328:User List
The user list has the following icons and features:
Create New Select to add a new user to the list.

Protocol Filter the list by selecting a protocol: AIM, ICQ, MSN, Yahoo, or
All.
Policy Filter the list by selecting a policy: Allow, Deny, or All.
Protocol The protocol associated with the user.
Username The name selected by the user when registering with an IM
list.
Policy The policy applied to the user when attempting to use the protocol:
Block or Deny.
Edit icon Change the following user information: Protocol, Username, and
Policy.
Delete icon Permanently remove users from the User List.
Adding a new user to the User List

Add users to the User List to allow them to access instant messaging services or
to block them from these services.
Go to IM, P2P & VoIP > User > User List and select Create New.
Figure 329:Edit User
Protocol Select a protocol from the dropdown list: AIM, ICQ, MSN, or
Yahoo!
Username Enter a name for the user.
Policy Select a policy from the dropdown list: Allow or Block.

522 01-30007-0203-20090112
IM, P2P & VoIP User
Configuring a policy for unknown IM users

The User Policy determines the action to be taken with unknown users. Unknown
users can be either allowed to use some or all of the IM protocols and added to a
white list, or blocked from using some or all of the IM protocols and added to a
black list. You can later view the white and black lists and add the users to the
user list.
To configure the IM policy, go to IM, P2P & VoIP > User > Config.
Figure 330:IM User policy
Configure or view the following settings for the IM user policy:
Automatically Allow Select the protocols that unknown users are allowed to use. The
unknown users are added to a temporary white list.
Automatically Block Select the protocols to which unknown users are denied access.
The unknown users are added to a temporary black list.
List of Temporary New users who have been added to the temporary white or black
Users lists. User information includes Protocol, Username, and the
Policy applied to the user.
Note: If the FortiGate unit is rebooted, the list is cleared.
Protocol Select a protocol by which to filter the list of temporary users.
Username The name selected by the user when registering with an IM
list.
Policy The policy applied to the user when attempting to use the protocol:
Block or Deny.
Permanently Allow Select to add the user to the permanent white list. The user
remains online and is listed in IM, P2P & VoIP > Users > User List.
Permanently Block Select to add the user to the permanent black list. The user is
listed in IM, P2P & VoIP > Users > User List.
Apply Click to apply the global user policy.

01-30007-0203-20090112 523
User IM, P2P & VoIP

524 01-30007-0203-20090112
Log&Report FortiGate logging
Log&Report
FortiGate units provide extensive logging capabilities for traffic, system and
network protection functions. They also allow you to compile reports from the
detailed log information gathered. Reports provide historical and current analysis
of network activity to help identify security issues that will reduce and prevent
network misuse and abuse.
This section provides information about how to enable logging, view log
messages, and configure reports. If you have VDOMs enabled, see “Using virtual
domains” on page 95 for more information.
• FortiGate logging
• FortiGuard Analysis and Management Service
• Log severity levels
• High Availability cluster logging
• Storing logs
• Log types
• Accessing Logs
• Viewing log information
• Customizing the display of log messages
• Content Archive
• Alert Email
• Reports
Note: If the FortiGate unit is in Transparent mode, certain settings and options for logging
may not be available because certain features do not support logging, or are not available
in Transparent mode. For example, SSL VPN events are not available in Transparent
mode.
FortiGate logging
A FortiGate unit can log many different network activities and traffic including:
• overall network traffic
• system-related events including system restarts, HA and VPN activity
• anti-virus infection and blocking
• web filtering, URL and HTTP content blocking
• signature and anomaly attack and prevention
• spam filtering
• Instant Messaging and Peer-to-Peer traffic
• VoIP telephone calls.

01-30007-0203-20090112 525
FortiGuard Analysis and Management Service Log&Report
When customizing the logging location, you can also customize what minimum log
severity level the FortiGate unit should log these events at. There are six severity
levels to choose from. For more information, see “Log severity levels” on
page 527.
For better log storage and retrieval, the FortiGate unit can send log messages to a
FortiAnalyzer™ unit. FortiAnalyzer units provide integrated log collection, analysis
tools and data storage. Detailed log reports provide historical as well as current
analysis of network activity. Detailed log reports also help identify security issues,
reducing network misuse and abuse. The FortiGate unit can send all log message
types, including quarantine files and content archives, to a FortiAnalyzer unit for
storage. The FortiAnalyzer unit can upload log files to an FTP server for archival
purposes. For more information about configuring the FortiGate unit to send log
messages to a FortiAnalyzer unit, see “Logging to a FortiAnalyzer unit” on
page 529.
If you have a subscription for the FortiGuard Analysis and Management Service,
your FortiGate unit can send logs to a FortiGuard Analysis server. This service
provides another way to store and view logs, as well as archiving email
messages. For more information, see “FortiGuard Analysis and Management
Service” on page 526. Fortinet recommends reviewing the FortiGuard Analysis
and Management Service Administration Guide to learn more about the logging,
reporting, and remote management features from the FortiGuard Analysis and
Management Service portal web site.
The FortiGate unit can also send log messages to either a Syslog server or
WebTrends server for storage and archival purposes. If your FortiGate unit has a
hard disk, you can also send logs to it by using the CLI. For more information
about configuring logging to the hard disk, see the FortiGate CLI Reference.
In the FortiGate web-based manager, you can view log messages available in
system memory, on a FortiAnalyzer unit running firmware version 3.0 or higher, or,
if available, the hard disk. You can use customizable filters to easily locate specific
information within the log files.
For details and descriptions of log messages and formats, see the FortiGate Log
Message Reference.

that provides logging and reporting solutions, as well as remote management
service, for all FortiGate units. The FortiGuard Analysis and Management Service
is available on all FortiGate units running FortiOS 3.0 MR6 and higher.
The logging and reporting side of FortiGuard Analysis and Management Service is
made up of two types of servers, the primary analysis server and the secondary
analysis server. The primary analysis server stores logs generated from the
FortiGate unit. The secondary analysis server provides redundancy, ensuring log
data is available at all times. There are several secondary analysis servers
available for redundancy for each FortiGate unit. The network also includes the
main analysis server, which is responsible for monitoring and maintaining the
primary and secondary analysis servers.

526 01-30007-0203-20090112
Log&Report Log severity levels
When the FortiGate unit connects to the logging and reporting network for the first
time, it retrieves its assigned primary analysis server, contract term, and storage
space quota from the main analysis server. The main analysis server contains this
information so it can maintain and monitor the status of each of the servers.
After configuring logging to the assigned primary analysis server, the FortiGate
unit begins sending encrypted logs to the primary analysis server through TCP
port 514. The connection between the main analysis server and the FortiGate unit
is secured using FCP over HTTPS, through port 443.
Fortinet recommends reviewing the FortiGuard Analysis and Management
Service Administration Guide because it contains very detailed information about
this FortiGuard service. This administration guide contains information about:
• registering your FortiGate unit, or multiple FortiGate units, for this FortiGuard
service
• enabling this FortiGuard service on your FortiGate unit
• configuring remote management and logging and reporting.
Note: After upgrading your FortiGate firmware, you need to re-enter your account ID and
then update the service to re-connect to the servers that support logging and reporting. You
may need to update the service from the portal web site as well.
FortiGuard Analysis and Management Service portal web site

The portal web site provides a central location for managing your information
about the FortiGate units and service account. The portal web site also allows you
to view logs and reports, including remote management services such as
configuration backups.
You need a service account ID, username and password before entering the
portal web site. You receive this information when you register for the FortiGuard
Analysis and Management Service on the Fortinet support web site. After entering
all appropriate information on the Fortinet support web site, you can then log into
the FortiGuard Analysis and Management Service portal web site.
For information about registering, enabling and configuring the FortiGuard
Analysis and Management Service, see the FortiGuard Analysis and
Management Service Administration Guide.
Note: The portal also includes remote management features. For more information about
remotely managing your FortiGate unit using the FortiGuard Analysis and Management
Service, see “System Maintenance” on page 229.
Log severity levels

You can define what severity level the FortiGate unit records logs at when you
configure the logging location. The FortiGate unit logs all messages at and above
the logging severity level you select. For example, if you select Error, the unit logs
Error, Critical, Alert and Emergency level messages.

01-30007-0203-20090112 527
High Availability cluster logging Log&Report
Table 50: Log severity levels
Levels Description
0 - Emergency The system has become unstable.
1 - Alert Immediate action is required.
2 - Critical Functionality is affected.
3 - Error An error condition exists and functionality could be affected.
4 - Warning Functionality could be affected.
5 - Notification Information about normal events.
6 - Information General information about system operations.
The Debug severity level, not shown in Table 50, is rarely used. It is the lowest log
severity level and usually contains some firmware status information that is useful
when the FortiGate unit is not functioning properly. Debug log messages are
generated only if the log severity level is set to Debug. Debug log messages are
generated by all types of FortiGate features.
High Availability cluster logging

When configuring logging with a High Availability (HA) cluster, you configure the
primary unit to send logs to a FortiAnalyzer unit or a Syslog server. The settings
are applied to the subordinate units, which send the log messages to the primary
unit. The primary unit then sends all logs to the FortiAnalyzer unit or Syslog
server.
If you configured a secure connection via an IPSec VPN tunnel between a
FortiAnalyzer unit and a HA cluster, the connection is between the FortiAnalyzer
unit and the HA cluster primary unit.
For more information, see the FortiGate High Availability User Guide.
Storing logs
The type and frequency of log messages you intend to save determines the type
of log storage to use. For example, if you want to log traffic and content logs, you
need to configure the FortiGate unit to log to a FortiAnalyzer unit or Syslog server.
The FortiGate system memory is unable to log traffic and content logs because of
their frequency and large file size.
Storing log messages to one or more locations, such as a FortiAnalyzer unit or
Syslog server, may be a better solution for your logging requirements than the
FortiGate system memory. Configuring your FortiGate unit to log to a FortiGuard
Analysis server may also be a better log storage solution if you do not have a
FortiAnalyzer unit and want to create reports. This particular log storage solution
is available to all FortiGate units running FortiOS 3.0 MR6 or higher, through a
subscription to the FortiGuard Analysis and Management Service. For more
information, see “FortiGuard Analysis and Management Service” on page 526.
If your FortiGate unit has a hard disk, you can also enable logging to the hard disk
from the CLI. See the FortiGate CLI Reference for more information before
enabling logging to the hard disk.

528 01-30007-0203-20090112
Log&Report Storing logs
If you require logging to multiple FortiAnalyzer units or Syslog servers, see the
Note: Daylight Saving Time (DST) is now extended by four weeks in the United States and
Canada and may affect your location. It is recommended to verify if your location observes
this change, since it affects the scope of the report. Fortinet has released supporting
firmware. See the Fortinet Knowledge Center article, New Daylight Saving Time support,
for more information.
Logging to a FortiAnalyzer unit

FortiAnalyzer units are network devices that provide integrated log collection,
analysis tools and data storage. Detailed log reports provide historical as well as
current analysis of network activity to help identify security issues and reduce
network misuse and abuse.
You can configure the FortiGate unit to log up to three FortiAnalyzer units. The
FortiGate unit sends logs to all three FortiAnalyzer units. Each FortiAnalyzer unit
stores the same information. Logging to multiple FortiAnalyzer units provides
real-time backup protection in the event one of the FortiAnalyzer units fails. You
can configure logging to multiple FortiAnalyzer units only in the CLI. For more
Figure 331:Configuring a connection to the FortiAnalyzer unit
Expand
Arrow
To configure the FortiGate unit to send logs to the FortiAnalyzer unit

1 Go to Log&Report > Log Config > Log Setting.
2 Select the Expand Arrow beside Remote Logging to reveal the available options.
3 Select FortiAnalyzer.
4 From the Minimum log level list, select one of the following:
Emergency The system in unusable.
Alert Immediate action is required.
Critical Functionality is affected.
Error An erroneous condition exists and functionality is probably
affected.
Warning Functionality might be affected.
Notification Information about normal events.
Information General information about system operations.
Debug Information used for diagnosing or debugging the FortiGate unit.

01-30007-0203-20090112 529
Storing logs Log&Report
5 Select Static IP Address.

6 Enter the static IP address of the FortiAnalyzer unit in the Static IP Address field.
7 Select Apply.
The FortiAnalyzer unit needs to be configured to receive logs from the FortiGate
unit after you have configured log settings on the FortiGate unit. Contact a
FortiAnalyzer administrator to complete the rest of the configuration.
Note: You cannot configure a FortiAnalyzer unit to be a backup solution for the FortiGuard
Analysis server, and vice versa. If you require a backup solution for one of these logging
devices, using a Syslog server or WebTrends server is preferred.
Connecting to FortiAnalyzer using Automatic Discovery

You can connect to a FortiAnalyzer unit by using the Automatic Discovery feature.
This feature allows the FortiGate unit to find a FortiAnalyzer unit that is on the
network within the same subnet.
When you select Automatic Discovery, the FortiGate unit uses HELLO packets to
locate any FortiAnalyzer units available on the network within the same subnet.
When the FortiGate unit discovers the FortiAnalyzer unit, the FortiGate unit
automatically begins sending log data, if logging is configured for traffic and other
events, to the FortiAnalyzer unit.
The Automatic Discovery feature must be enabled on the FortiAnalyzer side to
work properly. The FortiAnalyzer unit requires 3.0 firmware (and higher) to use
this feature. Fortinet recommends contacting a FortiAnalyzer administrator to
verify Automatic Discovery is enabled on the FortiAnalyzer unit before using this
feature.
To enable automatic discovery

3 Select FortiAnalyzer.
4 Select Automatic Discovery.
5 Select a FortiAnalyzer unit from the Connect To list, if available.
If no FortiAnalyzer unit is available, contact a FortiAnalyzer administrator to verify
if there is one on the network.
6 Select Discover.
The FortiGate unit searches within the same subnet for a response from any
available FortiAnalyzer units.
7 Select Apply.
Note: If your FortiGate unit is in Transparent mode, you must modify the interface in the CLI
before Automatic Discovery can carry traffic. Use the procedure in the Fortinet Knowledge
Center article, Fortinet Discovery Protocol in Transparent mode, to enable the interface to
also carry traffic when using the Automatic Discovery feature.

530 01-30007-0203-20090112
Testing the FortiAnalyzer configuration

After configuring FortiAnalyzer settings, test the connection between the
FortiGate unit and FortiAnalyzer unit to verify both devices are communicating
properly. During testing, the FortiGate unit displays information about specific
settings for transmitting and receiving logs, reports, content archive and
quarantine files.
The FortiGate unit must learn the IP address of the FortiAnalyzer unit before
testing the connection. A false test report failure may result if testing the
connection occurs before the FortiGate unit learns the IP address of the
FortiAnalyzer unit.
To test the connection

3 Select Test Connectivity.
Figure 332:Test Connectivity with FortiAnalyzer
FortiAnalyzer The name of the FortiAnalyzer unit. The default name of a

(Hostname) FortiAnalyzer unit is its product name, for example, FortiAnalyzer-400.
FortiGate The serial number of the FortiGate unit.
(Device ID)
Registration The status of whether or not the FortiGate unit is registered with the
Status FortiAnalyzer unit. If the FortiGate unit is unregistered, it may not have
full privileges. For more information, see the FortiAnalyzer
Administration Guide.
Connection The connection status between FortiGate and FortiAnalyzer units. A
Status green check mark indicates there is a connection and a gray X
indicates there is no connection.
Disk Space (MB) The amount of disk space, in MB, on the FortiAnalyzer unit for logs.
Allocated The amount of space designated for logs, including
Space quarantine files and content archives.

01-30007-0203-20090112 531
Used Space The amount of used space.

Total Free The amount of unused space.
Space
Privileges The permissions of the device for sending and viewing logs, reports,
content archives, and quarantined logs.
• Tx indicates the FortiGate unit is allowed to transmit log packets to
the FortiAnalyzer unit.
• Rx indicates the FortiGate unit is allowed to display reports and logs
stored on the FortiAnalyzer unit.
A check mark indicates the FortiGate unit has permissions to send or
view log information and reports. An X indicates the FortiGate unit is
not allowed to send or view log information.
You can also test the connection status between the FortiGate unit and the
FortiAnalyzer unit by using the following CLI command:
execute log fortianalyzer test-connectivity
The command displays the connection status and the amount of disk usage in
percent. For more information, see the FortiGate CLI Reference.
Note: The test connectivity feature also provides a warning when a FortiGate unit requires
a higher-end FortiAnalyzer unit or when the maximum number of VDOMs/FortiGate units
has been reached on the FortiAnalyzer unit.
Logging to a FortiGuard Analysis server

You can configure logging to a FortiGuard Analysis server after registering for the
FortiGuard Analysis and Management Service on the Fortinet support web site.
Fortinet recommends verifying that the connection is working properly before
configuring logging to a FortiGuard Analysis server.
You can enable FortiGate features from the FortiGate web-based manager. For
more information, see “Log types” on page 535. Logging traffic, as well as
summary and email content archiving, is also available.
To log to a FortiGuard Analysis server

1 Go to Log&Report > Log Config.
3 Select FortiGuard Analysis Service.
4 Enter the account ID in the Account ID field.
5 Select one of the following:
Overwrite oldest Deletes the oldest log entry and continues logging when the
logs maximum log disk space is reached.
Do not log Stops log messages going to the FortiGuard Analysis server when
the maximum log disk space is reached.
6 Select a severity level.

7 Select Apply.

532 01-30007-0203-20090112
Logging to memory
The FortiGate system memory has a limited capacity for log messages. The
FortiGate system memory displays only the most recent log entries. It does not
store traffic and content logs in system memory due to their size and the
frequency of log entries. When the system memory is full, the FortiGate unit
overwrites the oldest messages. All log entries are cleared when the FortiGate
unit restarts.
If your FortiGate unit has a hard disk, use the CLI to enable logging to it. You can
also upload logs stored on the hard disk to a FortiAnalyzer unit. For more
To configure the FortiGate unit to save logs in memory

2 Select the check box beside Memory.
3 Select the Expand Arrow beside the check box to reveal the available Memory
options.
4 Select a severity level.
The FortiGate unit logs all messages at and above the logging severity level you
select. For details on the logging levels, see Table 50, “Log severity levels,” on
page 528.
Note: You can configure logging to an AMC disk and schedule when to upload logs to a
FortiAnalyzer unit.
The AMC disk is available on FortiGate-3600A, FortiGate-3016B and FortiGate-3810A
units.
Logging to a Syslog server

A Syslog server is a remote computer running Syslog software and is an industry
standard for logging. Syslog is used to capture log information provided by
network devices. The Syslog server is both a convenient and flexible logging
device, since any computer system, such as Linux, Unix, and Intel-based
Windows can run syslog software.
When configuring logging to a Syslog server, you need to configure the facility and
log file format, normal or Comma Separated Values (CSV). The CSV format
contains commas whereas the normal format contains spaces. Logs saved in the
CSV file format can be viewed in a spread-sheet application, while logs saved in
normal format are viewed in a text editor (such as Notepad) because they are
saved as plain text files.
Configuring a facility easily identifies the device that recorded the log file.
Figure 333:Logging to a Syslog server

01-30007-0203-20090112 533
To configure the FortiGate unit to send logs to a syslog server

2 Select the check box beside Syslog.
3 Select the Expand Arrow beside the check box to reveal the Syslog options.
4 Set the following syslog options:
Name/IP The domain name or IP address of the syslog server.

Port The port number for communication with the syslog server, typically
port 514.
Minimum log The FortiGate unit logs all messages at and above the logging
level severity level you select. For more information about the logging
levels, see Table 50, “Log severity levels,” on page 528.
Facility Facility indicates to the syslog server the source of a log message.
By default, FortiGate reports Facility as local7. You may want to
change Facility to distinguish log messages from different FortiGate
units.
Enable CSV If you enable CSV format, the FortiGate unit produces the log in
Format Comma Separated Value (CSV) format. If you do not enable CSV
format the FortiGate unit produces plain text files.
5 Select Apply.
Note: If more than one Syslog server is configured, the Syslog servers and their settings
appear on the Log Settings page. You can configure multiple Syslog servers in the CLI. For
more information, see the FortiGate CLI Reference.
Logging to WebTrends
WebTrends is a remote computer running a NetIQ WebTrends firewall reporting
server. FortiGate log formats comply with WebTrends Enhanced Log Format
(WELF) and are compatible with NetIQ WebTrends Security Reporting Center and
Firewall Suite 4.1.
Use the CLI to configure the FortiGate unit to send log messages to WebTrends.
After logging into the CLI, enter the following commands:
config log webtrends setting
set server <address_ipv4>
set status {disable | enable}
end
Keywords and variables Description Default

server <address_ipv4> Enter the IP address of the WebTrends No default.
server that stores the logs.
status Enter enable to enable logging to a disable
{disable | enable} WebTrends server.
Example
This example shows how to enable logging to a WebTrends server and to set an
IP address for the server.

534 01-30007-0203-20090112
Log&Report Log types
config log webtrends setting

set status enable
set server 172.16.125.99
end
For more information about setting the options for the types of logs sent to
WebTrends, see the Log chapter in the FortiGate CLI Reference.
Log types
The FortiGate unit provides a wide range of features to log, enabling you to better
monitor activity that is occurring on your network. For example, you can enable
logging of IM/P2P features, to obtain detailed information on the activity occurring
on your network where IM/P2P programs are used.
This topic also provides details on each log type and explains how to enable
logging of the log type.
Before enabling FortiGate features, you need to configure what type of logging
device will store the logs. For more information, see “Storing logs” on page 528.
Note: If the FortiGate unit is in Transparent mode, certain settings and options for logging
may not be available because they do not support logging, or are not available in
Transparent mode. For example, SSL VPN events are not available in Transparent mode.
Traffic log
The Traffic log records all the traffic to and through the FortiGate interfaces. You
can configure logging of traffic controlled by firewall policies and for traffic
between any source and destination addresses. You can also filter to customize
the traffic logged:
• Allowed traffic – The FortiGate unit logs all traffic that is allowed according to
the firewall policy settings.
• Violation traffic – The FortiGate unit logs all traffic that violates the firewall
policy settings.
If you are logging “other-traffic”, the FortiGate unit will incur a higher system load
because “other-traffic” logs log individual traffic packets. Fortinet recommends
logging firewall policy traffic since it minimizes the load. Logging “other-traffic” is
disabled by default.
Note: You need to set the logging severity level to Notification when configuring a logging
location to record traffic log messages. Traffic log messages generally have a severity level
no higher than Notification. If VDOMs are in Transparent mode, make sure that VDOM
allows access for enabling traffic logs.
Enabling firewall policy traffic logging

Firewall policy traffic logging records the traffic that is both permitted and denied
by the firewall policy, based on the protection profile. Firewall policy traffic logging
records packets that match the policy. This method of traffic logging is preferred
because it reduces system load on the FortiGate unit.

01-30007-0203-20090112 535
Log types Log&Report
To enable firewall policy traffic logging

2 Select the Expand Arrow to view the policy list for a policy.
3 Select Edit beside the policy that you want.
If required, create a new firewall policy by selecting Create New. For more
information, see “Firewall Policy” on page 293.
4 Select Log Allowed Traffic.
5 Select OK.
Event log
The Event Log records management and activity events, such as when a
configuration has changed, or VPN and High Availability (HA) events occur.
When you are logged into VDOMs that are in Transparent mode, or if all VDOMs
are in Transparent mode, certain options may not be available such as VIP ssl
event or CPU and memory usage event. You can enable event logs only when you
are logged in to a VDOM; you cannot enable event logs in the root VDOM.
To enable the event logs

1 Go to Log&Report > Log Config > Event Log.
2 Select the Enable check box.
3 Select one or more of the following logs:
System Activity All system-related events, such as ping server failure and gateway
event status.
IPSec negotiation All IPSec negotiation events, such as progress and error reports.
event
DHCP service All DHCP-events, such as the request and response log.
event
L2TP/PPTP/PPPoE All protocol-related events, such as manager and socket creation
service event processes.
Admin event All administrative events, such as user logins, resets, and
configuration updates.
HA activity event All high availability events, such as link, member, and state
information.
Firewall All firewall-related events, such as user authentication.
authentication
event
Pattern update All pattern update events, such as antivirus and IPS pattern
event updates and update failures.
SSL VPN user All user authentication events for an SSL VPN connection, such as
authentication logging in, logging out and timeout due to inactivity.
event
SSL VPN All administration events related to SSL VPN, such as SSL
administration configuration and CA certificate loading and removal.
event

536 01-30007-0203-20090112
Log&Report Log types
SSL VPN session All session activity such as application launches and blocks,
event timeouts, and verifications.
VIP ssl event All server-load balancing events happening during SSL session,
especially details about handshaking.
VIP server health All related VIP server health monitor events that occur when the
monitor event VIP health monitor is configured, such as an interface failure.
CPU & memory All real-time CPU and memory events, at 5-minute intervals.
usage (every 5 min)
4 Select Apply.
Antivirus log
The Antivirus log records virus incidents in Web, FTP, and email traffic. For
example, when the FortiGate unit detects an infected file, blocks a file type, or
blocks an oversized file or email that is logged, it records an antivirus log. You can
also apply filters to customize what the FortiGate unit logs, which are:
• Viruses – The FortiGate unit logs all virus infections.
• Blocked Files – The FortiGate unit logs all instances of blocked files.
• Oversized Files/Emails – The FortiGate unit logs all instances of files and
email messages exceeding defined thresholds.
• AV Monitor – The FortiGate unit logs all instances of viruses, blocked files,
and oversized files and email. This applies to HTTP, FTP, IMAP, POP3, SMTP,
and IM traffic.
To enable antivirus logs

2 Select Edit beside the protection profile that you want.
3 Select the Expand Arrow beside Logging to reveal the available options.
4 Select the antivirus events you want logged.
5 Select OK.
Web filter log

The Web Filter log records HTTP FortiGuard log rating errors including web
content blocking actions.
To enable web filter logs

4 Select the web filtering events to log.
5 Select the “FortiGuard Web Filtering Rating Errors (HTTP only)” check box, to log
FortiGuard filtering.
6 Select OK.

01-30007-0203-20090112 537
Log types Log&Report
Spam filter log

The Spam Filter log records blocking of email address patterns and content in
SMTP, IMAP and POP3 traffic.
To enable the Spam log

4 Select Log Spam.
5 Select OK.
Attack log (IPS)

The Attack (IPS) log records attacks detected and prevented by the FortiGate unit.
The FortiGate unit logs the following:
• Attack Signature – The FortiGate unit logs all detected and prevented attacks
based on the attack signature, and the action taken by the FortiGate unit.
• Attack Anomaly – The FortiGate unit logs all detected and prevented attacks
based on unknown or suspicious traffic patterns, and the action taken by the
FortiGate unit.
To enable the attack logs

4 Select Log Intrusions under IPS.
5 Select OK.
Note: Make sure attack signature and attack anomaly DoS sensor settings are enabled to
log the attack. The logging options for the signatures included with the FortiGate unit are
set by default. Ensure any custom signatures also have the logging option enabled. For
more information, see “Intrusion Protection” on page 463.
IM and P2P log

The Instant Message (IM) and Peer-to-Peer (P2P) log records instant message
text, audio communications, and file transfers attempted by users. This type of log
file also records the time a transmission was attempted, the type of IM application
used, and the content of the transmission.
To enable IM and P2P logs

4 Select Log IM Activity.
5 Select Log P2P Activity.
6 Select OK.

538 01-30007-0203-20090112
Log&Report Accessing Logs
VoIP log
You can log Voice over Internet Protocol (VoIP) calls. You can also configure VoIP
rate limiting for Session Initiated Protocol (SIP) and Skinny Client Control Protocol
(SCCP) or Skinny protocol. SIP and SCCP are two types of VoIP protocols.
Rate limiting is generally different between SCCP and SIP. For SIP, rate limiting is
for that SIP traffic flowing through the FortiGate unit. For SCCP, the call setup rate
is between the FortiGate unit and the clients because the call manager normally
resides on the opposite side of the FortiGate unit from the clients.
To enable VoIP logs

4 Select Log VoIP Activity.
5 Select OK.
To configure VoIP activity (rate limiting)

3 Select the Expand Arrow beside VoIP to reveal the available options.
4 Select the SIP and SCCP check boxes/policy.
5 Enter a number for requests per second in the Limit REGISTER request
(requests/sec/policy) (SIP only) field.
6 Enter a number for requests per second in the Limit INVITE request
(requests/sec/policy) (SIP only) field
7 Enter a number for the maximum calls per minute in the Limit Call Setup
(calls/min/client) (SCCP only) field.
8 Select OK.
Accessing Logs
You can use the Log Access feature in the FortiGate web-based manager to view
logs stored in memory, on a hard disk, or stored on a FortiAnalyzer unit running
FortiAnalyzer 3.0, or on the FortiGuard Analysis server.
Log Access provides tabs for viewing logs according to these locations. Each tab
provides options for viewing log messages, such as search and filtering options,
and choice of log type. The Remote tab displays logs stored on either the
FortiGuard Analysis server or FortiAnalyzer unit.
For the FortiGate unit to access logs on a FortiAnalyzer unit, the FortiAnalyzer
unit must run firmware version 3.0 or higher.

01-30007-0203-20090112 539
Accessing Logs Log&Report
Accessing log messages stored in memory

You can access logs stored in the FortiGate system memory from the Memory tab.
The traffic log type is not available in the Log Type list because the FortiGate
system memory is unable to store them.
To view log messages in the FortiGate memory buffer

1 Go to Log&Report > Log Access.
2 Select the Memory tab.
3 Select a log type from the Log Type list.
Accessing log message stored on the hard disk

You can access logs stored on the hard disk if your FortiGate unit has a hard disk.
Logs stored on the hard disk are available for viewing in the Disk tab. You can
view, navigate, and download logs stored on the hard disk.
To access log files on the hard disk

1 Go to Log & Report > Log Access.
2 Select the Disk tab.
The FortiGate unit displays a list of rolled log files. You can view log messages
when you select the View icon.
Figure 334:Viewing log files stored on the FortiGate hard disk
Download
Clear
log
Delete
View
Log Type Select the type of log you want to view. Some log files, such as the
traffic log, cannot be stored to memory due to the volume of information
logged.
File name The names of the log files of the displayed Log Type stored on the
FortiGate hard disk.
When a log file reaches its maximum size, the FortiGate unit saves the
log files with an incremental number, and starts a new log file with the
same name. For example, if the current attack log is alog.log, any
subsequent saved logs appear as alog.n, where n is the number of
rolled logs.
Size (bytes) The size of the log file in bytes.
Last access The time a log message was recorded on the FortiGate unit. The time is
time in the format name of day month date hh:mm:ss yyyy, for
example Fri Feb 16 12:30:54 2007.
Clear log icon Clear the current log file. Clearing deletes only the current log
messages of that log file. The log file is not deleted.

540 01-30007-0203-20090112
Log&Report Accessing Logs
Download icon Download the log file or rolled log file. Select either Download file in
Normal format link or Download file in CSV format link. Select the
Return link to return to the Disk tab page. Downloading the current log
file includes only current log messages.
View icon Display the log file in the Log Access menu.
Delete icon Delete rolled logs. It is recommended to download the rolled log file
before deleting it because the rolled log file cannot be retrieved after
deleting it.
Accessing logs stored on the FortiAnalyzer unit

You can view and navigate through logs saved to the FortiAnalyzer unit. For
information about configuring the FortiGate unit to send log files to the
FortiAnalyzer unit, see “Logging to a FortiAnalyzer unit” on page 529.
Logs accessed on a remote logging device such as the FortiAnalyzer unit,
automatically appear in the Remote tab.
To access log files on the FortiAnalyzer unit

2 Select the Remote tab.
Figure 335:Viewing log files stored on the FortiAnalyzer unit
Current
Page
Log Type Select the type of log you want to view.

number of pages appears after the current page number. For
example, if 3/54 appears, you are currently viewing page 3 of 54
pages.
press Enter.
Column Settings Select to add or remove columns. This changes what log information
appears in Log Access. For more information, see “Column settings”
on page 543.
Raw or Formatted By default, log messages is displayed in Formatted mode. Select
Formatted to view log messages in Raw mode, without columns.
When in Raw mode, select Formatted to switch back to viewing log
messages organized in columns.
When log messages are displayed in Formatted view, you can
customize the columns, or filter log messages.
Clear All Filters Clear all filter settings. For more information, see “Filtering log
messages” on page 545.
Note: The FortiAnalyzer unit must be running firmware version 3.0 or higher to view logs

01-30007-0203-20090112 541
Viewing log information Log&Report
Accessing logs stored on the FortiGuard Analysis server

You can access log files stored on the FortiGuard Analysis server from the
FortiGate web-based manager, if you have subscribed to FortiGuard Analysis and
Management Service. After enabling logging to the FortiGuard Analysis server, a
Remote tab appears in the Log Access menu. For more information about viewing
real-time and historical log files, see the FortiGuard Analysis and Management
Service Guide.
To access log files on the FortiGuard Analysis server

2 Select the Remote tab.
Viewing log information

Log information is displayed in the Log Access menu. Different tabs in Log Access
display log information stored on the FortiAnalyzer unit, FortiGate system memory
and hard disk if available, including the FortiGuard Analysis server.
The columns that appear reflect the content found in the log file. The top portion of
the Log Access page includes navigational features to help you move through the
log messages and locate specific information.
To view log messages, go to Log&Report > Log Access and then select the tab
that corresponds to the log storage device used: Remote, Memory or Disk. If you
are logging to the FortiGate unit’s hard disk, select Edit beside a rolled log file to
view log messages.
Figure 336:Viewing log messages
Current
Page

542 01-30007-0203-20090112
Log&Report Customizing the display of log messages
Log Type Select the type of log you want to view. Some log files, such as the
traffic log, cannot be stored to memory due to the volume of
information logged.
number of pages displays after the current page number. For example,
if 3/54 appears, you are currently viewing page 3 of 54 pages.
press Enter.
Column Settings Select to add or remove columns. This changes what log information
appears in Log Access. For more information, see “Column settings”
on page 543.
Raw or Formatted By default, log messages are displayed in Formatted mode. Select
Formatted to view log messages in Raw mode, without columns.
When in Raw mode, select Formatted to switch back to viewing log
messages organized in columns.
When log messages are displayed in Formatted view, you can
customize the columns, or filter log messages.
Clear All Filters Clear all filter settings. For more information, see “Filtering log
messages” on page 545.
Customizing the display of log messages

By customizing the display of log messages, you can view certain parts or
different formats of log messages. For example, log messages can be viewed in
Formatted or Raw view. In Formatted view, you can customize the columns, or
filter log messages. In Raw view, the log message appears as it would in the log
file.
Filtering is also another way to customize the display of log messages. By using
the filter icon, you can display specific information of log messages. For example,
you may want to display only event log messages that have a severity level of
alert.
Note: For more information about filtering log messages, see “Adding filters to web-based
Column settings
By using Column Settings, you can customize the view of log messages in
Formatted view. By adding columns, changing their order, or removing them, you
can view only the log information you want.
The Column Settings feature is available only in Formatted view.

01-30007-0203-20090112 543
Customizing the display of log messages Log&Report
Figure 337:Column settings for viewing log messages
To customize the columns

2 Select the tab to view logs from, Memory, Disk or Remote.
4 Select the View icon if you are viewing a log file on a FortiAnalyzer unit.
5 Select the Column Settings icon.
6 Select a column name and select one of the following to change the views of the
log information:
-> Select the right arrow to move selected fields from the “Available fields”
list to the “Show these fields in this order” list.
<- Select the left arrow to move selected fields from the “Show these fields
in this order” list to the “Available fields” list.
Move up Move the selected field up one position in the “Show these fields in this
order” list.
Move down Move the selected field down one position in the “Show these fields in
this order” list.
7 Select OK.
Note: The Detailed Information column provides the entire raw log entry and is needed only
if the log contains information not available in any of the other columns. The VDOM column
displays which VDOM the log was recorded in.
You can view the device ID and device name when customizing columns. The device ID
provides the identification name of the device. The device name is the Host name that you
configured for the FortiGate unit, for example Headquarters.

544 01-30007-0203-20090112
Log&Report Content Archive
Filtering log messages

You can filter log messages by removing, adding or moving columns using the
Filter icon. You can use this feature to display specific information about log
messages.
Figure 338:Log filters
Filter icon
Column Filter
(enabled)
(disabled)
The filter settings that are applied remain until you log out of the web-based
manager. Log filters automatically reset to default settings when you log into the
web-based manager.
To filter log messages

2 Select the tab to view logs from, Memory, Remote or Disk.
4 Select the Filter icon in the column to view logs.
5 Select Enable to enable filtering for the column.
6 Enter the information as appropriate. Fields vary between type.
For more information about using the filter icons to filter log messages, see
“Adding filters to web-based manager lists” on page 58.
7 Select OK.
8 Select the columns to filter in the Filter list.
You can also select the columns that appear in the Filter list instead of selecting
the actual column.
You can view log messages in Raw format only after configuring the filters. If you
want to delete all filter settings, select the Clear All Filters that is located under the
Filters list.
Content Archive
You can use Content Archive to view archived logs stored on the FortiAnalyzer
unit from the FortiGate web-based manager and the content archives of HTTP,
FTP, Email, IM, and VoIP that are stored on the FortiAnalyzer unit. You can also
view content summaries of HTTP, FTP, Email, IM, and VoIP if you have
subscribed to the FortiGuard Analysis and Management Service.
Before viewing content archives, you need to enable this feature on your
FortiGate unit, within a protection profile. For more information, see “Firewall
Protection Profile” on page 365.

01-30007-0203-20090112 545
Content Archive Log&Report
The FortiGate unit allocates only one sixteenth of its memory for transferring
content archive files. For example, FortiGate units with 128RAM use only 8MB of
memory when transferring content archive files. It is recommended not to enable
full content archiving if antivirus scanning is also configured because of these
memory constraints.
Note: Infected files are clearly indicated in the Content Archive menu so that you know
which content archives are infected and which are not.
Configuring content archiving

When configuring content archiving, you select various archiving options from
within a protection profile in Firewall > Protection Profile. Content archiving is
available when the FortiGate unit is configured to log to either a FortiAnalyzer unit
or FortiGuard Analysis server. If you are logging to the FortiGuard Analysis server,
you can receive only content summary of logs. This includes email content
archives as well.
To enable content archiving for your FortiGate unit

2 Select Edit for a protection profile.
3 Select the Expand Arrow to view the Content Archive option.
4 Select the content archives you require beside “Display content meta-information
on the system dashboard”.
5 Select the available options in each list you require for “Archive to
FortiAnalyzer/FortiGuard”.
6 Select the check boxes for “Archive SPAMed email to FortiAnalyzer”, if required.
7 Select OK.
Note: Email content archiving is also supported on the FortiGuard Analysis server.
Viewing content archives

By using Content Archive, you can view all archived logs in the web-based
manager. You can view either content archive logs stored on a FortiAnalyzer unit
or FortiGuard Analysis server. The FortiGuard Analysis server stores only a
content summary of logs.
If you need to view logs in Raw format, select Raw beside the Column Settings
icon. For more information, see “Column settings” on page 543.
Content archives are displayed only if either the FortiAnalyzer unit or the
FortiGuard Analysis server is enabled in the protection profile for that remote
logging device. For example, if the FortiAnalyzer unit is configured to receive
content archives, then only content archives from the FortiAnalyzer unit appear in
the Content Archive menu.
To view content archives

1 Go to Log&Report > Content Archive.
2 Select the archived log type tab to view: Email, Web, FTP, IM, VOIP.

546 01-30007-0203-20090112
Log&Report Alert Email
To view content summary logs from the FortiGuard Analysis server

1 Go to Log&Report > Content Archive.
2 Select FortiGuard from Select Log Device.
3 Select the tab of the content summary log type to view.
Alert Email
You can use the Alert Email feature to monitor logs for log messages, and to send
email notification about a specific activity or event logged. For example, if you
require notification about administrators logging in and out, you can configure an
alert email that is sent whenever an administrator logs in and out.
You can also base alert email messages on the severity levels of the logs.
Figure 339:Alert Email options
Configuring Alert Email

Before configuring alert email, you must configure at least one DNS server if you
are configuring with an Fully Qualified Domain Server (FQDN). The FortiGate unit
uses the SMTP server name to connect to the mail server, and must look up this
name on your DNS server. You can also specify an IP address.
To configure alert email

1 Go to Log&Report > Log Config > Alert E-mail.
2 Set the following options and select Apply.

01-30007-0203-20090112 547
Alert Email Log&Report
SMTP Server The name/address of the SMTP email server.

Email from The SMTP user name.
Email To Enter up to three email address recipients for the alert email message.
Authentication Select the Authentication Enable check box to enable SMTP
Enable authentication.
SMTP user Enter the user name for logging on to the SMTP server to send alert
email messages. You need to do this only if you have enabled the SMTP
authentication.
Password Enter the password for logging on to the SMTP server to send alert
email. You need to do this only if you selected SMTP authentication.
3 Select Test Connectivity to send a test email message to the email account you
configured in the above step.
4 Select “Send alert email for the following” if you require sending an
email based on one or more of the following:
Interval Time Enter the minimum time interval between consecutive alert
(1-9999 minutes) emails. Use this to rate-limit the volume of alert emails.
Intrusion detected Select if you require an alert email message based on
attempted intrusion detection.
Virus detected Select if you require an alert email message based on virus
detection.
Web access Select if you require an alert email message based on blocked
blocked web sites that were accessed.
HA status changes Select if you require an alert email message based on HA
status changes.
Violation traffic Select if you require an alert email message based on violated
detected traffic that is detected by the FortiGate unit.
Firewall authentication Select if you require an alert email message based on firewall
failure authentication failures.
SSL VPN login failure Select if you require an alert email message based on any SSL
VPN logins that failed.
Administrator Select if you require an alert email message based on whether
login/logout administrators log in or out.
IPSec tunnel errors Select if you require an alert email message based on whether
there is an error in the IPSec tunnel configuration.
L2TP/PPTP/PPPoE Select if you require an alert email message based on errors
errors that occurred in L2TP, PPTP, or PPPoE.
Configuration changes Select if you require an alert email message based on any
changes made to the FortiGate configuration.
FortiGuard license Enter the number of days before the FortiGuard license expiry
expiry time time notification is sent.
(1-9999 days)
FortiGuard log quota Select if you require an alert email message based on the
usage FortiGuard Analysis server log disk quota getting full.
5 Select “Send an alert based on severity” if you require sending an alert email
based on log severity level.
6 Select the minimum severity level in the Minimum severity level list if you are
sending an alert based on severity.
7 Select Apply.

548 01-30007-0203-20090112
Log&Report Reports
Note: The default minimum log severity level is Alert. If the FortiGate unit collects more
than one log message before an interval is reached, the FortiGate unit combines the
messages and sends out one alert email.
Reports
You can use the Log&Report menu to configure FortiAnalyzer report schedules
and to view generated FortiAnalyzer reports. You can also configure basic traffic
reports, which use the log information stored in your FortiGate system memory to
present basic traffic information in a graphical format.
Viewing basic traffic reports

The FortiGate unit uses collected log information and presents it in a graphical
format to show network usage for a number of services. The charts show the
bytes used for the service traffic.
To view basic traffic reports, go to Log&Report > Report Access > Memory.
Figure 340:Viewing the basic traffic report from a FortiGate-60 unit

01-30007-0203-20090112 549
Reports Log&Report
Time Period Select a time range to view for the graphical analysis. You can choose
from one day, three days, one week or one month. The default is one
day. When you refresh your browser or go to a different menu, the
settings revert to default.
Services By default all services are selected. When you refresh your browser or
go to a different menu, all services revert to default settings. Clear the
check boxes beside the services you do not want to include in the
graphical analysis.
• Browsing • Streaming
• DNS • TFTP
• Email • VoIP
• FTP • Generic TCP
• Gaming • Generic UDP
• Instant Messaging • Generic ICMP
• Newsgroups • Generic IP
• P2P
Bandwidth Per This bar graph is based on what services you select, and is updated
Service when you select Apply. The graph is based on date and time, which is
the current date and time.
Top Protocols This bar graph displays the traffic volume for various protocols, in
Ordered by decreasing order of volume. The bar graph does not update when you
Total Volume select different Services and then select Apply.
The report is not updated in real-time. You can refresh the report by selecting the
Memory tab.
Note: The data used to present the graphs is stored in the FortiGate system memory.
When the FortiGate unit is reset or rebooted, the data is erased.
Configuring the graphical view

The FortiGate basic traffic report includes a wide range of services you can
monitor. For example, you can choose to view only email services for the last
three days.
To change the graphical information

1 Go to Log&Report > Report Access > Memory.
2 Select the time period to include in the graph from the Time Period list.
3 Clear the services to exclude them from the graph. All services are selected by
default.
4 Select Apply.
The graph refreshes and displays the content you specified in the above
procedure. The Top Protocols Ordered by Total Volume graph does not change.
Note: If you require a more specific and detailed report, you can configure a simple report
from the FortiAnalyzer web-based manager or CLI. The FortiAnalyzer unit can generate
over 140 different reports providing you with more options than the FortiGate unit provides.
If you need to configure a FortiAnalyzer report schedule, see “FortiAnalyzer report
schedules” on page 551.

550 01-30007-0203-20090112
Log&Report Reports
FortiAnalyzer report schedules

You can configure a FortiAnalyzer report schedule from FortiGate logs in the
web-based manager or CLI. You need to configure a report layout (previously
called report profiles) before configuring a report schedule. Contact a
FortiAnalyzer administrator before configuring report schedules from the
FortiGate unit to verify that the appropriate report layout is configured and ready
for you to access on the FortiAnalyzer unit. Report layouts can only be configured
from the FortiAnalyzer unit.
For information about how to add and configure report layout, see the
The FortiGate unit provides a list of report schedules. The following procedures
describe how to configure, edit, delete, and clone report schedules in this list.
When you clone a report schedule, a duplicate is used as a basis for a new one.
To view the list of report schedules, go to Log&Report > Report Config.
Figure 341:Report schedules in Report Config
Delete
Edit
Clone
Create New Create a new report schedule.

Name The name of the report schedule.
Description The comment made when the report schedule was created.
Report Layout The name of the report layout used for the report schedule.
Schedule When the report schedule will be generated. The time depends on
what time period was selected when the report schedule was
created: once, daily, or specified days of the week.
For example, if you select monthly, the days of the month and time
(hh:mm) will appear in the format Monthly 2, 10, 21, 12:00.
Delete and Edit icons Delete or edit a report schedule in the list.
Clone Select Clone to create a duplicate of the report schedule and use
it as a basis for a new report schedule.
Note: FortiAnalyzer reports do not appear if the FortiGate unit is not connected to a
FortiAnalyzer unit, or if the FortiAnalyzer unit is not running firmware 3.0 or higher.
To configure a report schedule

1 Go to Log&Report > Report Config.
3 Enter the appropriate information for the following:
Name Enter a name for the schedule.
Description Enter a description for the schedule. This is optional.

01-30007-0203-20090112 551
Reports Log&Report
Report Layout Select a configured report layout from the list. You must apply a
report layout to a report schedule. For more information, see the
Language Select the language you want used in the report schedule from the
list.
Schedule Select one of the following to have the report generate once only,
daily, weekly, or monthly at a specified date or time period.
Once Select to have the report generated only once.
Daily Select to generate the report every date at the
same time, and then enter the hour and minute
time period for the report. The format is hh:mm.
These Days Select to generate the report on specified days
of the week, and then select the days of the
week check boxes.
These Dates Select to generate the report on a specific day or
days of the month, and then enter the days with
a comma to separate them. For example, if you
want to generate the report on the first day, the
21st day and 30th day, enter: 1, 21, 30.
Log Data Filtering You can specify the following variables for the report:
Virtual Domain Select to create a report based on virtual
domains. Enter a specific virtual domain to
include in the report.
User Select to create a report based on a network
user. Enter the user or users in the field,
separated by spaces. If a name or group name
contains a space, if should be specified between
quotes, for example, “user 1”.
Group Select to create a report based on a group of
network users, defined locally. Enter the name of
the group or groups in the field.
LDAP Query Select the LDAP Query check box and then
select an LDAP directory or Windows Active
Directory group from the list.
Time Period Select to include the time period of the logs to include in the report.
Relative to Select a time period from the list. For example,
Report Runtime this year.
Specify Select to specify the date, day, year and time for
the report to run.
From – Select the beginning date and time of
the log time range.
To – Select the ending date and time of the log
time range.
Output Select the format you want the report to be in and if you want to
apply an output template.
Output Types Select the type of file format for the generated
report. You can choose from PDF, MS Word,
Text, and MHT.
Email/Upload Select the check box if you want to apply a
report output template from the list.
This list is empty if a report output template does
not exist. For more information, see the
4 Select OK.

552 01-30007-0203-20090112
Log&Report Reports
To edit a report schedule

2 Select Edit.
3 Remove and enter the appropriate information.
4 Select OK.
To delete a report schedule

2 Select Delete in the row of the report schedule you want deleted.
To clone a report schedule

2 Select Clone in the same row of the report schedule that will be the basis of a new
report schedule.
3 Rename the report schedule.
The report schedule is renamed, for example, CloneOfFGT_100A.
4 Enter the appropriate information and select OK.
Viewing FortiAnalyzer reports

After the FortiAnalyzer unit generates the report, it appears on the Report Access
page. All reports are listed on the page, including the rolled reports. A list displays
the generated report schedules as well as other reports that the FortiAnalyzer unit
generated.
To view reports, go to Log&Report > Report Access and select a report name in
the Report Files column. You can also select the Expand Arrow to view the rolled
report and view the entire report. After viewing the report, select Historical Reports
to return to the list.
Figure 342:Generated reports displayed in Report Access

01-30007-0203-20090112 553
Reports Log&Report
Report Files The name of the generated report. Select the name to view the
report.
You can also select the Expand Arrow to view the report and the
select the rolled report to view the report.
Date The date the report was generated on.
Size(bytes) The size of the report in bytes.
Other Formats Displays the formats PDF, RTF or MHT or all if these formats were
chosen in the report schedule.
Printing your FortiAnalyzer report

After the FortiAnalyzer unit generates the report, you may want to print the report
to have as a hardcopy reference or for a presentation. You can print your report
from the web-based manager in the Report Access menu.
To print a FortiAnalyzer report

1 Go to Log&Report > Report Access.
2 Select the report you want printed from the list.
3 Select Print.

554 01-30007-0203-20090112
Managing firmware versions
Managing firmware versions

Before upgrading to FortiOS 3.0, it is recommended to review this chapter so you
can be fully aware of the procedures and issues when upgrading to FortiOS 3.0.
This chapter includes upgrading issues for all FortiOS 3.0 firmware versions and
how to revert back to a previous firmware version, either to FortiOS 2.80 MR11 or
an earlier FortiOS 3.0 firmware version.
In addition to firmware images, Fortinet releases patch releases–maintenance
release builds that resolve important issues. Fortinet strongly recommends
reviewing the release notes for the patch release before upgrading the firmware.
Follow the steps below:
• download and review the release notes for the patch release
• download the patch release
• back up the current configuration
• install the patch release using the procedure “Testing firmware before
upgrading” on page 557
• test the patch release until you are satisfied that it applies to your configuration
Installing a patch release without reviewing release notes or testing the firmware
may result in changes to settings or unexpected issues.
FortiOS 3.0 also enables you to configure your FortiGate unit to use NAT while in
Transparent mode. See “Adding NAT firewall policies in transparent mode” on
page 361.
If you enable virtual domains (VDOMs) on the FortiGate unit, system firmware
versions are configured globally. For more information, see “Using virtual
This chapter includes the following sections:
• Backing up your configuration
• Testing firmware before upgrading
• Upgrading your FortiGate unit
• Reverting to FortiOS 2.80 MR11
• Backing up your FortiOS 3.0 configuration
• Downgrading to FortiOS 2.80 MR11 using web-based manager
• Restoring your configuration
• Upgrading from FortiOS 3.0 MR1 to FortiOS 3.0 MR2
• Reverting to FortiOS 3.0 MR1
• Upgrading issues for 3.0 MR7
Note: Fortinet does not support upgrading from FortiOS 3.0 MR4 or earlier to FortiOS
3.0 MR7. You must upgrade to FortiOS 3.0 MR5 or MR6 before upgrading to FortiOS
3.0 MR7. Fortinet supports upgrading from the most recent patch release of FortiOS
3.0 MR5 and MR6 to FortiOS 3.0 MR7.

01-30007-0203-20090112 555
Backing up your configuration Managing firmware versions
Backing up your configuration

Fortinet recommends backing up all configuration settings from your FortiGate
unit(s) before upgrading to FortiOS 3.0. This ensures all configuration settings are
not lost if you require downgrading to FortiOS 2.80 MR11 and want to restore
those configuration settings.
Caution: Always back up your configuration before installing a patch release,

! upgrading/downgrading, or when resetting to factory defaults.
Backing up your configuration using the web-based manager

The following procedures enable you to back up your current configuration using
the web-based manager.
To back up your configuration file using the web-based manager

1 Go to System > Maintenance > Backup & Restore.
2 For All Configuration Files, select the Backup icon.
3 Select OK.
4 Save the file.
Note: You can enter a password to encrypt the configuration file when backing up.
Backing up your configuration using the CLI

The following procedure enables you to back up your current configuration using
the CLI.
To back up your configuration file using the CLI

Enter the following to back up the configuration file:
execute backup allconfig <filename> <address_ip>
This may take a few minutes.
After successfully backing up your configuration file, either from the CLI or the
web-based manager, proceed with upgrading to FortiOS 3.0.

556 01-30007-0203-20090112
Managing firmware versions Testing firmware before upgrading
Testing firmware before upgrading

You may want to test the firmware you want to install before upgrading to a new
firmware version, maintenance or patch release. By testing the firmware, you can
familiarize yourself with the new features and changes to existing features, as well
as understand how your configuration works with the firmware. A firmware image
is tested by installing it from a system reboot, then saving it to system memory.
After the firmware is saved to system memory, the FortiGate unit operates using
the firmware with the current configuration.
The following procedure does not permanently install the firmware; the next time
the FortiGate unit restarts, it operates using the firmware originally installed on the
FortiGate unit. You can install the firmware permanently using the procedures in
“Upgrading your FortiGate unit” on page 558.
You can use the following procedure regardless of the type of firmware image, for
example, a patch release.
To test the firmware image before upgrading

1 Copy the new firmware image file to the root directory of the TFTP server.
2 Start the TFTP server.
3 Log into the CLI.
4 Enter the following command to ping the computer running the TFTP server:
execute ping <server_ipaddress>
Pinging the computer running the TFTP server verifies that the FortiGate unit and
TFTP server are successfully connected.
5 Enter the following to restart the FortiGate unit.
execute reboot
6 As the FortiGate unit reboots, a series of system startup messages appears.
When the following message appears,
Press any key to display configuration menu…
7 Immediately press any key to interrupt the system startup.
You have only three seconds to press any key. If you do not press a key soon
enough, the FortiGate unit reboots and you must log in and repeat steps 5 to 7
again.
If you successfully interrupt the startup process, the following message appears:
[G]: Get firmware image from TFTP server.
[F]: Format boot device.
[Q]: Quit menu and continue to boot with default firmware.
[H]: Display this list of options.
8 Type G to get the new firmware image from the TFTP server.
Enter TFTP server address [192.168.1.168]:

01-30007-0203-20090112 557
Upgrading your FortiGate unit Managing firmware versions
9 Type the address of the TFTP server and press Enter.

Enter Local Address [192.168.1.188]:
10 Type the internal IP address of the FortiGate unit.
This IP address connects the FortiGate unit to the TFTP server. This IP address
must be on the same network as the TFTP server, but make sure you do not use
an IP address of another device on the network.
Enter File Name [image.out]:
11 Enter the firmware image file name and press Enter.
The TFTP server uploads the firmware image file to the FortiGate unit and the
following appears:
Save as Default firmware/Backup firmware/Run image without
saving: [D/B/R]
12 Type R.
The FortiGate firmware image installs and saves to system memory. The
FortiGate unit starts running the new firmware image with the current
configuration.
When you are done testing the firmware, you can reboot the FortiGate unit and
resume using the original firmware.
Upgrading your FortiGate unit

If your upgrade is successful, and your FortiGate unit has a hard-drive, you can
use the Boot alternate firmware option located in System > Maintenance >
Backup and Restore. This option enables you to have two firmware images,
such as FortiOS 2.80 MR11 and FortiOS 3.0, for downgrading/upgrading
purposes. Use the Fortinet Knowledge Center article 2.80MR11 to 3.0MR1
upgrade/downgrade/dual-boot to configure a dual-boot/configuration for your
FortiGate unit.
If upgrading to FortiOS 3.0 is unsuccessful, go to “Reverting to FortiOS
2.80 MR11” on page 561 to downgrade to FortiOS 2.80 MR11.
You may need to reconfigure some configuration settings in FortiOS 3.0. See the
FortiOS Upgrade Guide or the Release Notes FortiOS 3.0MR1 for more
information.
You can also use the following procedure when installing a patch release. A patch
release is a firmware image that resolves specific issues without containing new
features and/or changes to existing features. You can install a patch release
whether you upgraded to the current firmware version or not.
Note: Before upgrading to FortiOS 3.0, ensure FortiOS 2.80 MR11 is installed.

558 01-30007-0203-20090112
Managing firmware versions Upgrading your FortiGate unit
Upgrading to FortiOS 3.0

This section describes the procedures for upgrading to FortiOS 3.0 using either
the web-based manager or CLI.
Upgrading using the web-based manager

The following procedure uses the web-based manager for upgrading to FortiOS
3.0. It is recommended to use the CLI to upgrade to FortiOS 3.0. The CLI upgrade
procedure reverts all current firewall configurations to factory default settings.

To upgrade to FortiOS 3.0 using the web-based manager

3 Go to System > Status > Unit Information.
4 Under Unit Information, select Update.
5 Enter the path and filename of the firmware image file, or select Browse and
locate the file.
6 Select OK.
version, restarts, and displays the FortiGate login. This process may take a few
minutes.
When the upgrade is successfully installed:
• Ping to your FortiGate unit to verify there is still a connection.
• Clear the browser’s cache and log into the web-based manager.
After logging back into the web-based manager, you should save the
configuration settings that carried forward. Some settings may have carried
forward from FortiOS 2.80 MR11, while others may not have such as certain IPS
group settings. Go to System > Maintenance > Backup and Restore to save the
configuration settings that carried forward.
Note: After upgrading to FortiOS 3.0, perform an “Update Now” to retrieve the latest
AV/NIDS signatures from the FortiGuard Distribution Network (FDN) as these signatures
included in the firmware may be older than those currently available on the FDN. See the
FortiGate Administration Guide for more information about updating AV/NIDS signatures.
Upgrading using the CLI

The following procedure uses the CLI to upgrade to FortiOS 3.0 and a TFTP
server. The CLI upgrade procedure reverts all current firewall configurations to
factory default settings.

01-30007-0203-20090112 559
Upgrading your FortiGate unit Managing firmware versions
See the Fortinet Knowledge Center article, Loading FortiGate firmware using
TFTP for CLI procedure, for additional information about upgrading firmware using
the CLI.
To upgrade to FortiOS 3.0 using the CLI

3 Log into the CLI.
5 Enter the following command to copy the firmware image from the TFTP server to
the FortiGate unit:
execute restore image <name_str> <tftp_ip4>
When <name_str> is the name of the firmware image file and <tftp_ip> is the
IP address of the TFTP server. For example, if the firmware image file name is
image.out and the IP address of the TFTP server er is 192.168.1.168, enter:
execute restore image.out 192.168.1.168
The FortiGate unit responds with a message similar to the following:
This operation will replace the current firmware version!
Do you want to continue? (y/n)
6 Type y.
version, and restarts. This process takes a few minutes.
7 Reconnect to the CLI.
8 Enter the following command to confirm the firmware image installed successfully:
get system status
9 Update antivirus and attack definitions, or from the CLI, enter:
execute update-now
Verifying the upgrade

After logging back into the web-based manager, most of your FortiOS 2.80 MR11
configuration settings have been carried forward. For example, if you go to
System > Network > Options you can see your DNS settings carried forward
from your FortiOS 2.80 MR11 configuration settings.
You should verify what configuration settings carried forward. You should also
verify that administrative access settings carried forward as well. Verifying your
configuration settings enables you to familiarize yourself with the new features
and changes in FortiOS 3.0.
You can verify your configuration settings by:
• going through each menu and tab in the web-based manager
• using the show shell command in the CLI

560 01-30007-0203-20090112
Managing firmware versions Reverting to FortiOS 2.80 MR11
Reverting to FortiOS 2.80 MR11

You may need to revert to a previous firmware version if the upgrade did not install
successfully. The following sections will help you to back up your current
FortiOS 3.0 configuration, downgrade to FortiOS 2.80 MR11, and restore your
FortiOS 2.80 MR11 configuration.
• Backing up your FortiOS 3.0 configuration
• Downgrading to FortiOS 2.80 MR11 using web-based manager
• Downgrading to FortiOS 2.80 MR11 using the CLI
• Restoring your configuration
Note: The FortiGate-1000A-FA2 does not support downgrading to FortiOS 2.80 because
with the introduction of the FortiClient Check feature, the flash card has a different partition
layout than it did in FortiOS 2.80.
Backing up your FortiOS 3.0 configuration

If you have configured additional settings in FortiOS 3.0, it is recommended to
back up these additional settings before downgrading to FortiOS 2.80 MR11. This
ensures you have a current configuration file for FortiOS 3.0 if you decide to
upgrade.
It is recommended to back up your configuration when installing patch releases as
well as upgrading the FortiGate firmware.
To back up your configuration to your PC

2 Select Local PC from Backup Configuration to list.
3 Select Apply.
If you want to encrypt your configuration file to save VPN certificates, select the
Encrypt configuration file checkbox and enter a password, then enter it again to
confirm.
Backing up to a USB key

You can back up your FortiOS 3.0 configuration to a USB key. Before proceeding,
ensure the USB key is inserted in the FortiGate unit USB port.
For information about supported USB keys, see “USB Disks” on page 238.
You can use the following procedure when backing up your configuration using a
FortiUSB key or a third-party USB key for FortiOS 3.0 MR5. A third-party USB key
is only available for FortiGate units running FortiOS 3.0 MR5 or higher.
Note: If FortiOS 3.0 MR1 is installed on your FortiGate unit, ensure that the FortiGate unit
is shutdown and powered off whenever you insert the FortiUSB key into the USB port on
the FortiGate unit.
To back up your configuration using a USB key

2 Select USB Disk from Backup Configuration to list.

01-30007-0203-20090112 561
Reverting to FortiOS 2.80 MR11 Managing firmware versions
3 Select Apply.
confirm.
Downgrading to FortiOS 2.80 MR11 using web-based manager

When downgrading to FortiOS 2.80 MR11, only the following settings are
retained:
• Operation mode
• Interface IP/Management IP
• Route static table
• DNS settings
• VDOM parameters/settings
• Admin user account
• Session helpers
• System accprofiles
If you created additional settings in FortiOS 3.0, make sure to back up the current
configuration before downgrading. See “Backing up your FortiOS 3.0
configuration” on page 561 for more information.
Note: Installing FortiOS 2.80 firmware on a partition in FortiOS 3.0 MR5 will not overwrite
the other partition.
To downgrade using the web-based manager

1 Go to System > Status > Firmware Version.
2 Select Update.
3 Type the location of the firmware version or select Browse.
4 Select OK.
The new image does not support CC mode. Do you want to
continue to upgrade?
5 Select OK.
This version will downgrade the current firmware version.
Are you sure you want to continue?
6 Select OK.
Go to System > Unit Information to verify the Firmware Version has changed to
FortiOS 2.80 MR11.

562 01-30007-0203-20090112
Verifying the downgrade

After successfully downgrading to FortiOS 2.80 MR11, verify your connections
and settings. If you are unable to connect to the web-based manager, make sure
your administration access settings and internal network IP address are correct.
The downgrade may change your configuration settings to default settings.
Downgrading to FortiOS 2.80 MR11 using the CLI

The following procedure enables you to downgrade to FortiOS 2.80 MR11 in the
CLI. If you have created additional settings in FortiOS 3.0, make sure you back up
your configuration before downgrading. See “Backing up your FortiOS 3.0
configuration” on page 561 for more information.
To downgrade using the CLI

3 Log into the CLI.
the FortiGate unit:
execute restore image tftp <name_str> <tftp_ipv4>
Where <name_str> is the name of the firmware image file and <tftp_ipv4>
is the IP address of the TFTP server. For example, if the firmware image file name
is image.out and the IP address of the TFTP server er is 192.168.1.168, enter:
execute restore image tftp image.out
192.168.1.168
The FortiGate unit responds with the message:
This operation will replace the current firmware version! Do
you want to continue? (y/n)
6 Type y.
The FortiGate unit uploads the firmware image file. After the file uploads, a
message similar to the following is displayed:
Get image from tftp server OK.
Check image OK.
This operation will downgrade the current firmware version!
7 Type y.
The FortiGate unit reverts to the old firmware version, resets the configuration to
factory defaults, and restarts. This process takes a few minutes.
After the FortiGate unit uploads the firmware, you need to reconfigure your IP
address since the FortiGate unit reverts to default settings, including its default IP
address. See your install guide for configuring IP addresses.

01-30007-0203-20090112 563
Restoring your configuration Managing firmware versions

get system status
See “Restoring your configuration” on page 564 to restore you FortiOS 2.80 MR11
configuration settings.
Restoring your configuration

Your configuration settings may not carry forward after downgrading to FortiOS
2.80 MR11. You can restore your configuration settings for
FortiOS 2.80 MR11 with the configuration file(s) you saved before upgrading to
FortiOS 3.0.
You can also use the following procedures for restoring your configuration after
installing a patch release.
Restoring your configuration settings using the web-based manager

The following restores your FortiOS 2.80 MR11 configuration settings using the
web-based manager.
To restore configuration settings using the web-based manager

3 Select the Restore icon for All Configuration Files.
4 If required, enter your password for the configuration file.
5 Type the location of the file or select Browse to locate the file.
6 Select OK.
The FortiGate unit restores the configuration settings for FortiOS 2.80 MR11. This
may take a few minutes since the FortiGate unit will reboot.
You can verify that the configuration settings are restored by logging into the
web-based manager and going through the various menus and tabs.
Restoring your configuration settings using the CLI

The following restores your FortiOS 2.80 MR11 configurations settings using the
CLI.
To restore configuration settings using the CLI

1 Copy the backed up configuration file to the root directory of the TFTP server.
3 Log into the CLI.

564 01-30007-0203-20090112
Managing firmware versions Restoring your configuration
5 Enter the following command to copy the backed up configuration file to restore
the file on the FortiGate unit:
execute restore allconfig <name_str> <tftp_ipv4> <passwrd>
Where <name_str> is the name of the backed up configuration file and
<tftp_ipv4> is the IP address of the TFTP server and <passwrd> is the
password you entered when you backed up your configuration settings. For
example, if the backed up configuration file is confall and the IP address of the
TFTP server is 192.168.1.168 and the password is ghrffdt123:
execute restore allconfig confall 192.168.1.168 ghrffdt123
The FortiGate unit responds with the message:
This operation will overwrite the current settings and the
system will reboot!
6 Type y.
The FortiGate unit uploads the backed up configuration file. After the file uploads,
a message, similar to the following, is displayed:
Getting file confall from tftp server 192.168.1.168
##
Restoring files...
All done. Rebooting...
Use the show shell command to verify your settings are restored, or log into the
web-based manager.

01-30007-0203-20090112 565
Upgrading from FortiOS 3.0 MR1 to FortiOS 3.0 MR2 Managing firmware versions
Upgrading from FortiOS 3.0 MR1 to FortiOS 3.0 MR2

FortiOS 3.0 MR2 supports all FortiGate units except for the FortiGate-50 unit.
Using a TFTP server to upgrade firmware versions reverts all current firewall
configurations to factory default settings.
The following provides information and procedures for upgrading from FortiOS
3.0 MR1 to FortiOS 3.0 MR2. You can use the following procedures when
upgrading to FortiOS 3.0 MR3 or higher.
When upgrading to a firmware version, and, depending on your current firmware
version, you may find that not all configuration settings carry forward. See the
FortiOS Upgrade Guide about what settings carry forward when upgrading from
FortiOS 3.0 MR1 to FortiOS 3.0 MR2.

You can back up your current configuration using the FortiUSB key, the
web-based manager or the CLI. Use one of the following procedures to back up
your current configuration.

To back up your current configuration using the web-based manager

3 Select Apply.
confirm.
To back up your current configuration using the CLI

1 Log into the CLI.
2 Enter the following CLI command:
execute backup config tftp <filename> <tftp_ipv4>
Example
execute backup config tftp fgt.conf 192.168.1.23
To back up your current configuration using the FortiUSB key

1 Go to System > Maintenance > Backup and Restore.
2 Select USB from the Backup Configuration list.
3 Select OK.
confirm.

566 01-30007-0203-20090112
Managing firmware versions Upgrading from FortiOS 3.0 MR1 to FortiOS 3.0 MR2
Upgrading to FortiOS 3.0 MR2

Use one of the following procedures to upgrade your FortiGate unit. The
procedure, To upgrade to FortiOS 3.0 MR2 using the CLI, uses a TFTP server to
upgrade to FortiOS 3.0 MR2. A TFTP server reverts all current firewall
configuration settings to default settings. You can use the following procedure for
upgrading to FortiOS 3.0 MR3 and higher.
See the Fortinet Knowledge Center article, Loading FortiGate firmware using
TFTP for CLI procedure, for additional information about upgrading firmware
using the CLI.
To upgrade to FortiOS 3.0 MR2 using the web-based manager

3 Go to System > Status > Update Firmware.
4 Select Update.
5 Type the path and filename of the firmware image file, or select Browse to locate
the file.
6 Select OK.
version, restarts, and displays the FortiGate login. This process may take a few
minutes.
After successfully upgrading to FortiOS 3.0 MR2:
• Ping to your FortiGate unit to verify there is still a connection.
• Clear the browser’s cache and log into the web-based manager.
To upgrade to FortiOS 3.0 MR2 using the CLI

3 Log into the CLI.
the FortiGate unit:
execute restore image <name_str> <tftp_ip4>
When <name_str> is the name of the firmware image file and <tftp_ip> is the
IP address of the TFTP server. For example, if the firmware image file name is
image.out and the IP address of the TFTP server is 192.168.1.168, enter:
execute restore image image.out 192.168.1.168
The FortiGate unit responds with a message similar to the following:

01-30007-0203-20090112 567
6 Type y.
version and restarts. This process takes a few minutes.
get system status
9 Update antivirus and attack definitions (see the FortiGate Administration Guide),
or from the CLI enter:
execute update-now
Reverting to FortiOS 3.0 MR1

In the event that upgrading to FortiOS 3.0 MR2 or higher is unsuccessful, you can
easily revert back to an earlier FortiOS 3.0 firmware version. There are several
ways to revert back to a previous firmware version in FortiOS 3.0. You can use the
Boot Alternate firmware feature, web-based manager, or the CLI.
The Boot Alternate firmware feature is only available on FortiGate units with a
hard drive. This feature, located on the Backup & Restore page, enables you to
partition the FortiGate unit’s hard drive and have two firmware images available
for either upgrading or downgrading. Use the Fortinet Knowledge Center article,
2.80MR11 to 3.0MR1 upgrade/downgrade/dual-boot, to configure this option for
upgrading and/or downgrading your FortiGate firmware.
When downgrading to FortiOS 3.0 MR1, only the following configuration settings
are carried forward:
• operation modes
• interface IP/management IP
• route static table
• DNS settings
• VDOM parameters/settings
• admin user account
• session helpers
• system access profiles


You can back up your current configuration to the management PC or the
FortiUSB key. The following procedures use the web-based manager to back up
your current configuration to the management PC or FortiUSB key.

568 01-30007-0203-20090112
To back up current configuration in FortiOS 3.0 MR2 or higher to your PC

3 Select Apply.
confirm.
To back up your current configuration in FortiOS 3.0 MR2 or higher using

the FortiUSB key
3 Select OK.
confirm.
Downgrading to a previous firmware maintenance release

After backing up your configuration, you can now proceed to downgrade your
FortiGate unit to FortiOS 3.0 MR1 (or other 3.0 maintenance release) using either
the web-based manager or the CLI.
The following procedures can be used when downgrading to a lower firmware
maintenance release from the current release, such as FortiOS 3.0 MR7 to
FortiOS 3.0 MR5.
To downgrade using the web-based manager

1 Go to System > Status > Firmware Version.
2 Select Update.
3 Enter the location of the firmware version or select Browse.
4 Select OK.
The new image does not support CC mode. Do you want to
continue to upgrade?
5 Select OK.
This version will downgrade the current firmware version.
Are you sure you want to continue?
6 Select OK.
8 Go to System > Status > Firmware Version to verify the Firmware Version has
changed to FortiOS 3.0 MR1.

01-30007-0203-20090112 569
To downgrade using the CLI

3 Log into the CLI.
the FortiGate unit.
execute restore image tftp <name_str> <tftp_ipv4>
Where <name_str> is the name of the firmware image file and <tftp_ipv4> is
the IP address of the TFTP server. For example, if the firmware image file name is
image.out and the IP address of the TFTP server is 192.168.1.168, enter:
execute restore image tftp image.out 192.168.1.168
The FortiGate unit responds with the following message:
6 Type y.
7 The FortiGate unit uploads the firmware image file. After the file uploads, a
message similar to the following is displayed:
Get image from tftp server. OK.
Check image OK.
This operation will downgrade the current firmware version!
Do you want to continue ? (y/n)
8 Type y.
The FortiGate unit reverts to the old firmware version, resets the configuration to
factory defaults, and restarts. This process takes a few minutes.
After the FortiGate unit uploads the firmware, you will need to reconfigure your IP
address since the FortiGate unit reverts to default settings, including its default IP
address. See your FortiGate unit’s install guide for configuring IP addresses.
9 Log into the CLI.
10 Enter the following command to confirm the firmware image loaded successfully:
get system status
Restoring your previous configuration

After downgrading successfully to FortiOS 3.0 MR1 (or other maintenance
release), you can now re-install your previous configuration settings using either
the web-based manager or the CLI.
The following procedures can be used when restoring a previous configuration,
such as FortiOS 3.0 MR5, after downgrading to that firmware maintenance
release.

570 01-30007-0203-20090112
To restore your FortiOS 3.0 MR1 configuration using the web-based

manager
3 Select the Restore icon for All Configuration Files.
4 Enter your password for the configuration file, if required.
5 Type the location of the file or select Browse.
6 Select OK.
The FortiGate unit restores the configuration settings for FortiOS 3.0 MR1. This
may take a few minutes since the FortiGate unit reboots.
You can verify the configuration settings are restored by logging into the
web-based manager and going through the menus and tabs to see that your
settings are restored.
To restore your FortiOS 3.0 MR1 configuration using the CLI

1 Copy the backed up configuration file to the root directory of the TFTP server.
3 Log into the CLI.
5 Enter the following command to copy the backed up configuration file to restore
the file on the FortiGate unit:
execute restore allconfig <name_str> <tftp_ipv4> <passwrd>
Where <name_str> is the name of the backed up configuration file and
<tftp_ipv4> is the IP address of the TFTP server and <passwrd> is the
password you entered when you backed up your configuration settings. For
example, if the backed up configuration file is confall and the IP address of the
TFTP server is 192.168.1.168 and the password is ghrffdt123:
execute restore allconfig confall 192.168.1.168 ghrffdt123
6 Type y.
7 The FortiGate unit uploads the backed up configuration file. After the file uploads,
a message similar to the following, is displayed:
Getting file confall from tftp server 192.168.1.168
##
Restoring files...
8 Use the show shell command to verify your settings are restored, or log into the
web-based manager.

01-30007-0203-20090112 571
Upgrading issues for 3.0 MR7 Managing firmware versions
Restoring your configuration settings using the FortiUSB key

If you saved your configuration settings to the FortiUSB key, you can restore them
from the FortiUSB key using either the web-based manager or the CLI.
To restore configuration settings using the FortiUSB key from the

web-based manager
4 Select OK.
confirm.
To restore configuration settings using the FortiUSB key from the CLI
1 Log into the CLI.
2 Enter the following commands:
execute restore config usb <config_name>
3 A message similar to the following displays:
This operation will overwrite current settings!
4 Type y.
5 Restoring lists using Import Bulk CLI command feature
Upgrading issues for 3.0 MR7

The following are upgrading issues that concern upgrading to FortiOS 3.0 MR7.
These upgrading issues carry forward unless otherwise stated.
When installing a patch release, review the release notes to find out more about
any upgrading issues that occur.
Upgrading issues from FortiOS 2.80 MR11

The following addresses only issues that occur when upgrading from FortiOS
2.80 MR11 and MR12. Fortinet recommends reviewing the Upgrade Guide for
FortiOS 3.0 to familiarize yourself with all the changes that occurred to existing
features between these two firmware versions.
IPSec-related settings
The following parameters for both phase 1 and phase 2 policy-based IPSec
tunnels are not carried forward.
• phase 1:
config vpn ipsec phase1

572 01-30007-0203-20090112
Managing firmware versions Upgrading issues for 3.0 MR7
set dpd {enable | disable}

set dpd-idleworry <integer>
set dpd-idlecleanup <integer>
• phase 2:
set bindtoif <interface_name>
set internetbrowsing <interface_name>
System DHCP exclude range

In FortiOS 2.80 MR11 and MR12, the command system dhcp
exclude_range, is a separate command to indicate the IP address that should
be exempted from DHCP address pool. This feature is now implemented by
configuring settings in config exclude-range under config system dhcp
server. These settings are carried forward to every DHCP server setting:
config system dhcp server
config exclude-range
edit 1
set start-ip 192.168.1.100
set end-ip 192.168.1.200
next
Firewall profiles and schedules

The firewall profile and firewall onetime/recurring settings are now found
per-VDOM, which are carried forward.
Firewall service custom

The firewall service custom is now found per-VDOM and is carried forward to
each VDOM.
IPSec DPD Setting

The DPD parameter in a phase 1 policy-based IPSec tunnel is not carried forward
to FortiOS 3.0 MR7.
IPS predefined signatures

The severities of predefined signatures are reset to recommended values after
upgrading from FortiOS 3.0 MR3 and MR4 and later. Previously, these signatures
were set to recommended levels and could not be altered.
IPSec Manual keys in a VDOM configuration

IPSec tunnels that are configured in a non-root VDOM that uses manual keys do
not carry forward if the tunnel was not referenced by a firewall policy.

01-30007-0203-20090112 573
Static routes without device setting configured

The device setting for static route is now mandatory and if this setting is not
configured, the static route is not carried forward.
HA monitor interfaces WLAN

The WLAN interfaces cannot be used as a monitored interface as of FortiOS
3.0 MR4 and are not carried forward.
SSL-VPN firewall policies without groups

An SSL-VPN firewall policy that was configured without a group is not carried
forward.
VPN IPSec phase 1 with type DDNS

The following command syntax is not carried forward because it no longer
accepted.
set type ddns
set peertype one
set peerid aaa
Firewall VPN policies sharing the same manual key

VPN tunnels that were shared across firewall policies in FortiOS 2.80, are not
carried forward because FortiOS 3.0 VPN tunnels are assigned to an interface.
Oversize file limit

When upgrading from FortiOS 2.80 MR12, all oversize file limit value may change
to zero.
Upgrading issues from FortiOS 3.0 MR5 and MR6

Fortinet does not support a direct upgrade from FortiOS 3.0 MR4 or earlier. If you
are upgrading to FortiOS 3.0 MR7 from FortiOS 3.0 MR4 or earlier, you must first
upgrade to FortiOS 3.0 MR5 or MR6.
FortiOS 3.0 MR7 supports upgrading from the most recent patch release of
FortiOS 3.0 MR5 and MR6.
FortiGate-3016B upgrade
The interface names on the FortiGate-3016B unit changed in FortiOS 3.0 MR7 to
match the port names on the face plate of the unit. The following table explains the
new naming scheme:

574 01-30007-0203-20090112
Managing firmware versions Upgrading issues for 3.0 MR7
Table 51: Explanation of port names in FortiOS 3.0 MR7
MR6 port names MR7 port names

port 1 mgmt1
port 2 mgmt2
port 3 port1
port 4 port2
port 5 port3
port 6 port4
port 7 port5
port 8 port6
port 9 port7
port 10 port8
port 11 port9
port 12 port10
port 13 port11
port 14 port12
port 15 port13
port16 port14
port 17 port15
port 18 port16
SNMP interface index

Previously in FortiOS 3.0 MR6, a new SSL interface (ssl.root) was added. When
upgrading from FortiOS 3.0 MR5, the SNMP interface index is increased,
automatically adding the new SSL interface (ssl.root) after the physical interfaces
in the list.
NTP configuration
The following NTP-related configuration commands are now under config
system ntp in the CLI:
config ntpserver
set ntpsync
set syncinterval
System interface
Previously, the command dns-server-override was available only for
interfaces configured in the management VDOM. In FortiOS 3.0 MR7, VLAN
interfaces cannot be created under a FortiGate switch interface, and therefore,
any VLANs under the switch interfaces are not carried forward to FortiOS
3.0 MR7.

01-30007-0203-20090112 575
Configuring reports
Configuring reports in FortiOS 3.0 MR7 has drastically changed. All reports
configured under the command, config log report, are not carried forward.
Reports that do carry forward are placed as correctly as possible in their FortiOS
3.0 MR7 configuration. You may need to reconfigure some settings – if so, contact
a FortiAnlayzer administrator before reconfiguring settings because you will need
to know if report layouts are available for your report schedules.
FortiGuard configuration
The default setting for the command, central-mgmt-auto-backup, was
changed to enable.
Firewall policy
The commands, auth-path, auth-cert and auth-redirect-addr settings
may not carry forward if the authentication group is not selected in the firewall
policy.
System IPv6
The command, config system ipv6-tunnel is carried forward, now under
config system sit-tunnel in FortiOS 3.0 MR7.
Global setting
The command, allow-interface-subnet-overlap, previously under
global settings, is carried forward into every VDOM and found under
config system setting.

576 01-30007-0203-20090112
Index
Index
Symbols BFD, 286
BFD on BGP, 287
, 469 BFD on OSPF, 288
BGP settings, 282
Numerics CA certificates, 226
Certificate Revocation List (CRL), 228
802.3ad aggregate interface cipher suite, 415
creating, 116 combined IP pool and virtual IP, 359
content archive, 546
A content archive options, 375
access profile custom firewall service, 325
administrator account, 208 custom IM/P2P/VoIP protocols, 518
CLI commands list, 209 custom service, firewall, 325
configuring, 211 custom signatures, 467
viewing list, 210 customized CLI console, 68
DHCP interface settings, 118
accessing logs stored in hard disk, 540
DHCP relay agent, 163
action DHCP server, 163
firewall policy, 296 Directory Service server, 433, 434
protection profile P2P option, 378 Directory Service user groups, 437
spam filter banned word, 504 DoS sensors, 475
spam filter IP address, 507 Dynamic DNS on an interface, 122
action type dynamic virtual IP, 352
spam filter email address, 509 event logs, 536
active sessions fail-open, IPS, 478
HA statistics, 174 firewall address, 317
ActiveX filter firewall address group, 318
protection profile, 370 firewall policy, 296, 297
add signature to outgoing email firewall policy traffic logging, 535
protection profile, 369 firewall policy, adding to VLAN subinterface, 145
adding, configuring or defining firewall policy, modem connections, 134
access profile, 211 firewall protection profile, 367
administrative access to interface, 125 firewall schedule, 329
administrator account, 205 firewall service group, 327
administrator password, 205 firewall user groups, 436
administrator settings, 215 firewall virtual IP, 333
ADSL interface settings, 115 firmware upgrade, 236
advanced SSL VPN user group options, 442 firmware version, 81
alert email, 547 FortiAnalyzer report schedules, 551
antispam advanced options, 510 FortiClient checking, 308
antispam email address list, 508, 510 FortiGuard override options for a user group, 441
antispam IP address, 507 FortiGuard Web Filtering options, 370
antispam IP address list, 506 FortiWiFi-50B settings, 150, 152
antivirus file filter list, 453, 454 FortiWiFi-60 MAC filter list, 157
antivirus file patterns, 454 FortiWiFi-60 settings, 154
antivirus file quarantine, 454 FortiWiFi-60A settings, 150, 152
antivirus log, 537 FortiWiFi-60AM, 152
antivirus quarantine options, 457 FortiWiFi-60AM settings, 150
antivirus scanning options, 367 FortiWiFi-60B settings, 150, 152
attack log (IPS), 538 gateway for default route, 261
authentication settings, 445 grayware list, 459
authentication, firewall policy, 302 HA, 167
automatic discovery, 530 HA device priority, 174
autosubmit list, 457 HA subordinate unit host name, 174
banned word list, 503, 504 health check monitor, 355
basic traffic report, graphical view, 550 IM user, 522

01-30007-0203-20090112 577
Index
IM/P2P log, 538 RIP settings, advanced, 270

IM/P2P options, 378 RIP settings, basic, 268
IM/P2P/VoIP applications, older versions, 518 RIP-enabled interface, 272
IM/P2P/VoIP protocols, 517 scripts, 240
IM/P2P/VoIP protocols, protection profile, 518 secondary IP address, 126
interface settings, 112 server load balance port forwarding virtual IP, 350
inter-VDOM links, 104 server load balance virtual IP, 348
IP pool, 359 SIP, 388
IPS log (attack), 538 SIP advanced features, 389
IPS options, 375 SNMP community, 176, 177
IPS sensor filters, 472 socket-size, IPS, 478
IPS sensors, 469 spam filter log, 538
IPSec encryption policy, 306 spam filtering options, 373
IPSec VPN concentrator, 408 SSL VPN bookmarks, 417
IPSec VPN phase 1, 396 SSL VPN options, firewall policy, 307
IPSec VPN phase 1 advanced options, 399 SSL VPN settings, 414
IPSec VPN phase 2, 401 SSL VPN user groups, 437
IPSec VPN phase 2 advanced options, 401 standalone mode, 133
IPv6 support, 217 static NAT port forwarding, IP address and port
LDAP authentication, 199 range, 346
LDAP server, 426, 427 static NAT port forwarding, single address and port,
license key, 254 344
local ratings, 496 static NAT virtual IP, IP address range, 343
local URL block categories, 495 static route (transparent mode), 138
local user account, 423 static route, adding to routing table, 262
log message display, 543 subnet object, 92
logging options, 380 system administrators, 195
logging to a FortiAnalyzer unit, 529 system certificates, 223
logging to a FortiGuard Analysis server, 532 system configuration backup and restore, 231
logging to a Syslog server, 533 system configuration backup and restore,
logging to memory, 533 FortiManager, 233
logging to WebTrends, 534 system configuration, central management options,
MAC filter list, 156 234
modem connections, firewall policy, 134 system status widgets, 68
modem interface, 129 system time, 80
MTU size, 126 TACACS+ authentication, 201
multicast settings, 284 TACACS+ server, 429, 430
NAT virtual IP, 341 topology diagram, 92, 93
OCSP certificates, 225 traffic shaping, 304
one-time schedule, 331 unknown IM users, 523
OSPF areas, 278 updates for FDN and FortiGuard services, 243
OSPF AS, 274 URL filter list, 488, 489
OSPF basic settings, 274 URL overrides, 493
OSPF interface, operating parameters, 279 user authentication settings, 445
OSPF networks, 279 user group, 438
OSPF settings, advanced, 277 user groups, 435
override server, 250 VDOM configuration settings, 97, 102
password, 197 VDOM configuration settings, advanced, 100
password, administrator, 205 VDOM configuration settings, global, 98
peer users and peer groups, 432 VDOM interface, 103
ping server, 137 VDOM, new, 101
PKI authentication, 203 VIP group, 354
policy, 297, 302 virtual IP, 338
policy route, 264 virtual IP group, 354
PPPoE or PPPoA interface settings, 120 virtual IP, port translation only, 353
PPTP range, 411 virtual IPSec interface, 122
protection profile, 381 VLAN subinterface, 141
push updates, 251 VoIP log, 539
RADIUS authentication, 198 VoIP options, 379
RADIUS server, 425 VPN firewall policy-based internet browsing, 407
recurring schedule, 330 VPN route-based internet browsing, 407
redundant interface, 117 web content block list, 483, 484
redundant mode, 132 web content exempt list, 485, 486, 487
remote authentication, 197 web filtering options, 369

578 01-30007-0203-20090112
Index
wireless interface, 152 AMC enhancements, 3.0 MR7, 21

zone, 128 AMC module, 109
address antispam
firewall address group, 318 port 53, 247
list, 316 port 8888, 247
address group, 318 antispam email address list
adding, 319 adding, 508
creating new, 318 viewing, 509
list, 318 antispam IP address list
Address Name viewing, 506
firewall address, 318 antispam. See also spam filter, 499
admin antivirus
administrator account, 49 adware grayware, 460
administrative access av_failopen, 461
changing, 50 BHO grayware, 460
interface settings, 114, 123, 127 CLI configuration, 461
monitoring logins, 216 configure antivirus heuristic, 461
administrative distance, 256 configuring grayware list, 459
administrative interface. See web-based manager dial grayware, 460
administrator download grayware, 460
assigning to VDOM, 105 file block, 450
administrator account file block list, 453
access profile, 208 game grayware, 460
admin, 49 heuristics, 461
configuring, 205 hijacker grayware, 460
netmask, 206, 207 joke grayware, 460
trusted host, 207 keylog grayware, 460
administrator password misc grayware, 460
changing, 49 NMT grayware, 460
optimize, 461
administrator settings, 215
P2P grayware, 460
administrators plugin grayware, 461
viewing list, 204 quarantine, 454
administrators, monitoring, 216 quarantine files list, 455
ADSL, 115, 120 RAT grayware, 461
Advanced Mezzanine Card (AMC), 73 scanning large files, 462
adware splice, 368
grayware category, 460 spy grayware, 461
age limit streaming mode, 368
quarantine, 458 system global av_failopen, 461
aggregate interface system global optimize, 461
creating, 116 toolbar grayware, 461
AH, predefined service, 322 virus list, 458
alert email antivirus and attack definitions, 249
options, 547 antivirus options
SMTP user, 548 protection profile, 367
alert mail messages, 189 antivirus updates, 249
Alert Message Console manual, 84
clearing messages, 75 through a proxy server, 250
alert message console ANY
viewing, 74 service, 322
ALG AOL
controlling the SIP ALG, 392 service, 322
SIP, 385 append tag format
allow inbound protection profile, 375
IPSec firewall policy, 306 append tag to location
allow outbound protection profile, 374
IPSec firewall policy, 306 application level gateway
allow web sites when a rating error occurs SIP, 385
protection profile, 371 applying through protection profile, 378
allowed archive content meta-information
web category report, 498 protection profile, 376, 377
area border router (ABR), 273, 278

01-30007-0203-20090112 579
Index
ARP, 338 band

proxy ARP, 338 wireless setting, 151
AS bandwidth
OSPF, 273 guaranteed, 301
attachments maximum, 301
viruses, 189 banned word
attack updates web content block, 484, 486
manual, 84 banned word (spam filter)
scheduling, 249 action, 504
through a proxy server, 250 adding words to the banned word list, 504
Authentication catalog, 502
IPSec VPN, phase 2, 402 language, 504, 505
authentication list, 503
client certificates and SSL VPN, 415 pattern, 504, 505
configuring remote authentication, 197 pattern type, 504, 505
defining settings, 445 banned word check
firewall policy, 301, 302, 303 protection profile, 374
MD5, 279 banned word list
RIP, 272 creating new, 503
server certificate and SSL VPN, 415 banned word list catalog
Authentication Algorithm viewing, 502
IPSec VPN, manual key, 404, 406 beacon interval
Authentication Key wireless setting, 151, 155
IPSec VPN, manual key, 406 BFD
Authentication Method configuring on BGP, 287
IPSec VPN, phase 1, 397 configuring on OSPF, 288
Auto Key disabling, 287
IPSec VPN, 395 BGP
Autokey Keep Alive AS, 281
IPSec VPN, phase 2, 403 flap, 281
automatic discovery, 530 graceful restart, 281
autonomous system (AS), 273, 281 MED, 281
AutoSubmit RFC 1771, 281
quarantine, 458 service, 322
settings, viewing, 282
autosubmit list
stabilizing the network, 281
configuring, 457
enabling uploading, 457 BHO
quarantine files, 456 grayware category, 460
av_failopen black/white list, 505
antivirus, 461 blackhole route, 258
block, 390
B block audio (IM)
protection profile, 378
back to HA monitor block file transfers (IM)
HA statistics, 174 protection profile, 378
backing up block login (IM)
2.80 MR11 configuration, 556 protection profile, 378
3.0 config, 561 blocked
3.0 config to FortiUSB, 561 web category report, 498
3.0 config to PC, 561 bookmark
config using web-based manager, 2.80 MR11, 556 online help icon, 54
FortiGate configuration, 52
Boot Strap Router (BSR), 283
system configuration, 231
BOOTP, 164
backing up 3.0 config using web-based manager, CLI,
FortiUSB key, 566 browsing log information, 542
backing up previous config to PC, FortiUSB key, 568 button bar
features, 52
backup (redundant) mode
modem, 129
backup and restore, system maintenance, 231 C
backup mode CA certificates
modem, 132 importing, 226
viewing, 226

580 01-30007-0203-20090112
Index
catalog Concentrator Name

banned word, 502 IPSec VPN, concentrator, 408
content block, 482 config antivirus heuristic
content exempt, 485 CLI command, 461
email address back/white list, 508 configuration
IP address black/white list, 505 backing up FortiGate configuration, 52
URL filter, 487 restore, 232
viewing file pattern, 452 connect to server, 116
category connecting
protection profile, 372 modem, dialup account, 134
web category report, 498 web-based manager, 48
category block conservation mode, 181
configuration options, 492 contact information
reports, 497 SNMP, 176
central management, 212 contacting customer support, 52
certificate authentication, 219 content archive
Certificate Name viewing, 87
IPSec VPN, phase 1, 397 content archive options
certificate, security. See system certificate full, 375
certificate, server, 415 metadata, 375
certificate. See system certificates protection profile, 375
channel summary, 375
wireless setting, 151 content block
channel, wireless setting catalog, 482
FortiWiFi-60, 154 web filter, 482
CIDR, 315 content exempt
cipher suite catalog, 485
SSL VPN, 415 content streams
CLI, 48 replacement messages, 188
access profile, 209 contents
connecting to from the web-based manager, 51 online help icon, 54
CLI configuration cookie filter
antivirus, 461 protection profile, 370
customizing CLI console, 68 CPU usage
system network, 123 HA statistics, 174
using in web-based manager, 76 CRL (Certificate Revocation List)
web category block, 497 importing, 228
CLI console, 76 viewing, 227
client certificates custom service
SSL VPN, 415 adding, 325
cluster member, 171 adding a TCP or UDP custom service, 325
cluster members list, 173 list, 325
priority, 173 custom signatures
role, 173 intrusion protection, 467
cluster unit viewing, 467
disconnecting from a cluster, 175 customer service, 46
code, 326 customer support
column settings, 543 contacting, 52
configuring, 62
system network, 110 D
using with filters, 63
comfort clients dashboard, 47, 67
protection profile, 369 data encryption
comments wireless setting, 153
firewall policy, 302 date
on documentation, sending, 46 quarantine files list, 455
concentrator DC
adding, 408 quarantine files list, 456
equivalent for route-based VPN, 395 DCE-RPC
IPSec tunnel mode, 407 firewall service, 322
IPSec VPN, policy-based, 407 Dead Peer Detection
IPSec VPN, phase 1, 401

01-30007-0203-20090112 581
Index
default gateway, 259 documentation

default route, 259 commenting on, 46
Designated Routers (DR), 283 Fortinet, 44
destination domain name, 316
firewall policy, 296, 299, 303 DoS sensor, 475
destination IP address IPS, 375
system status, 86 list, 475
destination NAT SCCP, 379
SIP, 385 SIP, 379
destination network address translation (DNAT) dotted-decimal notation, 278
virtual IPs, 335, 336 double NAT, 359
destination port, custom services, 326 downgrading. See also reverting
device priority 2.80 MR11 using the CLI, 563
HA, 169 2.80 MR11 using web-based manager, 562
subordinate unit, 174 download
DH Group grayware category, 460
IPSec VPN, phase 1, 400 quarantine files list, 456
IPSec VPN, phase 2, 403 DSCP, 308
DHCP dummy policy
and IP Pools, 300 SIP, 387
configuring relay agent, 163 duplicates
configuring server, 163 quarantine files list, 456
servers and relays, 161 Dynamic DNS
service, 162 IPSec VPN, phase 1, 397
system, 161 monitor, 409
transparent mode, 161 network interface, 122
viewing address leases, 165 VPN IPSec monitor, 409
DHCP (Dynamic Host Configuration Protocol), 115 dynamic IP pool
configuring on an interface, 118 SIP, 386
service, 322 dynamic routing, 267
DHCP-IPSec OSPF, 273
IPSec VPN, phase 2, 403 PIM, 283
diagnose dynamic virtual IP
commands, 51 adding, 352
diagram
topology viewer, 90 E
dial
grayware category, 460 ECMP, 258
dialup VPN email
monitor, 409 online help icon, 53
differentiated services email address
firewall policy, 308 action type, 509
adding to the email address list, 510
differentiated services code point (DHCP), 308
back/white list catalog, 508
DiffServ BWL check, protection profile, 374
firewall policy, 308 list, spam filter, 509
Directory Service pattern type, 509
configuring server, 433, 434 email blocked as spam, 189
FSAE, 434
enable FortiGuard Web Filtering
disconnecting protection profile, 371
modem, dialup account, 134
enable FortiGuard Web Filtering overrides
disk space protection profile, 371
quarantine, 458
Enable perfect forward secrecy (PFS)
display content meta-information on dashboard IPSec VPN, phase 2, 403
protection profile option, 376
Enable replay detection
Distinguished Name IPSec VPN, phase 2, 403
query, 429
enable session pickup
DNAT HA, 170
virtual IPs, 335, 336
encrypt configuration file
DNS backup configuration, 232
service, 322
Encryption

582 01-30007-0203-20090112
Index
Encryption Algorithm file name

IPSec VPN, manual key, 404, 406 quarantine files list, 455
Encryption Key file pattern
IPSec VPN, manual key, 406 catalog, 452
end IP quarantine autosubmit list, 456
IP pool, 358 filter
Equal Cost Multipath (ECMP), 258 filtering information on web-based manager lists,
ESP 58
service, 322 IPS sensor, 472
Ethernet over ATM (EoA), 115 quarantine files list, 455
example using with column settings, 63
firewall policy, 308 web-based manager lists, 58
source IP address and IP pool address matching, FINGER
357 service, 322
exclude range firewall, 293, 315, 321, 329, 333, 365
adding to DHCP server, 165 address list, 316
expire configuring, 293, 315, 365
system status, 86 configuring firewall service, 321
configuring service group, 327
expired
configuring virtual IP, 333
subscription, 245
configuring, schedule, 329
exported server certificates custom service list, 325
importing, 223 one-time schedule, 330
external interface overview, 293, 315, 321, 365
virtual IP, 338 overview, firewall schedule, 329
external IP address overview, virtual IP, 333
virtual IP, 338 policy list, 295
external service port policy matching, 293
virtual IP, 339 predefined services, 321
recurring schedule, 329
F virtual IP list, 337
firewall address
fail-open, CLI command for IPS, 478 adding, 317
FDN address group, 318
attack updates, 194 address name, 318
HTTPS, 248 create new, 317
override server, 246 IP range/subnet, 318
port 443, 248 list, 316
port 53, 247 name, 317
port 8888, 247 subnet, 318
port forwarding connection, 251 firewall address group
proxy server, 250 adding, 319
push update, 246 available addresses, 319
troubleshooting connectivity, 248 group name, 319
updating antivirus and attack definitions, 249 members, 319
FDS, 241 firewall IP pool list, 358
file block firewall IP pool options, 359
antivirus, 450
default list of patterns, 451
list, antivirus, 453

01-30007-0203-20090112 583
Index
firewall policy INFO_REQUEST, 323

action, 296 Internet-Locator-Service, 323
adding, 297 IRC, 323
adding a protection profile, 381 L2TP, 323
allow inbound, 306 LDAP, 323
allow outbound, 306 MGCP, 323
authentication, 301, 302, 303 NetMeeting, 323
changing the position in the policy list, 294 NFS, 323
comments, 302 NNTP, 323
configuring, 297 NTP, 323
creating new, 296 OSPF, 323
deleting, 294 PC-Anywhere, 323
destination, 296, 299, 303 PING, 323
differentiated services, 308 PING6, 323
DiffServ, 308 POP3, 323
example, 308 PPTP, 323
fixed port NAT option, 300 QUAKE, 324
FortiClient checking, 308 RAUDIO, 324
guaranteed bandwidth, 301 REXEC, 324
ID, 296 RIP, 324
inbound NAT, 306 RLOGIN, 324
insert policy before, 297 RSH, 324
list, 295 SAMBA, 324
log traffic, 301, 304 SCCP, 324
matching, 293 SIP, 324
maximum bandwidth, 301 SIP-MSNmessenger, 324
modem, 134 SMTP, 324
moving, 294 SNMP, 324
multicast, 295 SSH, 324
outbound NAT, 306 SYSLOG, 324
protection profile, 300 TALK, 324
schedule, 296, 299, 304 TCP, 324
service, 296, 300 TELNET, 324
source, 296, 299 TFTP, 324
SSL VPN options, 307 TIMESTAMP, 324
traffic shaping, 301, 304 UDP, 324
user groups, 436 UUCP, 324
firewall protection profile VDOLIVE, 324
default protection profiles, 366 viewing custom service list, 325
list, 366 viewing list, 321
options, 367 WAIS, 325
firewall service WINFRAME, 325
AH, 322 X-WINDOWS, 325
ANY, 322 firmware
AOL, 322 reverting to previous version, 83
BGP, 322 upgrading to a new version, 82
DCE-RPC, 322 viewing, 235
DHCP, 322 fixed port
DNS, 322 firewall policy NAT option, 300
ESP, 322 IP pool, 357
FINGER, 322 FortiAnalyzer, 40, 529
FTP, 322 accessing logs, 541
FTP_GET, 322 configuring report schedules, 551
FTP_PUT, 322 logging to, 529
GOPHER, 322 printing reports, 554
GRE, 322 VDOM, 96
group list, 327 FortiBridge, 40
H323, 322 FortiClient, 40
HTTP, 322 Host Security checking, 308
HTTPS, 322 system maintenance, 230
ICMP_ANY, 323 viewing version, 236
IKE, 323 FortiGate 4000, 109
IMAP, 323
FortiGate documentation
INFO_ADRESS, 323
commenting on, 46

584 01-30007-0203-20090112
Index
FortiGate logging, 525 FortiManager, 40

FortiGate proxy, 378 backup configuration, 231
FortiGate SNMP event, 178 restore configuration, 232
FortiGate traps, 180 FortiManager Management Services
FortiGate unit revision control, 238
registering, 52 Fortinet customer service, 46
FortiGate-224B, 36 Fortinet documentation, 44
FortiGate-5001A Fortinet Family Products, 40
introduction, 31 Fortinet Knowledge Center, 46
FortiGate-5001FA2 Fortinet MIB, 179, 182
introduction, 31 FortiWiFi-50B
FortiGate-5001SX wireless settings, 150
introduction, 31 FortiWiFi-60A
FortiGate-5002FB2 wireless settings, 150
introduction, 32 FortiWiFi-60AM
FortiGate-5020 wireless settings, 150
chassis, 30 FortiWiFi-60B
FortiGate-5050 wireless settings, 150
chassis, 30 fragmentation threshold
FortiGate-5140 wireless setting, 154, 156
chassis, 30 FSAE
FortiGate-ASM-FB4, 109 Directory Service server, 434
FortiGuard, 40 FSAE-related enhancements for 3.0 MR7, 21
back up configuration, 231 FTP
changing the host name, 497 service, 322
CLI configuration, 497 FTP_GET
configuration options, 492 service, 322
configuring FortiGuard Web filtering options, 370 FTP_PUT
manually configuring definition updates, 84 service, 322
override options for user group, 441 fully qualified domain name (FQDN), 316
report allowed, 498
report blocked, 498
report category, 498
G
report profiles, 498 game
report range, 498 grayware category, 460
report type, 498 Geography, 154
reports, 497 geography
restore configuration, 232 wireless setting, 151, 154
web filter, 491 GOPHER
FortiGuard Analysis Service, 526 service, 322
accessing logs on FortiGuard Analysis server, 542 graceful restart, 281
portal web site, 527
graphical user interface. See web-based manager
FortiGuard Antispam
grayware
email checksum check, 373
adware, 460
IP address check, 373
antivirus, 459
FortiGuard Distribution Network. See FDN BHO, 460
FortiGuard Distribution Server. See FDS dial, 460
FortiGuard Management Services download, 460
remote management options, 234 game, 460
FortiGuard Services, 242 hijacker, 460
antispam service, 242 joke, 460
configuring antispam service, 242 keylog, 460
configuring updates for FDN and services, 243 misc, 460
configuring web filter service, 243 NMT, 460
FortiGuard Management and Analysis Services, P2P, 460
243 plugin, 461
licenses, 70, 243 RAT, 461
management and analysis service options, 248 spy, 461
support contract, 244 toolbar, 461
web filtering, 243 updating antivirus and attack definitions, 249
web filtering and antispam options, 247 GRE, 272
FortiMail, 40 service, 322

01-30007-0203-20090112 585
Index
group name heuristics

HA, 170 antivirus, 461
grouping services, 327 quarantine, 461
groups high availability See HA, 167
user, 435 hijacker
guaranteed bandwidth grayware category, 460
firewall policy, 301 host name
traffic shaping, 301 changing, 80
GUI. See web-based manager changing for a cluster, 173
viewing, 80
H hostname
cluster members list, 173
H323 HTTP, 355
service, 322 service, 322
HA, 167, 173 virus scanning large files, 462
changing cluster unit host names, 173 HTTPS, 47, 194
cluster logging, 528 service, 322
cluster member, 173 hub-and-spoke
cluster members list, 171 IPSec VPN (see also concentrator), 394
configuring, 167
device priority, 169
disconnecting a cluster unit, 175 I
enable session pickup, 170 ICMP custom service, 326
group name, 170 code, 326
heartbeat interface, 171 protocol type, 326
host name, 173 type, 326
interface monitoring, 170 ICMP echo request, 355
mode, 169 ICMP_ANY
out of band management, 109 service, 323
password, 170
ID
port monitor, 170
firewall policy, 296
router monitor, 290
routes, 290 idle timeout
session pickup, 170 changing for the web-based manager, 51
subordinate unit device priority, 174 IEEE 802.11a, channels, 148
subordinate unit host name, 174 IEEE 802.11b, channels, 149
VDOM partitioning, 171 IEEE 802.11g, channels, 150
viewing HA statistics, 173 IEEE 802.3ad, 116
HA statistics IKE
active sessions, 174 service, 323
back to HA monitor, 174 IM
CPU usage, 174 adding user, 522
intrusion detected, 174 applying through protection profile, 378
memory usage, 174 configuring unknown users, 523
monitor, 174 viewing current user list, 521
network utilization, 174 IM, P2P & VoIP, 515
refresh every, 174 IM/P2P/VoIP
status, 174 viewing statistics, 518
total bytes, 174 viewing statistics by protocol, 520
total packets, 174 viewing user list, 522
unit, 174 IMAP
up time, 174 service, 323
virus detected, 174
inbound NAT
health check monitor IPSec firewall policy, 306
configuring, 355
index
heartbeat, HA online help icon, 54
interface, 171
INFO_ADDRESS
HELO DNS lookup service, 323
INFO_REQUEST
help service, 323
navigating using keyboard shortcuts, 55
insert policy before
searching the online help, 54
firewall policy, 297
using FortiGate online help, 53

586 01-30007-0203-20090112
Index
inspect non-standard port (IM) IP pool

protection profile, 378 adding, 359
Instant Messaging. See IM configuring, 359
interface creating new, 358
adding system settings, 112 DHCP, 300
administrative access, 114, 123, 127 end IP, 358
administrative status, 109 fixed port, 357
configuring administrative access, 125 interface, 359
GRE, 272 IP range/subnet, 359, 360
IP pool, 359 list, 358
loopback, 109, 258 name, 359, 360
modem, configuring, 129 options, 359
MTU, 114 PPPoE, 300
proxy ARP, 338 proxy ARP, 338
software switch, 113 SIP, 386
wireless, 147 start IP, 358
WLAN, 147 transparent mode, 361
Interface Mode, 111 IP range/subnet
interface monitoring firewall address, 318
HA, 170 IP pool, 359, 360
internet browsing IPS
IPSec VPN configuration, 407 see intrusion protection
Internet-Locator-Service IPS sensor
service, 323 filter, 472
inter-VDOM links, 103 options, protection profile, 375
introduction IPSec, 272
Fortinet documentation, 44 IPSec firewall policy
intrusion detected allow inbound, 306
HA statistics, 174 allow outbound, 306
inbound NAT, 306
intrusion protection
outbound NAT, 306
custom signature list, 467
DoS sensor list, 475 IPSec Interface Mode
DoS sensor, protection profile, 375 IPSec VPN, manual key, 406
fail-open, CLI command for IPS, 478 IPSec VPN, phase 1, 399
filter, 472 IPSec VPN
IPS sensor list, 469 adding manual key, 405
IPS sensor, protection profile, 375 authentication for user group, 436
predefined signature list, 465 Auto Key list, 395
protection profile options, 375 concentrator list, 407
protocol decoder, 468 configuring phase 1, 396
protocol decoder list, 468 configuring phase 1 advanced options, 399
signatures, 465 configuring phase 2, 401
socket-size, CLI command for IPS, 478 configuring phase 2 advanced options, 401
IP configuring policy-, route-based Internet browsing,
virtual IP, 337 407
Manual Key list, 404
IP address
monitor list, 409
action, antispam, 507
remote gateway, 436
antispam black/white list catalog, 505
route-based vs policy-based, 394
BWL check, protection profile, 374
defining PPTP range, 411 IPv6, 217, 258
IPSec VPN, phase 1, 397 IRC
list, spam filter, 506 service, 323
spam filter, 505 ISP, 115
IP address, configuring secondary, 126
IP custom service, 327 J
protocol number, 327 java applet filter
protocol type, 327 protection profile, 370
IP over ATM (IPoA), 115 joke
grayware category, 460

01-30007-0203-20090112 587
Index
K local certificates
options, 221
Keepalive Frequency viewing, 219
IPSec VPN, phase 1, 401 Local Gateway IP
key IPSec VPN, phase 1, 399
license, 254 Local ID
wireless setting, 153, 155 IPSec VPN, phase 1, 400
keyboard shortcut Local Interface
online help, 55 IPSec VPN, manual key, 406
Keylife IPSec VPN, phase 1, 397
IPSec VPN, phase 1, 400 local PC
IPSec VPN, phase 2, 403 backup configuration, 231
keylog restore configuration, 232
grayware category, 460 local ratings
Knowledge Center, 46 configuring, 496
local ratings list
L viewing, 495
L2TP, 436 Local SPI
service, 323 IPSec VPN, manual key, 405
language local user, 422
changing the web-based manager language, 50 local user account
spam filter banned word, 504, 505 configuring, 423
web content block, 484, 486 log
web-based manager, 50, 216 attack anomaly, 538
LDAP attack signature, 538
configuring server, 426, 427 column settings, 543
service, 323 messages, 542
SSL VPN, 307 raw or formatted, 543
user authentication, 423 to FortiAnalyzer, 529
LDAP Distinguished Name query, 429 traffic, firewall policy, 301, 304
LDAP server log messages
authentication, 197 viewing, 542
configuring authentication, 199 log traffic
license key, 254 firewall policy, 301, 304
licenses log types, 535
viewing, 70 antivirus, 537
attack, 538
limit (P2P)
event, 536
IM, P2P, 538
lists spam filter, 538
using web-based manager, 57 traffic, 535
VOIP, 539
web filter, 537

588 01-30007-0203-20090112
Index
logging, 540 Manual Key

accessing logs in memory, 540 IPSec VPN, 404
accessing logs on FortiAnalyzer unit, 541 map to IP
accessing logs on FortiGuard Analysis server, 542 virtual IP, 337
ActiveX filter, 380 map to port
alert email, configuring, 547 virtual IP, 337, 339
applying through protection profile, 380 matched content, 356
basic traffic reports, 549 matching
blocked files, 380 firewall policy, 293
browsing log messages, 542
max filesize to quarantine
cluster, HA, 528
quarantine, 458
configuring content archive, 546
configuring FortiAnalyzer report schedules, 551 maximum bandwidth, 301
configuring graphical system memory report, 550 firewall policy, 301
connecting using automatic discovery, 530 traffic shaping, 301
content archive, 545 MD5
content block, 380 OSPF authentication, 279, 280
cookie filter, 380 Members
customizing display of log messages, 543 IPSec VPN, concentrator, 408
FortiGuard Analysis server, 532 memory usage
IM activity, 381 HA statistics, 174
intrusions, 381 menu
java applet filter, 380 web-based manager menu, 57
log severity levels, 527 messages, log, 542
log types, 535 MGCP
oversized files/emails, 380 service, 323
P2P activity, 381 mheader, 510
printing FortiAnalyzer reports, 554 MIB, 182
rating errors, 381 FortiGate, 179
reports, 549 RFC 1213, 179
searching, filtering logs, 545 RFC 2665, 179
SIP, 389
misc
spam, 381
storing logs, 528
testing FortiAnalyzer configuration, 531 Mode
to a FortiAnalyzer unit, 529 IPSec VPN, phase 1, 397
to memory, 533 mode
to syslog server, 533 HA, 169
to WebTrends, 534 modem
URL block, 380 adding firewall policies, 134
viewing content archives, 546 backup mode, 132
viewing raw or formatted logs, 543 connecting and disconnecting to dialup account,
viruses, 380 134
web site, FortiGuard Analysis Service, 527 redundant (backup) mode, 129
logging out standalone mode, 129, 133
web-based manager, 56 viewing status, 134
loopback interface, 109, 258 modem interface
lost password configuring, 129
recovering, 49, 197, 206, 207 monitor
low disk space administrator logins, 216
quarantine, 458 HA statistics, 174
IPSec VPN, 409
routing, 289
M moving a firewall policy, 294
MAC address MS-CHAP, 425
filtering, 156 MS-CHAP-V2, 425
wireless setting, 154 MTU size, 114, 125
MAC filter multicast, 283
configuring FortiWiFi-60, 157 multicast destination NAT, 285
wireless, 156 multicast policy, 295
MAC filter list multicast settings
configuring, 156 overriding, 285
viewing, 156 viewing, 284
management VDOM, 102, 106 Multi-Exit Discriminator (MED), 281

01-30007-0203-20090112 589
Index
N online help
content pane, 53
Name keyboard shortcuts, 55
IP pool, 359, 360 navigation pane, 54
IPSec VPN, manual key, 405 search, 54
IPSec VPN, phase 1, 397 using FortiGate online help, 53
IPSec VPN, phase 2, 401 operation mode, 193
NAT wireless setting, 151, 154
in transparent mode, 361 operational history
inbound, IPSec firewall policy, 306 viewing, 84
multicast, 285 optimize
outbound, IPSec firewall policy, 306 antivirus, 461
preserving SIP NAT IP, 391
OSPF
push update, 251
area ID, 279
SIP, 385
AS, 276
symmetric, 336
authentication, 279, 280
NAT virtual IP Dead Interval, 281
adding for single IP address, 341 dead packets, 281
adding static NAT virtual IP for IP address range, GRE, 280
343 Hello Interval, 281
Nat-traversal Hello protocol, 273
IPSec VPN, phase 1, 400 interface definition, 279
netmask IPSec, 280
administrator account, 206, 207 link-state, 273
NetMeeting LSA, 280
service, 323 multiple interface parameter sets, 280
network neighbor, 273
topology viewer, 90 network, 276
network address translation (NAT), 334 network address space, 280
network utilization NSSA, 278, 290
HA statistics, 174 path cost, 273
next regular area, 278
online help icon, 53 service, 323
NFS settings, 274
service, 323 stub, 278
virtual lan, 279
NMT
virtual link, 278
VLAN, 280
NNTP
OSPF AS, 273
service, 323
defining, 274
not registered
out of band, 109
subscription, 245
outbound NAT
Not-so-stubby Area (NSSA), 278
IPSec firewall policy, 306
not-so-stubby area (NSSA), 290
override server
Novel edirectory, 433 adding, 250
NTP oversized file/email
service, 323 protection profile, 369
O P
object identifier (OID), 182 P1 Proposal
OCSP certificates IPSec phase 1, 399
importing, 225 P2 Proposal
one-time schedule IPSec VPN, phase 2, 402
adding, 331 P2P, 378
configuring, 331 grayware category, 460
creating new, 330 supported protocols list, 516
list, 330
packets
start, 331
VDOM, 96
stop, 331
page controls
web-based manager, 61
PAP, 425

590 01-30007-0203-20090112
Index
pass fragmented email policy

protection profile, 369 action, 296
password adding, 297
configuring authentication password, 197 allow inbound, 306
HA, 170 allow outbound, 306
recovering lost password, 49, 197, 206, 207 authentication, 301, 302, 303
PAT changing the position in the policy list, 294
virtual IPs, 334 comments, 302
pattern configuring, 297
default list of file block patterns, 451 creating new, 296
spam filter banned word, 504, 505 deleting, 294
pattern type destination, 296
spam filter banned word, 504, 505 differentiated services, 308
spam filter email address, 509 DiffServ, 308
web content block, 484, 486 example, 308
fixed port NAT option, 300
PC-Anywhere
FortiClient checking, 308
service, 323
guaranteed bandwidth, 301
peer group ID, 296
configuring, 432 inbound NAT, 306
Peer option insert policy before, 297
IPSec VPN, phase 1, 398 list, 295
peer user log traffic, 301, 304
configuring, 432 matching, 293
peer-to-peer. See P2P maximum bandwidth, 301
Perl regular expressions move, 294
spam filter, 511 multicast, 295
Phase, 401 outbound NAT, 306
phase 1 protection profile, 300
IPSec VPN, 396, 401 schedule, 296, 299, 304
phase 1 advanced options service, 296, 300
IPSec VPN, 399 source, 296
phase 2 SSL VPN options, 307
IPSec VPN, 401 traffic shaping, 301, 304
phase 2 advanced options policy route
IPSec VPN, 401 moving in list, 265
PIM policy-based routing, 263
BSR, 283 POP3
dense mode, 283 service, 323
DR, 283 port 53, 247
RFC 2362, 283 port 8888, 247
RFC 3973, 283 port 9443, 251
RP, 283 port address translation
sparse mode, 283 virtual IPs, 334
PING, 355 port forwarding, 334
service, 323 port monitor
ping server HA, 170
adding to an interface, 137 PPPoE
PING6 and IP Pools, 300
firewall service, 323 PPPoE (Point-to-Point Protocol over Ethernet)
pinholing configuring ADSL interface, 115
RTP, 390 RFC 2516, 120
SIP, 390 PPTP, 411, 436
PKI, 431 service, 323
authentication, 203 PPTP range
plugin defining addresses, 411
grayware category, 461 predefined services, 321
Point-to-Point Protocol over ATM (PPPoA), 115 predefined signature
default action, 466
list, 465
Pre-shared Key

01-30007-0203-20090112 591
Index
pre-shared key logging, oversized files/emails, 380

wireless setting, 153, 155 logging, P2P activity, 381
previous logging, rating errors, 381
online help icon, 53 logging, spam, 381
print logging, URL block, 380
online help icon, 53 logging, viruses, 380
priority options, 367
cluster members, 173 oversized file/email, 369
private key pass fragmented email, 369
importing, 223, 224 provide details for blocked HTTP errors, 371
quarantine, 369
product registration, 52
rate images by URL, 371
products, family, 40 rate URLs by domain and IP address, 372
profile return email DNS check, 374
category block reports, 498 scan (default protection profile), 366
proposal SIP, 389
IPSec phase 1, 399 spam action, 374
IPSec VPN, phase 2, 402 spam filtering options, 373
protection profile strict (default protection profile), 366
action (P2P), 378 strict blocking (HTTP only), 372
ActiveX, 370 tag format, 375
add signature to outgoing email, 369 tag location, 374
adding to a firewall policy, 381 unfiltered (default protection profile), 366
allow web sites when a rating error occurs, 371 virus scan, 368
antivirus options, 367 web (default protection profile), 366
append tag format, 375 web content block, 369
append tag to location, 374 web content exempt, 370
archive content meta-information, 376, 377 web filtering options, 369, 480
banned word check, 374 web resume download block, 370
block audio (IM), 378 web URL block, 370
block file transfers (IM), 378 protocol
block login (IM), 378 number, custom service, 327
category, 372 OSPF Hello, 273
comfort clients, 369 service, 322
configuring IM/P2P/VoIP, 518 system status, 86
content archive options, 375 type, custom service, 326
cookie filter, 370 virtual IP, 339
default protection profiles, 366 protocol decoder, 468
display content meta-information on dashboard, list, 468
376 Protocol Independent Multicast (PIM), 283
DoS sensor, 375
protocol type, 327
email address BWL check, 374
enable FortiGuard Web Filtering, 371 provide details for blocked HTTP errors
enable FortiGuard Web Filtering overrides, 371 protection profile, 371
file block, 368 proxy
firewall policy, 300 SIP, 383
FortiGuard Antispam IP address check, 373 proxy ARP, 338
FortiGuard email checksum check, 373 FortiGate interface, 338
HELO DNS lookup, 374 IP pool, 338
inspect non-standard port (IM), 378 virtual IP, 338
IP address BWL check, 374 Proxy ID Destination
IPS sensor, 375 IPSec interface mode, 409
IPS sensor options, 375 Proxy ID Source
java applet filter, 370 IPSec interface mode, 409
limit (P2P), 378 proxy server, 250
list, 366 push updates, 250
logging, ActiveX filter, 380 push update, 246
logging, blocked files, 380 configuring, 250
logging, content block, 380 external IP address changes, 251
logging, cookie filter, 380 IP address changes, 251
logging, IM activity, 381 management IP address changes, 251
logging, intrusions, 381 through a proxy server, 250
logging, java applet filter, 380

592 01-30007-0203-20090112
Index
Q rate URLs by domain and IP address

QoS, 308 RAUDIO
QUAKE service, 324
service, 324 read & write access level
quality of service, 308 administrator account, 80, 81, 204
quarantine read only access level
age limit, 458 administrator account, 80, 82, 204, 206
antivirus, 454 reading log messages, 542
autosubmit list, 456 recurring schedule
autosubmit list file pattern, 456 adding, 330
configuring, 457 configuring, 330
configuring the autosubmit list, 457 creating new, 329
enable AutoSubmit, 458 list, 329
enabling uploading autosubmit file patterns, 457 select, 330
heuristics, 461 start, 330
low disk space, 458 stop, 330
max filesize to quarantine, 458
redirect
options, 458
SIP, 383
redundant interface
quarantine files list
adding system settings, 117
antivirus, 455
apply, 455 redundant mode
date, 455 configuring, 132
DC, 456 refresh every
download, 456 HA statistics, 174
duplicates, 456 registering
file name, 455 FortiGate unit, 52
filter, 455 regular administrator, 195
service, 456 relay
sorting, 455 DHCP, 161, 163
status, 456 remote administration, 125, 194
status description, 456 remote certificates
TTL, 456 options, 224
upload status, 456 viewing, 224
query, 429 Remote Gateway
Quick Mode Selector IPSec manual key setting, 405
IPSec VPN, phase 2, 403 IPSec VPN, manual key, 404
R VPN IPSec monitor field, 409
remote peer
RADIUS manual key configuration, 405
configuring server, 425
Remote SPI
servers, 424
IPSec VPN, manual key, 405
SSL VPN, 307
user authentication, 423 remote user authentication, 423
viewing server list, 424 Rendezvous Point (RP), 283
WPA Radius, 153 replacement messages, 188
RADIUS server report
authentication, 197, 198 basic traffic, 549
wireless setting, 153 configuring report schedules, 551
RADIUS server name FortiAnalyzer, printing, 554
wireless setting, 155 FortiGuard, 497
range type, category block, 498
web category reports, 498 viewing FortiAnalyzer reports, 553
web category block, 497
RAT
grayware category, 461 restore
configuration, 232
rate images by URL
protection profile, 371 restoring 2.80 MR11 configuration, 564
using the CLI, 564
rate limiting
using web-based manager, 564
SCCP, 379
SIMPLE, 378, 379 restoring previous config, 570
SIP, 379, 388 restoring previous config using FortiUSB key, 572

01-30007-0203-20090112 593
Index
return email DNS check RSH

protection profile, 374 firewall service, 324
Reverse Path Forwarding (RPF), 285 RTP, 385
reverting pinholing, 390
backing up 3.0 config, 561 RTS threshold
reverting to a previous 3.0 firmware version, 568 wireless setting, 154, 156
reverting to a previous 3.0 maintenance release, 569
REXEC S
firewall service, 324
SAMBA
RFC, 283 service, 324
RFC 1058, 268 scan
RFC 1213, 176, 179 default protection profile, 366
RFC 1215, 180 SCCP
RFC 1321, 279 DoS sensor, 379
RFC 1771, 281 firewall service, 324
RFC 2132, 164 protection profile, 379
RFC 2362, 283 rate limiting, 379
RFC 2453, 268 schedule
RFC 2474, 308 antivirus and attack definition updates, 249
RFC 2475, 308 firewall policy, 296, 299, 304
RFC 2516, 120 one-time schedule list, 330
recurring schedule list, 329
RFC 2665, 176, 179
scheduled updates
RFC 3509, 273
through a proxy server, 250
RFC 3973, 283
screen resolution
RFC 5237, 264 minimum recommended, 47
RIP search
authentication, 272 online help, 54
hop count, 268 online help icon, 54
RFC 1058, 268 online help wildcard, 55
RFC 2453, 268
searching
service, 324
routing table, 291
settings, viewing, 268
split horizon, 272 security
version 1, 268 MAC address filtering, 156
version 2, 268 security certificates. See system certificates
RLOGIN security mode
service, 324 wireless setting, 153, 155
role select
cluster members, 173 recurring schedule, 330
route sensor
HA, 290 DoS, 475
router monitor IPS, 469
HA, 290 separate server certificates
routing importing, 224
administrative distance, 256 server
blackhole, 258 DHCP, 161
configuring, 137 log WebTrends setting, 534
ECMP, 258 server certificate, 415
loopback interface, 258 server certificates
monitor, 289 importing, 223, 224
static, 258 server health, 356
routing policy server load balance port forwarding virtual IP
protocol number, 264 adding, 350
routing table, 289 server load balance virtual IP
searching, 291 adding, 348

594 01-30007-0203-20090112
Index
service UUCP, 324

AH, 322 VDOLIVE, 324
ANY, 322 WAIS, 325
AOL, 322 WINFRAME, 325
BGP, 322 X-WINDOWS, 325
custom service list, 325 service group, 327
DCE-RPC, 322 adding, 327, 328
DHCP, 162, 322 create new, 327
DNS, 322 list, 327
ESP, 322 service port
FINGER, 322 virtual IP, 337
firewall policy, 296, 300 service set identifier (SSID), 107
FTP, 322 Session Initiation Protocol for Instant Messaging and
FTP_GET, 322 Presence Leveraging Extensions. See SIMPLE
FTP_PUT, 322
Session Initiation Protocol. See SIP
GOPHER, 322
GRE, 322 session list
group, 327 viewing, 85
H323, 322 session pickup
HTTPS, 322 HA, 170
ICMP_ANY, 323 settings, 152
IKE, 323 administrators, 215
IMAP, 323 Shortest Path First (SPF), 273
INFO_ADDRESS, 323 show in contents
INFO_REQUEST, 323 online help icon, 54
Internet-Locator-Service, 323 show navigation
IRC, 323 online help icon, 53
L2TP, 323 signatures
LDAP, 323 custom, intrusion protection signatures, 467
MGCP, 323 SIMPLE
NetMeeting, 323 protection profile, 378, 379
NFS, 323 rate limiting, 378, 379
NNTP, 323 SIP, 383
NTP, 323 accepting register response, 392
organizing services into groups, 328 ALG, 385
OSPF, 323 application level gateway, 385
PC-Anywhere, 323 archiving communication, 390
PING, 323 blocking requests, 390
PING6, 323 configuring, 388
POP3, 323 configuring advanced features, 389
PPTP, 323 controlling client connection, 391
predefined, 321 controlling the SIP ALG, 392
QUAKE, 324 destination NAT, 385
quarantine files list, 456 different source and destination NAT for SIP and
RAUDIO, 324 RTP, 387
REXEC, 324 DoS sensor, 379
RIP, 324 dummy firewall policy, 387
RLOGIN, 324 enabling, 388
RSH, 324 logging, 389
SAMBA, 324 NAT, 385
SCCP, 324 NAT with dynamic IP pool, 386
service name, 322 operating modes, 383
SIP, 324 preserving NAT IP, 391
SIP-MSNmessenger, 324 protection profile, 379, 389
SMTP, 324 proxy, 383
SNMP, 324 rate limiting, 379, 388
SSH, 324 redirect, 383
SYSLOG, 324 RTP pinholing, 390
TALK, 324 service, 324
TCP, 324 source NAT, 385
TELNET, 324 support workflow, 388
TFTP, 324 triggering firewall policy, 387
TIMESTAMP, 324 turning on tracking, 389
UDP, 324 viewing statistics, 389

01-30007-0203-20090112 595
Index
VoIP, 383 SSL

SIP requests, 390 service definition, 322
SIP support workflow, 388 SSL VPN
SIP-MSNmessenger bookmark, 416
service, 324 bookmark group, 418
Skinny Call Control Protocol. See SCCP checking client certificates, 415
SMTP configuring settings, 414
service, 324 firewall policy, 307
user, 548 monitoring sessions, 416
setting the cipher suite, 415
SNAT
specifying server certificate, 415
virtual IPs, 335
specifying timeout values, 415
SNMP terminating sessions, 416
configuring community, 177 tunnel IP range, 415
contact information, 176 web-only mode, 413
event, 178
SSL VPN Client Certificate, 307
manager, 176, 177
MIB, 182 SSL VPN login message, 192
MIBs, 179 SSL VPN user group
queries, 178 configuring advanced options, 442
RFC 12123, 179 standalone mode
RFC 1215, 180 modem, 129, 133
RFC 2665, 179 start
service, 324 IP pool, 358
traps, 178, 180 one-time schedule, 331
SNMP Agent, 176 recurring schedule, 330
SNMP communities, 176 static IP
socket-size, CLI command for IPS, 478 monitor, 409
software switch, 113 static NAT port forwarding
sorting adding for IP address and port range, 346
quarantine files list, 455 adding for single address and port, 344
URL filter list, 491 static route
source adding, 138, 262
firewall policy, 296, 299 adding policy, 264
administrative distance, 256
source IP address
concepts, 255
system status, 86
creating, 258
source IP port default gateway, 259
system status, 86 default route, 259
source NAT editing, 258
SIP, 385 moving in list, 265
source port, 326 overview, 255
spam action policy, 263
protection profile, 374 policy list, 263
spam filter, 499 selecting, 256
adding an email address or domain to the email table building, 256
address list, 510 table priority, 257
adding words to the banned word list, 504 table sequence, 257
banned word list, 503 viewing, 258
email address list, 509 viewing in transparent mode, 137
IP address, 505 statistics
IP address list, 506 viewing, 85
Perl regular expressions, 511 viewing HA statistics, 173
spam filtering options status
protection profile, 373 HA statistics, 174
splice, 368 interface, 109
spy log WebTrends setting, 534
grayware category, 461 quarantine files list, 456
SSH, 194 status description
service, 324 quarantine files list, 456
SSID stop
wireless setting, 153, 155 one-time schedule, 331
SSID broadcast recurring schedule, 330
wireless setting, 153, 155 streaming mode, 368

596 01-30007-0203-20090112
Index
strict system status widgets

default protection profile, 366 customizing, 68
strict blocking (HTTP only) system time
protection profile, 372 configuring, 80
stub system wireless. See wireless
OSPF area, 278
subnet T
adding object, 92
firewall address, 318 TACACS+
subscription configuring server, 429, 430
expired, 245 user authentication, 423
not registered, 245 TACACS+ server
valid license, 245 authentication, 197, 201
superadministrator, 195 tag format
support protection profile, 375
Fortinet technical support, 46 tag location
switch mode, 111 protection profile, 374
sync interval, 80 TALK
service, 324
SYSLOG
service, 324 TCP, 355
service, 324
system administrators, 195
TCP custom service, 326
system certificate
adding, 325
FortiGate unit self-signed security certificate, 49
destination port, 326
system certificates, 219 protocol type, 326
CA, 226 source port, 326
CRL, 227
technical support, 46
importing, 223
OCSP, 225 TELNET
requesting, 221, 222 service, 324
viewing, 219 TFTP
system configuration, 167 service, 324
backup, 231 time
system DHCP see also DHCP, 161 configuring, 80
system global av_failopen timeout values
antivirus, 461 specifying for SSL VPN, 415
system global optimize TIMESTAMP
antivirus, 461 service, 324
system idle timeout, 194 toolbar
system information
viewing, 69 top attacks
viewing, 78
system maintenance
advanced, 237 top sessions
backup and restore, 231 viewing, 77
creating scripts, 240 top viruses
enabling push updates, 250 viewing, 78
firmware, 235 topology viewer, 90
firmware upgrade, 236 total bytes
FortiClient, 236 HA statistics, 174
managing configuration, 229 total packets
push update through a NAT device, 251 HA statistics, 174
remote FortiManager options, 233 tracking
remote management options, 234 SIP, 389
revision control, 238 traffic history
scripts, 240 viewing, 79
updating antivirus and attack definitions, 249 traffic reports
uploading scripts, 241 viewing, 549
USB disks, 238 traffic shaping
VDOM, 230 firewall policy, 301, 304
system resources guaranteed bandwidth, 301
viewing, 74 maximum bandwidth, 301
system status
viewing, 67

01-30007-0203-20090112 597
Index
transparent mode upload status

IP pools, 361 quarantine files list, 456
NAT, 361 URL block
VDOMs, 96 adding a URL to the web filter block list, 489
VIP, 361 configuring overrides, 493
virtual IP, 361 local categories, 495
VLAN, 143 web filter, 487
traps URL filter
SNMP, 180 adding new list, 488
trigging policy catalog, 487
SIP, 387 sorting in list, 491
troubleshooting viewing list, 488
FDN connectivity, 248 URL formats, 490
trusted host USB disk, 231
administrator account, 207 auto-install, 238
administrators options, 206 backup and restore configuration, 229
security issues, 207 backup configuration, 231
TTL formatting, 238
quarantine files list, 456 restore configuration, 232
tunnel IP range system maintenance, 238
SSL VPN, 415 user authentication
tunnel mode LDAP, SSL VPN, 307
SSL VPN, SSL VPN local, SSL VPN, 307
tunnel mode, 413 overview, 421
Tunnel Name PKI, 431
IPSec VPN, manual key, 404 RADIUS, SSL VPN, 307
remote, 423
Tx Power
wireless setting, 151, 155 user group
configuring, 438
type, 326
virtual IP, 338 user groups
configuring, 435
Directory Service, 437
U firewall, 436
UDP custom service, 326 SSL VPN, 437
adding, 325 viewing, 438
destination port, 326 UUCP
protocol type, 326 service, 324
source port, 326
UDP service, 324 V
unfiltered
valid license, 245
default protection profile, 366
VDOLIVE
unit
service, 324
HA statistics, 174
VDOM
unit operation
adding interface, 103
viewing, 72
assigning administrator, 105
up time assigning interface, 104
HA statistics, 174 configuration settings, 97
update enabling multiple VDOMs, 100
push, 250 FortiAnalyzer, 96
upgrading inter-VDOM links, 103
3.0 MR1 to 3.0 MR2 (and higher) using the CLI, 567 license key, 254
3.0 MR1 to 3.0 MR2 (and higher) using web-based management VDOM, 102
manager, 567 NAT/Route, 96
3.0 using the CLI, 559 packets, 96
3.0 using web-based manager, 559 system maintenance, 230
backing up using the CLI, 2.80 MR11, 556 transparent mode, 96
firmware, 82 VDOM partitioning
FortiGate unit to 3.0, 558 HA, 171
using the web-based manager, 559 verifying
using web-based manager, 2.80 MR11, 556 downgrade to 2.80 MR11, 563
upgrade to 3.0, 560

598 01-30007-0203-20090112
Index
viewing session list, 85

access profiles list, 210 SIP statistics, 389
address group list, 318 SSL VPN bookmark groups, 418
administrators, 216 SSL VPN bookmarks, 416
administrators list, 204 SSL VPN sessions, 416
Alert Message Console, 74 static route, 258
antispam email address list catalog, 508 static route (transparent mode), 137
antispam IP address list, 506 statistics, 85
antispam IP address list catalog, 505 system information, 69
antivirus file filter list, 453 system resources, 74
antivirus file pattern list catalog, 452 system status, 67
antivirus list, 458 system topology, 90
antivirus quarantined files list, 455 TACACS+ server, 429
autosubmit list, 456 top attacks, 78
banned word list, 503 top sessions, 77
banned word list catalog, 502 top viruses, 78
BGP settings, 282 traffic history, 79
CA certificates, 226 traffic reports, 549
certificates, 219 unit operation, 72
cluster members list, 171 URL filter list, 488
content archive, 87 URL filter list catalog, 487
content archives, 546 URL override list, 492
CRL (Certificate Revocation List), 227 user group list, 438
current IM user list, 521 VIP group list, 354
custom service list, firewall service, 325 virtual IP group list, 354
custom signatures, 467 virtual IP list, 337
DHCP address leases, 165 virtual IP pool list, 358
DoS sensor list, 475 web content block list, 483
firewall policy list, 295 web content block list catalog, 482
firewall service group list, 327 web content exempt list, 486
firewall service list, 321 web content exempt list catalog, 485
firmware, 235 wireless monitor, 159
FortiAnalyzer reports, 553 viewport, 90
FortiClient version, 236 VIP
FortiGuard support contract, 244 transparent mode, 361
grayware list, 459 VIP group
HA statistics, 173 configuring, 354
hostname, 80 Virtual Circuit Identification (VCI), 116
IM/P2P/VoIP statistics, 518
Virtual IP
IM/P2P/VoIP statistics by protocol, 520
transparent mode, 361
IM/P2P/VoIP user list, 522
IP pool list, 358 virtual IP, 338
IPS sensor list, 469 configuring, 338
IPS sensor options, 375 create new, 337, 354
IPSec VPN auto key list, 395 destination network address translation (DNAT),
IPSec VPN concentrator list, 407 335, 336
IPSec VPN manual key list, 404 external interface, 338
IPSec VPN monitor list, 409 external IP address, 338
LDAP server list, 426 external service port, 339
licenses, 70 health check monitor, 355
local ratings list, 495 IP, 337
log messages, 542 list, 337
modem status, 134 map to IP, 337
multicast settings, 284 map to port, 337, 339
one-time schedule list, 330 NAT, 334
operational history, 84 PAT, 334
protection profile list, 366 port address translation, 334
protocol decoder list, 468 protocol, 339
RADIUS server list, 424 server down, 356
recurring schedule list, 329 service port, 337
remote certificates, 224 SNAT, 335
revision control, 238 source network address translation, 335
RIP settings, 268 type, 338
routing information, 289 virtual IP group
configuring, 354

01-30007-0203-20090112 599
Index
virtual IP group list web content block

viewing, 354 banned word, 484, 486
virtual IP, port translation only language, 484, 486
adding, 353 pattern type, 484, 486
virtual IPSec protection profile, 369
configuring interface, 122 web filter, 484
virus detected web content block list
HA statistics, 174 web filter, 483
virus list, 458 web content exempt
virus name, 191 protection profile, 370
virus protection. See antivirus web content exempt list
virus scan adding, 485
protection profile, 368 web equivalent privacy, 153, 155
virus-infected attachments, 189 web filter, 479
VLAN adding a URL to the web URL block list, 489
adding firewall policy to subinterface, 145 configuring the web content block list, 484
adding subinterface, 141 configuring the web URL block list, 489
jumbo frames, 126 content block, 482
OSPF, 279 filter interaction, 480
overview, 138 FortiGuard, 491
protection profile options, 480
VoIP, 515
URL block, 487
SIP, 383
URL category, 247
supported protocols list, 517
web content block list, 483
VoIP options web URL block list, 488
applying through protection profile, 379
web filtering options
VoIP security, 384 protection profile, 369
VPN IPSec (see also IPSec VPN), 393 web filtering service, 191
VPN PPTP, 411 web resume download block
VPN SSL. See SSL VPN protection profile, 370
VPN tunnel web site, content category, 190
IPSec VPN, firewall policy, 306 Web UI. See web-based manager
VPN, IPSec web URL block
firewall policy, 306 configuring the web URL block list, 489
VPNs, 219, 411 list, 488
list, web filter, 488
W protection profile, 370
WAIS web-based manager, 47, 48
service, 325 changing the language, 50
connecting to the CLI, 51
web
idle timeout, 51
default protection profile, 366
language, 50, 216
web category block logging out, 56
changing the host name, 497 online help, 53
CLI configuration, 497 pages, 56
configuration options, 492 screen resolution, 47
report allowed, 498 using the menu, 57
report blocked, 498 using web-based manager lists, 57
report category, 498
web-only mode
report profiles, 498
SSL VPN, 413
report range, 498
report type, 498 WebTrends, 534
reports, 497 WEP, 153, 155
WEP128, 147, 153, 155
WEP64, 147, 153, 155
what’s new 3.0 MR7, 21

600 01-30007-0203-20090112
Index
what’s new, 3.0 MR7 wireless

alert email changes, 25 adding advanced settings, 155
AMC enhancements, 21 adding settings for WiFi-60, 154
authentication, 24 band, 151
chassis monitoring removed, 20 beacon interval, 151, 155
content archiving improvements, 25 channel, 151
dashboard, 22 channel, FortiWiFi-60, 154
DNS enhancements, 19 configuration, 147
email archive enhancements, 26 data encryption, 153
FortiGuard Analysis and Management Service, 22 fragmentation threshold, 154, 156
FSAE-related enhancements, 21 geography, 151, 154
HA heartbeat IP address change, 27 interface, 147
HA primary unit acts as router, 26 key, 153, 155
interface order change on HA heartbeat interface MAC address, 154
failover, 28 MAC filter, 156
intrusion protection, 24 operation mode, 151, 154
log messages, new and changed, 25 pre-shared key, 153, 155
modem support enhancements, 23 RADIUS server, 153
reports, 25 RADIUS server name, 155
router, 23 RTS threshold, 154, 156
SIP servers source port, 20 security, 153, 155
SNMP, 23 security mode, 153, 155
SSL VPN virtual desktop application, 24 settings FortiWiFi-50B, 150
standalone SSL VPN client, 24 settings FortiWiFi-60A, 150
support for operating systems for SSL VPN, 24 settings FortiWiFi-60AM, 150
system dashboard, 22 settings FortiWiFi-60B, 150
VDOM and Global icons, 23 SSID, 153, 155
virtual domains, 22 SSID broadcast, 153, 155
Wi-Fi protected access, 153, 155 Tx power, 151, 155
wildcard viewing monitor, 159
online help search, 55 WLAN
Windows Active Directory, 433 interface, 147
WINFRAME interface, creating on WiFi-60, 154
service, 325 WLAN interface
adding to a FortiWiFi-50B, 152
adding to a FortiWiFi-60A, 152
adding to a FortiWiFi-60AM, 152
adding to a FortiWiFi-60B, 152
WPA, 147, 153, 155
WPA Radius
wireless security, 153
WPA2, 147, 153
WPA2 Auto, 147, 153
WPA2 Radius
wireless security, 153
X
X.509 security certificates. See system certificates
XAuth
X-WINDOWS
service, 325
Z
zones
configuring, 128

01-30007-0203-20090112 601
Index

602 01-30007-0203-20090112
www.fortinet.com
www.fortinet.com

Fortiget

Uploaded by

Document Information

Original Description:

Original Title

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

Fortiget

Uploaded by

Copyright:

Available Formats

ADMINISTRAT ION GUIDE

© Copyright 2009 Fortinet, Inc. All rights reserved. No part of this

FortiGate Version 3.0 MR7 Administration Guide

FortiGate Version 3.0 MR7 Administration Guide

Web-based manager pages ............................................................................ 56

System Status .................................................................................. 67

Using virtual domains...................................................................... 95

FortiGate Version 3.0 MR7 Administration Guide

System Network ............................................................................. 107

System Wireless ............................................................................ 147

FortiGate Version 3.0 MR7 Administration Guide

System wireless settings .............................................................................. 150

System DHCP ................................................................................. 161

System Config ................................................................................ 167

FortiGate Version 3.0 MR7 Administration Guide

System Administrators.................................................................. 195

System Certificates........................................................................ 219

System Maintenance ..................................................................... 229

FortiGate Version 3.0 MR7 Administration Guide

FortiGuard ...................................................................................................... 241

Router Static .................................................................................. 255

Router Dynamic.............................................................................. 267

FortiGate Version 3.0 MR7 Administration Guide

Multicast ......................................................................................................... 283

Router Monitor ............................................................................... 289

Firewall Policy ................................................................................ 293

Firewall Address ............................................................................ 315

Firewall Service.............................................................................. 321

FortiGate Version 3.0 MR7 Administration Guide

Firewall Schedule........................................................................... 329

Firewall Virtual IP ........................................................................... 333

Firewall Protection Profile............................................................. 365

FortiGate Version 3.0 MR7 Administration Guide

Configuring a protection profile................................................................... 367

SIP support..................................................................................... 383

VPN IPSEC...................................................................................... 393

VPN PPTP ....................................................................................... 411

VPN SSL.......................................................................................... 413

FortiGate Version 3.0 MR7 Administration Guide

Configuring SSL VPN .................................................................................... 414

User Authentication ....................................................................... 421

AntiVirus ......................................................................................... 447

FortiGate Version 3.0 MR7 Administration Guide

File Filter......................................................................................................... 450

Intrusion Protection....................................................................... 463

FortiGate Version 3.0 MR7 Administration Guide

Intrusion protection CLI configuration ........................................................ 478

Web Filter........................................................................................ 479

FortiGate Version 3.0 MR7 Administration Guide

Black/White List............................................................................................. 505

IM, P2P & VoIP................................................................................ 515

Log&Report .................................................................................... 525

FortiGate Version 3.0 MR7 Administration Guide

Storing logs.................................................................................................... 528

Managing firmware versions......................................................... 555

FortiGate Version 3.0 MR7 Administration Guide

Reverting to FortiOS 2.80 MR11................................................................... 561

FortiGate Version 3.0 MR7 Administration Guide

What’s new in 3.0 MR7

FortiGate Version 3.0 MR7 Administration Guide

FortiGate Version 3.0 MR7 Administration Guide

3.0 MR7 new features and changes