Re: udpTable byte order issues (again)

On Thu, 22 Jun 2006, Wes Hardaker wrote: It's not that simple, I'm afraid. Much of the time it's also how the structures used by the kernel store them. I'm pretty sure that some systems are storing them in host order and others in network order, which means you sometimes need to apply htonl a

Re: linkup linkdown monitoring impacts the performance

On Tue, 28 Feb 2006, David T. Perkins wrote: HI Peder Chr. Norgaard, I believe we pretty are much in agreement that what was done in many of the access routines and event reporing routines in NET-SNMP can and should be updated. The note was to help other readers with understanding that the

Re: linkup linkdown monitoring impacts the performance

On Fri, 24 Feb 2006, David T. Perkins wrote: > HI, > > I'm concerned a little over the use of different terms > that mean essentially the same thing, since this may confuse > many people. That is, I've seen "alarm", "alert", etc. > > In all cases, it appears to me, that you are trying > to find an

Re: linkup linkdown monitoring impacts the performance

On Fri, 24 Feb 2006, Robert Story wrote: > > On Fri, 24 Feb 2006 10:29:31 +0100 (CET) Peder wrote: > PCN> If you work on a system with "netlink" support (a linux system, for > PCN> instance) and don't shrink from a bit of C coding you can make a solution > PCN> that gives the alarms immediately, a

RE: linkup linkdown monitoring impacts the performance

On Fri, 24 Feb 2006 [EMAIL PROTECTED] wrote: > Date: Fri, 24 Feb 2006 15:28:18 +0530 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Cc: net-snmp-coders@lists.sourceforge.net > Subject: RE: linkup linkdown monitoring impacts the performance > > > Hi Peder, > > Could you plea

Re: linkup linkdown monitoring impacts the performance

On Fri, 24 Feb 2006, Dave Shield wrote: > On Fri, 2006-02-24 at 13:59 +0530, [EMAIL PROTECTED] wrote: > > > monitor -r 5 -e linkUpTrap "Generate linkUp" ifOperStatus != 2 > > monitor -r 5 -e linkDownTrap "Generate linkDown" ifOperStatus == 2 > > > Since this set-up makes frequently so man

Re: Endian - ness issue

On Mon, 24 Oct 2005, Dave Shield wrote: > > On Mon, 2005-10-24 at 11:01 -0400, Robert Story wrote: > > On Mon, 24 Oct 2005 14:01:44 +0100 Dave wrote: > > DS> > I do agree with Peder on shared IPv4/IPv6 storage as a char array (and > > DS> > that's what I did for the data access functions for the M

Re: Endian - ness issue

I have been following the endianness discussion with some interest, having been bitten myself by the problems when I had to implement a MIB table with IpAddress in the index. I have studied the current implementation and must agree that any solution is complex and not something you wish to do imme

Re: 5.2.2.pre3 on Debian

On Thu, 6 Oct 2005, Thomas Anders wrote: > Peder Chr. Norgaard wrote: > > > > What I did was to pick up the Debian-related patches from a recent > > packaging that the Debian maintainer of net-snmp, Jochen Friedrich, made > > to Debian experimental. It was based on CVS

Re: Unable to implement trap

On Thu, 6 Oct 2005, Krishna Mohan wrote: There is an excellent example in the tutorial - worked right out of the box for me. best regards -- Peder Chr. Nørgaard Senior System Developer, M. Sc. Ericsson Denmark A/S, Te

5.2.2.pre3 on Debian (was: [ net-snmp-Bugs-1313667 ] snmpd crashes ...)

This discussion is not really related to the bug in which it popped up, therefore I just take it to the mailing list. I wrote in bug report comment: > No, I have not tried it with newer software. I tried, but > the libtool/aclocal/autoconf/configure sequence did not > work on my system, and I am

Re: snmpd crash when master agentx and informs (possibly related to bug #1154117)

On Sat, 1 Oct 2005, Robert Story wrote: > On Sat, 24 Sep 2005 18:11:16 +0200 (CEST) Peder wrote: > PCN> The crash happens shortly after a subagent has sent a notification > PCN> that must be forwarded as an inform. The crash only happens when the > PCN> receiver is not responding, so the inform

snmpd crash when master agentx and informs (possibly related to bug #1154117)

Hello. My snmpd agent have started crashing on me; I spent some time figuring out how and why. I think I know that now - but not how to solve it. My problem may be related to the bug 1154117 in the bug database. The behaviour is not identical, however. Version is Debian

Re: Problem combining alarms and snmp_select_info - and a possible solution

On Mon, 12 Sep 2005, Wes Hardaker wrote: > > Peder> run_alarms(); > > Whoops. I just noticed that you put that into the library function. > I read the code too fast and assumed you put it in your code instead. > > What you should do is put a call to that function inside *your* select > loop. It

Problem combining alarms and snmp_select_info - and a possible solution

Hello coders. Using net-snmp 5.2.1.2, the Debian Linux distribution, to build an Agent-X sub-agent I discovered that the ping monitoring and reattachment logic did not work. Closer investigation disclosed that this was related to my use of snmp_select_info instead of agent_check_and_proces

"Error in ipCidrRouteTable" or "Endianness of IpAddress is a mess"

Hello, net-snmp-coders. I am a newbie to net-snmp, but definitely not to SNMP agent development as such; I have been working with SNMP agents for 15+ years. I was asked to whip together an agent that supports the (not-yet-released-from-IETF) OSPFV3-MIB using the net-snmp agent API. Trying t