Description This article explains the log rate/log insert speed info in
some FortiAnalyzer CLI commands. Scope FortiAnalyzer. Solution In some
outputs of some FortiAnalyzer CLI commands, there is such log rate info:
diagnose fortilogd lograte last 5 ...
Description This article describes the requirements of a Server
Certificate in an SSL Inspection profile while selecting 'Protecting SSL
Server'. Scope FortiGate. Solution When creating or editing an SSL
Inspection profile, and selecting 'Protecting ...
Description This article describes one scenario (GRE + IPSec) that is
unsupported for NP7 offloading. Scope FortiGate. Solution NP7 offloading
supports the GRE tunnel, including terminating on FortiGate or passing
through FortiGate.NP7 offloading sup...
Description This article explains the behavior of 'Inspect All' in an
SSL/SSH inspection profile. Scope FortiProxy. Solution When creating or
editing an SSL/SSH inspection profile, there is an option called
'Inspect All'. Full SSL Inspection: Perform...
Description This article describes the 'Default Device Selection for
Install' option in ADOM settings while creating or editing one ADOM on
FortiManager. Scope FortiManager. Solution When creating or editing one
ADOM on FortiManager, there is an opti...
Do you have to use IKEv2? For IKEv2, my understanding is that the FGT
will try to match the tunnel from top to bottom in the IKE_SA_INIT
phase. The Peer ID info is in the next phase, called IKE_AUTH. For
IKEv1, the peer ID info is in the very first m...
Again: 1) Did you configure both tunnels as "Aggressive mode"? 2) "ike
V=root:0:TUNNELB: ignoring IKEv2 request, no policy configured"This
message indicates that you have no firewall policies configured for this
tunnel. If possible, please share your...
Hi @ForgetItNet , 1) No need to configure "local ID" for the IPSec VPN
on FGT; 2) Make sure that you are using "aggressive mode" for both IPSec
VPN tunnels. If you still have the issue, please: 1) Provide your FGT
config, or at least, the IPSec VPN t...
Hi @akazemfar , 1) Technically, if the destination LAN network knows how
to return the traffic, no need to enable NAT in the firewall policies
for the IPSec VPN traffic; 2) Double check whether you have any IP Pool
configured with or including 172.16...
