chrony sources: make add .sample to local-servers.sources, make it more useful for me

This commit is contained in:
Aminda Suomalainen 2024-04-28 10:02:31 +03:00
parent 18a04b1351
commit 44e22716f9
Signed by: Mikaela
SSH Key Fingerprint: SHA256:CXLULpqNBdUKB6E6fLA1b/4SzG0HvKD19PbIePU175Q
3 changed files with 21 additions and 11 deletions

View File

@ -1,2 +1,3 @@
jauderho-nts.sources
jauderho-nts-servers
local-servers.sources

View File

@ -1,11 +0,0 @@
# xleave probably won't be on local router
#server LOCALMACHINE.local iburst auto_offline xleave prefer
# Or alternatively reciprocally TODO: how do `key` options work? This
# apparently should only be done in trusted LAN.
# xleave is probably best to be used with other local Chronys, I somehow
# doubt potential router NTP might have it.
# A lot of reading say that it's better to use "server" on both sides
# rather than peer, I think even Chrony manual and that is where I took
# trusted LAN
#peer LOCALMACHINE.local auto_offline xleave prefer

View File

@ -0,0 +1,20 @@
# In my experience local routers are unlikely to support xleave
# I don't remember if this does NTP, probably not, but auto_offline.
server 192.168.8.1 iburst auto_offline prefer
# Local router, MikroTik
server 192.168.88.1 iburst auto_offline prefer
# Local machines/Chronys
server sedric.local iburst auto_offline xleave prefer
server lumina.local iburst auto_offline xleave prefer
server rbtpzn.local iburst auto_offline xleave prefer
server zaldaryn.local iburst auto_offline xleave prefer
# Or alternatively reciprocally TODO: how do `key` options work? This
# apparently should only be done in trusted LAN.
# xleave is probably best to be used with other local Chronys, I somehow
# doubt potential router NTP might have it.
# A lot of reading say that it's better to use "server" on both sides
# rather than peer, I think even Chrony manual and that is where I took
# trusted LAN
#peer LOCALMACHINE.local auto_offline xleave prefer