On Thu, 2010-10-14 at 11:24 +0530, Shibu George wrote:
> Hi Frnds,
>
> I'm using netsnmp in Agent-Subagent mode. Whenever I run my subagent
> (with snmpd running) following error comes which repeats for more than 100
> times:
>
> registering pdu failed: 263!
> registering pdu failed:
Hi Frnds,
I'm using netsnmp in Agent-Subagent mode. Whenever I run my
subagent
(with snmpd running) following error comes which repeats for more than
100
times:
registering pdu failed: 263!
registering pdu failed: 263!
registering pdu failed: 263!
registering pdu failed: 263!
register
> On Wed, 13 Oct 2010 22:41:25 +0200, Magnus Fromreide
> said:
MF> One big drawback is that AC_AUTOCONF_VERSION was introduced in 2.62
MF> so any releases with a requirement below that can't use this.
Yep, that's one of the reasons I went with the other way (at least for
the older branc
Is this patch reasonable or just plain stupid?
Index: configure.ac
===
--- configure.ac(revision 19427)
+++ configure.ac(working copy)
@@ -11,7 +11,8 @@
# Process this file with autoconf to produce a configure script.
> On Wed, 13 Oct 2010 19:28:01 +0200, Magnus Fromreide
> said:
MF> Is it a good test case? Should I commit it?
I like it!
We should, however, put it in a new test directory called "package" or
something for package related tests.
--
Wes Hardaker
Please mail all replies to net-snmp-c
On Wed, 2010-10-13 at 09:58 -0700, Wes Hardaker wrote:
> > On Wed, 13 Oct 2010 17:23:04 +0100, Dave Shield
> > said:
>
> DS> Though there is still the question of why these APIs are using
> DS> "struct netsnmp_transport_s"
> DS> in the first place, rather than
> DS> "ne
> On Wed, 13 Oct 2010 17:23:04 +0100, Dave Shield
> said:
DS> Though there is still the question of why these APIs are using
DS> "struct netsnmp_transport_s"
DS> in the first place, rather than
DS> "netsnmp_transport "
DS> (which is the naming style used for all other s
On Wed, Oct 13, 2010 at 2:00 PM, Magnus Fromreide wrote:
> On Wed, 2010-10-13 at 09:58 +, [email protected] wrote:
> > Revision: 19421
> >
> http://net-snmp.svn.sourceforge.net/net-snmp/?rev=19421&view=rev
> > Author: bvassche
> > Date: 2010-10-13 09:58:34 + (Wed, 13 Oc
On 13 October 2010 17:16, Wes Hardaker wrote:
> BF> I updated net-snmp to 5.6, and all of my net-snmp consumers broke. It
> BF> looks like (included from
> BF> accidentally used "netsnmp_transport *"
> BF> instead of "struct netsnmp_transport_s *":
> Also, I bet if you had included net-snmp/t
Hello,
snmplib/cert_util.c contains the following code:
[ ... ]
/** add certificate type mapping */
se_add_pair_to_slist("cert_types", strdup("pem"), NS_CERT_TYPE_PEM);
se_add_pair_to_slist("cert_types", strdup("crt"), NS_CERT_TYPE_DER);
se_add_pair_to_slist("cert_types", strdup(
BF> I updated net-snmp to 5.6, and all of my net-snmp consumers broke. It
BF> looks like (included from
BF> accidentally used "netsnmp_transport *"
BF> instead of "struct netsnmp_transport_s *":
Hi Bill!
Though I think your patch is fine, I find it odd that you're the only
person that has hit
On 13 October 2010 17:03, Wes Hardaker wrote:
>>> Could you please confirm If snmpwalk/ get support AES 256 protocol?
>
> DS> Yes - any vaguely recent version (5.1 or above) should include AES
> DS> support.
>
> Actually, no. Net-SNMP implements the standard which uses AES128, not AES256.
Oops
The Net-SNMP project contains a fair amount of code and we're actually
embarking on optionally removing parts of it for small devices. But
this work won't be ready for a year or so.
However, the package doesn't require much in terms of external libraries
for base working support. You'll likely
> On Wed, 13 Oct 2010 08:50:59 +0100, Dave Shield
> said:
>> Could you please confirm If snmpwalk/ get support AES 256 protocol?
DS> Yes - any vaguely recent version (5.1 or above) should include AES
DS> support.
Actually, no. Net-SNMP implements the standard which uses AES128, not AE
You're almost certainly going to need to run it in a debugger... Some
useful information on doing so can be found at:
http://www.net-snmp.org/wiki/index.php/Debugger
--
Wes Hardaker
Please mail all replies to [email protected]
-
On Wed, 2010-10-13 at 09:58 +, [email protected] wrote:
> Revision: 19421
> http://net-snmp.svn.sourceforge.net/net-snmp/?rev=19421&view=rev
> Author: bvassche
> Date: 2010-10-13 09:58:34 + (Wed, 13 Oct 2010)
>
> Log Message:
> ---
> CHANGES: Cygwin: Ru
With Linux on x86(_64) hardware I get a bad netmask from the ipCidrRouteTable:
$ snmpwalk -OX localhost:6161 ipCidrRouteTable
IP-FORWARD-MIB::ipCidrRouteDest[0.0.0.0][0.0.0.0][0][172.18.0.1] = IpAddress:
0.0.0.0
IP-FORWARD-MIB::ipCidrRouteDest[169.254.0.0][0.0.255.255][0][0.0.0.0] =
IpAddress: 1
On 13 October 2010 11:10, Tapan Kanta Mishra (tamishra)
wrote:
> I Install openSSL but facing same issue
Have you recompiled the code to make use of OpenSSL?
Dave
--
Beautiful is writing same markup. Internet Explorer 9
I Install openSSL but facing same issue
Here is my test result
C:\>openssl
OpenSSL>
C:\>snmpwalk -v3 -l authPriv -u XXaccessXX -a SHA -A pyZPp2u\"al -x aes
-X Priv_
3245frMP#443$$ 10.104.149.184 sysName.0
Invalid privacy protocol specified after -x flag: aes
USAGE: snmpwalk [OPTIONS] AGENT [OID]
On 13 October 2010 09:40, Tapan Kanta Mishra (tamishra)
wrote:
> No sure If I did include OpenSSL
>
> I'm using Windows XP, Do you have any document to do that.
See README.win32
Dave
--
Beautiful is writing same markup.
No sure If I did include OpenSSL
I'm using Windows XP, Do you have any document to do that.
Thanks
Tapan Mishra
High Touch Technical Services (HTTS)
HTTS Toll Free +1 800 495 9121
Working Hours - Sunday to Thursday, 5:30 AM to 1:30 PM IST (GMT +5:30)
-Original Message-
From: dave.shi
Hi Dave,
I did try in winxp but result is different, here is my syntax
snmpget -v 3 -u teaccesskk -l authPriv -a SHA -A hhjajjsa -x aes -X
asadaswa sysUpTime.0
Invalid privacy protocol specified after -x flag: aes
USAGE: snmpget [OPTIONS] AGENT OID [OID]...
Version: 5.5.pre2
Web:
On 13 October 2010 09:28, Tapan Kanta Mishra (tamishra)
wrote:
> I did try in winxp but result is different, here is my syntax
>
> snmpget -v 3 -u teaccesskk -l authPriv -a SHA -A hhjajjsa -x aes -X
> asadaswa sysUpTime.0
>
> Invalid privacy protocol specified after -x flag: aes
> USAGE: snm
On 13 October 2010 05:25, Tapan Kanta Mishra (tamishra)
wrote:
> Could you please confirm If snmpwalk/ get support AES 256 protocol?
Yes - any vaguely recent version (5.1 or above) should include AES support.
> Version: 5.0.9
The 5.0.x line is long obsolete, and no longer being supported
Pl
Dear Support,
Could you please confirm If snmpwalk/ get support AES 256 protocol? If
not when can I expect this to work.
This is what I'm getting result If I issue "snmpget" syntax
Invalid privacy protocol specified after -x flag: aes256
USAGE: snmpwalk [OPTIONS] AGENT [OID]
Ver
Hi,
I want to port net-snmp on texas instruments DSP board. What is a minimal
source code which i should port on my board. Does project snmpd contain all
source code I need or I need some library. My plan is to first port v1 and
v2c snmp version. I saw that that snmp v3 require open ssl, which wil
26 matches
Mail list logo
