Simon,
The USM AES192 and AES256 support is based upon an Internet Draft, which
never became a standard - therefore, you have to pass
"--enable-blumenthal-aes" to ./configure. (You don't have to enable TSM or
the TLS transports; that's a whole different kettle of fish.)
Bill
On Fri, Apr 6, 20
net-snmp developers,
Please join us for an IRC chat on #newguard at freenode.net on April
12 5:30 AM PDT/6:30 AM MDT/7:30 AM CDT/8:30 AM EDT/12:30 PM UTC for a
meet-and-greet with ICEI's newguards who wants to contribute to the
net-snmp project.
Looking forward to chatting with you guys.
Thanks,
Hi Simon,
Hope you're doing well.
These weird looking messages are actually representation of the data that
is sent from an snmpd agent to a sub-agent or vice versa.
Generally, when I'm starting my snmpd agent's binary I use the following
command:
*./snmpd -d -Lo -f -c /{Path_to_snmp.conf}/snmp
On 04/06/2018 11:33 AM, Keith Mendoza wrote:
After going through the list, we feel that any bugs created before
2012 Nov 8 should just be closed/dropped at this point. That way we
can focus our efforts on working on bugs that are left after that
date.
I can explain the reasoning behind /this/
net-snmp dev team,
Ian and I went through another round of going through the bug lists
for ones that we feel can either be closed, or placed in WONTFIX:
* 1989, 2490, 2101, 1765, 2554: These have proposed patches that
doesn't appear to have been applied.
* 2438: Fixed in patch 1249, which is merge
Thanks for the tip.
I did compile with the following options:
--disable-embedded-perl
--without-perl-modules with_endianness=big
--enable-mini-agent
--with-default-snmp-version="3"
--enable-ipv6
--disable-debugging
--with-sys-contact="who@where"
--with-logfile="/va
