Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Wireshark won't capture packets as non-root, but then works after it crashes

I am running Ubuntu LTS 20.04. I have a customized wireshark 3.4.4 installed (required for a customized dissector). I uninstalled the version of wireshark I initially installed through apt. And then I

Wireshark won't capture packets as non-root, but then works after it crashes

I am running Ubuntu LTS 20.04. I have a customized wireshark 3.4.4 installed (required for a customized dissector). I uninstalled the version of wireshark I initially installed through apt. And then II successfully built from source, and installed it. I did the things that I see on the internet about reconfiguring the package to allow non-root users to capture, and adding my user to the wireshark group or adding +x permissions to dumpcap. However, when I start wireshark it always gives the same error that it can't capture packets.

However, sometimes it will crash and I'm asked to report the problem to Ubuntu. When I do that, and then hit "relaunch", it then works fine and can capture packets fine. Until the next time I close it and re-open it when it goes back to not being able to capture packets. Any idea how I can get around this issue?

Wireshark won't capture packets as non-root, but then works after it crashes

I am running Ubuntu LTS 20.04. I have a customized wireshark 3.4.4 installed (required for a customized dissector). I uninstalled the version of wireshark I initially installed through apt. And then I successfully built from source, and installed it. I did the things that I see on the internet about reconfiguring the package to allow non-root users to capture, and adding my user to the wireshark group or adding +x permissions to dumpcap. However, when I start wireshark it always gives the same error that it can't capture packets.

ls -la /usr/bin/dumpcap -rwxr-xr-x 1 root wireshark 468224 May 3 07:27 /usr/bin/dumpcap

sudo adduser user wireshark The user `user' is already a member of `wireshark'.

However, sometimes it will crash and I'm asked to report the problem to Ubuntu. When I do that, and then hit "relaunch", it then works fine and can capture packets fine. Until the next time I close it and re-open it when it goes back to not being able to capture packets. Any idea how I can get around this issue?

Wireshark won't capture packets as non-root, but then works after it crashes

I am running Ubuntu LTS 20.04. I have a customized wireshark 3.4.4 installed (required for a customized dissector). I uninstalled the version of wireshark I initially installed through apt. And then I successfully built from source, and installed it. I did the things that I see on the internet about reconfiguring the package to allow non-root users to capture, and adding my user to the wireshark group or adding +x permissions to dumpcap. However, when I start wireshark it always gives the same error that it can't capture packets.

 ls -la /usr/bin/dumpcap  
-rwxr-xr-x 1 root wireshark 468224 May  3 07:27 /usr/bin/dumpcap

sudo adduser user wireshark The user `user' is already a member of `wireshark'.

However, sometimes it will crash and I'm asked to report the problem to Ubuntu. When I do that, and then hit "relaunch", it then works fine and can capture packets fine. Until the next time I close it and re-open it when it goes back to not being able to capture packets. Any idea how I can get around this issue?

Wireshark won't capture packets as non-root, but then works after it crashes

I am running Ubuntu LTS 20.04. I have a customized wireshark 3.4.4 installed (required for a customized dissector). I uninstalled the version of wireshark I initially installed through apt. And then I successfully built from source, and installed it. I did the things that I see on the internet about reconfiguring the package to allow non-root users to capture, and adding my user to the wireshark group or adding +x permissions to dumpcap. However, when I start wireshark it always gives the same error that it can't capture packets.

ls -la /usr/bin/dumpcap  
/bin/dumpcap
-rwxr-xr-x 1 root wireshark 468224 May  3 07:27 /usr/bin/dumpcap
/bin/dumpcap

sudo adduser user wireshark  
The user `user' is already a member of `wireshark'.

However, sometimes it will crash and I'm asked to report the problem to Ubuntu. When I do that, and then hit "relaunch", it then works fine and can capture packets fine. Until the next time I close it and re-open it when it goes back to not being able to capture packets. Any idea how I can get around this issue?

Wireshark won't capture packets as non-root, but then works after it crashes

I am running Ubuntu LTS 20.04. I have a customized wireshark 3.4.4 installed (required for a customized dissector). I uninstalled the version of wireshark I initially installed through apt. And then I successfully built from source, and installed it. I did the things that I see on the internet about reconfiguring the package to allow non-root users to capture, and adding my user to the wireshark group or adding +x permissions to dumpcap. However, when I start wireshark it always gives the same error that it can't capture packets.

ls -la /bin/dumpcap
-rwxr-xr-x 1 root wireshark 468224 May  3 07:27 /bin/dumpcap

sudo adduser user wireshark  
The user `user' is already a member of `wireshark'.

groups
user adm cdrom sudo dip plugdev lpadmin lxd sambashare wireshark

However, sometimes it will crash and I'm asked to report the problem to Ubuntu. When I do that, and then hit "relaunch", it then works fine and can capture packets fine. Until the next time I close it and re-open it when it goes back to not being able to capture packets. Any idea how I can get around this issue?

Wireshark won't capture packets as non-root, but then works after it crashes

I am running Ubuntu LTS 20.04. I have a customized wireshark 3.4.4 installed (required for a customized dissector). I uninstalled the version of wireshark I initially installed through apt. And then I successfully built from source, and installed it. I did the things that I see on the internet about reconfiguring the package to allow non-root users to capture, and adding my user to the wireshark group or adding +x s+x permissions to dumpcap. However, when I start wireshark it always gives the same error that it can't capture packets.

ls -la /bin/dumpcap
-rwxr-xr-x /usr/bin/dumpcap 
-rwsr-xr-x 1 root wireshark 468224 May  3 07:27 /bin/dumpcap
/usr/bin/dumpcap

sudo adduser user wireshark  
The user `user' is already a member of `wireshark'.

groups
user adm cdrom sudo dip plugdev lpadmin lxd sambashare wireshark

However, sometimes it will crash and I'm asked to report the problem to Ubuntu. When I do that, and then hit "relaunch", it then works fine and can capture packets fine. Until the next time I close it and re-open it when it goes back to not being able to capture packets. Any idea how I can get around this issue?

Wireshark won't capture packets as non-root, but then works after it crashes

I am running Ubuntu LTS 20.04. I have a customized wireshark 3.4.4 installed (required for a customized dissector). I uninstalled the version of wireshark I initially installed through apt. And then I successfully built from source, and installed it. I did the things that I see on the internet about reconfiguring the package to allow non-root users to capture, and adding my user to the wireshark group or adding s+x permissions to dumpcap. However, when I start wireshark it always gives the same error that it can't capture packets.

ls -la /usr/bin/dumpcap 
-rwsr-xr-x 1 root wireshark 468224 May  3 07:27 /usr/bin/dumpcap

sudo getcap /usr/bin/dumpcap
/usr/bin/dumpcap = cap_net_admin,cap_net_raw+eip

sudo adduser user wireshark  
The user `user' is already a member of `wireshark'.

groups
user adm cdrom sudo dip plugdev lpadmin lxd sambashare wireshark

However, sometimes it will crash and I'm asked to report the problem to Ubuntu. When I do that, and then hit "relaunch", it then works fine and can capture packets fine. Until the next time I close it and re-open it when it goes back to not being able to capture packets. Any idea how I can get around this issue?