Wes Hardaker

It now looks like the certificate is properly working, so this bug can be closed as someone did something so it works now ! Thank you.

I don't know when it was first set up. Many many years ago. Note that www.net-snmp.org is pointed at 204.68.111.101, but net-snmp.org was not because the sourceforge system only supported the www instance in the past. I've changed net-snmp.org to point directly to sourceforge's 204.68.111.101 address now if that helps. (sorry for the delay ... travelling for a conference)

Net-SNMP web certificate has invalid common name

Just to be clear, this looks like it only affected V5-8-patches and newest code. IE, 5.8.0 was actually already clear from this bug, correct?

I suspect that drive is super slow in returning information. Can you try running snmpwalk with a long timeout? IE, try -t 30

You likely have a configuration file or a enviromental variable that doesn't include those MIBs by default. Do you have a "mibs" configuration line in your snmp.conf file by chance that doesn't have a "+" in front of the value? IE, this: mibs +HOST-RESOURCES-MIB says to add the mib to the list, where as this: mibs HOST-RESOURCES-MIB says to completely replace the list with just that MIB. The MIBS environmental variable works in a similar way.

snmptrapd ignores msgAuthoritativeEngineBoots and msgAuthoritativeEngineTime for v3 traps

Closing per discussion in #2899 (warning: carefully analyzing remote boots/times values for traps and informs may result in a splitting headache...)