On 01/07/2019 12:51, Denys Vlasenko wrote: > On Sat, Jun 29, 2019 at 4:12 PM <[email protected]> wrote: >> ntpd appears to be up and running/listening >> >> ss -tulpn | grep 123 >> udp UNCONN 0 0 *:123 *:* users:(("ntpd",pid=7589,fd=3)) >> >> However, querying the server appears not working, as if queries being >> refused and thus wondering what could be causing this, let alone >> resolving it? > Crank up log verbosity, it will tell you: > > $ ntpd --help > BusyBox v1.31.0 (2019-06-10 12:10:11 CEST) multi-call binary. > > Usage: ntpd [-dnqNwl] [-I IFACE] [-S PROG] [-k KEYFILE] [-p [keyno:N:]PEER]... > > NTP client/server > > -d Verbose (may be repeated) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > -n Do not daemonize > -q Quit after clock is set > -N Run at high priority > -w Do not set time (only query peers), implies -n > -S PROG Run PROG after stepping time, stratum change, and every 11 min > -k FILE Key file (ntp.keys compatible) > -p [keyno:NUM:]PEER > Obtain time from PEER (may be repeated) > Use key NUM for authentication > -l Also run as server on port 123 > -I IFACE Bind server to IFACE, implies -l
ran > /sbin/ntpd -nNlSddddp 1.openwrt.pool.ntp.org < and then ntpq -p ntpd: malformed packet received from ::1: size 12 ntptime -r no output from ntpd ntpdc -lnps no output from ntpd ntpdate localhost no output from ntpd Not sure what to make of that? _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
