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: Mon, 28 Feb 2011 13:37:20 +0100 [thread overview]
Message-ID: <20110228123720.GG4698@lunn.ch> (raw)
In-Reply-To: <AANLkTim+tN9NKUUHJqcaaxS-RpWeLQqrUoB0D+=sA0J7@mail.gmail.com>
> In attachment you will also find a draft/proposals of a new routing
> approach. It is based on the collection of more link parameters (the
> current TQ, bit-rate and node-load) to write in OGM at each hop. This
> permit to develop a more thorough metric and can open new room of
> improvement such multi-path routing.
Hi Daniele
Do you have any suggestions how to collect this bit-rate information?
Do you suggest measuring it, or asking the wireless LAN driver? Is
there an API in the kernel to allow access to this information?
Also, how do you see this interacting with the hidden node problem? In
order to reduce the hidden node problem, you ideally want to use the
lowest coding rate and transmit power possible to get your packets
through. Currently this is not being done. Current wireless systems
optimize for maximum bandwidth between two nodes, which may not be the
optimum for the complete mesh bandwidth, due to inter node
interference.
Will you be at the WBMv4 next Month?
Andrew
next prev parent reply other threads:[~2011-02-28 12:37 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 [this message]
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
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=20110228123720.GG4698@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