From owner-freebsd-stable Fri Oct 26 1:52:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 99FA837B406 for ; Fri, 26 Oct 2001 01:52:17 -0700 (PDT) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 3.33 #1) id 15x2ih-000OkT-00; Fri, 26 Oct 2001 09:52:03 +0100 To: drais@wow.atlasta.net, john_wilson100@excite.com Subject: Re: 4.4-STABLE machine unusable (was Re: Openssh) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: Message-Id: From: Pete French Date: Fri, 26 Oct 2001 09:52:03 +0100 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 seen this before, or something that sounds identical. telnet did the > same thing, and anything over a size i dont remember via http did it as > well. I've also seen this before - very recently. After a day and a half searching it turned out to be a bad port on the ether switch (and not the port I was connected too, one of the other ports affected the traffic). The switches themselves were suffering from someone in the buoilding getting a NIMDA virus which affected theswitches. Whether the two effects are related I dont know, but they happened in the order virus->switches start failing->broken port. Nimda can affect switches which have an IP address and a HTTP management interface as it sends overly long requests,. some buffer overflows and things start going pear shaped. Id check your ether connecctivity very carefully. -pcf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message