From owner-freebsd-security@FreeBSD.ORG Tue Apr 5 01:32: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 7BC2416A4CE for ; Tue, 5 Apr 2005 01:32:04 +0000 (GMT) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E9A543D5D for ; Tue, 5 Apr 2005 01:32:03 +0000 (GMT) (envelope-from jesper@hackunite.net) Received: from omikron.hackunite.net ([213.112.198.142] [213.112.198.142]) by mxfep01.bredband.com with ESMTP <20050405013202.ZTIQ25559.mxfep01.bredband.com@omikron.hackunite.net>; Tue, 5 Apr 2005 03:32:02 +0200 Received: from mail.hackunite.net (omikron.hackunite.net [127.0.0.1]) by omikron.hackunite.net (Postfix) with ESMTP id F2EB460CD; Tue, 5 Apr 2005 03:32:00 +0200 (CEST) Received: from 213.112.198.172 (SquirrelMail authenticated user z3l3zt@hackunite.net) by mail.hackunite.net with HTTP; Tue, 5 Apr 2005 03:32:01 +0200 (CEST) Message-ID: <1656.213.112.198.172.1112664721.squirrel@mail.hackunite.net> In-Reply-To: <20050404201428.C4511@odysseus.silby.com> References: <1614.213.112.198.172.1112663454.squirrel@mail.hackunite.net> <20050404201428.C4511@odysseus.silby.com> Date: Tue, 5 Apr 2005 03:32:01 +0200 (CEST) From: "Jesper Wallin" To: "Mike Silbersack" User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at mail.hackunite.net 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 Reply-To: jesper@hackunite.net 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 01:32:04 -0000 > > On Tue, 5 Apr 2005, Jesper Wallin wrote: > >> Dear list, >> >> A few days ago one of my machines were attacked by a DDoS-attack using >> UDP >> on random ports.. When I later on analyzed the logs, I found this in my >> dmesg: >> >> xl0: initialization of the rx ring failed (55) >> xl0: initialization of the rx ring failed (55) >> xl0: initialization of the rx ring failed (55) >> >> I tried to find out on google what it ment, but without any luck. What >> does that mean and how can I correct it (if it's a problem of course). >> >> >> Best regards, >> Jesper Wallin > > It means that we have a bug in the xl driver, probably nothing too > serious. Were there any other xl0 related messages, like "watchdog > timeout"? > > My guess is that we have a problem under high traffic conditions, and the > DDoS would qualify as that. > > Mike "Silby" Silbersack > 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