FreeBSD on Virtualbox: No network access
weihang at vt.edu
Sat Dec 4 22:22:05 UTC 2010
Thank you so much for your advices. I am using NAT mode now. Just as you said, there is no need to configure DHCP in /etc/rc.conf. I just choose the Intel PRO/1000 T Server as my virtual network interface. It works well.
Thank you very much. : )
On Dec 4, 2010, at 8:32 AM, Matthew Seaman wrote:
> On 03/12/2010 09:25, Timm Wimmers wrote:
>> 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).
> Hmmm.... I don't know about bridge mode being appropriate in "most"
> cases. NAT and bridge modes are useful in different circumstances
> * NAT mode means that your VMs are not exposed to incoming
> connections on the net.
> * Bridge mode means that the VMs can run network services
> for users on other machines.
> Which one of those you prefer depends very much on how you're using the
> VMs. Eg. for a dev playground and for local testing, NAT looks like a
> better idea.
> Now, I run VirtualBox on my Mac with FreeBSD (inter alia) as a guest OS.
> Your setup may differ, but I find NAT mode to be the best choice.
> In addition to the considerations above, I also see:
> * In NAT mode, the FreeBSD guest is insulated from how the Mac
> connects to the network. Switching between wired or wireless
> networking, or even using a 3G dongle "just works" as far as
> the FreeBSD guest is concerned.
> * Similarly if the MAC gets a new IP when switching between
> different networks and DHCP servers, the guest OS just doesn't
> You don't need to worry about configuring routing and so forth in the
> guests: just use DHCP for the i/f, and it all works automagically.
> Actually, I generally enable two network interfaces for unixoid guests
> (ie. capable of running sshd) -- set to NAT and vboxnet0. This means I
> can ssh into local guest OSes from a Terminal.app session, which I find
> more convenient than logging in via the console. Again, it's all
> configured effortlessly with DHCP.
> My only complaint is that IPv6 doesn't work in these modes, but I can
> live with that.
> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
> Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
> JID: matthew at infracaninophile.co.uk Kent, CT11 9PW
More information about the freebsd-questions