<?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: Skype &amp; unknown traffic in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/skype-unknown-traffic/m-p/39839#M29217</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Jørgen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is not currently a way to apply a security policy based on source port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please ensure you are running the latest application and content release as we are continually modifying the applications. In our latest release(311) the skype-probe application has been modified so updating may resolve your issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you continue to see skype identified as unknown-udp and unknown-tcp on the latest release, please gather packet captures of the traffic and open a support case so we may address the problem in a future application and content release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 07 Jun 2012 17:51:35 GMT</pubDate>
    <dc:creator>sspringer</dc:creator>
    <dc:date>2012-06-07T17:51:35Z</dc:date>
    <item>
      <title>Skype &amp; unknown traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/skype-unknown-traffic/m-p/39838#M29216</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello PAN,&lt;/P&gt;&lt;P&gt;It seems to me that in order to have skype working correctly - particually with multi-site PA's with Site2Site VPN tunnels in between - it is nessesarely to enable both unknown-tcp &amp;amp; unknown-udp.&lt;/P&gt;&lt;P&gt;At least - all our connection problems / delivery delays seems to go away whit the above allowed.&lt;/P&gt;&lt;P&gt;But obviously - allowing "unknown" traffic thru your firewall is not the most obvious solution......&lt;/P&gt;&lt;P&gt;A more soft solution could be if it's possible to define a private application/service where:&lt;/P&gt;&lt;P&gt;if client is connected to skype with src.port = x&lt;BR /&gt;then&lt;BR /&gt;allow unknown-tcp and unknown-udp where src.port = x&lt;/P&gt;&lt;P&gt;Does anyone know if this is possible somehow&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jørgen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2012 15:48:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/skype-unknown-traffic/m-p/39838#M29216</guid>
      <dc:creator>sitecore</dc:creator>
      <dc:date>2012-06-07T15:48:59Z</dc:date>
    </item>
    <item>
      <title>Re: Skype &amp; unknown traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/skype-unknown-traffic/m-p/39839#M29217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Jørgen,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is not currently a way to apply a security policy based on source port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please ensure you are running the latest application and content release as we are continually modifying the applications. In our latest release(311) the skype-probe application has been modified so updating may resolve your issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you continue to see skype identified as unknown-udp and unknown-tcp on the latest release, please gather packet captures of the traffic and open a support case so we may address the problem in a future application and content release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Jun 2012 17:51:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/skype-unknown-traffic/m-p/39839#M29217</guid>
      <dc:creator>sspringer</dc:creator>
      <dc:date>2012-06-07T17:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: Skype &amp; unknown traffic</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/skype-unknown-traffic/m-p/39840#M29218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Stefan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just confirmed that we are on ﻿311-1412 and we're experiencing the same problem.&amp;nbsp;&amp;nbsp; I have some logs and a pcap that I'll open a case with.&amp;nbsp; Although in my traffic analysis I noted that the unknown-tcp source ports did vary from the allowed skype and skype-probe packets.&amp;nbsp;&amp;nbsp; Specifically this is causing an interruption and non-delivery of chat messages in our case.&amp;nbsp;&amp;nbsp; The chat message time stamp will be replaced by "pending" when this occurs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Jun 2012 23:26:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/skype-unknown-traffic/m-p/39840#M29218</guid>
      <dc:creator>keitmi01</dc:creator>
      <dc:date>2012-06-08T23:26:06Z</dc:date>
    </item>
  </channel>
</rss>

