From owner-freebsd-net Mon Feb 4 6:43:51 2002 Delivered-To: freebsd-net@freebsd.org Received: from inje.iskon.hr (inje.iskon.hr [213.191.128.16]) by hub.freebsd.org (Postfix) with ESMTP id 5ABCE37B426 for ; Mon, 4 Feb 2002 06:43:43 -0800 (PST) Received: from tel.fer.hr (zg04-228.dialin.iskon.hr [213.191.137.229]) by mail.iskon.hr (8.11.4/8.11.4/Iskon 8.11.3-1) with ESMTP id g14EhRM26462; Mon, 4 Feb 2002 15:43:27 +0100 (MET) Message-ID: <3C5E9DFE.4AEB55BE@tel.fer.hr> Date: Mon, 04 Feb 2002 15:43:10 +0100 From: Marko Zec X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer , freebsd-net@freebsd.org Subject: Re: ng_dummy - netgraph traffic shaping node References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Julian Elischer wrote: > hmm interesting... > > any docs? > (we always include a man page when we commit a new node type.) As the code is still work in progress, writing manpages doesn't make too much sense before reaching a mature code state. Until then, I hope a basic howto included on the web page will do the job. > Any comments on netgraph in general I'm still catching the impressions right now, though I must admit the first banal thing I noticed I don't like is somewhat unconsistent hook naming (left/right, upper/lower, downstream/upstream etc.). Btw, where could I find some examples on parsing setsockopt() calls to selected nodes, if such thing is possible at all? Marko > On Fri, 1 Feb 2002, Marko Zec wrote: > > > The result of an innocent netgraph programming exercise can be found at: > > > > http://www.tel.fer.hr/zec/BSD/ng_dummy/ > > > > "ng_dummy" is a simple traffic shaper node that implements control of > > traffic flow in both upstream and downstream direction. In each > > direction, the traffic flows through the sequence of two FIFO-type > > queues, which implement different queuing policies. The "inbound" queue > > is rate limited, and emulates an interface output buffer. On "outbound" > > queue, frames are dequeued based on preconfigured delay, thus emulating > > propagation effects on a transmission link. Additional features include > > random frame discarding based on BER; and emulation of phantom traffic, > > which competes for available bandwidth, and thereby introduces inbound > > queue congestions and delay jitter. > > > > Have fun! > > > > Marko > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message