aakansha rajvi wrote:
I am Installing net-snmp 5.2.1 under windows in VC++ environment.
Output of nmake is as follows..
cl.exe /nologo /MD /W3 /GX /O2 /I "." /I ".." /I "..\..\snmplib" /I "..\
.." /I "..\..\include" /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /Fp".\rel
ease\lib
Hi,
I'm trying to use the perl-module.pl reference to get a few more fields
inserted for HP-UX. I don't know much Perl, but I'm able to guess my way
through Perl syntaxes and what not. The weird thing is, the default
perl-module.pl won't load:
./sar-snmp.pl
starting perl_module.pl
perl_mod
While I was playing with net-snmp, my agentx client crashed
at send() in netsnmp_tcp_send.
Can anyone provide a clue on what this file is:
../sysdeps/unix/sysv/linux/powerpc/powerpc32/socket.S:87
is it a file generated by net-snmp or a file provided
by my OS?
I am running agentx as subagent on p
Hi Dave,
That piece of code(lines 196-198) is generated by mib2c.
In fact, besides the change mentioned in your email, there is another change needs to be done inside memcpy.
I have verified the following code works correct.
rowreq_ctx->data.historyControlDataSource_len =
h
hi,
i'm a complete newbie to net-snmp. i try to compile it since yesterday but
there is always the same error:
make: *** No rule to make target 'winservicerc.lo', needed by
'libnetsnmp.la' . Stop.
make[1]: Leavingdirectory '/cygdrive/d/net-snmp/snmplib'
make: *** [subdirs] Error 1
I use win
Hi,
Can you please comment on adding this check to
snmp_pdu_parse() of snmp_api.c in snmplib/ directory?
Regards,
Saif
--- Dave Shield <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-08-10 at 02:14 -0700, Austin Schutz
> wrote:
> > So.. was the original question regarding
> sub-identifiers
I am Installing net-snmp 5.2.1 under windows in VC++ environment.
I Initialized the environment using VCVARS32.bat
and executed win32/build.bat. But the operation failed.
I installed Active State Perl too.
Output of nmake is as follows..
.." /I "..\..\include" /I "..\..\agent" /I "..\..\agen
On Wed, 2005-08-10 at 02:14 -0700, Austin Schutz wrote:
> So.. was the original question regarding sub-identifiers,
> or bytes?
Subidentifiers.
> I have seen objects in the wild with greater than 128 bytes,
Yes - that's perfectly legal
> but not 128 sub-identifiers.
and that's not.
>
On Wed, Aug 10, 2005 at 08:44:22AM +0100, saifulla Mohd Abdul wrote:
>
> Hi,
>
> Yes, we don't need to process request with
> OID (sub-id count more than 128).
>
> RFC 3416 says:
>
>SNMP limits OBJECT IDENTIFIER values to a maximum
> of 128 sub-identifiers, where each sub-identifier has
>
Andre Schneider wrote:
I want to change the snmpdemoapp so I can set a value instead of getting
one. I read several times in this mailing-list something of a demo
application file called apps/snmpset.c - where can I find this file?
Or can someone send me a little demo of setting a mib-value with
hello,
I want to change the snmpdemoapp so I can set a value instead of getting
one. I read several times in this mailing-list something of a demo
application file called apps/snmpset.c - where can I find this file?
Or can someone send me a little demo of setting a mib-value with a
C-Program?
On Tue, 2005-08-09 at 14:47 -0500, [EMAIL PROTECTED] wrote:
> Hi Robert,
>
> Using the patch you sent me on 7/25, I still have problem with mib2c
> generated OID type such as historyControlDataSource. See the snmpwalk
> result below, the populated oid length is 4 times of it should be.
>
> $ snmp
On Mon, 2005-08-08 at 15:40 -0700, Fong Tsui wrote:
> What mib2c conf file(s) should be used for creating full RMON
> and RMON2 code?
That probably doesn't matter too much.
With many MIBs (and particularly with RMON), the hardest aspect
is working out how to retrieve the necessary information that
On Wed, 2005-08-10 at 09:41 +0530, toby sebastian wrote:
> i have already run netsnmp in linux 2.4 kernel (32 bit os).
> now i want to run the same in linux 2.6 kernel.
> What all changes or configurations need to be done in order
> to run this in 2.6 kernel.
You shouldn't need to make any confi
Hi,
Yes, we don't need to process request with
OID (sub-id count more than 128).
RFC 3416 says:
SNMP limits OBJECT IDENTIFIER values to a maximum
of 128 sub-identifiers, where each sub-identifier has
a maximum value of
2**32-1.
Any PDU with an OID having More than 128
sub-identifiers is
15 matches
Mail list logo
