
warning but I never really worried too much, thinking that I couldn't possibly damage anything really badly, right? Anyway to cut a long story short, wireshark started hanging up on me when I started it up and told it to capture on ANY interface - it would just freeze. it gave me the usual "wireshark should not be run as root" etc etc.


The Mad thing is, I used to have wireshark running on my root user account (which was the only account I had lol) and it worked fine for ages and ages. usr/local/bin/ - you can just cd into there and then in a terminal execute 'sudo wireshark' it will ask for your user password then everything will be hunky-dory (but it will still warn you about running as root!). As above - assuming your user account has access to.
