Use case

First of all, I am deeply grateful to you for developing such a user-friendly tool for remote networking.
In some cases, some servers that are not very useful are used as transit servers due to their low latency. However, I actually have a server with higher bandwidth, and I prefer to use this server instead of the server with low latency. But I cannot remove the server with low latency because I need it as a backup server. So this is what I am struggling with.
If I can set priorities in derper.yaml, I believe this would be a great solution. Would this be considered?
Thank you!

Description

I would like to request support for configurable server priority in derper.yaml.

Currently, DERP clients always choose the server with the lowest latency. In some cases, this leads clients to use a low-latency but low-bandwidth server that should only serve as a backup.

By allowing administrators to assign a priority value to each DERP server, clients could prefer higher-priority servers regardless of small latency differences, while keeping lower-priority servers available as fallbacks. This would give administrators more control over routing behavior and improve reliability and performance in multi-server environments.

Contribution

• I can write the design doc for this feature
• I can contribute this feature

How can it be implemented?

No response