I have observed that net-snmp does not support snmpCommunityTable of RFC > 3584(SNMP-COMMUNITY-MIB), though the data related to this is maintained > in local memory. > Is there any particular reason that this is not supported.
Because no-one has implemented this particular MIB. The equivalent functionality (i.e. "com2sec" handling) was actually written *before* the SNMP-COMMUNITY-MIB first appeared, and there hasn't been a pressing need to re-work this to use the more standard approach. It's been on my list for a while, but other tasks have tended to come first. If you're in a position to address this, and can feed back the necessary changes, we'd be delighted to incorporate them into the main Net-SNMP code base. > Please let me know if I am missing anything with related to dealing with > snmpCommunityTable. The main thing to realise is that the snmpCommunityTable covers slightly *more* than the com2sec settings do - in particular a community string will be mapped to a (name/engineID/context) triple rather than simply a security name. And you'd have to use the snmpTargetTable (plus snmpCommunityTransportTag) to handle the source address filtering. But other than that, it shouldn't be too difficult to implement. Dave ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id149&alloc_id66&op=click _______________________________________________ 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
