ntp won't find peers

JeGr

Our lab VM has configured 3 NTP pools:

1.<country>.pool.ntp.org
2.<country>.pool.ntp.org
3.<country>.pool.ntp.org

Same config works on the current plus-devel VM (still on 22.09 from august) and formerly worked with the CE devel VM. Now it won't connect to servers. Log shows dozends of Soliciting pool server <ip> but no active peer shows up even after more then 15min. First assumed it may be a MultiWAN problem (lab has 2 WANs) so I disabled one but still no NTP.

Cheers
\jens

fireodo

@jegr said in ntp won't find peers:

1.<country>.pool.nt.org
2.<country>.pool.nt.org
3.<country>.pool.nt.org

Should it not be *.pool.NTP.org?

JeGr

@fireodo said in ntp won't find peers:

@jegr said in ntp won't find peers:

1.<country>.pool.nt.org
2.<country>.pool.nt.org
3.<country>.pool.nt.org

Should it not be *.pool.NTP.org?

it is, sorry, just copy&paste error. The config was working before so no error there :) The names are resolving as shown by the soliticing messages in the log.

jimp

I see the problem, it's not fully handling a case where there the list of selected NTP interfaces has a single empty entry and nothing else, which IIRC is the default. When the code was updated to handle the new config access style it ends up with a slightly different result than it did in the past.

I pushed a fix just now, the next snapshot should be OK.

https://github.com/pfsense/pfsense/commit/941eca9a6fe02cda70a4c5b5697fd6c0f6e2c3a9

JeGr

@jimp said in ntp won't find peers:

https://github.com/pfsense/pfsense/commit/941eca9a6fe02cda70a4c5b5697fd6c0f6e2c3a9

Can confirm that works. After restarting, NTP immediatly pulls pool servers into the mix and connects to peers :)
Great!