| commit | 64fb5ead702d076ab9fe775a577c9302c3727de5 | [log] [tgz] |
|---|---|---|
| author | Guy Harris <gharris@sonic.net> | Tue Sep 27 21:17:12 2022 -0700 |
| committer | Guy Harris <gharris@sonic.net> | Thu Oct 06 01:54:12 2022 -0700 |
| tree | 86f331385d71c34bcf9ec191f504ac2d90ca623d | |
| parent | bab653d2bc2d1de8dcfddc1addff84c90d736977 [diff] |
autoconf, cmake: fix generated pcap-config and libpcap.pc. In libpcap.pc, don't put libraries into Libs.private if we can just put the package to which the libraries belong in Requires.private and let pkg-config do the work. When configuring with CMake, make sure that we do *NOT* put library full paths into the lists of libraries required when linking statically against libpcap. In the configure script, do a push settings/pop settings operation before checking various libraries similar to what's done in CMake files, to make sure that the results of the tests aren't affected by tests done previously. Have the macros for autoconf that run pcap-config take arbitrary arguments rather than a single flag value, to allow testing with --libs and --static. This should fix issue #1062. (cherry picked from commit 6493919a4c7cf15d3d4f9878b2f290dd36efafc0)
To report a security issue please send an e-mail to security@tcpdump.org.
To report bugs and other problems, contribute patches, request a feature, provide generic feedback etc please see the guidelines for contributing.
The documentation directory has README files about specific operating systems and options.
Anonymous Git is available via:
https://github.com/the-tcpdump-group/libpcap.git
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.
formerly from Lawrence Berkeley National Laboratory Network Research Group <libpcap@ee.lbl.gov> ftp://ftp.ee.lbl.gov/old/libpcap-0.4a7.tar.Z
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'' (compressed PostScript, gzipped PostScript, PDF).
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/OS, NetBSD, FreeBSD, OpenBSD, DragonFly BSD, macOS, and Solaris 11; an older, modified and undocumented version is standard in AIX. {DEC OSF/1, Digital UNIX, Tru64 UNIX} uses the packetfilter interface but has been extended to accept BPF filters (which libpcap utilizes).
Linux has a number of BPF based systems, and libpcap does not support any of the eBPF mechanisms as yet, although it supports many of the memory mapped receive mechanisms. See the Linux-specific README for more information.
There's now a rule to make a shared library, which should work on Linux and *BSD, among other platforms.
It sets the soname of the library to libpcap.so.1; this is what it should be, NOT libpcap.so.1.x or libpcap.so.1.x.y or something such as that.
We‘ve been maintaining binary compatibility between libpcap releases for quite a while; there’s no reason to tie a binary linked with libpcap to a particular release of libpcap.