SNMPv3 Engine ID Discovery problem

[joeclarkia]

I am trying to use the MibbleBrowser from 2.10.1 to do SNMP GETs from a Net-SNMP agent. I know the SNMPv3 configuration, except "Context Name" and "Context Engine" are a mystery to me, so I'm leaving them blank. The first time I do a GET request from a particular IP, all is well and I get the answer I'm looking for. However, after that first GET, I get this error:

GET: Error: Engine ID discovery: Timed out

Is this a Mibble issue? Westhawk issue? User issue?

[cederberg]

The Westhawk stack should auto-discover and handle the context engine I think. Seems something is broken there in version 6.1 of the stack that is currently used by Mibble. Or perhaps the API has changed in some way. Will have to investigate this a bit.

[joeclarkia]

I am using 2.10.1 and am seeing a similar problem. I am also leaving the Context fields empty, and the first Get I do is fine, but after that, I see this:

GET: Error: Context can no longer be used, since it is already destroyed

The only way I can find to reset this condition is to restart Mibble. Question is: Is this a bug in the Westhawk stack, or a problem with how Mibble is using the Westhawk API?

[joeclarkia]

Just revisiting this issue... any new thoughts on it?

[fer-marino]

ping. From 2017 to 2025 and we are still here

[cederberg]

The Westhawk stack is no longer maintained and the MibbleBrowser is a demo app (with full source code available for anyone to modify).

A fix for this issue will be considered for the next version of Mibble, but there are no current plans.