ASA PAT rule

I have a cisco ASA. A vendor has asked me to setup a PAT rule from an outisde IP to the DMZ IP of a server. IP info is:

Outside IP: 173.219.37.x
DMZ IP: 192.168.10.x

The Vendor has asked for this:
Internet to DMZ server
48622 Public IP ---> 48622 DMZ IP
443 Public IP ---> 8443 DMZ IP

I have assigned a NAT rule from the DMZ IP to the Public IP.
I have created the access rule allowing any from the outside to the public IP on port 48622 and 443

What I am not sure about is the rule changing the port from 443 to 8443. I want to be sure that not all 443 traffic hitting the firewall is directed to the one server as I have other web based servers using https.

I am learning cisco ASA setup as I go, so I apologize if this is an odd question.

Thanks for any help and insite.
jamesddavisAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
MikeKaneConnect With a Mentor Commented:
Technically, this is a port-forwarding request, not a PAT request.    

You want to take a public IP and have those ports redirected inside to a server on the DMZ.    Then you create the access list to allow the traffic.   It would looklike this:


static (dmz,outside) tcp 173.219.37.x 48622 192.168.10.x 48622 netmask 255.255.255.255
static (dmz,outside) tcp 173.219.37.x 443 192.168.10.x 443 netmask 255.255.255.255

access-list outside_in extended permit tcp any host 173.219.37.x eq 48622
access-list outside_in extended permit tcp any host 173.219.37.x eq 48622

access-group outside_in in interface outside


Now this would have to fit into your config, so the acl name may be different, etc.   Plus, you can only forward the 443 to one internal host, so if you have 443 already going to another internal host, this won't fly.  
0
 
Ernie BeekExpertCommented:
Well, if you only have one public ip you can only forward port 443 once.....

So if you want to forward port 443 to multiple servers, you will need multiple public ip's as well (one 443 port per ip address only).
0
 
MikeKaneCommented:
Oops , this:
access-list outside_in extended permit tcp any host 173.219.37.x eq 48622
access-list outside_in extended permit tcp any host 173.219.37.x eq 48622

should be this:
access-list outside_in extended permit tcp any host 173.219.37.x eq 48622
access-list outside_in extended permit tcp any host 173.219.37.x eq 443
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
jamesddavisAuthor Commented:
Sorry, I have multiple outside IP addresses provided by my ISP. I am using one of those IP addresses, 173.219.37.x, for the DMZ host 192.168.10.x with a static NAT.

Sorry for the incorrect wording, I am looking to port forward not PAT.

So if I only want traffic coming to IP 173.219.37.x on port 443 to be changed to port 8443 to the DMZ server mentioned, would the config above be correct?

Thanks,



0
 
Ernie BeekExpertCommented:
Yes it would. To forward a second port 443, you'll need a second public, etc.
0
 
jamesddavisAuthor Commented:
OK, now where in the above statement is it changing from 443 to 8443? Just making sure I understand. This is a learning exercise as much as it is getting this setup.

Thanks,
0
 
Ernie BeekConnect With a Mentor ExpertCommented:
Good catch, it isn't. It should be:
static (dmz,outside) tcp 173.219.37.x 443 192.168.10.x 8443 netmask 255.255.255.255
0
 
MikeKaneCommented:
Thank you ernie... I missed that...  
443 Public IP ---> 8443 DMZ IP


0
 
Ernie BeekExpertCommented:
My pleasure ;)
0
 
jamesddavisAuthor Commented:
Thanks for the help, I thought that was the case, but wanted to be sure. Didn't want to break all of my other https web servers.

Thanks
0
All Courses

From novice to tech pro — start learning today.