Wireshark mailing list archives
Re: Usb dissectors, usb.protocol is always 0x000000
From: Pascal Quantin <pascal.quantin () gmail com>
Date: Fri, 23 Oct 2015 17:39:01 +0200
2015-10-23 17:30 GMT+02:00 [AvataR] <public.avatar () gmail com>:
Hi, ensure to capture the USB enumeration. This is required to fill those fields. Best regards, Pascal.To be really sure, I start capture before plugging device to hub. There are enumeration, and descriptors are properly parsed. I can place pcap somewhere, if this may help.
yes it could be useful. On my side I'm using USBPcap and USB Class ID, Subclass ID and Protocol are properly populated when the capture contains the USB enumeration. You did not indicate us which Wireshark version you are using. BR, Pascal.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Usb dissectors, usb.protocol is always 0x000000 [AvataR] (Oct 23)
- Re: Usb dissectors, usb.protocol is always 0x000000 Pascal Quantin (Oct 23)
- Re: Usb dissectors, usb.protocol is always 0x000000 [AvataR] (Oct 23)
- Re: Usb dissectors, usb.protocol is always 0x000000 Pascal Quantin (Oct 23)
- Re: Usb dissectors, usb.protocol is always 0x000000 Oleksii Shevchuk (Oct 23)
- Re: Usb dissectors, usb.protocol is always 0x000000 Pascal Quantin (Oct 24)
- Re: Usb dissectors, usb.protocol is always 0x000000 [AvataR] (Oct 23)
- Re: Usb dissectors, usb.protocol is always 0x000000 Pascal Quantin (Oct 23)