OK - There must be something wrong with my config

[kooma]

This is my configuration. It works for basic traffic through the PIX 515 6.1(2). I get my internal traffic for internet in and out the firewall + my ping response works.

What my problem is any port or static route, telnet, vpn (pptp), SMTP, etc, I setup, nothing can route properly in and out.

For example if I add:

static (inside,outside) 192.168.10.70 172.16.32.14
conduit permit tcp host 192.168.10.70 eq ftp any
conduit permit tcp host 192.168.10.70 eq ftp-data any

I cannot get FTP traffic passing through the PIX...?..??


I must have a fundamental wrong or missing. Can someone please have a look and point me in the right direction? PIX Version 6.1(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 intf2 security50
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
domain-name xyz.com
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 1720
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
no fixup protocol smtp 25
names
pager lines 24
logging on
logging buffered debugging
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
mtu outside 1500
mtu inside 1500
mtu intf2 1500
ip address outside 192.168.10.70 255.255.255.0
ip address inside 172.16.32.254 255.255.0.0
ip address intf2 127.0.0.1 255.255.255.255
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 192.168.10.69 netmask 255.255.255.0
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
conduit permit icmp any any echo-reply
conduit permit icmp any any source-quench
conduit permit icmp any any unreachable
conduit permit icmp any any time-exceeded
route outside 0.0.0.0 0.0.0.0 192.168.10.65 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 si
p 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
http server enable
http 0.0.0.0 0.0.0.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
no sysopt route dnat
telnet timeout 5
ssh timeout 5
terminal width 80
Cryptochecksum:02ca204ed266efef2c4e4b314c2ef17c


Thanks in advance. This fixwall has been one up hill climb for me. Not to mention the 1000 hrs of troubleshooting.

 

[yizhar]

HI.

> ip address outside 192.168.10.70 255.255.255.0
So you're using private ip addresses for the pix outside, which means you probably have another NAT at the external router.
This is not good, and might be the cause for not being able to get to internal servers, unless you are trying to get from your private intranet to a department protected by the pix.

> conduit permit tcp host 192.168.10.70 eq ftp any
In pix ver 6.1, you should use the access-list command instead of the obsolue conduit command. Look here:

http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_61/cmd_ref/a.htm

> conduit permit tcp host 192.168.10.70 eq ftp-data any
In any case, no need to open ftp-data. The pix firewall inspects ftp traffic and opens additional ports as needed.

> ip address outside 192.168.10.70 255.255.255.0
> static (inside,outside) 192.168.10.70 172.16.32.14
Use a different ip address for the internal server then the pix own interface to avoid conflicts. For example:
ip address outside 192.168.10.70 255.255.255.0
static (inside,outside) 192.168.10.71 172.16.32.14

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar