Multi-WAN + CARP, moved VPN tunnels to new WAN, strange routing issue

  • We are using two WAN connections on two different physical interfaces.  We recently moved our IPSEC VPN tunnels to our second WAN connection and that all seemed to work fine.  However, now we cannot hit the public IPs of the remote gateway as a new route was added that directs that traffic through the secondary WAN's gateway instead of the primary WAN.

    We have outbound NAT rules for the primary WAN connection so I'm suspecting we need to add outbound NAT rules for those specific destinations to force them over the secondary WAN.  Is this correct or am I missing something?

  • The answer was indeed outbound NAT rules needed.

Log in to reply