Date: Sat, 4 Jun 2016 23:28:57 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: mmacy@nextbsd.org Cc: rwestlun@gmail.com, freebsd-current@FreeBSD.org, freebsd-emulation@FreeBSD.org Subject: Re: VirtualBox network connectivity broken on recent -CURRENT Message-ID: <201606050629.u556SvjR049729@gw.catspoiler.org> In-Reply-To: <1551e5f0389.c6f4129d128923.4644303903619975278@nextbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201606050629.u556SvjR049729>