Blog

All communications channels to Muonics (web site, phone, email) have been down for almost three weeks and I wanted to apologize for appearing to have suddenly and closed up shop with no notice.

I received notice that the lease was being terminated and was in a mad scramble to get everything physically prepared for the move and to find and secure a new lease elsewhere. By the time I was [almost] prepared, knew where things were moving to, and get moving bids, the movers had an opening for the either next day or more than a month after the lease was to terminate. Less than 24 hours was just too short of a time to have new internet services or a backup web site in place to provide notice to customers.

I had been wanting to switch ISPs for some time but was waiting for their wireless or fiber options to become available at the old place. They would not be at the new place yet either, but I decided to take the opportunity to switch anyway. Unfortunately the service they could offer now, a rebranded service from a third ISP that they could get installed a few days after the move, turned out to be an unworkable disaster. It was another week before giving up on that ISP and another week still before I could get the old service with the old ISP moved to the new location.

So, once again I apologize for the downtime and the lack of responsiveness leading up to the move. Fortunately things are finally, mostly, back online. There is still more to do and I have a fair bit of catching up to do, but hopefully things will be back to normal within a few more days.

The online ordering system was temporarily unavailable. Attempts to place an order reported an “unable to get local issuer certificate” error and would not go through. I believe the issue has been resolved, and I apologize for the inconvenience. No credit transactions were processed during the outage.

The issue stemmed from bringing up a new web server with new OS and server software versions and retiring the old one. The CA root certificate chain needed to verify the Authorize.NET SSL certificate was not installed on the new server, so it could not establish a secure connection to Authorize.NET and would not allow transactions to proceed. I was notified of the issue when a case was automatically opened in our bug tracker, and it took a bit to track down the issue.

If you have any questions or experience any other issues with the new server, please contact support.

Thank you

MIB Smithy 4.5 is now available for download. This release includes feature updates and bug fixes up through MIB Smithy SDK 4.4.3 and MIB Views 1.8.1.

4758: Recursive OID assignments can cause hang

In some cases, two OID assignments that were defined as subnodes of each other could cause an infinite loop during MIB validation. Measures were implemented to fix the cases where this could still occur.

4392: Startup crash when no physical interfaces are detectable

When no ethernet interfaces were detectable, a bad pointer when generating the message about needing a license key (that includes the list of Host IDs) could lead to a crash or corrupted error message at startup.

4393: Windows: Startup crash obtaining Host IDs under Windows 7

A buffer overrun could lead to a crash at startup when using using one of the fallback methods to obtain the list of available Host IDs (particularly, but not necessarily, under Windows 7).

4187: Duplicate sysUpTime or snmpTrapOID in translated v1 traps

The SDK translates received SNMPv1 traps into SNMPv2 format by converting the v1 trap fields into into snmpTrapOID and sysUpTime varbinds. However, if the sending agent included varbinds with these OIDs already (e.g. due to translation by proxy along the way) then multiples of these varbinds could appear. The received varbinds are now discarded in favor of the ones generated by the SDK’s translation.

4799: Trap Watch: Add support for SNMPv3 auth/priv informs

With support for receiving SNMPv3 auth/priv informs added in MIB Smithy SDK, the Trap Watch tool in MIB Smithy now supports these as well. The Trap Settings dialog that comes up to configure the listening port now has addition fields for specifying a user name, auth/priv passwords and protocols, and local snmpEngineID.

4800: Save agent settings for defaults between MIB Smithy sessions

As with MIB Views, MIB Smithy will now save SNMP agent settings (except passwords) so that they are remembered and used for defaults at the next run.

4797: TDomain/TAddress formatting in SNMP tools

Provided the appropriate MIBs are loaded, the various SNMP tools in MIB Smithy will now detect TDomain/TAddress object pairs and format the TAddress value according to the associated TDomain value (e.g. if the TDomain is snmpUDPDomain, then the TAddress will be formatted according to the SnmpUDPAddress DISPLAY-HINT). Previously the TAddress was displayed in hex, as with other unknown OCTET STRINGs.

4798: SNMP Query Tool: Adjustable panel size

The relative size of the Value entry area and the Variable List area of the SNMP Query tool can now be adjusted. At smaller window sizes, the Value entry area could become obscured and unusable, and this is an interim solution. (Longer-term plan is to redesign this tool to be more spread-sheet like, allowing data entry directly in the Variable List.)

1225: Add corner sizegrip to toplevels

The Windows and Unix versions now have size grips in the lower right corner of some windows if they’re resizable. The Mac version already displayed these.

640: Artifacts in Project Tree and MIB Browser

On Unix, expanding and collapsing branches in the Project Tree or MIB Browser could sometimes leave artifacts of what was previously displayed that would remain until the window was resized, forcing a full re-display. This was fixed with a newer version the control they’re built with.

4804: Update bundled MIBs

Bundled IETF MIBs have been updated or added from RFCs 4004 through 6672, and IANA MIBs as of 07/23/2012.

4805: parse error in hyphenated enumeration comments

In a rare corner case (one out of all the MIBs bundled), a multiply-hyphenated word in a comment following the comma after an enumeration value could cause a parse error.

4803: rfc2mib may generate wrong filename

When using the -s option to generate separate module files with rfc2mib tool (for extracting MIB/PIB modules from RFC documents), it could sometimes get confused by comments prior to the module header and use a word from the comment rather than the actual module name for the generated file name.

MIB Smithy SDK 4.4.3 is now available for Download. Changes in this release:

4804: Update bundled MIBs

Bundled IETF MIBs have been updated or added from RFCs 4004 through 6672, and IANA MIBs as of 07/23/2012.

4805: parse error in hyphenated enumeration comments

In a rare corner case (one out of all the MIBs bundled), a multiply-hyphenated word in a comment following the comma after an enumeration value could cause a parse error.

4802: Wrong contextEngineID in responses to SNMPv3 informs

The Response PDU returned to an SNMPv3 Inform Request sender was including the local Engine ID for contextEngineID, as with msgAuthoritativeEngineID, instead of the Inform sender’s. The contextName and contextEngineID in the response are now taken from the Inform Request.

4803: rfc2mib.tcl may generate wrong filename

When using the -s option to generate separate module files with rfc2mib tool (for extracting MIB/PIB modules from RFC documents), it could sometimes get confused by comments prior to the module header and use a word from the comment rather than the actual module name for the generated file name.

MIB Smithy SDK version 4.4 is now available for download. This release includes the following changes, which will be incorporated into new MIB Smithy and MIB Views releases shortly:

274: Alphabetize command options

The list of command options given in error messages when a bad option is given is now alphabetized to make it easier to figure out the correct option. They’ve also been alphabetized in the SDK documentation.

530: Add APIs for configuring local Engine ID

A -localengid session configuration option was added in an earlier SDK release, but was not used for anything. The option can now be used to configure the actual snmpEngineID value for the session for when the session is the authoritative engine (i.e., when receiving SNMPv3 inform requests).

3778: Fat Binaries for Mac OS X

Fat binaries (PPC and x86 32-bit) for the SDK are now available.

531: Add SNMPv3 Inform Support

Support for receiving and responding to SNMPv3 inform requests at all security levels is now supported. Previously inform requests could be sent with SNMPv3, but could only be received with SNMPv2c.

4719: Add support for SNMPv3 context name/engine ID

Added -ctxname and -ctxengineid session configuration and message generation options for specifying SNMPv3 contextName and contextEngineID. If -ctxengineid is empty (default), contextEngineID will be the same as msgAuthoritativeEngineID, which was the prior behavior.

4728: Default local SNMP Engine ID assignment

The session’s -localengid value was previously defaulted to an empty string. Sessions are now assigned a unique partially-random Engine ID at creation time or can be assigned the same Engine ID. (The non-random component is based on the Muonics enterprise number and Product ID, per the SnmpEngineID TEXTUAL-CONVENTION). Persistence to non-volatile storage is left to the user to implement as they wish.

4657: Allow local interface selection for traps

A -localaddress session configuration option was added to specify the IP address of a local interface to bind to for receiving notifications. The default (empty string) indicates that notifications should be received on all applicable interfaces, which was the previous behavior.

4720: Add option to configure remote Engine ID

A -engineid session configuration option was added to configure the remote SNMP Engine ID (the one authoritative for request PDUs), primarily to hook into the Tnm compatibility. The value configured will be changed in response to a usmStatsUnknownEngineIDs report from the agent, however.

4758: Recursive OID assignments can cause hang

In some cases, two OID assignments that were defined as subnodes of each other could cause an infinite loop during MIB validation. Measures were implemented to fix the cases where this could still occur.

4392: Startup crash when no physical interfaces are detectable

When no ethernet interfaces were detectable, a bad pointer when generating the message about needing a license key (that includes the list of Host IDs) could lead to a crash or corrupted error message at startup.

4393: Windows: Startup crash obtaining Host IDs under Windows 7

A buffer overrun could lead to a crash at startup when using using one of the fallback methods to obtain the list of available Host IDs (particularly, but not necessarily, under Windows 7).

4187: Duplicate sysUpTime or snmpTrapOID in translated v1 traps

The SDK translates received SNMPv1 traps into SNMPv2 format by converting the v1 trap fields into into snmpTrapOID and sysUpTime varbinds. However, if the sending agent included varbinds with these OIDs already (e.g. due to translation by proxy along the way) then multiples of these varbinds could appear. The received varbinds are now discarded in favor of the ones generated by the SDK’s translation.

4464: Code audit for Tcl_Obj leaks

A thorough code audit was done to check for any leaks of allocated Tcl_Obj values and several were fixed. In general, the ones that were found only occurred when an API call resulted in an error (e.g. allocating an empty Tcl_Obj for the non-error result that was not discarded before returning an error). Since Tcl holds onto the memory for discarded Tcl_Objs for later reuse, though, and the error would likely be due to a script error to be corrected, the impact was negligible.