| Bug ID |
10563
|
| Summary |
Display target number for SCM USB-SCSI converters (USB Mass Storage)
|
| Product |
Wireshark
|
| Version |
1.99.x (Experimental)
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13163 [details]
Capture from XP VM on connecting USB-SCSI converter
Build Information:
Wireshark 1.99.0+git20140730111853~82bb8008 (Git Rev Unknown from unknown)
--
This is an enhancement request to the USB mass storage dissector.
The USB Mass Storage Class (Bulk Only Transport) has the LUN in bits [3:0] of
byte 13 of the command block wrapper. Bits [7:4] of that byte are
undefined/reserved.
USB-SCSI converters based on a chipset from SCM Microsystems can work with
multiple SCSI devices. After enabling multi-target mode (which the vendor
driver and Linux do), the target number is given in bits [6:4] of CBW byte 13.
For example if LUN 4 of the the drive at SCSI ID 2 is being accessed, CBW byte
13 would be %00100100 = 0x24. Currently Wireshark doesn't show the target
number. With the above example, Wireshark would show:
.... 0100 = LUN: 0x04
Clicking on that text would highlight the 0x24 byte in the hex dump below, so
you can see from that target 2 is being accessed.
Attached is an example capture taken from a Windows XP VM when a USB-SCSI
converter (with a single drive set to SCSI ID 1) is connected. For example
packet 71 is INQUIRY to target 2, packet 79 shows INQUIRY to target 3 etc.
It would be good if Wireshark could display the target number.
You are receiving this mail because:
- You are watching all bug changes.