I’m happy with the general Openvpn improvements in ROS, still it has a limitation that makes a scenario with multiple mobile clients (one of the main uses for Openvpn) hard to manage: I cannot push openvpn parameters (mostly routes) to the clients from a Mikrotik server.
This makes it hard to manage confg changes because if for example I add a network on the server side, and want to teach the clients about that new network that has to be routed through the vpn, I have to edit every client config file with a new “route x.x.x.x” config line.
With the pushable config lines, it’s just a matter of adding a “push route x.x.x.x” to the server config, and all the clients will get the new route.
Thanks Mikrotik for adding the push route configuration, I’m now using it.
Next step, please consider adding a generic push configuration option.
In my opinion it should be quite easy to set up a generic text field where I can write all of the options I want to push to the clients, because the options are indeed just text strings.
Using openvpn server on Linux I can set multiple options in the config file, like this:
and all that this does is that the server sends the strings inside the quotation marks as concatenated strings to the client, separated by commas, like this:
In ROS, I can only set routes and DNS, and they get pushed, but there is no way to just set arbitrary strings to get pushed to the client.
Being able to push everything I want to the clients is a very nice feature because you can easily manage config changes to the clients without having to edit every single client configuration, which is really time-saving when you have more than 2 or 3 clients.
