Question Locked

Cisco PIX 501: Applying 2 IP Addr to Outside Interface

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The ISP has assigned 13 usable public IPs to my client. They want me to setup the PIX 501 with 6.3(4) OS to allow two public IPs to connect to two servers on the private network. I can't get one to work because I don't know how to assign two public IPs on the outside interface. I configured it to FTP and TELNET from outside to IP on private which is a M/S Exchange server to test logic, however no packets are hitting the access-list count. The PIX connects on .99 ok but I am unable to FTP to .101. I see Cisco statement allowing multiple IPs on public interface but I cannot find an example. Thanks in advance of any help offered.

Here is my config:
PIX Version 6.3(4)
interface ethernet0 100full
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt24 encrypted
passwd 2KFQdI.2KYOU encrypted
hostname pixfirewall
domain-name ciscopix.com
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 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
name x.y.184.97 public_gateway
name x.y.184.101 public_exchange
name 192.168.10.7 inside_exchange
access-list outside_in permit tcp any host public_exchange eq telnet
access-list outside_in permit tcp any host public_exchange eq ftp
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside x.y.184.99 255.255.255.240
ip address inside 192.168.10.3 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp public_exchange telnet inside_exchange telnet netmas
k 255.255.255.255 0 0
static (inside,outside) tcp public_exchange ftp inside_exchange ftp netmask 255.
255.255.255 0 0
access-group outside_in in interface outside
route outside 0.0.0.0 0.0.0.0 public_gateway 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 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
ntp server 216.218.192.202 source outside prefer
http server enable
http 192.168.10.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 192.168.10.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.10.150-192.168.10.200 inside
dhcpd dns 192.168.10.8 64.60.0.17
dhcpd wins 192.168.10.8
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd domain boatswains.com
dhcpd enable inside
terminal width 80
Cryptochecksum:d15d1b244e8dbb0dc5ded650f03d3333

8 replies

by blairh

I could be wrong, but I beleive that you are stepping into Pix 506E territory with what you are looking to do. I will try to find the documentation that I had, but I beleive that the 501 is not able to handle 2 Public IP's on its singele external interface.

by john.licalsi

Have tested you whether you can make a connection on the port by trying to telnet to port 21 for the .101 address?

Also, if you are using a passive ftp client, I believe you need to open port 20(ftp-data) as well.

by stoney

It seems like you are close to getting this to work. If I understand correctly, you are trying to send traffic directed to a public IP address inside your network. All you should do from here is add an access-list and point the outside traffic to the internal machine. You don't need to give the outside interface two public IP addresses. If you were issued 12 usuable IP addresses, pick one that's not being used, and direct that traffic to the inside, using ACL's. You aleady have the static commands. See how that works.

by kwicnet

Thank You for lending support to a lost PIX de-coder. Cisco's Document ID:12496 (on there web site) page 9 access-list 101 attached to the outside interface is what I am trying to implement. One of my problems is trying to test from a PC attached to the outside interface (I don't think it will work). In acl 101 the "any" key word is used, what is the difference between "any", "interface" and using the actual IP address in a acl like "access-list 101 permit tcp ANY host 172.18.124.99 eq telnet"? Also, I place the key words TELNET or FTP in the static (inside, outside) cmd it causes trouble. Should I not use these key words in the static for the desired outcome?
Thank you very much for the help. I will post my completed config when it works so the next person can use it as a learning tool.

by mcovitz

Since your access list is only allowing certain traffic to those IP's, I don't see a reason to put TELNET and FTP in the static mappings.

The only reason I could see to do that would be if you wanted to redirect traffic hitting one external IP to two different internal IP addresses, one for FTP and one for TELNET.

Otherwise, just do:

static (inside,outside) public_exchange inside_exchange netmask 255.255.255.255 0 0

by kwicnet

That explains why I can leave out the protocol type in the static. I thought the identification of protocols was required it both the static and access-list.

Thank you,

Kwicnet

by mcovitz

The way you have it setup now should work. At least it did on the 515e that we had.

That being said, you can add another IP (at least on the 515e) with the following command:

global (outside) 1 x.y.184.101

Hope that helps you.

This discussion is closed to new replies.