I'd almost consider this a configuration issue instead of a bug.
I wonder would a static host route to your vpn target fix the issue.
Like:
ip route add <open-vpn-server> dev <your-non-vpn-main-dev> scope host
I agree that if that would be the solution that openvpn could have an option to "exclude my own connection". Maybe it has and I don't know, but for now I'd wait to see if that is a valid workaround for now and then we can still suggest that to openvpn or otherwise.
I'd almost consider this a configuration issue instead of a bug.
I wonder would a static host route to your vpn target fix the issue. vpn-main- dev> scope host
Like:
ip route add <open-vpn-server> dev <your-non-
I agree that if that would be the solution that openvpn could have an option to "exclude my own connection". Maybe it has and I don't know, but for now I'd wait to see if that is a valid workaround for now and then we can still suggest that to openvpn or otherwise.