From owner-freebsd-net@FreeBSD.ORG Tue May 30 12:00:31 2006 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 985DB16A43B; Tue, 30 May 2006 12:00:31 +0000 (UTC) (envelope-from yb@bashibuzuk.net) Received: from a.6f2.net (a.6f2.net [213.189.5.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36E4A43D53; Tue, 30 May 2006 12:00:30 +0000 (GMT) (envelope-from yb@bashibuzuk.net) Received: by a.6f2.net (Postfix, from userid 66) id 7D494BF9083; Tue, 30 May 2006 14:00:29 +0200 (CEST) Received: by cc.bashibuzuk.net (Postfix, from userid 1001) id AB266BCD2; Tue, 30 May 2006 14:00:43 +0200 (CEST) Date: Tue, 30 May 2006 14:00:43 +0200 From: Yann Berthier To: Gleb Smirnoff Message-ID: <20060530120043.GA1540@bashibuzuk.net> References: <20060528194319.GL1424@bashibuzuk.net> <20060529115146.GQ27819@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060529115146.GQ27819@cell.sick.ru> X-Operating-System: FreeBSD 7.0-CURRENT User-Agent: Mutt/1.5.11 Cc: net@FreeBSD.org Subject: Re: netgraph on disc(4) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2006 12:00:31 -0000 On Mon, 29 May 2006, at 15:51, Gleb Smirnoff wrote: > On Sun, May 28, 2006 at 09:43:19PM +0200, Yann Berthier wrote: > Y> > Y> Hello Gleb, > Y> > Y> err, sorry for the forward if you saw the thread already but, have > Y> you any input on this ? that's not critical but still, i see value in > Y> being able to use ng_netflow on traffic flowing on dummy interfaces > Y> (lo, disc, ...) > > I've have written some code to wrap any interface some time ago. Here > it is attached. Sorry, I didn't ever used it and not sure it is compilable > on recent FreeBSD versions. Many thanks - so, it compiles on a one month old -CURRENT, but it fails when i try to use it on a loopback interface - i'm able to wrap a real one though: mkpeer ifwrap qq upper name .:qq wrap_disc0 disconnect .:qq msg wrap_disc0: attach "disc0" ngctl: send msg: Operation not supported Anyway, do others see an interest in it ? would it be worth integrating it into the tree ? Except for ng_netflow over loopback links, would there be other consumers of this feature ? - yann