Route metrics

[grzegorz-gutowski]

Hello,
It seems that openvpn3 silently discards metric specification on route commands:
--route network/IP [netmask] [gateway] [metric]
and creates all routes with default metric.
I'm using metric in my pushed routes and openvpn2 linux clients handle metric specification correctly.
Should I stop relying on this behavior?

[grzegorz-gutowski]

There is a hint in the source code that suggests that somebody is aware of the issue.
My question is: is it decided to stop supporting metrics on routes, or it may be implemented in the future? In other words, would you accept patches that add this functionality?

[dsommers]

This is clearly a missing feature. I'm working my way through this code, as part of #171. The whole "network configuration service" (openvpn3-service-netcfg) is being ported to a new D-Bus implementation. Once that is done, we can look into how to improve route metric handling.

The current v22_dev work in progress is already quite large and intrusive, so I'll postpone this for a following release.