RE: SnmpTargetAddress

> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of Joan Landry
> Sent: Thursday, April 10, 2008 10:40 AM

> >>It does not, as that would be contrary to the intent of the
> snmpTargetAddrTable.  
> 
> I think that this is not true. The snmpTargetAddrTable 
> defines a tagList
> that can be used to limit the outgoing notifications and also can be
> used to limit the incoming requests.

<SNIP>
   snmpTargetAddrTable OBJECT-TYPE
       SYNTAX      SEQUENCE OF SnmpTargetAddrEntry
       MAX-ACCESS  not-accessible
       STATUS      current
       DESCRIPTION
           "A table of transport addresses to be used in the generation
            of SNMP messages."
       ::= { snmpTargetObjects 2 }
</SNIP>

	The words "generation" and "target" imply "not incoming".



> snmpCommunityTransportTag OBJECT-TYPE

	Ah!  So this is not about the snmpTargetAddrTable at all, really.  The question you wanted to ask was, "Does net-snmp support the community MIBs?"  The answer is, "Net-snmp does not support the community MIBs."  If you want to restrict the source address of v1 or v2c requests, I direct your attention again to the com2sec directive of the snmpd.conf file.  If you want actual security, I direct your attention again to v3/USM/VACM.


	HTH,

Mike

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users