Home > Misc > Wireshark ChmodBPF errors on Snow Leopard

Wireshark ChmodBPF errors on Snow Leopard

October 3rd, 2009 Leave a comment Go to comments

When I got Snow Leopard, I decided to do some house cleaning. I wiped the disk and reinstalled everything from scratch. I didn’t have any problems along the way until I went to install my favorite network protocol analyzer: Wireshark.

Installing is a simple matter of dragging the application into your Applications folder, but there’s also a startup item that sets some necessary permissions. To set that up, go into the Utilities folder on the Wireshark disk image, and drag the ChmodBPF folder onto the StartupItems shortcut. It’ll prompt you to authenticate and then copy. If you restart at this point, you’ll get an error message that says “Insecure Startup Item disabled. – “/Library/StartupItems/ChmodBPF” has not been started because it does not have the proper security settings.”

Using information from an Apple support article, I realized you need to change the owner of the scripts for them to be run on startup. Run the command below and everything will work fine!

cd /Library/StartupItems
sudo chown -R root:wheel ChmodBPF


Update (7/14/2010)
– Make sure you restart your computer after running this command. The script only runs at startup, so just changing the permissions doesn’t do anything by itself. You have to restart for the script to run.

Share and Enjoy:
  • Print
  • Digg
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • FriendFeed
  • HackerNews
  • Reddit
  • StumbleUpon
  • Tumblr
  • Twitter
Categories: Misc Tags:
  1. October 9th, 2009 at 04:26 | #1

    IT WORKS :D thank you.

  2. November 3rd, 2009 at 06:06 | #2

    Yesss!!! Thank you!

    For others who will undoubtedly run into the same problem, I’ll make the following note:

    The fact that ChmodBPF is failing to set the correct permissions will go unnoticed to the majority of users, because the ““Insecure Startup Item disabled” error, is of course only visible at the command line.

    However, at a higher level, the very real and visual problem, that this will solve is that “The wireshark interface list is empty”

    That was my problem and it took a little bit of detective work to track down the ultimate culprit. But now everything up and running, thanks again to this tip :-)

  3. Vi
    November 10th, 2009 at 17:52 | #3

    Thank you for this tip. It was the last step I needed to get Wireshark working.

  4. Richard
    November 25th, 2009 at 13:03 | #4

    Thank you, thank you, thank you!
    I can now diagnose my Draytek router when it loses DNS connectivity over Wifi.

  5. November 30th, 2009 at 16:24 | #5

    Thanks – That’s been bugging me for a while now…

  6. December 5th, 2009 at 17:12 | #6

    Awesome, thanks!

  7. Marco
    January 13th, 2010 at 09:03 | #7

    Good job! Thanks a lot

  8. Bill
    January 23rd, 2010 at 13:40 | #8

    Thank you so much. This was driving me crazy only being able to get it to work from the command line.

  9. Rob
    March 23rd, 2010 at 11:12 | #9

    The above commands did not work for me, but this did:

    sudo chmod 644 /dev/bpf*

  10. Terry
    March 24th, 2010 at 15:10 | #10

    Also, for the StartupParameters.plist files, invoke this from the CLI:

    sudo chown -R root:wheel StartupParameters.plist

    then restart so that BPF permissions are enabled for Wireshark, or simply
    invoke this on the CLI without restarting:

    sudo SystemStarter start ChmodBPF

  11. lowlow
    April 21st, 2010 at 09:42 | #11

    many thx
    for the command to
    gettnig it work !!!

  12. May 19th, 2010 at 12:17 | #12

    Thank you so much. This was driving me crazy only being able to get it to work from the command line.

  13. Thomas
    July 5th, 2010 at 16:47 | #13

    I didn’t have any luck with this, I still get the error. ug.

  14. tecnik
    July 9th, 2010 at 05:46 | #14

    What they said^^ Cheers!!

  15. Jahn
    July 13th, 2010 at 18:49 | #15

    Same as Thomas, still not having any luck. I opened up the command prompt copied the above command
    cd /Library/StartupItems
    sudo chown -R root:wheel ChmodBPF

    It asked me for my password, i entered it, pressed enter then opened up WireShark.
    Still no interfaces or capturing devices

  16. Nick Kleinschmidt
    July 14th, 2010 at 09:16 | #16

    I wasn’t very clear on this in the article, but you need to restart your Mac after changing the permissions for the script to work. Adding an update to my post to make sure nobody misses it in the future. I just reinstalled on Mac OS 10.6.4 and everything shows up fine for me after a restart.

  1. October 13th, 2009 at 15:03 | #1