<?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: How does this connection attempt to reach internal device? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622603#M1090553</link>
    <description>&lt;P&gt;what is the&amp;nbsp; IP 10.239.36.133 ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jun 2022 14:26:12 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2022-06-01T14:26:12Z</dc:date>
    <item>
      <title>How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622588#M1090552</link>
      <description>&lt;P&gt;How does a connection from an internet device reach the firewall's outside interface with a connection to a private IP? It's blocked, but still concerning some since I don't have a static NAT for this device, etc.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 14:19:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622588#M1090552</guid>
      <dc:creator>Jack G</dc:creator>
      <dc:date>2022-06-01T14:19:01Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622603#M1090553</link>
      <description>&lt;P&gt;what is the&amp;nbsp; IP 10.239.36.133 ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 14:26:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622603#M1090553</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-06-01T14:26:12Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622604#M1090554</link>
      <description>&lt;P&gt;That's an internal server. There's a route on the firewall on how to get to that server.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 14:27:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622604#M1090554</guid>
      <dc:creator>Jack G</dc:creator>
      <dc:date>2022-06-01T14:27:47Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622609#M1090556</link>
      <description>&lt;P&gt;if that public routable IP, then do you have any rule block outside to inside ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 14:32:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622609#M1090556</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-06-01T14:32:30Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622612#M1090557</link>
      <description>&lt;P&gt;Yes, it's called block, also the default action would block it, but not sure how&amp;nbsp;&lt;SPAN&gt;10.239.36.133 is getting into the connection event.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 14:36:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622612#M1090557</guid>
      <dc:creator>Jack G</dc:creator>
      <dc:date>2022-06-01T14:36:38Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622816#M1090561</link>
      <description>&lt;P&gt;What is the IP of SB01MAG01 ?&lt;/P&gt;
&lt;P&gt;Are there any other NAT statements other than the three that you posted?&lt;/P&gt;
&lt;P&gt;My initial thought is that&amp;nbsp;&lt;SPAN&gt;10.239.36.133 sends some packets to a destination public IP which then redirects to 192.241.212.215.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 19:49:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622816#M1090561</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2022-06-01T19:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622820#M1090562</link>
      <description>&lt;P&gt;SB01MAG01 is 10.220.10.5, so that's not it. RAVPN is enabled on the outside interface which the connector was toward.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 19:54:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622820#M1090562</guid>
      <dc:creator>Jack G</dc:creator>
      <dc:date>2022-06-01T19:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622836#M1090563</link>
      <description>&lt;P&gt;I still suspect that a redirect is happening.&amp;nbsp; That&amp;nbsp;&lt;SPAN&gt;10.239.36.133 is sending to the internet via dynamic NAT and then whichever IP it sends to redirects to&amp;nbsp;192.241.212.215 and then the&amp;nbsp; return traffic does not match any existing connection and gets dropped.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jun 2022 20:23:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4622836#M1090563</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2022-06-01T20:23:24Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4623312#M1090584</link>
      <description>&lt;P&gt;I think is half-open DDoS if you see only SYN and there is no ACK.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H3&gt;""Protect Servers from a SYN Flood DoS Attack (TCP Intercept)&lt;/H3&gt;&lt;P class=""&gt;A SYN-flooding denial of service (DoS) attack occurs when an attacker sends a series of SYN packets to a host. These packets usually originate from spoofed IP addresses. The constant flood of SYN packets keeps the server SYN queue full, which prevents it from servicing connection requests from legitimate users.&lt;/P&gt;&lt;P class=""&gt;You can limit the number of embryonic connections to help prevent SYN flooding attacks. An embryonic connection is a connection request that has not finished the necessary handshake between source and destination.&lt;/P&gt;&lt;P class=""&gt;When the embryonic connection threshold of a connection is crossed, the ASA acts as a proxy for the server and generates a SYN-ACK response to the client SYN request using the SYN cookie method (see Wikipedia for details on SYN cookies). When the ASA receives an ACK back from the client, it can then authenticate that the client is real and allow the connection to the server. The component that performs the proxy is called TCP Intercept.&lt;/P&gt;&lt;P class=""&gt;The end-to-end process for protecting a server from a SYN flood attack involves setting connection limits, enabling TCP Intercept statistics, and then monitoring the results.""&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2022 13:20:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4623312#M1090584</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2022-06-02T13:20:29Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4623743#M1090594</link>
      <description>&lt;P&gt;If this was a DDoS attack the log would be flooded with SYN messages from the internet.&amp;nbsp; As the poster has not yet stated that this is the case I currently doubt that this is of concern.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jun 2022 06:59:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4623743#M1090594</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2022-06-03T06:59:24Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4624105#M1090597</link>
      <description>&lt;P&gt;we see only SYN not complete handshake, this is why I think it DDoS.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jun 2022 13:53:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4624105#M1090597</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2022-06-03T13:53:20Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4624686#M1090624</link>
      <description>&lt;P&gt;Fair enough, but a DDoS attack will have many more entries than just a few now and then, also it will have an affect on the firewall resources.&amp;nbsp; I think the subject of this post would have been different if this really was a DDoS.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Jun 2022 11:52:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4624686#M1090624</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2022-06-04T11:52:06Z</dc:date>
    </item>
    <item>
      <title>Re: How does this connection attempt to reach internal device?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4636134#M1091147</link>
      <description>&lt;P&gt;Appears to be a bug:&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy33676" target="_blank"&gt;CSCvy33676 : Bug Search Tool (cisco.com)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 19:55:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-this-connection-attempt-to-reach-internal-device/m-p/4636134#M1091147</guid>
      <dc:creator>Jack G</dc:creator>
      <dc:date>2022-06-21T19:55:54Z</dc:date>
    </item>
  </channel>
</rss>

