Frustrating PIX

[jce001]

I've posted a few message here trying to get help setting up a new pix. Thanks to everyone and every post, it really helped. I thought I had everything all figured out. Now, when I plug the pix in and turn the old linux server off, noone can get internet. It's a Pix506e. Plugs into a 2621 router. It is handling dhcp and vpn. I've checked the config to numerous others, and can't find the error. I'm including the config. PLEASE HELP. Thanks.

Building configuration...
: Saved
:
PIX Version 6.3(1)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password SXvq7P8buC7GW0tb encrypted
passwd 7arcFHBCVf3ZofMH encrypted
hostname firewall
domain-name millstl.com
clock timezone CST -6
clock summer-time CDT recurring
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
names
no pager
mtu outside 1500
mtu inside 1500
ip address outside 64.242.49.194 255.255.255.192
ip address inside 192.168.25.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.25.240 255.255.255.255 inside
pdm history enable
arp timeout 14400
global (outside) 1 64.242.49.197-64.242.49.254 netmask 255.255.255.192
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 64.242.49.193 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 RADIUS protocol radius
aaa-server LOCAL protocol local
http server enable
http 192.168.25.240 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
tftp-server inside 192.168.25.240 root
floodguard enable
sysopt connection permit-ipsec
telnet 192.168.25.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.25.30-192.168.25.230 inside
dhcpd dns 192.168.25.1 204.194.10.206
dhcpd lease 432000
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
Cryptochecksum:6492a14bd35192d06de914895f52bc6d
: end
[OK]

 

[baddos]

Ethernet0 is plugged into the 2621?

Also, please post a "show interfaces" from the PIX.

Are your internal clients getting the proper DHCP lease information?

 

[jce001]

Ethernet0 is plugged into the 2621.
DHCP works great.
I'll get the "show interfaces" in a few.

 

[jce001]

interface ethernet0 "outside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000d.2857.62c9
IP address 64.242.49.194, subnet mask 255.255.255.192
MTU 1500 bytes, BW 100000 Kbit full duplex
17 packets input, 3908 bytes, 0 no buffer
Received 23 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1 packets output, 60 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
1 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/1)
output queue (curr/max blocks): hardware (0/1) software (0/1)
interface ethernet1 "inside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000d.2857.62ca
IP address 192.168.25.1, subnet mask 255.255.255.0
MTU 1500 bytes, BW 100000 Kbit full duplex
19 packets input, 4108 bytes, 0 no buffer
Received 25 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1 packets output, 60 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
1 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/1)
output queue (curr/max blocks): hardware (0/1) software (0/1)

 

[jce001]

here's another strange problem. Both interfaces show up, but I can't ping the router. Anyone have any ideas why?

 

[baddos]

You should be able to ping the router from the PIX's console. If you can't, then there is a problem. By default you won't be able to ping through the firewall though.

 

[jce001]

Don't mean to be a smart axx, but I know there is a problem. The real problem is that I can't figure it out. I can't figure out why I can't ping the router from the firewall. I do need to update one thing the firewall is plugged into a switch, and so is the router. I have checked the switch, and it has no vlans or anything to stop traffic.

 

[baddos]

Can you do a show interface of your router?

 

[jce001]

GOT IT, GOT IT. Sometimes the smallest things cause the BIGGEST problems. DNS server was down, and didn't know it. I can ping the router now from a telnet interface, but not from a console, Baddos can you explain? Also, I can't telnet to my router. What line do I need to add to my pix to allow telnet traffic? Thanks a million for your help.

 

[havanajoe]

The line that you need to enter on the pix to allow you to ping and get responses back to the pix console is...

ICMP permit any echo-reply outside

 

[yizhar]

HI.

Here are some general notes - not only related to the original problems.

> Now, when I plug the pix in and turn the old linux server off
You've already solved the problem, but anyway remember that if you replace firewalls you should reboot the router or clear its ARP cache from the router command line.

> global (outside) 1 64.242.49.197-64.242.49.254 netmask 255.255.255.192
How many internal hosts do you have?
If there are more then 50, then you should add:
global (outside) 1 64.242.49.196
So when the NAT pool is full, it will use the above address for PAT.

> What line do I need to add to my pix to allow telnet traffic
The pix will allow outbound telnet traffic by default, but will block inbound connections.
The following links can help you:

http://www.cisco.com/warp/public/707/28.html

But note that some obsolute commands presented in the link like "conduit" are for backward compatibility only and should not be used in new configs.

Here are 2 more:

http://www.cisco.com/pcgi-bin/Support/browse/psp_view.pl?p=Hardware:PIX&s=Software_Configuration

http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/

It's now time for you to start using syslog messages at the pix. These are very usefull for managing and troubleshooting the pix.


Yizhar Hurwitz

http://come.to/yizhar

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