Re: PIX 501 routing issues
- From: "Mike W." <wallmrnospam@xxxxxxxxx>
- Date: Thu, 28 Jun 2007 19:40:23 GMT
You need to allow those pings that you send out back in. I am certain they are going out, they're just not being allowed back in by the firewall.
Try adding the following commands:
access-list outside_access_in permit icmp any any echo-reply
access-group outside_access_in in interface outside
HTH
Justin wrote:
Good day to everyone..
I have been toying with a PIX 501 running v. 6.3(5) and have run into
a routing issue. The configuration for this unit is very basic at
this time. All it is intended to do is stand as the gateway to the
internet and allow traffic out while blocking most outside traffic.
Eventually it will be one end of a dedicated VPN tunnel but I need it
to be able to pass information to the internet for right now.
Internal devices (configured with the PIX as the gateway) can ping the
inside interface of the PIX but not the outside. The PIX can ping
devices on the inside and the outside, including successful ping
replies from internet servers. Traceroute commands have the same
results.
If anyone can spot what I may be missing and offer a suggestion of a
fix, I would be greatly appreciative.
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname drtest
domain-name nonetospeakof.org
clock timezone CST -6
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
icmp permit 172.16.0.0 255.255.0.0 inside
icmp permit 10.10.10.0 255.255.255.0 inside
mtu outside 1500
mtu inside 1500
ip address outside 63.225.175.115 255.255.255.224
ip address inside 10.10.10.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 172.16.0.0 255.255.0.0 inside
pdm location 0.0.0.0 255.255.255.224 outside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 63.225.175.113 1
timeout xlate 0:05: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
http server enable
http 10.10.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 10.10.10.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
console timeout 10
terminal width 80
banner motd Unauthorized access is strictly prohibited.
Cryptochecksum:f333d02c5a5d110ec76c7c460a896519
- Follow-Ups:
- Re: PIX 501 routing issues
- From: Justin
- Re: PIX 501 routing issues
- References:
- PIX 501 routing issues
- From: Justin
- PIX 501 routing issues
- Prev by Date: Re: VPN Client 4.8 - how to trouble shoot
- Next by Date: Re: PIX 501 routing issues
- Previous by thread: PIX 501 routing issues
- Next by thread: Re: PIX 501 routing issues
- Index(es):
Relevant Pages
|
