Hi,
apologies for the huge delay. Have you solved this issue? To debug this
kind of problems it would be best to run "ip route" in the frontend,
hypervisor and virtual machine. If you can send those outputs to the
mailing list we will probably be able to help you out.
Cheers,
Jaime
On Sat, Dec 21, 2013 at 3:56 PM, Br4ve wrote:
> Hi,
> I got some issues with my Opennebula installation I think. First of all,
> I'm running Opennebula 4.4 and I got 2 machines ( 1 FrontEnd and 1 Node).
> These machines have 2 network interfaces (a direct crossover connection
> between them and an interface connected to the network and internet). Via
> Sunstone Marketplace I created a ttylinux vm, which worked fine so far. I
> am able to connect to the VM via VNC but not through SSH. Using VNC, I
> noticed I couldn't even ping the VM from the Frontend or the node, neither
> ping from the VM to the machines. Because of that I assumed the problem to
> be in the bridge. Then I pinged another IP(XXX.XXX.XXX.190) and suddenly it
> was succesful. After some testing via traceroute I found out that this IP
> has to be a router, because if I traceroute from the node with the frontend
> IP, it connects to exactly that IP(190) first and then it goes on to the
> specified Frontend-IP. Having this in mind, I am kind of confused now,
> because the bridge seems to work then? I'm not a networking specialist at
> all, but it seems to me as if there was a DNS or a routing problem? Any
> ideas how to fix that?
>
> Best regards
>
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
--
Jaime Melis
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | jme...@opennebula.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
