freifunk-common: set default mcate_rate for 802.11s #34
Conversation
Set the default mcast_rate for 802.11s to 12000. This value is derived from the experiences made at Freifunk Berlin and the best working value for both 2.4 and 5Ghz for the largest running 802.11s mesh-island in the network. Signed-off-by: pmelange <isprotejesvalkata@gmail.com>
|
What's the basis for "best working value"? are there comparisons with other values avail? |
|
The is the test network. Experimented with many possible combinations. For more details, contact @kls0e https://hopglass.berlin.freifunk.net/#!v:m;n:kls0e-d0nut.olsr |
|
@kls0e can you provide some numbers why this is the "best working value"? So that a benefit of this merge can be seen. Not sure if anyone will merge "just out of the blue" ... |
SvenRoederer
added
enhancement
|
Not 100% sure if it'd help, but you can derive a list for Gluon based firmwares typically from the site.conf from the community site repositories listed here: https://github.com/freifunk-gluon/gluon/wiki/Site-Configurations I picked 10 random ones and 9 of those had an mcast rate of 12 MBit/s and one had 24 MBit/s. Usually a higher mcast rate increases available airtime. But a higher mcast rate also helps especially packet loss based routing protocols which use broadcast packets to probe link quality to find better / higher throughput paths. Downside of higher mcast rates is a slightly reduced distance, of course. But it's not as significant as in the old 802.11b/g days (at least with values between 12 and 24 MBit/s). |
|
I am closing the PR as it seems like the freifunk community has no interest in merging this. |
Set the default mcast_rate for 802.11s to 12000. This
value is derived from the experiences made at Freifunk Berlin
and the best working value for both 2.4 and 5Ghz for the
largest running 802.11s mesh-island in the network.
Signed-off-by: pmelange isprotejesvalkata@gmail.com