Setting contextEngineId

[D. R. Evans]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have created an SNMPv3 agent using the examples as a template. I finally 
reached the point where everything seemed to be working fine. In particular, if 
I start the agent, I can then walk the MIB and manipulate my table entries using 
the SNMP++ snmpWalk example program.

However, when a colleague tries to remotedly walk the MIB from a non-SNMP++ 
manager, he tells me:

- -----

 BUT, it appears that you are not setting the "pdu.contextEngineID" and 
"pdu.contextEngineIDlen" fields.  This would be appropriate if I were acting as 
a proxy, but I am not.  The message, therefore, is being rejected.
 
- -----

None of the examples seems to make any mention of setting the context engine, 
and I couldn't find anything in the archives. (And, as I say, snmpWalk doesn't 
seem to have any trouble walking the MIB without me having to define the 
contextEngineId explicitly.)

How do I set this so that my colleague's manager will not reject the packets?

We have agreed on the user and auth passwords, as well as the engineID (since he 
does not support discovery). He says that he can decrypt and authenticate the 
packets correctly. So I think that it is just the context Engine that is a 
problem for us now.

  Doc Evans



- ----------------------------------------------------------
D.R. Evans N7DR / G4AMJ                      N7DR at arrl.net

A dead lawyer in a Colorado ski resort and an Australian detective 
who doesn't play by the rules: 
   "All Or Nothing" is now available. 
See http://www.sff.net/people/N7DR/drevans.htp for details.
- ----------------------------------------------------------


-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60 
Comment: Key obtainable from servers: ID 0x362912B8

iQA/AwUBO9R6JWnXrLw2KRK4EQJCAACfQ+LMwAkrThJgj36GX5MQJqtQ3DQAn0XY
MSKWtYTnwWpTmnqfsfdovGcj
=nDf7
-----END PGP SIGNATURE-----