<?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 debug Palo alto firewall rule in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/debug-palo-alto-firewall-rule/m-p/200217#M59255</link>
    <description>&lt;P&gt;we maintain one PA security policy rule&amp;nbsp;and give ip 192.168.0.11 to access server UTP01, the user is using ip 192.168.0.11, and he can't access the server, &amp;nbsp;we can't find any security log for this. may i know how to debug this rule?&lt;/P&gt;</description>
    <pubDate>Tue, 13 Feb 2018 15:11:49 GMT</pubDate>
    <dc:creator>palolili</dc:creator>
    <dc:date>2018-02-13T15:11:49Z</dc:date>
    <item>
      <title>debug Palo alto firewall rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/debug-palo-alto-firewall-rule/m-p/200217#M59255</link>
      <description>&lt;P&gt;we maintain one PA security policy rule&amp;nbsp;and give ip 192.168.0.11 to access server UTP01, the user is using ip 192.168.0.11, and he can't access the server, &amp;nbsp;we can't find any security log for this. may i know how to debug this rule?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2018 15:11:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/debug-palo-alto-firewall-rule/m-p/200217#M59255</guid>
      <dc:creator>palolili</dc:creator>
      <dc:date>2018-02-13T15:11:49Z</dc:date>
    </item>
    <item>
      <title>Re: debug Palo alto firewall rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/debug-palo-alto-firewall-rule/m-p/200231#M59256</link>
      <description>&lt;P&gt;for me the quickest and easiest way (via GUI) is to edit the interzone-default rule at the bottom of your policies.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;set the logging to session start.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you can then Monitor/Traffic and should see where the address 192.168.0.11&amp;nbsp; is trying to go to.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2018 15:46:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/debug-palo-alto-firewall-rule/m-p/200231#M59256</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2018-02-13T15:46:09Z</dc:date>
    </item>
    <item>
      <title>Re: debug Palo alto firewall rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/debug-palo-alto-firewall-rule/m-p/200232#M59257</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/83013"&gt;@palolili&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're not seeing any logs chances are the package is dropped before the security policy is evaluated (check the global counters).&lt;/P&gt;
&lt;P&gt;Chances are also that the package isn't reaching the firewall even ... get PCAPS to make sure that the packages sent from the client are reaching the firewall interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck !&lt;/P&gt;
&lt;P&gt;-Kiwi.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2018 15:52:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/debug-palo-alto-firewall-rule/m-p/200232#M59257</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2018-02-13T15:52:23Z</dc:date>
    </item>
  </channel>
</rss>

