Post-quantum VPN
Additional key exchanges on IPsec · built Sun Nov 22 2026 04:16 PMWhich 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
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 end | Phase 1 KE | Phase 2 KE | PPK | Other end | Phase 1 KE | Phase 2 KE | PPK | IKE / DH | Post-quantum |
|---|---|---|---|---|---|---|---|---|---|
| Atlanta to-chicago | — | — | — | Chicago to-atlanta | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware first – needs FortiOS 7.6.1 Boston: FortiOS 7.4.8; Chicago: FortiOS 7.4.8 |
| Boston to-dallas | — | — | — | Dallas to-boston | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware first – needs FortiOS 7.6.1 Charlotte: FortiOS 7.4.8; Chicago: FortiOS 7.4.8 |
| Chicago to-dallas | — | — | — | Dallas to-chicago | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware first – needs FortiOS 7.6.1 Chicago: FortiOS 7.4.8; Dallas: FortiOS 7.2.4 |
| Chicago to-denver | — | — | — | Denver to-chicago | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware first – needs FortiOS 7.6.1 Chicago: FortiOS 7.4.8; Denver: FortiOS 7.4.8 |
| Chicago to-detroit | — | — | — | Detroit to-chicago | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware first – needs FortiOS 7.6.1 Chicago: FortiOS 7.4.8; Detroit: FortiOS 7.4.8 |
| Chicago to-houston | — | — | — | Houston to-chicago | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware first – needs FortiOS 7.6.1 Chicago: FortiOS 7.4.8; Miami: FortiOS 7.4.8 |
| Chicago to-minneapolis | — | — | — | Minneapolis to-chicago | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware first – needs FortiOS 7.6.1 Chicago: FortiOS 7.4.8; Philadelphia: FortiOS 7.4.8 |
| Chicago to-phoenix | — | — | — | Phoenix to-chicago | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware first – needs FortiOS 7.6.1 Chicago: FortiOS 7.4.8; Phoenix: FortiOS 7.4.8 |
| Chicago to-seattle | — | — | — | Seattle to-chicago | — | — | — | IKEv2 · DH 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 14 | Firmware 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 5 | IKEv1 – 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).
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.
| Site | Tunnel | Configured | Negotiated (live SA) |
|---|---|---|---|
| Atlanta | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Atlanta | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Azure East | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Azure East | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Azure West | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Azure West | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Boston | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Boston | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Boston | to-dallas | PQ no · PPK no | PQC-KEM no · PPK no |
| Charlotte | to-charlotte-ot | PQ no · PPK no | PQC-KEM no · PPK no |
| Charlotte | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Charlotte | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Charlotte OT | to-charlotte | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-atlanta | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-atlanta-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-azure-east | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-azure-east-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-azure-west | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-azure-west-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-boston | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-boston-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-charlotte | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-charlotte-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-dallas | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-dallas-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-denver | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-denver-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-detroit | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-detroit-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-houston | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-houston-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-losangeles | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-losangeles-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-miami | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-miami-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-minneapolis | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-minneapolis-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-newyork | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-newyork-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-philadelphia | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-philadelphia-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-phoenix | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-phoenix-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-seattle | PQ no · PPK no | PQC-KEM no · PPK no |
| Chicago | to-seattle-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Dallas | to-boston | PQ no · PPK no | PQC-KEM no · PPK no |
| Dallas | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Dallas | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Denver | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Denver | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Detroit | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Detroit | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Detroit | to-detroit-ot | PQ no · PPK no | PQC-KEM no · PPK no |
| Detroit OT | to-detroit | PQ no · PPK no | PQC-KEM no · PPK no |
| Houston | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Houston | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Houston | to-houston-ot | PQ no · PPK no | PQC-KEM no · PPK no |
| Houston OT | to-houston | PQ no · PPK no | PQC-KEM no · PPK no |
| Los Angeles | to-chicago | PQ no · PPK no | PQC-KEM — · PPK — |
| Los Angeles | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Miami | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Miami | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Minneapolis | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Minneapolis | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| New York | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| New York | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Philadelphia | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Philadelphia | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Phoenix | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Phoenix | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
| Seattle | to-chicago | PQ no · PPK no | PQC-KEM no · PPK no |
| Seattle | to-chicago-b | PQ no · PPK no | PQC-KEM no · PPK no |
Certificate algorithms
Local certificate Algorithm / Signature when FortiOS prints them. ML-DSA is flagged when present.
| Site | Certificate | Algorithm | Note |
|---|---|---|---|
| Atlanta | Fortinet_Factory | sha256WithRSAEncryption | — |
| Atlanta | Northline-Mgmt | sha256WithRSAEncryption | — |
| Atlanta | Northline-Inspect-CA | sha384WithRSAEncryption | — |
| Azure East | Fortinet_Factory | sha256WithRSAEncryption | — |
| Azure East | Northline-Mgmt | sha256WithRSAEncryption | — |
| Azure West | Fortinet_Factory | sha256WithRSAEncryption | — |
| Azure West | Northline-Mgmt | sha256WithRSAEncryption | — |
| Boston | Fortinet_Factory | sha256WithRSAEncryption | — |
| Boston | Northline-Mgmt | sha256WithRSAEncryption | — |
| Charlotte | Fortinet_Factory | sha256WithRSAEncryption | — |
| Charlotte | Northline-Mgmt | sha256WithRSAEncryption | — |
| Charlotte | Northline-Inspect-CA | sha384WithRSAEncryption | — |
| Charlotte OT | Fortinet_Factory | sha256WithRSAEncryption | — |
| Charlotte OT | Northline-Mgmt | sha256WithRSAEncryption | — |
| Chicago | Fortinet_Factory | sha256WithRSAEncryption | — |
| Chicago | Northline-Mgmt | sha256WithRSAEncryption | — |
| Chicago | Northline-Inspect-CA | sha384WithRSAEncryption | — |
| Chicago | Northline-VPN | sha256WithRSAEncryption | — |
| Chicago | Northline-Web | ecdsa-with-SHA384 | — |
| Chicago | Northline-Portal | sha256WithRSAEncryption | — |
| Dallas | Fortinet_Factory | sha256WithRSAEncryption | — |
| Dallas | Northline-Mgmt | sha256WithRSAEncryption | — |
| Dallas | Northline-Inspect-CA | sha384WithRSAEncryption | — |
| Dallas | northline-vpn | sha256WithRSAEncryption | — |
| Dallas | retired-vpn | sha1WithRSAEncryption | — |
| Denver | Fortinet_Factory | sha256WithRSAEncryption | — |
| Denver | Northline-Mgmt | sha256WithRSAEncryption | — |
| Denver | Northline-Inspect-CA | sha384WithRSAEncryption | — |
| Detroit | Fortinet_Factory | sha256WithRSAEncryption | — |
| Detroit | Northline-Mgmt | sha256WithRSAEncryption | — |
| Detroit | Northline-Inspect-CA | sha384WithRSAEncryption | — |
| Detroit OT | Fortinet_Factory | sha256WithRSAEncryption | — |
| Detroit OT | Northline-Mgmt | sha256WithRSAEncryption | — |
| Houston | Fortinet_Factory | sha256WithRSAEncryption | — |
| Houston | Northline-Mgmt | sha256WithRSAEncryption | — |
| Houston | Northline-Inspect-CA | sha384WithRSAEncryption | — |
| Houston | Northline-VPN | sha256WithRSAEncryption | — |
| Houston | Houston-MES | sha1WithRSAEncryption | — |
| Houston OT | Fortinet_Factory | sha256WithRSAEncryption | — |
| Houston OT | Northline-Mgmt | sha256WithRSAEncryption | — |
| Los Angeles | Fortinet_Factory | sha256WithRSAEncryption | — |
| Los Angeles | Northline-Mgmt | sha256WithRSAEncryption | — |
| Miami | Fortinet_Factory | sha256WithRSAEncryption | — |
| Miami | Northline-Mgmt | sha256WithRSAEncryption | — |
| Minneapolis | Fortinet_Factory | sha256WithRSAEncryption | — |
| Minneapolis | Northline-Mgmt | sha256WithRSAEncryption | — |
| New York | Fortinet_Factory | sha256WithRSAEncryption | — |
| New York | Northline-Mgmt | sha256WithRSAEncryption | — |
| Philadelphia | Fortinet_Factory | sha256WithRSAEncryption | — |
| Philadelphia | Northline-Mgmt | sha256WithRSAEncryption | — |
| Phoenix | Fortinet_Factory | sha256WithRSAEncryption | — |
| Phoenix | Northline-Mgmt | sha256WithRSAEncryption | — |
| Seattle | Fortinet_Factory | sha256WithRSAEncryption | — |
| Seattle | Northline-Mgmt | sha256WithRSAEncryption | — |
| Seattle | Northline-Inspect-CA | sha384WithRSAEncryption | — |
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.
| Site | SSH |
|---|---|
| Atlanta | not collected |
| Azure East | not collected |
| Azure West | not collected |
| Boston | not collected |
| Charlotte | not collected |
| Charlotte OT | not collected |
| Chicago | not collected |
| Dallas | not collected |
| Denver | not collected |
| Detroit | not collected |
| Detroit OT | not collected |
| Houston | not collected |
| Houston OT | not collected |
| Los Angeles | not collected |
| Miami | not collected |
| Minneapolis | not collected |
| New York | not collected |
| Philadelphia | not collected |
| Phoenix | not collected |
| Seattle | not collected |
By site
AtlantaFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Atlanta | 7.4.8 before 7.6.1 | 2 | 0 |
Azure EastFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Azure East | 7.4.8 before 7.6.1 | 2 | 0 |
Azure WestFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Azure West | 7.4.8 before 7.6.1 | 2 | 0 |
BostonFortiOS 7.4.8 · before 7.6.1 · 3 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Boston | 7.4.8 before 7.6.1 | 3 | 0 |
CharlotteFortiOS 7.4.8 · before 7.6.1 · 3 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Charlotte | 7.4.8 before 7.6.1 | 3 | 0 |
Charlotte OTFortiOS 7.4.8 · before 7.6.1 · 1 tunnel · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Charlotte OT | 7.4.8 before 7.6.1 | 1 | 0 |
ChicagoFortiOS 7.4.8 · before 7.6.1 · 32 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Chicago | 7.4.8 before 7.6.1 | 32 | 0 |
DallasFortiOS 7.2.4 · before 7.6.1 · 3 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Dallas | 7.2.4 before 7.6.1 | 3 | 0 |
DenverFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Denver | 7.4.8 before 7.6.1 | 2 | 0 |
DetroitFortiOS 7.4.8 · before 7.6.1 · 3 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Detroit | 7.4.8 before 7.6.1 | 3 | 0 |
Detroit OTFortiOS 7.4.8 · before 7.6.1 · 1 tunnel · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Detroit OT | 7.4.8 before 7.6.1 | 1 | 0 |
HoustonFortiOS 7.4.8 · before 7.6.1 · 3 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Houston | 7.4.8 before 7.6.1 | 3 | 0 |
Houston OTFortiOS 7.4.8 · before 7.6.1 · 1 tunnel · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Houston OT | 7.4.8 before 7.6.1 | 1 | 0 |
Los AngelesFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Los Angeles | 7.4.8 before 7.6.1 | 2 | 0 |
MiamiFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Miami | 7.4.8 before 7.6.1 | 2 | 0 |
MinneapolisFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Minneapolis | 7.4.8 before 7.6.1 | 2 | 0 |
New YorkFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| New York | 7.4.8 before 7.6.1 | 2 | 0 |
PhiladelphiaFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Philadelphia | 7.4.8 before 7.6.1 | 2 | 0 |
PhoenixFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Phoenix | 7.4.8 before 7.6.1 | 2 | 0 |
SeattleFortiOS 7.4.8 · before 7.6.1 · 2 tunnels · 0 with post-quantum
| Site | FortiGate firmware | IPsec tunnels | With post-quantum |
|---|---|---|---|
| Seattle | 7.4.8 before 7.6.1 | 2 | 0 |