On 09.07.2012 12:08, Hiroki Sato wrote:
"Alexander V. Chernikov"<melif...@freebsd.org> wrote
in<4ffa894d.9050...@freebsd.org>:
I meant there was no strong objection. I am sorry for not commenting
your implementation, but at least for ipfw0 it is difficult to
decouple ifnet and bpf because the primary consumer is tcpdump(8),
which depends on NET_RT_IFLIST to find the target. Probably your
tcpdump -i still works with interface name supplied.
solution can be used for usbdump(8). The reason why I committed the
patch now is there are reports that these pseudo interfaces made some
applications confused and/or caused some performance degradation on
9.0R, and wanted to fix it in some way.
Do you plan to take this to 9.1 ?
I am still open for more sophisticated implementation and have no
objection to replace mine with it. Do you have an idea about
converting it with a loadable module?
Personally I think that the right way is to add user<>kernel interface
for requesting interface list since this is the most major stopper for
doing BPF-only providers. However this should be discussed with rpaulo@
and delphij@ (so most probably this skips 9.1).
And, as fallback solution we can probably add separate ipfwlog module
which is quite easy but much less clean.
-- Hiroki
_______________________________________________
svn-src-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
