summaryrefslogtreecommitdiffstats
path: root/contrib/libpcap/README
diff options
context:
space:
mode:
authorbms <bms@FreeBSD.org>2004-03-31 09:07:39 +0000
committerbms <bms@FreeBSD.org>2004-03-31 09:07:39 +0000
commitda13a5a9d72229b2a6026a49b9977934bdef13ed (patch)
treeb024e287db2b122351a0e433fbc33120af98a9eb /contrib/libpcap/README
parent34111fdf72727e35d5c81dc576ce3f5a87c9ef84 (diff)
downloadFreeBSD-src-da13a5a9d72229b2a6026a49b9977934bdef13ed.zip
FreeBSD-src-da13a5a9d72229b2a6026a49b9977934bdef13ed.tar.gz
Import libpcap 0.8.3, from http://www.tcpdump.org/releases/libpcap-0.8.3.tar.gz
Diffstat (limited to 'contrib/libpcap/README')
-rw-r--r--contrib/libpcap/README59
1 files changed, 44 insertions, 15 deletions
diff --git a/contrib/libpcap/README b/contrib/libpcap/README
index ca6347c..35ab2f8 100644
--- a/contrib/libpcap/README
+++ b/contrib/libpcap/README
@@ -1,6 +1,6 @@
-@(#) $Header: /tcpdump/master/libpcap/README,v 1.24 2001/06/05 03:45:55 guy Exp $ (LBL)
+@(#) $Header: /tcpdump/master/libpcap/README,v 1.27.2.1 2003/11/15 23:29:19 guy Exp $ (LBL)
-LIBPCAP 0.6.2
+LIBPCAP 0.8
Now maintained by "The Tcpdump Group"
See www.tcpdump.org
@@ -11,8 +11,8 @@ Anonymous CVS is available via:
(password "anoncvs")
cvs -d :pserver:tcpdump@cvs.tcpdump.org:/tcpdump/master checkout libpcap
-Version 0.6.2 of LIBPCAP can be retrieved with the CVS tag "libpcap_0_6rel2":
- cvs -d :pserver:tcpdump@cvs.tcpdump.org:/tcpdump/master checkout -r libpcap_0_6rel2 libpcap
+Version 0.8 of LIBPCAP can be retrieved with the CVS tag "libpcap_0_8rel1":
+ cvs -d :pserver:tcpdump@cvs.tcpdump.org:/tcpdump/master checkout -r libpcap_0_8rel1 libpcap
Please send patches against the master copy to patches@tcpdump.org.
@@ -32,12 +32,30 @@ system-dependent packet capture modules in each application.
Note well: this interface is new and is likely to change.
+For some platforms there are README.{system} files that discuss issues
+with the OS's interface for packet capture on those platforms, such as
+how to enable support for that interface in the OS, if it's not built in
+by default.
+
The libpcap interface supports a filtering mechanism based on the
architecture in the BSD packet filter. BPF is described in the 1993
Winter Usenix paper ``The BSD Packet Filter: A New Architecture for
-User-level Packet Capture''. A compressed postscript version is in:
+User-level Packet Capture''. A compressed PostScript version can be
+found at
+
+ ftp://ftp.ee.lbl.gov/papers/bpf-usenix93.ps.Z
+
+or
+
+ http://www.tcpdump.org/papers/bpf-usenix93.ps.Z
+
+and a gzipped version can be found at
- ftp://ftp.ee.lbl.gov/papers/bpf-usenix93.ps.Z.
+ http://www.tcpdump.org/papers/bpf-usenix93.ps.gz
+
+A PDF version can be found at
+
+ http://www.tcpdump.org/papers/bpf-usenix93.pdf
Although most packet capture interfaces support in-kernel filtering,
libpcap utilizes in-kernel filtering only for the BPF interface.
@@ -47,19 +65,30 @@ added overhead (especially, for selective filters). Ideally, libpcap
would translate BPF filters into a filter program that is compatible
with the underlying kernel subsystem, but this is not yet implemented.
-BPF is standard in 4.4BSD, BSD/OS, NetBSD, FreeBSD, and OpenBSD. DEC OSF/1
-uses the packetfilter interface but has been extended to accept BPF
-filters (which libpcap utilizes). Also, you can add BPF filter support
-to Ultrix using the kernel source and/or object patches available in:
+BPF is standard in 4.4BSD, BSD/OS, NetBSD, FreeBSD, and OpenBSD. DEC
+OSF/1/Digital UNIX/Tru64 UNIX uses the packetfilter interface but has
+been extended to accept BPF filters (which libpcap utilizes). Also, you
+can add BPF filter support to Ultrix using the kernel source and/or
+object patches available in:
ftp://gatekeeper.dec.com/pub/DEC/net/bpfext42.tar.Z.
-Problems, bugs, questions, desirable enhancements, etc.
-should be sent to the address "tcpdump-workers@tcpdump.org".
+Linux, in the 2.2 kernel and later kernels, has a "Socket Filter"
+mechanism that accepts BPF filters; see the README.linux file for
+information on configuring that option.
+
+Problems, bugs, questions, desirable enhancements, etc. should be sent
+to the address "tcpdump-workers@tcpdump.org". Bugs, support requests,
+and feature requests may also be submitted on the SourceForge site for
+libpcap at
+
+ http://sourceforge.net/projects/libpcap/
-Source code contributions, etc. should be sent to the email address
-"patches@tcpdump.org".
+Source code contributions, etc. should be sent to the email address
+"patches@tcpdump.org", or submitted as patches on the SourceForge site
+for libpcap.
-Current versions can be found at www.tcpdump.org
+Current versions can be found at www.tcpdump.org, or the SourceForge
+site for libpcap.
- The TCPdump team
OpenPOWER on IntegriCloud