> Am 10.06.2016 um 01:35 schrieb Guy Harris :
>
> On Jun 9, 2016, at 4:09 PM, Guenter Ebermann
> wrote:
>
>>
>>> Am 10.06.2016 um 00:13 schrieb Guy Harris :
>>>
>>> But that doesn't mean that the packets time stamped by the hardware whe
> Am 10.06.2016 um 00:13 schrieb Guy Harris :
>
> But that doesn't mean that the packets time stamped by the hardware when
> transmitted will be delivered to the PF_PACKET sockets used by libpcap *with
> the hardware time stamp as the time stamp*.
>
> In order make that happen, if hardware tra
> Am 09.06.2016 um 15:47 schrieb Michael Richardson :
>
> Guenter Ebermann wrote:
>> Hardware timestamping of sending/receiving buffer descriptors is done
>> by NIC.
>
> Receiving I understand.
>
> Are you sure that the hardware is going to timestamp sent pa
> Am 08.06.2016 um 23:10 schrieb Michael Richardson :
>
> Christian Rupp wrote:
>> The Timestamp when tcpdump grabs the package off of the receiver is 36
>> seconds( +/- innaccuracy, here roughly +/- 5-10 µs) after the timestamp when
>> tcpdump grabs the package of the sender. resulting in an a
2016-01-20 20:50 GMT+01:00 Guy Harris :
> On Jan 20, 2016, at 7:38 AM, Guenter Ebermann
> wrote:
>
>> I have a first draft of the packet-specification available:
>> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14264
>
> So it looks as if the extra low-level f
Hi,
I have a first draft of the packet-specification available:
https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14264
The specification is available as an attachment to the following
wireshark bugzilla entry:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12033
This first draft does n
> Am 20.01.2016 um 03:00 schrieb Guy Harris :
>
> On Jan 19, 2016, at 5:50 PM, Guy Harris wrote:
>
>> OK, so the new format is that the frame begins with a measurement header,
>> which is followed by the bitstream from the bus?
Yes. It only contains additional information. The idea is that th
2016-01-15 21:35 GMT+01:00 Guy Harris :
>
> On Jan 15, 2016, at 10:44 AM, Guenter Ebermann
> wrote:
>
> I don't know whether Hannes still works at X2E. You might want to try
> sending an e-mail to him asking whether a format for DLT_FLEXRAY was ever
> defined - and
Hi,
For which type of frame was the LINKTYPE_FLEXRAY 210 allocated?
The file https://github.com/the-tcpdump-group/libpcap/blob/master/pcap-common.c
simply state that:
/*
* FlexRay automotive bus - http://www.flexray.com/ - as requested
* by Hannes Kaelber .
*/
#define LINKTYPE_FLEXRAY 210
Als
