vyos-1x.git/data/templates/chrony, branch rolling

ntp: T8882: add per-server poll interval, presend and extension field options

2026-09-28T18:30:00+00:00

Poll intervals were left entirely to the NTP daemon's built-in defaults, so an operator could not widen or narrow the polling range for an individual server, warm up authenticated associations before a poll, or ask a peer for the higher resolution timestamps it may be able to provide. Each configured server and pool now accepts a minimum and maximum poll exponent, defaulting to the values the daemon already used, plus an optional presend exponent and a switch for the F323 extension field. Existing configurations render the same associations as before. Co-authored-by: Christian Breunig

ntp: T9159: add source-interface option for client requests

2026-08-05T06:38:05+00:00

Complements source-address (bindacqaddress) with a device-based bind (chrony's bindacqdevice) for outgoing NTP client requests. Addresses feedback on T9159 that a source IP alone cannot unambiguously select the egress path in multi-VRF setups with overlapping address ranges. Both options bind different socket properties and can be combined. If "vrf" is set, source-interface must belong to that VRF, mirroring the existing check for "interface".

ntp: T9159: add source-address option for client requests

2026-08-03T21:14:08+00:00

chrony (the daemon backing VyOS' NTP service) has no way to pin the local address used for outgoing client requests to upstream servers. "interface"/"listen-address" only configure the server/listening role (binddevice/bindaddress); nothing controls the source address chosen for packets chronyd itself originates. On a router with more than one usable egress path to a given NTP server (e.g. multiple transit/peering sessions), the kernel's default source-address selection depends on whichever route wins at query time. If that route happens to egress through an interface whose own address is not globally reachable (a private peering-fabric segment, for example), the request goes out with an address the reply can never route back to - an intermittent, path-dependent failure with no existing workaround at the NTP layer. BGP and friends already solve the equivalent problem via "update-source" bound to the loopback; NTP had no analogous option. Add "service ntp source-address

", reusing the existing source-address-ipv4-ipv6-multi include (same pattern already used for e.g. RADIUS servers), and render it as chrony's "bindacqaddress" directive - the client-side counterpart to "bindaddress" that chrony already supports natively.

ntp: T8601: add local stratum option

2026-05-21T15:32:53+00:00

T6630: ntp: fix timestamp nested under ptp

2024-11-26T06:01:34+00:00

T6630: ntp: move interface timestamping configuration under ptp node

2024-09-21T06:51:28+00:00

T6630: ntp: rename ptp-transport to ptp and use defaultValue for port

2024-09-21T06:51:28+00:00

T6630: ntp: add chrony "ntp over ptp" transport

2024-09-21T06:51:28+00:00

T6630: ntp: add hardware timestamp offload

2024-09-21T06:51:28+00:00

T6630: ntp: add "interleave" option

2024-09-21T06:51:28+00:00