What are these settings used for?
WDS Default Cost:
Cost Range:
I see that nobody answered. I’d like to know that also.
I’m trying to figure out a way to use the quality of a link to determine the path cost on a bridged network.
I’m having the problem of the bridge selecting links that have gone marginal due to fading. Because the link was originally configured with a lower path cost, it keeps getting selected as the route path. This is proper behavior when the link is performing well, but I want the bridge to select another path when the link gets bad enough that it starts flickering on and off.
I was wondering if the WDS cost range parameter would help with this.
My google search turned up nothing but your post.
Anyone at MikroTik HQ care to comment on these undocumented parameters?
from the documentation:
wds-cost-range (integer; default: 50-150) - range, within which the bridge port cost of the WDS links are adjusted. The calculations are based on the p-throughput value of the respective WDS interface, which represents estimated approimate rhtoughput on the interface, which is mapped on the wds-cost-range scale so that bigger p-throughput would correspond to numerically lower port cost. The cost is recalculated every 20 seconds or when the p-throughput changes more than by 10% since the last recalculation
wds-default-cost (integer; default: 100) - default bridge port cost of the WDS links
p-throughput (read-only: integer) - (on station only) estimated approximate throughput that is expected on the given link, by taking into account the effective transmit rate and hardware retries. Calculated once in 5 seconds
Thank you uldis! Since I have ROS 2.9.50 I didn’t check the R3 documentation.
These parameters do not show up in the 2.9 documentation.
Am I correct in assuming that the description in R3 applies to 2.9?
If this is working as expected, with the values left as default, will I see the bridge port cost value as shown in
the bridge port print command reflect the adjusted value if the link is working poorly? On my 2.9.50 system,
I do not see the bridge port costs change as the links fade.
It also appears, on my ROS 2.9.50, that even with a very poorly performing link, the bridge selects the port with the lowest configured cost, not modified by wds-cost-range. I would expect to see the ‘good’ link become the root path and the ‘bad’ link become the alternate path. This does not happen on my 2.9.50 nodes.
Also, do I assume that the values like 50 and 150 are percent values that are applied to the configured
bridge port cost?
The value called p-throughput would be useful to debug this, but I see that it’s only available on station. My
wds links are between radios configured as AP-bridge. Does wds-cost-range work in AP-bridge mode, even though the p-throughput variable is only displayed in station mode?
Thanks for pointing this out. Are there plans to update the 2.9 documentation, or should we 2.9 users consult
the 3.0 docs for the latest in 2.9 feature descriptions. It’s hard, in that case, to tell if the 3.0 docs are describing
a feature as it works in 3.0 or just adding to the description in the 2.9 doc to make it more clear.
If this feature is really in 2.9.50, it is exactly what I need. Since it doesn’t appear to be working in my network, perhaps I need to configure it differently?
Thanks for your help on this.