tcpdump mailing list archives

Re: Speed specific Link-Layer Header Types for USB 2.0


From: Tomasz Moń via tcpdump-workers <tcpdump-workers () lists tcpdump org>
Date: Mon, 09 May 2022 22:02:26 +0200

--- Begin Message --- From: Tomasz Moń <desowin () gmail com>
Date: Mon, 09 May 2022 22:02:26 +0200
On Mon, 2022-05-09 at 12:52 -0700, Guy Harris wrote:
On May 9, 2022, at 12:40 PM, Tomasz Moń <desowin () gmail com> wrote:

On Mon, 2022-05-09 at 12:02 -0700, Guy Harris wrote:
On May 9, 2022, at 7:41 AM, Tomasz Moń <desowin () gmail com> wrote:

That would require defining pseudoheader that would have to be
included in every packet.

Is that really a great burden?

I think it would make it harder to understand the protocol for
newcomers that use tools like Wireshark to try to make sense of
USB.

In what fashion would it do so?

The same as why URB level captures are confusing. Maybe not to the same
level as that would be just a single byte (and the URB metadata
contains way more information), but it would still raise the questions
like "where in USB specification this byte is defined?", "Why this
doesn't match all the documents on USB that I have read?".

--- End Message ---
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Current thread: