From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 06:06:18 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 400B433C; Tue, 1 Apr 2014 06:06:18 +0000 (UTC) Received: from mailhost.dlr.de (mailhost.dlr.de [129.247.252.33]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mailhost.dlr.de", Issuer "DLR CA - G02" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C445113C; Tue, 1 Apr 2014 06:06:17 +0000 (UTC) Received: from DLREXHUB01.intra.dlr.de (172.21.152.130) by dlrexedge02.dlr.de (172.21.163.101) with Microsoft SMTP Server (TLS) id 14.3.174.1; Tue, 1 Apr 2014 08:06:14 +0200 Received: from KNOP-BEAGLE.kn.op.dlr.de (129.247.178.136) by smtp.dlr.de (172.21.152.151) with Microsoft SMTP Server (TLS) id 14.3.174.1; Tue, 1 Apr 2014 08:06:13 +0200 Date: Tue, 1 Apr 2014 08:06:09 +0200 From: Hartmut Brandt X-X-Sender: brandt_h@KNOP-BEAGLE.kn.op.dlr.de To: "Marciano, Anthony" Subject: RE: Call for testers: SNMPv3 support for bsnmpd(1) In-Reply-To: <401084E5E73F4241A44F3C9E6FD79428010918381C@exch-01> Message-ID: References: <401084E5E73F4241A44F3C9E6FD7942801091834B4@exch-01> <401084E5E73F4241A44F3C9E6FD794280109183637@exch-01> <401084E5E73F4241A44F3C9E6FD79428010918381C@exch-01> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Cc: "Bjoern A. Zeeb" , "syrinx@FreeBSD.org" , "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: Tue, 01 Apr 2014 06:06:18 -0000 On Mon, 31 Mar 2014, Marciano, Anthony wrote: MA>Currently, we are just looking to monitor standard objects such as MA>interfaces and send traps accordingly. Would it be possible to provide MA>a trap example of what needs to be added to the snmpd.config file to MA>monitor an object and have it sent via V3? MA> MA>I've searched for this information and read through various RFCs but MA>have not discovered any bsnmpd specific trap syntax and/or examples. Well, bsnmp can send only the standard traps currently. This is configured via the begemotTrapSinkTable (/usr/share/snmp/mibs/BEGEMOT-SNMPD.txt). Each row in the table is a trap target and all traps are sent to all targets in the table. I don't know, how this interacts with v3, though. harti