Folks, Maybe the user mailing list was not the right place for this. I will file a bug about the following, if nobody explains otherwise.
The -e option in trapsess (snmpd.conf) sets the contextEngineID. This is easily observable using tcpdumps. The -E option in trapsess also sets the contextEngineID. This goes against the snmpcmd manual page where -e sets the authoritative security engineID. There is no way to set that value in a trapsess statement in 5.4.1 and also 5.5. In contrast to this, the snmptrap utility uses the -e and -E parameters correctly. What I would like to know is, is this bug not very important in the field in actual customer use ? I mean, can it be that users are simply not caring much about that in general ? Thanks. ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
