From owner-freebsd-current@freebsd.org  Sun Jun  5 06:29:09 2016
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 27D89B69B39;
 Sun,  5 Jun 2016 06:29:09 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id F023813D8;
 Sun,  5 Jun 2016 06:29:08 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u556SvjR049729;
 Sat, 4 Jun 2016 23:29:01 -0700 (PDT)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201606050629.u556SvjR049729@gw.catspoiler.org>
Date: Sat, 4 Jun 2016 23:28:57 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: VirtualBox network connectivity broken on recent -CURRENT
To: mmacy@nextbsd.org
cc: rwestlun@gmail.com, freebsd-current@FreeBSD.org,
 freebsd-emulation@FreeBSD.org
In-Reply-To: <1551e5f0389.c6f4129d128923.4644303903619975278@nextbsd.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.22
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: Sun, 05 Jun 2016 06:29:09 -0000

On  4 Jun, Matthew Macy wrote:
> 
> 
> 
>  ---- On Sat, 04 Jun 2016 19:04:42 -0700 Randy Westlund
>  <rwestlun@gmail.com> wrote ----
>  > On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: 
>  > > It looks like something changed in -CURRENT to break network 
>  > > connectivity to VirtualBox guests.  This was last known to work
>  > > with r299139 (May 6th) and is definitely broken with r301229.
>  >  
>  > I've been having VirtualBox networking problems as well.  I can't
>  > get my VMs on the network recently, but I don't recall when it
>  > last worked. Everything looks right from the guest (the arp cache
>  > shows the VirtualBox NAT router), but tcpdump on the host shows no
>  > traffic.  I haven't had time to investigate further :/
>  > 
> 
> The odds of it being fixed will increase greatly if someone would do a
> bisect and test.

I started bisecting a bit earlier today.  So far all I know is r300184
is also broken.