[arm-allstar] Echolink

[David McGough]

Whoa! Be careful with nmap! Full port scans frequently will trip alarms at
both ISP's and the hosts you're probing. So, you may cause even more
connectivity issues if an automatic filter gets enabled somewhere, totally 
blocking your traffic!


73, David KB4FXC


On Fri, 24 May 2019, "Tony Ross via ARM-allstar" 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
> 
> _______________________________________________
> 
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>