Technical Tip: Understanding the IPsec tunnel SA MTU value
Description
Â
This article describes the IPsec Security Association (SA) MTU displayed by the diagnose commands, distinguishes it from the tunnel interface MTU, and describes the factors that influence its value.
Â
Scope
Â
FortiGate, FortiOS v7.4, v7.6.
Â
Solution
Â
An IPsec tunnel has two separate MTU values:
IPsec Tunnel interface MTU: The MTU assigned to the virtual IPsec network interface.
IPsec Security Association (SA) MTU: The maximum inner IP packet size calculated for a negotiated IPsec SA, taking into account the outer path MTU and IPsec encapsulation overhead.
The MTU field in diagnose vpn tunnel list represents the SA MTU and can differ from the tunnel interface MTU.
Â
Diagnostic command to view IPsec Tunnel interface MTU:
diagnose netlink interface list <tunnel-name>Â
Diagnostic command to view IPsec SA MTU:
diagnose vpn tunnel list name <tunnel-name>Â
Sample output for SA MTU from IPsec site-to-site tunnel between FortiGate devices. Notice the mtu=1458 value for the Phase2 tunnel proxyid=VMto91G:
blackbird-kvm54 # diagnose vpn tunnel list name VMto91G
list ipsec tunnel by names in vd 0
------------------------------------------------------
name=VMto91G ver=2 serial=3 10.109.1.1:0->10.109.1.99:0 nexthop=0.0.0.0 tun_id=10.109.1.99 tun_id6=::10.109.1.99 status=up dst_mtu=1500 weight=1
bound_if=4 real_if=4 lgwy=static/1 tun=intf mode=auto/1 encap=none/552 options[0228]=npu frag-rfc run_state=0 role=primary accept_traffic=1 overlay_id=0
proxyid_num=1 child_num=0 refcnt=5 ilast=80 olast=80 ad=/0
stat: rxp=5 txp=5 rxb=420 txb=420
dpd: mode=on-demand on=1 status=ok idle=20000ms retry=3 count=0 seqno=0
natt: mode=none draft=0 interval=0 remote_port=0
fec: egress=0 ingress=0
proxyid=VMto91G proto=0 sa=1 ref=2 serial=2
src: 0:10.4.1.1-10.4.1.1:0
dst: 0:10.91.1.1-10.91.1.1:0
SA: ref=3 options=30202 type=00 soft=0 mtu=1458 expire=42597/0B replaywin=2048
seqno=6 esn=0 replaywin_lastseq=00000016 qat=0 rekey=0 hash_search_len=1
life: type=01 bytes=0/0 timeout=42901/43200
dec: spi=7cde4b0c esp=null key=0
ah=md5 key=16 72b78e6daa119cbc7b31fe8f2479bc45
enc: spi=bd4eeca6 esp=null key=0
ah=md5 key=16 d90ac62a02acc00e3957c32c6d82dd12
dec:pkts/bytes=5/420, enc:pkts/bytes=5/420
npu_flag=00 npu_rgwy=0.0.0.0:0 npu_lgwy=0.0.0.0:0 npu_selid=0
dec_npuid=0 enc_npuid=0 dec_engid=-1 enc_engid=-1 dec_saidx=-1 enc_saidx=-1Â
Sample output for IPsec Tunnel interface MTU. Note the mtu=1402, which is different from the SA MTU of 1458:
blackbird-kvm54 # diagnose netlink interface list VMto91G
if=VMto91G family=00 type=768 index=42 mtu=1402 link=0 master=0
ref=12 state=start present fw_flags=400 flags=up p2p run noarp multicast
Qdisc=noqueue
stat: rxp=0 txp=0 rxb=0 txb=0 rxe=0 txe=2 rxd=0 txd=0 mc=0 collision=0 @ time=1791308674
re: rxl=0 rxo=0 rxc=0 rxf=0 rxfi=0 rxm=0
te: txa=0 txc=0 txfi=0 txh=0 txw=0
misc rxc=0 txc=0
input_type=0 state=3 arp_entry=0 refcnt=12
blackbird-kvm54 # fnsysctl ifconfig VMto91G
VMto91G Link encap:Unknown
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1402 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:2 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0 Bytes) TX bytes:0 (0 Bytes) Â
The SA MTU depends on the outer path MTU and the overhead introduced by the negotiated Phase 2 algorithms and encapsulation. This overhead includes the outer IP header, a UDP header when NAT-T is active, the ESP header, the initialization vector, padding, the Pad Length and Next Header fields, and the Integrity Check Value.
Â
Related articles:
