12, 2011 5:21 PM
> To: Lewis Adam-VNQM87
> Cc: net-snmp-users@lists.sourceforge.net
> Subject: Re: Limiting ip addresses which have access to SNMP agent
>
> On 12 April 2011 16:57, Lewis Adam-VNQM87
> wrote:
> > does anyone know if there is a standard MIB which allows you to
Hi,
does anyone know if there is a standard MIB which allows you to
configure the list of IP addresses which have access to an agent?
I'm guessing there isn't because we should probably be relying on either
the community string or the auth/priv combination to control access, but
I just thought I
Hi, I just wanted to check what was the recommended latest stable
release. It looks like 5.6.1 but if you click on , the webpage:
http://sourceforge.net/projects/net-snmp/files/net-snmp/5.6.1/ shows the
slightly misleading message :
Looking for the latest version? Download net-snmp-5.4.4.pre1.z
Does anyone have any experience in what is judged to be acceptable agent
behaviour when you use ifAdminStatus to disable the very interface you
are using to talk to the agent? The description in RFC 2863 3.1.13 seems
to hint at it being implementation-specific. I guess the 2 main choices
are:
1. re
I tried both the -e and -E options (in addition to the -Z option) and
the result is the same:
A noAuthNoPriv request will cause just the reply to the request to be
generated.
A authNoPriv/authPriv request will cause an additional exchange where
the agent (correctly) first sends usmStatsNotInTim
I'm doing some testing and am trying to avoid the "discovery exchange"
which commands like snmpget, snmpgetnext, etc use to get the engine ID,
engineBoots, & engineTime.
I set the -Z option which is accepted but when I look at the wireshark
trace, I can see the first packet still gets sent with
m
WH> The right thing to do is actually to follow the instructions
WH> in RFC3416 which describes in detail what to do for requests
WH> to objects that aren't supported in some way. (in
WH> particular, I refer to section 4.2.5 all the time for SET handling).
Thanks Wes, RFC3416 does provide clea
I have a 'multi-lingual' snmp agent, capable of sending SNMPv1 & SNMPv2
traps. I was just trying to work out what varbindings should be sent
with, say, a v2 coldstart trap. Currently we send:
sysUpTime.0
snmpTrapOID.0
snmpTrapEnterprise.0
We suspect that snmpTrapEnterprise.0 should not be include
Just to give some context to what I am doing: basically, we are looking
to use a cut-down version of the net-snmp agent code as one of many
tasks running on an embedded platform. The platform has a number of
interfaces, some of which (currently) cannot be controlled via SNMP.
What I was trying to w
Thanks Ron.
I had a rummage through the net-snmp support for the interface mib but I
couldn't see much in the way of exception handling or cross-checking
with the value of ifOperStatus. Lots of "TODO" comments lurking in
there. Maybe it's regarded as an implementation-specific design decision
but
Hmmm, no replies.
As a matter of interest, can anyone tell me whether the question was too
dumb, not appropriate for this forum, so incredibly clever it's beyond
the scope of this forum, ...
Better still, if anyone knows where I could get an answer, it would be
much appreciated.
Regards,
Adam.
just wondering if anyone had any advice on how to handle a request to
set ifAdminStatus up when the condition of the unit meant the operation
could not currently be supported (e.g. ifOperStatus = notPresent).
1. Do we allow the ifAdminStatus to be set but happily ignore it
(according to rfc 2863, s
Thanks Dave. That's pretty much what I thought.
> -Original Message-
> From: dave.shi...@googlemail.com
> [mailto:dave.shi...@googlemail.com] On Behalf Of Dave Shield
> Sent: Tuesday, April 06, 2010 8:04 PM
> To: Lewis Adam-VNQM87
> Cc: net-snmp-users@lists.source
recently checking a proprietary MIB with a MIB validator used by an SNMP
Manager, I got the following error:
ERR-166 For newly-defined conceptual rows which allow the creation of
new
object instances and/or the deletion of existing object instances,
there should be one columnar object with
To: Lewis Adam-VNQM87
> Cc: net-snmp-users@lists.sourceforge.net
> Subject: Re: mib2c generation of snmpNotifyFilterTable code
>
> 2010/1/13 Lewis Adam-VNQM87 :
> > Okay, thanks again. I may well speak to the -coders. It
> seems a shame
> > to have gone to the effort of
t: Wednesday, January 13, 2010 3:10 PM
> To: Lewis Adam-VNQM87
> Cc: net-snmp-users@lists.sourceforge.net
> Subject: Re: mib2c generation of snmpNotifyFilterTable code
>
> 2010/1/13 Lewis Adam-VNQM87 :
> > Are the mib2c scripts purely for the benefit of creating new
> >
dnesday, January 13, 2010 1:43 PM
> To: Lewis Adam-VNQM87
> Cc: net-snmp-users@lists.sourceforge.net
> Subject: Re: mib2c generation of snmpNotifyFilterTable code
>
> 2010/1/13 Lewis Adam-VNQM87 :
> > Looking at the files that combine to provide support for the
> > snmpN
Looking at the files that combine to provide support for the
snmpNotifyFilterTable:
agent\mibgroup\notification\snmpNotifyFilterTable.c
agent\mibgroup\notification\snmpNotifyFilterTable_data_access.c
agent\mibgroup\notification\snmpNotifyFilterTable_interface.c
etc.
I can see that these f
Looking at version 5.5 of the net-snmp suite ... in
agent\mibgroup\notification\snmpNotifyTable.c, the function
send_notifications() has the lines [251 .. 255] :
if (send && sess->paramName) {
int filter = _checkFilter(sess->paramName, template_pdu);
if (filter)
send = 0;
> From: dave.shi...@googlemail.com
> [mailto:dave.shi...@googlemail.com] On Behalf Of Dave Shield
> Sent: Tuesday, December 08, 2009 10:14 AM
> To: Lewis Adam-VNQM87
> Cc: net-snmp-users@lists.sourceforge.net
> Subject: Re: vacm_getAccessEntry() doesn't look for best mat
Hi,
I'm having trouble with multiple vacm access table entries associated
with a given vacm group.
Looking at version 5.5 of the net-snmp suite (although I believe the
problem has existed for many previous versions), in snmplib\vacm.c, the
function vacm_getAccessEntry() just gets the first entry
21 matches
Mail list logo
