Ilya Etingof

Hey o/ You are right! Apparently, `py-redis` operates on `bytes` on Py3, while it used to be `str` on Py2. That causes all sorts of weirdness... Let me see if...

The latest commit to master hopefully fixes this problem.

Could you share which pysnmp version you have installed and what example you trying to run?

I suspect you have taken the example from GitHub master (pysnmp 5.x.x), but installed pysnmp (4.4.10) from PyPI. Then you should take examples from [release-4.4.10](https://github.com/etingof/pysnmp/blob/release-4.4.10/examples/v3arch/asyncore/agent/cmdrsp/listen-on-ipv4-and-ipv6-interfaces.py) branch.

Just keep in mind that pysnmp 4 is stable, pysnmp 5 is still in development (though it should work).

I think the system prevents you from binding port 161 unless you are a superuser. Printer IP perhaps is a remote IP, you can only listen on local IP interfaces....

Hey, thanks for poking at me! I think the release is near! Still have a few breaking things in mind to stuff into 5.x. May be in a month. Sorry...

Hey Matt! Sorry for it is taking time... I had to partially refocus on something else lately. However, we are inevitably moving towards the better pysnmp - just look at...

Hey, I just put together a [project](https://github.com/etingof/pysnmp/projects/1) to track the items that make sense to address... The items are ordered from most desirable ones.

You do not need to prepare MIBs anyhow to let pysnmp consuming them. Do you get all the compiled MIBs in ~/.pysnmp/mibs/ ? Do you have MIB compiler piece uncommented?...