kern/99188: [tcp] [patch] FIN in same packet as duplicate ACK is lost

[Staffan Ulfberg]

The following reply was made to PR kern/99188; it has been noted by GNATS.

From: Staffan Ulfberg <staffan at ulfberg.se>
To: bug-followup at FreeBSD.org
Cc:  
Subject: Re: kern/99188: [tcp] [patch] FIN in same packet as duplicate ACK is lost
Date: 20 Jun 2006 21:49:16 +0200

 I forgot to say that the Windows XP test code in the PR was compiled
 using the "cl" command line compiler from Microsoft Visual Studio.
 
 Anyway, when runnging the test code in the report, the following is a
 dump of the last packets captured by tcpdumpa dn presented by ethereal:
 
 No.     Time            Source                Destination           Protocol Info
     135 23:48:02.409915 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=122401 Ack=1 Win=65535 Len=1360
     136 23:48:02.409922 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=123761 Ack=1 Win=65535 Len=1360
     137 23:48:02.409926 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=125121 Ack=1 Win=65535 Len=1360
     138 23:48:02.409932 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=126481 Ack=1 Win=65535 Len=1360
     139 23:48:02.409936 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=127841 Ack=1 Win=65535 Len=1360
     140 23:48:02.409939 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=129201 Ack=1 Win=65535 Len=1360
     141 23:48:02.410012 10.0.3.5              172.22.32.206         TCP      1327 > 5000 [ACK] Seq=1 Ack=121041 Win=65535 Len=0
     142 23:48:02.410029 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=130561 Ack=1 Win=65535 Len=1360
     143 23:48:02.410033 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=131921 Ack=1 Win=65535 Len=1360
     144 23:48:02.410037 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [ACK] Seq=133281 Ack=1 Win=65535 Len=1360
     145 23:48:02.431375 10.0.3.5              172.22.32.206         TCP      1327 > 5000 [ACK] Seq=1 Ack=125121 Win=65535 Len=0
     146 23:48:02.431378 10.0.3.5              172.22.32.206         TCP      1327 > 5000 [ACK] Seq=1 Ack=127841 Win=65535 Len=0
     147 23:48:02.431380 10.0.3.5              172.22.32.206         TCP      1327 > 5000 [ACK] Seq=1 Ack=131921 Win=65535 Len=0
     148 23:48:02.431382 10.0.3.5              172.22.32.206         TCP      1327 > 5000 [ACK] Seq=1 Ack=134641 Win=65535 Len=0
     149 23:48:02.431384 10.0.3.5              172.22.32.206         TCP      1327 > 5000 [FIN, ACK] Seq=1 Ack=134641 Win=65535 Len=0
     150 23:48:02.431399 172.22.32.206         10.0.3.5              TCP      5000 > 1327 [PSH, ACK] Seq=134641 Ack=1 Win=65535 Len=1360
     151 23:48:02.647004 10.0.3.5              172.22.32.206         TCP      1327 > 5000 [ACK] Seq=2 Ack=136001 Win=65535 Len=0
     152 23:48:03.413573 10.0.3.5              172.22.32.206         TCP      1327 > 5000 [RST, ACK] Seq=2 Ack=136001 Win=0 Len=0
 
 10.0.3.5 was the client computer, and 172.22.32.206 was the server.
 
 After the session above, the socket on the server was in "ESTABLISHED" state.
 
 Staffan