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.
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) or a
domain name.
Using the domain name together with a dyndns service works sometimes,
but fails when the interface has just been brought up, and the dyndns
update hasn't yet propagated through the DNS system.
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, which in some cases involves messing around with the way
your distro usually does things, something I prefer to avoid.
Fede
