Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New to pix 515 please help

Status
Not open for further replies.

BK2002

MIS
Jul 16, 2002
2
US
I am newbie to pix and I try setup a pix firewall lab, somehow I can not ping from inside nor outside, but I can ping router successfully from the Pix. I read the cisco doc, by default I should be able to ping any where from inside network.Is there something that I missed ?

thanks in advance for any help.
BK.
here is my config.

PIX Version 6.2(1)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security50
nameif ethernet3 intf3 security15
nameif ethernet4 intf4 security20
nameif ethernet5 intf5 security25
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
names
pager lines 24
interface ethernet0 10baset
interface ethernet1 10baset
interface ethernet2 10baset
interface ethernet3 auto shutdown
interface ethernet4 auto shutdown
interface ethernet5 auto shutdown
mtu outside 1500
mtu inside 1500
mtu dmz 1500
mtu intf3 1500
mtu intf4 1500
mtu intf5 1500
ip address outside 192.168.1.10 255.255.255.0
ip address inside 10.1.1.3 255.255.255.0
ip address dmz 192.168.11.1 255.255.255.0
ip address intf3 127.0.0.1 255.255.255.255
ip address intf4 127.0.0.1 255.255.255.255
ip address intf5 127.0.0.1 255.255.255.255
ip audit info action alarm
ip audit attack action alarm
no failover
failover timeout 0:00:00
failover poll 15
failover ip address outside 0.0.0.0
failover ip address inside 0.0.0.0
failover ip address dmz 0.0.0.0
failover ip address intf3 0.0.0.0
failover ip address intf4 0.0.0.0
failover ip address intf5 0.0.0.0
pdm history enable
arp timeout 14400
global (outside) 1 xxx.xxx.xxx.130-xxx.xxx.xxx.254 netmask 255.255.255.0
nat (inside) 1 195.200.15.0 255.255.255.0 0 0
static (inside,outside) xxx.xxx.xxx.131 195.200.15.34 netmask 255.255.255.255 0 0

conduit permit icmp any any echo-reply
route outside 0.0.0.0 0.0.0.0 192.168.1.2 1
route inside 10.1.2.0 255.255.255.0 10.1.2.2 2
route inside 195.200.15.0 255.255.255.0 10.1.2.1 3
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
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
aaa-server LOCAL protocol local
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
---------
When I ping from the inside, I got this in debug

1407: Outbound ICMP echo request (len 56 id 2736 seq 43012) 195.200.15.34 > xxx.xxx.xx.131 > xxx.xxx.xx.21
-------
I notice there is no echo reply, Is there something that I need to configure?
 
HI.

This seems like an ip routing issue.

Check these lines:
ip address outside 192.168.1.10 255.255.255.0
global (outside) 1 xxx.xxx.xxx.130-xxx.xxx.xxx.254

In any case, all outside routers should know to route packets for xxx.xxx.xxx.yyy via the pix outside interface, or the global address should be in the same subnet of the pix outside and external router inside.

Please provide more details about your ip addressing and routing if you still have the problem.

Note - ping reply is blocked by default at the pix because of the seurity levels. You can allow it using

access-list fromoutside permit icmp any any
access-list fromoutside in interface outside

You should try TCP connections and not only ICMP, for example telnet from internal host to perimeter router.

Bye
Yizhar Hurwitz
 
Yizhar,

You are right!!!It is routing problem. I used the destination IP address ( xxx.xxx.xxx.130-xxx.xxx.xxx.254)which I wanted to ping for Global (outside) IP pools. I should have used 192.168.1.yyy. Since this is a lab, 192.168.1.yyy is okay for me.

Thank so much for your help.

BK
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top