Dear all,
I'm very confused on how ntp do the timestamp. I'm running ntpd on
vxworks. It seems to me that the receive timestamp and the Transmit
timestamp are using two different clocks, because when I use ethereal/
wireshark to look up the information of the ntp packet,
the Recevie Time Stamp is:
>I'm very confused on how ntp do the timestamp. I'm running ntpd on
>vxworks. It seems to me that the receive timestamp and the Transmit
>timestamp are using two different clocks, because when I use ethereal/
>wireshark to look up the information of the ntp packet,
>the Recevie Time Stamp is: Jan
Aggie <[EMAIL PROTECTED]>
Subject: [ntp:questions] TimeStamp
To: questions@lists.ntp.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Dear all,
I'm very confused on how ntp do the timestamp. I'm running ntpd on
vxworks. It seems to
On Oct 30, 3:51 pm, [EMAIL PROTECTED] (Hal
Murray) wrote:
> >I'm very confused on how ntp do the timestamp. I'm running ntpd on
> >vxworks. It seems to me that the receive timestamp and the Transmit
> >timestamp are using two different clocks, because when I use ethereal/
> >wireshark to look up th
>> It looks like a bug in the Receive timestamp code.
>I don't know think it's a bug, because when both the server and the
>client are Windows. NTP runs perfectly fine. Just something wrong with
>VxWorks.
I was trying to suggest a bug in the vxworks receive timestamp code.
I could have misinter
Aggie wrote:
> Dear all,
> I'm very confused on how ntp do the timestamp. I'm running ntpd on
> vxworks. It seems to me that the receive timestamp and the Transmit
> timestamp are using two different clocks, because when I use ethereal/
> wireshark to look up the information of the ntp packet,
> th
