ntpq reports different polling intervall than thesniffed UDP packet - NTP
This is a discussion on ntpq reports different polling intervall than thesniffed UDP packet - NTP ; Hello,
I'm wondering why I get from ntpq this output :
tfoerste@n22 ~/devel/linux-2.6 $ ntpq -pn
remote refid st t when poll reach delay offset jit
ter
================================================== ========================*85.25.144.154 143.93.99.252 2 u 84 128 377 29.453 10.241 1.
066
+87.32.12.19 ...
-
ntpq reports different polling intervall than thesniffed UDP packet
Hello,
I'm wondering why I get from ntpq this output :
tfoerste@n22 ~/devel/linux-2.6 $ ntpq -pn
remote refid st t when poll reach delay offset jit
ter
================================================== ========================*85.25.144.154 143.93.99.252 2 u 84 128 377 29.453 10.241 1.
066
+87.32.12.19 4.176.44.157 2 u 88 128 377 50.685 8.234 1.
607
+81.169.180.26 192.53.103.104 2 u 4 128 377 31.092 -1.381 1.
082
whereas the field "peer polling intervall" of the sniffed network stream sh
ows a value of 8 (=%6 sec)
for all packets except packet 3 and 4.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
-
Re: ntpq reports different polling intervall than the sniffed UDPpacket
How did you sniff ?
Are you using tcpdump/ethereal ?
Venu
Toralf Förster wrote:
> Hello,
>
> I'm wondering why I get from ntpq this output :
>
> tfoerste@n22 ~/devel/linux-2.6 $ ntpq -pn
> remote refid st t when poll reach delay offset jit
> ter
> ================================================== =======================
> *85.25.144.154 143.93.99.252 2 u 84 128 377 29.453 10.241 1.
> 066
> +87.32.12.19 4.176.44.157 2 u 88 128 377 50.685 8.234 1.
> 607
> +81.169.180.26 192.53.103.104 2 u 4 128 377 31.092 -1.381 1.
> 082
>
> whereas the field "peer polling intervall" of the sniffed network stream sh
> ows a value of 8 (=56 sec)
> for all packets except packet 3 and 4.
>
>
-
Re: ntpq reports different polling intervall than the sniffed UDPpacket
Toralf Förster wrote:
> +81.169.180.26 192.53.103.104 2 u 4 128 377 31.092 -1.381 1.
> 082
>
> whereas the field "peer polling intervall" of the sniffed network stream sh
> ows a value of 8 (=56 sec)
> for all packets except packet 3 and 4.
>
Your Usenet client (combination of your email program and the list to
Usenet gateway) has broken MIME quoted-printable handling, with the
result that I see 56, rather than 256, although the
exact behaviour is error recovery dependent.
You haven't included the trace, so I don't know what you mean by packets
3 and 4. If you included these as an attachment, please note that the
mailing list is not the real forum, it is just a convenience for
accessing the newsgroup comp.protocols.time.ntp, which is a non-binaries
group, so should not have attachments (and any may well have been
stripped by the gateway as a result).
>
-
Re: ntpq reports different polling intervall than the sniffed UDP packet
On 2008-03-20, David Woolley wrote:
> Toralf Förster wrote:
>
>> +81.169.180.26 192.53.103.104 2 u 4 128 377 31.092 -1.381 1.082
>>
>> whereas the field "peer polling intervall" of the sniffed network
>> stream sh ows a value of 8 (=56 sec) for all packets except packet 3
>> and 4.
>
> Your Usenet client (combination of your email program and the list to
> Usenet gateway) has broken MIME quoted-printable handling, with the
> result that I see 56, rather than 256, although the
> exact behaviour is error recovery dependent.
His original message to the questions@ list is here:
https://lists.ntp.org/pipermail/ques...ch/017925.html
--
Steve Kostecke
NTP Public Services Project - http://support.ntp.org/
-
Re: ntpq reports different polling intervall than the sniffed UDPpacket
> His original message to the questions@ list is here:
>
> https://lists.ntp.org/pipermail/ques...ch/017925.html
>
Thanks. Different error recovery for the invalid quoted printable, but
it still has the attachment stripped, because it was a binary.