Fortios v7.0.9 Release Notes
Fortios v7.0.9 Release Notes
Fortios v7.0.9 Release Notes
FortiOS 7.0.9
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]
March 8, 2023
FortiOS 7.0.9 Release Notes
01-709-855155-20230308
TABLE OF CONTENTS
Change Log 5
Introduction and supported models 6
Supported models 6
Special branch supported models 6
Special notices 8
Azure-On-Demand image 8
GCP-On-Demand image 8
ALI-On-Demand image 8
Unsupported websites in SSL VPN web mode 9
RDP and VNC clipboard toolbox in SSL VPN web mode 9
CAPWAP offloading compatibility of FortiGate NP7 platforms 9
FEC feature design change 9
Support for FortiGates with NP7 processors and hyperscale firewall features 10
Upgrade information 11
Fortinet Security Fabric upgrade 11
Downgrading to previous firmware versions 12
Firmware image checksums 13
IPsec interface MTU value 13
HA role wording changes 13
Strong cryptographic cipher requirements for FortiAP 13
How VoIP profile settings determine the firewall policy inspection mode 14
L2TP over IPsec configuration needs to be manually updated after upgrading from 6.4.x
or 7.0.0 to 7.0.1 and later 14
Add interface for NAT46 and NAT64 to simplify policy and routing configurations 15
Upgrading 15
Creating new policies 15
Example configurations 16
ZTNA configurations and firewall policies 18
Default DNS server update 18
Product integration and support 19
Virtualization environments 19
Language support 20
SSL VPN support 21
SSL VPN web mode 21
Resolved issues 22
Explicit Proxy 22
Firewall 22
GUI 22
HA 22
IPsec VPN 23
Proxy 23
2022-12-19 Updated Resolved issues on page 22 and Known issues on page 27.
2023-01-03 Updated Introduction and supported models on page 6 and Known issues on page 27.
2023-01-09 Updated Introduction and supported models on page 6 and Known issues on page 27.
This guide provides release information for FortiOS 7.0.9 build 0444.
For FortiOS documentation, see the Fortinet Document Library.
Supported models
The following models are released on a special branch of FortiOS 7.0.9. To confirm that you are running the correct
build, run the CLI command get system status and check that the Branch point field shows 0444.
Azure-On-Demand image
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.
For ONDEMAND models before 6.4.2, upgrade to 6.4.2 using the FG-VM64-AZUREONDEMAND image. Then, upgrade
to a later build using the FG-VM64-AZURE image.
GCP-On-Demand image
Starting from FortiOS 7.0.0, the FG-VM64-GCPONDEMAND image is no longer provided. Both GCP PAYG and GCP
BYOL models will share the same FG-VM64-GCP image for upgrading and new deployments. Remember to back up
your configuration before upgrading.
For PAYG models with a 6.2.x build, upgrade to the latest 6.4.x build (6.4.5 or later) using the FG-VM64-
GCPONDEMAND image. Then, upgrade to 7.0.x using the FG-VM64-GCP image.
ALI-On-Demand image
Starting from FortiOS 7.0.0, the FG-VM64-ALIONDEMAND image is no longer provided. Both ALI PAYG and ALI BYOL
models will share the same FG-VM64-ALI image for upgrading and new deployments. Remember to back up your
configuration before upgrading.
For PAYG models with a 6.2.x build, upgrade to the latest 6.4.x build (6.4.5 or later) using the FGT-VM64-
ALIONDEMAND image. Then, upgrade to 7.0.x using the FGT-VM64-ALI image.
The following websites are not supported in SSL VPN web mode in FortiOS 7.0.1:
l Facebook
l Gmail
l Office 365
l YouTube
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 7.0.1.
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.
The FEC feature design has the following changes starting in FortiOS 7.0.2:
l FEC enabled on FortiGates running 7.0.2 is not backward compatible with FEC enabled on FortiGates running
previous versions.
l In addition to enabling FEC on IPsec interfaces in previous versions, there is a new option, fec, that should also be
enabled under the related firewall policy so the feature works:
config firewall policy
edit <id>
set fec enable
next
end
l The fec option is not automatically enabled in a firewall policy when upgrading from a previous version. It must be
enabled manually.
FortiOS 7.0.9 includes main branch support for FortiGates with NP7 processors (FG-1800F, FG-1801F, FG-2600F, FG-
2601F, FG-3500F, FG-3501F, FG-4200F, FG-4201F, FG-4400F, and FG-4401F). These FortiGates can also be
licensed for hyperscale firewall features. Previous versions of FortiOS supported FortiGates with NP7 processors
through special branch firmware builds.
For more information, refer to the Hyperscale Firewall Release Notes.
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.
FortiOS 7.0.9 greatly increases the interoperability between other Fortinet products. This includes:
FortiAnalyzer l 7.0.5
FortiManager l 7.0.5
FortiExtender l 4.0.0 and later. For compatibility with latest features, use latest 7.0 version.
*
If you are using FortiClient only for IPsec VPN or SSL VPN, FortiClient version 6.0 and later are supported.
When upgrading your Security Fabric, devices that manage other devices should be upgraded first.
When using FortiClient with FortiAnalyzer, you should upgrade both to their latest versions.
The versions between the two products should match. For example, if using FortiAnalyzer
7.0.0, use FortiClient 7.0.0.
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
17. FortiDeceptor
18. FortiAI/FortiNDR
19. FortiTester
20. FortiMonitor
If Security Fabric is enabled, then all FortiGate devices must be upgraded to 7.0.9. When
Security Fabric is enabled in FortiOS 7.0.9, all FortiGate devices must be running FortiOS
7.0.9.
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
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.
IPsec interfaces may calculate a different MTU value after upgrading from 6.4.
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.
FortiOS 7.0.0 has removed 3DES and SHA1 from the list of strong cryptographic ciphers. To satisfy the cipher
requirement, 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.3 and later
l FortiAP-S and FortiAP-W2 (E models): version 6.2.4, 6.4.1, and later
l FortiAP-U (EV and F models): version 6.0.3 and later
l FortiAP-C (FAP-C24JE): version 5.4.3 and later
If FortiGates running FortiOS 7.0.1 need to manage FortiAP models that cannot be upgraded or legacy FortiAP models
whose names end with the letters B, C, CR, or D, administrators can allow those FortiAPs' connections with weak cipher
encryption by using compatibility mode:
config wireless-controller global
set tunnel-mode compatible
end
When upgrading, all firewall policies with a VoIP profile selected will be converted to proxy-based inspection. All firewall
policies that do not have a VoIP profile selected will remain in the same inspection mode after upgrading.
If the setting is not manually updated after upgrading, the VPN connection will be established, but it will not be accessible
from the internal network (office network). This setting change is necessary regardless of whether route-based or policy-
based IPsec is used.
1. Add a static route for the IP range configured in vpn l2tp. For example, if the L2TP setting in the previous
version's root VDOM is:
config vpn l2tp
set eip 210.0.0.254
set sip 210.0.0.1
set status enable
set usrgrp "L2tpusergroup"
end
Add interface for NAT46 and NAT64 to simplify policy and routing
configurations
This update simplifies the policy and routing of NAT46 and NAT64 policies by adding the NAT tunnel interface and
options in firewall vip/vip6 and firewall policy settings. The policy46 and policy64 settings have been
merged into policy, and vip46 and vip64 into vip and vip6. Most firewall policy options can now be used in policies
with NAT46 and NAT64 options enabled.
Upgrading
When upgrading from FortiOS 6.4.x or 7.0.0 to 7.0.1 and later, the old configurations for vip46, vip64, policy46,
policy64, nat64, and gui-nat46-64 will be removed. All objects in them will be removed.
The following CLI commands have been removed:
l config firewall vip46
During the upgrade process after the FortiGate reboots, the following message is displayed:
The config file may contain errors,
Please see details by the command 'diagnose debug config-error-log read'
After upgrading FortiOS 6.4.x or 7.0.0 to 7.0.1, you will need to manually create new vip46 and vip64 policies.
l Create a vip46 from config firewall vip and enable the nat46 option.
l Create a vip64 from config firewall vip6 and enable the nat64 option.
l Create or modify ippool and ippool6, and enable the nat64 or nat46 option.
l Create a policy and enable the nat46 option, apply the vip46 and ippool6 in a policy.
l Create a policy and enable the nat64 option, apply the vip64 and ippool in policy.
l Ensure the routing on the client and server matches the new vip/vip6 and ippool/ippool6.
Example configurations
vip46 object:
ippool6 object:
NAT46 policy:
vip64 object
ippool object
NAT64 policy:
Since FortiOS 7.0.2, ZTNA configurations no longer require a firewall policy to forward traffic to the access proxy VIP.
This is implicitly generated based on the ZTNA rule configuration.
When upgrading from FortiOS 7.0.1 or below:
l If an access-proxy type proxy-policy does not have a srcintf, then after upgrading it will be set to any.
l To display the srcintf as any in the GUI, System > Feature Visibility should have Multiple Interface Policies
enabled.
l All full ZTNA firewall policies will be automatically removed.
If both primary and secondary DNS servers are set to use the default FortiGuard servers prior to upgrading, the
FortiGate will update them to the new servers and enable DoT after upgrading. If one or both DNS servers are not using
the default FortiGuard server, upgrading will retain the existing DNS servers and DNS protocol configuration.
The following table lists FortiOS 7.0.9 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.
Fortinet Single Sign-On l 5.0 build 0304 and later (needed for FSSO agent support OU in group filters)
(FSSO) l Windows Server 2022 Standard
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
AV Engine l 6.00282
Virtualization environments
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 105
Google Chrome version 107
Other operating systems and web browsers may function correctly, but are not supported by Fortinet.
The following issues have been fixed in version 7.0.9. To inquire about a particular bug, please contact Customer
Service & Support.
Explicit Proxy
Bug ID Description
805703 FortiGate does not load balance requests evenly when the ldb-method is set to least-
session.
Firewall
Bug ID Description
835413 Inaccurate sFlow interface data reported to PRTG after upgrading to 7.0.
843274 Source interface filter (srcintf-filter) is not working with virtual servers.
GUI
Bug ID Description
719476 FortiLink NAC matched device is displayed in the CLI but not in the GUI under WiFi & Switch
Controller > NAC Policies > View Matched Devices.
HA
Bug ID Description
Bug ID Description
840954 The HA pair primary keeps sending fgFmTrapIfChange and fnTrapIpChange after upgrading
to 7.0.6.
843907 Session load balancing is not working in HA A-A configuration for traffic flowing via the VLAN
interface when the port1 link is down on platforms with a 4.19 kernel.
IPsec VPN
Bug ID Description
819276 After changing the password policy to enable it, all non-conforming IPsec tunnels were wiped out
after rebooting/upgrading.
832920 Unable to edit the parent interface from the IPsec configuration if it was configured on an IPIP
tunnel.
840153 Unexpected dynamic selectors block traffic when set mesh-selector-type subnet is
configured.
840940 Unable to reestablish a new IPsec L2TP connection for 10 minutes after the previous one
disconnected. The issue conditions are local in traffic and a policy-based IPsec tunnel.
842528 Improper IKEv1 quick mode fragmentation from third-party client can cause an IKE crash.
Proxy
Bug ID Description
827807 WAD crash at signal 11 is observed after configuring 250 CGN VDOMs (full offload is enabled in the
VDOMs).
837095 WAD daemon runs high with many child processes and is not coming down after configuring 250
CGN VDOMs.
Routing
Bug ID Description
833800 The speed-test-server list cannot be loaded due to limited buffer size.
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.
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.
808634 SSL VPN daemon sometimes could not be recovered, even when setting the server certificate back
from empty to a specific certificate.
820536 SSL VPN web mode bookmark incorrectly applies a URL redirect.
822432 SSL VPN crashes after copying a string to the remote server using the clipboard in RDP web mode
when using RDP security.
848437 The sslvpn process crashes if a POST request with a body greater than 2 GB is received.
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.
System
Bug ID Description
798992 Get newcli crash when running the diagnose hardware test memory command.
Bug ID Description
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.
831486 HQIP memory test failed and triggered a log out with a newcli process crash.
844316 IPS and application control is causing the FortiGate (VWP) to change either the source MAC
address or the destination MAC address based on the flow.
844908 Outbandwidth does not control traffic properly on platforms with a 4.19 kernel when VDOM links are
used.
844937 FG-3700D unexpectedly reboots after the COMLog reported a kernel panic due to an IPv6 failure to
set up the master session for the expectation session under some conditions.
850430 DHCP relay does not work properly with two DHCP relay servers configured.
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.
VM
Bug ID Description
Bug ID Description
838913 The WAF is indicating malformed request false positives caused by incorrect setups of four known
headers: Access-Control-Max-Age, Access-Control-Allow-Headers, Access-Control-Allow-
Methods, and Origin.
Web Filter
Bug ID Description
742483 System events logs randomly contain a msg=UrlBwl-black gzopen fail message.
847676 Unrated is displayed, even if the system language is set to Japanese when the policy inspection
mode is set to flow.
WiFi Controller
Bug ID Description
844172 The cw_acd process is deleting dynamic IPsec tunnels on the secondary device, which causes the
FortiAPs to disconnect on the primary device.
The following issues have been identified in version 7.0.9. To inquire about a particular bug or report a bug, please
contact Customer Service & Support.
Endpoint Control
Bug ID Description
730767 The new HA primary FortiGate cannot get EMS Cloud information when HA switches over.
Workaround: delete the EMS Cloud entry then add it back.
Firewall
Bug ID Description
860480 FG-3000D cluster kernel panic occurs when upgrading from 7.0.5 to 7.0.6 and later.
861990 Increased CPU usage in softirq after upgrading from 7.0.5 to 7.0.6.
865661 Standard and full ISDB sizes are not configurable on FG-101F.
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.
677806 On the Network > Interfaces page when VDOM mode is enabled, the Global view incorrectly shows
the status of IPsec tunnel interfaces from non-management VDOMs as up. The VDOM view shows
the correct status.
685431 On the Policy & Objects > Firewall Policy page, the policy list can take around 30 seconds or more
to load when there is a large number (over 20 thousand) of policies.
Workaround: use the CLI to configure policies.
Bug ID Description
707589 System > Certificates list sometimes shows an incorrect reference count for a certificate, and
incorrectly allows a user to delete a referenced certificate. The deletion will fail even though a
success message is shown. Users should be able to delete the certificate after all references are
removed.
708005 When using the SSL VPN web portal in the Firefox, users cannot paste text into the SSH terminal
emulator.
Workaround: use Chrome, Edge, or Safari as the browser.
755177 When upgrade firmware from 7.0.1 to 7.0.2, the GUI incorrectly displays a warning saying this is not
a valid upgrade path.
810225 An undefined error is displayed when changing an administrator password for the first time. Affected
models: NP7 platforms.
853352 On the View/Edit Entries slide-out pane (Policy & Objects > Internet Service Database dialog),
users cannot scroll down to the end if there are over 100000 entries.
HA
Bug ID Description
810286 FGSP local sessions exist after rebooting an HA pair with A-P mode, and the HW SSE/session
count is incorrect.
Hyperscale
Bug ID Description
782674 A few tasks are hung on issuing stat verbose on the secondary device.
795853 VDOM ID and IP addresses in the IPL table are incorrect after disabling EIF/EIM.
807476 After packets go through host interface TX/RX queues, some packet buffers can still hold
references to a VDOM when the host queues are idle. This causes a VDOM delete error with
unregister_vf. If more packets go through the same host queues for other VDOMs, the issue
should resolve by itself because those buffers holding the VDOM reference can be pushed and get
freed and recycled.
811109 FortiGate 4200F, 4201F, 4400F, and 4401F HA1, HA2, AUX1, and AUX2 interfaces cannot be
added to an LAG.
836976 Traffic impact on changing from log to hardware to log to host during runtime (with PPA enabled).
Bug ID Description
838654 Hit count not ticking for implicit deny policy for hardware session in case of NAT46 and NAT64
traffic.
842659 srcaddr-negate and dstaddr-negate are not working properly for IPv6 traffic with FTS.
843132 After dynamically adding an ACL policy, the existing matched session is not cleared immediately.
843197 Output of diagnose sys npu-session list/list-full does not mention policy route
information.
843266 Diagnose command should be available to show hit_count/last_used for policy route and NPU
session on hyperscale VDOM.
843305 Get PARSE SKIP ERROR=17 NPD ERR PBR ADDRESS console error log when system boots up.
844421 The diagnose firewall ippool list command does not show the correct output for
overload type IP pools.
846520 NPD/LPMD process killed by out of memory killer after running mixed sessions and HA failover.
IPsec VPN
Bug ID Description
761754 IPsec aggregate static route is not marked inactive if the IPsec aggregate is down.
Log & Report
Bug ID Description
850642 Logs are not seen for traffic passing through the firewall.
Proxy
Bug ID Description
Bug ID Description
856235 The WAD process memory usage gradually increases over a few days, causing the FortiGate to
enter into conserve mode.
Routing
Bug ID Description
847037 When the policy route has a gateway set, the FortiGate is not following the policy route to forward
traffic and sends unreasonable ARP requests.
Security Fabric
Bug ID Description
614691 Slow GUI performance in large Fabric topology with over 50 downstream devices.
794703 Security Rating report for Rogue AP Detection and FortiCare Support checks show incorrect
results.
839258 Unable to add another FortiGate to the Security Fabric after updating to the latest patch.
SSL VPN
Bug ID Description
746230 SSL VPN web mode cannot display certain websites that are internal bookmarks.
819754 Multiple DNS suffixes cannot be set for the SSL VPN portal.
848067 RDP over VPN SSL web mode stops work after upgrading.
852566 User peer feature for one group to match to multiple user peers in the authentication rules is broken.
System
Bug ID Description
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.
824543 The reply-to option in the email server settings is no longer visible in a default server
configuration on FortiOS 7.2.0.
827240 FortiGate in HA may freeze and reboot. Before the reboot, softIRQ may be seen as high. This leads
to a kernel panic.
847077 Can't find xitem. Drop the response. error appears for DHCPOFFER packets in the
DHCP relay debug.
847314 NP7 platforms may encounter random kernel crash after reboot or factory reset.
847664 Console may display mce: [Hardware Error] error message after fresh image burn or reboot.
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.
853794 Issue with the server_host_key_algorithm compatibility when using SSH on SolarWinds.
855573 False alarm of the PSU2 occurs with only one installed.
856202 Random reboots and kernel panic on NP7 cluster when the FortiGate sends a TCP RST packet and
IP options are missing in the header.
859717 The FortiGate is only offering the ssh-ed25519 algorithm for an SSH connection.
Workaround: factory reset the FortiGate, then restore the same configuration without making any
changes to the configuration.
Upgrade
Bug ID Description
850691 The endpoint-control fctems entry 0 is added after upgrading from 6.4 to 7.0.8 when the
FortiGate does not have EMS server, which means the endpoint-control fctems feature was
not enabled previously. This leads to a FortiManager installation failure.
Workaround: upgrade from FortiOS 6.4.x to 7.0.7 and then 7.0.8. If you have already upgraded to
FortiOS 7.0.8, reboot the FortiGate to automatically set endpoint-control fctems to 1.
Bug ID Description
854550 After upgrading to 7.0.8, replacemsg utm parameters are not taken over and revert to the default.
Affected replacement messages under config system replacemsg utm: virus-html,
virus-text, dlp-html, dlp-text, and appblk-html.
Bug ID Description
765184 RADIUS authentication failover between two servers for high availability does not work as
expected.
WAN Optimization
Bug ID Description
728861 HTTP/HTTPS traffic cannot go through when wanopt is set to manual mode and an external proxy
is used.
Workaround: set wanopt to automatic mode, or set transparent disable in the wanopt
profile.
Web Filter
Bug ID Description
766126 Block replacement page is not pushed automatically to replace the video content when using a
video filter.
ZTNA
Bug ID Description
848222 ZTNA TCP forwarding is not working when a real server is configured with an FQDN address type.
An FQDN address type that can resolve public IPs is not recommended for ZTNA TCP forwarding
on real servers because the defined internal DNS database zone is trying to override it at the same
time. By doing so, the internal private address may not take effect after rebooting, and causes a
ZTNA TCP forwarding failure due to the real server not being found.
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.
Copyright© 2023 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein
may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were
attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance
results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract,
signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only
the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to performance in the same ideal
conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change,
modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.