I have two FG61Fs running 7.4.6 with a Dial-Up IPSec VPN between them. I
recently added a second WAN connection for failover purposes. I use the
link monitor to kill the static route with higher priority when my
primary goes down. That works great. F...
I'm on a FortiGate 61F running 7.4.3. I have a VoIP PBX behind it using
SIP Trunks. When this was all set up originally I only had a single WAN
connection (connected to WAN 2), and I did have to disable the SIP ALG
helper in order to resolve dropped ...
Hello,I am trying to set up automatic failover wan using link-monitor
and not SDWAN. Before I even get as far setting up the link-monitor I am
running into an issue. My primary is wan2 and backup is wan1. I have
tried setting the static route for the...
I have a FGT40F (behind NAT) at a remote office and a FGT61F at my home
office with an IPsec tunnel between them. Both were on 7.4.3 and all
good. I updated the 40F to 7.4.4 and now the IPsec VPN will not connect.
I rebooted both ends and tried to en...
I have a FGT61F running 7.4.3 at the home office and another identical
in a remote office. Home office has the static IP. We had a long-term
power outage over the weekend and once it was restored the tunnel will
not come back up. I have rebooted the ...
Interesting Update - This is happening on a 61F running 7.4.3. I ported
the conifg from it over to a 61E running 7.4.6 and I am not having the
SIP ALG issues on that one. I will upgrade the 61F tonight once the
business is closed and see what happens...
I ran the show command there and verified that it looks like you said it
should. HomeOffice (settings) # showconfig system settingsset
default-voip-alg-mode kernel-helper-basedend
Toshi,Thank you! That was it. I disabled default gw and it now works as
expected. I also tried leaving it enabled and entering a higher distance
on the retrieve gw for the backup wan and that worked as well. Thanks
again for all of your help. Really ...
No change. No matter which one has the higher priority, it goes through
wan1 whenever it is connected.It shows wan2 with a * but I get public IP
from wan1 Routing table for VRF=0S* 0.0.0.0/0 [5/0] via 192.168.10.1,
wan2, [1/0] [5/0] via 192.168.21.1,...
Here it is. Weird thing is [both up, working on wan2] and [wan2
restored] look the same, but when [wan2 restored] and I go
whatismyipaddress.com I still see the wan1 IP.