forward error correction fortigate
Fortinet Public company Business Business, Economics, and Finance. As packet loss increases, the number of redundant packets sent can rise accordingly. Created on Because FEC does not support NPU offloading, the ability to specify streams and policies that do not require FEC allows those traffic to be offloaded. Fortinet SD WAN Forward Error Correction Example - YouTube Fortinet SD WAN Forward Error Correction Voice Fortinet SD WAN Forward Error Correction Voice AboutPressCopyrightContact. Copyright 2023 Fortinet, Inc. All Rights Reserved. Edited By For example how many redundant packets are being sent. 11-26-2020 Adaptive FEC starts to work at 2% packet loss; this value is hard-coded and is not configurable. The time before sending Forward Error Correction packets, in milliseconds (1 - 1000, default = 8). B. FEC transmits the original payload Which statement is correct about the SD-WAN and ADVPN? Created on FortiGate / FortiOS; FortiGate 5000; FortiGate 6000; FortiGate 7000; FortiProxy; NOC & SOC Management If your FortiGate is NPU capable, disable npu-offload in your phase1 configurations: For example, a customer has two ISP connections, wan1 and wan2. This technique is known as the Forward Error Correction technique. In this example, an IPsec tunnel is configured between two FortiGates that both have FEC enabled. Enable/disable Forward Error Correction for egress IPsec traffic (default = disable). Because FEC does not support NPU offloading, the ability to specify streams and policies that do not require FEC allows those traffic to be offloaded. The URL category must be specified on the traffic shaping policy. Forward Error Correction Three common methods for error detection: I Parity I Checksum I Cyclic . It's not just a simple duplication of the data. B. Lastly, it is necessary to make sure the correct media type is configured on the interface settings. FEC can be applied only to streams that are sensitive to packet loss. An FEC profile is configured to adaptively increase redundant levels if the link quality exceeds a 10% packet loss threshold, or the bandwidth exceeds 950 Mbps. 01:43 AM, The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.. FortiGate is not performing traffic shaping as expected, based on the policies shown in the exhibits. 10-29-2019 1100E, 2200E, 3300E, 3400E, 3960E, 3980E models. do cookie clicker mods disable achievements? The intention is to apply FEC to UDP traffic that is passing through the VPN overlay, while allowing all other traffic to pass through without FEC. The plethora of vendors that resell hardware but have zero engineering knowledge resulting in the wrong hardware or configuration being deployed is a major pet peeve of Michael's. On both FortiGates, enable FEC and NPU offloading on the IPsec tunnel vd1-p1: The VPN overlay member (vd1-p1) must be included in the health-check and configured as the higher priority member in the SD-WAN rule. Answer. The time before dropping Forward Error Correction packets, in milliseconds (1 - 1000, default = 5000). FEC is enabled on vd1-p1, and health-check works on vd1-p1. In order to correct the errors, one has to know the exact position of the error. If fec-codec is set to xor the base and redundant packet values will not be updated. Following are some NSE7_SDW-6.4 Exam Questions for Review. The sender adds parts of the data again. This option is only available for 25Gbps ports. Forward Error Correction (FEC) is a mechanism to recover lost packets on a link by sending extra "parity" packets for every group of 4 packets. It uses six parameters in IPsec phase1/phase1-interface settings: For every fec-base number of sent packets, the tunnel will send fec-redundant number of redundant packets. FEC can be applied only to streams that are sensitive to packet loss. FEC is enabled on vd1-p1, and health-check works on vd1-p1. Forward Error Correction (FEC) is used to lower the packet loss ratio by consuming more bandwidth. FEC can be applied only to streams that are sensitive to packet loss. Supported managed-switch ports can be configured with a forward error correction (FEC) state of Clause 74 FC-FEC for 25-Gbps ports and Clause 91 RS-FEC for 100-Gbps ports. Hamming Codes It is a block code that is capable of detecting up to two simultaneous bit errors and correcting single-bit errors. Which two reasons make forward error correction (FEC) ideal to enable in a phase one VPN interface? A. Forward error correction (FEC) is a digital signal processing technique used to enhance data reliability. 08:54 AM Forgot password? Adaptive FEC considers link conditions and dynamically adjusts the FEC packet ratio: The FEC base and redundant packet relationship is dynamically adjusted based on changes to the network SLA metrics defined in the SD-WAN SLA health checks. This topic shows an SD-WAN with forward error correction (FEC) on VPN overlay networks. Does any one know how to build a FortiAnalyzer query for this? Home; Product Pillars. This blog post explains how FEC works and describes how leading SD-WAN platforms utilize it to mitigate packet loss. In this example, an IPsec tunnel is configured between two FortiGates that both have FEC enabled. The mechanism sends out x number of redundant packets for every y number of base packets. A. FEC is useful to increase speed at which traffic is routed through IPsec tunnels. It is important to keep FEC settings the same on both FortiGate and switch sides, otherwise, ports will not get up due to mismatch. Send TCP and UDP traffic from PC1 to PC2, then check the sessions on FortiGate A: Non-FEC protected TCP traffic is offloaded, while FEC protected UDP traffic is not offloaded. If fec-codec is set to xor the base and redundant packet values will not be updated. The tunnel is an SD-WAN zone, and an SLA health-check is used to monitor the quality of the VPN overlay. Solution. The number of base Forward Error Correction packets (1 - 100, default = 20). The intention is to apply FEC to UDP traffic that is passing through the VPN overlay, while allowing all other traffic to pass through without FEC. If more than one tunnel is available, duplicated packets will be sent over the tunnel with the best parameters. As packet loss increases, the number of redundant packets sent can rise accordingly. Solution Six new parameters are added to the IPsec phase1-interface settings: fec-ingress: Enable/disable Forward Error Correction for ingress IPsec traffic (default = disable). Question 1. Forward Error Correction (FEC) is used to control and correct errors in data transmission by sending redundant data across the VPN in anticipation of dropped packets occurring during transit. Add real-time FortiView monitors for proxy traffic 7.0.4, Add options for API Preview, Edit in CLI, and References, Seven-day rolling counter for policy hit counters, FortiGate administrator log in using FortiCloud single sign-on, Export firewall policy list to CSV and JSON formats 7.0.2, GUI support for configuration save mode 7.0.2, Automatically enable FortiCloud single sign-on after product registration 7.0.4, Loading artifacts from a CDN for improved GUI performance 7.0.4, Security Fabric support in multi-VDOM environments, Enhance Security Fabric configuration for FortiSandbox Cloud, Show detailed user information about clients connected over a VPN through EMS, Add FortiDeceptor as a Security Fabric device, Improve communication performance between EMS and FortiGate with WebSockets, Simplify EMS pairing with Security Fabric so one approval is needed for all devices, FortiTester as a Security Fabric device 7.0.1, Simplify Fabric approval workflow for FortiAnalyzer 7.0.1, Allow deep inspection certificates to be synchronized to EMS and distributed to FortiClient 7.0.1, Add FortiMonitor as a Security Fabric device 7.0.2, Display EMS ZTNAand endpoint tags in user widgets and Asset Identity Center 7.0.4, Replace FSSO-based FortiNAC tag connector with REST API 7.0.4, Add WebSocket for Security Fabric events 7.0.4, FortiGate Cloud logging in the Security Fabric 7.0.4, Add support for multitenant FortiClient EMS deployments 7.0.8, STIX format for external threat feeds 7.0.2, Add test to check for two-factor authentication, Add test to check for activated FortiCloud services, Add tests for high priority vulnerabilities 7.0.1, Add FortiGuard outbreak alerts category 7.0.4, Usability enhancements to SD-WAN Network Monitor service, Hold down time to support SD-WAN service strategies, SD-WAN passive health check configurable on GUI 7.0.1, ECMP support for the longest match in SD-WAN rule matching 7.0.1, Override quality comparisons in SD-WAN longest match rule matching 7.0.1, Specify an SD-WAN zone in static routes and SD-WAN rules 7.0.1, Display ADVPN shortcut information in the GUI 7.0.1, Speed tests run from the hub to the spokes in dial-up IPsec tunnels 7.0.1, Interface based QoS on individual child tunnels based on speed test results 7.0.1, Passive health-check measurement by internet service and application 7.0.2, Summarize source IP usage on the Local Out Routing page, Add option to select source interface and address for Telnet and SSH, ECMP routes for recursive BGP next hop resolution, BGP next hop recursive resolution using other BGP routes, Add SNMPOIDs for shaping-related statistics, PRP handling in NAT mode with virtual wire pair, NetFlow on FortiExtender and tunnel interfaces, Integration with carrier CPE management tools, BGP conditional advertisement for IPv6 7.0.1, Enable or disable updating policy routes when link health monitor fails 7.0.1, Add weight setting on each link health monitor server 7.0.1, Enhanced hashing for LAG member selection 7.0.1, Add GPS coordinates to REST API monitor output for FortiExtender and LTE modems 7.0.2, Configure IPAM locally on the FortiGate 7.0.2, Use DNS over TLS for default FortiGuard DNS servers 7.0.4, Accept multiple conditions in BGP conditional advertisements 7.0.4, Enhanced BGP next hop updates and ADVPN shortcut override 7.0.4, Allow per-prefix network import checking in BGP 7.0.4, Support QinQ 802.1Q in 802.1Q for FortiGate VMs 7.0.4, Allow only supported FEC implementations on 10G, 25G, 40G, and 100G interfaces 7.0.4, Support 802.1X on virtual switch for certain NP6 platforms 7.0.6, SNMP OIDs for port block allocations IP pool statistics 7.0.6, Increase the number of VRFs per VDOM 7.0.6, Support cross-VRF local-in and local-out traffic for local services 7.0.6, Configuring IPv6 multicast policies in the GUI, FortiGate as an IPv6 DDNS client for generic DDNS, FortiGate as an IPv6 DDNS client for FortiGuard DDNS, Allow backup and restore commands to use IPv6 addresses, IPv6 tunnel inherits MTU based on physical interface 7.0.2, Selectively forward web requests to a transparent web proxy, mTLS client certificate authentication 7.0.1, WAN optimization SSL proxy chaining 7.0.1, Support CORS protocol in explicit web proxy when using session-based, cookie-enabled, and captive portal-enabled SAML authentication 7.0.6, Allow administrators to define password policy with minimum character change, Add monitoring API to retrieve LTE modem statistics from 3G and 4G FortiGates 7.0.1, Add USB support for FortiExplorer Android 7.0.1, Enabling individual ciphers in the SSH administrative access protocol 7.0.2, Clear multiple sessions with REST API 7.0.2, Disable weak ciphers in the HTTPS protocol 7.0.2, Extend dedicated management CPU feature to 1U and desktop models 7.0.2, Improve admin-restrict-local handling of multiple authentication servers 7.0.8, Optimizing FGSP session synchronization and redundancy, Layer 3 unicast standalone configuration synchronization between peers, Improved link monitoring and HA failover time, HA monitor shows tables that are out of synchronization, Resume IPS scanning of ICCP traffic after HA failover 7.0.1, Applying the session synchronization filter only between FGSP peers in an FGCP over FGSP topology 7.0.6, FGCP over FGSP per-tunnel failover for IPsec 7.0.8, Allow IPsec DPD in FGSP members to support failovers 7.0.8, Add option to automatically update schedule frequency, Use only EU servers for FortiGuard updates 7.0.2, FDS-only ISDB package in firmware images 7.0.4, Establish device identity and trust context with FortiClient EMS, ZTNA HTTPS access proxy with basic authentication example, ZTNA proxy access with SAML authentication example, ZTNA TCP forwarding access proxy without encryption example 7.0.1, Migrating from SSL VPN to ZTNA HTTPS access proxy, Implicitly generate a firewall policy for a ZTNA rule 7.0.2, Posture check verification for active ZTNA proxy session 7.0.2, GUI support for multiple ZTNA features 7.0.2, Use FQDN with ZTNA TCP forwarding access proxy 7.0.4, UTM scanning on TCP forwarding access proxy traffic 7.0.4, Connect a ZTNA access proxy to an SSL VPN web portal 7.0.4, ZTNA FortiView and log enhancements 7.0.4, ZTNA session-based form authentication 7.0.4, Using the IP pool or client IP address in a ZTNA connection to backend servers 7.0.6, Filters for application control groups in NGFW mode, DNS health check monitor for server load balancing, Allow multiple virtual wire pairs in a virtual wire pair policy, Simplify NAT46 and NAT64 policy and routing configurations 7.0.1, Cisco Security Group Tag as policy matching criteria 7.0.1, Allow VIPs to be enabled or disabled in central NAT mode 7.0.1, Stream-based antivirus scan in proxy mode for FTP, SFTP, and SCP, Configure threat feed and outbreak prevention without AV engine scan, FortiAI inline blocking and integration with an AV profile 7.0.1, FortiGuard web filter categories to block child sexual abuse and terrorism, Add categories for URL shortening, crypto mining, and potentially unwanted programs 7.0.2, HTTP/2 support in proxy mode SSL inspection, Define multiple certificates in an SSL profile in replace mode, Add TCP connection pool for connections to ICAP server, DNS filter handled by IPS engine in flow mode, Allow the YouTube channel override action to take precedence 7.0.6, Packet distribution for aggregate dial-up IPsec tunnels, Dual stack IPv4 and IPv6 support for SSL VPN, Disable the clipboard in SSL VPN web mode RDP connections 7.0.1, SSL VPN and IPsec VPN IP address assignments 7.0.1, Dedicated tunnel ID for IPsec tunnels 7.0.1, Allow customization of RDP display size for SSL VPN web mode 7.0.4, Integrate user information from EMS connector and Exchange connector in the user store, Improve FortiToken Cloud visibility 7.0.1, Use a browser as an external user-agent for SAML authentication in an SSL VPN connection 7.0.1, Add configurable FSSO timeout when connection to collector agent fails 7.0.1, Track users in each Active Directory LDAP group 7.0.2, Migrating FortiToken Mobile users from FortiOS to FortiToken Cloud 7.0.4, Synchronizing LDAP Active Directory users to FortiToken Cloud using the group filter 7.0.6, Captive portal authentication when bridged via software switch, Increase maximum number of supported VLANs, Station mode on FortiAP radios to initiate tests against other APs, Allow indoor and outdoor flags to be overridden 7.0.1, DNS configuration for local standalone NAT VAPs 7.0.1, Backward compatibility with FortiAP models that uses weaker ciphers 7.0.1, Disable console access on managed FortiAP devices 7.0.1, Captive portal authentication in service assurance management (SAM) mode 7.0.1, Support CAPWAP hitless failover using FGCP 7.0.1, Provide LBS station information with REST API 7.0.2, Allow users to select individual security profiles in bridged SSID 7.0.2, Wireless client MAC authentication and MPSK returned through RADIUS 7.0.2, FQDN for FortiPresence server IP address in FortiAP profiles 7.0.2, Wi-Fi Alliance Hotspot 2.0 Release 3 support 7.0.2, Syslog profile to send logs to the syslog server 7.0.4, Support Dynamic VLAN assignment by Name Tag 7.0.4, DAARP to consider full channel bandwidth in channel selection 7.0.4, Support multiple DARRP profiles and per profile optimize schedule 7.0.4, Support WPA3 on FortiWiFi F-series models 7.0.4, Support advertising vendor specific element in beacon frames 7.0.4, GUI support for Wireless client MAC authentication and MPSK returned through RADIUS 7.0.4, GUI enhancements to distinguish UTM capable FortiAP models 7.0.4, Upgrade FortiAP firmware on authorization 7.0.4, Wireless Authentication using SAML Credentials 7.0.5, Add profile support for FortiAP G-series models supporting WiFi 6E Tri-band and Dual 5 GHz modes 7.0.8, Forward error correction settings on switch ports, Cancel pending or downloading FortiSwitch upgrades, Automatic provisioning of FortiSwitch firmware upon authorization, Additional FortiSwitch recommendations in Security Rating, PoE pre-standard detection disabled by default, Cloud icon indicates that the FortiSwitch unit is managed over layer 3, GUI support for viewing and configuring shared FortiSwitch ports, Ability to re-order FortiSwitch units in the Topology view 7.0.1, Support of the DHCP server access list 7.0.1, SNMP OIDs added for switch statistics and port status 7.0.1, Display port properties of managed FortiSwitch units 7.0.1, IGMP-snooping querier and per-VLAN IGMP-snooping proxy configuration 7.0.2, Managing DSL transceivers (FN-TRAN-DSL) 7.0.2, One-time automatic upgrade to the latest FortiSwitch firmware 7.0.4, Support hardware vendor matching in dynamic port policies 7.0.4, Configure the frequency of IGMP queries 7.0.8, Use wildcards in a MAC address in a NAC policy, Dynamic port profiles for FortiSwitch ports, Support dynamic firewall addresses in NAC policies 7.0.1, Specify FortiSwitch groups in NAC policies 7.0.2, Introduce LAN extension mode for FortiExtender 7.0.2, Using the backhaul IP when the FortiGate access controller is behind NAT 7.0.2, Bandwidth limits on the FortiExtender Thin Edge 7.0.2, IPAM in FortiExtender LAN extension mode 7.0.4, FortiExtender LAN extension in public cloud FGT-VM 7.0.4, Add logs for the execution of CLI commands, Logging IP address threat feeds in sniffer mode, Generate unique user name for anonymized logs 7.0.2, Collect only node IP addresses with Kubernetes SDN connectors, Update AliCloud SDN connector to support Kubernetes filters, Synchronize wildcard FQDN resolved addresses to autoscale peers, Obtain FortiCare-generated license and certificates for GCP PAYG instances, FortiGate VM on KVM running ARM processors 7.0.1, Support MIME multipart bootstrapping on KVM with config drive 7.0.1, FIPS cipher mode for OCI and GCP FortiGate VMs 7.0.1, SD-WAN transit routing with Google Network Connectivity Center 7.0.1, Support C5d instance type for AWS Outposts 7.0.1, FGSP session sync on FortiGate-VMs on Azure with autoscaling enabled 7.0.1, Flex-VM token and bootstrap configuration file fields in custom OVF template 7.0.2, Subscription-based VDOM license for FortiGate-VM S-series 7.0.2, Multitenancy support with AWS GWLB enhancement 7.0.4, FortiCarrier upgrade license for FortiGate-VM S-series 7.0.4, Injecting Flex-VM license via web proxy 7.0.4, Support Graviton c7g and c6gn instance types on AWS 7.0.8, Support Ampere A1 Compute instances on OCI 7.0.8. c191: Enable Clause 91 RS-FEC. REGISTER. Using these two connections, create two IPsec VPN interfaces as SD-WAN members. For Example, policies that allow the UDP based VoIP protocol can enable FEC, while TCP based traffic policies do not. With the default register settings in AT86RF215, FEC can be enabled with FSKPHRTX.SFD = 1. Show Forward Error Correction (FEC) in FAZ reporting Hi All, We are using FEC on some FortiGates. Refer to the exhibit. It does this by introducing redundant data, called error correcting code, prior to data transmission or storage. For Example, policies that allow the UDP based VoIP protocol can enable FEC, while TCP based traffic policies do not. On FortiGate A, create a policy to specify performing FEC on UDP traffic, and a policy for other traffic: On FortiGate A, configure FEC mapping to bind network SLA metrics and FEC base and redundant packets: The mappings are matched from top to bottom: packet loss greater than 10% with eight base and two redundant packets, and then uploading bandwidth greater than 950 Mbps with nine base and three redundant packets. Forward error correction In telecommunications Forward error correction (FEC) is a special code for error detection and correction. Forward error connection is not supported for interfaces in FortiGates with NP7 processors operating at any other speeds. The receiver is then able to detect certain errors that came from the sending the data. FortiAnalyzer Fortigate 35 0 Share Reply All forum topics Previous Topic Next Topic This article describes how to cover the changes in FEC settings for some FortiGates. Created on For example how many redundant packets are being sent. Configure FEC on each VPN interface to lower packet loss ratio by re-transmitting the packets using its backend algorithm. Forward error correction only available for 100 GigE interfaces On FortiGate models with NP7 processors, the forward-error-correction CLI option is only available for interfaces with speed set to 100Gfull. Network Security. (Choose two ) A The debug output shows per-IP shaper values and real-time readings. As packet loss increases, the number of redundant packets sent can rise accordingly. FEC is a technique used to control and correct errors in data transmission by sending redundant data across the VPN. Does any one know how to build a FortiAnalyzer query for this? FortiGate supports unidirectional and bidirectional FEC, and achieves the expected packet loss ration and latency by tuning the above parameters. 'Enable' was forked into two options - Reed-Solomon (FEC CL91) and Fire-Code (FEC CL74). Technical Tip: changes in Forward Error Correct (F Technical Tip: changes in Forward Error Correct (FEC) settings. It is especially important to keep in mind the changes when upgrading the setup to newer FortiOS versions from 6.2 and 6.4. Adaptive FEC considers link conditions and dynamically adjusts the FEC packet ratio: The FEC base and redundant packet relationship is dynamically adjusted based on changes to the network SLA metrics defined in the SD-WAN SLA health checks. Home FortiGate / FortiOS 7.0.0 New Features 7.0.0 Download PDF Forward error correction settings on switch ports Supported managed-switch ports can be configured with a forward error correction (FEC) state of Clause 74 FC-FEC for 25-Gbps ports and Clause 91 RS-FEC for 100-Gbps ports. This reduces unnecessary bandwidth consumption by FEC. FG22E1-2 (port25) # set forward-error-correction ?enable <----- Enable forward error correction (FEC).disable <----- Disable forward error correction (FEC). Password. An FEC profile is configured to adaptively increase redundant levels if the link quality exceeds a 10% packet loss threshold, or the bandwidth exceeds 950 Mbps. On FortiGate A, apply the FEC mappings on vd1-p1: The FEC base and redundant values are used when the link quality has not exceeded the limits specified in the FEC profile mapping. B This traffic shaper drops traffic that exceeds the set limits. If fec-codec is set to xor the base and redundant packet values will not be updated. Yes, it's additional redundant data, but it's gone through a complex mathematical transformation that means that you can lose any portion of a data block and still recover the original. For Example, policies that allow the UDP based VoIP protocol can enable FEC, while TCP based traffic policies do not. Forward Error Correction (FEC) is a mechanism to recover lost packets on a link by sending extra "parity" packets for every group (N) of packets. FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic. meraas board of directors; missile silos in illinois Fortinet Community Knowledge Base FortiGate Forward-looking statements in this report, including without limitation, statements related to the Company's plans, strategies, objectives, expectations, intentions and adequacy of resources, are made pursuant to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995. On FortiGate A, create a policy to specify performing FEC on UDP traffic, and a policy for other traffic: On FortiGate A, configure FEC mapping to bind network SLA metrics and FEC base and redundant packets: The mappings are matched from top to bottom: packet loss greater than 10% with eight base and two redundant packets, and then uploading bandwidth greater than 950 Mbps with nine base and three redundant packets. Show Forward Error Correction (FEC) in FAZ reporting Hi All, We are using FEC on some FortiGates. FortiGate supports unidirectional and bidirectional FEC, and achieves the expected packet loss ration and latency by tuning the above parameters. Email. FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic. This means that all traffic suffers a performance impact. An FEC profile is configured to adaptively increase redundant levels if the link quality exceeds a 10% packet loss threshold, or the bandwidth exceeds 950 Mbps. Technical Tip: changes in Forward Error Correct (FEC) settings Description This article describes how to cover the changes in FEC settings for some FortiGates. 11-29-2022 Two checkboxes are added to the IPsec phase1 settings in the GUI: Telemetry Integration - New FTNTProducts, Telemetry Integration - AWS Cloud Segments, Security Rating - Extend Checks to FortiAnalyzer, Security Rating Historical Rating Dashboard Widget, Dynamic Policy FortiClient EMS (Connector), FortiToken Cloud multi-factor authentication in the GUI6.2.1, Dynamic VLAN 'Name' Assignment from RADIUS Attribute, QoS Assignment and Rate Limiting for Quarantined VLANs, FortiLink Auto Network Configuration Policy, Leverage SAML to switch between Security Fabric FortiGates6.2.1, Leverage LLDP to Simplify Security Fabric Negotiation, Configuring single-sign-on in the Security Fabric6.2.2, VMware NSX-T managed by FortiManager6.2.2, Filter Lookup Improvement for SDNConnectors, Obtain full user information through the MS Exchange connector, External Block List (Threat Feed) Policy, External Block List (Threat Feed)- File Hashes, External Block List (Threat Feed) - Authentication, Use active directory objects directly in policy6.2.1, LDAP connector to get more user information from user login IDs6.2.1, ClearPass endpoint connector via FortiManager6.2.2, ClearPass integration for dynamic address objects6.2.2, Support for wildcard SDN connectors in filter configurations6.2.3, Enable dynamic connector address used in policies6.2.1, Traffic shaping profile additional priorities6.2.1, Represent Multiple IPsec Tunnels as a Single Interface, Per-link controls for policy and SLA checks6.2.1, Weighted random early detection support6.2.1, FortiCare-generated license adoption for AWS PAYG variant6.2.2, Azure SDN connector support for non-VM resources6.2.3, High Availability between Availability Domains, Active-Passive HA support between Availability Zones6.2.1, Active-Passive HA support on AliCloud6.2.1, OpenStack Network Service Header (NSH) Chaining Support, Physical Function (PF)SR-IOV Driver Support, FortiMeter - Fallback to Public FortiGuard, CPU only licensing for private clouds6.2.2, File Filtering for Web and Email Filter Profiles, NGFW policy mode application default service6.2.1, Adding CPU affinity for URL filters6.2.1, Extend log timestamp to nanoseconds6.2.1, Password change prompt on first login6.2.1, Logging - Session versus Attack Direction, Application Control Profile GUI Improvements, Extend Policy/Route Check to Policy Routing, Automatic Address Creation for Attached Networks, Unified Login for FortiCare and FortiGate Cloud, Advanced policy options in the GUI6.2.2, Support for wildcard FQDN addresses in firewall policy6.2.2, Traffic class ID configuration updates6.2.2, Security Fabric topology improvements6.2.2, Adding IPsec aggregate members in the GUI6.2.3, Extend Interface Failure Detection to Aggregate Interfaces, Multiple FortiAnalyzer (or Syslog) Per VDOM, Restricted SaaS Access (0365, G-Suite, Dropbox), Syntax update for Microsoft compatibility6.2.1, LACP support on entry-level E-series devices6.2.1, FortiGate Cloud / FDNcommunication through an explicit proxy6.2.1, Transceiver information on FortiOSGUI6.2.1, LACP support on entry-level devices6.2.2, LACP support on entry-level devices6.2.4, Recognize AnyCast Address in Geo-IP Blocking, Firewall - Allow to Customize Default Service, Option to Disable Stateful SCTP Inspection, Option to Fragment IP Packets Before IPSec Encapsulation, Controlling return path with auxiliary session, Decouple FortiSandbox Cloud from FortiCloud, FortiGuard Distribution of Updated Apple Certificates (for token push notifications), Device detection changes when upgrading to 6.26.2.1, Flow versus proxy policy improvement6.2.1, Virtual switch support for FortiGate 300E series6.2.2, IPsec VPN wizard hub-and-spoke ADVPN support6.2.2, FortiGuard communication over port 443 with HTTPS6.2.2, FortiGuard third Party SSL validation and Anycast support6.2.2, Remove FortiGate Cloud standalone reference6.2.3, Dynamic address support for SSL VPN policies6.2.3, GUI support for FortiAP U431F and U433F6.2.3, Retrieve client OS information from FortiAP 6.2.4.