<?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 Intermediate ASA-5525 breaks communication after 3-way handshake, Why? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/intermediate-asa-5525-breaks-communication-after-3-way-handshake/m-p/4772172#M1097679</link>
    <description>&lt;P&gt;Please view attached image. (**undocumented is that a Nexus 9k lives between the ASA and the "server".)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1. What might be the cause of the illustrated symptom?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2. Could this symptom be caused by the MSS inconsistency =1380 outbound vs.1460 inbound?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3. Could this symptom be caused by some kind of deep packet inspection? If so, how can I determine that?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Maybe this is relevant (I'm reading it right now) --&lt;STRONG&gt;&lt;A href="https://bluenetsec.com/asa-tcp-state-bypass/" target="_blank"&gt;Cisco ASA TCP State Bypass | Blue Network Security (bluenetsec.com)&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Feb 2023 15:44:55 GMT</pubDate>
    <dc:creator>MicJameson1</dc:creator>
    <dc:date>2023-02-09T15:44:55Z</dc:date>
    <item>
      <title>Intermediate ASA-5525 breaks communication after 3-way handshake, Why?</title>
      <link>https://community.cisco.com/t5/network-security/intermediate-asa-5525-breaks-communication-after-3-way-handshake/m-p/4772172#M1097679</link>
      <description>&lt;P&gt;Please view attached image. (**undocumented is that a Nexus 9k lives between the ASA and the "server".)&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1. What might be the cause of the illustrated symptom?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2. Could this symptom be caused by the MSS inconsistency =1380 outbound vs.1460 inbound?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3. Could this symptom be caused by some kind of deep packet inspection? If so, how can I determine that?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Maybe this is relevant (I'm reading it right now) --&lt;STRONG&gt;&lt;A href="https://bluenetsec.com/asa-tcp-state-bypass/" target="_blank"&gt;Cisco ASA TCP State Bypass | Blue Network Security (bluenetsec.com)&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2023 15:44:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intermediate-asa-5525-breaks-communication-after-3-way-handshake/m-p/4772172#M1097679</guid>
      <dc:creator>MicJameson1</dc:creator>
      <dc:date>2023-02-09T15:44:55Z</dc:date>
    </item>
    <item>
      <title>Re: Intermediate ASA-5525 breaks communication after 3-way handshake,</title>
      <link>https://community.cisco.com/t5/network-security/intermediate-asa-5525-breaks-communication-after-3-way-handshake/m-p/4772197#M1097680</link>
      <description>&lt;P&gt;I don't believe TCP state bypass would be the case here because if that was the case the 3-way handshake wouldn't have been completed, I wrote that post btw &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; From the attached image it does seem that after the 3-way handshake is completed the client doesn't start to send data to the server.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2023 16:13:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/intermediate-asa-5525-breaks-communication-after-3-way-handshake/m-p/4772197#M1097680</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2023-02-09T16:13:07Z</dc:date>
    </item>
  </channel>
</rss>

