From: Dave Taht <dave.taht@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net
Subject: [Make-wifi-fast] Fwd: [Battlemesh] BSS load element patch
Date: Fri, 7 Aug 2015 12:09:20 +0200 [thread overview]
Message-ID: <CAA93jw55S+3uXiBz=RHb-zOcJoQ2JqNEJNJiaYNdBvheeOQ==g@mail.gmail.com> (raw)
In-Reply-To: <55C47A29.5010402@ftw.at>
---------- Forwarded message ----------
From: Paul Fuxjaeger <fuxjaeger@ftw.at>
Date: Fri, Aug 7, 2015 at 11:28 AM
Subject: Re: [Battlemesh] BSS load element patch
To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
On 05.08.15 14:57, Bastian Bittorf wrote:
> Does e.g. a client gets informed about a congested network
Exactly.
It allows nearby clients/nodes to make MUCH better decisions. [1]
> or in other words: does it solve a problem?
###
Essentially, very small local channel utilization measurement reports
are broadcasted to all direct neighbors by piggybacking them onto
IEEE802.11 beacons. [2]
###
1) Maintainers could better distinguish causes of link problems [3]
2) Our current algorithms for rate control, routing and
network-selection could make better decisions if they have access this
"remote channel load" statistic.
So, we think this feature could be really helpful. It increases the
networks capability to self-regulate, for a small price. [4]
-paul
PS: Arthur did all the hard work, I'm just doing the cheap talking.
[1] that is probably the reason for recent AP models in the enterprise
segment already broadcasting it.
[2] channel utilization measured at the receive antenna port of the
device that is sending that beacon.
[3] if LTE-U/LAA/muLTEfire becomes widespread :( we need a way to detect
that such a nearby non-IEEE80211 source is blocking the channel.
[4] Currently, OpenWRT sends around 200bytes PSDUs per beacon (depending
on mode etc). Assuming a 100ms beacon interval and 1Mbit/s, adding
these 7 bytes to them would increase the channel utilization each
beaconing node is generating by less than 0.06% of total airtime.
_______________________________________________
Battlemesh mailing list
Battlemesh@ml.ninux.org
http://ml.ninux.org/mailman/listinfo/battlemesh
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next prev parent reply other threads:[~2015-08-07 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55BFBBF1.4080709@lena.im>
2015-08-07 10:08 ` Dave Taht
[not found] ` <20150805125746.GR25597@medion.lan>
[not found] ` <55C47A29.5010402@ftw.at>
2015-08-07 10:09 ` Dave Taht [this message]
2015-08-07 10:55 ` Michael Welzl
2015-08-07 17:21 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw55S+3uXiBz=RHb-zOcJoQ2JqNEJNJiaYNdBvheeOQ==g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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