I compiled this code and set snmpd.conf to pass an oid to the resulting
executable. My /tmp/foo.txt shows the program has executed when I do an
snmpget, but the snmpset output is the usual output.
prompt:
snmpset -c private -v1 localhost enterprises.40 i 5
output:
SNMPv2-SMI::enterprises.40 =
[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. T
> When I do:
> enterprises.myBranch.main.myTable.myEntry.myIndex.5
> snmpset -v1 -c private -m all localhost .1.3.6.1.4.1..1.4.1.1.5
>
> myIndex does have a STATUS of 'read-only'.
But the core agent driving code doesn't know that.
It's up to the "subagent" (i.e. the pass-script) to reject
an
/etc/snmp/snmpd.conf:
rocommunity public
rwcommunity private
pass_persist .1.3.6.1.4.1..1 /home/bob/agent.py
When I do:
enterprises.myBranch.main.myTable.myEntry.myIndex.5
snmpset -v1 -c private -m all localhost .1.3.6.1.4.1..1.4.1.1.5
myIndex does have a STATUS of 'read-only'.
The snmpd tr
