Re: [one-users] VMs are not reachable over their IP

2011-11-17 Thread Jaime Melis
Hello Martin, When OpenNebula launches a (the first) VM, the vnet0 is attached to the bridge (this works flawlessly in my case). If my bridge has the IP 141.x.x.66 and the VMs get an IP , ranged from 141.x.x.67-141.x.x.80, how are the packets been routed to the VMs? Does OpenNebula (my

Re: [one-users] VMs are not reachable over their IP

2011-11-16 Thread Jaime Melis
Hi Martin, The way the default network configuration works in OpenNebula is by making the hypervisor hook the virtual network interface of a virtual machine to a pre-existent bridge (created by the administrator), which is, in turn, connected to a real physical device: +---+

Re: [one-users] VMs are not reachable over their IP

2011-11-16 Thread Martin Lauer
Hey Jaime, thanks for the explanation. Maybe the formulation of my question wasn't really good at all. I've read most of the documentation and bridging isn't a new topic for me. When OpenNebula launches a (the first) VM, the vnet0 is attached to the bridge (this works flawlessly in my case).

[one-users] VMs are not reachable over their IP

2011-11-14 Thread Martin Lauer
Hi, I've set up my machine images with contextualization and they're configured right, when looking into the machines via VNC. The leases from my public.net are also given to the machines. Shouldn't the bridge on the host(s) br0 be mapped with additional IPs (the ones from the VMs)? This is