HardenedBSD/contrib/libpcap
1997-02-22 10:53:59 +00:00
..
bpf/net
lbl
aclocal.m4
bpf_image.c
CHANGES
config.guess
config.sub
configure
configure.in
etherent.c
ethertype.h
FILES
FREEBSD-upgrade
gencode.c Update to reflect changes in net/if.h. 1997-01-03 20:10:04 +00:00
gencode.h
grammar.y Kill another bogus inclusion of <netinet/if_ether.h>. 1997-01-05 18:14:12 +00:00
inet.c
INSTALL
install-sh
Makefile.in
mkdep
nametoaddr.c Update to reflect changes in net/if.h. 1997-01-03 20:10:04 +00:00
nlpid.h
optimize.c
pcap-bpf.c
pcap-dlpi.c
pcap-enet.c
pcap-int.h
pcap-namedb.h
pcap-nit.c
pcap-nit.h
pcap-null.c
pcap-pf.c
pcap-pf.h
pcap-snit.c
pcap-snoop.c
pcap.3 Back out an easy $FreeBSD$ (file already left vendor branch) 1997-02-22 10:53:59 +00:00
pcap.c
pcap.h
README
savefile.c
scanner.l
VERSION

@(#) $Header: README,v 1.15 96/07/07 22:38:34 leres Exp $ (LBL)

LIBPCAP 0.2.1
Lawrence Berkeley National Laboratory
Network Research Group
libpcap@ee.lbl.gov
ftp://ftp.ee.lbl.gov/libpcap.tar.Z

This directory contains source code for libpcap, a system-independent
interface for user-level packet capture.  libpcap provides a portable
framework for low-level network monitoring.  Applications include
network statistics collection, security monitoring, network debugging,
etc.  Since almost every system vendor provides a different interface
for packet capture, and since we've developed several tools that
require this functionality, we've created this system-independent API
to ease in porting and to alleviate the need for several
system-dependent packet capture modules in each application.

Note well: this interface is new and is likely to change.

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:

	ftp://ftp.ee.lbl.gov/papers/bpf-usenix93.ps.Z.

Although most packet capture interfaces support in-kernel filtering,
libpcap utilizes in-kernel filtering only for the BPF interface.
On systems that don't have BPF, all packets are read into user-space
and the BPF filters are evaluated in the libpcap library, incurring
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/386, NetBSD, and FreeBSD.  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:

	ftp://gatekeeper.dec.com/pub/DEC/net/bpfext42.tar.Z.

Problems, bugs, questions, desirable enhancements, source code
contributions, etc., should be sent to the email address
"libpcap@ee.lbl.gov".

 - Steve McCanne
   Craig Leres
   Van Jacobson