Closed kuro68k closed 5 years ago
You can download the capture here: https://drive.google.com/file/d/0Bxo3omeSKZ7AcWVTdUVacFpWOWM/view?usp=sharing
I also checked with a logic analyzer, I can see the correct packets and data being sent.
Which Windows version are you using?
Windows 7 x64 Pro.
I can confirm that Microsoft Network Monitor works and captures the packets correctly.
I believe this was fixed in fbef41944d369680765bb7d82d2cc8c3b9455d32
The USBPcap 1.3.0.0 release should no longer miscapture these packets.
I'm running USBPcap 1.5.4.0 (Win 7 SP1/x86 under VirtualBox) and Wireshark v3.4.3-0-g6ae6cd335aa9 (OSX 10.14.6) and am seeing:
USB URB
[Source: 1.2.1]
[Destination: host]
USBPcap pseudoheader length: 27
IRP ID: 0xffffffff854e29a8
IRP USBD_STATUS: USBD_STATUS_SUCCESS (0x00000000)
URB Function: URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER (0x0009)
IRP information: 0x01, Direction: PDO -> FDO
URB bus id: 1
Device address: 2
Endpoint: 0x81, Direction: IN
URB transfer type: URB_BULK (0x03)
Packet Data Length: 1
[Request in: 722]
[Time from request: 0.000000000 seconds]
[bInterfaceClass: Vendor Specific (0xff)]
[Malformed Packet: IPPUSB]
Netmon is decoding the packet and showing a one byte payload. Wireshark is showing "Packet Data Length" as "01 00 00 00" with a trailing byte that's being classed as a malformed packet. The device itself appears to be functioning as the bundled app communicates with it appropriately.
I'm running USBPcap 1.5.4.0 (Win 7 SP1/x86 under VirtualBox) and Wireshark v3.4.3-0-g6ae6cd335aa9 (OSX 10.14.6) and am seeing:
USB URB [Source: 1.2.1] [Destination: host] USBPcap pseudoheader length: 27 IRP ID: 0xffffffff854e29a8 IRP USBD_STATUS: USBD_STATUS_SUCCESS (0x00000000) URB Function: URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER (0x0009) IRP information: 0x01, Direction: PDO -> FDO URB bus id: 1 Device address: 2 Endpoint: 0x81, Direction: IN URB transfer type: URB_BULK (0x03) Packet Data Length: 1 [Request in: 722] [Time from request: 0.000000000 seconds] [bInterfaceClass: Vendor Specific (0xff)] [Malformed Packet: IPPUSB]
This looks like a bug in Wireshark, but I would need complete pcap file to check what's exactly going on.
I'll email the pcap and ETL files in a moment.
I am trying to debug an issue with a device I built. When I connect it, Windows can read the descriptors and strings okay. It shows up in Device Manager as "Example Device" (the product ID I set) and the properties page shows the correct VID/PID, Manufacturer ID etc. Other USB debug tools show that the descriptor was read correctly (vendor specific device with bulk endpoint).
However, in Wireshark the usbpcap capture shows "malformed packet" on all the descriptors and strings.
The request from the host is for string 0x02, which is the product ID, which in this case should be "Example Device", which is what Windows displays.