Bruce_Briggs

You can associate 192.168.13.51 with x.x.x.133 using a 1-to-1 NAT setup. About 1-to-1 NAT https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/nat/one_to_one_nat_c.html (View Post)

Not needed. Try what I recommended (View Post)

The reason is that policy 2 specifies a specific WAN interface and not Any-external. Unexpected routing results with Multi-WAN and the use of specific WAN interfaces in the To: field of a policy inst… (View Post)

FYI - this info is in a prior post, here: https://community.watchguard.com/watchguard-community/discussion/4080/policy-set-up (View Post)

As I said in an earlier post - you need to specify Any-external instead of a specific WAN interface on an outgoing policy when using Multi-WAN. Otherwise unexpected routing occurs, such as you are se… (View Post)