b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] Broadcast Avoidances, Neighborhood Hash
Date: Tue, 20 Sep 2016 14:12:42 +0200	[thread overview]
Message-ID: <20160920121245.593-1-linus.luessing@c0d3.blue> (raw)

Hi,

Here's the second broadcast avoidance patchset (rebased on the former one).

Hopefully, those two patchsets together should be an automatic
approach and replacement for the (non-upstream) no-rebroadcast flag
patch and the cases it is currently used for.

Documentation:
* https://www.open-mesh.org/projects/batman-adv/wiki/Broadcast-Avoidances

Branch:
* https://git.open-mesh.org/batman-adv.git/shortlog/refs/heads/linus/neighhash

Regards, Linus


             reply	other threads:[~2016-09-20 12:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 12:12 Linus Lüssing [this message]
2016-09-20 12:12 ` [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: Store and transmit own neighborhood hash Linus Lüssing
2016-09-20 13:01   ` Sven Eckelmann
2016-09-29 15:31   ` Sven Eckelmann
2016-10-06  1:55     ` Linus Lüssing
2016-10-06  3:03       ` Linus Lüssing
2016-10-06 15:41     ` Linus Lüssing
2016-09-29 16:05   ` Sven Eckelmann
2016-09-29 16:39   ` Sven Eckelmann
2016-09-20 12:12 ` [B.A.T.M.A.N.] [PATCH 2/3] batman-adv: Introduce packet type independent TVLV handler API Linus Lüssing
2016-09-29 16:05   ` Sven Eckelmann
2016-09-29 16:46   ` Sven Eckelmann
2016-09-20 12:12 ` [B.A.T.M.A.N.] [PATCH 3/3] batman-adv: Evaluate and use neighborhood hash TVLV Linus Lüssing
2016-09-29 15:48   ` Sven Eckelmann
2016-09-29 16:05   ` Sven Eckelmann
2016-09-29 16:55   ` Sven Eckelmann
2016-09-20 12:23 ` [B.A.T.M.A.N.] Broadcast Avoidances, Neighborhood Hash Linus Lüssing

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=20160920121245.593-1-linus.luessing@c0d3.blue \
    --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;
as well as URLs for NNTP newsgroup(s).