Date: Sat, 19 Apr 2014 19:36:59 -0600 From: Warner Losh <imp@bsdimp.com> To: David Chisnall <theraven@FreeBSD.org> Cc: "FreeBSD-CURRENT@freebsd.org Current" <freebsd-current@freebsd.org> Subject: Re: Ordering for network-sensitive rc scripts Message-ID: <21178648-68BE-41D7-8D6D-246A8CE167AB@gmail.com> In-Reply-To: <DA602ED0-ECBC-4A3D-8F1B-9CB80EDE12B5@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Apr 17, 2014, at 2:21 AM, David Chisnall <theraven@FreeBSD.org> wrote: > For a little while, I've had an issue with the machine that sits on the edge of my network deciding to start avahi as soon as a network is available, meaning that it then runs mDNS advertisements on the external interface and not the wireless one, requiring a manual restart once the machine boots. I'm now seeing something similar with pf - it manages to start before the external interface comes up and so silently ignores all of the rules for routing packets off the network. > > Do we have a mechanism for stating that certain services should not be started until ALL of the interfaces are up, rather than just the first one? Or even of restarting them when a new network appears? devd network events will allow you to do this on a per-network basis. The script that you run can then determine if the relevant criteria are in place and then do something... Warnerhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21178648-68BE-41D7-8D6D-246A8CE167AB>