[Bug 355613] Re: wireshark/libpcap does not support sniffing USB streams

2010-03-13 Thread eapache
Capturing on USB buses works in Karmic (9.10), and there's no way this will be accepted as a stable release update for Jaunty. ** Changed in: libpcap0.8 (Ubuntu) Status: New => Invalid -- wireshark/libpcap does not support sniffing USB streams https://bugs.launchpad.net/bugs/355613 You re

[Bug 355613] Re: wireshark/libpcap does not support sniffing USB streams

2009-08-28 Thread Dan Lenski
I don't think this problem is just with Jaunty. I'm having the same problem with Intrepid (found this while Googling for it). Also, neither tcpdump nor wireshark will actually log the *contents* of the USB packets (aka URBs), merely things like the length and type of packet. Is this a problem wi

[Bug 355613] Re: wireshark/libpcap does not support sniffing USB streams

2009-05-12 Thread Daniel Brodie
The problem is AppArmor just change it to complain: # aa-complain /usr/sbin/tcpdump (WARNING! This will disable apparmor for tcpdump, to reenable use: # aa-enforce /usr/sbin/tcpdump) Also you have to run tcpdump so that it will dump th eoutput to a file using the -w command: # tcpdump -i usb1 -w

[Bug 355613] Re: wireshark/libpcap does not support sniffing USB streams

2009-04-05 Thread Neil Wilson
** Description changed: - Binary package hint: libpcap0.8 - The libpcap installed on Jaunty doesn't appear to support sniffing USB - buses via the usbmon module. - - The package needs upgrading to an upstream > 1.0 version to support the - facility. (Not actually sure why this package is still

[Bug 355613] Re: wireshark/libpcap does not support sniffing USB streams

2009-04-05 Thread Neil Wilson
Actually it looks like it is an enumeration problem stopping wireshark getting the interfaces. tcpdump -D shows: r...@neil-laptop:/var/log# tcpdump -D 1.eth0 2.wmaster0 3.wlan0 4.any (Pseudo-device that captures on all interfaces) 5.lo tcpdump -i usb3 shows: r...@neil-laptop:/var/log# tcpdump -