From owner-freebsd-stable Tue Feb 6 22:24:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120]) by hub.freebsd.org (Postfix) with SMTP id 05BFD37B4EC for ; Tue, 6 Feb 2001 22:24:34 -0800 (PST) Received: (qmail 82377 invoked from network); 7 Feb 2001 06:24:31 -0000 Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217) by proxy.outblaze.com with SMTP; 7 Feb 2001 06:24:31 -0000 Received: (qmail 30108 invoked by uid 500); 7 Feb 2001 06:28:53 -0000 Date: Wed, 7 Feb 2001 14:28:53 +0800 From: Yusuf Goolamabbas To: Joao Carlos Mendes Luis Cc: Luigi Rizzo , freebsd-net@FreeBSD.ORG, freebsd-stable@freebsd.org, phk@freebsd.org, dwmalone@FreeBSD.org Subject: Re: Solved: Bridging and dummynet seems to destroy dmesg output Message-ID: <20010207142853.A30058@outblaze.com> References: <200101312212.f0VMCHj08290@iguana.aciri.org> <3A79B707.3DF0B6D@jonny.eng.br> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <3A79B707.3DF0B6D@jonny.eng.br>; from jonny@jonny.eng.br on Thu, Feb 01, 2001 at 05:20:39PM -0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I cvsupped today and got all of Luigi's commit [the one where he does 1.16.2.13 of bridge.c alongwith a few others], I also have David Malone's fix to syslogd.c [1.59.2.5] If I don't have the following sysctl net.inet.ip.fw.verbose_limit=10 then dmesg gets busted as mentioned earlier and if I do a sync;reboot then I get a huge amount of ipfw messages scrolling on the console [It's as if they were backlogged in some buffer somewhere] and after a few seconds the syncing disk messages comes along I have the following in my kernel config options IPFIREWALL options IPFIREWALL_DEFAULT_TO_ACCEPT options BRIDGE options DUMMYNET my /etc/sysctl.conf is as follows net.link.ether.bridge_ipfw=1 net.link.ether.bridge=1 net.inet.ip.fw.verbose=1 net.inet.ip.fw.verbose_limit=10 > Luigi Rizzo wrote: > > > > > I tried only removing DUMMYNET from config, and the bug continues. Should > > > I try the changes below? > > > > no-they only affect dummynet. But this seems to suggest that > > the problem is unrelated to my changes... > > > > cheers > > luigi > > Hi, > > I found the problem! > > I started searching for the point where ipfw writes to the msgbuf, and > like all other kernel modules, it uses the log(9) function. But differently > from the other modules, ip_fw.c uses a LOG_SECURITY argument. I removed it, > recompiled, reboot, and BINGO! Probably the log(9) function does not expect a > facility parameter, as it is assumed to be LOG_KERNEL. > > Searching the cvsweb tree, I assume the changes that made it fail were > made to kern/subr_prf.c, and not directly to netinet/ip_fw.c. Probably a > longer search should be made to detect if any other call to log(9) uses this > approach. (CC: to phk, who made the change to kern/subr_prf.c, 1.61.2.1, at > 2000.01.16) > > Hoping this is the final solution and waiting for the cvs commit, thanks > to everybody, > > Jonny > > -- > João Carlos Mendes Luís jonny@embratel.net.br > Networking Engineer jonny@jonny.eng.br > Internet via Embratel jcml@ieee.org -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message