[AGENT++] Problem with SNMPv3 Traps

[Jochen Katz]

Hi Philippe,

>  I use "add_v3_trap_destination()" function and I define a MD5DES user,

just in case you didn't fix the function already:
for (int i=0; i<addr.get_length()-2; i++) {
              ^^^

> then, when I send the request with "Mib::notify()" the agent remains blocked
> during about 1 minute (in EventListHolder::SNMPBlockForResponse() ).

One minute is the result of a timeout (3 retries and 15 seconds timeout).

>  I used Ethereal to see traffic, there are an INFORM request of emitted, and
> a response of REPORT's PDU type with an Authoritative Engine ID and a
> Context Engine ID.

Obviously the agent does not accept the response, but then you should
see the retries. Do agent and manager have different engine ids? What do
the log messages say? You can get much more logging messages through
DefaultLog::log()->set_filter() and if you define _DEBUG at compilation
of snmp++/agent++.

> The traces are in enclosure

They didn't make it to through mailman...

Regards,
  Jochen