id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc 1481,Please support `inactive` in ``,András Korn,,"I have several openvpn servers, and a well defined order of preference; I only want to connect to the 2nd or 3rd server if the 1st one is not available. If I don't specify `remote-random`, openvpn will try them in the correct order; however, if the first server is not reachable, it will get stuck on the first lower-preference server that ''is'' available. Currently there is no mechanism that would cause openvpn to periodically retry connecting to the first server. I imagine implementing a mechanism that keeps trying to connect to the first server while retaining the active connection to the 2nd one would be relatively difficult; however, allowing users to specify `inactive` in lower-preference `` blocks would be a poor man's way of doing this. I realize I can include `inactive` in the global configuration, but I would like to avoid disconnecting from the primary server if possible; I only want to disconnect from the secondaries. I can't implement this on the server side, because I only actually have one server instance that has several public IPs (which are on different uplinks). The next best solution would be to run a script from cron that checks where the running openvpn client is connected; if it's not the preferred server IP, then also checks whether the preferred server is available; and if yes, restarts the client. This feels even kludgier than abusing `inactive`.",Feature Wish,new,minor,,Configuration,,"Not set (select this one, unless your'e a OpenVPN developer)",,,