pix 无法ping通外网 - 思科技术 - 51CTO技术论坛

社区导航: 专家门诊网络技术操作系统数据库程序设计系统应用考试认证 CIO及信息化站长交流综合交流下载基地 51CTO产品服务

【设为首页 | 收藏本站】

51CTO技术论坛» 思科技术 » pix 无法ping通外网 [ 打印] [ 订阅] [ 收藏] [ 推荐给朋友] [ 本帖文本页]

论坛跳转:

flinginsky
新新人类

帖子 70
精华 0
无忧币 0
积分 105
阅读权限 20

注册日期 2007-1-30

最后登录 2008-10-7

离线

[查看资料] [发短消息] [Blog]

发表于:2008-6-27 10:40　　标题：pix 无法ping通外网
＜上一帖 | 下一帖＞

公司有台pix防火墙，配置好之后，无法ping通外网但能够上网。配置在下面，请帮忙看看有什么问题。
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 9jNfZuG3TC5tCVH0 encrypted
passwd 9jNfZuG3TC5tCVH0 encrypted
hostname Firewall
domain-name ns-pdb.online.sh.cn
clock timezone gmt 8
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
no fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list acl_inside permit icmp any any
access-list acl_inside permit ip any any
access-list acl_outside permit icmp any any
access-list acl_outside permit tcp any host x.x.x.x eq www
access-list acl_outside permit tcp any host x.x.x.xeq 3389
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside x.x.x.x 255.255.255.248
ip address inside x.x.x.x 255.255.255.0
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
pdm location 0.0.0.0 0.0.0.0 outside
pdm location 0.0.0.0 0.0.0.0 inside
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
static (inside,outside) x.x.x.x x.x.x.x netmask 255.255.255.255 0 0
access-group acl_outside in interface outside
access-group acl_inside in interface inside
route outside 0.0.0.0 0.0.0.0 x.x.x.x1
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
aaa authentication ssh console LOCAL
ntp server 207.46.130.100 source outside prefer
http server enable
http 0.0.0.0 0.0.0.0 outside
http 192.168.1.0 255.255.255.0 inside
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
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 30
console timeout 0
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
Cryptochecksum:4e8bdedf5d4c9e83cd29d770a7e700f0
: end

论坛活动：测测你对IT技术大会的了解指数(赠微软礼品、无忧币)

2008-6-27 10:40

1楼

[ 顶部 ]

mbbwy

新新人类

帖子 20
精华 0
无忧币 52
积分 21
阅读权限 20

注册日期 2008-6-24

最后登录 2008-7-31

离线

[查看资料] [发短消息] [Blog]

发表于:2008-6-27 14:26　

在有PIX/ASA的网络环境下，ping不是一个很好的工具来测试网络的连接性。telnet和ftp更为可靠一些。因为ping/traceroute用的是icmp echo，即使你permit icmp any any，PIX也不会让echo通过的，因为Smurf攻击通常是用ICMP echo来实现的。

如果你一定要让ping/traceroute工作的话，试试：

access-list inbound permit icmp any host x.x.x.x echo (x.x.x.x是你的控制终端，最好不要用any来代替，否则会有安全隐患)
access-group inbound in interface outside

access-list outbound permit icmp any any echo-reply
access-list outbound permit icmp any any source-quench
access-list outbound permit icmp any any unreachable
access-list outbound permit icmp any any time-exceeded
access-group outbound in interface outside

论坛活动：测测你对IT技术大会的了解指数(赠微软礼品、无忧币)

2008-6-27 14:26

2楼

[ 顶部 ]

cnpfidc

技术员