Re: Issue in snmpv2 walk while filling handler context name( netsnmp_handler_registration_create->contextName)

On Fri, 23 Sep 2016 14:13:52 + Sridhar wrote: LS> I am new to Netsnmp, I adding the context support . LS> LS> I am facing issue in snmpv2 walk , If I filling the context Name LS> during the registration table . I am not able do the walk for register LS> table , It only access

Issue in snmpv2 walk while filling handler context name( netsnmp_handler_registration_create->contextName)

Hi , I am new to Netsnmp, I adding the context support . I am facing issue in snmpv2 walk , If I filling the context Name during the registration table . I am not able do the walk for register table , It only accessible in context based walk , So what I need to add , for support the default

setting a context name to the default mibs in snmpd

Hi, Is there a way to compile/set a context name to the mibs (i.e. snmpEngine, usmUser, etc...) that are compiled within the agent (snmpd) code by default? >From the code, I can see they are compiled with a null context n

RE: Using Context-Name in Snmpv3 returns Authorization Error

nal access line and tried. But same timeout happens. > proxy -Cn context-name -v 3 -u V3User -a md5 -A "Password" -l authnopriv > localhost .1.3.6.1 >Hmmm... you are taking any requests received for .1.3.6.1 (with the >specified context) >and passing them back to th

Re: Using Context-Name in Snmpv3 returns Authorization Error

tant bits. > After reading the man page for snmpd.conf I modified the file as below > createUser V3User MD5 "Password" > > com2sec –Cn context-name V3User default community Not relevant (see above) > group v3_group usm V3User > view v3_view included .1.3.6.1 >

RE: Using Context-Name in Snmpv3 returns Authorization Error

>> How can I properly configure the context name on the server side? >See the section covering "rouser" and "rwuser" in the snmpd.conf(5) man page - >this comes in the section headed "Traditional Access Control" >(or the description of "acces

Re: Using Context-Name in Snmpv3 returns Authorization Error

On 19 July 2012 11:08, wrote: > I have an application which worked perfectly in SNMpv3 in AuthnoPriv mode. > There is a requirement like a “context name” is to be added to the snmp > requests which is sent by the application. > I have only one snmpd server which sends responses

Using Context-Name in Snmpv3 returns Authorization Error

Hi, I have an application which worked perfectly in SNMpv3 in AuthnoPriv mode. There is a requirement like a "context name" is to be added to the snmp requests which is sent by the application. So I have filled the contextName and contextNameLen in netsnmp_pdu with the proper va

Re: Context Name

On 2 November 2011 14:50, Jordan Kagan wrote: > Can anyone tell me where the interface to  "Context Name" within the > Net-SNMP library is located?  This is what can be changed using the -n flag > via the command line. >From snmplib/snmp_parse_args.c: case &#

Context Name

Greetings, Can anyone tell me where the interface to "Context Name" within the Net-SNMP library is located? This is what can be changed using the -n flag via the command line. Thank you, Jordan -- RSA® Confe

Help regarding context name

context name to the netsnmp_handle_request() ? -- Thanks and Regards, VENU -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and

Context-name Help

Hi, Can net-snmp perl module be used to support the multiple instances of same MIB(scalar)? I want to implement the Bridge MIB which is designed for one bridge to support multiple bridges. Can I get some pointers to make the basic net-snmp (C module) support dynamic context names OR any way to s

Re: Help regarding context name

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

Re: Help regarding context name

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

Re: Help regarding context name

h the error message unknown token defContextName. > > The defContextName tells the *management* side of the snmp library which > default context name to use when sending *requests* to an agent. And it > should go into the "snmp.conf" file instead (note the missing "d&q

Re: Help regarding context name

the defContextName directive. DS> It fails with the error message unknown token defContextName. The defContextName tells the *management* side of the snmp library which default context name to use when sending *requests* to an agent. And it should go into the "snmp.conf" file inst

Help regarding context name

ister_handler(reg); reg = netsnmp_create_handler_registration(.); reg->contextName = strdup("my_context"); netsnmp_register_handler(reg); Do I need to have as many handlers as my posiible context Names? Second Can I have my context name changing dynamically when agent is running? Any

RE: Passing context name and Engine ID in Request

t: Re: Passing context name and Engine ID in Request On 28/08/07, <[EMAIL PROTECTED]> wrote: > Do we need to configure "context Name" and "context Engine" somewhere > in snmpd.conf or it is automatically done for snmpv3 by Net-SNMP If you want to use a non-default

RE: Passing context name and Engine ID in Request

It seems good, I'm working on it to confirm. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: 2007年9月4日 17:33 To: [EMAIL PROTECTED] Cc: [email protected]; [EMAIL PROTECTED] Subject: Re: Passing context name and E

Re: Passing context name and Engine ID in Request

On 28/08/07, <[EMAIL PROTECTED]> wrote: > Do we need to configure "context Name" and "context Engine" somewhere > in snmpd.conf or it is automatically done for snmpv3 by Net-SNMP If you want to use a non-default context, then yes - this needs to be configured.

Passing context name and Engine ID in Request

Hello, Do we need to configure "context Name" and "context Engine" somewhere in snmpd.conf or it is automatically done for snmpv3 by Net-SNMP I have added following lines in snmpd.conf for authentication : defSecurityName abc defAuthTypeMD5 defSecurity

Configuring contextEngineId and Context Name

Hello, Do we need to configure "context Name" and "context Engine" somewhere in snmpd.conf or it is automatically done for snmpv3 by Net-SNMP I have added following lines in snmpd.conf for authentication : defSecurityName abc defAuthTypeMD5 defSecurity

Re: [PATCH] Allow wildcard context name

On Thu, 29 Sep 2005 10:17:46 +0300 Pantelis wrote: PA> Here's an updated version of the patch, that does just that. I strongly recommend submitting this to the patch tracker so it doesn't get lost. Unless someone who's reviewed it wants to check it in right away (he said, looking over at Wes)...

Re: [PATCH] Allow wildcard context name

Wes Hardaker wrote: On Wed, 28 Sep 2005 13:00:10 +0300, Pantelis Antoniou <[EMAIL PROTECTED]> said: Pantelis> The following small patch allows a wildcard context "*" be used. Pantelis> That way an agent/proxy that responds to a large number of contexts Pantelis> can be used in a more lightweig

Re: [PATCH] Allow wildcard context name

> On Wed, 28 Sep 2005 13:00:10 +0300, Pantelis Antoniou <[EMAIL PROTECTED]> > said: Pantelis> The following small patch allows a wildcard context "*" be used. Pantelis> That way an agent/proxy that responds to a large number of contexts Pantelis> can be used in a more lightweight manner.

[PATCH] Allow wildcard context name

Hi all The following small patch allows a wildcard context "*" be used. That way an agent/proxy that responds to a large number of contexts can be used in a more lightweight manner. Regards Pantelis PS. This is my first net-snmp patch, so if it's a stupid idea, I don't mind being told :)

Re: how to send context name in a v3 trap

On Thu, 2005-08-18 at 13:23 +0530, madanagopal wrote: > Since i am going to do all this as a module part > of agent, should i create a new session and open it everytime for sending > a new trap. Having created a session, there's no need to re-open it for each trap. Just use

Re: how to send context name in a v3 trap

On Sat, 11 Dec 2004, Wes Hardaker wrote: > > On Tue, 16 Nov 2004 18:37:56 +0530 (IST), madanagopal <[EMAIL > > PROTECTED]> said: > > If it is the case, can i do the following steps to send a v3 trap with > different contexts: > > 1. Create a session using snmp_sess_init(session) and fill

Re: Context name in SNMP Proxy

On Mon, 18 Jul 2005 17:46:39 +0530 Ravi, wrote: RRS> I came across a proxy configuration in Net-Snmp's snmpd.conf file and it RRS> reads as RRS> RRS> proxy [-Cn CONTEXTNAME] [SNMPCMD ARGS] HOST OID [REMOTEOID] RRS> RRS> What is this CONTEXTNAME and how it is configured. Can somebody explain RRS>

Context name in SNMP Proxy

Hi All, I came across a proxy configuration in Net-Snmp's snmpd.conf file and it reads as proxy [-Cn CONTEXTNAME] [SNMPCMD ARGS] HOST OID [REMOTEOID] What is this CONTEXTNAME and how it is configured. Can somebody explain briefly how to configure this CONTEXTNAME? Thanks in Advance. Regards, R

Re: how to send context name in a v3 trap

madanagopal> trapsess line in snmpd.conf. But i want to send different > madanagopal> context name for different traps. How to set the context > madanagopal> name for each trap from agent? > > I don't think that's possible to do at this point (but is a good point). >

Re: how to send context name in a v3 trap

e in snmpd.conf. But i want to send different madanagopal> context name for different traps. How to set the context madanagopal> name for each trap from agent? I don't think that's possible to do at this point (but is a good point). -- Wes Hardaker Sparta

how to send context name in a v3 trap

hai, I want to send a v3 trap from agent. So i am using send_v2trap(). I have defined v3 parameters using trapsess line in snmpd.conf. But i want to send different context name for different traps. How to set the context name for each trap from agent