On Aug 25, 2018, at 1:27 PM, Guy Harris <ghar...@sonic.net> wrote:
> On Aug 25, 2018, at 1:10 PM, Matwey V. Kornilov <matwey.korni...@gmail.com>
> wrote:
>
>> Answering your questions and Michael question, the url describes the
>> data coming from the hardware as is. Its format is defined by the
>> people developing FPGA firmware, that is currently not quite active:
>> https://github.com/openvizsla/ov_ftdi/tree/master/software/fpga So it
>> is unlikely that the format will change dramatically, but I just would
>> like to follow initial format as close as possible.
>
> I suspected that's what the FPGA delivered.
>
>> However, I agree that we can just use the following simple
>> representation for pcap:
>>
>> struct {
>> uint32_t timestamp;
>> uint16_t flags;
>> uint8_t usb_packet[];
>> };
>
> So your code to construct pcap files (or your libpcap module) would shuffle
> the header data around before providing the packet?
So which would be better:
1) the raw data from
https://github.com/matwey/libopenvizsla/wiki/OpenVizsla-protocol-description
is what's in the packet in a pcap or pcapng file, and we just note
that the Size field is redundant (it's the captured length minus 8 for the
header)
or
2) the simple representation?
We can do either one.
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
