Fortios v6.4.12 Release Notes
Fortios v6.4.12 Release Notes
Version 6.4.12
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
FORTIGUARD CENTER
https://www.fortiguard.com
FEEDBACK
Email: techdoc@fortinet.com
Change Log 6
Introduction and supported models 7
Supported models 7
Special branch supported models 7
Special notices 9
CAPWAP traffic offloading 9
FortiClient (Mac OS X) SSL VPN requirements 9
Use of dedicated management interfaces (mgmt1 and mgmt2) 9
Tags option removed from GUI 10
System Advanced menu removal (combined with System Settings) 10
PCI passthrough ports 10
FG-80E-POE and FG-81E-POE PoE controller firmware update 10
AWS-On-Demand image 10
Azure-On-Demand image 11
FortiClient EMS Cloud registration 11
SSL traffic over TLS 1.0 will not be checked and will be bypassed by default 11
RDP and VNC clipboard toolbox in SSL VPN web mode 12
Hyperscale firewall support 12
CAPWAP offloading compatibility of FortiGate NP7 platforms 12
IP pools and blackhole route configuration 12
New features or enhancements 13
Upgrade information 14
Device detection changes 14
FortiClient Endpoint Telemetry license 15
Fortinet Security Fabric upgrade 15
Minimum version of TLS services automatically changed 16
Downgrading to previous firmware versions 16
Amazon AWS enhanced networking compatibility issue 17
FortiLink access-profile setting 17
FortiGate VM with V-license 18
FortiGate VM firmware 18
Firmware image checksums 19
FortiGuard update-server-location setting 19
FortiView widgets 19
WanOpt configuration changes in 6.4.0 19
WanOpt and web cache statistics 20
IPsec interface MTU value 20
HA role wording changes 20
Virtual WAN link member lost 20
Enabling match-vip in firewall policies 21
Hardware switch members configurable under system interface list 21
2023-03-06 Updated Introduction and supported models on page 7 and Fortinet Security Fabric upgrade on
page 15.
2023-03-21 Updated Known issues on page 32 and Built-in IPS engine on page 39.
2023-03-24 Updated VDOM link and policy configuration is lost after upgrading if VDOM and VDOM link
have the same name on page 21 and Product integration and support on page 22.
2023-05-30 Updated SSL traffic over TLS 1.0 will not be checked and will be bypassed by default on page 11
and Known issues on page 32.
This guide provides release information for FortiOS 6.4.12 build 2060.
For FortiOS documentation, see the Fortinet Document Library.
Supported models
The following models are released on a special branch of FortiOS 6.4.12. To confirm that you are running the correct
build, run the CLI command get system status and check that the Branch point field shows 2060.
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. The following models are affected:
l FG-900D
l FG-1000D
l FG-2000E
l FG-2500E
When using SSL VPN on Mac OS X 10.8, you must enable SSLv3 in FortiOS.
For optimum stability, use management ports (mgmt1 and mgmt2) for management traffic only. Do not use management
ports for general user traffic.
The Tags option is removed from the GUI. This includes the following:
l The System > Tags page is removed.
l The Tags section is removed from all pages that had a Tags section.
l The Tags column is removed from all column selections.
Bug ID Description
584254 l Removed System > Advanced menu (moved most features to System > Settings page).
l Moved configuration script upload feature to top menu > Configuration > Scripts page.
l Removed GUI support for auto-script configuration (the feature is still supported in the CLI).
l Converted all compliance tests to security rating tests.
Bug ID Description
605103 PCI passthrough ports order might be changed after upgrading. This does not affect VMXNET3 and
SR-IOV ports because SR-IOV ports are in MAC order by default.
FortiOS 6.4.0 has resolved bug 570575 to fix a FortiGate failing to provide power to ports. The PoE hardware controller,
however, may require an update that must be performed using the CLI. Upon successful execution of this command, the
PoE hardware controller firmware is updated to the latest version 2.18:
diagnose poe upgrade-firmware
AWS-On-Demand image
Bug ID Description
589605 Starting from FortiOS 6.4.0, the FG-VM64-AWSONDEMAND image is no longer provided. Both
AWS PAYG and AWS BYOL models will share the same FG-VM64-AWS image for upgrading and
new deployments. Remember to back up your configuration before upgrading.
Azure-On-Demand image
Bug ID Description
657690 Starting from FortiOS 6.4.3, the FG-VM64-AZUREONDEMAND image is no longer provided. Both
Azure PAYG and Azure BYOL models will share the same FG-VM64-AZURE image for upgrading
and new deployments. Remember to back up your configuration before upgrading.
FortiOS 6.4.3 and later adds full support for FortiClient EMS Cloud service.
SSL traffic over TLS 1.0 will not be checked and will be bypassed by
default
FortiOS 6.2.6 and 6.4.3 ended support for TLS 1.0 when strong-crypto is enabled under system global. With this
change, SSL traffic over TLS 1.0 will not be checked so it will be bypassed by default.
To examine and/or block TLS 1.0 traffic, an administrator can either:
l Disable strong-crypto under config system global. This applies to FortiOS 6.2.6 and 6.4.3, or later
versions.
l Under config firewall ssl-ssh-profile, set the following to block in the SSL protocol settings:
l in FortiOS 6.2.6 and later:
config firewall ssl-ssh-profile
edit <name>
config ssl
set unsupported-ssl block
end
next
end
Press F8 to access the RDP/VNC clipboard toolbox. The functionality in previous versions with the clipboard toolbox in
the right-hand side of the RDP/VNC page has been removed in FortiOS 6.4.7 and later.
FortiOS 6.4.12 supports hyperscale firewall features for FortiGates with NP7 processors (FG-1800F, FG-1801F, FG-
2600F, FG-2601F, FG-4200F, FG-4201F, FG-4400F, and FG-4401F). For more information, refer to the Hyperscale
Firewall Release Notes.
To work with FortiGate NP7 platforms, current FortiAP models whose names end with letter E or F should be upgraded
to the following firmware versions:
l FortiAP (F models): version 6.4.7, 7.0.1, and later
l FortiAP-S and FortiAP-W2 (E models): version 6.4.7, 7.0.1, and later
l FortiAP-U (EV and F models): version 6.2.2 and later
l FortiAP-C (FAP-C24JE): version 5.4.3 and later
The CAPWAP offloading feature of FortiGate NP7 platforms is not fully compatible with FortiAP models that cannot be
upgraded (as mentioned above) or legacy FortiAP models whose names end with the letters B, C, CR, or D. To work
around this issue for these FortiAP models, administrators need to disable capwap-offload under config system
npu and then reboot the FortiGate.
Starting in FortiOS 6.4.9, 7.0.1, 7.2.0, and 7.4.0, all IP addresses used as IP pools and VIPs are no longer considered
local IP addresses if responding to ARP requests on these external IP addresses is enabled (set arp-reply enable
by default). In this case, the FortiGate is not considered a destination for those IP addresses and cannot receive reply
traffic at the application layer without special handling.
l This behavior affects FortiOS features in the application layer that use an IP pool as its source IP pool, including
SSL VPN web mode and explicit web proxy.
l When a blackhole route is configured in the routing table and matches the IP pool reply traffic, the FortiGate will not
receive reply traffic at the application layer and the corresponding the FortiOS feature will not work as desired.
l Configuring an IP pool as the source NAT IP address in a regular firewall policy works as before.
See IP pools and blackhole route configuration in the FortiOS Administration Guide for more information.
Bug ID Description
776052 Add four SNMP OIDs for polling critical port block allocations (PBAs) IP pool statistics including:
l Total PBAs: fgFwIppStatsTotalPBAs (1.3.6.1.4.1.12356.101.5.3.2.1.1.9)
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.
In FortiOS 6.0.x, the device detection feature contains multiple sub-components, which are independent:
l Visibility – Detected information is available for topology visibility and logging.
l FortiClient endpoint compliance – Information learned from FortiClient can be used to enforce compliance of those
endpoints.
l Mac-address-based device policies – Detected devices can be defined as custom devices, and then used in device-
based policies.
In 6.2, these functionalities have changed:
l Visibility – Configuration of the feature remains the same as FortiOS 6.0, including FortiClient information.
l FortiClient endpoint compliance – A new fabric connector replaces this, and aligns it with all other endpoint
connectors for dynamic policies. For more information, see Dynamic Policy - FortiClient EMS (Connector) in the
FortiOS 6.2.0 New Features Guide.
l MAC-address-based policies – A new address type is introduced (MAC address range), which can be used in
regular policies. The previous device policy feature can be achieved by manually defining MAC addresses, and then
adding them to regular policy table in 6.2. For more information, see MAC Addressed-Based Policies in the FortiOS
6.2.0 New Features Guide.
If you were using device policies in 6.0.x, you will need to migrate these policies to the regular policy table manually after
upgrade. After upgrading to 6.2.0:
1. Create MAC-based firewall addresses for each device.
2. Apply the addresses to regular IPv4 policy table.
In 6.4.0, device detection related GUI functionality has been relocated:
1. The device section has moved from User & Authentication (formerly User & Device) to a widget in Dashboard.
2. The email collection monitor page has moved from Monitor to a widget in Dashboard.
In 6.4.4, a new sub-option, Delete, was added when right-clicking on the device. This option is not available when the
device is online, or the device is retrieved from FortiClient.
Starting with FortiOS 6.2.0, the FortiClient Endpoint Telemetry license is deprecated. The FortiClient Compliance profile
under the Security Profiles menu has been removed as has the Enforce FortiClient Compliance Check option under
each interface configuration page. Endpoints running FortiClient 6.2.0 now register only with FortiClient EMS 6.2.0 and
compliance is accomplished through the use of Compliance Verification Rules configured on FortiClient EMS 6.2.0 and
enforced through the use of firewall policies. As a result, there are two upgrade scenarios:
l Customers using only a FortiGate device in FortiOS 6.0 to enforce compliance must install FortiClient EMS 6.2.0
and purchase a FortiClient Security Fabric Agent License for their FortiClient EMS installation.
l Customers using both a FortiGate device in FortiOS 6.0 and FortiClient EMS running 6.0 for compliance
enforcement, must upgrade the FortiGate device to FortiOS 6.2.0, FortiClient to 6.2.0, and FortiClient EMS to 6.2.0.
The FortiClient 6.2.0 for MS Windows standard installer and zip package containing FortiClient.msi and language
transforms and the FortiClient 6.2.0 for macOS standard installer are included with FortiClient EMS 6.2.0.
FortiOS 6.4.12 greatly increases the interoperability between other Fortinet products. This includes:
l FortiAnalyzer 6.4.11
l FortiManager 6.4.11
l FortiClient EMS 6.4.3 build 1600 or later
l FortiClient 6.4.3 build 1608 or later
l FortiAP 6.4.4 build 0456 or later
l FortiSwitch 6.4.5 build 0461 or later
When upgrading your Security Fabric, devices that manage other devices should be upgraded first. Upgrade the
firmware of each device in the following order. This maintains network connectivity without the need to use manual
steps.
1. FortiAnalyzer
2. FortiManager
3. Managed FortiExtender devices
4. FortiGate devices
5. Managed FortiSwitch devices
6. Managed FortiAP devices
7. FortiClient EMS
8. FortiClient
9. FortiSandbox
10. FortiMail
11. FortiWeb
12. FortiADC
13. FortiDDOS
14. FortiWLC
15. FortiNAC
16. FortiVoice
If Security Fabric is enabled, then all FortiGate devices must be upgraded to 6.4.12. When
Security Fabric is enabled in FortiOS 6.4.12, all FortiGate devices must be running FortiOS
6.4.12.
For improved security, FortiOS 6.4.12 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.4.12 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 admin user account
l session helpers
l system access profiles
With this enhancement, there is a compatibility issue with 5.6.2 and older AWS VM versions. After downgrading a 6.4.12
image to a 5.6.2 or older version, network connectivity is lost. Since AWS does not provide console access, you cannot
recover the downgraded image.
When downgrading from 6.4.12 to 5.6.2 or older versions, running the enhanced NIC driver is not allowed. The following
AWS instances are affected:
C5 Inf1 P3 T3a
C5d m4.16xlarge R4 u-6tb1.metal
C5n M5 R5 u-9tb1.metal
F1 M5a R5a u-12tb1.metal
G3 M5ad R5ad u-18tb1.metal
G4 M5d R5d u-24tb1.metal
H1 M5dn R5dn X1
I3 M5n R5n X1e
I3en P2 T3 z1d
A workaround is to stop the instance, change the type to a non-ENA driver NIC type, and continue with downgrading.
The new FortiLink local-access profile controls access to the physical interface of a FortiSwitch that is managed by
FortiGate.
After upgrading FortiGate to 6.4.12, the interface allowaccess configuration on all managed FortiSwitches are
overwritten by the default FortiGate local-access profile. You must manually add your protocols to the local-
access profile after upgrading to 6.4.12.
To enable split-vdom:
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 Server 2019 and Windows Server 2012R2 with Hyper-V role
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. 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, go to Support > Firmware Image Checksums (in the Downloads
section), enter the image file name including the extension, and click 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.
FortiView widgets
Port configuration is now done in the profile protocol options. HTTPS configurations need to have certificate inspection
configured in the firewall policy.
In FortiOS 6.4.0, set ssl-ssh-profile certificate-inspection must be added in the firewall policy:
config firewall policy
edit 1
select srcintf FGT_A:NET_CLIENT
select dstintf FGT_A:WAN
select srcaddr all
select dstaddr all
The statistics for WanOpt and web cache have moved from Monitor to a widget in Dashboard.
IPsec interfaces may calculate a different MTU value after upgrading from 6.2.
This change might cause an OSPF neighbor to not be established after upgrading. The workaround is to set mtu-
ignore to enable on the OSPF interface's configuration:
config router ospf
config ospf-interface
edit "ipsce-vpnx"
set mtu-ignore enable
next
end
end
The term master has changed to primary, and slave has changed to secondary. This change applies to all HA-related
CLI commands and output. The one exception is any output related to VRRP, which remains unchanged.
The member of virtual-wan-link is lost after upgrade if the mgmt interface is set to dedicated-to management
and part of an SD-WAN configuration before upgrade.
As of FortiOS 6.4.3, match-vip is not allowed in firewall policies when the action is set to accept.
Starting in FortiOS 6.4.7, hardware switch members are also shown under config system interface with limited
configuration options available.
Affected versions:
l FortiOS 6.4.9 and later
l FortiOS 7.0.6 and later
l FortiOS 7.2.0 and later
When upgrading to one of the affected versions, there is a check within the set vdom-links function that rejects vdom-
links that have the same name as a VDOM. Without the check, the FortiGate will have a kernel panic upon bootup
during the upgrade step.
A workaround is to rename the vdom-links prior to upgrading, so that they are different from the VDOMs.
The following table lists FortiOS 6.4.12 product integration and support information:
Other browser versions have not been tested, but may fully function.
Other web browsers may function correctly, but are not supported by Fortinet.
Other browser versions have not been tested, but may fully function.
Other web browsers may function correctly, but are not supported by Fortinet.
FortiClient: l 6.4.0
l Microsoft Windows See important compatibility information in FortiClient Endpoint Telemetry license
l Mac OS X on page 15 and Fortinet Security Fabric upgrade on page 15.
l Linux 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 6.0
and later are supported.
Fortinet Single Sign-On l 5.0 build 0309 and later (needed for FSSO agent support OU in group filters)
(FSSO) l Windows Server 2022 Standard
l Windows Server 2022 Datacenter
l Windows Server 2019 Standard
l Windows Server 2019 Datacenter
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 64-bit (requires Microsoft SHA2 support
package)
l Windows Server 2008 R2 64-bit (requires Microsoft SHA2 support
package)
l Windows Server 2008 Core (requires Microsoft SHA2 support package)
l Novell eDirectory 8.8
FortiExtender l 4.0.0 and later. For compatibility with latest features, use latest 4.2 version.
AV Engine l 6.00172
Virtualization Environments
Linux KVM l Ubuntu 18.0.4 LTS, 4.15.0-72-generic, QEMU emulator version 2.11.1
(Debian 1:2.11+dfsg-1ubuntu7.21)
Language support
Language support
Language GUI
English ✔
Chinese (Simplified) ✔
Chinese (Traditional) ✔
French ✔
Japanese ✔
Korean ✔
Portuguese (Brazil) ✔
Spanish ✔
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 103
Google Chrome version 104
Mozilla Firefox
Google Chrome
Other operating systems and web browsers may function correctly, but are not supported by Fortinet.
The following issues have been fixed in version 6.4.12. To inquire about a particular bug, please contact Customer
Service & Support.
Explicit Proxy
Bug ID Description
774442 WAD is NATting to the wrong IP pool address for the interface.
GUI
Bug ID Description
794757 Inbound traffic on the interface bandwidth widget shows 0 bps on the VLAN interface.
HA
Bug ID Description
662978 Long lasting sessions are expired on HA secondary device with a 10G interface.
750978 Interface link status of HA members go down when cfg-revert tries to reboot post cfg-
revert-timeout.
785514 In some cases, the fgfmd daemon is blocked by a query to the HA secondary checksum, and it will
cause the tunnel between FortiManager and the FortiGate to go down.
Hyperscale
Bug ID Description
805846 In the FortiOS MIB files, the trap fields fgFwIppStatsGroupName and
fgFwIppStatsInusePBAs have the same OID. As a result, the fgFwIppStatsInusePBAs field
always returns a value of 0.
IPsec VPN
Bug ID Description
675838 iked ignores phase 1 configuration changes due to frequent FortiExtender CMDB changes.
855772 FortiGate IPsec tunnel role could be incorrect after rebooting or upgrading, and causes negotiation
to be stuck when it comes up.
858715 IPsec phase 2 fails when both HA cluster members reboot at the same time.
Bug ID Description
Proxy
Bug ID Description
650348 FortiGate refuses incoming TCP connection to FTP proxy port after explicit proxy related
configurations are changed.
799381 WAD crash occurs when TLS 1.2 receives the client certificate and that server-facing SSL port has
been closed due to the SSL bypass.
Routing
Bug ID Description
Security Fabric
Bug ID Description
837347 Upgrading from 6.4.8 to 7.0.5 causes SDN firewall address configurations to be lost.
843043 Only the first ACI SDN connector can be kept after upgrading from 6.4.8 if multiple ACI SDN
connectors are configured.
857441 Azure Fabric connector process (azd) has high memory consumption during updates, which leads
to low-end FortiGate models entering conserve mode.
SSL VPN
Bug ID Description
705880 Updated empty group with SAML user does not trigger an SSL VPN firewall policy refresh, which
causes the SAML user detection to not be successful in later usage.
746230 SSL VPN web mode cannot display certain websites that are internal bookmarks.
748085 Authentication request of SSL VPN realm can now only be sent to user group, local user, and
remote group that is mapped to that realm in the SSL VPN settings. The authentication request will
not be applied to the user group and remote group of non-realm or other realms.
784522 When trying to create a support ticket in Jira with SSL VPN proxy web mode, the dropdown field
does not contain any values.
822432 SSL VPN crashes after copying a string to the remote server using the clipboard in RDP web mode
when using RDP security.
834713 Getting re-authentication pop-up window for VNC quick connection over SSL VPN web proxy.
848067 RDP over VPN SSL web mode stops work after upgrading to 6.4.10.
852566 User peer feature for one group to match to multiple user peers in the authentication rules is broken.
854143 Unable to access Synology NAS server through SSL VPN web mode.
Bug ID Description
856316 Browser displays an Error, Feature is not available message if a file larger than 1 MB is uploaded
from FTP or SMB using a web bookmark, even though the file is uploaded successfully. There are
no issues with downloading files.
Switch Controller
Bug ID Description
845667 Enabling allowed-vlans-all on FortiSwitch ports will push VLANs from both owner and tenant
VDOMs.
System
Bug ID Description
713951 Not all ports are coming up after an LAG bounce on 8 × 10 GB LAG with ASR9K. Affected platforms:
FG-3960E and FG-3980E.
724085 Traffic passing through an EMAC VLAN interface when the parent interface is in another VDOM is
blocked if NP7 offloading is enabled. If auto-asic-offload is disabled in the firewall policy, then
the traffic flows as expected.
733096 FG-100F HA secondary's unused ports flaps from down to up, then to down.
784169 When a virtual switch member port is set to be an alternate by STP, it should not reply with ARP;
otherwise, the connected device will learn the MAC address from the alternate port and send
subsequent packets to the alternate port.
787929 Deleting a VDOM that contains EMAC interfaces might affect the interface bandwidth widget of the
parent VLAN.
810466 EHP and HRX drop on NP6 FortiGate, causing low throughput.
811367 Ports 33-35 constantly show suspect messaging in the transceiver output. Affected platforms: FG-
2600F and FG-2601F.
Bug ID Description
815692 Slow upload speeds when connected to FIOS connection. Affected platforms: NP6Lite and
NP6xLite.
821000 QSFP and QSFP+ Fortinet transceivers are not operational on FG-3401E.
824543 The reply-to option in the email server settings is no longer visible in a default server
configuration.
827240 FortiGate in HA may freeze and reboot. Before the reboot, softIRQ may be seen as high. This leads
to a kernel panic.
827736 As the size of the internet service database expands, ffdb_err_msg_print: ret=-4,
Error: kernel error is observed frequently on 32-bit CPU platforms, such as the FG-100E.
834850 GUI CLI console displays a Connection lost message when logging in as an API administrator.
847077 Can't find xitem. Drop the response. error appears for DHCPOFFER packets in the
DHCP relay debug.
850774 Session synchronization packets may be dropped when using HA1/HA2. Affected platforms: FGT-
420xF and FGT-440xF.
Upgrade
Bug ID Description
848926 After upgrading, the AV filter feature set is changed from proxy mode to flow mode.
Bug ID Description
751763 When MAC-based authentication is enabled, multiple RADIUS authentication requests may be sent
at the same time. This results in duplicate sessions for the same device.
824999 Subject Alternative Name (SAN) is missing from the certificate upon automatic certificate renewal
made by the FortiGate.
845198 Local-in policies for authentication disappear and the authentication page returns a ERR_
CONNECTION_TIMED_OUT error. The authentication page is not displayed because it is not
rebuilt when firewall local-in-policy is added, edited, or deleted.
853793 FG-81F 802.1X MAC authentication bypass (MAB) failed to authenticate Cisco AP.
WiFi Controller
Bug ID Description
761836 FWF-8xF platforms should allow the DHCP server configuration of an aggregate interface (aplink)
to be edited in the GUI.
807713 FortiGate is not sending RADIUS accounting message consistently to RADIUS server for wireless
SSO.
The following issues have been identified in version 6.4.12. To inquire about a particular bug or report a bug, please
contact Customer Service & Support.
Firewall
Bug ID Description
719311 On the Policy & Objects > Firewall Policy page in 6.4.0 onwards, the IPv4 and IPv6 policy tables are
combined but the custom section name (global label) is not automatically checked for duplicates. If
there is a duplicate custom section name, the policy list may show empty for that section. This is a
display issue only and does not impact policy traffic.
Workaround: rename the custom section to unique name between IPv4 and IPv6 policies.
770541 Within the Policy & Objects menu, the firewall, DoS, and traffic shaping policy pages take around
five seconds to load when the FortiGate cannot reach the FortiGuard DNS servers.
Workaround: set the DNS server to the FortiGuard DNS server.
808264 Stress test shows packet loss when testing with flow inspection mode and application control.
843554 If the first firewall service object in the service list (based on the order in the command line table) has
a protocol type of IP, the GUI may incorrectly modify its protocol number whenever a new firewall
service of the same protocol type IP is created in the GUI.
This silent misconfiguration can result in unexpected behavior of firewall policies that use the
impacted service. For example, some 6K and 7K platforms have firewall service ALL (protocol type
IP) as the first service, and this can cause the ALL service to be modified unexpectedly.
Workaround: create a new service in the CLI, or move a non-IP type services to the top of the
firewall service list. For example, if ALL is the first firewall service in the list:
config firewall service custom
edit "unused"
set tcp-portrange 1
next
move "unused" before "ALL"
end
FortiView
Bug ID Description
683654 FortiView pages with FortiAnalyzer source incorrectly display a Failed to retrieve data error on all
VDOM views when there is a newly created VDOM that is not yet registered to FortiAnalyzer. The
error should only show on the new VDOM view.
GUI
Bug ID Description
440197 On the System > FortiGuard page, the override FortiGuard server for AntiVirus & IPS Updates
shows an Unknown status, even if the server is working correctly. This is a display issue only; the
override feature is working properly.
602397 Managed FortiSwitch and FortiSwitch Ports pages are slow to load when there are many managed
FortiSwitches.
653952 The web page cannot be found is displayed when a dashboard ID no longer exists.
Workaround: load another page in the navigation pane. Once loaded, load the original dashboard
page (that displayed the error) again.
688016 GUI interface bandwidth widget does not show correct data for tunnel interface when ASIC offload
is enabled on the firewall policy.
695163 When there are a lot of historical logs from FortiAnalyzer, the FortiGate GUI Forward Traffic log
page can take time to load if there is no specific filter for the time range.
Workaround: provide a specific time range filter, or use the FortiAnalyzer GUI to view the logs.
743477 On the Log & Report > Forward Traffic page, filtering by the Source or Destination column with
negation on the IP range does not work.
HA
Bug ID Description
771999 Sessions not synchronized to HA secondary on an FGSP and FGCP combined setup.
Hyperscale
Bug ID Description
734305 In the GUI, an FQDN or ISDB can be selected for a DoS policy, which is not supported (an error
message appears). The CLI shows the correct options.
760560 The timestamp on the hyperscale SPU of a deny policy (policy id 0) is incorrect.
796368 Traffic shaping profile does not seem to have an effect on TCP/UDP traffic in hyperscale.
802369 Large client IP range makes fixed allocation usage relatively limited.
Intrusion Prevention
Bug ID Description
763736 IPS custom signature logging shows (even after being disabled) after upgrading to FortiOS 6.4.7.
IPsec VPN
Bug ID Description
877161 IPsec traffic failing from FortiGate with Failed to find IPsec Common error when dialup
IPsec VPN tunnel has remote IP configured on the IPsec VPN interface.
892699 In an HA cluster, static routes via the IPsec tunnel interface are not inactive in the routing table when
the tunnel is down.
Workaround: in an SD-WAN scenario, a health check for the IPsec tunnel (SD-WAN member) with
update-static-route enable is required.
config system sdwan
config health-check
edit <name>
set server <string>
next
end
end
Bug ID Description
next
end
Bug ID Description
860822 When viewing logs on the Log & Report > System Events page, filtering by domain\username does
not display matching entries.
Workaround: use a double backslash (domain\\username) while filtering or searching by username
only without the domain.
Proxy
Bug ID Description
604681 WAD process with SoC SSL acceleration enabled consumes more memory usage over time, which
may lead to conserve mode.
Workaround: disable SoC SSL acceleration under the firewall SSL settings.
REST API
Bug ID Description
759675 Connection failed error occurs on FortiGate when an interface is created and updated using
the API in quick succession.
Routing
Bug ID Description
769100 Policy routes order is changed after updating the source/destination of SD-WAN rules.
846107 IPv6 VRRP backup is sending RA, which causes routing issues.
Security Fabric
Bug ID Description
614691 Slow GUI performance in large Fabric topology with over 50 downstream devices.
SSL VPN
Bug ID Description
730416 Forward traffic log does not generate logs for HTTP and HTTPS services with SSL VPN web mode.
System
Bug ID Description
555616 When NTurbo is enabled, it is unexpectedly provided with the wrong traffic direction information
(from server or from client) to decide the destination for the data. This causes the traffic to be sent
back to the port where it came from.
648085 Link status on peer device is not down when the admin port is down on the FortiGate.
664856 A VWP named .. can be created in the GUI, but it cannot be edited or deleted.
666664 Interface belonging to other VDOMs should be removed from interface list when configuring a
GENEVE interface.
685674 FortiGate did not restart after restoring the backup configuration via FortiManager after the following
process: disable NPU offloading, change NGFW mode from profile-based to policy-based, retrieve
configuration from FortiGate via FortiManager, and install the policy package via FortiManager.
751715 Random LTE modem disconnections due to certain carriers getting unstable due to WWAN modem
USB speed under super-speed.
766834 forticron allocates over 700 MB of memory, causes the FortiGate to go into conserve mode, and
causes kernel panic due to 100 MB of configured CRL.
850430 DHCP relay does not work properly with two DHCP relay servers configured.
Bug ID Description
850683 Console keeps displaying bcm_nl.nr_request_drop ... after the FortiGate reboots because
of the cfg-save revert setting under config system global. Affected platforms: FG-10xF
and FG-20xF.
850688 FG-20xF system halts if setting cfg-save to revert under config system global and after
the cfg-revert-timeout occurs.
855151 There may be a race condition between the CMDB initializing and the customer language file
loading, which causes the customer language file to be removed after upgrading.
Workaround: re-upload the customer language file after the FortiGate boots up.
859795 High CPU utilization occurs when relay is enabled on VLAN, and this prevents users from getting an
IP from DHCP.
Upgrade
Bug ID Description
767808 The asicdos option for enabling/disabling NP6XLite DoS offloading is missing after upgrading to
6.4.9. Affected platforms: NP6XLite.
840921 When upgrading from 6.0.15 to 6.4.11, an existing explicit flow-based web filter profile changes to
proxy-based.
Bug ID Description
778521 SCEP fails to renew if the local certificate name length is between 31 and 35 characters.
VM
Bug ID Description
596742 Azure SDN connector replicates configuration from primary device to secondary device during
configuration restore.
639258 Autoscale GCP health check is not successful (port 8443 HTTPS).
Bug ID Description
668625 During every FortiGuard UTM update, there is high CPU usage because only one vCPU is
available.
764392 Incorrect VMDK file size in the OVF file for hw13 and hw15.
Workaround: manually correct the hw13 and hw15 OVF file's ovf:size value.
WiFi Controller
Bug ID Description
Bug ID Description
773711 HTTPS sessions to some internal destinations are randomly dropped for users from the same group
set.
822551 EICAR virus test file HTTPS traffic cannot be blocked, even when there is a block IPS log.
836955 Primary and secondary units of HA cluster are not accessible and drop traffic.
838875 Application control filename field has unexpected character and breaks the syslog format.
847129 IPS engine crashes and FortiGate enters conserve mode. IPS engine stalled and IPS fail-open is
triggered.
856793 In flow mode, URL filter configuration changes cause a spike in CPU usage of the IPS engine
process.
863074 Both block and passthrough logs are sent out by the web filter override function.
870243 ZIP file block does not work as expected with flow-mode DLP.
873153 URLs longer than 8000 characters are unable to get a FortiGuard rating with flow-based URL filter.
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.