| Bug ID |
10748
|
| Summary |
Wireshark says "No interface can be used ..." when it hits the lack of permissions problem
|
| Product |
Wireshark
|
| Version |
1.12.2
|
| Hardware |
Other
|
| OS |
FreeBSD
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
TShark 1.12.2 (Git Rev Unknown from unknown)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GLib 2.42.0, with libpcap, with libz 1.2.8, without
POSIX
capabilities, with SMI 0.4.8, without c-ares, with ADNS, without Lua, without
Python, without GnuTLS, with Gcrypt 1.6.1, with Heimdal Kerberos, with GeoIP.
Running on FreeBSD 10.1-STABLE, with locale en_US.UTF-8, with libpcap version
1.4.0, with libz 1.2.8.
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
Built using clang 4.2.1 Compatible FreeBSD Clang 3.4.1
(tags/RELEASE_34/dot1-final 208032).
--
When pcap has insufficient permissions, wireshark just says "No interface can
be used for capturing in this system with the current cinfiguration"
This message is very generic and vague, and hides the particular error dumpcap
got:
2035 dumpcap NAMI "/dev/bpf"
2035 dumpcap RET open -1 errno 13 Permission denied
In this case it needs to say all the details about what happened, and be more
suggestive:
````
Wireshark is unable to access network packets because dumpcap failed to open
'/dev/bpf' as user 'username': Permission denied
Generally only members of the 'network' group can access device '/dev/bpf'
````
Otherwise, the current message just leaves the used wondering what exactly
happened and what actions can remedy the situation.
You are receiving this mail because:
- You are watching all bug changes.