VirtualBox

[Ian Spray]

On Fri, Jun 12, 2009 at 05:26:35PM +0200, Dom Latter wrote:
> 
> NATed worked fine, but I want to run web and mail servers on it, so
> I think I need "bridged".  Directly on the LAN, as it were.
> 
Yup - most of my work is done in bridged mode.

> What I don't get is what IP address the host OS is supposed to end up
> with, and where it gets it from.
> 
> Any pointers?
> 
I've never tried to specify an aliased interface in bridge mode: I set 
up the VM as a bridge, choose an Intel Pro network card (they work best 
for the O/S I try to run) and let it go.  The VB system will create 
whatever it needs on the host without me asking it to, and then as the 
VM image starts up it requests a DHCP address like any other system on 
my LAN.

I would suggest you unalias eth0 (so loose eth0:1 on the host) first, 
set VB up for bridge, boot the VM image and then either do a DHCP in the 
VM, or set up the static IP inside the VM just as if you'd installed the 
system on a new machine.  You shouldn't need to do anything at all on 
the host.

> [snip NAT fallback]
> 
If it involved NAT and port bouncing, I'll stick my fingers in my ears 
and shout "lalalala".  The last time I had to fall back o something like 
this, Virtualisation wasn't around, so hopefully this can be avoided.

You are just using plain old IPv4 here, aren't you ?  There are caveats 
in the VB manual about wifi cards and non-IPv4 stuff.

HTH,
-- 
Ian Spray
GPG Fingerprint: D170 35A3 C858 6E85 9B5B  1557 4CD5 6F6F E176 2D0A