Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: NetBSD on AWS



On Sun, Nov 10, 2013 at 8:53 PM, Christoph Egger 
<christoph_egger%gmx.de@localhost> wrote:
> Am 10.11.13 08:52, schrieb Abhinav Upadhyay:
>> Hi,
>>
>> I am trying to run NetBSD in AWS. I have tried launching instances
>> with 3 different NetBSD AMIs (6.1.2, 6.1.1, and 6.0), all 64 bit
>> variants. However, upon starting up the instance, I am unable to
>> connect to it using ssh. Port 22 is open in the security group
>> configurations.
>>
>> I tried to probe the ports open in the instance using nmap. As per
>> nmap, only port 25 is open in the instance.
>>
>> [abhinav:~/]$ nmap -Pn  ec2-54-200-58-185.us-west-2.compute.amazonaws.com
>>
>> Starting Nmap 6.40 ( http://nmap.org ) at 2013-11-10 12:56 IST
>> Nmap scan report for ec2-54-200-58-185.us-west-2.compute.amazonaws.com
>> (54.200.58.185)
>> Host is up (0.0027s latency).
>> Not shown: 999 filtered ports
>> PORT   STATE SERVICE
>> 25/tcp open  smtp
>>
>> I tried connecting to port 22 using telnet as well, which failed
>> (telnet connection on port 25 passed). Is it possible that sshd is not
>> being started on the instance?
>>
>> Regards
>> Abhinav
>
> Have you add the same ssh key to ssh-agent for publickey auth
> you have used to start the NetBSD instance?
> This is one of the most common mistakes.
>
> Unless the problem is NetBSD specific I think the AWS Forums are
> the right places to get help.

Yes, I am using the correct key pair. Even if I had the wrong key, the
telnet to port 22 should have succeeded. I will ask on AWS forums as
well.

Regards
Abhinav


Home | Main Index | Thread Index | Old Index