Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Ambiguity in manual for SD-WAN policy destination

Manual notes the following, but WAN is not an option.

Check if an SD-WAN policy route has Destination networks set to Any.

Change the setting from Any to a specific choice (example: WAN) from the list. Setting it to Any forces XG Firewall to forward internal traffic also to the WAN interface.

 

This seems like a very easy solution to my problem of all VPN SSL traffic appearing to try routing out the WAN interface.

I am using OSPF routing for the network, and precedence is sd-wan. vpn, static, and I have no static routes.

Am I missing a workaround to the possible Any/Any issue?



This thread was automatically locked due to age.
Parents Reply
  • With the above, I am now getting to one local LAN subnet, where the VPN connection is made, but not across to anything else in the OSPF range.

    I currently have just one other subnet (192.168.20.x) in the allowed resource list of "Permitted network resources", which is back to the head office, but this is not accessible.

    The OpenVPN config is listing:

    remote x.x.x.x 8443 (public interface)
    remote 192.168.10.1 8443 (local lan)
    remote 172.30.255.10 8443 (ospf p2p)
    remote 10.10.1.1 8443 (local ospf area)

Children