-Coders,
when using 5.1.2.pre2 as a client against a 5.0.9 agent on Linux (Debian Woody), I recently ran into two (possibly related) problems:
1. The agent (uptime 268 days) suddenly started to answer all (previously working) SNMPv3 authPriv requests with a SNMP REPORT indicating an usmStatsNotInTimeWindows error, even if we use latest 5.1.2.pre2 as the client. Does this ring a bell with anyone? USM engine time is ~21.700.000, currently. Did I cross a magic boundary?
2. The 5.1.2.pre2 command-line tools (e.g. snmpget) handle this situation quite badly: after sending the request seven times (and getting the REPORT response each time), they hang in select() forever :( The agent responses *do* arrive at the client (as "snmpget -Ddump" shows).
Restarting the agent will possibly fix the first issue (as it did for an agent on another machine) and hide the second, but I'd really prefer to track this down instead. Consequently, I can only turn on "-Dtoken" debugging on the client, not on the agent.
Suggestions are highly appreciated.
+Thomas
-- Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
