On 03/09/2010 12:47:36 AM, Peter Stuge wrote:
> Karl O. Pinc wrote:
> > 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
>
> At least some distributions work more like this:
>
> foreach interface:
> set link up
> possibly start openvpn
> address add
Ok. So this then relies on openVPN retries to get the connection
open, because when openvpn starts it's not got addresses
in place to reach the other endpoint. The only downside
is that the startup is not really synchronous so that if
later portions of the boot process are relying on having
the VPN available they'd better be able to retry too.
In this case it should "just work" on those distros, at least so
long as the "address add" part is configured to use dhcp. Yes?
Anyone know if it does work?
Which distros work like that? I'm most familiar with
Debian and RedHat, although I've not looked at openvpn
on RedHat in a while. I seem to recall on these
that the sysV init stuff starts openvpn last.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
