httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Murcko <ch...@topsail.org>
Subject Re: Netscape 3.0/Win95 doesn't have "Roy's" FIN_WAIT_2 problem
Date Thu, 30 Jan 1997 03:58:08 GMT
Marc Slemko wrote:
> 
> I'm not trying to say it does not leave the server with lots of
> FIN_WAIT_2s, but that does not mean it is the particular problem Roy
> noticed with keepalive timeouts.
> 
> It does tend to indicate that it is likely not entirely due to packets
> being dropped (but I wouldn't trust Win95 not to drop a packet on a good
> network, no matter how uncongested...) but I still think the RST thing is
> part of the problem.  But no, it doesn't look like it is the whole
> problem.
> 
> I've seen enough netstats to publish a book of 'em, but what _would_ be
> useful is a tcpdump output from a connection that hung.  That shouldn't be
> too hard to generate if you can reproduce the problem;  you just need to
> leave the tcpdump running for a while (say with a -w to a file) then later
> check to see a port number that is in FIN_WAIT_2 and find that in the
> tcpdump and pull it out.  That could help a lot if it says the right
> things.  A tcpdump on the proxy would be best, but anywhere on the segment
> would be fine.

I'll do that. I agree with you on tcpdump (that and netcat, and you can
debug *anything* to do with TCP/IP) and I'll try to get some data in the
next 3-5 days while I can still get to this network.
-- 
chuck
Chuck Murcko
The Topsail Group, West Chester PA USA
chuck@topsail.org

Mime
View raw message