From owner-freebsd-stable Sun Jun 23 23:40: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id 4CC8937B489 for ; Sun, 23 Jun 2002 23:39:31 -0700 (PDT) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id 47DBF62D1A for ; Sun, 23 Jun 2002 23:39:27 -0700 (PDT) Date: Sun, 23 Jun 2002 23:44:35 -0700 (PDT) From: Lamont Granquist To: freebsd-stable@freebsd.org Subject: Did someone break TCP? In-Reply-To: <3D16A0B6.7010104@owt.com> Message-ID: <20020623233659.A15697-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've got an IRC server with a few days of uptime now after upgrading to both FBSD 4.6 and ircd-hybrid 6.3 out of the ports tree. Tonight I found that I couldn't login, TCP wasn't completing the 3-way handshake (no RST, no SYN|ACK). Stopping the service and restarting it fixed the problem. At this point it looks like TCP freaked out. I tried multiple different ways to login to the ircd, both remotely, from the local box and from behind the machine that it acts as a firewall for. All the users reported a 3+ hour outage prior to me finding the problem. There was nothing that I was doing to the box at the time. This has been previously stable hardware. Unfortunately, I didn't collect much better information than that... I'll try to do a better job if the reoccurs after I'm back from vacation... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message