Fortios - Release Notes
Fortios - Release Notes
Version 6.0.16
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
NSE INSTITUTE
https://training.fortinet.com
FORTIGUARD CENTER
https://www.fortiguard.com
FEEDBACK
Email: [email protected]
Change Log 5
Introduction 6
Supported models 6
Special branch supported models 6
Special Notices 8
WAN optimization and web caching functions 8
FortiGuard Security Rating Service 8
Using FortiManager as a FortiGuard server 9
Built-in certificate 9
FortiGate and FortiWiFi-92D hardware limitation 9
FG-900D and FG-1000D 10
FortiClient (Mac OS X) SSL VPN requirements 10
FortiClient profile changes 10
Use of dedicated management interfaces (mgmt1 and mgmt2) 10
Using FortiAnalyzer units running older versions 10
L2TP over IPsec on certain mobile devices 11
Upgrade Information 12
FortiGuard protocol and port number 12
Fortinet Security Fabric upgrade 12
Minimum version of TLS services automatically changed 13
Downgrading to previous firmware versions 13
Amazon AWS enhanced networking compatibility issue 14
FortiGate VM firmware 14
Firmware image checksums 15
FortiGuard update-server-location setting 15
External IP not allowed to be the same as mapped IP 15
Product Integration and Support 16
Language support 18
SSL VPN support 18
SSL VPN standalone client 18
SSL VPN web mode 19
SSL VPN host compatibility list 19
Resolved Issues 21
SSL VPN 21
Common Vulnerabilities and Exposures 21
Known Issues 22
Antivirus 22
Firewall 22
GUI 22
Log & Report 22
Proxy 23
This document provides release information for FortiOS 6.0.16 build 0505.
For FortiOS documentation, see the Fortinet Document Library.
Supported models
FortiOS Carrier FortiOS Carrier 6.0.16 images are delivered upon request and are not available on the
customer support firmware download page.
The following models are released on a special branch of FortiOS 6.0.16. To confirm that you are running the correct
build, run the CLI command get system status and check that the Branch point field shows 0505.
WAN optimization and web caching functions are removed from 60D and 90D series platforms, starting from 6.0.0 due to
their limited disk size. Platforms affected are:
l FGT-60D
l FGT-60D-POE
l FWF-60D
l FWF-60D-POE
l FGT-90D
l FGT-90D-POE
l FWF-90D
l FWF-90D-POE
l FGT-94D-POE
Upon upgrading from 5.6 patches to 6.0.0, diagnose debug config-error-log read will show command parse
error about wanopt and webcache settings.
Not all FortiGate models can support running the FortiGuard Security Rating Service as a Fabric "root" device. The
following FortiGate platforms can run the FortiGuard Security Rating Service when added to an existing Fortinet Security
Fabric managed by a supported FortiGate model:
If you use FortiManager as a FortiGuard server, and you configure the FortiGate to use a secure connection to
FortiManager, you must use HTTPS with port 8888. HTTPS with port 53 is not supported.
Built-in certificate
FortiGate and FortiWiFi D-series and above have a built in Fortinet_Factory certificate that uses a 2048-bit certificate
with the 14 DH group.
FortiOS 5.4.0 reported an issue with the FG-92D model in the Special Notices > FG-92D High Availability in Interface
Mode section of the release notes. Those issues, which were related to the use of port 1 through 14, include:
l PPPoE failing, HA failing to form.
l IPv6 packets being dropped.
l FortiSwitch devices failing to be discovered.
l Spanning tree loops may result depending on the network topology.
FG-92D and FWF-92D do not support STP. These issues have been improved in FortiOS 5.4.1, but with some side
effects with the introduction of a new command, which is enabled by default:
config global
set hw-switch-ether-filter <enable | disable>
l ARP (0x0806), IPv4 (0x0800), and VLAN (0x8100) packets are allowed.
l BPDUs are dropped and therefore no STP loop results.
l PPPoE packets are dropped.
l IPv6 packets are dropped.
l FortiSwitch devices are not discovered.
l HA may fail to form depending the network topology.
l All packet types are allowed, but depending on the network topology, an STP loop may result.
CAPWAP traffic will not offload if the ingress and egress traffic ports are on different NP6 chips. It will only offload if both
ingress and egress ports belong to the same NP6 chip.
When using SSL VPN on Mac OS X 10.8, you must enable SSLv3 in FortiOS.
With introduction of the Fortinet Security Fabric, FortiClient profiles will be updated on FortiGate. FortiClient profiles and
FortiGate are now primarily used for Endpoint Compliance, and FortiClient Enterprise Management Server (EMS) is now
used for FortiClient deployment and provisioning.
The FortiClient profile on FortiGate is for FortiClient features related to compliance, such as Antivirus, Web Filter,
Vulnerability Scan, and Application Firewall. You may set the Non-Compliance Action setting to Block or Warn.
FortiClient users can change their features locally to meet the FortiGate compliance criteria. You can also use FortiClient
EMS to centrally provision endpoints. The EMS also includes support for additional features, such as VPN tunnels or
other advanced options. For more information, see the FortiOS Handbook – Security Profiles.
For optimum stability, use management ports (mgmt1 and mgmt2) for management traffic only. Do not use management
ports for general user traffic.
When using FortiOS 6.0.16 with FortiAnalyzer units running 5.6.5 or lower, or 6.0.0-6.0.2, FortiAnalyzer might report
increased bandwidth and session counts if there are sessions that last longer than two minutes.
For accurate bandwidth and session counts, upgrade the FortiAnalyzer unit to the latest version.
Bug ID Description
459996 Samsung Galaxy Tab A 8 and Android 9.0 crash after L2TP over IPsec is connected.
Supported upgrade path information is available on the Fortinet Customer Service & Support site.
1. Go to https://support.fortinet.com.
2. From the Download menu, select Firmware Images.
3. Check that Select Product is FortiGate.
4. Click the Upgrade Path tab and select the following:
l Current Product
5. Click Go.
Fortinet has updated the protocol that is used between the FortiGate unit and FortiGuard. Please read the section under
Resolved Issues > Common Vulnerabilities and Exposures. Upon upgrading to a patched version of FortiOS, customers
must manually change the protocol and port used for connecting to FortiGuard.
config system fortiguard
set protocol https
set port 8888
end
Once the FortiGate is upgraded to a patched version, any factory reset will change the default FortiGuard settings to
those above—protocol HTTPS and port 8888.
FortiOS 6.0.16 greatly increases the interoperability between other Fortinet products. This includes:
l FortiAnalyzer 6.0.11 and later
l FortiClient EMS 6.0.8
l FortiClient 6.0.10
l FortiAP 5.4.4 and later
l FortiSwitch 3.6.9 and later
Upgrade the firmware of each product in the correct order. This maintains network connectivity without the need to use
manual steps.
If Security Fabric is enabled, then all FortiGate devices must be upgraded to 6.0.16. When
Security Fabric is enabled, you cannot have some FortiGate devices running 6.0.16 and some
running 5.6.x.
For improved security, FortiOS 6.0.16 uses the ssl-min-proto-version option (under config system global)
to control the minimum SSL protocol version used in communication between FortiGate and third-party SSL and TLS
services.
When you upgrade to FortiOS 6.0.16 and later, the default ssl-min-proto-version option is TLS v1.2. The following
SSL and TLS services inherit global settings to use TLS v1.2 as the default. You can override these settings.
l Email server (config system email-server)
l Certificate (config vpn certificate setting)
l FortiSandbox (config system fortisandbox)
l FortiGuard (config log fortiguard setting)
l FortiAnalyzer (config log fortianalyzer setting)
l LDAP server (config user ldap)
l POP3 server (config user pop3)
Downgrading to previous firmware versions results in configuration loss on all models. Only the following settings are
retained:
l operation mode
l interface IP/management IP
l static route table
l DNS settings
l VDOM parameters/settings
l admin user account
l session helpers
l system access profiles
If you have long VDOM names, you must shorten the long VDOM names (maximum 11 characters) before downgrading:
1. Back up your configuration.
2. In the backup configuration, replace all long VDOM names with its corresponding short VDOM name.
For example, replace edit <long_vdom_name>/<short_name> with edit <short_name>/<short_
name>.
3. Restore the configuration.
4. Perform the downgrade.
With this new enhancement, there is a compatibility issue with older AWS VM versions. After downgrading a 6.0.16
image to an older version, network connectivity is lost. Since AWS does not provide console access, you cannot recover
the downgraded image.
When downgrading from 6.0.16 to older versions, running the enhanced nic driver is not allowed. The following AWS
instances are affected:
l C3
l C4
l R3
l I2
l M4
l D2
FortiGate VM firmware
Fortinet provides FortiGate VM firmware images for the following virtual environments:
l .out: Download the 64-bit firmware image to upgrade your existing FortiGate VM installation.
l .out.OpenXen.zip: Download the 64-bit package for a new FortiGate VM installation. This package contains the
QCOW2 file for Open Source XenServer.
l .out.CitrixXen.zip: Download the 64-bit package for a new FortiGate VM installation. This package contains
the Citrix XenServer Virtual Appliance (XVA), Virtual Hard Disk (VHD), and OVF files.
Linux KVM
l .out: Download the 64-bit firmware image to upgrade your existing FortiGate VM installation.
l .out.kvm.zip: Download the 64-bit package for a new FortiGate VM installation. This package contains QCOW2
that can be used by qemu.
Microsoft Hyper-V
l .out: Download the 64-bit firmware image to upgrade your existing FortiGate VM installation.
l .out.hyperv.zip: Download the 64-bit package for a new FortiGate VM installation. This package contains
three folders that can be imported by Hyper-V Manager on Hyper-V 2012. It also contains the file fortios.vhd in
the Virtual Hard Disks folder that can be manually added to the Hyper-V Manager.
l .out: Download either the 64-bit firmware image to upgrade your existing FortiGate VM installation.
l .ovf.zip: Download either the 64-bit package for a new FortiGate VM installation. This package contains Open
Virtualization Format (OVF) files for VMware and two Virtual Machine Disk Format (VMDK) files used by the OVF
file during deployment.
The MD5 checksums for all Fortinet software and firmware releases are available at the Customer Service & Support
portal, https://support.fortinet.com. After logging in select Download > Firmware Image Checksums, enter the image file
name including the extension, and select Get Checksum Code.
The FortiGuard update-server-location default setting is different between hardware platforms and VMs. On
hardware platforms, the default is any. On VMs, the default is usa.
On VMs, after upgrading from 5.6.3 or earlier to 5.6.4 or later (including 6.0.0 or later), update-server-location is
set to usa.
If necessary, set update-server-location to use the nearest or low-latency FDS servers.
Traffic will be dropped when the IPS is enabled in a policy with a VIP that has the same external and mapped IP.
To avoid this, the kernel will disallow the configuration of the same extip and mappedip for VIPs in the CLI starting
from FortiOS 6.0.0.
The following table lists FortiOS 6.0.16 product integration and support information:
Other web browsers may function correctly, but are not supported by Fortinet.
Other web browsers may function correctly, but are not supported by Fortinet.
FortiClient: l 6.0.0
l Microsoft Windows See important compatibility information in Fortinet Security Fabric upgrade on
l Mac OS X page 12.
l Linux
If you're upgrading both FortiOS and FortiClient from 5.6 to 6.0, upgrade
FortiClient first to avoid compatibility issues.
FortiClient for Linux is supported on Ubuntu 16.04 and later, Red Hat 7.4 and
later, and CentOS 7.4 and later.
If you are using FortiClient only for IPsec VPN or SSL VPN, FortiClient version
5.6.0 and later are supported.
Fortinet Single Sign-On l 5.0 build 0308 and later (needed for FSSO agent support OU in group filters)
(FSSO) l Windows Server 2019 Datacenter
l Windows Server 2019 Standard
l Windows Server 2019 Core
l Windows Server 2016 Datacenter
l Windows Server 2016 Standard
l Windows Server 2016 Core
l Windows Server 2012 Standard
l Windows Server 2012 R2 Standard
l Windows Server 2012 Core
l Windows Server 2008 (32-bit and 64-bit)
l Windows Server 2008 R2 64-bit
l Windows Server 2008 Core
l Novell eDirectory 8.8
AV Engine l 6.00033
Virtualization Environments
Microsoft l Hyper-V Server 2008 R2, 2012, 2012 R2, and 2016
Language support
Language support
Language GUI
English ✔
Chinese (Simplified) ✔
Chinese (Traditional) ✔
French ✔
Japanese ✔
Korean ✔
Portuguese (Brazil) ✔
Spanish ✔
The following table lists SSL VPN tunnel client standalone installer for the following operating systems.
Linux CentOS 6.5 / 7 (32-bit & 64-bit) 2336. Download from the Fortinet Developer Network:
Linux Ubuntu 16.04 (32-bit & 64-bit) https://fndn.fortinet.net.
Other operating systems may function correctly, but are not supported by Fortinet.
SSL VPN standalone client no longer supports the following operating systems:
l Microsoft Windows 7 (32-bit & 64-bit)
The following table lists the operating systems and web browsers supported by SSL VPN web mode.
Microsoft Windows 7 SP1 (32-bit & 64-bit) Mozilla Firefox version 104
Google Chrome version 105
Other operating systems and web browsers may function correctly, but are not supported by Fortinet.
The following table lists the antivirus and firewall client software packages that are supported.
The following issues have been fixed in version 6.0.16. To inquire about a particular bug, please contact Customer
Service & Support.
SSL VPN
Bug ID Description
848437 The sslvpn process crashes if a POST request with a body greater than 2 GB is received.
The following issues have been identified in version 6.0.16. To inquire about a particular bug or report a bug, please
contact Customer Service & Support.
Antivirus
Bug ID Description
590092 Cannot clear scanunit vdom-stats to reset the statistics on ATP widget.
Firewall
Bug ID Description
508015 Editing a policy in the GUI changes the FSSO setting to disable.
GUI
Bug ID Description
682440 On Firewall Policy list, the tooltip for IP Pool shows Port Block Allocation as being exhausted if there
are expiring PBAs available to be reallocated.
697290 In Firefox, the GUI cannot load the IPS signature list page if the user clicks View IPS Signatures
before the IPS profile page finishes loading. Other browsers do not have this issue.
Log & Report
Bug ID Description
592766 Log device defaults to empty and cannot be switched on in the GUI after enabling FortiAnalyzer
Cloud.
Proxy
Bug ID Description
System
Bug ID Description
657629 ARM-based platforms do not have sensor readings included in SNMP MIBs.
735306 Enabling ssl-mirror-intf on a management port in a firewall policy with flow mode IPS or
application control profiles will cause all traffic to be blocked and the FortiGate to go into kernel
panic and automatically reboot.
Workaround: do not use a management port as an SSL mirror interface.
User & Device
Bug ID Description
701356 When a GUI administrator certificate, admin-server-cert, is provisioned via SCEP, the
FortiGate does not automatically offer the newly updated certificate to HTTPS clients. FortiOS 7.0.0
and later does not have this issue.
Workaround: manually unset admin-server-cert and set it back to the same certificate.
config system global
unset admin-server-cert
end
l VHD
l OVF
l The XVA format comes pre-configured with default configurations for VM name, virtual CPU, memory, and virtual
NIC. Other formats will require manual configuration before the first power on process.
When using Linux Ubuntu version 11.10, XenServer version 4.1.0, and libvir version 0.9.2, importing issues may arise
when using the QCOW2 format and existing HDA issues.