VirtualBox

[Dom Latter]

Ian Spray wrote:

> 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've read the manual about eleventeen times and about eleventeen
hundred forum posts and this is the first time someone's said *how*
it works, not just "it works".

> 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.

Right.  I believe I've tried all this.  I certainly gave up with
the aliased eth0:1 a while back.  I'll try again, now I have a clearer
picture of things.  You really wouldn't believe how your short post
here has made such a huge difference!

I may try a different virtual network card (and why not?).

Later I hope to be able to try a 64 bit guest OS.

> 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.

Yes.  But it may have to happen that way.

> 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.

Certainly not wifi - this is data centre stuff.  And it's all IPv4.

(Hey, I thought we all moved to IPv6 in about 2001, didn't we?)

thanks again.