Dave, The problem is this: the contextEngineId that what I receive from the agent's initial table lookup is u_char * contextEngineId. This, I need to send down to the agent in my next request as contextEngineId. However, the request that I send down takes a char * rep of a hex string (from the -E option in commandline) - converts it into unsigned char *. So, if I send down the u_char * contextEngineId in the second request, it will be converted to u_char* again - which will not be the same as the contextEngineId that I want to send - and I will get back a no such mib instance. I guess, if there is a way that I can specify the u_char * contextEngineId in the -E option - and this is not further converted into u_char *, it should be OK.
Thanks and regards, Arijit -----Original Message----- From: Dave Shield [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 08, 2004 9:40 PM To: Mukherjee, Arijit (Arijit) Cc: [EMAIL PROTECTED] Subject: Re: Anyway to get the char * contextEngineId back in manager > Is there anyway that the data can be sent back as char* and not as > u_char *. What difference will it make? The contextEngineId field is an octet string, so the data should be the same either way. In fact, this *should* be u_char rather than (signed) char, since that's what character values are. I don't understand where the problem lies? Dave ------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ 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
