Fortigate Version 7.2.10 We have several internet facing devices that
use virtual IPs and a phone system that uses SIP which has a one-to-one
IP assigned to it. We have two ISPs with link-monitor setup. To match
our new locations, we are attempting t...
Hi, I'm sure this is something I'm overlooking but it does have me a
little confused. My Fortigates are still in a lab setting set to roll
out to production in the coming weeks. Currently I have two Fortigates
with private IP on WAN ports 192.168.2.1...
I've setup ADVPN using BGP on loopback design with SDWAN. Traffic flows
and failover to another link when when it disconnected on all devices.
Right now I have 1 hub and 2 spoke. I can steer traffic from spoke 1 out
the correct interface - but the AD...
Hopefully someone can help with this as my knowledge with BGP, ADVPN,
Hub\Spoke is not strong - but it is growing. We plan on having 4 spoke
devices and 1 hub device all with 2 wan interfaces (if we get things
working we may introduce a second Fortig...
Hi, We are planning on rolling out a handful of Fortigates 90G -
currently we have 3 setup in a non-production environment. We are
receiving a TLS link between some sites and other sites will use ADVPN
Hub\Spoke with SD-WAN and dual ISP. The VPN part...
Hi sorry to waste anyone's time but this seems to be a configuration
issue - likely from some old config on the fortigate that I'm looking
into. I configured this at our new location on a temporary PBX and it
worked fine right away. I thought perhaps...
Sorry for this post... I am an idiot - or just over worked this past
month. I changed the IP of the one Fortigate to 192.168.6.4 and it
worked... I pinged 192.168.6.1 and it was working .... long story short
I noticed an interface on this device alre...
Hi Stephen, I have been waiting on TAC since a few days after posting
this but did hear back from them and we have been discussing for a
couple days. At this point I believe this issue is resolved. If anyone
comes across this in summary - we used the...
I appreciate it. Yesterday it worked with the two shortcuts properly
created on both tunnels and it was sending traffic to the correct
locations. Upon a link failure it restored and went back to not having
the correct shortcut tunnel... One-time Spok...
I'll make a new post as this one was likely just a subpar configuration
and I resolved 90% of my issue by using BGP on loopback with a new
configuration but am having a different concern now.
