2009/1/12 Dana Burns <[email protected]>: > com2SecList suffers from being transport-domain specific. > I believe it should be moved to snmplib/snmp_transport.c and > made tdomain-neutral.
I agree. Most other transport-related configuration uses a standard prefix-based syntax for specifying transport-specific addresses. It would be sensible for com2sec to work in the same way. > Actually, the 3 existing flavors of com2SecEntry > should be replaced with an snmpCommunityEntry defined by the > coexistence mib (rfc 3584). In an ideal world, I'd agree. Unfortunately, the functionality supplied by the snmpCommunityTable isn't sufficient to match that provided by the existing com2sec (and related) tokens. We'd actually need to extend this table to support the current behaviour. It's been on our ToDo list for some time, but this additional functionality is a major reason why it hasn't been tackled yet. Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
