[tcpdump-workers] DLT for RFtap

[George Hopkins via tcpdump-workers]

--- Begin Message ---
Hello

A few years ago there was a request to assign a DLT for RFtap [1]:
https://lists.sandelman.ca/pipermail/tcpdump-workers/2016-August/000619.html

Somehow some of the messages weren't kept by the archive. As I
understand it, it would only be possible to assign a DLT if the RFtap is
tied to an actual link-layer type (e.g. RFtap followed by AX25). Does
this assumption still hold? If so, is there an other, recommended way to
store such information?

Thanks,
George Hopkins

[1]: https://rftap.github.io/specifications/
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers

Re: [tcpdump-workers] DLT for RFtap

[George Hopkins via tcpdump-workers]

--- Begin Message ---
On Fri, Sep 11, 2020 at 01:16:03PM -0400, Michael Richardson wrote:
>
> I think that I fail to understand some subletie in the question.
> I think that RFtap is essentially a new DLT which happens to be able to
> include other DLT inside of it?

Yes, specifically I was looking for a pre-built way to store the
frequency offset and signal power of packets received over a custom
radio interface. RFtap would fit these requirements and is already
supported by Wireshark.

> pcapng has a better solution to that, but I respect that it isn't ubiquitous
> yet. (I blame myself really)

I'm not opposed to using pcapng for this purpose, I just looked for the
easiest way possible. Would you mind giving me a hint how to do store it
in pcapng? As far as I understood the specifications the information
could be stored as a (custom) option in an Enhanced Packet Block. Is
there a better/already specified way to do it?
--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers