Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1563
  • Last Modified:

Cisco ASA 5505 - Setting Up NAT's Port Forwarding

What I require is a few ports opening up on my Cisco ASA 5505 and them port forwarding to internal local IP addresses

I have attached my running config so you can see what I currently have.

For Example the ports I require are as follows:

Service we can calll "Vuze" this needs to allow TCP port 42270 & UDP 42271 to internal IP address 192.168.1.100

Service we can call "AXIS Camera" this needs to allow TCP port 81 to internal IP address 192.168.1.101

Please can you tell me what needs to be added to my current config to achieve this
Experts-Exchange-Config.txt
0
Robert_Rayworth
Asked:
Robert_Rayworth
  • 2
  • 2
1 Solution
 
gcl_hkCommented:
Try Try

access-list outside_in permit tcp any interface outside eq 42270
access-list outside_in permit udp any interface outside eq 42271
access-list outside_in permit tcp any interface outside eq 81

static (inside,outside) tcp interface 42270 192.168.1.100 42270 netmask 255.255.255.255
static (inside,outside) udp interface 42271 192.168.1.100 42271 netmask 255.255.255.255
static (inside,outside) tcp interface 81 192.168.1.100 81 netmask 255.255.255.255



0
 
Istvan KalmarHead of IT Security Division Commented:
this line is need, but the static command not working on 8.3

access-list outside_in permit tcp any interface outside eq 42270
access-list outside_in permit udp any interface outside eq 42271
access-list outside_in permit tcp any interface outside eq 81

so you need:

hostname(config)# object network my-server
hostname(config-network-object)# host 192.168.1.100
hostname(config-network-object)# nat (inside,outside) static interface service tcp 42270 42270
hostname(config-network-object)# nat (inside,outside) static interface service tcp 42271 42271
hostname(config-network-object)# nat (inside,outside) static interface service tcp 81 81
0
 
Robert_RayworthAuthor Commented:
ikalmar you were right in thinking about the version of IOS as I am currently on ASA version 8.3(1) with ASDM version 6.3(1)

Something I want to know can I call the service or object-network by a friendly name so I can easily identifiy it

I wanted AXIS Camera for one name and Vuze for the other could you be a bit more specific
0
 
Istvan KalmarHead of IT Security Division Commented:
you need to create individual object groups with static nat

hostname(config)# object network Vuze
hostname(config-network-object)# host 192.168.1.100
hostname(config-network-object)# nat (inside,outside) static interface service tcp 42270 42270
hostname(config-network-object)# nat (inside,outside) static interface service tcp 42271 42271


hostname(config)# object network AXIS
hostname(config-network-object)# host 192.168.1.101
hostname(config-network-object)# nat (inside,outside) static interface service tcp 81 81
0
 
Robert_RayworthAuthor Commented:
Sorry for the late reply we had a family death which we needed to attend
Thanks for the response ikalmar
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

Identify and Prevent Potential Cyber-threats

Become the white hat who helps safeguard our interconnected world. Transform your career future by earning your MS in Cybersecurity. WGU’s MSCSIA degree program was designed in collaboration with national intelligence organizations and IT industry leaders.

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