Ubuntu
wireshark package

How do I get permission to use eth0 or lo with wireshark

Asked by eric tennant

I can not get wireshark to work it does not show network configerations, & if I try & use eth0 or lo I get a message to say I do not have permission to use it.???
So whats the use of having wireshark to inastll at all.??

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu wireshark Edit question
Assignee:
No assignee Edit question
Solved by:
actionparsnip
Solved:
Last query:
Last reply:
Revision history for this message
Best actionparsnip (andrew-woodhead666) said : 		#1

run:

gksudo wireshark

And you should be ok, the app doesn't work if ran as user.

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#2

See also http://wiki.wireshark.org/CaptureSetup/CapturePrivileges (scroll down to Linux).

Revision history for this message
eric tennant (erictennant) said : 		#3

Thanks again,
it seems a waste of time loading wireshark from the packet manager.??
if this is all one has to do.??
Cheers
Eric Tennant

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#4

You had to install wireshark *somehow*, before using it. The best, fastest, and easiest way to install it is with the package manager. If you hadn't installed it with the package manager, then running "gksudo wireshark" would not have done anything!

Revision history for this message
eric tennant (erictennant) said : 		#5

Thanks for the info. much appreciated.
regards
Eric Tennant

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#6

you can edit the menu item if it does not have the gksudo item on it so it is default when you run the app

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#7

Apparently, the information on the wireshark website to the effect that wireshark must be run as root (e.g. with gksu/gksudo) is no longer current. That works, of course (as you have experienced). But an alternative and arguably preferable solution is to reconfigure the package wireshark-common, add yourself to the wireshark group, and then log out (and back in). See bug 513903 for details. If you want to do this and need help, please feel free to reopen this question.