Page 1 of 1

Host interface networking on Fedora10

Posted: 19. Jan 2009, 14:58
by wzzrd_
Hi!

I'm new at VB, but not a virtualization in general: I've been using VMware ESX, Workstation and KVM for quite some time, so I'm not a complete newbie.

Anyway, I have a VB 2.1.0 install on my laptop running Fedora 10 x86_64 and I'm not able to get host interface networking to work.

I can select the eth0 interface when configuring networking on a virtual machine, but when I put the host interface on the my laptop in 192.168.1.0/24 and do the same with the interface on the virtual machine, not connection is possible: no route to host.

I have turned off both firewalling and SElinux, but that's not where the problem lies. I know I can achieve connections when doing NAT and then setting up port forwarding for ssh, but that is not a good solution. I want to do some web experiments in a VM, so I need access to all 65k ports on the VM ;-)

When I RTFM, I see I need only select the host interface when configuring networking in a VM and all should be done automatically by VB. What am I missing?

(And if this is an extremely n00bish question: sorry :) )

Posted: 20. Jan 2009, 17:17
by wzzrd_
Solved, well, cause known at least.

I had expected the host interface networking option to provide some switching "inside" virtualbox and / or *before* traffic would be spit out of the physical interface. The problem was the fact that I had the physical interface configured, but not connected. I had expected traffic to be switched between VM's and the physical interface internally, but it seems traffic is routed outside of my box, on the physical network.

So, when I connect the box to the network all works fine.

Does anyone know of a way to be able to have networking between the host machine and the guest machines similar to the VMware Workstation "Host-only networking" option?

Posted: 20. Jan 2009, 22:08
by Sasquatch
Install UML-utilities and create a TAP adapter. Set that to HIF on the Guest, configure both ends with some IP (like 172.16.0.0, 255.255.0.0) and you're good to go.