Destination NAT/PAT clarification

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Destination NAT/PAT clarification

L2 Linker

Prior to shooting myself in the foot I want to make sure I'm on the right track.

I have an application where I'd like to take inbound connections directed at a particular port on my untrusted "outside" FW interface and redirect them to the same port on an RFC1918-addressed host on my trusted "inside" interface. That is:

OUTfirewall:47808 -> INrinkchiller:47808

I'm looking a Understanding_NAT-4.1-RevC.pdf and it seems to point to a NAT policy like this:

Capture.JPG

This doesn't make a whole lot of sense to me. Am I on the right track or hopelessly confused? 🙂

8 REPLIES 8

L6 Presenter

Hi,

Why did you choose source translation also ? I don'th think you need that.

L6 Presenter

destination translation is for inbound traffic (out to out zone) so removing the source translation would the first step. Dest translation address object should point to your internal IP. The OUTfirewall object should also reflect the public facing IP.

Thanks! So something along the lines of this?

Capture.JPG

Capture.JPG

And finally, it just occurred to me, since I'm hiding a bunch of devices behind that same external FW IP am I asking for trouble?

Capture.JPG

The security rule is good (outside to inside) destined for public facing IP. Inside to Outside source translation with dynamic IP/Port Src Translation for outbound traffic is a typical Src. NAT rule.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!