This is my final chapter on this topic.
Replacing snmpTargetAddrRowStatus.\`testTarget\`
with
.1.3.6.1.6.3.12.1.2.1.9.\'testTarget\'
also works when running on the ARM target.
Other experiments I've now run have ruled out b), leaving only c) as the
culprit (from previous post).
I will conside
An interesting update to this. With the ARM target's agent logging some
debug, I see that it is happily digesting
snmpTargetAddrRowStatus.\'testTarget\` (for example) as OID
.1.3.6.1.6.3.12.1.2.1.9.116.101.115.116.84.97.114.103.101.116 from the
snmpset running on the Fedora host.
On the ARM t
Does your snmdp.conf use 'agentaddress udp:161' to set the listening port?
Having snmpd also listening on TCP 161 is mostly benign, but it looks like you
don't have the correct option set.
-
Jim
- Original Message - Subject: SNMP is listening on the wrong
transport protocol
Hi All,
In response to an earlier question of mine asking for clarification of
whether AES 128 was supported Bill Fenner said:
AES128 support is described in RFC3826, and SHA2 support is described in
RFC7630.
...
Yes, when the tools refer to AES, they are referring to AES as described in
RFC382
