Hi ,
We are trying to support a single MIB implementation for multiple virtual
devices.
Since contextName are loaded from the configuration file, and in
handle_snmp_packet() function will do all the access checks for it.
is there any way to disable that check for ContextName and forward the
cont
My intention wasn't the demand for dynamic context names.
On Thu, Aug 27, 2009 at 12:59 PM, Dave Shield wrote:
> 2009/8/26 Deepali Singalkar :
> > When is the support for dynamic context names expected?
>
> When someone writes the necessary code.
>
> Remember, this project is effectively
2009/8/26 Deepali Singalkar :
> When is the support for dynamic context names expected?
When someone writes the necessary code.
Remember, this project is effectively a part-time hobby for most
of those involved with it. All of the core developers have other
(paid) employment, and this mu
Thanks for clarification!
When is the support for dynamic context names expected?
On Wed, Aug 26, 2009 at 10:47 PM, Wes Hardaker <
harda...@users.sourceforge.net> wrote:
> > On Wed, 26 Aug 2009 12:53:01 +0530, Deepali Singalkar <
> deepali.singalk...@gmail.com> said:
>
> DS> Here I n
> On Wed, 26 Aug 2009 12:53:01 +0530, Deepali Singalkar
> said:
DS> Here I need to support same MIB tree for multiple virtual devices from same
DS> subagent.
DS> I tried setting the contextname in /usr/local/share/snmp/snmpd.conf file
DS> with the defContextName directive.
DS> It fails w
Hi,
I am develoing a AgentX subagent for virtual devices.
Here I need to support same MIB tree for multiple virtual devices from same
subagent.
I tried setting the contextname in /usr/local/share/snmp/snmpd.conf file
with the defContextName directive.
It fails with the error message unknown token
