Mar/29 2011 - version 0.8.6

In the last couple of moths, majority of comments posted have been spam and for that reason I have disabled comment functionality of the site. To post comments, bugs or other notices, please use SourceForge project page. -MilanS

I would like to thank Jozsef Horvath for discovering, reporting and providing a fix for an issue related to encoding of specific unsigned integer values used by Gauge32, Counter32, etc. variable types derived from UInteger32 base type.

Fix for the issue will be included in the version 0.7.5 scheduled for release tomorrow.

I am in the process of migrating the web site from static html and WordPress to drupal based Content Management System.

In the past I have found it time consuming and boring to post content to the web site. Split between the blog and the documentation site has not worked out very well and there has been some documentation.

The plan is to 1) consolidate the information in one place, 2) allow for it to be easily available, and 3) make it easier for me to post content.

I have tried to migrate all registered user accounts from the WordPress blog. If you are having trouble with your login, please reset your password.

I have changed the layout of the download packages. From version 0.6 binary, source and documentation downloads will be posted under snmpsharpnet package. Old snmpsharpnet-doc and snmpsharpnet-src packages have been hidden and are no longer accesible. If you need an older version of the SnmpSharpNet library, feel free to contact me on dev [at] snmpsharpnet [dot] com and I will make version you require available again.

I have released library version 0.6 that introduces AES-192 and AES-256 privacy protocols.

I have held off for a long time on implementing the high encryption AES protocols because I didn’t have anything to test my implementation against.

Just had an interesting time testing TRAP and INFORM handling with SNMP version 3 using net-snmp snmptrap utility.

Here is the summary of what I have learned over the last week and what the testing has confirmed.

SNMP Traps are handled like a response to a query. You get a packet, parse it using USM information for the specific agent and presto, you’ve got the notification information.