Rob,


Yea, I also sync with multiple severs (I'm also Stratum 2). I sync with mostly atomic servers of governments/universities, as well as mains power companies (I believe I received approval from one). I have 1 or 2 GPS-based ISPs as well.

I will add other AMPRNet peers (Stratum 1, 2 or 3) as they note them to me.

I agree with your assessment (for IPENCAP GW's), as long as operators configure accordingly.

This should be noted in the Wiki.

Justification: I actually began allowing this years ago as courtesy because I noted the same failed NTP requests from some operators Public IPs in netflow. Doing route testing yesterday I now see why. I think it may require a custom IPv4 rule to accommodate the ns.ardc.net NTP Access Policy.

---

Mark,

I'm not able to successfully run the following command from my Public IP:


`ntpdate -q 44.64.24.123`


I do appreciate your consideration of the issue and thank you for your reply. The issue is my my GW (i.e. possessing is own Main Routing Table to reach the Public Internet for IPENCAP) - is the NTP server. This in layman's terms means this requires the GW to have 3 split routing/DNS/etc. (not just 2 for Internet/AMPRNet). You present the same issue for Gateways that the ns.ardc.net conversion causes (i.e. you need to first be on the Mesh for Time Services, but you might need time first - the chicken-or-the-egg paradox I noted).

Noting this in the Wiki may be helpful for others. - if that's gonna be the suggestion for NTP as well - e.g. "just use one that works".


Thanks, appreciation and 73 to both,



- Lynwood
KB3VWG


On Wednesday, May 8, 2024 at 09:23:24 AM EDT, Rob PE1CHL via 44net <44net@mailman.ampr.org> wrote:


Lynwood,

I don't consider it a problem that ARDC would not provide NTP services.
NTP is such an easily run service... we have too many NTP servers inside our 44.137/16
network to even mention them here.  Every Linux host in the network runs either ntpd
or chrony to synchronize its own time, and allows queries from within net44.
So no problem at all to get synchronized using a couple of nearby servers.

As we run co-channel repeaters on the network, many of those NTP servers are stratum 1.
(synchronized by PPS from a GPSDO).  I also have a LeoNTP at 44.137.41.102

At address 44.137.0.1 (internet address 145.220.78.2 or 2001:67c:6ec:6861:145:220:78:2)
we have an NTP server with about 20 sources, which is also used for monitoring.

And of course on the internet there is pool.ntp.org.

Rob

_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org