What I configured in snmpd.conf file
*engineID 8000b85c03d0672649a01e*
NetSNMP converted the above engineID in to equivalent Hex value for each
character, i.e (8000b85c03d0672649a01e => 38 30 30 30 62 38 35 63 30 33 64
30 36 37 32 36 34 39 61 30 31 65) with some prefix *0x80001f8804*
*snippet:*
Abhishek Singh writes:
> 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 1
> oldEngineID 0x80001f880438303030623835633033653030373162633735333532
>
> The question is why t
Craig Small writes:
> Debian net-snmp packages 5.9.3-1 have also been built and uploaded.
Nice, thanks.
--
Wes Hardaker
Please mail all replies to net-snmp-coders@lists.sourceforge.net
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourcefor
On Thu, 14 Jul 2022 at 07:42, Wes Hardaker via Net-snmp-coders <
net-snmp-coders@lists.sourceforge.net> wrote:
>
> So a 5.9.3 release has now been pushed to:
>
Debian net-snmp packages 5.9.3-1 have also been built and uploaded.
No major issues, I'm hoping to reduce some of the patches I'm carrying
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
