<?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: Ping outside interface from inside in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ping-outside-interface-from-inside/m-p/78328#M42908</link>
    <description>&lt;P&gt;Is there a security policy that allows pinging between the zones associated with those two interfaces?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;While pinging, try running "show counter global filter delta yes". &amp;nbsp;This should show you other reasons for packet drops (outside of policy). &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you using NAT? &amp;nbsp;Does your NAT policy translate the internal addresses to the external interface address? &amp;nbsp;(The one you're trying to ping?) &amp;nbsp;That may be the cause of the problem. &amp;nbsp;You could create a "no-nat" rule that bypasses NAT when the source is internal and the destination is the outside interface IP address. &amp;nbsp;Make sure this new policy is above your other NAT policy for outbound access. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 18 May 2016 18:10:01 GMT</pubDate>
    <dc:creator>jvalentine</dc:creator>
    <dc:date>2016-05-18T18:10:01Z</dc:date>
    <item>
      <title>Ping outside interface from inside</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-outside-interface-from-inside/m-p/78326#M42906</link>
      <description>&lt;P&gt;Can somebody explain how I would be able to ping the IP address on an untrusted interface from inside (trusted). I setup a interface management profile on the interface and I can ping the outside interface IP address from the public internet, but not from inside. I don't see any drops, and creating a policy has not seemed to help either.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm trying to do to troubleshoot something and not intended for long term usage.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2016 17:28:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-outside-interface-from-inside/m-p/78326#M42906</guid>
      <dc:creator>bbilut</dc:creator>
      <dc:date>2016-05-18T17:28:07Z</dc:date>
    </item>
    <item>
      <title>Re: Ping outside interface from inside</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ping-outside-interface-from-inside/m-p/78328#M42908</link>
      <description>&lt;P&gt;Is there a security policy that allows pinging between the zones associated with those two interfaces?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;While pinging, try running "show counter global filter delta yes". &amp;nbsp;This should show you other reasons for packet drops (outside of policy). &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Are you using NAT? &amp;nbsp;Does your NAT policy translate the internal addresses to the external interface address? &amp;nbsp;(The one you're trying to ping?) &amp;nbsp;That may be the cause of the problem. &amp;nbsp;You could create a "no-nat" rule that bypasses NAT when the source is internal and the destination is the outside interface IP address. &amp;nbsp;Make sure this new policy is above your other NAT policy for outbound access. &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2016 18:10:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ping-outside-interface-from-inside/m-p/78328#M42908</guid>
      <dc:creator>jvalentine</dc:creator>
      <dc:date>2016-05-18T18:10:01Z</dc:date>
    </item>
  </channel>
</rss>

