Wireshark-dev: Re: [Wireshark-dev] No interfaces listed to capture packets

From: Michael Tüxen <Michael.Tuexen@xxxxxxxxxxxxxxxxx>
Date: Thu, 25 Feb 2010 19:37:28 +0100
On Feb 25, 2010, at 6:24 PM, David Baird wrote:

> Michael,
> 
> Thanks for the tip on the interactive work around. I have created an alias that I can use everytime I need to use wireshark. I now have all the interfaces lised.
> 
> Looking forward to the "fixed" version of Wireshark for 10.6.
... maybe I was not clear enough. Instead of only copying the ChmodBPF
folder you need to fix the owner and group. So installing it is
more than just copying it.

Maybe we should provide an installer. What do you think, Guy?

Best regards
Michael
> 
> With regards,
> 
> David
> 
> On 2/25/10 9:30 AM, Michael Tüxen wrote:
>> On Feb 24, 2010, at 11:53 PM, David Baird wrote:
>> 
>>> I just installed the MacOSX version of Wireshark downloaded from
>>> www.wireshark.org/download.html.
>>> 
>>> I have a brand new MacBook Pro running Snow Leopard (10.6.2). The
>>> downloaded item was OS X 10.5(Leopard) Intel.dmg.
>>> 
>>> I followed the instructions regarding the installation of the
>>> application and the various scripts. But when I start Wireshark it does
>>> not list any interfaces (eth0, eth1, etc) to select.
>>> 
>>> Also when starting the machine, it complains about the items in
>>> /Library/StartupItems:
>>> 
>>> "/Library/StartupItems/ChmodBPF" has not been started because it does
>>> not have the proper security settings.
>> This needs to be fixed. I think the owner needs to be root and the group
>> wheel. When it actually loads, you interfaces should show up.
>> 
>> If you want the same interactively:
>> sudo chmod uog+r /dev/bpf*
>> 
>> Best regards
>> Michael
>>> 
>>> Any ideas, or does the application need to be tweaked for Snow Leopard?
>>> 
>>> I'm not sure if this is the correct place to report this.
>>> 
>>> Thanks,
>>> 
>>> David Baird
>>> University of Chicago
>>> ___________________________________________________________________________
>>> Sent via:    Wireshark-dev mailing list<wireshark-dev@xxxxxxxxxxxxx>
>>> Archives:    http://www.wireshark.org/lists/wireshark-dev
>>> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>>>             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>>> 
>> 
>