Date: Thu, 3 Aug 2017 16:11:20 -0300 From: Mario Lobo <lobo@bsd.com.br> To: Mike Clarke <jmc-freebsd2@milibyte.co.uk> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: VirtualBox bridged networking stopped working after upgrading host to 11.1 RELEASE Message-ID: <CA%2ByoEx9RzdBBH2fQPTNn8B_6giu=fHGJqzGkh=5uVBva3HdHbA@mail.gmail.com> In-Reply-To: <20170803125642.4e4133ff@curlew> References: <20170802211628.1e40814f@curlew> <20170802190734.3f95f36e@Papi> <20170803125642.4e4133ff@curlew>
next in thread | previous in thread | raw e-mail | index | archive | help
2017-08-03 8:56 GMT-03:00 Mike Clarke <jmc-freebsd2@milibyte.co.uk>: > On Wed, 2 Aug 2017 19:07:34 -0300 > Mario Lobo <lobo@bsd.com.br> wrote: > > > I recently upgraded from 11.0 to 11.1 > > > > FreeBSD Papi 11.1-STABLE FreeBSD 11.1-STABLE #0 r321652: Sat Jul 29 > > > > and immediately sfter, I recompiled vbox (5.1.26) and have no network > > issues whatsoever (bridge,NAT,whatever..) with any guest OS type. > > > > I believe you should try ports instead of packages. > > > > Maybe is a RELEASE thing? > > Thanks for the suggestion. > > It looks like the problem is related to virtualbox-ose-kmod installed > from the FreeBSD package repository not being compatible with 11.1. > > I'm running virtualbox-ose-5.1.26 and virtualbox-ose-kmod-5.1.26 on > 11.1-RELEASE. Rebuilding virtualbox-ose-kmod from ports and keeping > virtualbox-ose from packages fixed the problem. > > -- > Mike Clarke > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" > Great!! -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winfoes FREE)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2ByoEx9RzdBBH2fQPTNn8B_6giu=fHGJqzGkh=5uVBva3HdHbA>