02-03-2010 11:34 AM - edited 03-11-2019 10:04 AM
What is the functional difference between the two for the following scenrio
static (inside,dmz) 1.1.1.1 1.1.1.1 netmask 255.255.255.255
vs
nat (inside) 0 1.1.1.1 255.255.255.255
Those accomplish the same thing. Is there something I'm missing?
Solved! Go to Solution.
02-03-2010 01:15 PM
static (inside,dmz) 1.1.1.1 1.1.1.1 netmask 255.255.255.255
This is only between inside and dmz
This is bi-directional meaning, in addition to the hosts on the inside, hosts in the DMZ can initiate traffic also provided ACLs allow.
This is called identity static
vs
nat (inside) 0 1.1.1.1 255.255.255.255
This can only be sourced from the inside interface going anywhere. This is called nat exemption.
-KS
02-03-2010 11:49 AM
Technically speaking the NAT statement actually does NAT. Granted it NATs to its own address, but it does NAT. With NAT0 is does not NAT at all.
Hope that helps.
Please let Cisco know that these forums are valuable to you!
https://supportforums.cisco.com/docs/DOC-6212
02-03-2010 01:15 PM
static (inside,dmz) 1.1.1.1 1.1.1.1 netmask 255.255.255.255
This is only between inside and dmz
This is bi-directional meaning, in addition to the hosts on the inside, hosts in the DMZ can initiate traffic also provided ACLs allow.
This is called identity static
vs
nat (inside) 0 1.1.1.1 255.255.255.255
This can only be sourced from the inside interface going anywhere. This is called nat exemption.
-KS
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