Fortinet white logo
Fortinet white logo

SPA with a FortiGate SD-WAN Deployment Guide

Verifying private access traffic from hubs

Verifying private access traffic from hubs

Note

Verifying private access traffic from SPA hubs to FortiSASE remote users depends on a private access policy being defined in the From Hub direction on a FortiSASE instance with the remote VPN user identification selected availability feature. See Remote VPN user identification.

In the FortiSASE portal, you can verify traffic from SPA hub sources (local networks or connected spokes) has reached FortiSASE remote user destinations through these methods:

  • From Analytics > Logs > Traffic by viewing All Internet and Private Access Traffic or Private Access Traffic (From Hubs)
  • From Dashboard > FortiView > Sources, Dashboard > FortiView > Destinations, or Dashboard > FortiView > Policies and filtering on the remote VPN user destination IP address

Verifying private access traffic from hubs

Verifying private access traffic from hubs

Note

Verifying private access traffic from SPA hubs to FortiSASE remote users depends on a private access policy being defined in the From Hub direction on a FortiSASE instance with the remote VPN user identification selected availability feature. See Remote VPN user identification.

In the FortiSASE portal, you can verify traffic from SPA hub sources (local networks or connected spokes) has reached FortiSASE remote user destinations through these methods:

  • From Analytics > Logs > Traffic by viewing All Internet and Private Access Traffic or Private Access Traffic (From Hubs)
  • From Dashboard > FortiView > Sources, Dashboard > FortiView > Destinations, or Dashboard > FortiView > Policies and filtering on the remote VPN user destination IP address