Jonathan Lemon wrote...
> On Nov 11, 1999 at 01:41:48PM +0100, Dag-Erling Smorgrav wrote:
> > Note that the state transition diagram in RFC793 does not specify a
> > timeout for the CLOSING -> TIME_WAIT transition, so any faithful
> > implementation of RFC793 has this bug (but why doesn't this hap
"Louis A. Mamakos" <[EMAIL PROTECTED]> writes:
> I think your interpretation of the TCP spec is in error. Since the FIN
> occupies sequence space, it's the same as unacknowledged data and should
> be retransmitted, just like any unacked data in the window would be.
> Eventually, the TCP stack s
> "Kenneth D. Merry" <[EMAIL PROTECTED]> writes:
> > Jonathan Lemon wrote...
> > > In article [EMAIL PROTECTED]> you
>write:
> > > > Before I spend a lot of time hunting this down, I figured it might be worth
> > > > asking -- is there any particular reason why TCP sockets may be getting
> > > >
On Nov 11, 1999 at 01:41:48PM +0100, Dag-Erling Smorgrav wrote:
> [bringing this back to -current, with a Bcc to -security]
>
> "Kenneth D. Merry" <[EMAIL PROTECTED]> writes:
> > Jonathan Lemon wrote...
> > > In article [EMAIL PROTECTED]> you
>write:
> > > > Before I spend a lot of time hunting
[bringing this back to -current, with a Bcc to -security]
"Kenneth D. Merry" <[EMAIL PROTECTED]> writes:
> Jonathan Lemon wrote...
> > In article [EMAIL PROTECTED]> you
>write:
> > > Before I spend a lot of time hunting this down, I figured it might be worth
> > > asking -- is there any particul
In article [EMAIL PROTECTED]> you write:
>
>Before I spend a lot of time hunting this down, I figured it might be worth
>asking -- is there any particular reason why TCP sockets may be getting
>stuck in the CLOSING state more often now?
Not sure. But here's a tcpdump trace of a socket that ends
On Thu, 4 Nov 1999, Kenneth D. Merry wrote:
>
> Before I spend a lot of time hunting this down, I figured it might be worth
> asking -- is there any particular reason why TCP sockets may be getting
> stuck in the CLOSING state more often now?
>
> I upgraded a machine from -current as of about J
Before I spend a lot of time hunting this down, I figured it might be worth
asking -- is there any particular reason why TCP sockets may be getting
stuck in the CLOSING state more often now?
I upgraded a machine from -current as of about June 26th to -current as of
last Friday (October 29th), an
