[tcpdump-workers] DLT request for EBHSCR
Hi, The Elektrobit High Speed Capture and Replay (EBHSCR) protocol is produced by a PCIe Card for interfacing high speed automotive interfaces. We write the captured data into a pcap file, using a user specific DLT. But we want to upstream our dissector, thus I want to request an official DLT. Please find the protocols header description here: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Major number |Sl.| Channel |Version| Status| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | +Start timestamp+ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | + Stop timestamp+ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | CRC | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ All multi-byte values in the header are big endian. Major number:type of the frame captured (e.g. camera, BroadR-Reach, .) Sl.: Slot 0-3 Channel: Each slot has sub-channels: 0-63 Version: set to 0 Everything bedsides these four bits and the Length may change with a new Version Status: flags used for error reporting, specific for each major number Length: length in bytes of the frame following this header, not including header Start timestamp: nanosecond counter, taken when we received the start of frame Stop timestamp: nanosecond counter, taken when we received the end of frame CRC: CRC-32C (Castagnoli) of frame bytes, not including header Reserved:set to 0 After the header comes a captured frame-payload. Its content depends on the major number in the header. Do you need any more information? Thanks, Günter Ebermann ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] DLT request for EBHSCR
> From: Guy Harris wrote: > > On Aug 8, 2018, at 8:23 AM, Michael Richardson wrote: > > > wrote: > >> After the header comes a captured frame-payload. Its content depends on the > >> major number in the header. > > > >> Do you need any more information? > > > > it would be great to point to a web site for this info. > > ...especially if the web site contains the same description *plus*: > > what versions of the header currently exist (updated as new versions > are introduced); > > what the header looks like, for each of those versions, including what > bits are used in the status field; > > what the payload looks like. Thanks for the suggestions! I have updated the description accordingly. Please find it here: http://www.elektrobit.com/ebhscr Do you need any more information? Thanks, Günter ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] DLT request for EBHSCR
> Guy Harris wrote: > > On Sep 24, 2018, at 1:46 AM, guenter.eberm...@elektrobit.com wrote: > > > Thanks for the suggestions! > > I have updated the description accordingly. Please find it here: > > http://www.elektrobit.com/ebhscr > > > > Do you need any more information? > > Is the "Major number specific header" fixed-length or is its length dependent > on > the value of the major number? > > If the former, how long is it? If the latter, how long is it for BroadR-Reach > packets? The "Major number specific header" is fixed-length. It is 8 bytes long. ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] DLT request for EBHSCR
Guy Harris wrote: > On Sep 24, 2018, at 11:22 AM, wrote: > > > The "Major number specific header" is fixed-length. > > It is 8 bytes long. > > Please update the specification page to note that. I have updated http://www.elektrobit.com/ebhscr ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
