Date: Tue, 22 Aug 2000 15:18:15 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.ORG> To: Luigi Rizzo <luigi@info.iet.unipi.it> Cc: Tomas Hodan <tomas@hodan.sk>, freebsd-net@FreeBSD.ORG Subject: Re: bridging and freebsd crash Message-ID: <Pine.NEB.3.96L.1000822151452.5556F-100000@fledge.watson.org> In-Reply-To: <200008221527.RAA24348@info.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Aug 2000, Luigi Rizzo wrote: > > hi all, > > i have a problem with 4-stable. i'm using bridging with 3 ethernet adapters > > and when i set net.link.ether.bridge_ipfw to 1 after few second freebsd > > crash with panic. has this see anybody already ? > > Darren :) Well, Darren has seen it specifically in the context of bad (abuseive) packets, but I'd be interested in knowing whether there is another general bug in the bridging code, or whether it's a case of malformed packets confusing the ipfw code. Tomas, any chance of compiling the kernel with debugging symbols, dropping in options DDB, and giving us a stack trace at the kernel panic? I'm beginning to feel that we might want to revamp the current bridging framework, combining the best aspects of the current work with the some of the structural framework from the OpenBSD implementation. I haven't had time, recently having returned from a vacation, to look at this option seriously, however. Luigi, don't know if you have time or not, but I was wondering if you'd had a chance to look at the OpenBSD implementation, and if so, what your thoughts were with respects to it? It looks like they've used the ARP/route tables to maintain host location information, rather than a seperate bridge address cache, and that may have different performance and scalability properties, although combining the tables does substantially reduce the use of new data structures. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1000822151452.5556F-100000>