T-X

> Since this is inconsistent in the website itself, do you have any ideas how this could be handled? I've briefly been wondering if it could be fixed up by...

Throwing in another idea: * Similar to IPv6 Neighbor Discovery "Solicited-Node Multicast Addresses" (see RFC4861 and RFC4291) generate a "Meshenger Peer Discovery" Multicast Address. Example: * Take the /64 interface...

> So that I understand this correctly: > > * this would enable enable direct calls in layer 3 networks with the help of multicast groups and pim6sd. > >...

One remark: pcap/batadv_packet.h and pcap/batadv_legacy_packet.h are basically copies from the Linux kernel and are therefore GPLv2 licensed. Let me know if that's okay for you or if I should ask...

Thanks for the great feedback! Changelog v2: * changes to batadv_{legacy_,}packet.h: * integrated @guyharris' suggested changes: removal of #pragma packed(2), bitfield endianess #ifdefs, Linux specific includes, unused definitions, conversion to...

Changelog v3: * removed unused variables "s" and "b1" in gen_batadv() to satisfy the AppVeyor CI / Visual Studio builds

Changelog v4: * changed offset parameter of gen_batadv_push_offset() from size_t to u_int and added according type cast on callers, to make AppVeyor CI / Visual Studio happy

@infrastation sure, generating some test packets is no issue, can do that next weekend. According tests need to be added to the tcpdump repository in a separate commit over there,...

Some simple tests for tcpdump for the batman-adv version 15 packet types and their decoding offsets can be found here: https://github.com/the-tcpdump-group/tcpdump/pull/891

I'm a bit hesitant to ask, as I can see with all the frequent commits that everyone is very eagerly working on libpcap/tcpdump. But any chance to get this merged?...