Issue w/ allowing ping through PIX Firewall - No NAT

Hello,

I have a Cisco PIX firewall version 6.3 connected on one interface (eth1) to a linux PC (200.0.10.5 in subnet 200.0.10.0/24) and on the other (eth0) to a SoHo router (interface IP 200.0.11.2 in network 200.0.11.0/24 - behind the router is the network 200.0.12.0/24). I would like to allow ping through it and I don't want to perform NAT.

So I went on Cisco.com and did exactly what is described here: Two interfaces without NAT ... but I doesn't work.

Here is my config:

pixfirewall# sh ru
: Saved
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto shutdown
interface ethernet3 auto shutdown
interface ethernet4 auto shutdown
interface ethernet5 auto shutdown
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 intf2 security4
nameif ethernet3 intf3 security6
nameif ethernet4 intf4 security8
nameif ethernet5 intf5 security10
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
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
pager lines 24
logging buffered debugging
mtu outside 1500
mtu inside 1500
mtu intf2 1500
mtu intf3 1500
mtu intf4 1500
mtu intf5 1500
ip address outside 200.0.11.1 255.255.255.0
ip address inside 200.0.10.1 255.255.255.0
no ip address intf2
no ip address intf3
no ip address intf4
no ip address intf5
ip audit info action alarm
ip audit attack action alarm
no failover
failover timeout 0:00:00
failover poll 15
no failover ip address outside
no failover ip address inside
no failover ip address intf2
no failover ip address intf3
no failover ip address intf4
no failover ip address intf5
pdm history enable
arp timeout 14400
nat (inside) 0 200.0.11.0 255.255.255.0 0 0
conduit permit icmp any any
route outside 0.0.0.0 0.0.0.0 200.0.11.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
snmp-server community public
no snmp-server enable traps
no floodguard enable
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
Cryptochecksum:a6a630892bef2247cecfd7667cf871a9
: end



The LINK llights are ON.
The router is, I believe, properly configured.
Help please ?

Identity NAT appears to be miss-configured. Remove this command:

nat (inside) 0 200.0.11.0 255.255.255.0 0 0

And replace it with

nat (inside) 0 200.0.10.0 255.255.255.0 0 0

This should basically allow the linux PC to ping the Soho network, but NOT vise versa. If this doesn't work, try:

nat (inside) 0 0.0.0.0 0.0.0.0 0 0

If no use, give us more details including the config of the router.

Thank you for your answer, actually I figured out what the problem was.

Our firewall was a “standby” unit (back up firewall), so we had to define failover IP addresses.

failover ip address outside 200.0.11.3

failover ip address inside 200.0.10.2


After that we could ping the firewall from host 200.0.10.5 and vice-versa.

Have a nice day,
Sam.