THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question

Revision history  [back]

Revision 2
nbal's avatar
1
nbal
updated 2022-11-24 04:30:03 +0000

This is due to lack of permission to capture from my loopback. I am using the group wireshark. Have booted several times. I have no problem running WS with sudo. I suspect that the problem is that WS never really created the group "wireshark" during installation. I had to do that myself. How does WS know the gid of a group, that it didn't create? Could this be the reason it doesn't work? What can be done about it? And while on that subject, why don't you change that message from "unknown data type -1" to "Insufficient permissions to access interface"?

Revision 1
nbal's avatar
1
nbal
answered 2022-11-23 22:26:02 +0000

This is due to lack of permission to capture from my loopback. I am using the group wireshark. Have booted several times. I have no problem running WS with sudo. I suspect that the problem is that WS never really created the group "wireshark" during installation. I had to do that myself. How does WS know the gid of a group, that it didn't create? Could this be the reason it doesn't work? What can be done about it? And while on that subject, why don't you change that message from "unknown data type -1" to "Insufficient permissions to access interface"?it?