Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Dec 2008 12:30:02 -0500
From:      George Nevill-Neil <gnn@neville-neil.com>
To:        Julian Elischer <julian@elischer.org>
Cc:        gnn@freebsd.org, Luigi Rizzo <rizzo@iet.unipi.it>, net@freebsd.org
Subject:   Re: A new tool for low level testing...
Message-ID:  <3BE32C00-3AF8-4C8F-B48D-45F50D55A2B2@neville-neil.com>
In-Reply-To: <495290EF.6020400@elischer.org>
References:  <7ihc4u3adr.wl%gnn@neville-neil.com> <4951515C.4030706@elischer.org> <495215A6.2040002@oltrelinux.com> <20081224111546.GA59523@onelab2.iet.unipi.it> <495290EF.6020400@elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Dec 24, 2008, at 2:43 PM, Julian Elischer wrote:

> Luigi Rizzo wrote:
>> On Wed, Dec 24, 2008 at 11:57:42AM +0100, Paolo Pisati wrote:
>>> Julian Elischer wrote:
>>>> OR
>>>>
>>>> ngctl mkpeer em0: echo lower echo
>>>>
>>>>
>>>> hmmmmm no this would leave the source and destination headers in  
>>>> hte same order.. they need to be swapped..
>>>>
>>>> ok so I need to make a patch, but it would be much quicker than a  
>>>> user utility..
>>> what about a netgraph cookbook?
>> indeed, that would be a nice Xmas present!
>> cheers
>> luigi
>
>
> I'm curious, what sort of things would you expect to see in such a  
> document?  Maybe we could get everyone to contribute their favourite
> netgraph recipes (scripts?).
>

I have often thought of updating the docs I've found but as usual  
$paidwork gets in the way.  I may be about
to use netgraph at work so I might be able to help with this.  The  
things that I find to be missing in the current
netgraph documentation are:

1) Developers Guide

How do I write new nodes?  Walk through a non trivial node step by step.

2) Updated overall use guide

I've found a few docs on netgraph on the net, but I bet most people  
are still looking
at Archie Cobb's old document and it's out of date.

3) Recipes

Sure, a fine idea, but it's not the first thing I need.

Best,
George




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BE32C00-3AF8-4C8F-B48D-45F50D55A2B2>