Hi community,I have the following VoIP setup:Avaya IP Office v2 ---
FG-80F --- ISP1 / ISP2 (SD-WAN)My goal is to configure a simple
failover, where the FortiGate automatically switches to the secondary
ISP if the primary link goes down.However, I’m r...
Hello everyone,I have a network that was configured a few years ago with
a FortiGate (FG) using a "hardware switch" on ports 1, 2, and 3. The
setup is as follows:"internal1" interface:Contains three VLANs:VLAN 1:
Used as the core VLAN (I know this is...
Hello, I have 2 branches that have 3 links each (this due to the
instability of the ISPs). In both branches I have the same 3 ISPs. 2 of
these ISPs do not offer a public IP, but rather an IP from their LAN
(CGNAT), I want to connect these branches vi...
No, it shouldn’t break after a month — I have it running on a Debian
system for over a year without issues.What can happen, however, is the
following:On Linux, updates to libraries such as libssl, glibc, or
network-manager can break the client and ca...
I solved the issue by assigning priorities to each SD-WAN member/route
(I have 4 routes per site to reach the peer). I only needed to assign
the same priorities on the corresponding routes at both sites, and now
the failovers happen symmetrically.I p...
Hi,I’ve seen similar behavior when configuring HTTPS/HTTP access to
network devices (like switches or VoIP servers). Sometimes, in addition
to MTU/MSS issues, the device itself requires that the client IP
addresses be explicitly allowed (a kind of wh...
Hi,What you’re facing is a NAT loopback (hairpin NAT) issue. When a
client inside the LAN/WLAN tries to reach a local server (your NVR)
using the public IP, the FortiGate doesn’t automatically translate that
traffic back into the LAN. That’s why it o...
Hi Thank you for your clarification. I understand that FortiLink and
local interfaces are usually treated as independent networks.However, in
my lab I was able to successfully extend VLANs (e.g. VLAN 1001–1009)
from a VLAN switch (port1) into the For...
