Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)

2018-02-14 Thread James Browning via devel
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

Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)

2018-02-14 Thread Hal Murray via devel
  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

Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)

2018-02-14 Thread Ian Bruene via devel
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

Re: ntpEntStatPktModeTable.... what is it? (NTPv4-MIB)

2018-02-13 Thread Hal Murray via devel
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.