topic Re: Destination NAT/PAT clarification in General Topics

Destination NAT/PAT clarification

MCmgt — Mon, 03 Jun 2013 16:24:25 GMT

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:

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

Re: Destination NAT/PAT clarification

Retired Member — Mon, 03 Jun 2013 16:30:11 GMT

Hi,

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

Re: Destination NAT/PAT clarification

gswcowboy — Mon, 03 Jun 2013 16:35:44 GMT

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.

Re: Destination NAT/PAT clarification

MCmgt — Mon, 03 Jun 2013 18:35:09 GMT

Thanks! So something along the lines of this?

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?

Re: Destination NAT/PAT clarification

gswcowboy — Mon, 03 Jun 2013 18:50:24 GMT

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.

Re: Destination NAT/PAT clarification

Retired Member — Mon, 03 Jun 2013 18:56:56 GMT

That config is correct.You will open only the ports what you need, so that you can protect your devices

Re: Destination NAT/PAT clarification

trondk — Wed, 19 Jun 2013 08:58:56 GMT

I`m currently testing a PA to see if we are going to replace our existing FWs

However, I`m about to throw this .. out the window.

Most likely I`m to dim to get this but I`m struggling with NAT and as far as I can see its the same scenario that McMgt presents.

I need the following:

any outside on port FTP to specific inside on port FTP

ie: IP any on port FTP to IP 192.168.something on port FTP

Can someone please explain to me how to do this in layman's terms

Re: Destination NAT/PAT clarification

mikand — Wed, 19 Jun 2013 19:24:08 GMT

Have you tried ?

In your case:

First create a NAT rule:

source zone: outside

destination zone: outside

destination interface: none (could be set to the physical interface if you wish)

source address: any

destination address: outside_ip

service: any (or set TCP21 along with the portrange you have defined for passive ftp preferly)

source translator: none

destination address: inside_ip

Then create a security rule:

source zone: outside

source address: any

destination zone: inside

destination address: outside_ip

application: ftp

service: application-default (or set TCP21 along with the portrange you have defined for passive ftp)

action: allow

profile: recommended to use an IPS profile thats configured according to: critical, high, medium: block - low, information: default

options: log on session end (enable log on session start for troubleshooting)

You could also use a network range instead of outside_ip. For example outside_range if thats what you mean by "any outside"?

Re: Destination NAT/PAT clarification

trondk — Sat, 22 Jun 2013 10:29:29 GMT

Thank you very much mikand!

I will have another go at this and see what I can do!