Date: Mon, 12 May 2014 07:50:54 -0500 From: Mark Felder <feld@FreeBSD.org> 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: <10A1433E-80EA-4AF4-BC38-B03D742E0D97@FreeBSD.org> In-Reply-To: <DA602ED0-ECBC-4A3D-8F1B-9CB80EDE12B5@FreeBSD.org> References: <DA602ED0-ECBC-4A3D-8F1B-9CB80EDE12B5@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 17, 2014, at 3:21, David Chisnall <theraven@FreeBSD.org> wrote: > Hi all, >=20 > 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. >=20 > 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? >=20 I always thought the proper solution here was pf's built-in keywords = "egress" and "ingress" interface names so you don't have to specify = interface names that may or may not exist at the time the pf rules load.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10A1433E-80EA-4AF4-BC38-B03D742E0D97>