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.] No rebroadcast on mesh links
Date: Thu, 31 Mar 2016 19:17:55 +0200 [thread overview]
Message-ID: <20160331171755.GD2989@otheros> (raw)
In-Reply-To: <20160331160141.GG5258@prodigo.lan>
On Fri, Apr 01, 2016 at 12:01:41AM +0800, Antonio Quartulli wrote:
> On Thu, Mar 31, 2016 at 02:11:19PM +0200, Simon Wunderlich wrote:
> > I thought a little more on automation, but I'm now at a point to agree that
> > there is no good way to do it - at least I'm out of ideas. If anyone else has
> > some ideas, please speak up NOW. :)
>
> Some time ago we had a proposal (by Linus I believe) which was about detecting
> transitive interfaces by exchanging neighbour tables between peers. This way a
> node can understand if every other node behind an interface can talk to each
> other or not.
Basically the first ELP patches had provided that information
already, there was a table of neighbors together with the measured
link RX metric. But the ELP version merged now is simpler with less overhead
and does not have such a table anymore, as the link metric is now
provided by mac80211 / the rate selection algorithm.
> Although this approach sounds more complex, it would also help optimizing the wifi
> case: a node can understand if the hosts in an adhoc cells can all talk to each
> other and then avoid the retransmission (thus saving previous airtime - as we
> would save bandwidth in a VPN).
Indeed.
>
> The only problem is that this would work only after extending BATMAN V and would
> unlikely be implemented in BATMAN IV.
I wouldn't see it as a problem but a feature instead, helping to
motivate to migrate to BATMAN V ;). Also, Matthias provides Debian
packages for BATMAN IV which includes the manual switch, so
it shouldn't be too painful for BATMAN IV users either.
>
> Not sure if Linus (?) or anybody else is willing to work on this....but I guess
> people would like a solution to be used on BATMAN IV ? Or is this an option ?
Back then I think I said (and this is still the case) I would love
to work on a detection mechanism, but only once the multicast
things are finished. I don't want to drag multiple patchsets along
for years.
If anyone else wants to work on that, great :).
next prev parent reply other threads:[~2016-03-31 17:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 21:35 [B.A.T.M.A.N.] No rebroadcast on mesh links Roland Volkmann
2016-03-25 22:46 ` Sven Eckelmann
2016-03-25 23:19 ` Roland Volkmann
2016-03-27 2:38 ` Marek Lindner
2016-03-28 13:43 ` Roland Volkmann
2016-03-28 14:43 ` Marek Lindner
2016-03-28 19:11 ` Linus Lüssing
2016-03-28 21:19 ` Roland Volkmann
2016-03-28 23:52 ` Linus Lüssing
2016-03-29 8:37 ` Adrian Reyer
2016-03-29 9:50 ` Sven Eckelmann
2016-03-29 17:59 ` Adrian Reyer
2016-03-29 18:55 ` Sven Eckelmann
2016-03-29 23:37 ` Roland Volkmann
2016-03-30 2:15 ` Marek Lindner
2016-03-30 8:00 ` Sven Eckelmann
2016-03-30 9:09 ` Roland Volkmann
2016-03-30 12:23 ` Sven Eckelmann
2016-03-30 11:58 ` Simon Wunderlich
2016-03-30 13:58 ` Adrian Reyer
2016-03-30 16:08 ` Sven Eckelmann
2016-03-30 19:55 ` Adrian Reyer
2016-03-31 12:11 ` Simon Wunderlich
2016-03-31 12:21 ` Simon Wunderlich
2016-03-31 15:54 ` Antonio Quartulli
2016-03-31 16:25 ` Linus Lüssing
2016-03-31 15:35 ` Linus Lüssing
2016-03-31 15:49 ` Antonio Quartulli
2016-03-31 16:53 ` Linus Lüssing
2016-03-31 16:01 ` Antonio Quartulli
2016-03-31 17:17 ` Linus Lüssing [this message]
2016-04-13 12:17 ` Simon Wunderlich
2016-04-13 12:22 ` Sven Eckelmann
2016-03-29 0:02 ` Linus Lüssing
2016-03-29 6:38 ` Roland Volkmann
2016-03-30 8:08 ` 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=20160331171755.GD2989@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 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.