[ubuntu-cloud] Cannot ping running instance

[Indra Suryatama]

I ve been experienced it,

Try to give your permission at port 22, 3389  for TCP and ICMP

Ex:

$ euca-authorize default -P tcp -p 22 -s 0.0.0.0/0
$ euca-authorize default -P tcp -p 3389 -s 0.0.0.0/0

$ euca-authorize default -P icmp -p 22 -s 0.0.0.0/0
$ euca-authorize default -P icmp -p 3389 -s 0.0.0.0/0

 

 

 

    Best Regards

Description: signature (Custom)

Indra Suryatama

Phone:   

+6285742865348

+6281325610080

 

 

From: ubuntu-cloud-bounces at lists.ubuntu.com [mailto:ubuntu-cloud-bounces at lists.ubuntu.com] On Behalf Of Shang Wu
Sent: Wednesday, January 26, 2011 10:06 PM
To: Darren Govoni
Cc: ubuntu-cloud at lists.ubuntu.com
Subject: Re: [ubuntu-cloud] Cannot ping running instance

 

So, all your UEC stuff is running on the same physical box? If so, I remember you need to do some special tweaks about this kind of settings... 

On 11-01-26 10:54 PM, Darren Govoni wrote: 

Hi,
All of UEC is running on my quad-core laptop. I know its not a preferred configuration but its useful for development.
So when I try to ssh its from the same physical machine using a shell prompt. Is this what you mean?

thanks,
Darren

On Wed, 2011-01-26 at 22:45 +0800, Shang Wu wrote:



Hi Darren,

On 11-01-26 10:24 PM, Darren Govoni wrote: 



Hi,
  I am running UEC (installed into a 10.10 desktop). After many failed attempts to install a store 10.04 image, it finally installed.
I was able to run the instance and its running.

I cannot ping or ssh into it. It is managed mode with public/private IP. I open port 22 on the security group.

>From my shell on my host machine, I am attached to my 192.168.0 network (wlan nic). My instance public IP is 192.168.2 network.
All the UEC stuff runs on 192.168.1 on eth0 nic.

So how does the routing occur?

thanks for any tips.

Darren 


I am also very new to UEC, but here is my two cents... Have you tried to ssh from the frontend server? if your security setting is right, you should be able to ssh from there. I believe the frontend is directing the request to the proper resource, in other words, routing is done at the frontend side.

Cheers,

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-cloud/attachments/20110126/4fe909d2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: application/octet-stream
Size: 1685 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-cloud/attachments/20110126/4fe909d2/attachment-0001.obj>