Date: Sat, 8 Jul 2017 23:32:30 +0200 From: Sydney Meyer <meyer.sydney@googlemail.com> To: freebsd-stable@freebsd.org Subject: Re: VirtualBox outbound networking Message-ID: <41167554-4C4D-4146-894F-098A41ED2098@googlemail.com> In-Reply-To: <D05CF85D-1983-4381-8829-6411778D5D16@googlemail.com> References: <D05CF85D-1983-4381-8829-6411778D5D16@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
That is, e.g. in "NAT" mode VirtualBox' own DHCP server hands out = addresses to guest, which are in turn able to ping the host but can't = get outside their own networks. I'm sorry for not mentioning this in the first post. > On 8. Jul 2017, at 20:46, Sydney Meyer <meyer.sydney@googlemail.com> = wrote: >=20 > Hello List, >=20 > i have trouble getting any form of outbound networking, i.e. "nat" or = "bridged" with the e1000 guest interfaces, to work with VirtualBox on = 11.1 BETAs and RCs. I have recompiled the virtualbox-ose port from head = with its virtualbox-ose-kmod dependency from hand but without any luck. >=20 > Am i missing something here in context of port-provided kernel modules = not being compatible with the non-release kernels or something? >=20 > Sydney
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41167554-4C4D-4146-894F-098A41ED2098>