[Battlemesh] Off-topic: tcpdump/Wireshark support for olsrd2?

Albert Rafetseder albert.rafetseder+v10 at univie.ac.at
Thu Apr 5 08:06:00 CEST 2018

Hello Henning,

Thank you very much for your swift and educational reply.

> So yes, you can decode OLSRv2 and NHDP with wireshark.

Yes, I can confirm. Now I see message upon message, TLV upon TLV!

I was set on the wrong track by my toy example trace of a single router
with no neighbors, and the "packetbb" protocol designation that my web
searches failed to link to olsrd2.

With a trace from a populated network and the right search terms
("olsr", not "olsrd2", d'oh!) in hand, things fall into place.

> (I provided the original dissector to Wireshark years ago)

Cool! I saw that a few message types that RFC5444 reserves for
"experimental use" are not yet decoded though, e.g. 227:


If you don't mind, I can probably contribute this to the dissector at
some point.


> Henning Rogge
> On Wed, Apr 4, 2018 at 4:43 PM, Albert Rafetseder
> <albert.rafetseder+v10 at univie.ac.at> wrote:
>> Hello Battlemeshers,
>> Apologies upfront for cross-posting this off-topic issue from the OLSR
>> user mailing list!
>> We are debugging a (presumed) olsrd2 issue in our community network,
>> https://funkfeuer.at/ , and wonder if there is a packet printer /
>> dissector for olsrd2 that we can use.
>> Are there private efforts any of you are willing to share or have us
>> contribute to?
>> I've tested tcpdump and Wireshark so far, neither of which decodes
>> olsrd2 currently.
>> My local OS X tcpdump is 4.7.3 - Apple version 67, built with libpcap
>> version 1.5.3 - Apple version 54. It does not support printing details
>> for olsrd2.
>> I've skimmed tcpdump's issue tracker and list of pull request, but found
>> nothing matching.
>> tcpdump's v1 printer is here,
>> https://github.com/the-tcpdump-group/tcpdump/blob/master/print-olsr.c
>> I also tried Wireshark in its most recent stable (2.4.6) and development
>> (2.5.1) versions, to no avail. UDP port 269 is auto-recognized as
>> "PacketBB". The manual decoding options only include OLSR (v1), not
>> olsrd2. This is Wireshark's v1 dissector:
>> https://code.wireshark.org/review/gitweb?p=wireshark.git;a=blob;f=epan/dissectors/packet-olsr.c;h=419e3db9e2186a01634b2bb47809abdfb3d51f5c;hb=HEAD
>> Wireshark's Gerrit issue tracker lists no hits for OLSR either.
>> Any hints?
>> Thank you,
>>   Albert.
>> _______________________________________________
>> Battlemesh mailing list
>> Battlemesh at ml.ninux.org
>> http://ml.ninux.org/mailman/listinfo/battlemesh
> _______________________________________________
> Battlemesh mailing list
> Battlemesh at ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh

More information about the Battlemesh mailing list