Date: Thu, 27 Jul 2017 20:19:30 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-stable@FreeBSD.org Subject: [Bug 221050] emulators/virtualbox-ose: Bridged network doesn't work (11.1-RELEASE) Message-ID: <bug-221050-8075-xJaqlgKK7i@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221050-8075@https.bugs.freebsd.org/bugzilla/> References: <bug-221050-8075@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221050 --- Comment #8 from steinex@nognu.de --- Ok, I can confirm that bridged networking works again when virtualbox-ose = is build from source when it's complete dependency chain is also built from ports. It makes sense to me that virtualbox needs to be compiled against the new kernel after upgrading, I didn't spot the gcc5 issue, thanks for that. However, I'm not the original bug submitter and I can relate to the confusi= on as of why a package stops working after upgrade to a new minor-release. I s= ee a chicken-and-egg problem between quarterlies (and most probably even latest) packages that provide out-of-tree modules and a new -RELEASE. I have no stake in here what to do, having a virtualbox-ose package sure is nice, but having none at all may be less confusing. tl;dr: bridged networking in virtualbox from ports (2017Q3) with 11.1 is totally fine, if you compile virtualbox with it's complete dependency chain from ports and not use packages. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221050-8075-xJaqlgKK7i>