[En-Nut-Discussion] Numerous LASTACK
Jean Pierre Gauthier
jp.gauthier at wanadoo.fr
Mon Jun 14 03:18:24 CEST 2004
Despite the latest tcpsm.c (1.9.2.1.2.1 2004/04/15), tcpout (1.1.1.1.4.1
2004/04/15)and realtek driver nicrtl.c (Revision 1.6 2004/05/17 ), some
(<1%?) TCP client connections are not ended correctly and stay in LASTACK
state. Is that a TCP state machine bug / how to avoid this?
Jean Pierre
TRACE( httpd "Sockets" menu ):
Sockets
Handle Type Local Remote Status
8B3C TCP 192.168.0.102:80 192.168.0.201:1271 ESTABL
91CE TCP 192.168.0.102:6106 193.252.22.108:110 LASTACK
8A8A TCP 192.168.0.102:6099 195.68.47.19:80 LASTACK
583E TCP 192.168.0.102:6017 193.252.22.108:110 LASTACK
949F TCP 192.168.0.102:5992 217.12.6.8:80 LASTACK
88C8 TCP 192.168.0.102:5989 209.207.134.75:80 LASTACK
7C5E TCP 192.168.0.102:5988 193.252.117.130:80 LASTACK
7A4F TCP 192.168.0.102:5542 193.252.22.108:110 LASTACK
7D35 TCP 192.168.0.102:4105 217.12.6.8:80 LASTACK
More information about the En-Nut-Discussion
mailing list