What's new

Phantom SYN_SENT, 386.7_2

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Igor

Regular Contributor
I have two networks::
192.168.1.0/24
192.168.50.0/24. There are several Cisco switches in this network.

Networks are bidirectionally connected via OpenVPN on an Asus RT-AX68U fw. 386.7_2 router. There is a server (Smart Home) on the network 192.168.50.47. Another network has a disabled media-player 192.168.1.14.

I see a lot of messages in the logs of the Cisco switch:
Code:
A TCP SYN Attack was identified on port gi10.  TCP SYN traffic destined to the local system is automatically blocked for 60 seconds
in relation to the ports of the Asus router.
Analyzing the logs
Code:
router# netstat-nat | grep 'SYN_SENT'
I see 12 (+-1) permanent TCP SYN_SENT connections from 192.168.50.47 to 192.168.1.14:9529".

At the same time, there are no such requests from server to the host:
Code:
server$ netstat -na | grep '192.168.1.14'

Question: where does the constant TCP SYN_SENT come from on the Asus router?

P.S.
I am not suggesting that these two problems are related. Perhaps this is a coincidence.
 
The TCP SYN_SENT entries from netstat-nat will hang around for a while even after the source machine has given up and closed its socket. If you constantly refresh the netstat command on the source machine you should be able to catch them.
 
Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top