Actions
Bug #7110
closed
Empty custom NTP ACL produces syntax error in /var/etc/ntpd.conf
Start date:
01/10/2017
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3
Affected Architecture:
Description
On the NTPD ACL tab [Services/NTP/ACLs] the blank default entry under Custom Access Restrictions results in addition of a naked restrict keyword to /var/etc/ntpd.conf. This results in a syntax error that is logged during ntpd startup.
2017-01-10T17:57:29.426040-08:00 pfsense <ntp.err> ntpd[78938]: line 19 column 0 syntax error, unexpected T_EOC 2017-01-10T17:57:29.426257-08:00 pfsense <ntp.err> ntpd[78938]: syntax error in /var/etc/ntpd.conf line 19, column 0
ntpd ignores the invalid configuration line and continues to run after logging the error.
# # pfSense ntp configuration file # tinker panic 0 # Orphan mode stratum tos orphan 12 # Upstream Servers server xx.xx.xx.xx iburst maxpoll 9 statsdir /var/log/ntp logconfig =syncall +clockall +peerall +sysall driftfile /var/db/ntpd.drift restrict default kod limited nomodify nopeer notrap restrict -6 default kod limited nomodify nopeer notrap restrict interface ignore all interface listen vtnet0
Running current 2.3.3 snapshot.
2.3.3-DEVELOPMENT (amd64) built on Tue Jan 10 05:04:57 CST 2017 FreeBSD 10.3-RELEASE-p15
Updated by Jim Pingle almost 8 years ago
- Assignee set to Jim Pingle
- Target version set to 2.4.0
Updated by Jim Pingle almost 8 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset d90beba66f545af414f00124ba32a9ae087a29d2.
Updated by John Silva almost 8 years ago
Can confirm that fix works on current 2.3.3 snapshot. Thanks, Jim!
Updated by Jim Pingle almost 8 years ago
- Status changed from Feedback to Resolved
Updated by Jim Pingle almost 8 years ago
- Target version changed from 2.4.0 to 2.3.3
Actions