Hello,
Darren Reed wrote:
Dan Groves wrote:
Hello all,
As part of project Clearview
(http://www.opensolaris.org/os/project/clearview/), we are updating
snoop so that it can filter VLAN tagged packets. I've posted a design
document and some background information to:
http://www.opensolaris.org/os/project/clearview/vlan_filtering/
A quick summary:
4.2 - Yes
4.3 - We can't replace pfmod, we need to add bpfmod
I will change the document. I'll send out mail when I've posted an
updated copy.
4.4 - No
4.5 - No
Maybe 4.2 can introduce a whole set of new commands for pfmod that
allows it to do variable-header retrieving of data?
I thought about that. That's what happens with user space filtering. I
think that route is less flexible and there are limitations on how much
we can add to pfmod. My detailed design document includes a section
that details how pfmod works, and includes a section explaining why I
chose to not add a whole set of commands similar to what's in user space.
After doing 4.3, a seperate(?) project/fast-track should be created
to integrate libpcap into ON. The libpcap shipped with ON should
present the same interface as open source (www.tcpdump.org) and
use bpfmod in Solaris. The downside is that interface provided by
libpcap isn't as stable as we'd like. The upside is that open source
applications could "auto-configure", find it present and use that
rather than opening up a DLPI STREAM and doing user-space
filtering on packets. And of course source code form an integrated
libpcap should be fed back to the original open source project to
get it supporting bpfmod and reduce future overhead of maintaining
libpcap in ON.
Good point. Thanks!
Despite pfmod being an unattractive interface to use, it is in man
pages and it has been around for a long time, so removing it may
not necessarily be an easy process, however bad it may be.
Understood.
Thanks for the comments!
Dan
_______________________________________________
networking-discuss mailing list
[email protected]
