On Tue, 2005-12-06 at 11:26 +0200, Andrei Pisau wrote: > Also, I have tried the latest release 5.3.pre5 and I have > problems when sending all kind of alerts. Even v1 TRAP or > V2c TRAP or INFORM are not logged, snmptrapd receives them > but some way, it discards them after some VACM checks.
Yes - the 5.3 release will require explicit access configuration for the trap handler to accept traps. > I am using the simple configuration with > ro/rwcommunity in snmpd.conf. Is that not supported anymore? > Should I use only com2sec, group &co ...? No - this is nothing to do with your 'snmpd.conf' settings. What you'll need is similar entries in your 'snmptrapd.conf' file - something along the lines of authcommunity log,execute,net public We'll document this properly before 5.3 is fully released. Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users