WireShark on MacOS

1. Download Wireshark 64-bit HTTPS://2.NA.DL.WIRESHARK.ORG/OSX/WIRESHARK%201.12.2%20INTEL%2064.DMG

2. Double-click Install

3. Start after installation , prompt

4, Installation X11

Address http://xquartz.macosforge.org/landing/

5, after downloading the installation, start Wireshark again, select the use of the tool X11.app

6, start Wireshark again, prompt initialization, wait about 1 minutes after the start of success

7. Read Me:

Before you Begin

This release of Wireshark requires Macintosh OS X 10.5.5 or later, including X11.app. If you is running OS X 10.5.4 or older you can install using another packaging system such as MacPorts or Homebrew.

Quick Setup

1. Simply Double-click the Wireshark package. For details about the installation read below.

What changes does the installer make?

The installer writes to the following locations:

• /applications/wireshark.app. The main Wireshark application.
• /library/launchdaemons/org.wireshark.chmodbpf.plist. A Launch daemon that adjusts permissions on the system ' s packet Capture devices (/DEV/BPF*) when the system start s up.
• /library/application SUPPORT/WIRESHARK/CHMODBPF A copy of the Launch Daemon property list, and the script, the launch daemon runs.
• /usr/local/bin. A wrapper script and symbolic links which would let you run Wireshark and their associated utilities from the command line. You can access them directly or by Adding/usr/local/bin to your path if it's not already in your path.

Additionally a group named ACCESS_BPF is created. The user who opened the added to the group.

How does I uninstall?

1. Remove /applications/wireshark.app
2. Remove /library/application Support/wireshark
3. Remove the wrapper scripts from /usr/local/bin
4. Unload the org.wireshark.ChmodBPF.plist launchd Job
5. Remove /library/launchdaemons/org.wireshark.chmodbpf.plist
6. Remove the ACCESS_BPF group.

How do does the wrapper script work? What if I move Wireshark.app?

The script should find the Wireshark application bundle and run the appropriate executable automatically. It looks for Wireshark.app in the following locations:

• The path set in the WIRESHARK_APP_DIR environment variable
• /applications/wireshark.app
• The first path returned by mdfind "kmditemcfbundleidentifier = = ' Org.wireshark.Wireshark '"

If you move wireshark.app the script should automatically find it. If it doesn ' t you'll have a to set Wireshark_app_dir to the path to (and including) Wireshark.app. Automatic discovery might fail if you had multiple copies of Wireshark installed on your system or if Spotlight indexing Isn ' t working properly.

WireShark on MacOS