Solved

Replacing Checkpoint NG AI Firewall with Cisco ASA 5520

Posted on 2009-05-03
3
1,094 Views
Last Modified: 2013-11-16
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
Comment
Question by:MPI-AP
  • 2
3 Comments
 
LVL 79

Expert Comment

by:lrmoore
ID: 24294106
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
 

Author Comment

by:MPI-AP
ID: 24300681
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
 
LVL 79

Accepted Solution

by:
lrmoore earned 500 total points
ID: 24307179
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

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This article will cover setting up redundant ISPs for outbound connectivity on an ASA 5510 (although the same should work on the 5520s and up as well).  It’s important to note that this covers outbound connectivity only.  The ASA does not have built…
For months I had no idea how to 'discover' the IP address of the other end of a link (without asking someone who knows), and it drove me batty. Think about it. You can't use Cisco Discovery Protocol (CDP) because it's not implemented on the ASAs.…
Both in life and business – not all partnerships are created equal. As the demand for cloud services increases, so do the number of self-proclaimed cloud partners. Asking the right questions up front in the partnership, will enable both parties …
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question