06-01-2022 07:05 AM - edited 06-01-2022 07:19 AM
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.
06-01-2022 07:26 AM
what is the IP 10.239.36.133 ?
06-01-2022 07:27 AM
That's an internal server. There's a route on the firewall on how to get to that server.
06-01-2022 07:32 AM
if that public routable IP, then do you have any rule block outside to inside ?
06-01-2022 07:36 AM
Yes, it's called block, also the default action would block it, but not sure how 10.239.36.133 is getting into the connection event.
06-01-2022 12:49 PM
What is the IP of SB01MAG01 ?
Are there any other NAT statements other than the three that you posted?
My initial thought is that 10.239.36.133 sends some packets to a destination public IP which then redirects to 192.241.212.215.
06-01-2022 12:54 PM
SB01MAG01 is 10.220.10.5, so that's not it. RAVPN is enabled on the outside interface which the connector was toward.
06-01-2022 01:23 PM
I still suspect that a redirect is happening. That 10.239.36.133 is sending to the internet via dynamic NAT and then whichever IP it sends to redirects to 192.241.212.215 and then the return traffic does not match any existing connection and gets dropped.
06-02-2022 06:20 AM
I think is half-open DDoS if you see only SYN and there is no ACK.
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.
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.
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.
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.""
06-02-2022 11:59 PM
If this was a DDoS attack the log would be flooded with SYN messages from the internet. As the poster has not yet stated that this is the case I currently doubt that this is of concern.
06-03-2022 06:53 AM
we see only SYN not complete handshake, this is why I think it DDoS.
06-04-2022 04:52 AM
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. I think the subject of this post would have been different if this really was a DDoS.
06-21-2022 12:55 PM
Appears to be a bug: CSCvy33676 : Bug Search Tool (cisco.com)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide