Date: Tue, 14 Nov 2000 11:32:53 -0800 (PST) From: Stefan Molnar <stefan@csudsu.com> To: "Thomas T. Veldhouse" <veldy@veldy.net> Cc: Wilko Bulte <wkb@freebie.demon.nl>, Rich Wales <richw@webcom.com>, freebsd-stable@FreeBSD.ORG Subject: Re: Bridging code in 4.2RC1 still not fixed Message-ID: <Pine.BSF.4.21.0011141131360.10599-100000@clockwork.csudsu.com> In-Reply-To: <006101c04e71$0e25c080$c70b200a@FairIsaac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have not reviced the reboot, I have made my NMBCLUSTERS reall high. Linksys card are the ones I just replaced. I have not tried fxp on this config. No idea on IPFILTER tho On Tue, 14 Nov 2000, Thomas T. Veldhouse wrote: > I have the same problem with Linksys cards (10/100 TX - version 2.0 and > version 4.0) using the dc driver. I also had this problem with previous ISA > NE2000 cards using the ed driver. In both cases, right before the reboot, > everything would slow down and suddenly, I would hear a beep from the other > room as the box rebooted. I was never able to catch it in action. It > always happened with bridging AND ipfw. > > Will bridging work [better] with IPFILTER? > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "Stefan Molnar" <stefan@csudsu.com> > To: "Wilko Bulte" <wkb@freebie.demon.nl> > Cc: "Rich Wales" <richw@webcom.com>; <freebsd-stable@FreeBSD.ORG> > Sent: Tuesday, November 14, 2000 1:16 PM > Subject: Re: Bridging code in 4.2RC1 still not fixed > > > > > > 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 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0011141131360.10599-100000>