<?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 sometimes the policy matched the multicast packets and sometimes it didn’t when each packet had the exact same source/dest IP and source/dest port? in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/sometimes-the-policy-matched-the-multicast-packets-and-sometimes/m-p/517326#M474</link>
    <description>&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;sometimes the policy matched the multicast packets and sometimes it didn’t when each packet had the exact same source/dest IP and source/dest port?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Some multicast traffic is allowed but other packets are denied. We need to understand why there is a difference.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-renderer-start-pos="98"&gt;In this case some multicast traffic was allowed by a policy that was not configured to allow multicast traffic. But other multicast traffic didn’t match the policy so it was evaluated by the remaining policies and dropped becuase there were not policies to allow that multicast traffic. For both groups the IP source and destination addresses and ports were identical.&lt;/P&gt;
&lt;P data-renderer-start-pos="98"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-renderer-start-pos="470"&gt;All of the multicast packets should have been denied. can some one explain why a different policy matched the multicast and permitted it.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Oct 2022 15:54:06 GMT</pubDate>
    <dc:creator>DJFirewallSupport</dc:creator>
    <dc:date>2022-10-10T15:54:06Z</dc:date>
    <item>
      <title>sometimes the policy matched the multicast packets and sometimes it didn’t when each packet had the exact same source/dest IP and source/dest port?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/sometimes-the-policy-matched-the-multicast-packets-and-sometimes/m-p/517326#M474</link>
      <description>&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;sometimes the policy matched the multicast packets and sometimes it didn’t when each packet had the exact same source/dest IP and source/dest port?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Some multicast traffic is allowed but other packets are denied. We need to understand why there is a difference.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-renderer-start-pos="98"&gt;In this case some multicast traffic was allowed by a policy that was not configured to allow multicast traffic. But other multicast traffic didn’t match the policy so it was evaluated by the remaining policies and dropped becuase there were not policies to allow that multicast traffic. For both groups the IP source and destination addresses and ports were identical.&lt;/P&gt;
&lt;P data-renderer-start-pos="98"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-renderer-start-pos="470"&gt;All of the multicast packets should have been denied. can some one explain why a different policy matched the multicast and permitted it.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Oct 2022 15:54:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/sometimes-the-policy-matched-the-multicast-packets-and-sometimes/m-p/517326#M474</guid>
      <dc:creator>DJFirewallSupport</dc:creator>
      <dc:date>2022-10-10T15:54:06Z</dc:date>
    </item>
  </channel>
</rss>

