> From: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] On
> Behalf Of Dave Shield
> Sent: Tuesday, April 06, 2010 3:17 AM
> Mike - do you wish to comment further?
I just think the OP should quit screwing around in the dark. RFC3414,
section 4 explains how to get an engineId from any engine. A non-engine has no
engineID, so that solves itself. There is no need to attempt to invent one's
own protocol. The authoritative engine for an inform is the sending engine, so
discovery is unnecessary. What problem is OP trying to solve that can't be
handled by just using the existing net-snmp code?
Mike
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
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
