NTS Time Server ntp.bollar.com

[Paul Theodoropoulos]

Yep - that was it. I'm able to connect now.

I did the same thing when I first set up my system to speak NTS.

In fact, when I first set up _NTP_ I had a sorta-kinda similar problem - 
peers could connect, but not clients. Eventually figured out it was AT&T 
blocking non-port 123 source ports to 123 destination. Had to change 
internet providers to fix that!

On 3/10/20 12:02, Rick Bollar wrote:
> Paul, thanks for testing. Since you see my refid as .NTS. I think you 
> were able to connect, but not authenticate. I notice that I forgot to 
> add TCP:123 to my firewall, so perhaps it's as simple as that. I'll 
> keep looking at the logs for future connections.
>
> Rick
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, March 10, 2020 12:56 PM, Paul Theodoropoulos via users 
> <users at ntpsec.org> wrote:
>
>> Yes, same results for me:
>>
>> root at relay: /var/log # ntpq -p
>>      remote                                   refid      st t when 
>> poll reach   delay   offset   jitter
>> =======================================================================================================
>> *aws.ntp                                 169.254.169.122  3 u   48   
>> 64  377   0.1159   0.0506   0.0403
>>  3.us.pool.ntp.org                       .POOL.          16 p    -  
>> 256    0   0.0000   0.0000   0.0001
>>  ntp.bollar.com                          .NTS.           16 u    -  
>> 68m    0   0.0000   0.0000   0.0001
>> +ntpsec.anastrophe.com                   .PPS.            1 8    5   
>> 64  377  32.8659  -2.4094   0.5334
>> -li290-38.members.linode.com             142.66.101.13    2 u  112  
>> 128  377  69.3320  -0.1490   0.6753
>> -hydrogen.constant.com                   209.51.161.238   2 u  122  
>> 128  377  83.4695  -2.8154   0.0483
>> -198.255.68.106                          192.168.1.193    2 u   65   
>> 64  377  33.4422   2.1068   0.0733
>> -144.172.126.201                         129.7.1.66       2 u  129   
>> 64  376 107.7060 -24.2448   0.6534
>> +tock.usshc.com                          .GPS.            1 u   62   
>> 64  377  60.3009  -3.6061   0.4029
>> +mirror1.sjc02.svwh.net                  216.218.254.202  2 u   59   
>> 64  377  27.9513   1.0609   0.3852
>>
>> If it assists in diagnosis in your logs, I'm testing from three 
>> different servers/three different networks -
>>
>>
>> 35.155.231.77
>> 129.146.214.219
>> 67.164.22.151
>>
>>
>> On 3/10/20 08:18, Stephan Seitz via users wrote:
>>> On Di, Mär 10, 2020 at 14:50:12 +0000, Rick Bollar via users wrote:
>>>
>>>> For those of you with a need, or who are testing NTS, I have spun 
>>>> up a Stratum 1 Raspberry Pi Server running ntpsec-1.1.8. It's at 
>>>> ntp.bollar.com:123. Configuration & statistics (using ntpviz) are 
>>>> available at https://ntp.bollar.com
>>>
>>> Well, I can’t connect neither to the NTS port nor the HTTPS port.
>>>
>>> Shade and sweet water!
>>>
>>>     Stephan
>>>
>>>
>>
>> --
>> Paul Theodoropoulos
>> www.anastrophe.com  <http://www.anastrophe.com>
>

-- 
Paul Theodoropoulos
www.anastrophe.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/users/attachments/20200310/8043f117/attachment.htm>