NetBSD/lib/libpcap
perry 1f4ad37fe3 "Utilize" has exactly the same meaning as "use," but it is more
difficult to read and understand. Most manuals of English style
therefore say that you should use "use".
2003-02-05 00:02:24 +00:00
..
bpf_image.c
CHANGES
etherent.c
ethertype.h Add support for VLAN (IEEE 802.1Q) frames. 2002-12-19 16:33:47 +00:00
gencode.c Add support for VLAN (IEEE 802.1Q) frames. 2002-12-19 16:33:47 +00:00
gencode.h Add support for VLAN (IEEE 802.1Q) frames. 2002-12-19 16:33:47 +00:00
gnuc.h
grammar.y Add support for VLAN (IEEE 802.1Q) frames. 2002-12-19 16:33:47 +00:00
inet.c
Makefile Don't override the definition of LEX. 2002-09-14 14:59:30 +00:00
nametoaddr.c
optimize.c sync partly with tcpdump.org. ok'ed by itojun 2002-08-26 11:21:18 +00:00
pcap2netbsd
pcap-bpf.c Open the BPF file descriptor as read-write. Some pcap-using programs 2002-10-19 22:03:44 +00:00
pcap-int.h * Add support for DLT_IEEE802_11. 2002-09-22 16:13:01 +00:00
pcap-namedb.h
pcap.3 Take descriptions for pcap_file() and pcap_fileno() from libpcap-current 2003-01-07 16:51:20 +00:00
pcap.c * Add support for DLT_IEEE802_11. 2002-09-22 16:13:01 +00:00
pcap.h * Add support for DLT_IEEE802_11. 2002-09-22 16:13:01 +00:00
ppp.h
README "Utilize" has exactly the same meaning as "use," but it is more 2003-02-05 00:02:24 +00:00
savefile.c
scanner.l Add support for VLAN (IEEE 802.1Q) frames. 2002-12-19 16:33:47 +00:00
shlib_version * Add support for DLT_IEEE802_11. 2002-09-22 16:13:01 +00:00
version.c

$NetBSD: README,v 1.5 2003/02/05 00:02:25 perry Exp $
@(#) Header: README,v 1.18 97/06/12 14:23:56 leres Exp  (LBL)

LIBPCAP 0.4
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 uses 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 uses).  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