Bug ID: 13961
Summary: ChmodBPF, launch daemon, does not load at startup on
OS: macOS 10.12
Component: Capture file support (libwiretap)
Target Milestone: ---
Created attachment 15763
Wireshark 2.4.0 GUI Packet Capture Error
Wireshark 2.4.0 (v2.4.0-0-g9be0fa5)
Copyright 1998-2017 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with
GLib 2.36.0, with zlib 1.2.5, with SMI 0.4.8, without c-ares, with Lua 5.2.4,
with GnuTLS 3.4.17, with Gcrypt 1.7.7, with MIT Kerberos, with GeoIP, with
nghttp2 1.14.0, with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia,
without AirPcap, with SBC, without SpanDSP.
Running on Mac OS X 10.12.6, build 16G29 (Darwin 16.7.0), with Intel(R)
i7-4980HQ CPU @ 2.80GHz (with SSE4.2), with 16384 MB of physical memory, with
locale en_US.UTF-8, with libpcap version 1.8.1 -- Apple version 67.60.1, with
GnuTLS 3.4.17, with Gcrypt 1.7.7, with zlib 1.2.8.
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
There is a problem with the org.wireshark.ChmodBPF.plist located at
/Library/LaunchDaemons/ not changing the group ownership of /dev/bpf* files.
The ownership of the org.wireshark.ChmodBPF.plist file is root:wheel. I am
unable to load this with launchtl because it states the service is disabled. I
have attempted to enable this service without success. The Wireshark GUI is
very slow to respond and no packet captures will take place because of
incorrect permissions with the /dev/bpf* files. The ownership of /dev/bpf*
files is root:wheel. If I change the group ownership permissions in terminal of
the /dev/bpf* files to access_bpf, restart the GUI, and initiate packet
capturing, then the program appears to function correctly. I've had this
problem with previous versions of this software beginning with 2.2.x. This
problem exists with a clean install, removing remnants of all previous
versions, of Wireshark 2.4.0 and restarting the OS.
You are receiving this mail because:
You are watching all bug changes.
Sent via: Wireshark-bugs mailing list <email@example.com>