[Pkg-virtualbox-devel] Bug#502574: Bug#502574: virtualbox-ose 1.6.6-dfsg-2: Host Interface Network not working.

[Joseph Rawson]

On Friday 17 October 2008 18:55:30 Patrick Yuen wrote:
> Package: virtualbox-ose
> Version: 1.6.6-dfsg-2
> Severity: important
>
> Hi,
>
> I am trying to connect Host Interface Network following documents on the
> /usr/share/doc/virtualbox-ose/
>
> 1 ... Both README.Debian.gz and README.Debian.html have the same content
> which does not require bridge-utils package and did not work.
>
> === Command ===
> VBoxAddIF vbox0 userA br0
>
> === Result /etc/vbox/interface ===
> vbox0 userA br0
>
> === Modify /etc/network/interface ===
>
> iface vbox0 inet static
> 	address 192.168.3.1
> 	netmask 255.255.255.0
> 	virtualbox-user userA
>
> - - - -
>
> 2 ... wiki.html is basically a copy of
> http://wiki.debian.org/VirtualBoxwhich requires bridge-utils package
> and also did not work.
>
> === Command ===
> aptitude install bridge-utils
>
> === Modify /etc/network/interface ===
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
> # An entry for eth0 is no longer needed
> #auto eth0
> #iface eth0 inet dhcp
> # Create the bridge (with the regular IP address of the host)
> auto br0
> iface br0 inet dhcp
>         bridge_ports eth0
>         bridge_fd 2.5
>
> === Command ===
> /etc/init.d/networking restart
>
> === Command ===
> VBoxAddIF vbox0 userA br0
>
> === Result /etc/vbox/interface ===
> vbox0 userA br0
>
> === Command ===
> /etc/init.d/virtualbox-ose restart
>
> - - - -
>
> And i did change the setting of virtualbox attached to = Host Interface and
> Interface Name = vbox0 in both cases.
>
> Is this a documenation bug or software bug ?
>
> Thanks.
I'm not sure if this letter will help much, because I don't know how you want 
your VM's to be networked.  If you plan to only use a single VM, using the 
static method may be better.

In my experience, I found that using the static vbox interfaces to be a little 
bit too cumbersome.  Instead, I've been using dynamic vbox tap interfaces 
that are brought up/down on demand.  I've found this to be much easier.

The instructions for doing this are just below the instructions for the static 
interfaces on http://wiki.debian.org/VirtualBox .  When using the dynamic 
method, each machine must have entries set in "Setup Application" 
and "Terminate Application" in the network configuration section of the VM.  
For this, I use a script similar to the one on the wiki page.  Also, on the 
wiki page there is a snippet that you can place in your /etc/sudoers file 
that will help when enabling/disabling the dynamic interfaces.

The instructions for setting up dynamic interfaces on the wiki page will 
bridge the VM's to your local network.  If you don't want the VM's to be 
attached to the local network, you will have to create a tap interface and 
bridge that one instead.  There are instructions on how to do that here  

http://wiki.debian.org/VirtualNetworking

If you do this, you don't really have to create the user-mode-linux machine as 
it's described, or run the uml_switch, but you will probably need to run both 
dns and dchp from the host.

I hope this helps. :)

-- 
Thanks:
Joseph Rawson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-virtualbox-devel/attachments/20081018/382e5847/attachment.pgp