I have created a internal zone IP address I want to use as generic for FTP communications 192.168.1.9.
I want to NAT this IP to our current FTP server 192.168.1.19. This way when our FTP server changes we just change our NAT rule rather than the rest of our partner companies firewalls, routes, etc.
I've created a DNAT rule and able to ping 192.168.1.9 and get a response from 192.168.1.19, but unable to connect via ftp.
I've done this before successfully between network zones (subnets) but not on the same zone (subnet) so far.
For it to work from outside you need:
From zone - Untrust
To zone - Untrust
Destination Address - 220.127.116.11
Service - create new tcp-21 with protocol tcp and port 21
Destination translation - 192.168.32.19
NB! Place this new wan rule above WebServer1 rule because otherwise WebServer1 will NAT all ports to 192.168.1.9
This does not affect users connecting directly to .19
Issue is that if client from 192.168.1.x network connects to 192.168.1.9 that is DNATed further to 192.168.1.19 then reply packet is sent directly to original source IP because 192.168.1.19 identifies that source is in it's own subnet and does not need to send this packet to gateway.
Client who received reply packet from 192.168.1.19 will drop it because it does not know anything about 192.168.1.19 as client initiated connection to 192.168.1.9
I would like to resolve this thread this week.
I have my DNAT rule in place and I can ping 192.168.1.9 (VIP) and get a response from 192.168.1.19 (FTP server), but ftp does not work when I try ftp://192.168.1.9.
How would I set up the correct SNAT rule for this to work? I just tried this SNAT rule, but not working so far.
Your original DNAT rule was fine.
All you were missing was Source NAT field.
Do not change other fields in your initial rule.
You need to have both Source NAT and Destination NAT configured in this single NAT policy.
Assume that your firewall internal IP is 192.168.1.1
In this case Source NAT is from this 192.168.1.1 IP
From zone - Trust
To zone - Trust
Source address - Any
Destination address - 192.168.1.9
Source translation - Dynamic-ip-port 192.168.1.1 (assuming this is your fw internal IP)
Destination translation - 192.168.1.19
That is working for me internally now. Still trying to wrap my head around it. 🙂
However, it does not work externally. I have a security rule that opens everything to my public IP. I have a NAT rule that translates public IP to 192.168.1.9 (and a source Dynamic IP and port to external interface IP). Neither http or ftp work, just times out. (I have a web server and ftp server here)
Curious if you comments about external connectivity?
Thank you for your guidance...
Internet = 18.104.22.168 (one of my public IPs I use for internet access)
Copperfield = 192.168.1.1 (IP of internal LAN Interface)
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!