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. Therefore, when an interface IP is not allowed to connect externally, the probe session fails and causes traffic to not work. When an explicit proxy is enabled with IP pools, certificate inspection probe sessions use the interface IP instead of IPs from the configured IP pool. When converting an explicit proxy session to SSL redirect, traffic may be interrupted inadvertently in some situations. Application ControlĪpplication control does not block FTP traffic on an explicit proxy. To inquire about a particular bug or report a bug, please contact Customer Service & Support. The following issues have been identified in version 6.4.9. VDOM link and policy configuration is lost after upgrading if VDOM and VDOM link have the same name Hardware switch members configurable under system interface list Minimum version of TLS services automatically changedĭowngrading to previous firmware versionsĪmazon AWS enhanced networking compatibility issueįortiGuard update-server-location setting IP pools and VIPs are not considered local addresses for certain FortiOS versions Support for FortiGates with NP7 processors and hyperscale firewall featuresĬAPWAP offloading compatibility of FortiGate NP7 platforms RDP and VNC clipboard toolbox in SSL VPN web mode Policy routing enhancements in the reply direction SSL traffic over TLS 1.0 will not be checked and will be bypassed by default System Advanced menu removal (combined with System Settings)įG-80E-POE and FG-81E-POE PoE controller firmware update Use of dedicated management interfaces (mgmt1 and mgmt2) FortiClient (Mac OS X) SSL VPN requirements
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |