From owner-freebsd-stable@FreeBSD.ORG Fri May 30 01:16:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3FE3106566B for ; Fri, 30 May 2008 01:16:03 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) Received: from mx1-a.inoc.net (mx1-a.inoc.net [64.246.131.30]) by mx1.freebsd.org (Postfix) with ESMTP id 8D0B28FC16 for ; Fri, 30 May 2008 01:16:03 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=inoc.net; h=Received:From:To:Subject:Date; b=YXSw5TDVt1WadKXfW2R4sLnObCZ797PJ0cEotjcM158tdhUbFsE/Q5bHhB083z7Mn5FOADopQoobNoDsgyA6BfyETghKVfSImwcJ/wjj5Juk2PqLQLM1l8i7X10bRpk2V2vT0FTfoI7ahfxOHrOb+29e/ZDSNArpUHdgvPg2j94=; Received: from [172.16.0.199] (cpe-67-240-119-200.nycap.res.rr.com [67.240.119.200]) by mx1-a.inoc.net (build v8.3.29) with ESMTP id 148556723-1941382 for multiple; Fri, 30 May 2008 01:15:58 +0000 (UTC) Message-Id: From: Robert Blayzor To: Matthew Dillon In-Reply-To: <200805300055.m4U0tkqx027965@apollo.backplane.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Thu, 29 May 2008 21:15:55 -0400 References: <1A19ABA2-61CD-4D92-A08D-5D9650D69768@mac.com> <23C02C8B-281A-4ABD-8144-3E25E36EDAB4@inoc.net> <483DE2E0.90003@FreeBSD.org> <483E36CE.3060400@FreeBSD.org> <483E3C26.3060103@paradise.net.nz> <483E4657.9060906@FreeBSD.org> <483EA513.4070409@earthlink.net> <96AFE8D3-7EAC-4A4A-8EFF-35A5DCEC6426@inoc.net> <483EAED1.2050404@FreeBSD.org> <200805291912.m4TJCG56025525@apollo.backplane.com> <14DA211A-A9C5-483A-8CB9-886E5B19A840@inoc.net> <200805291930.m4TJUeGX025815@apollo.backplane.com> <0C827F66-09CE-476D-86E9-146AB255926B@inoc.net> <200805292132.m4TLWhCv026720@apollo.backplane.com> <200805300055.m4U0tkqx027965@apollo.backplane.com> X-Mailer: Apple Mail (2.924) Cc: freebsd-stable@freebsd.org Subject: Re: Sockets stuck in FIN_WAIT_1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 May 2008 01:16:04 -0000 On May 29, 2008, at 8:55 PM, Matthew Dillon wrote: > It's got to a be a bug on the client(s) in question. I can't think > of anything else. You may have to resort to injecting a TCP RST > packet (e.g. via a TUN device) to clear the connections. That would be most unpleasant... and also seems like some sort of exploit if a client and run a server out of socket buffers so easily. On a side note, I may be onto something... The server traffic right now is calming down, but it picks up... I made a change to the IPFW rules which basically went from something like: 100 permit tcp from any to any established 200 permit tcp from any to me 80 setup 300 deny log ip from any to me to: 100 check-state 150 deny tcp from any to any established 200 permit tcp from any to me 80 setup keep-state 300 deny log ip from any to me While the traffic is lower now, I don't see the FIN_WAIT_1's going up like I did before. At least I'm not going to count my chickens before they hatch. I'm going to watch this over the next 24 hours and see what comes up. Unfortunately if it doesn't end up being part of the solution I may have to resort to running some flavor of Linux 2.6 (*sob*). -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net http://www.inoc.net/~rblayzor/