Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I had just installed Wireshark on my Intel NUC 6th Gen running Debian 9 and the KDE desktop. What's interesting is that Wireshark can somehow see any network interfaces at all (being run as non-root for the first time), but the big thing is that it can't see my WiFi and the Ethernet interface comes up with the name enp3s0 instead of eno1 as it does on my other workstation, and no traffic comes through it that I can see, not even DNS. Also, Bluetooth appears in the interface list here, it does not on my other workstation.
Where did you download the WireShark, have you check whether hash of the file if it's available whether it has not been rigged while it was being downloaded.
Finally figured out what was wrong after all this time. Hadn't done the sudo dpkg-reconfigure wireshark-common thing yet in order to enable dumpcap, but for some odd reason, I wasn't given the opportunity to during the initial installation of Wireshark. Now everything works just great!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.