Hey everybody!
I'm using the latest VirtualBox 3.2.6 on Ubuntu 10.04 32bit. I'm not sure when this happend, maybe within the last few days, that the bridged networking feature has stopped working. I run a Drupal webserver that requires bridged networking so this is a big problem for me.
So anyways, whenever I select bridged networking it does list eth0 and eth1, like always, (eth1 is the one I use). So when I select eth1 it selects successfully but below the dropdown box it usually lists the hardware interface that its actually (if I remember correctly) connecting to (Dell Wireless 1345 blah blah blah). But now this doesn't show up. Neither does it for eth0. So now whenever the VM web server tries to connect it times out. So now I need to know why its not working. So I searched for bridged networking and VirtualBox on google but all of the solutions were from 2008 which were too outdated. But they lead me to look at the files "/etc/network/interfaces" and "/etc/vbox/interfaces".
The /etc/network/interfaces file does not list eth1 but it lists loopback and eth0 fine.
The /etc/vbox/interfaces file is non existant, so does VirtualBox still use this? Actually the whole directory was empty.
Then I was lead to a command leaving me to think it could be an Ubuntu problem, the command was "sudo /etc/init.d/networking restart". When I run this I get this error,But I can connect to Eth1 (wireless) just fine. When I click connection information from the network app in Ubuntu it lists my current wifi connection as eth1.[sudo] password for justin:
* Reconfiguring network interfaces... Ignoring unknown interface eth1=eth1.
[ OK ]
I'm so confused with all of this! Is this an Ubuntu or VirtualBox problem?
I tried reinstalling virtualbox with no help and also reconfiguring the kernel module but that didn't work.
So does anybody have any troubleshooting tips or solutions that could help me?
Thank you.
Bookmarks