From owner-freebsd-current@FreeBSD.ORG Mon Mar 31 12:13:41 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 577518E9 for ; Mon, 31 Mar 2014 12:13:41 +0000 (UTC) Received: from smtp1.redcom.com (smtp1.redcom.com [192.86.3.143]) by mx1.freebsd.org (Postfix) with ESMTP id 277F338F for ; Mon, 31 Mar 2014 12:13:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.redcom.com (Postfix) with ESMTP id 3E138AF5C; Mon, 31 Mar 2014 08:13:34 -0400 (EDT) X-Virus-Scanned: amavisd-new at redcom.com Received: from smtp1.redcom.com ([127.0.0.1]) by localhost (smtp1.redcom.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXkvRPZ0iVdj; Mon, 31 Mar 2014 08:13:31 -0400 (EDT) Received: from pie.redcom.com (pie [192.168.33.15]) by smtp1.redcom.com (Postfix) with ESMTP id 9CCC2A043; Mon, 31 Mar 2014 08:13:31 -0400 (EDT) Received: from exch-01.redcom.com (exch-01.redcom.com [192.168.32.17]) by pie.redcom.com (8.11.7p1+Sun/8.10.2) with ESMTP id s2VCDRj24574; Mon, 31 Mar 2014 08:13:31 -0400 (EDT) Received: from exch-01.redcom.com ([192.168.32.17]) by exch-01 ([192.168.32.17]) with mapi; Mon, 31 Mar 2014 08:14:26 -0400 From: "Marciano, Anthony" To: Hartmut Brandt Date: Mon, 31 Mar 2014 08:14:24 -0400 Subject: RE: Call for testers: SNMPv3 support for bsnmpd(1) Thread-Topic: Call for testers: SNMPv3 support for bsnmpd(1) Thread-Index: Ac9ME59HROPcuxnjRHuR7WirjRKCcgAxrA0Q Message-ID: <401084E5E73F4241A44F3C9E6FD794280109183637@exch-01> References: <401084E5E73F4241A44F3C9E6FD7942801091834B4@exch-01> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 31 Mar 2014 12:41:12 +0000 Cc: "freebsd-current@freebsd.org" , "tomarox52@gmail.com" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2014 12:13:41 -0000 Thanks Harti. I did get the basic V3 configuration working in that I could walk the mib u= sing authorization and encryption. If Shteryana has the time, maybe he would be able to provide me with some i= nformation needed to configure and test V3 traps. I don't have his e-mail so if you could forward this to him I would appreci= ate it. Thanks! Tony -----Original Message----- From: Hartmut Brandt [mailto:hartmut.brandt@dlr.de]=20 Sent: Sunday, March 30, 2014 8:22 AM To: Marciano, Anthony Cc: freebsd-current@freebsd.org; tomarox52@gmail.com Subject: Re: Call for testers: SNMPv3 support for bsnmpd(1) Hi Anthony, On Fri, 28 Mar 2014, Marciano, Anthony wrote: MA>I've been tasked to get bsnmpd V3 working for my company. The post=20 MA>referenced in the subject above gave me some insights but I'm still=20 MA>stuck and was wondering if you would take the time to answer some=20 MA>questions. I'm a snmpV3 newbie and have never worked with bsnmpd. I=20 MA>have worked minimally with net-snmp V2. MA> MA>First, is there a document listing all of the configuration options=20 MA>in the snmpd.confg file? It appears to differ from other packages=20 MA>such as net-snmp. I can answer only this question - I'm not very familiar with SNMPv3, but Sh= teryana should be able to help. No, there is no document with all the setting. The reason is simple: the co= nfig file is just a set of SNMP SET PDUs executed at startup, SIGHUP or mod= ule load. The file is segmented into sections by %name lines with all segme= nts having the same name beeing put together. At the begin of the file ther= e is an implicit %snmpd line. Each section is a SET PDU. The %snmpd PDU is executed on startup and SIGHUP= , all other sections are executed when the corresponding module is beeing l= oaded or on SIGHUP if that module is already loaded when the SIGHUP occures= . So any writeable or creatable MIB variable can be put into the configuratio= n file. harti