Fixing Connectivity After Interface Down/Up (Solved) | Fortigate Firewall | Connection Not Working
In this video, we tackle a common routing issue with FortiGate Firewall, where the connectivity via an interface doesn't restore after the interface goes down and comes back up, unless the FortiGate is rebooted. I'll walk you through the troubleshooting process and show how I fixed the problem using a simple deny policy. Specifically, I configured my FortiGate Firewall with two static routes—one for default WAN traffic and one for a telecom network on internal 2. After internal 2 faced connectivity drops, traffic was incorrectly routed via WAN 1, breaking SIP communication.
Watch to learn how I resolved this by blocking the incorrect route and ensuring the connection restores without rebooting the FortiGate.
If you find this video helpful, don't forget to like, comment, and subscribe!