12-31-2007 11:11 AM - edited 02-21-2020 01:50 AM
I am using an ASA-5540 strickly for IPsec VPN lan-2-lan tunnels and will never be NATing outbound as we have a public Class-B address space.
Since I'm never going to be NATing, can I disable the nat 0 and no-nat funcationality completely so that the ASDM doesn't always supply a no nat line for every ACL entry? I'll have 100s of host and network objects and don't want to no-nat any of them.
If so, how do I disable that?
01-01-2008 06:46 PM
I believe you can accomplish this through the use of no nat-control command in ASA, I personaly have not faced this scenario but have read about it , look into the nat-control disabling/enabling command and its purpose, I think it should provide you with what you are looking for.
http://www.cisco.com/en/US/docs/security/asa/asa71/command/reference/no_711.html#wp1603837
Rgds
Jorge
01-02-2008 02:15 PM
Hi,
Looks like you simply need to disable NAT on the firewall, you should have some lines like below.
nat (inside) 0 access-list natzero
nat (inside) 1 0.0.0.0 0.0.0.0
nat (DMZ) 0 access-list natzero
nat (DMZ) 1 0.0.0.0 0.0.0.0
you can remove access-list part and this will remove natzero config, if you need to remove NAT all together then you may want to remove nat statements all together. however you need to look for traffic between different segments as removing NAT from firewall completely is not a good idea.
01-02-2008 07:20 PM
Would it be a good idea to remove NAT completely if we don't ever use private address spaces - even in a DMZ scenario?
01-03-2008 10:17 AM
like someone already said, the 'no nat-control' command is what you're looking for. If you need to nat anything at a later time, you can still do so. the 'no nat-control' command doesn't mean you can't nat, only that you don't have to nat.
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