Dear,

consider this situation:

[Machine HQ] ------------------------------- [Remote location]
bridge over wifi ========================= bridge over wifi
eth0 10.111.111.1 eth5 10.111.111.10
|| ||
openvpn server ============================== openvpn client
tun0 172.19.1.1 tun0 172.19.1.250

the openvpn does not push any routes so all traffic is currently moving over the bridged wireless connection.
I change the ccd from the client on the server to include some routes to take over the bridged connection when it fails. then I kill the openvpn client's connection.

The client reconnects and now gets the routes from it's ccd on the server which actually make the same networks available but over the openvpn.

The weird part: although both routes have a metric of 0, the newer route from the openvpn connection gets listed first in the routing table so the failover works but I don't see why it gets priority over the existing metric 0 route over the bridge...

...
10.111.111.0/24 via 172.23.1.1 dev tun0
10.111.111.0/24 dev eth0 proto kernel scope link src 10.111.111.1
...

any thoughts?

thanks.