From owner-freebsd-current@FreeBSD.ORG Thu Apr 17 08:21:55 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 964AE44F for ; Thu, 17 Apr 2014 08:21:55 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 64DE21A1A for ; Thu, 17 Apr 2014 08:21:54 +0000 (UTC) Received: from [192.168.0.100] (cpc14-cmbg15-2-0-cust307.5-4.cable.virginm.net [82.26.1.52]) (authenticated bits=0) by theravensnest.org (8.14.7/8.14.7) with ESMTP id s3H8Leci081055 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 17 Apr 2014 08:21:47 GMT (envelope-from theraven@FreeBSD.org) From: David Chisnall Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Ordering for network-sensitive rc scripts Message-Id: Date: Thu, 17 Apr 2014 09:21:34 +0100 To: "FreeBSD-CURRENT@freebsd.org Current" Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2014 08:21:55 -0000 Hi all, 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? David