Thanks. Created PR for libpcap and tcpdump. Wireshark changes pending. https://github.com/the-tcpdump-group/libpcap/pull/803 https://github.com/the-tcpdump-group/tcpdump/pull/734
The existing DLTs for IEEE 802.15.4 have versions for FCS, NOFCS, NONASK_PHY, and LINUX (address fields padded). The NONASK_PHY includes only fixed preamble bytes, and the FCS/NOFCS versions support for heuristic match for ZBOSS generated format again with some fixed fields. The proposed format attempts to wrap up the different types into one and provide an extensible TLV format for capture devices to provide additional meta-data. James On Fri, Feb 15, 2019 at 9:45 AM Michael Richardson <m...@sandelman.ca> wrote: > > James Ko <j...@exegin.com> wrote: > > Is there something blocking my request? Concerns that I may address > to get > > an assignment? > > I don't recall seeing it last week, sorry. > > > On Fri, Feb 8, 2019 at 3:37 PM James Ko <j...@exegin.com> wrote: > > >> Please assign a new DLT_/LINKTYPE_ value for IEEE802_15_4_TAP > packets. > >> > >> The IEEE 802.15.4 TAP packet format proposal is in > >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15429. > >> > >> IEEE 802.15.4 defines both PHY and MAC layers and the proposed > format > >> enables the sniffer/tap device to provide additional information > from both > >> layers. > > 1) You are welcome to send pull request! > 2) I see that Guy has engaged your ticket. I could have sworn we already > had > 802.15.4 DLT that could take a variety of extra data. > > -- > ] Never tell me the odds! | ipv6 mesh > networks [ > ] Michael Richardson, Sandelman Software Works | IoT > architect [ > ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on > rails [ > > > _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
