We are planning to deploy ISP redundancy (currently single ISP... ISP X... with multiple uplinks via our Firewall) and need MX Concentrator traffic to failover between ISPs upon failure of ISP X   We are not using our own public IPv4 allocation (expensive) and thus relying on ISP allocated prefixes on both links.   We had/have issues with unhealthy NAT via our Firewalls, largely relating to tunnels failing to re-establish cleanly after failover.   Manual NAT config has prevented this issue from happening since implemented. How are we able to deploy a dual ISP solution in this manner while still retaining Manual NAT Config, one for each ISP Address used? Do we need our own /24 public address allocation to use this or to somehow fix our unclean NAT issue? If we were able to set a separate Manual Port Forwarding NAT Traversal Config on the Warm Standby MX, that may help, or a Dual WAN (Dual VIP + Dual Manual Port Forwarding NAT Traversal config, that could work. In the Attached Diag, ISP Y is the service we need to be able to failover to.   Has anyone done this without Auto NAT Traversal and their own portable public IPv4 prefix?     ... View more