Bridged networks in VirtualBox only works one way.

enine · 07-31-2010, 09:12 PM

I've setup a virtual guest on VirtualBox using a bridged adapter and can not reach the guest from the rest of my network. Its been a while but I thought this used to work. So example

test workstation 192.168.1.100
host server 192.168.1.108
virtual guest 192.168.1.109

the workstation on .100 can't ping the guest on .109 but can the server on .108. I thought I've set this up before and it worked fine, would think the bridged adapter should pass through both ways.

alroger · 08-02-2010, 01:43 PM

It should work without any trouble. Are you sure you using BRIDGE mode, and not NAT or user mode?
Is there only one network adapter on the host?
Could it be a firewall blocking stuff from the LAN?

scheidel21 · 08-03-2010, 08:53 AM

Go with what alroger said, I would hazard you are using host only, or something other than bridged by accident. If that is not the case t is very likely the guest is running some sort of firewall.

enine · 08-03-2010, 09:23 PM

I double and triple checked, guest is set for bridged. Guest can get to the internet, ping other systems on the network but not the host. Other systems on the network can't ping the guest, no firewall, its just a simple install of slackware 13.1.
Only think I could think, is virtualbox particular about what nic you bridge the guests to? I'm using the hosts wireless for now until I run a cable to my closet.

krasl · 08-03-2010, 09:26 PM

If the guest is running a recent Linux distro with iptables, try turning iptables off then testing. (not a good idea in production environments)

service iptables stop on Fedora-based distros

What about firewall on host pc? does it have one?

enine · 08-03-2010, 09:58 PM

The host is also slackware 13.1, iptables or any other firewall doesn't run by default, I'd have to turn any on myself.

alroger · 08-04-2010, 12:01 AM

Quote:

Originally Posted by enine

I double and triple checked, guest is set for bridged. Guest can get to the internet, ping other systems on the network but not the host. Other systems on the network can't ping the guest, no firewall, its just a simple install of slackware 13.1.
Only think I could think, is virtualbox particular about what nic you bridge the guests to? I'm using the hosts wireless for now until I run a cable to my closet.

Ooooops, I think that's your problem. Very few wireless adapters will work right with BRIDGE. Try the cable before anything else.

krasl · 08-04-2010, 07:46 AM

Sorry; didn't notice that you were working with a wireless adapter.

Here's a quote from http://forums.virtualbox.org/viewtopic.php?t=1787
"Wireless adapters don't always bridge properly in Windows. They will report connected to the bridge (so it reports bridged) but does not pass on the IP address at all..."

Good luck!

enine · 08-04-2010, 07:57 PM

Quote:

Originally Posted by krasl

Sorry; didn't notice that you were working with a wireless adapter.

Here's a quote from http://forums.virtualbox.org/viewtopic.php?t=1787
"Wireless adapters don't always bridge properly in Windows. They will report connected to the bridge (so it reports bridged) but does not pass on the IP address at all..."

Good luck!

I'm not running Windows.

alroger · 08-05-2010, 01:56 AM

enine, forget bridging on wireless adapters.
A quote from https://help.ubuntu.com/community/KVM/Networking

Warning: Network bridging will not work when the physical network device (eg eth1, ath0) used for bridging is a wireless device (eg ipw3945), as most wireless device drivers do not support bridging!

And the tech behind it:
http://www.linuxfoundation.org/colla...reless_card.21

enine · 08-05-2010, 06:21 AM

OK, thanks, that makes more sense. I'll have to pick up a roll or cable next week and climb in the attic.