All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Кирилл Луконин" <klukonin@gmail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Gui Iribarren <gui@altermundi.net>, openwrt-devel@lists.openwrt.org
Subject: Re: [B.A.T.M.A.N.] [RFC openwrt-routing] batman-adv: Split batadv proto in meshif and hardif part
Date: Mon, 25 Feb 2019 13:03:52 +0500	[thread overview]
Message-ID: <CALYz8yqCAkcrvjcBhgf-2YYTrejhEXnnbRWP3bCtv-joXfP3jA@mail.gmail.com> (raw)
In-Reply-To: <2667717.mmYbNj13ue@bentobox>

Hello.


That looks pretty cool.
But what about ELP interval parameter?
As I think, it should be covered by UCI config too.


Best Regards,
Lukonin Kirill

пн, 25 февр. 2019 г. в 12:36, Sven Eckelmann <sven@narfation.org>:
>
> On Monday, 25 February 2019 02:24:56 CET Gui Iribarren wrote:
> > have you considered, to simplify backwards compatibility, to keep proto
> > "batadv" as it currently is (hardif) and naming "batadv_mesh" the new proto?
>
> It was one of the goals to *not* name the batadv hardif interface proto
> "batadv". And I wanted to have the batman-adv interface proto named "batadv"
> because this is the rtnl kind string. So you actually create batman-adv
> meshifs using:
>
>    ip link add dev bat0 type batadv
>
> But we can call this proto also "batadv_meshif" if there is a strong
> preference for this name.
>
> Kind regards,
>         Sven

  reply	other threads:[~2019-02-25  8:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 16:51 [B.A.T.M.A.N.] [RFC openwrt-routing] batman-adv: Split batadv proto in meshif and hardif part Sven Eckelmann
2019-02-25  1:24 ` Gui Iribarren
2019-02-25  7:35   ` [B.A.T.M.A.N.] " Sven Eckelmann
2019-02-25  8:03     ` Кирилл Луконин [this message]
2019-02-25  8:22       ` Sven Eckelmann
2019-03-07 15:55 ` Simon Wunderlich

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=CALYz8yqCAkcrvjcBhgf-2YYTrejhEXnnbRWP3bCtv-joXfP3jA@mail.gmail.com \
    --to=klukonin@gmail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=gui@altermundi.net \
    --cc=openwrt-devel@lists.openwrt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.