Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 May 1998 17:25:11 -0700 (PDT)
From:      Jim Shankland <jas@flyingfox.com>
To:        tlambert@primenet.com
Cc:        hackers@FreeBSD.ORG
Subject:   Re: TIME_WAIT/FIN_WAIT_2...
Message-ID:  <199805230025.RAA04614@biggusdiskus.flyingfox.com>

next in thread | raw e-mail | index | archive | help
> I think it's you that are mixed up... see the Apache FAQ on FIN_WAIT_2,
> and contact Paul Vixie, as I've suggested.

Let's assume that we mostly differ on terminology.  (I confess I get slightly
disoriented by phrases like, "Wait for the LAST-ACK," and "If you get
a CLOSE_WAIT" -- these being TCP states, not messages.  However, I
think I can figure out what you mean.)

You are, in effect, suggesting turning on a keepalive with a short
timeout (overriding the normal retry timer) whenever a connection is
in FIN_WAIT_2 and the socket is closed.  After 2 MSL in the state
"FIN_WAIT_2-and-the-socket-has-been-closed," you send a keepalive.  If
the peer responds with a RST, you tear the connection down.  If the
peer responds with its own FIN within the next 2 MSL, you go through
the normal close sequence.  If the peer doesn't respond at all, then
after the second 2MSL wait, you tear the connection down.You don't
state what you would do if the peer merely ACKs the keepalive;
presumably keep the connection up, and probe it again later (how much
later?) with another keepalive?

I dunno; might be marginally better than just tearing the connection
down after a few minutes.  CGEW.

btw, whoever it was who said, "Don't do this because rsh uses
half-open connections" -- you missed a key point.  None of this
applies if the application process still has the socket open.
This only applies when the application has entirely closed the
socket, so there's nobody there to receive any data that might
arrive.

Jim Shankland
Flying Fox Computer Systems, Inc.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805230025.RAA04614>