Skip to main content
karlo_mrazovic
karlo_mrazovic
New Member
March 2, 2017
Question

Fortigate 200B - problem with IPsec Hardware Acceleration

  • March 2, 2017
  • 2 replies
  • 8020 views

Hello!

 

I have a problem with IPsec Hardware Acceleration on my Fortigate 200B device (Version: FortiGate-200B v5.2.9,build0736,160906 (GA)). Two FortiGate 200B device are in HA cluster in Active-Active mode and my IPsec tunnel from Central Location to Branch works, but the traffic not offloaded to Network Processor. Same problem occur when I configure IPsec tunnel on FortiGate 200B single device. Port15 are configure for LAN and port16 for WAN network.

Tunnel are configure using "Custom VPN Tunnel (No Template)".

 

Thank you in advance for the help!

 

FGT-200B-1 # sh vpn ipsec phase1-interface config vpn ipsec phase1-interface edit "Branch_VPN" set interface "port16" set local-gw CENTRAL-LOCATION-PUBLIC-IP set keylife 28800 set proposal 3des-md5 aes128-sha1 set dhgrp 5 set remote-gw BRANCH-PUBLIC-IP set psksecret ENC v56zZzqi+xWPgYhGy2XJJE3eeJhwWnBr5YTeHHAiIahMKmGXb0WGYXCMWpvLu2apeJH0RyhdCvBbzl/EB9NozsCNEzERUN0W3byqOGY83xwYR3wPhPv688KQshzJTYanTUiEU4h765RIUSKdj80YTUGMUhh0MEEKupfDUubVtlB/ next end

 

FGT-200B-1 # diagnose vpn ipsec status All ipsec crypto devices in use: NP2-0 null: 0 0 des: 0 0 3des: 0 0 aes: 0 0 aria: 0 0 seed: 0 0 null: 0 0 md5: 0 0 sha1: 0 0 sha256: 0 0 sha384: 0 0 sha512: 0 0 NPU HARDWARE null: 0 0 des: 0 0 3des: 0 0 aes: 0 0 aria: 0 0 seed: 0 0 null: 0 0 md5: 0 0 sha1: 0 0 sha256: 0 0 sha384: 0 0 sha512: 0 0 CP6 null: 0 0 des: 0 0 3des: 11112 4148 aes: 0 0 aria: 0 0 seed: 0 0 null: 0 0 md5: 11112 4148 sha1: 0 0 sha256: 0 0 sha384: 0 0 sha512: 0 0 SOFTWARE: null: 0 0 des: 0 0 3des: 0 0 aes: 0 0 aria: 0 0 seed: 0 0 null: 0 0 md5: 0 0 sha1: 0 0 sha256: 0 0 sha384: 0 0 sha512: 0 0

 

FGT-200B-1 # diagnose vpn tunnel list list all ipsec tunnel in vd 0 ------------------------------------------------------ name=Branch_VPN_VPN ver=1 serial=1 CENTRAL-LOCATION-PUBLIC-IP:0->BRANCH-PUBLIC-IP:0 lgwy=static tun=intf mode=auto bound_if=9 proxyid_num=1 child_num=0 refcnt=40 ilast=3 olast=3 stat: rxp=4151 txp=11123 rxb=551392 txb=723863 dpd: mode=active on=1 idle=5000ms retry=3 count=0 seqno=3269 natt: mode=none draft=0 interval=0 remote_port=0 proxyid=Branch_VPN_ph2 proto=0 sa=1 ref=2 serial=2 src: 0:192.168.5.0/255.255.255.0:0 dst: 0:10.200.1.0/255.255.255.0:0 SA: ref=37 options=0000000e type=00 soft=0 mtu=1446 expire=889/0B replaywin=1024 seqno=16a life: type=01 bytes=0/0 timeout=1749/1800 dec: spi=1e2a1f58 esp=3des key=24 bc4751192de0f258ece9e71ee6f77f753f700555d63aa60f ah=md5 key=16 2b191f2a928f5216a57c280bc24e8611 enc: spi=4989b8c2 esp=3des key=24 5ab8ea4fa68d76104062d6466fc845cea5bc40b741674900 ah=md5 key=16 4481700fff05d01dd5c77dc4b5b44e28 dec:pkts/bytes=124/9752, enc:pkts/bytes=361/43408 npu_flag=20 npu_rgwy=BRANCH-PUBLIC-IP npu_lgwy=CENTRAL-LOCATION-PUBLIC-IP npu_selid=1 dec_npuid=0 enc_npuid=0 FGT-200B-1 # get system npu enc-offload-antireplay: enable dec-offload-antireplay: enable offload-ipsec-host : enable

 

FGT-200B-1 # show firewall policy config firewall policy edit 1 set srcintf "port15" set dstintf "Branch_VPN" set srcaddr "LAN" set dstaddr "LAN_Branch" set action accept set schedule "always" set service "ALL" set logtraffic disable set comments "LAN to LAN_Branch" next edit 2 set srcintf "Branch_VPN" set dstintf "port15" set srcaddr "LAN_Branch" set dstaddr "LAN" set action accept set schedule "always" set service "ALL" set logtraffic disable set comments "LAN_Branch to LAN" next end

 

FGT-200B-1 # show router static config router static edit 1 set gateway PUBLIC-GTW-IP set device "port16" next edit 2 set dst 10.200.1.0 255.255.255.0 set device "Branch_VPN" next end

 

2 replies

ede_pfau
SuperUser
ede_pfau
SuperUser
March 2, 2017

Why do you suspect that IPsec traffic is not offloaded?

Counters of CP6 show that 3DES and MD5 are handled by the ASIC.

romanr
romanr
New Member
March 2, 2017

Hey,

 

I just did lookup a 200B running a similar configuration where NPU offloading works fine.

 

The only difference from your config seems to be, that we did not set the "local-gw" - because we run it from the main interface ip and not from an alias. And it is 5.2.10 but I know, this worked since 4.2 or 4.3... and it is full GB Ethernet encryption, we would have noticed, if offloading did not work.

 

Do you have the tunnel on a different ip, than your main interface ip? If not, the you can unset this parameter and see if this changes something.

 

Br,Roman

 

Proper NP offloading should bring counters like this:

 

ZZZ_FGT_02 (Firewall) #  diagnose vpn ipsec status All ipsec crypto devices in use: NP2-0         null:   0       0         des:    0       0         3des:   0       0         aes:    370829448155    0         aria:   0       0         seed:   0       0         null:   0       0         md5:    0       0         sha1:   370829448155    0         sha256: 0       0         sha384: 0       0         sha512: 0       0 NPU HARDWARE         null:   0       0         des:    0       0         3des:   0       0         aes:    400447258       0         aria:   0       0         seed:   0       0         null:   0       0         md5:    0       0         sha1:   400447258       0         sha256: 0       0         sha384: 0       0         sha512: 0       0 CP6         null:   0       0         des:    0       0         3des:   0       0         aes:    978     8525         aria:   0       0         seed:   0       0         null:   0       0         md5:    0       0         sha1:   978     8525         sha256: 0       0         sha384: 0       0         sha512: 0       0 SOFTWARE:         null:   0       0         des:    0       0         3des:   0       0         aes:    1010784 2374057         aria:   0       0         seed:   0       0         null:   0       0         md5:    0       0         sha1:   0       0         sha256: 1010784 2374057         sha384: 0       0         sha512: 0       0

ede_pfau
SuperUser
ede_pfau
SuperUser
April 6, 2017

IPsec traffic acceleration can be handled by the NP (here: NP2) and/or the CP (here: CP6) ASICs.

 

The CP processes DES/3DES/AES encryption and decryption, random number generation, hash algorithms (MD5, SHA1) and more. The examples listed refer to the CP6.

 

Traffic handling is done in the NP. The 200B has 4 NP-accelerated ports (9,10,11,12).

 

There are a number of conditions under which ASIC acceleration is disabled:

- in a policy: applying content inspection (AV, IPS, AppControl,...)

- in a policy: "set auto-asic-offload disable"

- in an IPsec phase1: "set npu-offload disable"

- configuring sFlow or NetFlow on a port

- using a port in a software switch (!)

- "config system global: set check-protocol-header strict" (!)

 

You wonder why acceleration is indeed working in most cases...

The definitive reference on this subject is

"FortiOS Handbook - Hardware Acceleration"

http://docs.fortinet.com/uploaded/files/2151/fortigate-hardware-accel-528.pdf

 

HTH.

Terms & ConditionsAccessibility statement