From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [PATCH 0/3] batctl: tcpdump: Add support to identify missing packets
Date: Sun, 9 Jun 2019 18:56:49 +0200 [thread overview]
Message-ID: <20190609165652.12841-1-sven@narfation.org> (raw)
Hi,
when running batctl's tcpdump today on a normal batman-adv slave interface,
you will see warnings like:
Warning - packet contains unknown batman packet type: 0x41
Warning - packet contains unknown batman packet type: 0x02
This is caused by missing dumping routinges in the tcpdump implementation.
Since these packets (coded, fragmented) cannot be decoded/reassembled
easily these packets are only identified and some basic header informations
are shown.
Also not all TVLVs in the header were shown. The mcast part was dropped and
thus the debugging of the new mcast feature flags was not possible with
batctl.
Kind regards,
Sven
Sven Eckelmann (3):
batctl: tcpdump: Add support for MCAST TVLV
batctl: tcpdump: Add support for unicast fragmentation
batctl: tcpdump: Add support for coded packets
tcpdump.c | 110 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
tcpdump.h | 1 +
2 files changed, 110 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2019-06-09 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 16:56 Sven Eckelmann [this message]
2019-06-09 16:56 ` [PATCH 1/3] batctl: tcpdump: Add support for MCAST TVLV Sven Eckelmann
2019-06-09 16:56 ` [PATCH 2/3] batctl: tcpdump: Add support for unicast fragmentation Sven Eckelmann
2019-06-09 16:56 ` [PATCH 3/3] batctl: tcpdump: Add support for coded packets Sven Eckelmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190609165652.12841-1-sven@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).