Re: config_require() Problem With MinGW

On Tue, 26 Oct 2004 23:15:15 -0400 Robert wrote: RS> On Tue, 26 Oct 2004 18:58:53 -0500 Andy wrote: RS> AS> Robert Story (Coders) wrote: RS> AS> > On Tue, 26 Oct 2004 07:38:33 -0500 Andy wrote: RS> AS> > AS> The MinGW build is broken by a call to the config_require() macro RS> AS> > AS> in interfac

Re: config_require() Problem With MinGW

On Tue, 26 Oct 2004 18:58:53 -0500 Andy wrote: AS> Robert Story (Coders) wrote: AS> > On Tue, 26 Oct 2004 07:38:33 -0500 Andy wrote: AS> > AS> The MinGW build is broken by a call to the config_require() macro in AS> > AS> interface.h. It looks like if-mib/data_access/interface_ioctl is AS> > AS> b

Re: Segmentation fault with ifXTable

On Wed, 20 Oct 2004 18:19:52 +0530 Karthikeyan wrote: KN> I am using netsnmp5.2Pre3 release in linux enviornment. I am getting the KN> following segementation fault when I run the agent (after including KN> ifXTable support): KN> KN> netsnmp_assert ((void *)0) != _ifXTable_container_get() failed K

Re: sysUptime

> On Tue, 26 Oct 2004 12:46:41 -0400, Binh Nguyen <[EMAIL PROTECTED]> said: Binh> Since sysUpTime is measured in one hundredth of a second, it Binh> will take approximately 497 days for this 32 bit counter to Binh> wrap. 497 days is not long enough because some telco equipment Binh> is let to

Re: PROXY ques: must all varbinds in a forwarded PDU belong to the forwarded-to agent?

> On Tue, 26 Oct 2004 11:50:29 +0100, Dave Shield <[EMAIL PROTECTED]> said: >> When the agent is configured to PROXY a portion of the MIB, is it >> necessary that all of the varbinds in a PDU refer to objects in the >> OID branch that the target (forwarded-to) agent is to handle? Dave> Which

Re: config_require() Problem With MinGW

I withdrawal my proposed patch. It is causing problems in other places. I am not sure why the MinGW build is failing now though, unless something was changed. /bin/sh ../../libtool --mode=compile i386-mingw32msvc-gcc -I../../include -I. -I../../agent -I../../agent/mibgroup -I../../snmplib -

Re: config_require() Problem With MinGW

Robert Story (Coders) wrote: On Tue, 26 Oct 2004 07:38:33 -0500 Andy wrote: AS> The MinGW build is broken by a call to the config_require() macro in AS> interface.h. It looks like if-mib/data_access/interface_ioctl is being AS> required unconditionally, causing Windows builds with MinGW to fail.

Mib code help

Hi, I am using the new net-snmp style for mib coding. I have created a test mib as follows: ciscoPortChannelMIB ciscoPortChannelObjects portChannelConfig portChannelTable portChannelProtocolEnable portChannelTestString On doing a walk on portChannelTestS

Files involved in CAN-2003-0935

I am working with a version of net-snmp prior to 5.0.9. The local version has a large number of local changes, so we are hesitant to attempt to upgrade to 5.0.9 or newer code (i.e. if it ain’t broke, don’t fix it). But CAN-2003-0935 is enough of an issue that we need to fix it. Can someone p

Segmentation fault with ifXTable

Hi, I am using netsnmp5.2Pre3 release in linux enviornment. I am getting the following segementation fault when I run the agent (after including ifXTable support): error finding ifTable cache could not initialize container for ifXTable netsnmp_assert ((void *)0) != _ifXTable_container_get() fai

IPv6 support

For a new platform we ar planning to support IPv6 and for snmp we plan to use net-snmp. Does net-snmp support IPv6? Thanks Srini > -Original Message- > From: Robert Story (Coders) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 19, 2004 11:33 AM > To: Srini Kode > Cc: [EMAIL PROTECTE

RE: new style of mib code

Comments inline. > -Original Message- > From: Robert Story (Users) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 26, 2004 6:55 AM > To: Srini Kode > Cc: net-snmp-users > Subject: Re: new style of mib code > > > On Mon, 25 Oct 2004 17:40:02 -0700 Srini wrote: > SK> 1) If you're wr

sysUptime

Since sysUpTime is measured in one hundredth of a second, it will take approximately 497 days for this 32 bit counter to wrap.   497 days is not long enough because some telco equipment is let to run for several years.  Am I missing something?  Are there any resolutions/workaround to lift this lim

Re: displaying IPv4-Address

On Tue, 26 Oct 2004 16:28:55 +0200 (MEST) Sven wrote: SJ> while i was working with setting and getting an IPv4 InetAddress one SJ> problem arise. SJ> SJ> But, when setting an Address like this 41.41.41.41, the result is a little SJ> bit strange: SJ> ... = STRING: "" SJ> SJ> >From my point of

Re: displaying IPv4-Address

> After setting an Address like this 192.168.143.10, i get with the > appropriate snmpget-command following result: > ... = Hex-STRING: C0 A8 8F 0A > > This is fine, because it is an InetAdressType Yup - which is represented in SNMP as a 4-element OCTET STRING. > But, when setting an Address li

displaying IPv4-Address

Hello, while i was working with setting and getting an IPv4 InetAddress one problem arise. After setting an Address like this 192.168.143.10, i get with the appropriate snmpget-command following result: ... = Hex-STRING:C0 A8 8F 0A This is fine, because it is an InetAdressType But, when setting

Re: new style of mib code

Please do not cross-post on the mailing lists. -- Robert Story; NET-SNMP Junkie Archive: You are lost in a twisty maze of little standards, all different. -

Re: config_require() Problem With MinGW

On Tue, 26 Oct 2004 07:38:33 -0500 Andy wrote: AS> The MinGW build is broken by a call to the config_require() macro in AS> interface.h. It looks like if-mib/data_access/interface_ioctl is being AS> required unconditionally, causing Windows builds with MinGW to fail. Can you be a little more spe

config_require() Problem With MinGW

The MinGW build is broken by a call to the config_require() macro in interface.h. It looks like if-mib/data_access/interface_ioctl is being required unconditionally, causing Windows builds with MinGW to fail. The attached patch fixes the problem. Anyone opposed to this patch going in? Andy ---

Re: 5.2.rc1 patch: configure adds invalid library on freebsd

> Problem > --- > A recent fix in configure.in uncovered a previous problem. A fix to > correctly determine when the dlmod module was configured into the agent > suddenly started working, What? We can't have things suddenly work when they've been broken for ages. Whatever happened to backward

Re: PROXY ques: must all varbinds in a forwarded PDU belong to the forwarded-to agent?

> When the agent is configured to PROXY a portion of the MIB, is it > necessary that all of the varbinds in a PDU refer to objects in the > OID branch that the target (forwarded-to) agent is to handle? Which PDU are you referring to? The incoming request (no), or the one forwarded to the proxie

Re: rwcommunity/rocommunity

> For my understanding, rwcommunity/rocommunity is wrap-up for > vacm's(com2c). For the full VACM config (com2sec/group/view/access), yes. > If I want a community to be able to read all MIB and only > to write a restrict OIDs, can this be done by specifying as follow: > > rocommunity public s