HI All,I'm running into an interesting issue. We have a script in
FortiManager that sets the source-ip of connections to their various
services, Netflow, FSSO, LDAP, etc. However, after updating our
firewalls to 7.2.11, I'm finding that the following...
Question... Is there anything which will alert me when a FortiExtender
is "offline" or unable to be connected to? We have had a couple of
instances lately where our FortiExtenders were needed, but weren't
connecting to either the Fortigate or the cel...
Question, with the new Windows Copilot+ PCs, will there be a version of
Forticlient for Windows on ARM that will also support ZTNA?I have SSL
VPN setup at the moment, so tried using the version of FortiClient from
the Windows Store, but while it conn...
We have a number of FGT devices running on 7.0.14 and all part of
FortiManager, with the basic configurations being pretty much the same.
One of those configurations is to setup AD users as admins based on
LDAP. This process works great for all but 1...
example of what should be in the config:config system netflowconfig
collectorsedit 1set collector-ip <---- my collector addressset
collector-port <----- my collector portset source-ip
$(lan1_ip)nextendend I changed lan1_ip to a new value for the site...
All of the other settings are there, I'm just updating the source-ip for
any service that uses it (FSSO, LDAP, NTP, etc.). All of the other
services take the set source-ip just fine (I can delete the config
system netflow block), it's just netflow th...
I thought the recommendation was to NOT use the same IP ranges because
the two processes that provide the addresses don't talk with each other
and could cause an IP Address conflict between two inbound connections
(one SSLVPN, one L2TP VPN). There wa...
I've been going through different scenarios and will be trying to at
least use Windows Native L2TP at first, followed by using wireguard or
some other product that I can run in my home lab for testing. I did see
in another post that it's possible ARM...
The typical issue I have had with Forticlient not connecting is IPv6
being active on the interface you're using. If it's a wireless
connection, disable IPv6 for that connection and try again. If it's
wired, deactivate it there and see if it works.
