https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4819
Tyson Key <tyson.key@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tyson.key@xxxxxxxxx
--- Comment #2 from Tyson Key <tyson.key@xxxxxxxxx> 2010-06-04 02:22:50 PDT ---
After spending ages reading specifications, dissecting the capture file and
fighting with display filters, I guess that the best way to go about things
would be to somehow match on the appropriate interface class (0x02 -
Communications) and subclass (0x06 - Ethernet Network Control Model) provided
that all of the correct device descriptors and other initialisation frames are
available to work with. An example of that class and subclass is available in
packet #42.
Sadly, that would likely involve building a new USB CDC dissector that at least
matches on that criteria for Ethernet (although it wouldn't cope with
non-compliant devices, or the existence of new subclasses/payload types), and
hands off to the PPP dissectors for stuff that can't be dealt with in that
manner.
Of course, the current method used for PPP and ISO/IEC 13818-1 with interfaces
of types IF_CLASS_UNKNOWN and IF_CLASS_VENDOR_SPECIFIC could probably go
unchanged - since you wouldn't see Ethernet frames there, unless someone
extracted CDC Ethernet frames without the associated set-up stuff, and then fed
it back to Wireshark.
I'm pretty much at a loss as to what could be done otherwise, and I could be
incorrect in some ways.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
