Cisco
--
Questions
--
Followers
Top Experts
PIX 506E Config Question ( NAT and PORTS )
I have a PIX 506E, and I am still getting used to working with it. I have an existing config that works fine, but I want to forward a Port, 3389 specifically to a different server (192.168.42.31 )
Currently, from what I assume, the outside ip address, xxx.xxx.77.36 is Nat'd to 192.168.42.33 with Port 3389 & FTP allowed through.
I would like to leave FTP forwarded to 192.168.42.33, but would like 3389 forwarded to 192.168.42.31.
Here is a copy of the config, and version.
sh ver
Cisco PIX Firewall Version 6.3(5)
Cisco PIX Device Manager Version 3.0(4)
Compiled on Thu 04-Aug-05 21:40 by morlee
pdc-pix01 up 20 days 22 hours
Hardware: PIX-506E, 32 MB RAM, CPU Pentium II 300 MHz
Flash E28F640J3 @ 0x300, 8MB
BIOS Flash AM29F400B @ 0xfffd8000, 32KB
0: ethernet0: address is 000f.3492.831a, irq 10
1: ethernet1: address is 000f.3492.831b, irq 11
This PIX has a Restricted (R) license.
Serial Number: xxxxxxxxxxxxxx
Running Activation Key: xxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx
Configuration last modified by enable_15 at 14:59:40.452 EST Thu Jan 22 2009
sh run
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxxxxxxxxxxx encrypted
passwd xxxxxxxxxxxxx encrypted
hostname xxx-pix01
domain-name xxxxxxxxxxxx.com
clock timezone EST -5
clock summer-time EDT recurring
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list outside_in permit tcp any host xxx.xxx.77.35 eq www
access-list outside_in permit tcp any host xxx.xxx.77.35 eq smtp
access-list outside_in permit tcp any host xxx.xxx.77.35 eq pop3
access-list outside_in permit tcp any host xxx.xxx.77.35 eq https
access-list outside_in permit tcp any host xxx.xxx.77.36 eq ftp
access-list outside_in permit tcp any host xxx.xxx.77.36 eq 3389
access-list outside_in permit tcp any host xxx.xxx.77.35 eq 8080
access-list no_nat permit ip 192.168.42.0 255.255.255.0 192.168.43.0 255.255.255.0
access-list split permit ip 192.168.42.0 255.255.255.0 192.168.43.0 255.255.255.0
access-list vpn_acl permit ip 192.168.42.0 255.255.255.0 192.168.43.0 255.255.255.0
pager lines 24
logging on
logging trap debugging
logging host inside 192.168.42.31
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.77.34 255.255.255.248
ip address inside 192.168.42.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_pool 192.168.43.1-192.168.43.20
pdm location 192.168.42.0 255.255.255.0 inside
pdm location 192.168.42.21 255.255.255.255 inside
pdm location 192.168.42.31 255.255.255.255 inside
pdm location 192.168.42.102 255.255.255.255 inside
pdm location 192.168.43.0 255.255.255.0 outside
pdm location 192.168.42.11 255.255.255.255 inside
pdm location 192.168.43.0 255.255.255.0 inside
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list no_nat
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) xxx.xxx.77.35 192.168.42.21 netmask 255.255.255.255 0 0
static (inside,outside) xxx.xxx.77.36 192.168.42.33 netmask 255.255.255.255 0 0
access-group outside_in in interface outside
route outside 0.0.0.0 0.0.0.0 xxx.xxx.77.33 0
route inside 192.168.45.0 255.255.255.0 192.168.42.2 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
no snmp-server location
no snmp-server contact
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set myset esp-3des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap client authentication LOCAL
crypto map mymap interface outside
isakmp enable outside
isakmp identity address
isakmp nat-traversal 10
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup pdc_vpn address-pool vpn_pool
vpngroup pdc_vpn dns-server 192.168.42.11
vpngroup pdc_vpn wins-server 192.168.42.11
vpngroup pdc_vpn default-domain phoenixdata.local
vpngroup pdc_vpn split-tunnel split
vpngroup pdc_vpn idle-time 1800
vpngroup pdc_vpn password ********
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 60
ssh 0.0.0.0 0.0.0.0 outside
ssh 0.0.0.0 0.0.0.0 inside
ssh timeout 60
console timeout 0
:end
Currently, from what I assume, the outside ip address, xxx.xxx.77.36 is Nat'd to 192.168.42.33 with Port 3389 & FTP allowed through.
I would like to leave FTP forwarded to 192.168.42.33, but would like 3389 forwarded to 192.168.42.31.
Here is a copy of the config, and version.
sh ver
Cisco PIX Firewall Version 6.3(5)
Cisco PIX Device Manager Version 3.0(4)
Compiled on Thu 04-Aug-05 21:40 by morlee
pdc-pix01 up 20 days 22 hours
Hardware: PIX-506E, 32 MB RAM, CPU Pentium II 300 MHz
Flash E28F640J3 @ 0x300, 8MB
BIOS Flash AM29F400B @ 0xfffd8000, 32KB
0: ethernet0: address is 000f.3492.831a, irq 10
1: ethernet1: address is 000f.3492.831b, irq 11
This PIX has a Restricted (R) license.
Serial Number: xxxxxxxxxxxxxx
Running Activation Key: xxxxxxxxx xxxxxxxxxx xxxxxxxxxx xxxxxxxxxx
Configuration last modified by enable_15 at 14:59:40.452 EST Thu Jan 22 2009
sh run
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxxxxxxxxxxx encrypted
passwd xxxxxxxxxxxxx encrypted
hostname xxx-pix01
domain-name xxxxxxxxxxxx.com
clock timezone EST -5
clock summer-time EDT recurring
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list outside_in permit tcp any host xxx.xxx.77.35 eq www
access-list outside_in permit tcp any host xxx.xxx.77.35 eq smtp
access-list outside_in permit tcp any host xxx.xxx.77.35 eq pop3
access-list outside_in permit tcp any host xxx.xxx.77.35 eq https
access-list outside_in permit tcp any host xxx.xxx.77.36 eq ftp
access-list outside_in permit tcp any host xxx.xxx.77.36 eq 3389
access-list outside_in permit tcp any host xxx.xxx.77.35 eq 8080
access-list no_nat permit ip 192.168.42.0 255.255.255.0 192.168.43.0 255.255.255.0
access-list split permit ip 192.168.42.0 255.255.255.0 192.168.43.0 255.255.255.0
access-list vpn_acl permit ip 192.168.42.0 255.255.255.0 192.168.43.0 255.255.255.0
pager lines 24
logging on
logging trap debugging
logging host inside 192.168.42.31
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.77.34 255.255.255.248
ip address inside 192.168.42.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_pool 192.168.43.1-192.168.43.20
pdm location 192.168.42.0 255.255.255.0 inside
pdm location 192.168.42.21 255.255.255.255 inside
pdm location 192.168.42.31 255.255.255.255 inside
pdm location 192.168.42.102 255.255.255.255 inside
pdm location 192.168.43.0 255.255.255.0 outside
pdm location 192.168.42.11 255.255.255.255 inside
pdm location 192.168.43.0 255.255.255.0 inside
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list no_nat
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) xxx.xxx.77.35 192.168.42.21 netmask 255.255.255.255 0 0
static (inside,outside) xxx.xxx.77.36 192.168.42.33 netmask 255.255.255.255 0 0
access-group outside_in in interface outside
route outside 0.0.0.0 0.0.0.0 xxx.xxx.77.33 0
route inside 192.168.45.0 255.255.255.0 192.168.42.2 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
no snmp-server location
no snmp-server contact
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set myset esp-3des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap client authentication LOCAL
crypto map mymap interface outside
isakmp enable outside
isakmp identity address
isakmp nat-traversal 10
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup pdc_vpn address-pool vpn_pool
vpngroup pdc_vpn dns-server 192.168.42.11
vpngroup pdc_vpn wins-server 192.168.42.11
vpngroup pdc_vpn default-domain phoenixdata.local
vpngroup pdc_vpn split-tunnel split
vpngroup pdc_vpn idle-time 1800
vpngroup pdc_vpn password ********
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 60
ssh 0.0.0.0 0.0.0.0 outside
ssh 0.0.0.0 0.0.0.0 inside
ssh timeout 60
console timeout 0
:end
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Using that config, doesn't it use the existing outside public ip ? Which is xxx.xxx.77.34
Just making sure, since the IP I want to use is: xxx.xxx.77.36
Just wondering how in that config, the 3389 and 21 get associated with the xxx.xxx.77.36 Public Address?
Hopefully what I just said makes sense... I am just trying to understand this for my future reference as well.
Thanks...
From the above config, here is what I assume:
These statements simply allow the specific ports to be allowed through.access-list outside_in permit tcp any host xxx.xxx.77.35 eq wwwaccess-list outside_in permit tcp any host xxx.xxx.77.35 eq smtpaccess-list outside_in permit tcp any host xxx.xxx.77.35 eq pop3access-list outside_in permit tcp any host xxx.xxx.77.35 eq httpsaccess-list outside_in permit tcp any host xxx.xxx.77.36 eq ftpaccess-list outside_in permit tcp any host xxx.xxx.77.36 eq 3389access-list outside_in permit tcp any host xxx.xxx.77.35 eq 8080
And these statments actually create the inbound NAT to the private ip addresses.static (inside,outside) xxx.xxx.77.35 192.168.42.21 netmask 255.255.255.255 0 0
static (inside,outside) xxx.xxx.77.36 192.168.42.33 netmask 255.255.255.255 0 0
But the actual Outside Public Address, and Inside Private Addresses are:ip address outside xxx.xxx.77.34 255.255.255.248
ip address inside 192.168.42.1 255.255.255.0
Just making sure, since the IP I want to use is: xxx.xxx.77.36
Just wondering how in that config, the 3389 and 21 get associated with the xxx.xxx.77.36 Public Address?
Hopefully what I just said makes sense... I am just trying to understand this for my future reference as well.
Thanks...
From the above config, here is what I assume:
These statements simply allow the specific ports to be allowed through.access-list outside_in permit tcp any host xxx.xxx.77.35 eq wwwaccess-list outside_in permit tcp any host xxx.xxx.77.35 eq smtpaccess-list outside_in permit tcp any host xxx.xxx.77.35 eq pop3access-list outside_in permit tcp any host xxx.xxx.77.35 eq httpsaccess-list outside_in permit tcp any host xxx.xxx.77.36 eq ftpaccess-list outside_in permit tcp any host xxx.xxx.77.36 eq 3389access-list outside_in permit tcp any host xxx.xxx.77.35 eq 8080
And these statments actually create the inbound NAT to the private ip addresses.static (inside,outside) xxx.xxx.77.35 192.168.42.21 netmask 255.255.255.255 0 0
static (inside,outside) xxx.xxx.77.36 192.168.42.33 netmask 255.255.255.255 0 0
But the actual Outside Public Address, and Inside Private Addresses are:ip address outside xxx.xxx.77.34 255.255.255.248
ip address inside 192.168.42.1 255.255.255.0
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
The idea behind port forwarding is if you have only one public ip address used as the outside public address of the firewall and you want hosts on the internet to access services e.g. web, ftp, smtp using only one public ip
The last post I sent U gives you the correct config to do this
the firewall forwards traffic from the outside public ip address outside xxx.xxx.77.34 255.255.255.248 to the ports specified in the access lists
The other method requires a static mapping of one public ip address (not the firewall outside ip) for each server. So you need several static ip's if you have ftp, smtp, rdp servers for internet hosts to access. Port forwarding eliminates this
The last post I sent U gives you the correct config to do this
the firewall forwards traffic from the outside public ip address outside xxx.xxx.77.34 255.255.255.248 to the ports specified in the access lists
The other method requires a static mapping of one public ip address (not the firewall outside ip) for each server. So you need several static ip's if you have ftp, smtp, rdp servers for internet hosts to access. Port forwarding eliminates this
Sorry bignewf if my wording and explanations were a little unclear.
But yes, the config above ( Original Post ) is working just fine. I have added a Terminal Server to the network, and that is why I need this change.
So, given the config above, how can I simply re-direct 3389 from it's current destination of : xxx.xxx.77.36:3389 ----> 192.168.42.33
to
xxx.xxx.77.36:3389 ----> 192.168.42.31
That's really all I want to do here is change the destination from the .33 to the .31.
Hopefully that helps.
Sorry again about the confusion...
Parry Sands
But yes, the config above ( Original Post ) is working just fine. I have added a Terminal Server to the network, and that is why I need this change.
So, given the config above, how can I simply re-direct 3389 from it's current destination of : xxx.xxx.77.36:3389 ----> 192.168.42.33
to
xxx.xxx.77.36:3389 ----> 192.168.42.31
That's really all I want to do here is change the destination from the .33 to the .31.
Hopefully that helps.
Sorry again about the confusion...
Parry Sands
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
no static (inside,outside) xxx.xxx.77.36 192.168.42.33 netmask 255.255.255.255 0 0
static (inside,outside) xxx.xxx.77.36 192.168.42.31 netmask 255.255.255.255 0 0
clear xlate
Won't this change the current translation in place for Port 21 that I need to keep in place for the xxx.xxx.77.36 that goes to the 192.168.42.33 ?
I was hoping the xxx.xxx.77.36 could be used for both.
Port 21 to the 192.168.42.33
Port 3389 to the 192.168.42.31
Both coming from the xxx.xxx.77.36 Public Address.
I was hoping the xxx.xxx.77.36 could be used for both.
Port 21 to the 192.168.42.33
Port 3389 to the 192.168.42.31
Both coming from the xxx.xxx.77.36 Public Address.
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
ThanQ
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Cisco
--
Questions
--
Followers
Top Experts
Cisco PIX is a dedicated hardware firewall appliance; the Cisco Adaptive Security Appliance (ASA) is a firewall and anti-malware security appliance that provides unified threat management and protection the PIX does not. Other Cisco devices and systems include routers, switches, storage networking, wireless and the software and hardware for PIX Firewall Manager (PFM), PIX Device Manager (PDM) and Adaptive Security Device Manager (ASDM).