https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15842
--- Comment #4 from Tomasz Mon <deso...@gmail.com> ---
The MBIM case is pretty confusing to me. How come did it dissect USBPcap
Control Data OUT? Also, does it dissect the SETUP bytes captured by usbmon?
The way I understand the code, dissect_usb_common() doesn't pass the
USB_CONTROL_STAGE_DATA to registered dissectors. Thus it is not dissected
through normal means.
dissect_usb_setup_request() creates the composite tvb that gets passed to
dissectors. The composite tvb consists of the 7 bytes of SETUP packet (omitting
the bmRequestType - which cannot be class/vendor specific) and the Data OUT.
The Data OUT is however, only present for Linux (as USBPcap SETUP packets have
always have 8 bytes of payload).
The "reassembly approach" would essentially involve creating the composite tvb
as done in dissect_usb_setup_request() for USBPcap. Is it possible for the
composite tvb to aggregate tvbs from different packets?
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
