From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [RFC v2 0/1] batctl: netlink restructuring, part 3
Date: Fri, 23 Nov 2018 17:14:41 +0100 [thread overview]
Message-ID: <20181123161442.13461-1-sven@narfation.org> (raw)
As mentioned earlier, the netlink config restructuring in batctl will be
splitted in multiple steps. The first step was already merged and the
RFC changes for the netlink interface in batman-adv were just posted.
It doesn't make sense to have a full implementation in batctl when
the batman-adv part is not yet in a state which survived the RFC phase. But
it also is useless to have only the batman-adv RFC part without at least
something in userspace. I have now only added the event monitor so it is
possible to at least parse the messages from the kernel.
An implementation of the sysfs config helper with netlink support (and sysfs
fallback) will be implemented when the RFC phase of the batman-adv part
doesn't require any major changes anymore.
v2:
* drop of generic config command
* reimplementation of the event command
Kind regards,
Sven
Sven Eckelmann (1):
batctl: Add support for config mcast group in event monitor
batman_adv.h | 188 +++++++++++++++++++++++++++++++++++++++--
event.c | 234 +++++++++++++++++++++++++++++++++++++++++++++++++++
netlink.c | 20 +++++
3 files changed, 437 insertions(+), 5 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-23 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 16:14 Sven Eckelmann [this message]
2018-11-23 16:14 ` [B.A.T.M.A.N.] [RFC v2 1/1] batctl: Add support for config mcast group in event monitor 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=20181123161442.13461-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).