Please fill in the following information:

Issue description 

Step 3.2 to says Use the chronyc ntpdata command to generate NTP traffic that is specific to the classroom server.
[root@workstation ~]#
chronyc ntpdata classroom.example.com{}

{{}}

This is not generating NTP traffic in when checked in Wireshark

Steps to reproduce:

"chronyc ntpdata classroom.example.com" is connecting to the chrony UNIX socket at "/var/run/chrony/chronyc.<PID>.sock". This can be verified using "strace -ff -s 4096 chronyc ntpdata classroom.example.com 2>&1 | grep chronyc".

The NTP traffic that can (once in a while) be seen using "tcpdump -i any 'port 123'" on the system does NOT belong to "chronyc ntpdata classroom.example.com", but to "chronyd" as part of the regular timekeeping work chronyd does with its upstream/reference NTP server as per the Poll interval set.

Workaround:

What however successfully generates NTP traffic is chronyd -Q 'server classroom.example.com iburst'.

Expected result: