Ilya Etingof

This is curious. I suspect that may be the response is coming to/from a different IP address? Could you please add `--debug io,msgproc` to the `snmpget.py` command to see what's...

Oh, sorry for forgetting this issue! You should have pinged it! > Thanks for your reply, and I used the same ipaddress No, my suspicion is that your agent is...

I suspect you are missing some VACM configuration pieces like: ``` config.addContext(snmpEngine, '') config.addVacmUser(snmpEngine, 1, 'my-area', 'noAuthNoPriv', (), (), (1, 3, 6)) ``` Or have them configured for different user/OIDs/SNMP...

Could you please share your `pip freeze` output? Thanks!

Actually, I think that's not exactly a bug... I suspect that when you switch into a non-privileged user, you lose access to root's virtual environment. So may be the solution...

Alternatively, commit f0505c1239a3460fd2dd1a9fd841b05f14515362 should fix this issue. Let's see if it works for you so I could cut next release?

Thank you for raising this and sorry for it takes time! There is a fix in [the release candidate](https://github.com/etingof/snmpsim/tree/release-0.4.8) as well as in master to address this problem.

This may have something to do with the malformed SNMP response occasionally coming to pysnmp... To track this down I'd suggest either of: * enabling `pyasn1` debugging from pyasn1 import...

I do not see related changes in the later versions of pysnmp. And pyasn1 is up to date. So it looks like a bug in either of these packages, more...

This may have something to do with malformed Counter32 encoding. Could you please share the blob (or a piece of it) of the response message causing this? I do not...