Hello.

The ntpdc queries timeout every time on the NTP version ntp-dev-4.2.7p411 
(compiled myself). Looks like the type 7 packets are blocked from localhost but 
I don't know why.

The same queries work on the 4.2.6 (distribution version, Debian).

I test it like this - here's a query result on 4.2.6

root@raspberrypi:~# ntpdc -c kern
pll offset:           -0.024376 s
pll frequency:        -49.895 ppm
maximum error:        0.0039681 s
estimated error:      8.071e-06 s
status:               2001  pll nano
pll time constant:    4
precision:            1e-09 s
frequency tolerance:  500 ppm

And the query on 4.2.7p411, with the same configuration file
root@raspberrypi:~# ntpdc -c kern
localhost: timed out, nothing received
***Request timed out

The ntpq command works on both versions.

The NTP documentation says that ntpq uses a different packet type to 
communicate, type 5 and ntpdc uses type 7.


What might be the reason for type 7 packets being blocked from localhost?



root@raspberrypi:~# cat /etc/ntp.conf
driftfile /var/lib/ntp/ntp.drift

statsdir /var/log/ntpstats/

statistics loopstats peerstats sysstats 
filegen loopstats file loopstats type day link enable 
filegen peerstats file peerstats type day link enable 
filegen sysstats  file sysstats  type day link enable 

server tempus1.gum.gov.pl iburst burst minpoll 10
server tempus2.gum.gov.pl iburst burst minpoll 10
server ntp1.tp.pl iburst burst minpoll 10
server ntp2.tp.pl iburst burst minpoll 10
server vega.cbk.poznan.pl iburst burst minpoll 10
server ntp.itl.waw.pl iburst burst minpoll 10
server ntp.elproma.com.pl iburst burst minpoll 10
server ntp.certum.pl iburst burst minpoll 10

server 127.127.20.0 mode 0 minpoll 4 maxpoll 4 prefer
fudge 127.127.20.0 flag1 1 flag2 0 flag3 0 time2 0.600

restrict default kod nomodify notrap nopeer noquery
restrict -6 default kod nomodify notrap nopeer noquery

restrict 127.0.0.1 
restrict -6 ::1

_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Reply via email to