Page 1 of 1
Bridged networking problem
Posted: 14. Jul 2009, 01:07
by DLag
Ubuntu 9.04 Host VirtualBox 3.0.2
Host have 2 dedicated IPs on eth0:
111.111.111.2
111.111.111.3
Router in the net:
111.111.111.1
#cat /etc/network/interfaces
# device: eth0
auto eth0
iface eth0 inet static
address 111.111.111.2
broadcast 188.40.32.255
netmask 255.255.255.0
gateway 111.111.111.1
I need to attach 111.111.111.3 to the guest.
I run the following command:
VBoxManage modifyvm VM --ostype RedHat_64 --acpi on --memory 1024 --vrdp on --vrdpport 9978 --vrdpauthtype null ...... --nic1 bridged --cableconnected1 on --bridgeadapter1 eth0
This does not work, the guest is not even seen the host.
What am I doing wrong?
Re: Bridged networking problem
Posted: 14. Jul 2009, 03:26
by Perryg
Maybe this will help. Look at the broadcast address
Re: Bridged networking problem
Posted: 14. Jul 2009, 10:13
by DLag
Ok. I have edited the post.
Re: Bridged networking problem
Posted: 14. Jul 2009, 12:01
by Sasquatch
So it still doesn't work? What if you put only the IP and netmask for the config, can you access the other machines or not? Just a ping to them will suffice. When that's working, add the gateway and try to access an external IP, like that of Google. You can add DNS too of course

. You don't always need the broadcast address, it's done automatically.
Re: Bridged networking problem
Posted: 15. Jul 2009, 23:52
by DLag
The problem still remains.
At home Ubuntu it works fine.
There may be a problem because the interfaces are created from /etc/network/interfaces rather than NetworkManager?
Or maybe the problem because the server is Ubuntu server edition and the Headless mode?
Re: Bridged networking problem
Posted: 15. Jul 2009, 23:59
by Sasquatch
Still not clear what your situation is and the exact problem.
Re: Bridged networking problem
Posted: 16. Jul 2009, 00:02
by DLag
Sasquatch wrote:Still not clear what your situation is and the exact problem.
Sasquatch, I can give you access to the server if this helps.
Re: Bridged networking problem
Posted: 16. Jul 2009, 11:07
by Sasquatch
You say that it works just fine at home, so I don't know what your problem is now. Do you use the same virtual hard disk image at work too, and is it giving problems there? If so, you have to make sure that in the config of both VMs, the MAC address for the NICs is the same. Linux creates new interface names when the MAC address changes. You can see that by running ifconfig -a in a terminal. The file /etc/udev/rules.d/70-persistent-net.rules contains these names too. Clearing the file, or removing it will generate a new list with the current MAC addresses as interfaces on reboot.