Date: Sat, 04 Jun 2016 19:23:11 -0700 From: Matthew Macy <mmacy@nextbsd.org> To: "Randy Westlund" <rwestlun@gmail.com> Cc: "Don Lewis" <truckman@FreeBSD.org>, "<freebsd-current@FreeBSD.org>" <freebsd-current@FreeBSD.org>, "<freebsd-emulation@FreeBSD.org>" <freebsd-emulation@FreeBSD.org> Subject: Re: VirtualBox network connectivity broken on recent -CURRENT Message-ID: <1551e5f0389.c6f4129d128923.4644303903619975278@nextbsd.org> In-Reply-To: <20160605020442.GN80638@gmail.com> References: <201606040011.u540BODD045000@gw.catspoiler.org> <20160605020442.GN80638@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
---- 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. -M
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1551e5f0389.c6f4129d128923.4644303903619975278>