From owner-freebsd-security@FreeBSD.ORG Tue Apr 5 02:48:04 2005 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C0ED16A4CE for ; Tue, 5 Apr 2005 02:48:04 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id CD8B643D1F for ; Tue, 5 Apr 2005 02:48:03 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 76459 invoked from network); 5 Apr 2005 02:48:02 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 5 Apr 2005 02:48:02 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 4 Apr 2005 21:47:58 -0500 (CDT) From: Mike Silbersack To: Jesper Wallin In-Reply-To: <1656.213.112.198.172.1112664721.squirrel@mail.hackunite.net> Message-ID: <20050404214404.I4823@odysseus.silby.com> References: <1614.213.112.198.172.1112663454.squirrel@mail.hackunite.net> <1656.213.112.198.172.1112664721.squirrel@mail.hackunite.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-security@freebsd.org Subject: Re: Strange messages in dmesg after DDoS-attack. X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2005 02:48:04 -0000 On Tue, 5 Apr 2005, Jesper Wallin wrote: > Hi Mike, > > First of all, thanks for your reply.. Nope, as far as I can see, I only > got 6 of those lines and nothing more. > > I have a fxp0 in my other server, would you recommend me to switch the > NICs since the server using the xl0 got higher priority than the fxp0 one? > > > Regards, > Jesper Wallin All network cards/drivers have some bugs in them, so as long as the 3com card survived the DDoS and didn't require the interface to be restarted, I'd stick with it. I think I found how those messages appeared, xl_init is called whenever the card sets the flag "ADFAIL", whatever that means. Apparently it's bad and the network driver resets itself when it happens. So, you're probably losing a few packets as a result of the reset, but other than that I don't see it causing any real problems. Mike "Silby" Silbersack