On 02/10/06, Jean-Sebastien Morisset <[EMAIL PROTECTED]> wrote: > I've been using the "rocommunity" directive, but had to use the whole > com2sec/group/access/view thing to exclude virtual interaces.
> If anyone can suggest an alternative to exclude > virtual interfaces on Solaris, I'd appreciate any tips. The upcoming 5.4 release will support the application of named views to the convenience access control directives. So it should be possible to set up the necessary view using view read excluded interfaces.ifTable.ifEntry.ifIndex.3 view read excluded interfaces.ifTable.ifEntry.ifIndex.4 view read excluded interfaces.ifTable.ifEntry.ifIndex.5 view read excluded interfaces.ifTable.ifEntry.ifIndex.6 (or whatever) and then apply this to a particular community name: rocommunity readCommunity default -V read That avoids needing to invoke the full com2sec/group/access setup. Note that this is new in 5.4, and won't work in any earlier releases. I'd also tend to suggest that you use different names for the community, group and view tokens. The agent won't care, but it can get confusing if you use the same name for all three, as to exactly what is being referred to at any point. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
