ā06-03-2015 01:49 PM - edited ā03-11-2019 11:02 PM
Hi
I am in the process of replacing some Watchguard firewalls with ASA firewalls. I have noticed a few static NAT rules on the Watchguard using the same public IP address but each NAT uses a different private IP Address.
e.g
98.98.98.1 > 192.168.10.1
98.98.98.1 > 192.168.10.5
98.98.98.1 > 192.168.10.20
98.98.98.1 > 192.168.10.44
How would I add this into an ASA. This is for external hosts trying to access internal servers on the one external IP but mapped to different internal IPs.
Would a standard PAT work using the different internal IPs to PAT to the single external IP.
Thanks
Solved! Go to Solution.
ā06-03-2015 06:09 PM
You could PAT say port 8080,8081,etc and translate that to 80 on the inside but you'd need to make sure you set it up the same way as watchguard. I assume watchguard does NAT the same way as ASA and just reads down the list. with the way you describe it, unless there was something to differentiate the NATs it would hit the first one only
I would first check to see if all the 192.168.10.x hosts are even live. most likely some are not if you are replacing an old firewall.
secondly, would these IPs happen to be in a cluster? If so, I have had to do a static nat to the VIP of the cluster so the outside world could talk to it but then also do dynamic nat for the individual cluster members. This is because the cluster members would use their own IP to initiate outbound traffic.
ā06-03-2015 06:09 PM
You could PAT say port 8080,8081,etc and translate that to 80 on the inside but you'd need to make sure you set it up the same way as watchguard. I assume watchguard does NAT the same way as ASA and just reads down the list. with the way you describe it, unless there was something to differentiate the NATs it would hit the first one only
I would first check to see if all the 192.168.10.x hosts are even live. most likely some are not if you are replacing an old firewall.
secondly, would these IPs happen to be in a cluster? If so, I have had to do a static nat to the VIP of the cluster so the outside world could talk to it but then also do dynamic nat for the individual cluster members. This is because the cluster members would use their own IP to initiate outbound traffic.
ā06-05-2015 12:26 AM
Thanks
I will go through and see what hosts are actually live, looks like many old rules so il tidy them up before moving further. I am order a new larger external ip address range so I may just NAT them out to individual IPs instead of doing the port address translations
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide