Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snmpsim snmpsim-command-responder doesn't work for SET requests #164

Open
itzikya opened this issue Jan 13, 2025 · 1 comment
Open

Snmpsim snmpsim-command-responder doesn't work for SET requests #164

itzikya opened this issue Jan 13, 2025 · 1 comment
Labels
bug Something isn't working priority:low Low priority items. triage New issues that need to be sorted out.

Comments

@itzikya
Copy link

itzikya commented Jan 13, 2025

Expected behavior

SET should have performed, and the new value should recieved.

Actual behavior

But a bug happened like this, I get this response: "No Such Instance currently exists at this OID" although this OID exists, and GET operation works fine and retrieves the value

Detailed steps

The steps are, i ran the sim like this:
snmpsim-command-responder --agent-udpv4-endpoint=127.0.0.1:16100 --v3-user=user --v3-auth-proto=SHA --v3-auth-key=0123456789 --v3-priv-proto=AES128 --v3-priv-key=1234567890 --logging-method=stdout:DEBUG

Python package information

6.2.6

Operating system information

linux (centos)

Python information

3.10.5

(Optional) Contents of your test script

No response

Relevant log output

snmpget -v3 -l authPriv -u user -A 0123456789 -X 1234567890 -a SHA -x AES128 -n user 127.0.0.1:16100 1.3.6.1.4.1.16215.1.1.1
SNMPv2-SMI::enterprises.16215.1.1.1 = INTEGER: 42

snmpset -v3 -l authPriv -u user -A 0123456789 -X 1234567890 -a SHA -x AES128 -n user 127.0.0.1:16100 1.3.6.1.4.1.16215.1.1.1 i 20
SNMPv2-SMI::enterprises.16215.1.1.1 = No Such Instance currently exists at this OID
@itzikya itzikya added bug Something isn't working triage New issues that need to be sorted out. labels Jan 13, 2025
@lextudio-support lextudio-support added the priority:low Low priority items. label Jan 13, 2025
@lextudio-support
Copy link

New issues are marked as low priority by default. Becoming our commercial customers, and then your reports are handled with higher priority after triage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority:low Low priority items. triage New issues that need to be sorted out.
Projects
None yet
Development

No branches or pull requests

2 participants