NTS-KE port is 4460

[Rick Bollar]

I have updated ntp.bollar.com and have UDP/123 and TCP/4460 open on my firewall.

ntpq ntpsec-1.1.9+ 2020-06-08T13:26:50Z (git rev 4efd47be3)

     remote                                   refid      st t when poll reach   delay   offset   jitter
=======================================================================================================
oPPS(0)                                  .PPS.            0 l    1    1  377   0.0000  -0.0002   0.0003
+SHM(1)                                  .GPSD.           1 l    5   16  377   0.0000  -0.0000   0.0002
 ntp2.bollar.com                         10.0.0.199       2 8   10   16  377   0.2824  -0.0031   0.0096
 reporting.bollar.com                    10.0.0.199       2 u    9   16  377   0.2486  -0.0188   0.0201
+time.cloudflare.com                     10.15.10.134     3 8  368  512    1  16.0063   1.4874   1.3467
 ntsts.sth.ntp.se                        .STEP.          16 7    -  512    0   0.0000   0.0000   0.0010
+ntp1.glypnod.com                        64.142.1.20      2 8  221  512    3  63.3096   0.0888   1.7872
-nts1.time.nl                            211.207.249.90   2 8  281  512    1 138.1889  -1.8001   2.6144
-ntpmon.dcs1.biz                         .PPS.            1 8  189  512    3 222.7183   0.8338   2.2392
-c-67-164-22-151.hsd1.ca.comcast.net     .PPS.            1 8  162 1024    1  71.2813  -2.2882   0.7373

Rick

Sent from ProtonMail, Swiss-based encrypted email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, June 8, 2020 4:02 AM, Hal Murray via users <users at ntpsec.org> wrote:

> <https://www.iana.org/assignments/service-names-port-numbers/service-names-port
> -numbers.xhtml?search=4460>
> 

> The servers atntp1.glypnod.com and ntp2.glypnod.com are listening on both the
> old and new ports.
> 

> When your servers are listening on the new port, please let me/us know and
> I'll contribute some test traffic.
> 

> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 

> The listen-on-both change is in git head. There are 2 other code changes
> before a final/clean release. The first is to change the default port number
> for KE connections. (We've been using 123.) The second is to drop listening
> on the old port number.
> 

> My plan is to wait a few days or a week before changing the default port
> number. The idea is to give time for most sites to start listening on the new
> port number. Then wait another few days or a week before stopping listening
> on port 123.
> 

> If the RFC is actually published before all that waiting happens, we'll
> probably make the changes and do a release with tarball.
> 

> 

> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 

> These are my opinions. I hate spam.
> 

> users mailing list
> users at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 217 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/users/attachments/20200608/a3b66af0/attachment.bin>