From owner-freebsd-net Mon Jun 11 12:38:28 2001 Delivered-To: freebsd-net@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 3F8A637B40B; Mon, 11 Jun 2001 12:38:17 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f5BJb9o99898; Mon, 11 Jun 2001 14:37:10 -0500 (CDT) (envelope-from jlemon) Date: Mon, 11 Jun 2001 14:37:10 -0500 (CDT) From: Jonathan Lemon Message-Id: <200106111937.f5BJb9o99898@prism.flugsvamp.com> To: gjohnson@srrc.ars.usda.gov, net@freebsd.org, kris@freebsd.org Subject: Re: select fails to return incoming connect on FreeBSD-4.3 X-Newsgroups: local.mail.freebsd-net In-Reply-To: Organization: Cc: Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In article you write: >First off, I hope this is the right list. > >Could someone take a look at PR misc/27880? This was broken by the initial sequence number patch to TCP. When the server closes the socket, it puts the entry into the TIME_WAIT state. When a new SYN is received from the client while the socket is in this state, the new connection is only accepted if the new sequence number is > than the old one. Unfortunately, with a randomized seqence #, the new connection ISN may be less than the old sequence used, and the SYN will be ignored. I've copied this over to kris, who (IIRC) brought in the new sequence numbering. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message