Hi All,
Updated engine-id is not being re-read after sending SIGHUP to snmpd.
I am performing a snmpwalk with '-e' engine-id. After changing the
engine-id and sending a SIGHUP to snmpd, I was expecting snmpwalk with the
previous engine-id to fail while snmpwalk with the updated engine-id to be
suc
problem.
Thanks,
Abhishek Singh
agent_usm.patch
Description: Binary data
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
Hello,
I have a question on the format how oldEngineID is stored in snmpd.conf.
After configuring an engine ID, I observed the oldEngineID in snmpd.conf
saved as
*engineBoots 1oldEngineID
0x80001f880438303030623835633033653030373162633735333532*
The question is why the oldEngineID is stored in A
