Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 8 Aug 2009 18:51:13 +0200 (CEST)
From:      Juergen Lock <nox@jelal.kn-bremen.de>
To:        matheus@eternamente.info
Cc:        emulation@freebsd.org, Jeremy Messenger <mezz7@cox.net>
Subject:   Re: VirtualBox NAT network works or not?
Message-ID:  <200908081651.n78GpDjV004629@triton8.kn-bremen.de>
In-Reply-To: <f01e4302942811415e4533fd29d7818e.squirrel@10.1.1.10>
References:  <op.uxrdsge29aq2h7@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <f01e4302942811415e4533fd29d7818e.squirrel@10.1.1.10> you write:
>On Tue, July 28, 2009 00:39, Jeremy Messenger wrote:
>> Hello,
>>
>> I have installed VirtualBox and very surpised about that it's very fast.
>> Very nice!
>>
>> But I have a problem with NAT network and uses DHCP in guest. It does not
>> work. The host is yesterday -CURRENT and very latest installed ports with
>> libtool 2.2. I don't know how I can debug it. I have decided to install
>> VirtualBox in Windows 7 and I have setup very same exactly how I do with
>> guest of FreeBSD 6.4. It works perfect. The only difference is that
>> VirtualBox version is 3.x in Windows and 2.x in -CURRENT. It is either bug
>> or not ready? I have tried to disable VT-x and it makes no difference. I
>> have tried all network adapter and no difference.
>
I've had nat mode problems too (guests randomly failing to dhcp on the
first attempt, have to manually run `dhclient eth0' a second time
in the guest), and the official vbox changelog,
	http://www.virtualbox.org/wiki/Changelog
mentions
	NAT: fixed network communication corruptions (bugs #4499, #4540, #4591, #4604) 
for their 3.0.4 release too, so maybe we just need to wait for these
fixes to reach the FreeBSD port...

>I've been using Vbox 3 in FreeBSD for a bit more of a week now, and it is
>doing what I want it to.
>
>the svn
>
>svn co
>http://svn.bluelife.at/projects/packages/blueports/emulators/virtualbox
>
>I can use nat, but still trying to figure out how to reach the vm using
>network. if anyone has any leads. so far, the best thing I think is to
>make a reverse tunnel using ssh.
>
 vbox' nat mode, like qemu's, can map individual guest ports to
ones on the host (port forwarding), see here for details:
	http://www.virtualbox.org/manual/UserManual.html#networking-nat

>matheus
>
>ps: I can't use my amd64 vm's if not from 7.2-STABLE. -CURRENT is no good
>in here, tested three diff machines by now.

 I have problems parsing this, :) you mean amd64 guests stopped
working on -current?  Guess I should test that here...

 HTH,
	Juergen



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200908081651.n78GpDjV004629>