Project

General

Profile

Actions
Copy link

Bug #9931

closed

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

Added by Isaac McDonald about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
NTPD
Target version:
2.4.5
Start date:
11/27/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
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.

Actions
Copy link
 #1

Updated by Jim Pingle about 5 years ago

  • Assignee set to Jim Pingle
  • Target version set to 2.5.0
  • Affected Version set to All
  • Affected Architecture All added
  • Affected Architecture deleted ()
Actions
Copy link
 #3

Updated by Jim Pingle about 5 years ago

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

Actions
Copy link
 #4

Updated by Jim Pingle about 5 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Jim Pingle about 5 years ago

  • Target version changed from 2.5.0 to 2.4.5
Actions
Copy link
 #6

Updated by Jim Pingle about 5 years ago

  • Status changed from Feedback to Resolved
: grep pool /conf.default/config.xml 
        <timeservers>2.pfsense.pool.ntp.org</timeservers>

And on a default installation with IPv6, there are IPv6 NTP servers in the list.

2.4.5.a.20191217.0637

Actions
Copy link

Also available in: Atom PDF