Snmpget with v3 AuthPriv unresponsive on Vendor's Device about sharpsnmplib HOT 6 CLOSED

Since the last posting, we've collected more data with Lextm.SharpSnmpLib and other tools to verify if the end bytes would be the same or different.

When referring to the end bytes, we're referring to the bytes in the red box of the screenshot below:

For what tools we used, we used NET-SNMP and pysnmp-lexstudio/snmpclitools-lextudio.

Here are the results:

Upon request, we can provide the rest of the wireshark screenshots of the results.

from sharpsnmplib.

Hello @lextm,

I noticed you've added the tag for more info needed, but I am not clear of what information you need at this time.

If you provide me with what you need, I'll do my best to provide you with that information.

Thank you.

from sharpsnmplib.

Hello @lextm,

Could you let us know what information that you need? We could then try to gather that data for you.

Thank you.

from sharpsnmplib.

Is there an update on this issue? I am seeing the same issue with my product. I can communicate to my device with the python library, but when I use the C# library, it fails.

from sharpsnmplib.

Initial analysis indicates that this is a compatibility issue around AES paddings, so it impacts on certain devices that dislike extra paddings.

We expect to ship a new release in the coming weeks once we restore our CI/CD system back to normal.

from sharpsnmplib.

Apologizes, I meant to comment instead of closing with comment.

from sharpsnmplib.