<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Pinging PIX Internal Interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216315#M595114</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you want to ping the internal interface from a network connected to another interface with a lower security level, then you need to create an access-list to allow the icmp traffic:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list test permit icmp any any&lt;/P&gt;&lt;P&gt;access-group test in interface &lt;NAME-OF-INTERFACE-FROM-WHERE-YOU-WANT-TO-PING&gt;&lt;/NAME-OF-INTERFACE-FROM-WHERE-YOU-WANT-TO-PING&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2004 20:13:11 GMT</pubDate>
    <dc:creator>tvanginneken</dc:creator>
    <dc:date>2004-01-26T20:13:11Z</dc:date>
    <item>
      <title>Pinging PIX Internal Interface</title>
      <link>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216314#M595113</link>
      <description>&lt;P&gt;Hi..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I ping a PIX internal interface from another network? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Actually I can ping the PIX Internal Interface from the same network that .e.g (mask 255.255.0.0)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pix Int. Interface: 10.100.5.12&lt;/P&gt;&lt;P&gt;My Ip : 10.100.0.75&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But at my PIX firewall I have another 5 interfaces that I must ping from my Tivoli Netview server, but I can do it because it's on another network. Also I can reach any host of these networks routed by PIX, so I don't have a routing problem...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried to use the &amp;lt;icmp&amp;gt; command with success.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Halan Leno&lt;/P&gt;&lt;P&gt;IT - Staff&lt;/P&gt;&lt;P&gt;Silvio Santos&lt;/P&gt;&lt;P&gt;Brazil&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:12:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216314#M595113</guid>
      <dc:creator>hleno</dc:creator>
      <dc:date>2020-02-21T07:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: Pinging PIX Internal Interface</title>
      <link>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216315#M595114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you want to ping the internal interface from a network connected to another interface with a lower security level, then you need to create an access-list to allow the icmp traffic:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list test permit icmp any any&lt;/P&gt;&lt;P&gt;access-group test in interface &lt;NAME-OF-INTERFACE-FROM-WHERE-YOU-WANT-TO-PING&gt;&lt;/NAME-OF-INTERFACE-FROM-WHERE-YOU-WANT-TO-PING&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Tom&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2004 20:13:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216315#M595114</guid>
      <dc:creator>tvanginneken</dc:creator>
      <dc:date>2004-01-26T20:13:11Z</dc:date>
    </item>
    <item>
      <title>Re: Pinging PIX Internal Interface</title>
      <link>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216316#M595115</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, this is not 100% accurate based on my understanding of the original post.  The above will work if you need to ping hosts off a lower security interface.  However, I believe the original poster is trying to ping the interface itself from a device located off of another interface.  If this is the case, you will not be able to do this.  This is by design and is part of the PIX ASA (Adaptive Security Algorithm).  Packets must ingress on one interface and egress another interface in order to be passed.  The PIX will not redirect packets back out the same interface where it was received.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This has caused a number of problems in other cases such as this.  So, I *think* this behavior is changing the in the 7.0 release of PIX which is due out the 2nd half of 2004.  I would recommend speaking with your local Cisco acct team to be sure.  Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2004 15:41:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216316#M595115</guid>
      <dc:creator>scoclayton</dc:creator>
      <dc:date>2004-01-27T15:41:36Z</dc:date>
    </item>
    <item>
      <title>Re: Pinging PIX Internal Interface</title>
      <link>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216317#M595116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The access-list that you've suggested already had been configured, by the way this is my PIX configuration...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;----------------------------------------------------&lt;/P&gt;&lt;P&gt;This is the access-list configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list acl_mdc_inside_access permit icmp any any  (interface 1)&lt;/P&gt;&lt;P&gt;access-list acl_mdc_gerencia_access permit icmp any any (interface 2)&lt;/P&gt;&lt;P&gt;access-list acl_mdc_andares_access permit icmp any any (interface 3)&lt;/P&gt;&lt;P&gt;access-list acl_mdc_sbt_access permit icmp any any  (interface 4)&lt;/P&gt;&lt;P&gt;access-list acl_mdc_utdcap_access permit icmp any any (interface 5)&lt;/P&gt;&lt;P&gt;access-list acl_mdc_pan_access permit icmp any any (interface 6)&lt;/P&gt;&lt;P&gt;----------------------------------------&lt;/P&gt;&lt;P&gt;This is the access-group configuration:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group acl_mdc_inside_access in interface inside&lt;/P&gt;&lt;P&gt;access-group acl_mdc_gerencia_access in interface gerencia&lt;/P&gt;&lt;P&gt;access-group acl_mdc_andares_access in interface andares&lt;/P&gt;&lt;P&gt;access-group acl_mdc_pan_access in interface pan&lt;/P&gt;&lt;P&gt;access-group acl_mdc_sbt_access in interface sbt&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;----------------------------------------------------&lt;/P&gt;&lt;P&gt;ip address outside 10.127.16.1 255.255.254.0&lt;/P&gt;&lt;P&gt;ip address inside 10.127.24.1 255.255.254.0&lt;/P&gt;&lt;P&gt;ip address gerencia 10.127.8.193 255.255.255.224&lt;/P&gt;&lt;P&gt;ip address andares 10.127.0.1 255.255.254.0&lt;/P&gt;&lt;P&gt;ip address sbt 10.127.8.1 255.255.255.224&lt;/P&gt;&lt;P&gt;ip address utdcap 10.100.6.12 255.255.0.0&lt;/P&gt;&lt;P&gt;ip address pan 10.127.7.65 255.255.255.224&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nameif ethernet0 outside security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;nameif ethernet2 gerencia security95&lt;/P&gt;&lt;P&gt;nameif ethernet3 andares security90&lt;/P&gt;&lt;P&gt;nameif ethernet4 sbt security50&lt;/P&gt;&lt;P&gt;nameif ethernet5 utdcap security60&lt;/P&gt;&lt;P&gt;nameif ethernet6 pan security70&lt;/P&gt;&lt;P&gt;nameif ethernet7 failover security35&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip address outside 10.127.16.1 255.255.254.0&lt;/P&gt;&lt;P&gt;ip address inside 10.127.24.1 255.255.254.0&lt;/P&gt;&lt;P&gt;ip address gerencia 10.127.32.1 255.255.254.0&lt;/P&gt;&lt;P&gt;ip address andares 10.127.0.1 255.255.254.0&lt;/P&gt;&lt;P&gt;ip address sbt 10.127.8.1 255.255.255.224&lt;/P&gt;&lt;P&gt;ip address utdcap 10.100.6.12 255.255.0.0&lt;/P&gt;&lt;P&gt;ip address pan 10.127.8.65 255.255.255.224&lt;/P&gt;&lt;P&gt;ip address failover 127.0.0.1 255.255.255.255&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g: From ip=10.127.33.3, I can't ping the PIX internal interface 10.100.6.12, but it is configured by acces-list: access-list acl_mdc_utdcap_access permit icmp any any (interface 5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Halan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Jan 2004 19:16:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-pix-internal-interface/m-p/216317#M595116</guid>
      <dc:creator>hleno</dc:creator>
      <dc:date>2004-01-27T19:16:25Z</dc:date>
    </item>
  </channel>
</rss>

