01-14-2016 08:18 AM - edited 03-12-2019 12:08 AM
I am attempting to cleanup some of the NAT configurations on our ASA before we upgrade from 8.2.5 to 8.3+. I had a question regarding the global nat configurations.
I understand of the purpose of most the statements below, but I don't understand the global (INSIDE) 10 interface. I also don't like the global (DMZ) 10 interface with the nat (INSIDE) 10 0.0.0.0 0.0.0.0 command. It causes the logs on the DMZ servers to only show the DMZ interface IP instead of the actual host IP. Can anyone think of a reason why they would be there?
global (OUTSIDE) 15 external-IP1
global (OUTSIDE) 10 external-IP2
global (OUTSIDE) 20 interface
global (INSIDE) 10 interface
global (DMZ) 10 interface
nat (OUTSIDE) 0 access-list NONAT-OUTSIDE
nat (OUTSIDE) 20 192.168.x.x 255.255.255.0
nat (INSIDE) 0 access-l NONAT
nat (INSIDE) 10 0.0.0.0 0.0.0.0
nat (DMZ) 0 access-l NONAT
nat (DMZ) 15 0.0.0.0 0.0.0.0
Solved! Go to Solution.
01-14-2016 08:45 AM
Hi,
For Global(inside) 10 and nat(inside) 10, it looks like the U Turning has been performed where the anything coming from inside hosts get natted to the inside interface ip.
This kind of configuration is used to prevent Asymetric routing as well where the SYN goes through ASA however SYN-ACK goes directly to client without passing through ASA. Therefore for return traffic to go through ASA, source ip is natted to Interface ip so that the reply packet first goes to the interface and then ASA performs Untranslation and sends the traffic back to actual source.
Regarding global (DMZ) 10 and nat (inside) 10, it could be possible that you might not want your DMZ hosts to see the actual source ip from Inside. Also you can check if 'nat-control' is enabled. If yes, then you need to have NAT configured on ASA for communication between interface. That could be also be the reason why this nat was kept.
Hope it helps you finding the main reason.
Regards,
Akshay Rastogi
Remember to rate helpful posts.
01-14-2016 08:45 AM
Hi,
For Global(inside) 10 and nat(inside) 10, it looks like the U Turning has been performed where the anything coming from inside hosts get natted to the inside interface ip.
This kind of configuration is used to prevent Asymetric routing as well where the SYN goes through ASA however SYN-ACK goes directly to client without passing through ASA. Therefore for return traffic to go through ASA, source ip is natted to Interface ip so that the reply packet first goes to the interface and then ASA performs Untranslation and sends the traffic back to actual source.
Regarding global (DMZ) 10 and nat (inside) 10, it could be possible that you might not want your DMZ hosts to see the actual source ip from Inside. Also you can check if 'nat-control' is enabled. If yes, then you need to have NAT configured on ASA for communication between interface. That could be also be the reason why this nat was kept.
Hope it helps you finding the main reason.
Regards,
Akshay Rastogi
Remember to rate helpful posts.
01-28-2016 12:54 PM
Thanks! This helped lead me to the right direction of what I needed to find.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide