Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-13281

ch07s06: No NTP traffic generation in step 3.2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • RH342 - RHEL8.4-en-3-20230209
    • RH342
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 7
    • ROLE
    • en-US (English)

      Please fill in the following information:


      URL: https://rol.redhat.com/rol/app/courses/rh342-8.4/pages/ch07s06
      Reporter RHNID: abhkuma
      Section Title: Guided Exercise: Inspecting Network Traffic                                                          

      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:

            alingaya@redhat.com Ashish Lingayat
            abhkuma@redhat.com Abhishek Kumar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: