Demo – made-up data. Northline, the sites and the numbers are invented. Notices 3.5 – work in progress
VANTAGENorthline
Collected✕7 sites need attention

Post-quantum VPN

Additional key exchanges on IPsec · built Sun Nov 22 2026 04:16 PM
0 pairs ready to turn on35 firmware first1 on IKEv1 – move first0 where the ends disagree0 done0 to other equipment – check the provider

Which IPsec tunnels add a post-quantum key exchange (ML-KEM) on phase 1 and phase 2, and a post-quantum pre-shared key (PPK), whether both ends agree, and when a live SA is collected – configured versus negotiated. SSL VPN tls-groups, certificate algorithms and SSH kex are listed when present. Session key lines are never shown.

What is read, and what it costs
From show vpn ipsec phase1-interface, show vpn ipsec phase2-interface, get system status, show vpn ssl settings (tls-groups), diagnose vpn ike gateway list (live SA flags only – SK_ lines scrubbed before save), get vpn certificate local details (Algorithm / Signature when printed), and show system ssh-config when collected (optional). FortiOS lists set addke1 to set addke7 and set ppk only when they are set, so a tunnel without them has no post-quantum key exchange. A group written as a number (35, 36, 37) or a name (ml-kem-768) is shown by name. Only IKEv2 can carry an additional key exchange or PPK, and it needs FortiOS 7.6.1 or later at both ends. childless-ike must be enable whenever addke is set. Configured and negotiated stay distinct: a tunnel can offer ML-KEM and still negotiate classical if the peer does not match. Decommissioned (DECOM) and FortiSASE tunnels are left out. A tunnel where the ends disagree, or where addke is set without childless-ike, is also on the Action list. This page does not change a site's colour.

Between your FortiGates

Both ends of a tunnel must offer the same phase 1 and phase 2 additional key exchange, and the same PPK setting. Tunnels are paired by remote gateway, as on the WAN map.

One endPhase 1 KEPhase 2 KEPPKOther endPhase 1 KEPhase 2 KEPPKIKE / DHPost-quantum
Atlanta to-chicago———Chicago to-atlanta———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Atlanta: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Atlanta to-chicago-b———Chicago to-atlanta-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Atlanta: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Azure East to-chicago———Chicago to-azure-east———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Azure East: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Azure East to-chicago-b———Chicago to-azure-east-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Azure East: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Azure West to-chicago———Chicago to-azure-west———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Azure West: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Azure West to-chicago-b———Chicago to-azure-west-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Azure West: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Boston to-chicago———Chicago to-boston———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Boston: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Boston to-chicago-b———Chicago to-boston-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Boston: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Boston to-dallas———Dallas to-boston———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Boston: FortiOS 7.4.8; Dallas: FortiOS 7.2.4
Charlotte to-charlotte-ot———Charlotte OT to-charlotte———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Charlotte: FortiOS 7.4.8; Charlotte OT: FortiOS 7.4.8
Charlotte to-chicago———Chicago to-charlotte———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Charlotte: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Charlotte to-chicago-b———Chicago to-charlotte-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Charlotte: FortiOS 7.4.8; Chicago: FortiOS 7.4.8
Chicago to-dallas———Dallas to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Dallas: FortiOS 7.2.4
Chicago to-dallas-b———Dallas to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Dallas: FortiOS 7.2.4
Chicago to-denver———Denver to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Denver: FortiOS 7.4.8
Chicago to-denver-b———Denver to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Denver: FortiOS 7.4.8
Chicago to-detroit———Detroit to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Detroit: FortiOS 7.4.8
Chicago to-detroit-b———Detroit to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Detroit: FortiOS 7.4.8
Chicago to-houston———Houston to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Houston: FortiOS 7.4.8
Chicago to-houston-b———Houston to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Houston: FortiOS 7.4.8
Chicago to-losangeles-b———Los Angeles to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Los Angeles: FortiOS 7.4.8
Chicago to-miami———Miami to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Miami: FortiOS 7.4.8
Chicago to-miami-b———Miami to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Miami: FortiOS 7.4.8
Chicago to-minneapolis———Minneapolis to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Minneapolis: FortiOS 7.4.8
Chicago to-minneapolis-b———Minneapolis to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Minneapolis: FortiOS 7.4.8
Chicago to-newyork———New York to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; New York: FortiOS 7.4.8
Chicago to-newyork-b———New York to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; New York: FortiOS 7.4.8
Chicago to-philadelphia———Philadelphia to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Philadelphia: FortiOS 7.4.8
Chicago to-philadelphia-b———Philadelphia to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Philadelphia: FortiOS 7.4.8
Chicago to-phoenix———Phoenix to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Phoenix: FortiOS 7.4.8
Chicago to-phoenix-b———Phoenix to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Phoenix: FortiOS 7.4.8
Chicago to-seattle———Seattle to-chicago———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Seattle: FortiOS 7.4.8
Chicago to-seattle-b———Seattle to-chicago-b———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Chicago: FortiOS 7.4.8; Seattle: FortiOS 7.4.8
Detroit to-detroit-ot———Detroit OT to-detroit———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Detroit: FortiOS 7.4.8; Detroit OT: FortiOS 7.4.8
Houston to-houston-ot———Houston OT to-houston———IKEv2 · DH 14Firmware first – needs FortiOS 7.6.1
Houston: FortiOS 7.4.8; Houston OT: FortiOS 7.4.8
Chicago to-losangeles———Los Angeles to-chicago———IKEv2 · DH 14 / IKEv1 · DH 5IKEv1 – move to IKEv2 first

To other equipment

Cloud, partner and dial-up tunnels, and tunnels whose other end was not found: only this end is known.

None.

SSL VPN TLS groups

Agentless / SSL VPN tls-groups from show vpn ssl settings (for example hybrid X25519-MLKEM768).

Sitetls-groups
Chicagosecp256r1 secp384r1 x25519
Houstonsecp256r1 x25519

Configured vs negotiated

Live SA flags from diagnose vpn ike gateway list (PQC-KEM / PPK), next to what phase 1 offers. Key material is never shown.

SiteTunnelConfiguredNegotiated (live SA)
Atlantato-chicagoPQ no · PPK noPQC-KEM no · PPK no
Atlantato-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Azure Eastto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Azure Eastto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Azure Westto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Azure Westto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Bostonto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Bostonto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Bostonto-dallasPQ no · PPK noPQC-KEM no · PPK no
Charlotteto-charlotte-otPQ no · PPK noPQC-KEM no · PPK no
Charlotteto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Charlotteto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Charlotte OTto-charlottePQ no · PPK noPQC-KEM no · PPK no
Chicagoto-atlantaPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-atlanta-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-azure-eastPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-azure-east-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-azure-westPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-azure-west-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-bostonPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-boston-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-charlottePQ no · PPK noPQC-KEM no · PPK no
Chicagoto-charlotte-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-dallasPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-dallas-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-denverPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-denver-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-detroitPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-detroit-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-houstonPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-houston-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-losangelesPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-losangeles-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-miamiPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-miami-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-minneapolisPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-minneapolis-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-newyorkPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-newyork-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-philadelphiaPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-philadelphia-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-phoenixPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-phoenix-bPQ no · PPK noPQC-KEM no · PPK no
Chicagoto-seattlePQ no · PPK noPQC-KEM no · PPK no
Chicagoto-seattle-bPQ no · PPK noPQC-KEM no · PPK no
Dallasto-bostonPQ no · PPK noPQC-KEM no · PPK no
Dallasto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Dallasto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Denverto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Denverto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Detroitto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Detroitto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Detroitto-detroit-otPQ no · PPK noPQC-KEM no · PPK no
Detroit OTto-detroitPQ no · PPK noPQC-KEM no · PPK no
Houstonto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Houstonto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Houstonto-houston-otPQ no · PPK noPQC-KEM no · PPK no
Houston OTto-houstonPQ no · PPK noPQC-KEM no · PPK no
Los Angelesto-chicagoPQ no · PPK noPQC-KEM — · PPK —
Los Angelesto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Miamito-chicagoPQ no · PPK noPQC-KEM no · PPK no
Miamito-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Minneapolisto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Minneapolisto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
New Yorkto-chicagoPQ no · PPK noPQC-KEM no · PPK no
New Yorkto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Philadelphiato-chicagoPQ no · PPK noPQC-KEM no · PPK no
Philadelphiato-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Phoenixto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Phoenixto-chicago-bPQ no · PPK noPQC-KEM no · PPK no
Seattleto-chicagoPQ no · PPK noPQC-KEM no · PPK no
Seattleto-chicago-bPQ no · PPK noPQC-KEM no · PPK no

Certificate algorithms

Local certificate Algorithm / Signature when FortiOS prints them. ML-DSA is flagged when present.

SiteCertificateAlgorithmNote
AtlantaFortinet_Factorysha256WithRSAEncryption—
AtlantaNorthline-Mgmtsha256WithRSAEncryption—
AtlantaNorthline-Inspect-CAsha384WithRSAEncryption—
Azure EastFortinet_Factorysha256WithRSAEncryption—
Azure EastNorthline-Mgmtsha256WithRSAEncryption—
Azure WestFortinet_Factorysha256WithRSAEncryption—
Azure WestNorthline-Mgmtsha256WithRSAEncryption—
BostonFortinet_Factorysha256WithRSAEncryption—
BostonNorthline-Mgmtsha256WithRSAEncryption—
CharlotteFortinet_Factorysha256WithRSAEncryption—
CharlotteNorthline-Mgmtsha256WithRSAEncryption—
CharlotteNorthline-Inspect-CAsha384WithRSAEncryption—
Charlotte OTFortinet_Factorysha256WithRSAEncryption—
Charlotte OTNorthline-Mgmtsha256WithRSAEncryption—
ChicagoFortinet_Factorysha256WithRSAEncryption—
ChicagoNorthline-Mgmtsha256WithRSAEncryption—
ChicagoNorthline-Inspect-CAsha384WithRSAEncryption—
ChicagoNorthline-VPNsha256WithRSAEncryption—
ChicagoNorthline-Webecdsa-with-SHA384—
ChicagoNorthline-Portalsha256WithRSAEncryption—
DallasFortinet_Factorysha256WithRSAEncryption—
DallasNorthline-Mgmtsha256WithRSAEncryption—
DallasNorthline-Inspect-CAsha384WithRSAEncryption—
Dallasnorthline-vpnsha256WithRSAEncryption—
Dallasretired-vpnsha1WithRSAEncryption—
DenverFortinet_Factorysha256WithRSAEncryption—
DenverNorthline-Mgmtsha256WithRSAEncryption—
DenverNorthline-Inspect-CAsha384WithRSAEncryption—
DetroitFortinet_Factorysha256WithRSAEncryption—
DetroitNorthline-Mgmtsha256WithRSAEncryption—
DetroitNorthline-Inspect-CAsha384WithRSAEncryption—
Detroit OTFortinet_Factorysha256WithRSAEncryption—
Detroit OTNorthline-Mgmtsha256WithRSAEncryption—
HoustonFortinet_Factorysha256WithRSAEncryption—
HoustonNorthline-Mgmtsha256WithRSAEncryption—
HoustonNorthline-Inspect-CAsha384WithRSAEncryption—
HoustonNorthline-VPNsha256WithRSAEncryption—
HoustonHouston-MESsha1WithRSAEncryption—
Houston OTFortinet_Factorysha256WithRSAEncryption—
Houston OTNorthline-Mgmtsha256WithRSAEncryption—
Los AngelesFortinet_Factorysha256WithRSAEncryption—
Los AngelesNorthline-Mgmtsha256WithRSAEncryption—
MiamiFortinet_Factorysha256WithRSAEncryption—
MiamiNorthline-Mgmtsha256WithRSAEncryption—
MinneapolisFortinet_Factorysha256WithRSAEncryption—
MinneapolisNorthline-Mgmtsha256WithRSAEncryption—
New YorkFortinet_Factorysha256WithRSAEncryption—
New YorkNorthline-Mgmtsha256WithRSAEncryption—
PhiladelphiaFortinet_Factorysha256WithRSAEncryption—
PhiladelphiaNorthline-Mgmtsha256WithRSAEncryption—
PhoenixFortinet_Factorysha256WithRSAEncryption—
PhoenixNorthline-Mgmtsha256WithRSAEncryption—
SeattleFortinet_Factorysha256WithRSAEncryption—
SeattleNorthline-Mgmtsha256WithRSAEncryption—
SeattleNorthline-Inspect-CAsha384WithRSAEncryption—

SSH key exchange

Admin SSH algorithms from show system ssh-config when that optional command was collected. PQ is only shown when a known post-quantum kex token appears – classical dumps stay classical.

SiteSSH
Atlantanot collected
Azure Eastnot collected
Azure Westnot collected
Bostonnot collected
Charlottenot collected
Charlotte OTnot collected
Chicagonot collected
Dallasnot collected
Denvernot collected
Detroitnot collected
Detroit OTnot collected
Houstonnot collected
Houston OTnot collected
Los Angelesnot collected
Miaminot collected
Minneapolisnot collected
New Yorknot collected
Philadelphianot collected
Phoenixnot collected
Seattlenot collected

By site

AtlantaFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Atlanta7.4.8 before 7.6.120
Azure EastFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Azure East7.4.8 before 7.6.120
Azure WestFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Azure West7.4.8 before 7.6.120
BostonFortiOS 7.4.8 · before 7.6.1 · 3 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Boston7.4.8 before 7.6.130
CharlotteFortiOS 7.4.8 · before 7.6.1 · 3 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Charlotte7.4.8 before 7.6.130
Charlotte OTFortiOS 7.4.8 · before 7.6.1 · 1 tunnel · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Charlotte OT7.4.8 before 7.6.110
ChicagoFortiOS 7.4.8 · before 7.6.1 · 32 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Chicago7.4.8 before 7.6.1320
DallasFortiOS 7.2.4 · before 7.6.1 · 3 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Dallas7.2.4 before 7.6.130
DenverFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Denver7.4.8 before 7.6.120
DetroitFortiOS 7.4.8 · before 7.6.1 · 3 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Detroit7.4.8 before 7.6.130
Detroit OTFortiOS 7.4.8 · before 7.6.1 · 1 tunnel · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Detroit OT7.4.8 before 7.6.110
HoustonFortiOS 7.4.8 · before 7.6.1 · 3 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Houston7.4.8 before 7.6.130
Houston OTFortiOS 7.4.8 · before 7.6.1 · 1 tunnel · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Houston OT7.4.8 before 7.6.110
Los AngelesFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Los Angeles7.4.8 before 7.6.120
MiamiFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Miami7.4.8 before 7.6.120
MinneapolisFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Minneapolis7.4.8 before 7.6.120
New YorkFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
New York7.4.8 before 7.6.120
PhiladelphiaFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Philadelphia7.4.8 before 7.6.120
PhoenixFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Phoenix7.4.8 before 7.6.120
SeattleFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
SiteFortiGate firmwareIPsec tunnelsWith post-quantum
Seattle7.4.8 before 7.6.120

Backups

philadelphia: no backup for 2 days – the FortiGate did not answer (site unreachable). See Change → Backups.