Could you explain why this is the case?
You can do it with a router !! :-)
- Original Message -
From: Lidiya White
To:
Sent: Tuesday, April 09, 2002 11:53 PM
Subject: RE: PIX problem [7:40928]
You'll never be able to ping interface of the PIX that is not directly
connected
, April 10, 2002 2:17 AM
To: Lidiya White
Cc: [EMAIL PROTECTED]
Subject: Re: PIX problem [7:40928]
Could you explain why this is the case?
You can do it with a router !! :-)
- Original Message -
From: Lidiya White
To:
Sent: Tuesday, April 09, 2002 11:53 PM
Subject: RE: PIX problem [7
Hi!
See http://www.cisco.com/warp/customer/110/31.html
According to this document Inbound ICMP through the PIX is denied by
default; outbound ICMP is permitted, but the incoming reply is denied by
default. So you can ping every PIX interface from the PIX and from the
directly connected LAN,
: Tuesday, April 09, 2002 4:04 PM
Subject: Re: PIX problem [7:40928]
Hi!
See http://www.cisco.com/warp/customer/110/31.html
According to this document Inbound ICMP through the PIX is denied by
default; outbound ICMP is permitted, but the incoming reply is denied by
default. So you can ping
Kent!
You can ping through the PIX (from E0 NET to E1 net (10.222.62.0) if you
permit this with an access-list statement (conduit in earlier release). You
can ping the PIX' interface from the directly connetced net, if you didn't
disabeled that feature with the icmp command. You can't ping
: Tuesday, April 09, 2002 10:14 AM
To: [EMAIL PROTECTED]
Subject: Re: PIX problem [7:40928]
Thanks for the input, I have allowed the required icmp access ...
To try and clarify ...
I'm trying to ping the pix interface E1 (ip address 10.222.62.1) through
pix
interface E0 (ip address 10.222.33.1) from
6 matches
Mail list logo
