FOLLOWUP: Small problem with TCP socket opening

Ricky Beam (root@defiant.interpath.net)
Tue, 26 Aug 1997 00:23:21 -0400 (EDT)


Ok, here are the results of the packet capture...

Good connection and data transfer:
14:09:49.268372 199.72.252.1.2252 > 205.149.163.212.2056:
S 1404452004:1404452004(0) win 32767 <mss 1460> (DF)
14:09:49.388372 205.149.163.212.2056 > 199.72.252.1.2252:
S 124102570:124102570(0) ack 1404452005 win 8760 <mss 1460> (DF)
14:09:49.388372 199.72.252.1.2252 > 205.149.163.212.2056:
. ack 1 win 64240 (DF)
14:09:49.398372 199.72.252.1.2252 > 205.149.163.212.2056:
P 1:169(168) ack 1 win 64240 (DF)
14:09:49.718372 205.149.163.212.2056 > 199.72.252.1.2252:
. ack 169 win 8592 (DF)
14:09:53.848372 205.149.163.212.2056 > 199.72.252.1.2252:
P 1:169(168) ack 169 win 8592 (DF)
14:09:53.858372 199.72.252.1.2252 > 205.149.163.212.2056:
. ack 169 win 64240 (DF)
14:09:54.398372 199.72.252.1.2252 > 205.149.163.212.2056:
P 169:337(168) ack 169 win 64240 (DF)
14:09:54.658372 205.149.163.212.2056 > 199.72.252.1.2252:
. ack 337 win 8424 (DF)
14:10:04.738372 205.149.163.212.2056 > 199.72.252.1.2252:
P 169:337(168) ack 337 win 8424 (DF)
14:10:04.748372 199.72.252.1.2252 > 205.149.163.212.2056:
. ack 337 win 64240 (DF)
14:10:05.398372 199.72.252.1.2252 > 205.149.163.212.2056:
F 337:337(0) ack 337 win 64240 (DF)
14:10:06.188372 205.149.163.212.2056 > 199.72.252.1.2252:
F 337:337(0) ack 338 win 8424 (DF)
14:10:06.188372 199.72.252.1.2252 > 205.149.163.212.2056:
. ack 338 win 64240 (DF)

Connection Hung:
14:26:50.558372 199.72.252.1.2320 > 128.101.162.50.2056:
S 2424233590:2424233590(0) win 32767 <mss 1460> (DF)
14:26:53.558372 199.72.252.1.2320 > 128.101.162.50.2056:
S 2424233590:2424233590(0) win 64240 <mss 1460> (DF)
14:26:58.558372 199.72.252.1.2320 > 128.101.162.50.2056:
S 2424233590:2424233590(0) win 64240 <mss 1460> (DF)
14:26:58.728372 128.101.162.50.2056 > 199.72.252.1.2320:
. ack 2424233591 win 8760 (DF)
14:26:58.728372 199.72.252.1.2320 > 128.101.162.50.2056:
R 2424233591:2424233591(0) win 0

This would indicate a larger problem... it would appear, the remote system
got one of the SYNs but the SYN/ACK was lost. I get back a plain ACK, then
attempt to reset the connection, but no timeout gets set anywhere to clear
the stalemate. The process will never get any indication of trouble; it
calls 'connect()' never to return.

--Ricky