topic Re: ASA 8.3 Static Nat and ACL in Network Security

ASA 8.3 Static Nat and ACL

iwearing — Mon, 11 Mar 2019 20:30:29 GMT

Hi,

Based on the network object below, I am looking for confirmation that It is good practice to use this natted object in my ACL applied incoming to the inside interface rather than have another object specifically for the object My_PC.

I have tested and it does work, however this is my preffered option rather than having to create 2 objects, for the host and also the natted host.

ASA(config)# object network My_PC
ASA(config-network-object)# host 192.168.33.2
ASA(config-network-object)# nat (inside,outside) static 209.165.201.2

thanks

Ian.

Re: ASA 8.3 Static Nat and ACL

varrao — Sat, 07 May 2011 11:02:04 GMT

Ian,

You are absolutely correct, you don't wanna keep any redundant configuration on your device. You can use the same object for your ACL as well.

Thanks,

Varun

Re: ASA 8.3 Static Nat and ACL

iwearing — Sun, 08 May 2011 08:27:46 GMT

Varun,

Thanks for your confirmation.

If I wanted to nat the same host to another interface is the config below valid where I would have 2 nats for the object My_PC

ASA(config)# object network My_PC
ASA(config-network-object)# host 192.168.33.2
ASA(config-network-object)# nat (inside,outside) static 209.165.201.2

ASA(config-network-object)# nat (inside,dmz) static 172.16.100.100

thanks

Ian.

Re: ASA 8.3 Static Nat and ACL

varrao — Sun, 08 May 2011 15:47:16 GMT

Ian,

Yes you can create two nats but for different interafaces. The configuration is good and it should definitely work.

Similarly you can also create the below NAT configuration as well, its just the same but its called Manual NAT or twice nat.

ASA(config)# object network My_PC
ASA(config-network-object)# host 192.168.33.2

ASA(config)#object network Public_IP

ASA(config-network-object)# host 209.165.201.2

ASA(config)# object network Remote_PC

ASA(config-network-object)# host 172.16.100.100

nat (inside,outside) source static My_PC Public_IP

nat (inside,dmz) source static My_PC Remote_PC

nat (outside,inside) source static any any destination static Public_IP My_PC

nat (dmz,inside) source static any any destination static Remote_PC My_PC

All the above configuration and the one that you have done are exactly same logically and hold true, but I just prefer it because in the context of a packet processing, manual nat is given preference over auto nat or object nat, so if there are some critical servers or application I usuall do Manual nat for them.

Otherwise you can go for anything that you are comfortable with.

Hope this helps.

Thanks,

Varun

Re: ASA 8.3 Static Nat and ACL

iwearing — Tue, 10 May 2011 13:11:27 GMT

Varun,

Thansk for the detailed response. Much appreciated.

Ian.

Re: ASA 8.3 Static Nat and ACL

varrao — Tue, 10 May 2011 13:17:50 GMT

Not a problem, you can message me on this thread if you face any issues with the configuration

Cheers,

Varun