Chrony

NTP Server, Purpose

Provides NTP service for devices on the network so systems maintain syncronization and accurate time even if external NTP sources become unavailable. Synchronized time provides basis for logs correlation. Local service enables disallow of random incoming NTP packets -> better security.

Host

hostname: april
hardware: raspberry pi
OS: ?
IP: DHCP reserves 192.168.42.186? for april on sysadmin group VLAN
Maintainer: Sysadmin Study Group
Software: chronyd (daemon) and chronyc (command line)
Package: chrony
Main Config: /etc/chrony/chrony.conf
Backup Configs: /etc/chrony/chrony.conf.mm-dd-yyyy.bak

Currently Have, Summary

April is running chrony, an NTP client and server.

April is currently getting time from the default Debian pool

2.debian.pool.ntp.org

The other servers (leonardo, michaelangelo, donatello, and rafael) are still getting their time from the same default Debian ntp.org pool via the default client, systemd-timesyncd

Would Like to Have / Next Steps

• Reconsider whether april should continue to be time server (b/c no Real Time Clock)
• Reconsider whether NTP and VPN should coexist on same machine, because DDOS potential.
• If yes, point timesyncd config on servers to get time from april.
• Contemplate whether to use chrony on servers.
• Add appropriate public NTP servers to april.

Verification and Troubleshooting

Check service status: systemctl status chrony.service
Check connected sources: chronyc sources
Check synchronization: chronyc tracking
Chrony allows reloading the config without restarting the service.

Foreseeable Complications

April - like all raspberry pi's - lacks a Real Time Clock. If turned off, she will need to get re-synced to an internet time server. Another solution is to Add a Real Time Clock to Raspberry Pi