<?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: ASA Syslog Event 106001 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-syslog-event-106001/m-p/898251#M973855</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is a connection-related message. This message occurs when an attempt to connect to an inside address is denied by your security policy. Possible tcp_flags values correspond to the flags in the TCP header that were present when the connection was denied. Indeed that means the conn table removed the connection. Such kind of messages are usually generated due to bad server kernel implementation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Oct 2007 16:55:58 GMT</pubDate>
    <dc:creator>didyap</dc:creator>
    <dc:date>2007-10-12T16:55:58Z</dc:date>
    <item>
      <title>ASA Syslog Event 106001</title>
      <link>https://community.cisco.com/t5/network-security/asa-syslog-event-106001/m-p/898250#M973853</link>
      <description>&lt;P&gt;I'm seeing a lot of events in our ASA logs for 106001 relating to external source TCP (port 80) connections being denied inbound to our PAT address. The sources are all valid web sites which users are accessing. If a source inside connects to a website outside, surely the return traffic will be permitted without needing any extra ACLs?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:22:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-syslog-event-106001/m-p/898250#M973853</guid>
      <dc:creator>jason.scott</dc:creator>
      <dc:date>2019-03-11T11:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Syslog Event 106001</title>
      <link>https://community.cisco.com/t5/network-security/asa-syslog-event-106001/m-p/898251#M973855</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is a connection-related message. This message occurs when an attempt to connect to an inside address is denied by your security policy. Possible tcp_flags values correspond to the flags in the TCP header that were present when the connection was denied. Indeed that means the conn table removed the connection. Such kind of messages are usually generated due to bad server kernel implementation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Oct 2007 16:55:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-syslog-event-106001/m-p/898251#M973855</guid>
      <dc:creator>didyap</dc:creator>
      <dc:date>2007-10-12T16:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Syslog Event 106001</title>
      <link>https://community.cisco.com/t5/network-security/asa-syslog-event-106001/m-p/898252#M973856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So the websites generating these messages are at fault rather than anything wrong with our configuration or something malicious?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Oct 2007 06:14:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-syslog-event-106001/m-p/898252#M973856</guid>
      <dc:creator>jason.scott</dc:creator>
      <dc:date>2007-10-15T06:14:45Z</dc:date>
    </item>
  </channel>
</rss>

