On 2/13/07, Robert D. <210525p42015@xxxxxxxxxxxxxx> wrote:
My google searching discovers this is pervasive. None the less, I can't
seem to solve it on my system.
If I type: sudo wireshark in Terminal (and give password) then I get:
Don't use sudo for running wireshark.
use it to change the permissions of /dev/bpf* son that your user can
read from them.
Assuming your user belongs to group admin(80) you should:
$ sudo chgrp admin /dev/bpf*
$ sudo chmod g+r /dev/bpf*
And then run wireshark as you, not as root (you do not want the files
that wireshark creates being owned by root).
Luis
(wireshark:528): Gtk-WARNING **: cannot open display:
If I navigate waaaaay down the tree in
opt/local/var/db/dports/software/wireshark/0.99.5_0+darwin_8/opt/local/share
and double click the unix executable Wireshark, then it runs but
obviously hasn't the ability to find the network points.
One time, shortly after re-installing X-11 this morning, I was able to
do a sudo wireshark and have it run corectly AND locate the various
network points.
When I discovered that none of my running programs could get to the
Internet anymore, I suspected Wireshark had intercepted the en1 path and
thus I re-booted ... all worked fine except I no longer can run wireshark.
Would some kind soul guide me back to success?
thanks ...
--
Frobozz
Mac OS/X 10.4.8
Macbook Pro 2.16 Intel Core Duo
wireshark 0.99.5
X11 1.1.3 - XFree86 4.4.0
Darwin
_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-users
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan