<?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: unknown-tcp when tls decryption is enabled in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/unknown-tcp-when-tls-decryption-is-enabled/m-p/229464#M65969</link>
    <description>&lt;P&gt;I was able to resolve the issue by reconfiguring my lab environment. I did some creative routing to initially configure this how I needed it, but seems all of a sudden it was creating an issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I really should switch to a PA-220 lab unit &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 04 Sep 2018 21:23:18 GMT</pubDate>
    <dc:creator>ce1028</dc:creator>
    <dc:date>2018-09-04T21:23:18Z</dc:date>
    <item>
      <title>unknown-tcp when tls decryption is enabled</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unknown-tcp-when-tls-decryption-is-enabled/m-p/229324#M65925</link>
      <description>&lt;P&gt;I have a VM-100 in my lab. I haven't used it in while but recently booted it up and upgraded to 8.0.12.&amp;nbsp; I noticed a lot of unknown-tcp traffic for mostly any site when I enabled tls decryption.&amp;nbsp;If i disabled tls decryption, the traffic is all ssl.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have never seen this before.&amp;nbsp; I'm running it on esxi 5.5&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 02:59:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unknown-tcp-when-tls-decryption-is-enabled/m-p/229324#M65925</guid>
      <dc:creator>ce1028</dc:creator>
      <dc:date>2018-09-04T02:59:49Z</dc:date>
    </item>
    <item>
      <title>Re: unknown-tcp when tls decryption is enabled</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unknown-tcp-when-tls-decryption-is-enabled/m-p/229345#M65927</link>
      <description>&lt;P&gt;I've seen similar issue with inbound SSL decryption of activesync towards Exchange on PAN-OS 8.0.10. The session was first 'recognised' as unknown-tcp instead of activesync. Later we started getting decrypt error messages in logs. The certificate was correct and the supported cipher suites on server matched those on PA. Still researching this issue before opening a case.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 07:04:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unknown-tcp-when-tls-decryption-is-enabled/m-p/229345#M65927</guid>
      <dc:creator>santonic</dc:creator>
      <dc:date>2018-09-04T07:04:47Z</dc:date>
    </item>
    <item>
      <title>Re: unknown-tcp when tls decryption is enabled</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unknown-tcp-when-tls-decryption-is-enabled/m-p/229464#M65969</link>
      <description>&lt;P&gt;I was able to resolve the issue by reconfiguring my lab environment. I did some creative routing to initially configure this how I needed it, but seems all of a sudden it was creating an issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I really should switch to a PA-220 lab unit &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 21:23:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unknown-tcp-when-tls-decryption-is-enabled/m-p/229464#M65969</guid>
      <dc:creator>ce1028</dc:creator>
      <dc:date>2018-09-04T21:23:18Z</dc:date>
    </item>
  </channel>
</rss>

