virtualbox.org

I have a fedora 18 guest and a Ubuntu 12.10 host with a single physical eth0 interface configuration. I need to be able to forward requests to my guest machine, which acts as a server(jenkins,nexus,tomcat). I've read an article on bridge networking and setup the connection (bridged adapter, eth0). It didn't help - resulted in a network connection error on my guest.

For this to work, VirtualBox needs a device driver on your host system.

What does it actually mean? Does it say that I need additional workaround complementing:

To enable bridged networking, all you need to do is to open the Settings dialog of a virtual machine, go to the "Network" page and select "Bridged network" in the drop down list for the "Attached to" field. Finally, select desired host interface from the list at the bottom of the page, which contains the physical network interfaces of your systems.

I would appreciate some elucidation. At this moment my guest has two adapters: nat and bridged adapter(eth0).

Guest's ifconfig:

[guest@localhost ~]$ ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 8 bytes 616 (616.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 616 (616.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

p2p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.0.2.15 netmask 255.255.255.0 broadcast 10.0.2.255
inet6 fe80::a00feb8:fed7 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:b8:fe:d7 txqueuelen 1000 (Ethernet)
RX packets 32 bytes 3877 (3.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 63 bytes 7349 (7.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

p7p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a00fe59:82b1 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:59:82:b1 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29 bytes 4750 (4.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Host's ifconfig:

midnight@midnight-System-Product-Name:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 30:85:a9:93:9a:e7
inet addr:10.64.192.114 Bcast:10.64.255.255 Mask:255.255.0.0
inet6 addr: fe80:a9ff:fe93:9ae7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:660189 errors:0 dropped:0 overruns:0 frame:0
TX packets:470342 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:713860139 (713.8 MB) TX bytes:237669744 (237.6 MB)
Interrupt:43 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5419 errors:0 dropped:0 overruns:0 frame:0
TX packets:5419 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:527268 (527.2 KB) TX bytes:527268 (527.2 KB)

Please provide a log file, for details read Minimum information needed for assistance.

midnight wrote:
For this [bridged networking] to work, VirtualBox needs a device driver on your host system.
What does it actually mean?

It means what it says. Bridged network uses a filter driver installed on your host, as part of the driver stack for the network card. This filter driver intercepts packets with MAC addresses belonging to guests, and redirects them to the simulated NICs in those guests. Without the filter driver installed on the host, bridged networking will not work.

I don't use a Linux host, but on Windows hosts, VirtualBox networking drivers is an installer option. It can be upset if the user doesn't have permissions to install drivers.

Also note that Ubuntu repo versions of VirtualBox are not supported here.

Thanks for the reply. I'm using 4.2.10 version, which I downloaded from the official downloads resource. So, can you give me any further directions?

I figured out that

p7p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::a00fe59:82b1 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:59:82:b1 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29 bytes 4750 (4.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

has something to do with the bridged adapter. How do I troubleshoot and eventually connect/forward calls to my guest server?

Bridging is like having a completely separate computer on your network.
The Guest is only hijacking the physical interface but has nothing to do with the host OS itself.

If any configuration needs to take place, it's on the guest. Simply see your guest as directly connected to the same hardware as the host, and the same steps has to be taken that you took to make the host work on your LAN.

virtualbox.org

Network setup question

Network setup question

Re: Network setup question

Re: Network setup question

Re: Network setup question