The last four bytes of the header represents the number of setup bytes present.
If it is 0 it is not displayed.
Maybe we whould change this so that the setup length is always displayed?
There was a very recent fix for libpcap that solves the offset-by-one
error for the data stored in each packet.
Can you generate a new USB memory stick trace and put on the wiki and
then Ill plug it in with the SCSI code later today?
best regards
ronnie s
On 10/15/06, Joerg Mayer <jmayer@xxxxxxxxx> wrote:
Hello Paolo,
Frame 1 (18 bytes on wire, 18 bytes captured)
Arrival Time: Jan 1, 1970 01:35:47.483647000
[Time delta from previous packet: 0.000000000 seconds]
[Time since reference or first frame: 0.000000000 seconds]
Frame Number: 1
Packet Length: 18 bytes
Capture Length: 18 bytes
[Frame is marked: False]
[Protocols in frame: usb]
USB URB
URB type: URB_INTERRUPT_INPUT (4)
Device: 1
Endpoint: 1
Application Data: 0D20
0000 00 00 00 04 00 00 00 01 00 00 00 01 00 00 00 00 ................
^^^^^^^^^^^
What do these bytes mean? -------------------|
0010 0d 20 .
Thanks!
Joerg
--
Joerg Mayer <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
