e89167f07a
Changes: Thu. April 1, 2010. guy@alum.mit.edu. Summary for 1.1.1 libpcap release Update CHANGES to reflect more of the changes in 1.1.0. Fix build on RHEL5. Fix shared library build on AIX. Thu. March 11, 2010. ken@netfunctional.ca/guy@alum.mit.edu. Summary for 1.1.0 libpcap release Add SocketCAN capture support Add Myricom SNF API support Update Endace DAG and ERF support Add support for shared libraries on Solaris, HP-UX, and AIX Build, install, and un-install shared libraries by default; don't build/install shared libraries on platforms we don't support Fix building from a directory other than the source directory Fix compiler warnings and builds on some platforms Update config.guess and config.sub Support monitor mode on mac80211 devices on Linux Fix USB memory-mapped capturing on Linux; it requires a new DLT_ value On Linux, scan /sys/class/net for devices if we have it; scan it, or /proc/net/dev if we don't have /sys/class/net, even if we have getifaddrs(), as it'll find interfaces with no addresses Add limited support for reading pcap-ng files Fix BPF driver-loading error handling on AIX Support getting the full-length interface description on FreeBSD In the lexical analyzer, free up any addrinfo structure we got back from getaddrinfo(). Add support for BPF and libdlpi in OpenSolaris (and SXCE) Hyphenate "link-layer" everywhere Add /sys/kernel/debug/usb/usbmon to the list of usbmon locations In pcap_read_linux_mmap(), if there are no frames available, call poll() even if we're in non-blocking mode, so we pick up errors, and check for the errors in question. Note that poll() works on BPF devices is Snow Leopard If an ENXIO or ENETDOWN is received, it may mean the device has gone away. Deal with it. For BPF, raise the default capture buffer size to from 32k to 512k Support ps_ifdrop on Linux Added a bunch of #ifdef directives to make wpcap.dll (WinPcap) compile under cygwin. Changes to Linux mmapped captures. Fix bug where create_ring would fail for particular snaplen and buffer size combinations Update pcap-config so that it handles libpcap requiring additional libraries Add workaround for threadsafeness on Windows Add missing mapping for DLT_ENC <-> LINKTYPE_ENC DLT: Add DLT_CAN_SOCKETCAN DLT: Add Solaris ipnet Don't check for DLT_IPNET if it's not defined Add link-layer types for Fibre Channel FC-2 Add link-layer types for Wireless HART Add link-layer types for AOS Add link-layer types for DECT Autoconf fixes (AIX, HP-UX, OSF/1, Tru64 cleanups) Install headers unconditionally, and include vlan.h/bluetooth.h if enabled Autoconf fixes+cleanup Support enabling/disabling bluetooth (--{en,dis}able-bluetooth) Support disabling SITA support (--without-sita) Return -1 on failure to create packet ring (if supported but creation failed) Fix handling of 'any' device, so that it can be opened, and no longer attempt to open it in Monitor mode Add support for snapshot length for USB Memory-Mapped Interface Fix configure and build on recent Linux kernels Fix memory-mapped Linux capture to support pcap_next() and pcap_next_ex() Fixes for Linux USB capture DLT: Add DLT_LINUX_EVDEV DLT: Add DLT_GSMTAP_UM DLT: Add DLT_GSMTAP_ABIS
75 lines
3.4 KiB
Plaintext
75 lines
3.4 KiB
Plaintext
As with other systems using BPF, Mac OS X allows users with read access
|
|
to the BPF devices to capture packets with libpcap and allows users with
|
|
write access to the BPF devices to send packets with libpcap.
|
|
|
|
On some systems that use BPF, the BPF devices live on the root file
|
|
system, and the permissions and/or ownership on those devices can be
|
|
changed to give users other than root permission to read or write those
|
|
devices.
|
|
|
|
On newer versions of FreeBSD, the BPF devices live on devfs, and devfs
|
|
can be configured to set the permissions and/or ownership of those
|
|
devices to give users other than root permission to read or write those
|
|
devices.
|
|
|
|
On Mac OS X, the BPF devices live on devfs, but the OS X version of
|
|
devfs is based on an older (non-default) FreeBSD devfs, and that version
|
|
of devfs cannot be configured to set the permissions and/or ownership of
|
|
those devices.
|
|
|
|
Therefore, we supply:
|
|
|
|
a "startup item" for older versions of Mac OS X;
|
|
|
|
a launchd daemon for Tiger and later versions of Mac OS X;
|
|
|
|
Both of them will change the ownership of the BPF devices so that the
|
|
"admin" group owns them, and will change the permission of the BPF
|
|
devices to rw-rw----, so that all users in the "admin" group - i.e., all
|
|
users with "Allow user to administer this computer" turned on - have
|
|
both read and write access to them.
|
|
|
|
The startup item is in the ChmodBPF directory in the source tree. A
|
|
/Library/StartupItems directory should be created if it doesn't already
|
|
exist, and the ChmodBPF directory should be copied to the
|
|
/Library/StartupItems directory (copy the entire directory, so that
|
|
there's a /Library/StartupItems/ChmodBPF directory, containing all the
|
|
files in the source tree's ChmodBPF directory; don't copy the individual
|
|
items in that directory to /Library/StartupItems). The ChmodBPF
|
|
directory, and all files under it, must be owned by root. Installing
|
|
the files won't immediately cause the startup item to be executed; it
|
|
will be executed on the next reboot. To change the permissions before
|
|
the reboot, run
|
|
|
|
sudo SystemStarter start ChmodBPF
|
|
|
|
The launchd daemon is the chmod_bpf script, plus the
|
|
org.tcpdump.chmod_bpf.plist launchd plist file. chmod_bpf should be
|
|
installed in /usr/local/bin/chmod_bpf, and org.tcpdump.chmod_bpf.plist
|
|
should be installed in /Library/LaunchDaemons. chmod_bpf, and
|
|
org.tcpdump.chmod_bpf.plist, must be owned by root. Installing the
|
|
script and plist file won't immediately cause the script to be executed;
|
|
it will be executed on the next reboot. To change the permissions
|
|
before the reboot, run
|
|
|
|
sudo /usr/local/bin/chmod_bpf
|
|
|
|
or
|
|
|
|
sudo launchctl load /Library/LaunchDaemons/org.tcpdump.chmod_bpf.plist
|
|
|
|
If you want to give a particular user permission to access the BPF
|
|
devices, rather than giving all administrative users permission to
|
|
access them, you can have the ChmodBPF/ChmodBPF script change the
|
|
ownership of /dev/bpf* without changing the permissions. If you want to
|
|
give a particular user permission to read and write the BPF devices and
|
|
give the administrative users permission to read but not write the BPF
|
|
devices, you can have the script change the owner to that user, the
|
|
group to "admin", and the permissions to rw-r-----. Other possibilities
|
|
are left as an exercise for the reader.
|
|
|
|
(NOTE: due to a bug in Snow Leopard, if you change the permissions not
|
|
to grant write permission to everybody who should be allowed to capture
|
|
traffic, non-root users who cannot open the BPF devices for writing will
|
|
not be able to capture outgoing packets.)
|