Date: Fri, 03 Dec 2010 10:25:54 +0100 From: Timm Wimmers <timm@ticore.de> To: Weihang Wang <weihang@vt.edu> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD on Virtualbox: No network access Message-ID: <1291368354.2905.19.camel@SHR-42-002> In-Reply-To: <EA5E99C7-AA29-4D8B-BBAD-F1463C7B1CDA@vt.edu> References: <BD9E30A7-919D-4145-A6B6-A9A086B6D7C2@vt.edu> <4CF87854.1030103@mgwigglesworth.net> <EA5E99C7-AA29-4D8B-BBAD-F1463C7B1CDA@vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Freitag, den 03.12.2010, 00:33 -0500 schrieb Weihang Wang: > Hi Martes, > > I have tried the first two interfaces which are said to be supported by FreeBSD, they do not work. Surprisingly, now I choose the option "Intel PRO/1000 T Server" and in NAT mode, it works now!!!! > Thank you so much, you do me a great favor!! Hope this also works for Chris! In most cases it is better to use bridge mode. In NAT mode your VM get a private subnet and other devices in your network can't find your VM, because the VM is behind (or encapsulated in) your HOST (as like as your HOST is behind your router to the internet). This can work if you define routes, but bridging is mostly easier. In Bridge mode your VM acts like any other machine in your network and will get an IP-Adress from your DHCP server (if you use DHCP). -- Timm [1] HSOT = your Ubuntu Workstation
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1291368354.2905.19.camel>