Federico Heinz wrote: > On 12/03/2011, Peter Stuge wrote: > > Federico Heinz wrote: > > > What I'm trying to solve here is a much simpler (and, in my case, > > > frequent) use case: I'm starting several instances of OpenVPN, > > > and I need each of them to listen on specific interfaces, but > > > their dyndns addresses may not be up-to date yet, so I can > > > specify neither an IP nor a domain name in the "local" directive. > > Why can't you specify the IP address? > > Because I don't know it at configuration time.
You said that you already have a solution in place for dealing with interface reconfiguration. Simply use the same mechanism for initial configuration. > The "local" directive will currently accept either a fixed IP > address (which I don't know, because it will be assigned in the > future, and may change every time that particular interface is > brought up) Yes. Third time, tap the configuration information from the authoritative source. Until OpenVPN has multilisten there's no point in OpenVPN trying to do this, because it will only do a poor job. > or a domain name. The domain name is irrelevant. Go closer to the authoritative source, not further away. > Alon mentioned earlier that this could be dealt with at run-time by > modifying the startup scripts to determine the IP address and > specify it through the command-line, but it's an unnecessarily > complex solution, I actually think this is an extremely simple solution. > which in some cases involves messing around with the way > your distro usually does things, Why would it? //Peter
