Paolo.
Could you have a look at the USB memory stick network trace that is
present on http://wiki.wireshark.org/SampleCaptures?
When I look at these traces it looks to me there is something wrong
with the captured data.
The USB header is fine, as is the SETUP data but the actual data
blob looks wrong to me, like an offset by one error.
If you look at for example the usb memory stick capture and the GET
DESCRIPTOR response packets
the response packets always start with a 0x0D byte and the payload
looks like it is shifted by one.
For example, see packets 21/22 in the memory stick trace.
Packet 21 is a GET DESCRIPTOR and packet 22 contains the data.
The data in packet 22 does not make sense.
However If you remove the initial 0x0D byte so that the packet
starts with 0x12 and then add an additional byte at the end, then
this packet actually makes sense as containing a valid device
descriptor.
Can you have a look at the capture code to see if there is an offset
by one error that would explain these malformed data packets?
And if so, produce a patch for libpcap?
best regards
ronnie sahlberg
On 10/11/06, Paolo Abeni <paolo.abeni@xxxxxxxx> wrote:
hello,
this patch reflect the changes into usb setup header from current
libpcap cvs.
Paolo
--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f
Sponsor:
Ti piace la chitarra? Impara a suonarla senza fatica ed evitando tutti gli
errori, con l'aiuto di un maestro professionista
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=5144&d=11-10
