[arm-allstar] Echolink

[Charles Powell]

PING is not a reliable way to see if a server is up or not.  They obviously block all ICMP packets and you will never get a ping response. NMAP does tell you what’s there but be careful.  If they detect you scanning, you could end up with your IP address blocked.

73,

Charles  NK8O

> On May 24, 2019, at 3:57 PM, Tony Ross via ARM-allstar <arm-allstar at hamvoip.org> wrote:
> 
> On 5/23/19 2:08 PM, "Boban Jovanovic YT1JB via ARM-allstar" quoted and wrote:
>> On 23.05.2019. 05:49, "Doug Crompton via ARM-allstar" wrote:
>>> The various Echolink servers have been up and down for awhile. At the
>>> moment I can't seem to ping any of them but since I have not tried that in
>>> awhile it is possible they do not allow pings any more.
>> 
>> Maybe you can test whether he lives by open / close socket on port 5200 B-)
> 
> # ping -c5 server1.echolink.org; nmap -sS -Pn server1.echolink.org
> PING server1.echolink.org (174.129.36.165) 56(84) bytes of data.
> 
> --- server1.echolink.org ping statistics ---
> 5 packets transmitted, 0 received, 100% packet loss, time 4100ms
> 
> 
> Starting Nmap 7.40 ( https://nmap.org ) at 2019-05-24 13:55 PDT
> Nmap scan report for server1.echolink.org (174.129.36.165)
> Host is up (0.10s latency).
> rDNS record for 174.129.36.165: ec2-174-129-36-165.compute-1.amazonaws.com
> Not shown: 998 filtered ports
> PORT???????? STATE SERVICE
> 22/tcp???? open?? ssh
> 5200/tcp open?? targus-getdata
> 
> Nmap done: 1 IP address (1 host up) scanned in 13.03 seconds