• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1143
  • Last Modified:

Replacing Checkpoint NG AI Firewall with Cisco ASA 5520

Hi

Im trying to replace a checkpoint NG AI Firewall thats securing a web hosting farm with several internal web servers running about 25 web sites.. I wan to replace the Checkpoint with a Cisco ASA 5520, running OS 8. One of the key implementations on the checkpoint that I need to replicate is a port redirection thats in place for all the web sites.. Which maps from a public IP to an internal IP and a different host.. i.e.

On the checkpoint side in destination field there is

www.zzzz.com static NAT to Y public IP.
www.kkk.com static NAT to Q public IP.
www.hhh.com static NAT to K public IP.
And so on for all the web sites..

On the service field there is a custom built service which has a match i.e. under advanced that has this&

SRV_REDIRECT(80,192.168.2.6,82)  
SRV_REDIRECT(82,192.168.2.6,92)  
SRV_REDIRECT(100,192.168.2.2,101)  
SRV_REDIRECT(110,192.168.2.2,111)  
And so on for all the web sites, for both https and http..

I assumed its a simple case of doing a PAT, so on the ASA I setup a static NAT where I put in the public IP on the original source field and on the translated to section inside interface and inside IP and enable PAT and put in the source and destination ports as above.. I also added the usual allow any traffic from any where to the public IP on the outside interface Access list&

All this does not seem to work on the ASA, works fine on the Checkpoint, Im sure Ive got it totally wrong & Any idea ??

Thanks
www.zzzz.com static NAT to Y public IP. 
www.kkk.com static NAT to Q public IP.
www.hhh.com static NAT to K public IP.
 
SRV_REDIRECT(80,192.168.2.6,82)  
SRV_REDIRECT(82,192.168.2.6,92)  
SRV_REDIRECT(100,192.168.2.2,101)  
SRV_REDIRECT(110,192.168.2.2,111)

Open in new window

0
MPI-AP
Asked:
MPI-AP
  • 2
1 Solution
 
lrmooreCommented:
You have the original and translated to backwards.
The original source is the internal 192.168.2.x ip address and the translated to is the public IP.
0
 
MPI-APAuthor Commented:
Hi,

Isn't that the case when its an outgoing NAT i.e. inside host (192.168.2.x) accessing the internet, then we translate from the internal private IP to the external public IP.
What's going on here is the public Internet users are accessing the web sites that are hosted on the internal private IP range. But the users access it via the public IP, each public IP port 80 is mapped to a different port on an internal private IP, so its a sort of a NAT in reverse i.e. outside to inside... And thats the part thats does not work on the ASA.

Thanks

Regards  
0
 
lrmooreCommented:
That's correct. That is called "hairpinning" and is a real challenge with Cisco. The "best" solution is for internal users to just resolve to the private IP addresses using an internal DNS. The 2nd best solution is to use DNS doctoring with external dns server. Key is that the dns servers that the clients use absolutely  must be outside the firewall. Just append the "dns" keyword to the static xlate.
Example:
 static (inside,outside) tcp <public ip> 80 192.168.2.6 82 netmask 255.255.255.255 dns
 static (inside,outside) tcp <public ip> 82 192.168.2.6 92 netmask 255.255.255.255 dns
<etc>
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now