Description This article describes how to find FortiGate AMIs in AWS
using the CLI. Scope FortiGates in AWS. Solution When deploying
FortiGate in AWS, finding the correct AMIs can be challenging,
especially when using Terraform. The most efficient wa...
Description This article describes how some local-in policies are
missing after upgrading to v7.4.6 or later because of new features.
Scope FortiGate v7.4.6, v7.6.1. Solution In the previous version: fgt #
config firewall local-in-policy fgt (local-i...
Description This article explains how FortiSASE handles route processing
in scenarios where SSLVPN subnets overlap with SPA BGP routes. Scope
FortiSASE. Solution In FortiSASE, the IPAM configuration can be enabled:
Region IP addresses A FortiSASE ins...
Description This article describes how to add subnets bypass in the
FortiSASE. Scope FortiSASE. Solution The FortiSASE default route goes to
SIA, but in the below situation: The PC IP address is 192.168.1.1/24,
while the printer IP address is 192.168...
Description This article explains how to configure the connectivity from
an HA mgmt and loopback interface to an SNMP Server. Scope FortiGate.
Solution In FortiGate SNMP configuration, the ha-redirect needs to be
enabled so that can reach the HA mgmt...
https://docs.fortinet.com/document/fortigate/6.2.0/cookbook/724772/ssl-vpn-multi-realm
This is the realm config example. The purpose of the realm here is to
allow user login from different channels. You can apply with different
portals that match dif...
Does a realm + portal help in your case? If with no-domain PC, try
https://wanip/byod byod is your new realm that also matches LDAP user
but no registry key check. The new portal can help to achieve limited
access and a different IP address.
