<?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: we are running in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/4294023#M1078599</link>
    <description>&lt;P&gt;Another case where the ASA will display the message "terminated by inspection engine" is when the FTP server's reply to the PASV command (which the client sends) contains a different IP address than the packets are coming from.&amp;nbsp; When the ASA sees the packets coming from one IP address and the PASV reply contain a different address in the control response, this will fail inspection and the ASA will reset the connection.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Feb 2021 23:01:22 GMT</pubDate>
    <dc:creator>jhubel@midwave</dc:creator>
    <dc:date>2021-02-18T23:01:22Z</dc:date>
    <item>
      <title>TCP flow terminated by inspection Engine.</title>
      <link>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114502#M394928</link>
      <description>&lt;P&gt;Hi eveyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am seeing in log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;%ASA-4-507003: tcp flow from xx:192.168.x.x/41211 to outside:69.171.224.36/80 terminated by inspection engine, reason - inspector reset unconditionally.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need to undertsand what does this log mean?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MAhesh&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:29:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114502#M394928</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2019-03-12T00:29:50Z</dc:date>
    </item>
    <item>
      <title>TCP flow terminated by inspection Engine.</title>
      <link>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114503#M394939</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What version are you running?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you using a websense?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2012 01:21:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114503#M394939</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-29T01:21:43Z</dc:date>
    </item>
    <item>
      <title>TCP flow terminated by inspection Engine.</title>
      <link>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114504#M394951</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Julio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Version is &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco Adaptive Security Appliance Software Version 8.0(5)27&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes we are using websense&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2012 15:29:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114504#M394951</guid>
      <dc:creator>mahesh18</dc:creator>
      <dc:date>2012-11-29T15:29:10Z</dc:date>
    </item>
    <item>
      <title>TCP flow terminated by inspection Engine.</title>
      <link>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114505#M394961</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Mahesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Right now we are facing the issue with the websense on the other discussion , can we doble check that the websense is reachable from the ASA and then focus on this..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this bug ID:&lt;STRONG style="color: #000000; font-family: 'Times New Roman'; font-size: large;"&gt;&lt;A href="https://cdetsng.cisco.com/webui/#view=CSCsx79354"&gt;CSCsx79354&lt;/A&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Add url-block url-size, url-block url-mempool and add the filter command&lt;/P&gt;&lt;P&gt;with the cgi-truncate option&lt;/P&gt;&lt;P&gt;&lt;BR style="line-height: 11.199999809265137px; color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 11.199999809265137px; background-color: #ffffff;" /&gt;&lt;/P&gt;&lt;P&gt;ex:&lt;/P&gt;&lt;P&gt;filter url 0 0 0 0 cgi-truncate&lt;/P&gt;&lt;P&gt;url-block url-mempool 5&lt;/P&gt;&lt;P&gt;url-block url-size 4&lt;/P&gt;&lt;P&gt;&lt;BR style="line-height: 11.199999809265137px; color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 11.199999809265137px; background-color: #ffffff;" /&gt;&lt;/P&gt;&lt;P&gt;Even the though the page may load with the workaround above, the syslogs&lt;/P&gt;&lt;P&gt;(507003) may still continue to print.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So try the workaround as soon as you got the websense up ( if you keep getting those messages)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Nov 2012 17:16:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114505#M394961</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-29T17:16:02Z</dc:date>
    </item>
    <item>
      <title>we are running </title>
      <link>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114506#M394968</link>
      <description>&lt;P&gt;we are running&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Version 9.1(6) and we see the same error&amp;nbsp;&lt;/P&gt;
&lt;P&gt;any insight will be greatly appreciate it&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2015 17:26:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/2114506#M394968</guid>
      <dc:creator>pedro.sanchez</dc:creator>
      <dc:date>2015-11-10T17:26:55Z</dc:date>
    </item>
    <item>
      <title>Re: we are running</title>
      <link>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/4294023#M1078599</link>
      <description>&lt;P&gt;Another case where the ASA will display the message "terminated by inspection engine" is when the FTP server's reply to the PASV command (which the client sends) contains a different IP address than the packets are coming from.&amp;nbsp; When the ASA sees the packets coming from one IP address and the PASV reply contain a different address in the control response, this will fail inspection and the ASA will reset the connection.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2021 23:01:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tcp-flow-terminated-by-inspection-engine/m-p/4294023#M1078599</guid>
      <dc:creator>jhubel@midwave</dc:creator>
      <dc:date>2021-02-18T23:01:22Z</dc:date>
    </item>
  </channel>
</rss>

