Date: Sat, 4 Jun 2016 23:33:20 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: otacilio.neto@bsd.com.br Cc: freebsd-current@freebsd.org Subject: Re: VirtualBox network connectivity broken on recent -CURRENT Message-ID: <201606050633.u556XKCL049747@gw.catspoiler.org> In-Reply-To: <399e4cd0-aed2-a69f-6e19-ff5645b1d372@bsd.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 Jun, Otacílio wrote: > Em 04/06/2016 23:04, Randy Westlund escreveu: >> 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 :/ > > I'm running rev 301210 guest and here looks working. It doesn't appear to be a guest problem. Both recent FreeBSD 11.0-CURRENT and Debian on broken if the host is FreeBSD 11.0 HEAD >= r300184. The same FreeBSD guest works if the host is FreeBSD 10.3-STABLE r301231.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201606050633.u556XKCL049747>