NAT on Firepower FDM

qazzapatol — Wed, 17 Jul 2024 20:51:25 GMT

Hi everyone,

I'm setting up a Firepower (FDM on box) running version 7 as part of a lab environment to prepare for some network changes in our production environment to try to avoid getting stuck late during implementation.

I was trying to create a simple inbound NAT policy to allow access to an internal server behind a DMZ interface using a public static IP on the outside interface.

In my experience with SonicWall devices, the public IP is typically the original destination and the private IP is the translated destination. However, I came across a Cisco tutorial suggesting that the FTD configuration would reverse this logic, setting the internal IP as the original packet destination and the public IP as the translated destination.

I am a bit confused as to why Cisco FTD handles NAT in this way. Is there something I am not getting?

Re: NAT on Firepower FDM

MHM Cisco World — Wed, 17 Jul 2024 09:16:03 GMT

the static NAT from private IP to Public IP for Server is bidirectional
you can config static NAT
1- IN , OUT
where the source is private IP and translate to public IP
2- OUT , IN
where the destination is public IP and translate to private IP

cisco always recommend op1 but you can run both op

MHM

topic Re: NAT on Firepower FDM in Network Security

NAT on Firepower FDM

Re: NAT on Firepower FDM