On Tuesday, 10 April 2018 14:59:39 BST Christoph Böhmwalder wrote: > On Tue, Apr 10, 2018 at 01:25:42PM +0200, Simon Thelen wrote: > > What does your /etc/runlevels/ look like? Is the openvpn service in one > > of the runlevels? Are either of your network interfaces in one of the > > runlevels? > > Looking at `rc-status -a`, the openvpn service and the wifi interface > are both in runlevel default (which is kind of intentional). The wired > interface is in runlevel manual (I don't use it that often, so that's > fine). > > The thing is, I want to: > * Start the wifi service at boot > * Start the openvpn service when _any_ network connection is active > > > Also check /etc/rc.conf and try setting rc_depend_strict="NO". I do wish > > there were a way to modify require/provides without having to edit the > > init scripts themselves. > > Unfortunately I can't test this anymore, but looking at the > documentation this _should_ work. > > Thanks! > > -- > Regards, > Christoph
I recall noticing a somewhat similar behaviour with the ipsec service of strongswan. In particular, it would complain that the wired interface was not up and therefore ipsec would not start until then. The wireless interface itself being up was not enough to start ipsec. I used to start it up manually from the command line. I didn't look into it back then. I wonder if it was also something to do with the configuration of the start up script of ipsec. PS. I had commented out #rc_depend_strict="YES" in /etc/rc.conf and set rc_hotplug="*", but did not experiment further with these settings at the time. -- Regards, Mick
Description: This is a digitally signed message part.