Hello All,
I cannot get ntp to work on my computer.
In the past, with previous versions, there have been no problems - it
just works!
I think there is a bug in ntp somewhere (it has 0.0.0.0
on the brain), but the maintainer seems to disagree.
I submitted bug 56551 which has now been closed again.
For more details, please look at that bug report.
He suggested I ask on debian-user, which is exactly what
I am doing.
Here are some of the symptons:
snoopy# ntptrace
localhost: stratum 16, offset 0.000160, synch distance 0.69316
0.0.0.0: *Timeout*
0.0.0.0??????? Why?
snoopy# ntptrace -d
localhost: DoTransmit(127.0.0.1)
DoTransmit to 127.0.0.1
ReceiveBuf(127.0.0.1, 127.0.0.1)
stratum 16, offset -0.000092, synch distance 0.70863
0.0.0.0: DoTransmit(0.0.0.0)
DoTransmit to 0.0.0.0
ReceiveBuf(0.0.0.0, 127.0.0.1)
receive: wrong server
DoTransmit(0.0.0.0)
DoTransmit to 0.0.0.0
ReceiveBuf(0.0.0.0, 127.0.0.1)
receive: wrong server
[...]
receive: wrong server
*Timeout*
tcpdump also reports:
[...]
09:33:12.013686 localhost.1069 > localhost.domain: 30406+ PTR?
0.0.0.0.in-addr.arpa. (38) (ttl 64, id 5249)
09:33:12.013686 localhost.1069 > localhost.domain: 30406+ PTR?
0.0.0.0.in-addr.arpa. (38) (ttl 64, id 5249)
09:33:12.023686 localhost.domain > localhost.1069: 30406 NXDomain* q:
0.0.0.0.in-addr.arpa. 0/1/0 (102) (ttl 64, id 5250)
09:33:12.023686 localhost.domain > localhost.1069: 30406 NXDomain* q:
0.0.0.0.in-addr.arpa. 0/1/0 (102) (ttl 64, id 5250)
[...]
looks wrong to me.
Also, ntpdate and ntpd often cannot get a response from the server
(this seems a bit unpredicatable). Other people have been using the
same server fine, so I am guessing it is related to these problems
here.
Later: when first running ntpd I get this from tcpdump:
tcpdump: listening on ppp0
09:54:35.433686 202.12.87.129.ntp > 203.12.236.9.ntp: v4 client strat 0 poll 6
prec -17
09:54:35.603686 203.12.236.9.ntp > 202.12.87.129.ntp: v4 server strat 2 poll 6
prec -19
09:54:35.603686 202.12.87.129 > 203.12.236.9: icmp: 202.12.87.129 udp port ntp
unreachable [tos 0xc0]
What is going on? ntpd not even listening for the reply? No wonder it
didn't receive it...
Any ideas?
--
Brian May <[EMAIL PROTECTED]>
