I originally just manually added a route and selected the gateway from the dropdown. However I saw today that rancid sent me a config diff from one of my mikrotik routers that showed the route was pointing to "unknown" rather than the ovpn interface:
When I logged-in to fix this, I saw that the ovpn connection must have dropped and reconnected and my old gateway, "ovpn-awstunnel" was gone, but a new one, "ovpn-awstunnel-1" was now present. Manually selecting the gateway from IP->Routes->edit made everything right again, but it appears this interface does not persist.
Code: Select all
- add comment="push aws-connected ovpn client traffic back to aws" distance=1 dst-address=10.100.0.0/24 gateway=<ovpn-awstunnel> + add comment="push aws-connected ovpn client traffic back to aws" distance=1 dst-address=10.100.0.0/24 gateway=(unknown)
How do I work around this? The tunnel had been up for months, but I'm sure at some point it will drop and I'd rather not have to manually alter the route.