From owner-freebsd-current@freebsd.org  Fri Aug 28 23:19:43 2015
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A8A79C5C22;
 Fri, 28 Aug 2015 23:19:43 +0000 (UTC)
 (envelope-from vidwer@gmail.com)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com
 [IPv6:2a00:1450:4010:c03::230])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id CC8351C4E;
 Fri, 28 Aug 2015 23:19:42 +0000 (UTC)
 (envelope-from vidwer@gmail.com)
Received: by labnh1 with SMTP id nh1so16545282lab.3;
 Fri, 28 Aug 2015 16:19:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=fd/3u4ANOIQZzmewU6Fx5Rw7okJ5oVJduaekkuwSVeQ=;
 b=I8uD3B7dcK0uILN5VrRgVd4AvQHXkHD8PtbbXaIW5WVGSMx9EqNMNJCaQXRZE3VlNJ
 UdbxrIaYLdQaCV2oRjl1D/0v1iZmB2x5EryncLAqDurOuxzqPwvS++Ld3c9VNGaeExWr
 nB+f3A3Us3NP9QqDnjDAwlRIFDR/qu2FHchdLax9gU8vxmS6UxRKytMTw09FlLcikmAd
 x2ZQPGVSY8rimMc5NVSCCFUlpUNFf+PQiys7+gRvwVpWuJGhNoAh2uSclc3qkgrsYzAA
 8ycCxNTsRdGE7x2lSaGfOyn8urP3QVbvUeeJB9x/ByMJ6J9wtpJ89M3wqEcnIw8Ww7N1
 n4Fw==
MIME-Version: 1.0
X-Received: by 10.112.136.170 with SMTP id qb10mr6229367lbb.34.1440803980896; 
 Fri, 28 Aug 2015 16:19:40 -0700 (PDT)
Received: by 10.25.86.149 with HTTP; Fri, 28 Aug 2015 16:19:40 -0700 (PDT)
Date: Sat, 29 Aug 2015 01:19:40 +0200
Message-ID: <CAPp9OrkP8LWhDP6BnKPBeaiS5s7do=+FjVuoR8dQpMFda7-s0A@mail.gmail.com>
Subject: r287197: wlan interfaces aren't brought up at boot or u
From: Idwer Vollering <vidwer@gmail.com>
To: freebsd-wireless@freebsd.org, freebsd-current@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Sat, 29 Aug 2015 00:39:31 +0000
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Aug 2015 23:19:43 -0000

Manually running 'service netif restart' works around this.

/etc/network.subr and /etc/rc.d/netif have been updated by mergemaster
-p and mergemaster -iF

I can provide the, rather lengthy, output of 'sh -x /etc/rc.d/netif
restart' when required.

Note that I'm not subscribed to freebsd-current.

Idwer