From owner-freebsd-hackers Thu Sep 27 13:53:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tsunami.acidpit.org (tsunami.acidpit.org [206.190.163.234]) by hub.freebsd.org (Postfix) with ESMTP id B7FAA37B40A for ; Thu, 27 Sep 2001 13:53:35 -0700 (PDT) Received: (from rch@localhost) by tsunami.acidpit.org (8.11.3/8.11.3) id f8RKrYd23767 for freebsd-hackers@freebsd.org; Thu, 27 Sep 2001 16:53:34 -0400 (EDT) (envelope-from rch@acidpit.org) Date: Thu, 27 Sep 2001 16:53:34 -0400 From: Robert Hough To: freebsd-hackers@freebsd.org Subject: ng_bridge Message-ID: <20010927165304.C23689@acidpit.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yesterday, I used a script on my bridge that pretty much brought down the entire network segment it was connected to. The script in question, was found in /usr/share/examples/netgraph -- called 'ether.bridge'. I modified the script, and ran it -- boom. Problems galore! At the time, the bridge did *not* function correctly. I was using a couple of cards that didn't support bridging. I have since corrected this, and on a smaller network repeated the same steps. This time, everything is working correctly. My question, is really this. Does anyone have an idea as to why this caused so much trouble to begin with, and how can I protect my network from allowing this to happen again? -- Robert Hough (rch@acidpit.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message