Hi legends.
I am trying to understand how DWB weights the path priorities for each uplink. I have set all my expected U/D limits on the dashboard for each interface as I have tested them under load in a changing congesting environment I want to aim for the most consistent services throughout the time period.
SF seems to override these configs and disregard them completely. I have all WANs in P1 because I want to keep the tunnel active and not have to rebuild on a link failure but I would like to be able to see the weights that have been applied to DWB. is this something that can be done via API? I just find it to be very inconsistent with its choices and would ideally like to steer it to what I think is best.
See below - this is favoring a long range 5G service 50/10 over 2x starlinks.
STLent: HP in priority 1tb - 400/50
STL06: is a gen2 in priority 1tb. 250/20
The Starlinks have far greater data pools and bandwidth so it would be nice if i could get them to be weighted higher without completely dropping the 5G into warm failover.
this seems to change if I restart the tunnel for no apparent reason. I would like to get some eyes on what is going on the background so that I can work with it a bit better and hopefully guid it to do what I want a little bit.
I have also noticed that when it favors the starlink ent HP as the p1 we tend to get much higher aggregate through put closer to 300/50 while 5g in p1 gets closer to 100/5
