From owner-freebsd-current Wed Jan 24 22:58:11 2001 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 1664B37B402 for ; Wed, 24 Jan 2001 22:57:54 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f0P6vaY27603; Wed, 24 Jan 2001 22:57:37 -0800 (PST) Date: Wed, 24 Jan 2001 22:57:36 -0800 (PST) From: Doug White To: Archie Cobbs Cc: Julian Elischer , "Thomas T. Veldhouse" , "Rogier R. Mulhuijzen" , freebsd-current@FreeBSD.ORG, vitaly@riss-telecom.ru Subject: Re: status of bridge code In-Reply-To: <200101250508.VAA04564@curve.dellroad.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Jan 2001, Archie Cobbs wrote: > Julian Elischer writes: > > > Is there any reasonable documentation or a HOWTO on the usage of netgraph? > > > I am currently using the standard bridging code and IPFIREWALL (ipfw) with > > > my dc cards. No problems so far - as long as I don't use DUMMYNET with it. > > > I really wish I could use DUMMYNET as I need to put bandwidth limits on a > > > few of the computers on my network. > > > > /usr/share/examples/netgraph > > man 4 netgraph > > man 4 ng_bridge > > (etc.) > > also a daemon-news article on how it works. > > http://www.daemonnews.org/200003/netgraph.html A small addendum to the Netgraph canon: Netgraph starts with a _clean_slate_. If this is your first time, make sure you define some endpoint first, then build on that. You don't have interfaces, sockets, nothin' to start with. Like a box of Legos and an empty table. :-) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message