There are a number of ways to bypass NAT using a Cisco ASA. I suppose the easiest way would be to leave it alone when you install it and don’t use NAT at all. Why? Because the ASA does not have NAT-Control enabled by default. This means that you can configure you ASA just as you would a router and exchange routes between the inside and outside. Aside from needing an ACL on the outside interface, applied in an inbound direction, you should notice that if functions very similar to what you would expect a router to function like.
However, for most of us, this is not feasible. Because of the use of RFC 1918 addresses we are required to use NAT or PAT when we make connections to the Internet. Still situations may arise where you have NAT configured but for some reason you need to bypass it. Here are a few examples of how to do this along with the terminology that these methods are referred to in ASA 8.2.
Identity NAT
When you use Identity NAT the connections can only be originated by the address that’s covered in the statement. Of course, return traffic will be allowed, but you can’t originate an outside connection into the address in the NAT statement.
Here is how you configure it:
ASA1(config)# nat (inside) 0 10.1.1.0 255.255.255.0
In this code example you can initiate an outbound connection from addresses on the 10.1.1.0/24 subnet and it will not translate the source.
Static Identity NAT
A Static Identity NAT Translation is always active. This means that a connection can be initiated into this address, provided there is an ACL inbound on the lower security-level interface that permits the connection. You can also originate connections from the address defined in the statement for outbound connections and the ASA will not Translate the source. [Read more...]







