Fortinet Document Library

Version:

Version:

Version:

Version:

Version:


Table of Contents

Hardware Acceleration

NP7 session fast path requirements

NP7 processors can offload IPv4 and IPv6 traffic and NAT64 and NAT46 traffic as well as IPv4 and IPv6 versions of the following traffic types where appropriate:

  • Link aggregation (LAG) (IEEE 802.3ad) traffic and traffic from static redundant interfaces (see Increasing NP6 offloading capacity using link aggregation groups (LAGs)Increasing NP7 offloading capacity using link aggregation groups (LAGs)).
  • TCP, UDP, ICMP, SCTP, GTP-u, and RDP traffic.
  • IPsec VPN traffic terminating on the FortiGate. NP7 processors also offload of IPsec encryption/decryption including:
    • Null, DES, 3DES, AES128, AES192, AES256, AES128-GCM, AES256-GCM, AES-GMAC128, AES-GMAC192, AES-GMAC256 encryption algorithms.
    • Null, MD5, SHA1, SHA256, SHA384, SHA512, HMAC-MD5, SHA2-256 and SHA2-512 authentication algorithms.
  • IPsec traffic that passes through a FortiGate without being unencrypted.
  • Anomaly-based intrusion prevention, checksum offload, and packet defragmentation.
  • IPIP tunneling (also called IP in IP tunneling), SIT tunneling, and IPv6 tunneling.
  • Multicast traffic (including Multicast over IPsec).
  • CAPWAP and wireless bridge traffic tunnel encapsulation to enable line rate wireless forwarding from FortiAP devices.
  • Virtual switch traffic including MAC management and forwarding, STP, and 802.1x.
  • GTP.
  • VXLAN.
  • CAPWAP and VXLAN over IPsec.
  • Fragmented packets (if the packet has been fragmented into two packets (see Reassembling and offloading fragmented packets).
  • Traffic shaping and priority queuing including:
    • Shared and per IP traffic shaping.
    • Interface in bandwidth and out bandwidth traffic shaping.
  • QoS.
  • Syn proxying.
  • DNS session helper.
  • Inter-VDOM link traffic.
  • Traffic over a loopback interface (including IPsec traffic terminated by the FortiGate). For information about using loopback interfaces, see the Fortinet KB article: Technical Tip : Configuring and using a loopback interface on a FortiGate.

Sessions that are offloaded must be fast path ready. For a session to be fast path ready it must meet the following criteria:

  • Layer 2 type/length must be 0x0800 for IPv4 or 0x86dd for IPv6 (IEEE 802.1q VLAN specification is supported).
  • Layer 3 protocol can be IPv4 or IPv6.
  • Layer 4 protocol can be UDP, TCP, ICMP, or SCTP.
  • In most cases, Layer 3 / Layer 4 header or content modification sessions that require a session helper can be offloaded.
  • NTurbo sessions can be offloaded if they are accepted by firewall policies that include IPS, Application Control, CASI, flow-based antivirus, or flow-based web filtering.

Offloading application layer content modification is not supported. This means that sessions are not offloaded if they are accepted by firewall policies that include proxy-based virus scanning, proxy-based web filtering, DNS filtering, DLP, Anti-Spam, VoIP, ICAP, Web Application Firewall, or Proxy options.

Note

If you disable anomaly checks by Intrusion Prevention (IPS), you can still enable hardware accelerated anomaly checks using the fp-anomaly field of the config system interface CLI command. See Configuring individual NP6 processors.

If a session is not fast path ready, the FortiGate will not send the session key or IPsec SA key to the NP7 processor. Without the session key, all session key lookup by a network processor for incoming packets of that session fails, causing all session packets to be sent to the main processing resources, and processed at normal speeds.

If a session is fast path ready, the FortiGate sends the session key or IPsec SA key to the network processor. Session key or IPsec SA key lookups then succeed for subsequent packets from the known session or IPsec SA.

NP7 session fast path requirements

NP7 processors can offload IPv4 and IPv6 traffic and NAT64 and NAT46 traffic as well as IPv4 and IPv6 versions of the following traffic types where appropriate:

  • Link aggregation (LAG) (IEEE 802.3ad) traffic and traffic from static redundant interfaces (see Increasing NP6 offloading capacity using link aggregation groups (LAGs)Increasing NP7 offloading capacity using link aggregation groups (LAGs)).
  • TCP, UDP, ICMP, SCTP, GTP-u, and RDP traffic.
  • IPsec VPN traffic terminating on the FortiGate. NP7 processors also offload of IPsec encryption/decryption including:
    • Null, DES, 3DES, AES128, AES192, AES256, AES128-GCM, AES256-GCM, AES-GMAC128, AES-GMAC192, AES-GMAC256 encryption algorithms.
    • Null, MD5, SHA1, SHA256, SHA384, SHA512, HMAC-MD5, SHA2-256 and SHA2-512 authentication algorithms.
  • IPsec traffic that passes through a FortiGate without being unencrypted.
  • Anomaly-based intrusion prevention, checksum offload, and packet defragmentation.
  • IPIP tunneling (also called IP in IP tunneling), SIT tunneling, and IPv6 tunneling.
  • Multicast traffic (including Multicast over IPsec).
  • CAPWAP and wireless bridge traffic tunnel encapsulation to enable line rate wireless forwarding from FortiAP devices.
  • Virtual switch traffic including MAC management and forwarding, STP, and 802.1x.
  • GTP.
  • VXLAN.
  • CAPWAP and VXLAN over IPsec.
  • Fragmented packets (if the packet has been fragmented into two packets (see Reassembling and offloading fragmented packets).
  • Traffic shaping and priority queuing including:
    • Shared and per IP traffic shaping.
    • Interface in bandwidth and out bandwidth traffic shaping.
  • QoS.
  • Syn proxying.
  • DNS session helper.
  • Inter-VDOM link traffic.
  • Traffic over a loopback interface (including IPsec traffic terminated by the FortiGate). For information about using loopback interfaces, see the Fortinet KB article: Technical Tip : Configuring and using a loopback interface on a FortiGate.

Sessions that are offloaded must be fast path ready. For a session to be fast path ready it must meet the following criteria:

  • Layer 2 type/length must be 0x0800 for IPv4 or 0x86dd for IPv6 (IEEE 802.1q VLAN specification is supported).
  • Layer 3 protocol can be IPv4 or IPv6.
  • Layer 4 protocol can be UDP, TCP, ICMP, or SCTP.
  • In most cases, Layer 3 / Layer 4 header or content modification sessions that require a session helper can be offloaded.
  • NTurbo sessions can be offloaded if they are accepted by firewall policies that include IPS, Application Control, CASI, flow-based antivirus, or flow-based web filtering.

Offloading application layer content modification is not supported. This means that sessions are not offloaded if they are accepted by firewall policies that include proxy-based virus scanning, proxy-based web filtering, DNS filtering, DLP, Anti-Spam, VoIP, ICAP, Web Application Firewall, or Proxy options.

Note

If you disable anomaly checks by Intrusion Prevention (IPS), you can still enable hardware accelerated anomaly checks using the fp-anomaly field of the config system interface CLI command. See Configuring individual NP6 processors.

If a session is not fast path ready, the FortiGate will not send the session key or IPsec SA key to the NP7 processor. Without the session key, all session key lookup by a network processor for incoming packets of that session fails, causing all session packets to be sent to the main processing resources, and processed at normal speeds.

If a session is fast path ready, the FortiGate sends the session key or IPsec SA key to the network processor. Session key or IPsec SA key lookups then succeed for subsequent packets from the known session or IPsec SA.