Wireshark mailing list archives
Re: Wireshark problem report
From: Martin Visser <martinvisser99 () gmail com>
Date: Sun, 12 Jun 2011 15:02:05 +1000
Unfortunately Debian/Ubuntu has chosen to use "safe" defaults rather than "sane" ones when they packaged wireshark. As per http://ubuntuforums.org/showthread.php?t=761461 the issue will be that Wireshark doesn't have privileges to open interfaces for capture. While the quick-and-dirty (and potentially unsafe) way is to just run "sudo wireshark" from the command-line, I use the "Other Linux based systems or other installation methods" as specified in http://wiki.wireshark.org/CaptureSetup/CapturePrivileges Regards, Martin MartinVisser99 () gmail com On 12 June 2011 03:28, Stephen Fisher <steve () stephen-fisher com> wrote:
On Sat, Jun 11, 2011 at 05:52:06AM -0700, Whom it may concern wrote:I am able to capture packets on interface wlan0 with tcpdump, but Wireshark does not see this interface, nor will it use it, even if specified manually in the Preferences. My OS is Ubuntu 10.04 Lucid, with kernel 2.6.32-31-generic #61-Ubuntu SMP. It appears to be a problem with Wireshark, and not the interface device driver.Do you see any interfaces in Wireshark? Wireshark and tcpdump both use libpcap for their live capturing/interface lists. ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- Wireshark problem report Whom it may concern (Jun 11)
- Re: Wireshark problem report Stephen Fisher (Jun 11)
- Re: Wireshark problem report Martin Visser (Jun 11)
- Re: Wireshark problem report Guy Harris (Jun 11)
- Re: Wireshark problem report Guy Harris (Jun 12)
- Re: Wireshark problem report Stephen Fisher (Jun 11)