From owner-freebsd-bugs Thu Oct 12 9: 7:37 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0277837B502; Thu, 12 Oct 2000 09:07:34 -0700 (PDT) Received: (from ru@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id JAA63001; Thu, 12 Oct 2000 09:07:34 -0700 (PDT) (envelope-from ru@FreeBSD.org) Date: Thu, 12 Oct 2000 09:07:34 -0700 (PDT) From: Message-Id: <200010121607.JAA63001@freefall.freebsd.org> To: kythorn@scorched.com, ru@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/13736: enabling NAT on 3.3RC results in panic sbappendaddr. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: enabling NAT on 3.3RC results in panic sbappendaddr. State-Changed-From-To: open->closed State-Changed-By: ru State-Changed-When: Thu Oct 12 09:02:19 PDT 2000 State-Changed-Why: Originator reports that the problem went away in the older releases: On Thu, Oct 12, 2000 at 11:57:31AM -0400, Jay Oliver wrote: > This problem ceased to exist sometime after I updated to the latest release. > I honestly can't say at this point which point on stable it went away, but > it did so. I'm currently using 4.1.1 without a problem, but I would like to > note the problem went away somewhere in the 3-STABLE series. While I'm not > an expert by any means, I believe it was an issue caused by the network > interface driver. This is also embarassing, but I can't remember which > interface it used to be. The cards are and always have been Linksys > LNE100TX's and the interface is currently dc0. I can remember that it wasn't > dc0 when I reported this problem, and as long as I upped and downed the > interfaces on a daily basis, I could have a workaround to the panic. I'm not > currently still doing this of course, but I can't pinpoint exactly when I > needed to stop. I neved upgraded to 3.5, so it must have been somewhere > between 3.3RC and 3.4-STABLE. Sorry I couldn't be more helpful, I was so > ecstatic when it finally went away, I guess I became a little lax in trying > to discover what had caused it. My aplogies. http://www.freebsd.org/cgi/query-pr.cgi?pr=13736 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message