[Bug 16264] New: NTP server t2 and t3 timestamps give bogus results

bugzilla at busybox.net bugzilla at busybox.net
Sun Dec 1 20:04:18 UTC 2024


https://bugs.busybox.net/show_bug.cgi?id=16264

            Bug ID: 16264
           Summary: NTP server t2 and t3 timestamps give bogus results
           Product: Busybox
           Version: 1.37.x
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Networking
          Assignee: unassigned at busybox.net
          Reporter: bert.broekhuizen at kpnmail.nl
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

Running the Busybox NTP server on an ARM32 platform (FreshTomato on Netgear
R7000 router) makes it give out bad timestamps.

Example output from an sntp client:
$ sntp -D 1 192.168.1.1
ntpdig: querying 192.168.1.1 (192.168.1.1)
org t1: eaf73ae1.de7a3000 rec t2: 7fffffff.ffffffff
xmt t3: 7fffffff.ffffffff dst t4: eaf73ae1.de98f000
org t1: 1733082209.869052 rec t2: -61505152.000000
xmt t3: -61505152.000000 dst t4: 1733082209.869521
rec-org t21: -1794587361.869052  xmt-dst t34: -1794587361.869521
1968-01-20 03:14:08.0 (+0000) -1794587361.869287 +/- 0.002188 192.168.1.1 s2
no-leap

On the same system, reverting only networking/ntpd.c to the one from version
1.36.1 brings back goodness.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the busybox-cvs mailing list