Description This article describes a script for automatically
compressing FSSO Collector Agent's debug logs for the purposes of
extending the log coverage and decreasing the total log size on disk,
and provides example guidelines for implementing it....
Description This article describes how to configure automation stitches
to update DNS records hosted in Cloudflare upon DHCP lease renewal or
PPPoE (re)connection, effectively creating a dynamic DNS (DDNS) setup.
Scope This guide applies to FortiGate...
Description This article discusses the details of the static DNS
filter's matching logic, with examples provided to illustrate the
behavior. Scope The DNS filter operates only on DNS traffic and filters
only domain names. If it is wanted to take spec...
Description This article describes how to configure a webhook automation
stitch that posts a message into a chosen Discord channel when the
stitch is triggered. Scope This guide is applicable to any FortiOS
version that supports webhook automation ac...
DescriptionAfter creating a new DLP sensor by cloning an existing one,
changing the file-type filter on one changes the other as
well.SolutionThis happens because the file-type filters are separate
objects referenced by number in the sensor’s configu...
You should review the SAML response when it is received by the FortiGate
from the IdP, and check if it contains the group's UUID as expected.
enable samld debug output: di de app saml -1 di de app sslvpn -1 di de
enable Reproduce the authentication a...
Not possible. FortiGates are authenticated by their Fortinet-issued
certificate when connecting to that server, but FAC cannot be configured
to use a client-cert in SMTP configs currently.
Yep, you certainly can! Just switch off the "NAT" toggle in the NAT
policy. And you're also correct about the matching order, top->down,
first valid match wins.
This is automatic, and not configurable. It is also worth pointing out
that this is a point-to-point L3 link, so the gateway is essentially
meaningless. Is it actually causing any functional issues (if yes, let's
discuss those), or is this only a cos...
You will likely need to enable logging of "invalid packets" first:
config log setting set log-invalid-packet enable end After that, you
should see this attempt logged in the relevant traffic log (likely
Forward, unless the destination is an IP owned ...
