<?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: Traffic Question in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19981#M14559</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;David,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It could also be that the handshake is completed. However, there may not be enough data in the bytes written to the firewall for the Palo Alto to correspond to an application. RSYNC uses SSL encrypt and is typically initiated via SSH. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 12 May 2014 16:59:42 GMT</pubDate>
    <dc:creator>ZackCamp</dc:creator>
    <dc:date>2014-05-12T16:59:42Z</dc:date>
    <item>
      <title>Traffic Question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19980#M14558</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a customer who is unable to access a site over port_873. When searching the traffic I see that the Source IP to Destination IP are being allowed over port 873 but the application is showing as incomplete. Now, I understand that this indicates that the handshake is not being completed most likely due to the distant end, but there are still some anomalies that have me scratching my head.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The rule that I see this traffic hitting:&lt;/P&gt;&lt;P&gt;Source Zone:: Inside&amp;nbsp;&amp;nbsp;&amp;nbsp; Source: Any&amp;nbsp;&amp;nbsp; Destination Zone: Outside&amp;nbsp;&amp;nbsp; Destination: Any&amp;nbsp;&amp;nbsp; Application: SSL, Web-browsing&amp;nbsp;&amp;nbsp; Service: Any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why would this traffic be hitting this rule when it is over port_873? Could it be that the traffic initially starts as 80/443 and then converts to 873?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Port_873: rsync file synchronisation protocol (official)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 May 2014 13:43:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19980#M14558</guid>
      <dc:creator>DaveCorwin</dc:creator>
      <dc:date>2014-05-12T13:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic Question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19981#M14559</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;David,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It could also be that the handshake is completed. However, there may not be enough data in the bytes written to the firewall for the Palo Alto to correspond to an application. RSYNC uses SSL encrypt and is typically initiated via SSH. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 May 2014 16:59:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19981#M14559</guid>
      <dc:creator>ZackCamp</dc:creator>
      <dc:date>2014-05-12T16:59:42Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic Question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19982#M14560</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dave,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While you will initiate a connection for RSYNS application, the first few packets will choose the first available policy in the same direction, regardless of the application defined in the security-policy.&amp;nbsp; As soon as PAN firewall identifies the application signature of the packet &lt;SPAN class="GINGER_SOFTWARE_mark"&gt;( &lt;/SPAN&gt;App-ID), then it will switch into the appropriate security policy. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you enable logging&amp;nbsp; session for&amp;nbsp; "Log at session start" in the security policy, it will be able to see the same behavior in traffic logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 May 2014 18:04:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19982#M14560</guid>
      <dc:creator>HULK</dc:creator>
      <dc:date>2014-05-12T18:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: Traffic Question</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19983#M14561</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As Hulk mentions, the session starts with the first possible rule match.&amp;nbsp; In your case that is the application ssl rule.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should reorder you security policy list so that the specific rules like this one for the vpn appear first on the list.&amp;nbsp; This prevents the application based rules from accidentally kicking in on the traffic as is apparently happening here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 18 May 2014 11:42:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/traffic-question/m-p/19983#M14561</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-05-18T11:42:56Z</dc:date>
    </item>
  </channel>
</rss>

