On 03/09/2010 08:01:32 AM, Stefan Monnier wrote:
> > bring the interfaces up
> > start dhcp client (if not triggered directly from the interfaces)
> > start openvpn
>
> That is a misconfiguration in my book. The only correct
> configuration
> is when the dhcp client is triggered from the interface. After all,
> openvpn may take half an hour to get the connection and it may lose
> the
> connection at some point and reconnect to another openvpn server (via
> round-robin DNS, for example) which might require a reconfiguration
> on
> the dhcp side.
My understanding of dhcp is that the client is supposed to
automatically reconfigure on lease expiration or whenever
the link goes up and down. There's no reason to
restart a dhcp client just to connect to another dhcp
server because dhcp should also do this automatically.
I suppose it's possible that there are dhcp clients
that exit when the link goes down and must be restarted
but I don't know of any. Then again I don't have
experience with various client implementations.
But it would seem kind of odd, having to restart
the dhcp client just because somebody unplugged
an ethernet cable.
The only reason why we're talking about restarting
dhcp clients in the first place is so that they
autodetect newly created tap devices. If the
dhcp client is configured with the tap device, or once
it detects the tap device and the tap device stays
existent, all the dhcp clients I know of should just
be able to keep running and do what's needed as
links go up and down and dhcp servers come and go.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
