From owner-freebsd-security@FreeBSD.ORG  Tue Apr  5 01:16:28 2005
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
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 D882016A4CE
	for <freebsd-security@freebsd.org>;
	Tue,  5 Apr 2005 01:16:28 +0000 (GMT)
Received: from relay02.pair.com (relay02.pair.com [209.68.5.16])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3AAC943D54
	for <freebsd-security@freebsd.org>;
	Tue,  5 Apr 2005 01:16:28 +0000 (GMT)	(envelope-from silby@silby.com)
Received: (qmail 35165 invoked from network); 5 Apr 2005 01:16:27 -0000
Received: from unknown (HELO localhost) (unknown)
  by unknown with SMTP; 5 Apr 2005 01:16:27 -0000
X-pair-Authenticated: 209.68.2.70
Date: Mon, 4 Apr 2005 20:16:21 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: Jesper Wallin <jesper@hackunite.net>
In-Reply-To: <1614.213.112.198.172.1112663454.squirrel@mail.hackunite.net>
Message-ID: <20050404201428.C4511@odysseus.silby.com>
References: <1614.213.112.198.172.1112663454.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]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2005 01:16:29 -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