On Tue, May 30, 2006 at 02:00:43PM +0200, Yann Berthier wrote: Y> > On Sun, May 28, 2006 at 09:43:19PM +0200, Yann Berthier wrote: Y> > Y> Y> > Y> Hello Gleb, Y> > Y> Y> > Y> err, sorry for the forward if you saw the thread already but, have Y> > Y> you any input on this ? that's not critical but still, i see value in Y> > Y> being able to use ng_netflow on traffic flowing on dummy interfaces Y> > Y> (lo, disc, ...) Y> > Y> > I've have written some code to wrap any interface some time ago. Here Y> > it is attached. Sorry, I didn't ever used it and not sure it is compilable Y> > on recent FreeBSD versions. Y> Y> Many thanks - so, it compiles on a one month old -CURRENT, but it Y> fails when i try to use it on a loopback interface - i'm able to wrap Y> a real one though: Y> Y> mkpeer ifwrap qq upper Y> name .:qq wrap_disc0 Y> disconnect .:qq Y> msg wrap_disc0: attach "disc0" Y> ngctl: send msg: Operation not supported Y> Y> Anyway, do others see an interest in it ? would it be worth Y> integrating it into the tree ? Except for ng_netflow over loopback Y> links, would there be other consumers of this feature ?
The problem is that most of interfaces in the stack doesn't have if_output method, that's why ng_ifwrap doesn't work on them. That is the main reason why I haven't committed the code to CVS. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
