From owner-freebsd-net  Thu Feb  8 21:58:18 2001
Delivered-To: freebsd-net@freebsd.org
Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.64.180.171])
	by hub.freebsd.org (Postfix) with ESMTP
	id AFD5037B401; Thu,  8 Feb 2001 21:58:00 -0800 (PST)
Received: (from richw@localhost)
	by wyattearp.stanford.edu (8.9.3/8.9.3) id VAA19427;
	Thu, 8 Feb 2001 21:57:33 -0800 (PST)
	(envelope-from richw)
Date: Thu, 8 Feb 2001 21:57:33 -0800 (PST)
From: Rich Wales <richw@webcom.com>
X-Sender: richw@wyattearp.stanford.edu
To: Luigi Rizzo <rizzo@aciri.org>
Cc: bmilekic@technokratis.com, luigi@FreeBSD.ORG,
	freebsd-net@FreeBSD.ORG
Subject: Re: Fw: if_ed.c && BRIDGE
In-Reply-To: <200102081735.f18HZY515166@iguana.aciri.org>
Message-ID: <20010209055043.19329.richw@wyattearp.stanford.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Luigi wrote:

    > Try the following patch: near line 2209 of if_ed.c
    > -       if ((len > sizeof(struct ed_ring)) &&
    > +       if ((len > ETHER_HDR_LEN + sizeof(struct ed_ring)) &&

I did, and it appears to avoid panics.  I downloaded 400 MB worth of
data just now, over my home DSL line, through a bridge cluster with
an "ed" card; the files were transferred correctly, and the bridge
didn't crash.

I got four "NIC memory corrupt - invalid packet length" messages.
Three of these messages reported a packet length of 18; one reported
a length of 10.

I'll try running my download test in a loop overnight and make sure
it doesn't crash.

Rich Wales         richw@webcom.com         http://www.webcom.com/richw/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message