Comments
-
Bruce thank you and yes it did turn out to be the SD-WAN on the policy. Since the policy was auto generated during the creation of the VPN in an earlier version of the fireware the upgrade to 12.6.3 simply added the SD-WAN and feature to switch or remove SD-WAN was disabled. I didn't think of recreating the policy without…
-
Different devices on each end (remote is Fortigate 60D) and (local an M370). Both devices working perfectly fine, WAN ip has not changes, cofiguration on fortigate has not been changed. Only thing was the upgrade to 12.6.3 and uses SD-WAN and everything looks good just no traffic back to the fortigate such as ping response.
-
"but can NOT reach" anything behind 192.168.10.2 thru 253.
-
From 10.216.5.1 <--> 192.168.10.1 works fine and can manage M370 device but can reach anything behind 192.168.10.2 thru 253. From the M370 I can ping everything 10.216.5.0/24 no problems there. Just strange I suspect something with the SD-WAN as this is a new feature in the version of the Watchguard I upgraded to.
-
Hi Mada, yes on the local network this particular IP is responding to ping. From 10.216.5.1 for example I can reach the interface of the M370 and manage the firewall but anything other than the gateway wont allow me to connect. On the traffic monitor everything is passing through I can see allowed BOVPN traffic.