This is from testing from 44.56.6.4 in Pennsylvania
root@pool4:~# ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 0, offset 0.000000, delay 0.00000 30 Jan 18:38:13 ntpdate[9399]: no server suitable for synchronization found
This is testing from my public ip on level 3 [root@2338 ~]# ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 0, offset 0.000000, delay 0.00000 30 Jan 18:35:07 ntpdate[6342]: no server suitable for synchronization found
Nothing found here. Corey N3FE
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail This email has been sent from a virus-free computer protected by Avast. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Sat, Jan 30, 2016 at 6:08 PM, lleachii--- via 44Net < 44net@hamradio.ucsd.edu> wrote:
(Please trim inclusions from previous messages) _______________________________________________ All,
Time - NTP UDP/123
This is odd, I'm able to reach the server and 44.60.44.1 from AMPR and
the Public Internet (what exactly are you trying to 'reach' at 44.60.44.1 to determine its status, as I've only announced NTP as being available there)
- using 'ntpdate -q 44.60.44.1' or 'ntpdate -q kb3vwg-001.ampr.org' works
for me anywhere on the Internet
kb3vwg@kb3vwg:~$ ntpdate -q 44.60.44.1 server 44.60.44.1, stratum 2, offset 0.001173, delay 0.02589 30 Jan 18:00:19 ntpdate[1058]: adjust time server 44.60.44.1 offset0.001173 sec
- I have now permitted access from the Public Internet (previously, it was
only available to 44 hosts), let me know
- Lynwood
KB3VWG