Date: Tue, 10 Jul 2012 17:40:04 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: net@FreeBSD.org Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, melifaro@FreeBSD.org Subject: Re: svn commit: r238277 - in head: etc/defaults etc/rc.d sbin/ipfw share/man/man5 sys/netinet/ipfw Message-ID: <20120710134004.GE21957@FreeBSD.org> In-Reply-To: <20120710.053002.914215153752773154.hrs@allbsd.org> References: <4FFA894D.9050104@FreeBSD.org> <20120709.170813.339720376082380726.hrs@allbsd.org> <4FFA9723.5000301@FreeBSD.org> <20120710.053002.914215153752773154.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hiroki, On Tue, Jul 10, 2012 at 05:30:02AM +0900, Hiroki Sato wrote: H> Given that we add a new API to H> enumerate the interfaces including bpf-only providers with fake H> ifnets, which providers/utilities should be converted to use it? IMO H> usbusN would be a reasonable target but others still need a real H> ifnet. In my understanding, the advantage of using a fake ifnet is H> just to prevent it from appearing as an interface. Is it correct? IMO, neither ipfwlog0 nor pflog0 nor pfsync0 need 'struct ifnet'. They are pure providers for tcpdump only. (pfsync0 also consumes if_ioctl to configure itself, but this can be axed and configuring should be done via /dev/pf as all other parts of pf.) As soon as Alexander comes with API that makes it possible to create BPF "dumping points" in kernel that aren't tied to 'struct ifnet', I'd be happy to remove pfsync/pflog/ipfwlog as interfaces. -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120710134004.GE21957>