From owner-freebsd-stable Mon Nov 13 16:35: 4 2000 Delivered-To: freebsd-stable@freebsd.org Received: from wyattearp.stanford.edu (wyattearp.Stanford.EDU [171.64.180.171]) by hub.freebsd.org (Postfix) with ESMTP id CB59F37B479 for ; Mon, 13 Nov 2000 16:35:00 -0800 (PST) Received: (from richw@localhost) by wyattearp.stanford.edu (8.9.3/8.9.3) id QAA64929; Mon, 13 Nov 2000 16:34:03 -0800 (PST) (envelope-from richw) Date: Mon, 13 Nov 2000 16:34:03 -0800 (PST) From: Rich Wales X-Sender: richw@wyattearp.stanford.edu To: freebsd-stable@freebsd.org Subject: Re: Bridging code in 4.2RC1 still not fixed Message-ID: <20001114002123.64508.richw@wyattearp.stanford.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marko Cuk wrote: > I installed 4.2RC1 from ISO and the bridging code in > conjuction with ipfw is still bad and it still crashes > machine after a few seconds of work. In case it will help any, I tried configuring a 3.4-RELEASE system as a bridge a few weeks ago, but it suffered random crashes too. The crashes were "fatal trap 12" (page fault while in kernel mode), in the routine in_cksum(), called from udp_input(). When I reconfigure the system to work as a conventional (non-bridge) IP router, it's solid as a rock. Again, I'm using 3.4-RELEASE; I do plan to upgrade to 4.something eventually, but not just yet. I posted this to comp.unix.bsd.freebsd.misc on October 14. I asked if anyone knew if the problem was fixed in the 4.* versions, but no one ever replied. I didn't submit a PR because the problem was with 3.4-RELEASE and I assumed no one would be interested in pursuing it. Rich Wales richw@webcom.com http://www.webcom.com/richw/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message