From owner-freebsd-isp Mon Jan 17 5:16: 1 2000 Delivered-To: freebsd-isp@freebsd.org Received: from velvet.sensation.net.au (tunnel0-velvet-brunswick.sensation.net.au [203.20.114.195]) by hub.freebsd.org (Postfix) with ESMTP id 67EFF14C85 for ; Mon, 17 Jan 2000 05:15:55 -0800 (PST) (envelope-from rowan@sensation.net.au) Received: from localhost (rowan@localhost) by velvet.sensation.net.au (8.8.8/8.8.8) with SMTP id AAA05067 for ; Tue, 18 Jan 2000 00:15:45 +1100 (EST) (envelope-from rowan@sensation.net.au) X-Authentication-Warning: velvet.sensation.net.au: rowan owned process doing -bs Date: Tue, 18 Jan 2000 00:15:43 +1100 (EST) From: Rowan Crowe To: freebsd-isp@freebsd.org Subject: RE: Bandwidth limiting on Switch. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 17 Jan 2000, Troy Settle wrote: > Something I've been meaning to ask... > > Can one monitor bandwidth as well as limit it with dummynet? Dummynet is part of (or configured via) ipfw, so you can just add in an identical 'count' ipfw rule... It would be handy if we could specify dummynet pipes as an interface, to prevent doubling up on ipfw rules (some dummynet implementations may have several ipfw rules feeding into a single pipe). eg: count ip from any to any via pipe 1 Thoughts? (I'm a bad C coder at best, and certainly not anywhere near good enough for kernel hacking :) ) Cheers. -- Rowan Crowe http://www.rowan.sensation.net.au/ Sensation Internet Services http://www.sensation.net.au/ Melbourne, Australia Phone: +61-3-9388-9260 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message