From: Andrew Lunn <andrew@lunn.ch>
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.] OGM overhead and routing metric proposal
Date: Tue, 1 Mar 2011 10:13:28 +0100 [thread overview]
Message-ID: <20110301091328.GD4022@lunn.ch> (raw)
In-Reply-To: <20110301085141.GA24189@Sellars>
> But I'm actually also a little confused why you, Andrew, came up
> with the hidden node problem :) (which these papers did not try to
> solve, if I'm not missing something). Or do you mean, that this
> idea could be extended maybe be able to solve that hidden node
> problem for OGMs, using the bitrate measuremens to detect / avoid
> switching to bad links?
Hi Linus
If we can extend minstrel so that it also takes transmit power and
load into consideration, we might be able to optimize the coding rate
& TX power for complete mesh bandwidth, not a single link bandwidth.
I would expect there are a number of research papers looking at this,
and many ideas which can be taken from cellular networks. I also think
the commercial mesh products do this.
However, for Daniele idea of putting the coding rate into the OGM, we
probably need the achievable coding rate, not the current coding rate.
It could be the link is idle, so is using the lowest coding rate and
minimum TX power, just to carrier a few ARP reply packets etc. If
however the link becomes loaded, it would increase the coding rate and
TX power so allowing more packets through.
Daniele's idea is good, but i'm just being careful it does not block
ideas like dynamic coding rate/TX power control.
Andrew
next prev parent reply other threads:[~2011-03-01 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 11:50 [B.A.T.M.A.N.] OGM overhead and routing metric proposal Daniele Furlan
2011-02-28 12:37 ` Andrew Lunn
2011-02-28 13:07 ` Daniele Furlan
2011-02-28 14:48 ` Andrew Lunn
2011-02-28 16:00 ` Daniele Furlan
2011-03-01 8:51 ` Linus Lüssing
2011-03-01 9:13 ` Andrew Lunn [this message]
2011-03-01 9:42 ` Daniele Furlan
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=20110301091328.GD4022@lunn.ch \
--to=andrew@lunn.ch \
--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