Asymmetric routing

[Orbit173]

I have three nodes connected in series nodeNL -> nodeDE -> nodeRU
nodeNL - client
nodeDE has about ~90 peers with over members
nodeRU has ~10 peers.

If i run iperf3 testing inside ygg between nodeDE and nodeRU (download and upload), the traffic goes directly.
When between nodeNL and nodeRU, upload goes directly, but download goes through a third pary.
nodeRU for some reason prefers peer with the lowest cost instead of the shortest path.
In adding, every few minutes nodeNL loses its avalilability with nodeRU (no ping), but nodeDE can ping.

Upload schema

Download schema

[neilalexander]

It should be noted that symmetric routing is not guaranteed in Yggdrasil. It may also be that there are nodes on the path running different Yggdrasil versions as we have tweaked the link costing a couple times in recent versions.

[Orbit173]

I checked via "getnodeinfo" and "getself", all nodes in this circuit use version 0.5.13.
It would be nice to be able to manually specify a higher priority, This will evenly distribute the load on the nodes with a large number of clients.

[majestrate]

there is currently a way to add priority to outbound peers (scheme://host:port?priority=N given N > 0 ). not sure if that'll help in this case

[Orbit173]

there is currently a way to add priority to outbound peers (scheme://host:port?priority=N given N > 0 ). not sure if that'll help in this case

I didn`t notice any effect from the change "?priority=100"