Success!!
After trying a few different things, I stumbled upon the problem.
I needed to rename the Startup folder to ChmodBPF.
The folder inside the WireShark for Mac OS X disk image was named Startup. The readme file said to copy the entire ChmodBPF folder into StartupItems. I assumed that meant the folder which contained the ChmodBPF script. Once again, I assumed too much.
Problem is now solved, at least for me!
Happy scanning/Sniffing to all.
Regards,
--Aaron Outhier.
------Original Message------
From: Guy Harris
To: Developer support list for Wireshark
Cc: Outhier, Aaron
Subject: Re: [Wireshark-dev] ChmodBPF problem - Fixed!
Sent: Jun 12, 2009 11:16 AM
On Jun 12, 2009, at 8:40 AM, Gerald Combs wrote:
> According to System Startup Programming Topics
> (http://developer.apple.com/documentation/MacOSX/Conceptual/BPSystemStartup/Articles/StartupItems.html
> )
> RunService should be used. It's defined in /etc/rc.common, which is
> included at the top of the script.
>
> Does your system have /etc/rc.common, and does it define RunService?
....and are you trying to run the script directly from the command
line, or did you install it as a startup item and then either manually
change the permissions of the BPF devices or do "sudo SystemStarter
start ChmodBPF"? (You have to do the latter because merely installing
a startup item doesn't provoke it to be run; when you next reboot,
it'll be run automatically at startup time.)
ChmodBPF is *NOT* intended to be run from the command line; it's
intended to be run as a startup item, as per the document Gerald cited.
Sent via BlackBerry from T-Mobile
