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

[Guy Harris via tcpdump-workers <tcpdump-workers () lists tcpdump org>]

> --- Begin Message ---
>
>
> From: Guy Harris <gharris () sonic net>
>
> Date: Mon, 9 May 2022 21:57:13 -0700
>
> On May 9, 2022, at 9:41 PM, Tomasz Moń <desowin () gmail com> wrote:
>
> > On Mon, 2022-05-09 at 13:19 -0700, Guy Harris wrote:
> > > On May 9, 2022, at 1:02 PM, Tomasz Moń <desowin () gmail com> wrote:
> > >
> > > > "Why this doesn't match all the documents on USB that I have
> > > > read?".
> > >
> > > What is the "this" that wouldn't match?
> >
> > Packet Bytes as shown by Wireshark.
>
> OK, thet suggests that it's time to finally default to *NOT* showing metadata in the packet bytes pane of Wireshark and 
> in hex dump data in tcpdump, as the only time its raw content is of interest is if you're debugging either 1) software 
> that generates those headers or 2) software that dissects those headers.
>
> *That* will quite effectively prevent people from asking where that byte is defined in a USB spec, as that byte won't 
> be there in the first place.
>
> > Also Wireshark would have to show "USB Full/Low speed capture" section with only the single byte denoting
> > full or low speed, followed by "USB Link Layer" (as shown currently for
> > usbll captures).
>
> No, it wouldn't.  It would just display that as an item in "USB Link Layer".
>
> --- End Message ---
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers