From owner-freebsd-current Mon May 27 23:52:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA06388 for current-outgoing; Mon, 27 May 1996 23:52:55 -0700 (PDT) Received: from ki.net (root@ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA06381; Mon, 27 May 1996 23:52:52 -0700 (PDT) Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id CAA29517; Tue, 28 May 1996 02:52:54 -0400 (EDT) Date: Tue, 28 May 1996 02:52:53 -0400 (EDT) From: "Marc G. Fournier" To: Gary Palmer cc: current@FreeBSD.ORG, wollman@FreeBSD.ORG Subject: Re: snmp for FreeBSD... In-Reply-To: <8798.833263973@palmer.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 28 May 1996, Gary Palmer wrote: > "Marc G. Fournier" wrote in message ID > : > > clean sources: ftp.ece.ucdavis.edu:/pub/snmp/ucd-snmp.tar.gz > > diff against: ftp.ki.net:/pub/users/scrappy/ucd-snmp.3.1-diffs.gz > > First impressions ... it doesn't work (properly). I couldn't get the > client s/w to work (perhaps I was driving it wrong, I'll look at that > later), so I used the tkined snmp interface to check out the snmpd. > The "No version" error? I've found *where* the problem is, just can't figure out *why*...am looking into that one now, since I don't know tkined :( > First thing that happened (on a default MIB walk, nothing special at > all) was that the daemon went into an infinite loop trying to figure > out how many TCP connections are open. Not QUITE sure why, as gdb > attaching to the process seems to make the error go away, though it there are a few bugs like that, actually...the above "No version" error with the clients is "fixed" by putting a printf() at line 1009 in snmplib/snmp_api.c (wasn't in my patch, since it was a kludge until I had a little more time to look at it...ie. tonight) > If this WAS brought in ``officially'' I'd probably like to see some > kernel changes made to better accomodate SNMP queries. The following > output is from a hacked up version of the daemon, patches being sent > to Marc under separate cover. > Realizing the the snmpd itself still needs work, the kernel changes that you are suggesting...would be required regardless of which snmpd was used? I still have alot to learn about snmp, but I don't want to waste time trying to fix one snmpd package to work with FreeBSD if we're going to end up ditching it for something else :( Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org