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.] [PATCH] batman-adv: introduce "noflood" broadcast flood prevention option
Date: Tue, 30 Apr 2019 18:07:26 +0200 [thread overview]
Message-ID: <20190430160726.GD5267@otheros> (raw)
In-Reply-To: <20190430160121.GC5267@otheros>
On Tue, Apr 30, 2019 at 06:01:21PM +0200, Linus Lüssing wrote:
> So while that was the main use-case for me before the discussions
> we had last year on how to improve DAT, it's now more a minor one
> for me. Though it would still be nice to have / work towards a zero-broadcast
> mesh as RFC7772 for instance explains that frequent broadcasts
> have a quite significant impact on battery power for small, mobile
> devices. And the noflood option would be a quick and easy option
> for us for now to achieve this for ARP and other packet types.
>
> [0]: https://tools.ietf.org/html/rfc7772
More precisely, RFC7772 section 4 has some estimates regarding power
cost for having frequent broadcast packets.
next prev parent reply other threads:[~2019-04-30 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 17:12 [B.A.T.M.A.N.] [PATCH] batman-adv: introduce "noflood" broadcast flood prevention option Linus Lüssing
2019-04-26 21:56 ` Marek Lindner
2019-04-27 2:38 ` Linus Lüssing
2019-04-27 2:53 ` Linus Lüssing
2019-04-28 17:04 ` Sven Eckelmann
2019-04-28 19:04 ` Martin Weinelt
2019-04-30 16:01 ` Linus Lüssing
2019-04-30 16:07 ` Linus Lüssing [this message]
2019-05-02 6:40 ` 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=20190430160726.GD5267@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