Hello I created a Performance SLA to monitor the quality of a link to
connect to a specific server on the Internet. The measurement uses
tcp-connect and makes requests to a specific IP and Port. The defined
check interval is 500ms and the time to con...
Hello I am having problems connecting to the FortiGuard servers on a
FortiGate 40f firmware v7.0.13 build0566 (Mature) (HA Cluster). I am
also receiving the message "FortiGate time is out of sync.", I use an
NTP server 200.160.0.8. Images belowFrom F...
Hello I have 3 links on my Fortigate 60F v7.0.13:- 2 WAN interfaces with
manual mode- 1 WAN interface with PPPoE modeI also have an SDWAN rule in
"maximize bandwidth (SLA)" mode with the three links.On my local network
there is a Zabbix server that p...
Hello I'm having problems with local traffic generated by Fortigate and
SDWAN rules. When one of the links that make up our SDWAN goes offline,
I receive the following error message: "unable to connect to
fortisandbox. Either the appliance is not rea...
hi I'm trying to ping 8.8.4.4 from my wan interfaces of my fortigate 40F
(v7.0.13). Interface 'a' can ping correctly but interface 'wan' cannot
reach the destination. Interface 'wan': #execute ping-options source
138.99.23.193 #execute ping 8.8.4.4 P...
I had to manually correct the fortigate date and then it started working
again. The funny thing is that I need to set the correct date so that
fortigate can communicate with the NTP server to retrieve the correct
date.
I do not have 2 IPs configured on my WAN interface. My two WAN
interfaces are PPPOE and receive a public IP from the ISP. FortiGate
should use the WAN IP of one of these interfaces to try to connect to
the FortiGuard servers. This should be automatic...
same behavior that occurs with policy routes. If the PPPOE link goes
down, the packets are automatically redirected to another interface, I
can't force the output through the PPPOE link, not even with a static
route
putting the PPPOE interface gateway in dynamic mode solved the problem
and the route is removed from the routing table when the link goes down.
However, this caused the problem reported in this post: link
