<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font face="Georgia">Yep - that was it. I'm able to connect now.<br>
      <br>
      I did the same thing when I first set up my system to speak NTS. <br>
      <br>
      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!<br>
    </font><br>
    <div class="moz-cite-prefix">On 3/10/20 12:02, Rick Bollar wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:4RuKPkxRybFypTjmfCpiALBEqN3vdPc8vGJX4pw3bg6XpgJtcbUgg0aeKxqFhOx0C1LPjpe7QA3-58pvEp7pTMb4AdW8yGv-NVxe57iGYro=@bollar.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div>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.<br>
      </div>
      <div><br>
      </div>
      <div>Rick</div>
      <div><br>
      </div>
      <div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br>
      </div>
      <div> On Tuesday, March 10, 2020 12:56 PM, Paul Theodoropoulos via
        users <a class="moz-txt-link-rfc2396E" href="mailto:users@ntpsec.org"><users@ntpsec.org></a> wrote:<br>
      </div>
      <div> <br>
      </div>
      <blockquote class="protonmail_quote" type="cite">
        <div>Yes, same results for me:<br>
        </div>
        <div> <br>
        </div>
        <div> <span style="font-family:menlo,consolas,"courier
            new",monospace">root@relay: /var/log # ntpq -p<br>
                 remote                                   refid      st
            t when poll reach   delay   offset   jitter<br>
=======================================================================================================<br>
            *aws.ntp                                 169.254.169.122  3
            u   48   64  377   0.1159   0.0506   0.0403<br>
             3.us.pool.ntp.org                       .POOL.          16
            p    -  256    0   0.0000   0.0000   0.0001<br>
             ntp.bollar.com                          .NTS.           16
            u    -  68m    0   0.0000   0.0000   0.0001<br>
            +ntpsec.anastrophe.com                   .PPS.            1
            8    5   64  377  32.8659  -2.4094   0.5334<br>
            -li290-38.members.linode.com             142.66.101.13    2
            u  112  128  377  69.3320  -0.1490   0.6753<br>
            -hydrogen.constant.com                   209.51.161.238   2
            u  122  128  377  83.4695  -2.8154   0.0483<br>
            -198.255.68.106                          192.168.1.193    2
            u   65   64  377  33.4422   2.1068   0.0733<br>
            -144.172.126.201                         129.7.1.66       2
            u  129   64  376 107.7060 -24.2448   0.6534<br>
            +tock.usshc.com                          .GPS.            1
            u   62   64  377  60.3009  -3.6061   0.4029<br>
            +mirror1.sjc02.svwh.net                  216.218.254.202  2
            u   59   64  377  27.9513   1.0609   0.3852<br>
          </span><span style="font-family:menlo,consolas,"courier
            new",monospace"><br>
          </span><span style="font-family:menlo,consolas,"courier
            new",monospace">If it assists in diagnosis in your
            logs, I'm testing from three different servers/three
            different networks -<br>
            <br>
            <br>
            35.155.231.77</span></div>
        <div> <span style="font-family:menlo,consolas,"courier
            new",monospace">129.146.214.219</span><span
            style="font-family:menlo,consolas,"courier
            new",monospace"><br>
          </span><span style="font-family:menlo,consolas,"courier
            new",monospace">67.164.22.151</span></div>
        <div> <br>
        </div>
        <div> <br>
        </div>
        <div class="moz-cite-prefix">On 3/10/20 08:18, Stephan Seitz via
          users wrote:<br>
        </div>
        <blockquote type="cite">
          <div>On Di, Mär 10, 2020 at 14:50:12 +0000, Rick Bollar via
            users wrote: <br>
          </div>
          <div> <br>
          </div>
          <blockquote type="cite">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 <a href="https://ntp.bollar.com" moz-do-not-send="true">https://ntp.bollar.com</a> 
            <br>
          </blockquote>
          <div><br>
          </div>
          <div>Well, I can’t connect neither to the NTS port nor the
            HTTPS port.<br>
          </div>
          <div> <br>
          </div>
          <div> Shade and sweet water! <br>
          </div>
          <div> <br>
          </div>
          <div>     Stephan <br>
          </div>
          <div> <br>
          </div>
          <div> <br>
          </div>
        </blockquote>
        <div><br>
        </div>
        <pre cols="72">--
Paul Theodoropoulos
<a href="http://www.anastrophe.com" moz-do-not-send="true">www.anastrophe.com</a>
</pre>
      </blockquote>
      <div><br>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Paul Theodoropoulos
<a class="moz-txt-link-abbreviated" href="http://www.anastrophe.com">www.anastrophe.com</a></pre>
  </body>
</html>