On 03/08/2010 05:09:49 PM, Stefan Monnier wrote:
> >> I think if the user just starts the dhcp client on an interface
> >> independently from the moment the interface goes up (or down),
> this
>
> >> is simply a misconfiguration.
> > I'm not sure I understand. Are you saying that manually starting
> > a dhcp client means that the system is mis-configured because
> > it's not configured to do the right thing automatically?
>
> No, I mean if the dhcp client is started for example in the
> boot scripts.
I see the boot scripts as problematic. The boot order
that makes sense to me is:
bring the interfaces up
start dhcp client (if not triggered directly from the interfaces)
start openvpn
The problem is that if the dhcp client is started before openvpn
and openvpn is creating the tap interface then it's too late
for the dhcp client to autodetect (at least at startup).
You could start openvpn before the dhcp client, and that could be
a good solution, but it does not work if there are tun
interfaces because the interfaces won't have yet
gotten an ip address from dhcp.
Or am I missing something?
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
