RE: SNMPv3 on embedded system

> From: Adrian Bica [mailto:[email protected]]

> The engineID seems to be ok (again, forcing a bad one will conduct to
some
> rejection message, good one - no message)

  Lack of an engine ID error does not equal engine ID success.  There
are many layers that the SNMPv3 traffic needs to pass before you can get
it working.  It will be very useful for you to enable debug modes on
both your agent and management applications to see exactly what's
happening.  If the agent is throwing the traffic away there is no way to
tell why other than debug mode.

  In my cases (net-snmp 5.4.1 and net-snmp 5.5) failed engine ID
verifications resulted in no error traffic.  This may be intentional to
help prevent brute force discovery of engine ID values.

  Ron



The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting all copies. Thank you.

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
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