Project

General

Profile

Bug #9931

0.pfsense.pool.ntp.org doesn't work on IPv6 only installations

Added by Isaac McDonald 10 days ago. Updated 5 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
NTPD
Target version:
Start date:
11/27/2019
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:
All

Description

I debated whether this should be considered a bug or a feature. I ultimately decided it should be considered a bug seeing as how NTP won't sync if you only have IPv6 connectivity.

The only zone that contains IPv6 pool members is 2.pfsense.pool.ntp.org. CentOS 8 has done the same thing and are now using 2.centos.pool.ntp.org by default. pfSense should be configured to use 2.pfsense.pool.ntp.org by default so IPv6 only hosts are able to obtain the correct time via NTP.

See the thread on the NTP pool forum for an explanation as to why only that zone is IPv6 enabled.

Associated revisions

Revision 65db2067 (diff)
Added by Jim Pingle 10 days ago

Switch default NTP pool server. Fixes #9931

2.<x> pools contain both IPv4 and IPv6 hosts.

Revision f6e1c731 (diff)
Added by Jim Pingle 10 days ago

Switch default NTP pool server. Fixes #9931

2.<x> pools contain both IPv4 and IPv6 hosts.

(cherry picked from commit ae132b611439c15003578e38ec338a60eb9ed904)

History

#1 Updated by Jim Pingle 10 days ago

  • Assignee set to Jim Pingle
  • Target version set to 2.5.0
  • Affected Version set to All
  • Affected Architecture set to All

#3 Updated by Jim Pingle 10 days ago

I didn't see the PR and had already made the change after testing it out locally, it will show up soon.

#4 Updated by Jim Pingle 10 days ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#5 Updated by Jim Pingle 5 days ago

  • Target version changed from 2.5.0 to 2.4.5

Also available in: Atom PDF