


In this case, you can set the setuid bit for dumpcap so that it always runs as root.Wireshark is a free tool that should be part of every networking professional’s arsenal. Finally, if the problem is still not resolved, it may be that dumpcap was not correctly configured, or there is something else preventing it from operating correctly. Then log out and log back in (or reboot), and Wireshark should work correctly without needing additional privileges.

In summary, after installing Wireshark, execute the following commands: sudo dpkg-reconfigure wireshark-common Since you are running Ubuntu, this can be resolved by following the instructions given in this answer on the Wireshark Q&A site. This sometimes results from an incomplete or partially successful installation of Wireshark. with sudo), it should generally be avoided (see here, specifically here). While you can avoid this issue by running Wireshark with elevated privileges (e.g.
This is usually caused by incorrectly setting up permissions related to running Wireshark correctly.
