https://community.cisco.com/t5/network-security/same-ip-nat-on-two-static/m-p/2876158#M153686 <P>Why don't you use a VPN on both links, and then you can either use the real addresses or a NAT translation - in either case it will be the same on both units.</P> Thu, 19 May 2016 23:18:17 GMT Philip D'Ath 2016-05-19T23:18:17Z https://community.cisco.com/t5/network-security/same-ip-nat-on-two-static/m-p/2876157#M153685 <P>I have a problem with a VPN redundancy link. In my infraestructure i have one dedicate link for a provider this link is filter by a FW-A on interface outside, we need a redundacy link this link are made by VPN on FWB that connect with FWA on inside interface, the problem is that; in dedicate link i apply a static NAT with 192.168.20.20 that maped real address on Outside FW-A (inside,outside) 192.168.20.20 X.X.X.X , but when the traffic switch to VPN the traffic arrive to FW-A on interface VPN . My question is that i can appli a static NAT like (inside,vpn) 192.168.20.20&nbsp; with the same ip nat that i asing to dedicate link. Or if i can translate the ip in the FWB where i make the VPN Tunnel. In less words i need keep the IP NAT 192.168.20.20 for the connection between the provider.</P> Tue, 12 Mar 2019 07:46:31 GMT https://community.cisco.com/t5/network-security/same-ip-nat-on-two-static/m-p/2876157#M153685 ricardo.hdz 2019-03-12T07:46:31Z https://community.cisco.com/t5/network-security/same-ip-nat-on-two-static/m-p/2876158#M153686 <P>Why don't you use a VPN on both links, and then you can either use the real addresses or a NAT translation - in either case it will be the same on both units.</P> Thu, 19 May 2016 23:18:17 GMT https://community.cisco.com/t5/network-security/same-ip-nat-on-two-static/m-p/2876158#M153686 Philip D'Ath 2016-05-19T23:18:17Z