From owner-freebsd-net@FreeBSD.ORG Thu Feb 15 21:11:41 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EAA1D16A401 for ; Thu, 15 Feb 2007 21:11:41 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7E74413C4A5 for ; Thu, 15 Feb 2007 21:11:41 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1277990nfc for ; Thu, 15 Feb 2007 13:11:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XUT+ZCx12VY+xZrZ9jO0L5lPJM+wsBLcz18g1+5Mg/7ZlZrHAIZv7vzjreeMe8yp+kYBWzVaQoiNPynAIujB5lZrJ4llToLcdNegk5EcoRgWM/s/ggagBd6Oov6K3rS1hn+rXX99xoqXG7lriEDhH4CqYIK1Vo50NbkwnXvgcaI= Received: by 10.82.160.2 with SMTP id i2mr3606225bue.1171573118942; Thu, 15 Feb 2007 12:58:38 -0800 (PST) Received: by 10.82.151.15 with HTTP; Thu, 15 Feb 2007 12:58:38 -0800 (PST) Message-ID: Date: Thu, 15 Feb 2007 12:58:38 -0800 From: "Kip Macy" To: "John Polstra" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-net@freebsd.org Subject: Re: bge0: discard frame w/o packet header X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 21:11:42 -0000 > > The "discard frame w/o packet header" message comes from ether_input() > if it gets an mbuf that doesn't have the M_PKTHDR flag set. That > can't happen unless something is very wrong with the system. I'd like > to make it a panic. At least then the machine would reboot instead of > just becoming unreachable. Any objections? Please don't make it the default. Odds are ifconfig down, ifconfig up would fix it for those of us with console access. Either way it sounds like someone has discovered a DOS in bge. -Kip