Prefer higher-frequency band when a node has multiple simultaneous me…#253
Draft
VA2XJM wants to merge 1 commit into
Draft
Prefer higher-frequency band when a node has multiple simultaneous me…#253VA2XJM wants to merge 1 commit into
VA2XJM wants to merge 1 commit into
Conversation
…sh radios On nodes like HaLowLink1 that can run more than one radio in a mesh role at once (e.g. HaLow + 2.4GHz), babeld_wrapper now ranks each mesh wlan interface by band and adds a configurable rxcost_penalty (default 256) to any radio that isn't the highest-frequency band present, so babel prefers the faster/less-congested link and leaves the narrower band's bandwidth free for peers that can only reach the node that way. The penalty is only ever applied relative to another mesh radio on the same node, so nodes with a single mesh radio see no change in behavior. Band is determined primarily from the mesh radio's configured channel bandwidth (HaLow is the only band using sub-5MHz widths), falling back to iw-reported frequency otherwise, since HaLow interfaces can report a translated/bogus frequency via iw dev info.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goes with aredn/aredn#2800
mesh radios
On nodes like HaLowLink1 that can run more than one radio in a mesh role at once (e.g. HaLow + 2.4GHz), babeld_wrapper now ranks each mesh wlan interface by band and adds a configurable rxcost_penalty (default 256) to any radio that isn't the highest-frequency band present, so babel prefers the faster/less-congested link and leaves the narrower band's bandwidth free for peers that can only reach the node that way. The penalty is only ever applied relative to another mesh radio on the same node, so nodes with a single mesh radio see no change in behavior.
Band is determined primarily from the mesh radio's configured channel bandwidth (HaLow is the only band using sub-5MHz widths), falling back to iw-reported frequency otherwise, since HaLow interfaces can report a translated/bogus frequency via iw dev info.