Similar results for me (from 44.131.243.2)
PING 44.185.22.1 (44.185.22.1): 56 data bytes 64 bytes from 44.185.22.1: icmp_seq=0 ttl=63 time=78.941 ms 64 bytes from 44.185.22.1: icmp_seq=1 ttl=63 time=78.692 ms 64 bytes from 44.185.22.1: icmp_seq=2 ttl=63 time=79.611 ms 64 bytes from 44.185.22.1: icmp_seq=3 ttl=63 time=78.421 ms
Regards
Andy Brittain G0HXT g0hxt@greatbrittain.co.uk
On 19 Feb 2016, at 13:14, Tom SP2L SP2L@wp.pl wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello Daftcho.
Your 44.185.22.1 is reachable from AMPRNet network:
root@linux:/# ping -c5 44.185.22.1 PING 44.185.22.1 (44.185.22.1) 56(84) bytes of data. 64 bytes from 44.185.22.1: icmp_req=1 ttl=64 time=119 ms 64 bytes from 44.185.22.1: icmp_req=2 ttl=64 time=113 ms 64 bytes from 44.185.22.1: icmp_req=3 ttl=64 time=113 ms 64 bytes from 44.185.22.1: icmp_req=4 ttl=64 time=121 ms 64 bytes from 44.185.22.1: icmp_req=5 ttl=64 time=112 ms
--- 44.185.22.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 112.776/116.131/121.457/3.576 ms root@linux:/#
Best regards.
-- Tom - SP2L
It is nice to be important. But it is more important to be nice!
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net