From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [RFC v4 00/20] batctl: netlink restructuring, part 3
Date: Mon, 7 Jan 2019 19:57:13 +0100 [thread overview]
Message-ID: <20190107185712.GD5399@otheros> (raw)
In-Reply-To: <20181207203209.22633-1-sven@narfation.org>
On Fri, Dec 07, 2018 at 09:31:49PM +0100, Sven Eckelmann wrote:
> 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.
>
> The batman-adv weren't directly rejected by Jiro and thus I've started
> to convert all settings to netlink while still allowing sysfs as fallback.
>
Is "batctl if" supposed to use netlink to get the interface status
yet?
Currently, with the items in *_attr[] in sysfs.c in batman-adv
commented out, I get these errors:
---
root@Linus-Debian:~# batctl if
ens3: <error reading status>
ens5: <error reading status>
---
next prev parent reply other threads:[~2019-01-07 18:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 20:31 [B.A.T.M.A.N.] [RFC v4 00/20] batctl: netlink restructuring, part 3 Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 01/20] batctl: Add support for config mcast group in event monitor Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 02/20] batctl: Don't allocate new buffer for vlan parent device Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 03/20] batctl: Automatically translate vlan to mesh_iface Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 04/20] batctl: Add settings_data hooks for netlink integration Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 05/20] batctl: Parse the arguments for gw_mode Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 06/20] batctl: Add netlink simple query helper Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 07/20] batctl: Support generic netlink for gw_mode command Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 08/20] batctl: Support generic netlink for loglevel command Sven Eckelmann
2019-01-07 16:57 ` Linus Lüssing
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 09/20] batctl: Support generic netlink for isolation_mark command Sven Eckelmann
2018-12-07 20:31 ` [B.A.T.M.A.N.] [RFC v4 10/20] batctl: Support generic netlink for orig_interval command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 11/20] batctl: Add helper to read/write boolean configuration values Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 12/20] batctl: Support generic netlink for aggregation command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 13/20] batctl: Support generic netlink for ap_isolation command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 14/20] batctl: Support generic netlink for bonding command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 15/20] batctl: Support generic netlink for bridge_loop_avoidance command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 16/20] batctl: Support generic netlink for distributed_arp_table command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 17/20] batctl: Support generic netlink for fragmentation command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 18/20] batctl: Support generic netlink for multicast_mode command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 19/20] batctl: Support generic netlink for network_coding command Sven Eckelmann
2018-12-07 20:32 ` [B.A.T.M.A.N.] [RFC v4 20/20] batctl: Drop settings_date param lists Sven Eckelmann
2019-01-07 18:57 ` Linus Lüssing [this message]
2019-01-08 7:37 ` [B.A.T.M.A.N.] [RFC v4 00/20] batctl: netlink restructuring, part 3 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=20190107185712.GD5399@otheros \
--to=linus.luessing@c0d3.blue \
--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