Request for data / ntpsnmpd report

Mark Atwood, Project Manager mark.atwood at ntpsec.org
Thu Feb 1 17:22:20 UTC 2018


The SNMP MIB RFCs are notorious for including magic blue sky values and
measurements that nobody knows how to measure and that are not well defined.

For things that don't make enough sense, it's ok to not implement that
particular snmp variable.

As for the "Check if ntpd configuration changed", that appears to me to be
a good example of "poorly defined".  "When did this host get a new IP
number" is better retrieved from one of the system MIBs.   It's okay to not
implement it.

..m

On Tue, Jan 9, 2018 at 7:26 AM Ian Bruene via devel <devel at ntpsec.org>
wrote:

>
> I have nearly finished filling out the MIB tree for SNMP. What gaps are
> left involve data I do not know how to get:
>
> * Time Resolution (not to be confused with Time *Precision*, which is one
> of the first entries I implemented)
>
> * Time Distance
>
> * Validation for the TestSet sequence. According to the RFC this is one of
> the most complicated parts of an agent to get right. Currently it is setup
> to be failsafe, which we can get away with for now because the NTP MIB only
> has two writable entries, and simple ones at that.
>
> * Check if ntpd configuration changed. The description listed in the RFC
> is: "The notification to be sent when the NTP configuration has changed,
> e.g., when the system connected to the Internet and was assigned a new IP
> address by the ISPs DHCP server.". But I do not know the full extent of
> what to check, or how to do so.
>
> There are other issues, but they mostly have to do with refactoring and
> robustifying the code. The ones I am listing here require input from
> someone else.
>
> --
> *"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 at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel

-- 

Mark Atwood
http://about.me/markatwood
+1-206-604-2198 Mobile & Signal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20180201/fd12b353/attachment.html>


More information about the devel mailing list