Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)
> IIRC there never was a mode 0. ... Thanks for the history. There isn't a counter for that case, but I have seen it in the mrulist printout. Or thought I did, I can't find an example now so I was probably thinking of something else. I do see a lot of version 2 requests. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)
On Wed, Feb 14, 2018 at 12:46 PM, Hal Murray via devel wrote: > I think we answer mode 0 as a client mode. It's probably some legacy > stuff. > IIRC there never was a mode 0. In NTP0 those bits were reserved and set to 0. Mode bits did not show up until NTP1. Before that the effective mode was was partially port based and partially contextual. Which is to say 123->!123 was server mode; !123->123 was client mode; and 123->123 varied. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)
symetricactive(1), symetricpassive(2), client(3), server(4), broadcastserver(5), broadcastclient(6) Those are close to the "mode" field in the packet. client and server are mode 3+4. symetricactive and symetricpassive are "peer, modes 1+2. We don't send symetricactive mode any more and don't process symetricpassive. We do answer a symetricactive with a symetricpassive - legacy. (I think.) We don't support broadcastclient. We do support broadcastserver - legacy. >From include/ntp.h #define MODE_UNSPEC 0 /* unspecified (old version) */ #define MODE_ACTIVE 1 /* symmetric active mode */ #define MODE_PASSIVE2 /* symmetric passive mode */ #define MODE_CLIENT 3 /* client mode */ #define MODE_SERVER 4 /* server mode */ #define MODE_BROADCAST 5 /* broadcast mode */ I think we answer mode 0 as a client mode. It's probably some legacy stuff. There should be counters, but I can't find them via ntpq or in the code. It should be simple to just add the counters, but that area is tangled up with a pile of stuff that I want to rip out. The receive packet processing goes through a double indexed table. So I vote we punt on this for a while. We should put it on the issue list as a reminder. If somebody thinks this is important, I'll take another look. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)
On 02/13/2018 04:23 PM, Hal Murray wrote:
devel@ntpsec.org said:
From the possible values of ntpEntStatPktMode it would appear that the
"modes" this table is talking about are not the normal NTP communication
modes like mode6.
What are the possibilies?
From the MIB:
ntpEntStatPktMode OBJECT-TYPE
SYNTAX INTEGER {
symetricactive(1),
symetricpassive(2),
client(3),
server(4),
broadcastserver(5),
broadcastclient(6)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The NTP packet mode."
::= { ntpEntStatPktModeEntry 1 }
--
/"In the end; what separates a Man, from a Slave? Money? Power? No. A
Man Chooses, a Slave Obeys."/ -- Andrew Ryan
/"Utopia cannot precede the Utopian. It will exist the moment we are fit
to occupy it."/ -- Sophia Lamb
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)
devel@ntpsec.org said: > From the possible values of ntpEntStatPktMode it would appear that the > "modes" this table is talking about are not the normal NTP communication > modes like mode6. What are the possibilies? -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
