On Mon, 14 Jan 2008, Mike Ayers wrote: >> I am writing a MIB module for some specific piece of hardware. Some of >> my code needs to return values that are already available from >> standard MIB modules. > > Then you should not need to return those values - the consuming > application can get them from their authoritative sources.
But then the application has to first get the name of the interface involved and then look up the data in the interfaces table and I sought to reduce the overhead for the application. > It is and isn't possible. There is no provision for sharing MIB > information inside an agent, and security planning demands that it not > be possible without access control. That is understandable. > There is a simple workaround, though, which is to have a USM > username/password (secure the password!) as part of the MIB > information, which the MIB uses to query 127.0.0.1 for the needed > information. The v3 security keeps the agent locked down while your > MIB gets the data it needs. It's probably a good idea to have a port > number in that tuple, too, just in case the agent must be run on an > off-port. This sounds like I would have to follow the steps described in the "Writing aa Simple Application" tutorial to get to the data from within my module? I just wonder if this is also the application field of the AgentX stuff and if it would pay off to use it here. TNX manfred ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
