diff options
author | Guy Harris <gharris@sonic.net> | 2022-03-18 19:16:52 -0700 |
---|---|---|
committer | Guy Harris <gharris@sonic.net> | 2022-03-18 19:16:52 -0700 |
commit | dcb90c46c20cb3483c4e53484adb3264dc7902f0 (patch) | |
tree | 7e319d8ce0ba214561bab0e03370887e941ee4e1 /pcap.c | |
parent | 21dfd4a6fb560ff22ede82f3481f705dadfcfc3f (diff) |
Make the error message for PCAP_ERROR_PERM_DENIED a little more open-ended.
PCAP_ERROR_PERM_DENIED can be returned for reasons other than "you don't
have any permission to capture on that device", e.g. it might be "you
have permission to capture on it, but not to capture on it with hardware
time stamps (as on Linux) or to capture in monitor mode or to...".
This leaves it more open-ended, in case we add support for
device-dependent or platform-dependent configuration parameters and some
of them require more privileges than just capturing with the default
setting does, without having to keep adding more PERM_DENIED error
codes.
This, along with some other changes, may help debug problems such as the
one in issue #1098.
Diffstat (limited to 'pcap.c')
-rw-r--r-- | pcap.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -3679,7 +3679,7 @@ pcap_statustostr(int errnum) return ("That operation is supported only in monitor mode"); case PCAP_ERROR_PERM_DENIED: - return ("You don't have permission to capture on that device"); + return ("You don't have permission to perform this capture on that device"); case PCAP_ERROR_IFACE_NOT_UP: return ("That device is not up"); |