From owner-freebsd-current  Fri Feb  2 16:20:50 2001
Delivered-To: freebsd-current@freebsd.org
Received: from hera.drwilco.net (10dyn211.dh.casema.net [212.64.31.211])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2E48937B4EC; Fri,  2 Feb 2001 16:20:29 -0800 (PST)
Received: from ceres.drwilco.net (ceres.drwilco.net [10.1.1.19])
	by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f130h2b74340;
	Sat, 3 Feb 2001 01:43:03 +0100 (CET)
	(envelope-from drwilco@drwilco.net)
Message-Id: <4.3.2.7.0.20010202205233.00d51c30@mail.drwilco.net>
X-Sender: drwilco@mail.drwilco.net
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 02 Feb 2001 20:55:37 +0100
To: freebsd-current@freebsd.org, freebsd-net@freebsd.org
From: "Rogier R. Mulhuijzen" <drwilco@drwilco.net>
Subject: Patch for non-netgraph bridge code worthy of attention for
  people experimenting with bridging setups (including ng_bridge)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I found this while experimenting with both "legacy" bridge and ng_bridge. 
The bridging code doesn't check its activation everywhere so when I started 
using an ng_bridge node I started getting weird errors.

Patch is rather simple, can someone submit this?

         DocWilco

>Date: Mon, 29 Jan 2001 08:20:01 -0800 (PST)
>To: drwilco@drwilco.net
>From: gnats-admin@FreeBSD.org
>Subject: Re: kern/24720: Bridging code does not always check activation 
>(w/patch)
>Reply-To: gnats-admin@FreeBSD.org, freebsd-bugs@FreeBSD.org
>Sender: gnats@FreeBSD.org
>
>Thank you very much for your problem report.
>It has the internal identification `kern/24720'.
>The individual assigned to look at your
>report is: freebsd-bugs.
>
>You can access the state of your problem report at any time
>via this link:
>
>http://www.freebsd.org/cgi/query-pr.cgi?pr=24720
>
> >Category:       kern
> >Responsible:    freebsd-bugs
> >Synopsis:       Bridging code does not always check activation (w/patch)
> >Arrival-Date:   Mon Jan 29 08:20:01 PST 2001



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message