NAT on a stick facing the internet (ip nat outside) interface.
I just came across a situation where a client had moved servers from their property to a data center and had trucks talking to a hardcoded ip address that was at their property. So they needed to redirect the old IP to the new datacenter ip address.
I managed to get this working but found a gotcha that i watned to share. These configs are from the test lab i used to set it up.
I will list the ip's and their uses:
Fa0/0 : 192.168.1.1 : internet interface
loopback0 : 10.22.22.22 : Doesnt matter what this actually is.
traffic is coming from any ip on the internet pointed at 10.0.0.1 which should be translated to the internet address 192.168.50.1 which sits out fa0/0 by the default route.
It is not shown in this config but due to the client actually using, in this case, the 10.0.0.0/24 on the internal interface of the router i had to put a static route for 10.0.0.1 255.255.255.255 pointing to fa0/0 to make it use the nat rules to rewrite the destination.
The one issue i had was when i made the static nat rule for the outside looking at the ip packet debug the traffic coming in no longer used the PBR i had setup to force it to loop back on the loopback interface.
If i was to pull out the static nat it would use the PBR and go via loopback. Thinking about it i put the no alias at the end of the static nat and this stopped the traffic jumping the PBR and forced it to work.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...