Date: Tue, 14 May 2019 18:53:40 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: rcorder - wait for tap0 Message-ID: <20190514185340.0159358c@gumby.homeunix.com> In-Reply-To: <20190514182945.0ced24d4@gumby.homeunix.com> References: <dc363ae4-d331-efd0-e099-ee01b7eaddb1@nethead.se> <20190514182945.0ced24d4@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 14 May 2019 18:29:45 +0100 RW wrote: > On Tue, 14 May 2019 08:49:52 +0200 > Per olof Ljungmark wrote: > > > Despite large amounts of cofee and time I cannot grasp how to make > > this happen. > > > > What I want is > > > > Boot -> start openvpn/tap0 configured -> start named -> start jails > > > > Because the jails uses tap0 of course they cannot start before tap0 > > is up, but this is what happens in the default configuration. > > > > Surely this cannot be unique? How did you do it? > > > > Preferrably without messing with rc.d scripts that gets overwritten > > when updated. > > You need an rc script in /usr/local/etc/rc.d with something like: > > > # PROVIDE: vpnwait > # REQUIRE: openvpn > # BEFORE: <whatever string the jail rc.d script provides> now I come to think about it openvpn runs after LOGIN, so either you have to put up with the order named, openvpn, jails or rewrite the openvpn script. What I did was to allow DNS to pass directly to one well-known server so lookups could happen before openvpn started.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190514185340.0159358c>