From: John Tafasi (johntafasi@yahoo.com)
Date: Tue Dec 03 2002 - 19:50:26 GMT-3
yes this is true, thank you for the reply.
Tafasi
----- Original Message -----
From: "P729" <p729@cox.net>
To: "John Tafasi" <johntafasi@yahoo.com>; "ccielab" <ccielab@groupstudy.com>
Sent: Tuesday, December 03, 2002 12:56 PM
Subject: Re: ntp stateless packet
> Just as a friendly suggestion, try checking the RFCs, for example RFC 1305
> (NTP V3). A brief scan of it reveals the following:
>
> "The service can operate in a symmetric mode, in which servers and clients
> are indistinguishable, yet maintain a small amount of state information,
> or in client/server mode, in which servers need maintain no state other
than
> that contained in the client request."
>
> The mode 3 in the packet from 10.10.10.2 indicates it is operating in
client
> mode:
>
> "Client (3): A host operating in this mode sends periodic messages
> regardless of the reachability state or stratum of its peer. By operating
in
> this mode the host, usually a LAN workstation, announces its willingness
to
> be synchronized by, but not to synchronize the peer."
>
> The mode 4 in the packet to 10.10.10.2 indicates server mode:
>
> "Server (4): This type of association is ordinarily created upon arrival
of
> a client request message and exists only in order to reply to that
request,
> after which the association is dissolved. By operating in this mode the
> host, usually a LAN time server, announces its willingness to synchronize,
> but not to be synchronized by the peer."
>
> So you're certainly running in client/server mode, which by definition is
> stateless.
>
> Regards,
>
> Mas Kato
> https://ecardfile.com/id/mkato
> ----- Original Message -----
> From: "John Tafasi" <johntafasi@yahoo.com>
> To: "Cisco Group Study" <cisco@groupstudy.com>; "ccielab"
> <ccielab@groupstudy.com>
> Sent: Monday, December 02, 2002 9:49 PM
> Subject: ntp stateless packet
>
>
> Hi group,
>
> Below is the output of debug ntp packets on my router. It show that the
> router is sending ntp stateless packets. Why is that? What it means? When
> will the router send stateless packet?
>
>
>
> Dec 2 22:43:12.909: NTP: rcv packet from 10.10.10.2:
> Dec 2 22:43:12.909: leap 0, mode 3, version 3, stratum 9, ppoll 64
> Dec 2 22:43:12.913: rtdel 08B1 (33.951), rtdsp 0077 (1.816), refid
> 0A0A0A01 (10.10.10.1)
> Dec 2 22:43:12.913: ref C1966040.F259C10C (22:42:08.946 UTC Mon Dec 2
> 2002)
> Dec 2 22:43:12.917: org C1966049.0FCC1B7E (22:42:17.061 UTC Mon Dec 2
> 2002)
> Dec 2 22:43:12.921: rec C1966049.13E7D9BE (22:42:17.077 UTC Mon Dec 2
> 2002)
> Dec 2 22:43:12.921: xmt C1966080.E4581349 (22:43:12.891 UTC Mon Dec 2
> 2002)
> Dec 2 22:43:12.925: inp C1966080.E8FD727C (22:43:12.910 UTC Mon Dec 2
> 2002)
>
>
> Dec 2 22:43:12.929: NTP: stateless xmit packet to 10.10.10.2:
> Dec 2 22:43:12.933: leap 0, mode 4, version 3, stratum 8, ppoll 64
> Dec 2 22:43:12.933: rtdel 0000 (0.000), rtdsp 0002 (0.031), refid
7F7F0701
> (127.127.7.1)
> Dec 2 22:43:12.937: ref C196607F.0FC1FFAC (22:43:11.061 UTC Mon Dec 2
> 2002)
> Dec 2 22:43:12.937: org C1966080.E4581349 (22:43:12.891 UTC Mon Dec 2
> 2002)
> Dec 2 22:43:12.941: rec C1966080.E8FD727C (22:43:12.910 UTC Mon Dec 2
> 2002)
> Dec 2 22:43:12.945: xmt C1966080.EE2232A6 (22:43:12.930 UTC Mon Dec 2
> 2002)
> r2-2516#show debug
> NTP:
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:38 GMT-3