OPNsense Forum

English Forums => General Discussion => Topic started by: siga75 on January 10, 2020, 08:05:56 am

Title: chronyd
Post by: siga75 on January 10, 2020, 08:05:56 am

is it planned to use chronyd instead of ntpd on 20.1? chrony is much better in general, but in particular for machine with a bad hardware clock, or for virtual machines

unrelated to that it would be nice to have, on ntp conf:
- configure peers and not only servers
- minpoll (some ntp servers are not happy with too frequent requests)
- GPS/PPS conf currently is or prefer or noselect, it should be possible to have nothing specified

cheers

Title: Re: chronyd
Post by: mimugmail on January 10, 2020, 09:01:47 am

As there was no real request it wont be changed in 20.1. Maybe you can start with a feature request via github?

Title: Re: chronyd
Post by: siga75 on January 10, 2020, 01:11:01 pm

Quote from: mimugmail on January 10, 2020, 09:01:47 am

As there was no real request it wont be changed in 20.1. Maybe you can start with a feature request via github?

I am not used to open requests since it's just a nice to have, and don't want to bother the guys, who have already a lot of stuff to do :)

But I will do an exception, eventually they will reject the request

Cheers

Title: Re: chronyd
Post by: fabian on January 11, 2020, 07:31:24 am

As far as I know this daemon is intended for clients and maybe servers but it cannot distribute the time in the network which would make sense in case of a domain controller or any kind of router which is accessible from every host to sync times.

Title: Re: chronyd
Post by: siga75 on January 11, 2020, 08:47:59 am

Quote from: fabian on January 11, 2020, 07:31:24 am

As far as I know this daemon is intended for clients and maybe servers but it cannot distribute the time in the network which would make sense in case of a domain controller or any kind of router which is accessible from every host to sync times.

Not sure if I understood what you mean, but it's indeed intended for servers too, it still speak NTP, every NTP client (or SNTP for windows you mentioned) can use it.

I built my own GPS/NTP server using a Pi and chronyd, it works like a charm: https://www.signorini.ch/content/gps-for-time-synchronization

I could try to participate in this community and create a plugin, following mimugmail tutorial, I will let you know if I succeed :)

Title: Re: chronyd
Post by: mimugmail on January 11, 2020, 08:52:38 am

First, wait for 20.1, then we will see if we get a pkg for it. Then we can start with a plugin

Title: Re: chronyd
Post by: siga75 on January 11, 2020, 09:16:50 am

Quote from: mimugmail on January 11, 2020, 08:52:38 am

First, wait for 20.1, then we will see if we get a pkg for it. Then we can start with a plugin

OK master :)

Title: Re: chronyd
Post by: Tubs on February 15, 2021, 12:42:29 pm

Quote from: siga75 on January 10, 2020, 08:05:56 am

unrelated to that it would be nice to have, on ntp conf:
- configure peers and not only servers

Chrony meanwhile is existing as a plugin. I will try out when I find time.
But this point above is what I am still missing in the current NTP config: peers.