From owner-freebsd-stable Tue Nov 14 11:16:37 2000 Delivered-To: freebsd-stable@freebsd.org Received: from clockwork.csudsu.com (clockwork.csudsu.com [209.249.57.100]) by hub.freebsd.org (Postfix) with ESMTP id BAB0537B479 for ; Tue, 14 Nov 2000 11:16:32 -0800 (PST) Received: from localhost (stefan@localhost) by clockwork.csudsu.com (8.9.3/8.9.3) with ESMTP id LAA91001; Tue, 14 Nov 2000 11:16:12 -0800 (PST) (envelope-from stefan@csudsu.com) Date: Tue, 14 Nov 2000 11:16:12 -0800 (PST) From: Stefan Molnar To: Wilko Bulte Cc: Rich Wales , freebsd-stable@FreeBSD.ORG Subject: Re: Bridging code in 4.2RC1 still not fixed In-Reply-To: <20001114074905.B333@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had bridging plus ipfw working in 4.0-R to 4.1-S for some time. I only had it crash when I used a tulip card (de0), I used dc0 for the setup. It did go to a slow crawl, and figured out it was the cards themself, it would goto a crawl with just nat. I do not have it running currently. What cards are you using? Stefan On Tue, 14 Nov 2000, Wilko Bulte wrote: > On Mon, Nov 13, 2000 at 04:34:03PM -0800, Rich Wales wrote: > > 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. > > That is not a really valid assumption. But I agree that the focus is on 4.x > and -current. Bugs reported on 3.x are crosschecked (by most committers) to > the 4.x codestream. > > I strongly suggest to sendpr the problem against 4.2-beta! > > -- > Wilko Bulte Arnhem, the Netherlands > wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message