A tcp socket does not respond for a SYN packet properly.
Issue
A tcp socket does not respond for a SYN packet properly, Then the socket receiving the SYN is TIME_WAIT.
Packet capture:
4061 2013-02-01 09:00:55.423794 192.168.0.1 192.168.0.2 TCP https > 57063 [FIN, ACK] Seq=2695690986 Ack=2835306979 Win=16 Len=0
4066 2013-02-01 09:00:55.437233 192.168.0.2 192.168.0.1 TCP 57063 > https [ACK] Seq=2835306979 Ack=2695690986 Win=65535 Len=0
4067 2013-02-01 09:00:55.437246 192.168.0.2 192.168.0.1 TCP 57063 > https [ACK] Seq=2835306979 Ack=2695690987 Win=65535 Len=0
4070 2013-02-01 09:00:55.460917 192.168.0.2 192.168.0.1 TLSv1 Encrypted Alert
4071 2013-02-01 09:00:55.461793 192.168.0.2 192.168.0.1 TCP 57063 > https [FIN, ACK] Seq=2835307002 Ack=2695690987 Win=65535 Len=0
4072 2013-02-01 09:00:55.461804 192.168.0.1 192.168.0.2 TCP https > 57063 [ACK] Seq=2695690987 Ack=2835307003 Win=16 Len=0
7646 2013-02-01 09:01:18.514561 192.168.0.2 192.168.0.1 TCP [TCP Port numbers reused] 57063 > https [SYN] Seq=1290965798 Win=65535 Len=0 MSS=1460 WS=0 TSV=2220310211 TSER=0
7647 2013-02-01 09:01:18.514574 192.168.0.1 192.168.0.2 TCP [TCP ACKed lost segment] https > 57063 [ACK] Seq=2695690987 Ack=2835307003 Win=16 Len=0
7685 2013-02-01 09:01:21.470302 192.168.0.2 192.168.0.1 TCP 57063 > https [SYN] Seq=1290965798 Win=65535 Len=0 MSS=1460 WS=0 TSV=2220313171 TSER=0
7686 2013-02-01 09:01:21.470315 192.168.0.1 192.168.0.2 TCP [TCP Dup ACK 7647#1] https > 57063 [ACK] Seq=2695690987 Ack=2835307003 Win=16 Len=0
netstat:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
:
tcp 0 0 192.168.0.1:443 0.0.0.0:* LISTEN 16669/httpd
:
tcp 0 0 192.168.0.1:443 192.168.0.2:57063 TIME_WAIT -
Environment
- Red Hat Enterprise Linux 5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.