Hi Dave,
The APIs are reading all values correctly till the point Security parameters
need to be read. Even, "Security name" is read correctly.
The command used is:
snmptrap -e 0x0102030405 -v 3 -u administrator -a MD5 -A mypassword -l
authNoPriv -d localhost 42 coldStart.0
The secEngineID value is some garbage value and secEngineIDLen is 5.
Thanks
Gaurav
On Wed, Jul 21, 2010 at 6:25 PM, Dave Shield <d.t.shi...@liverpool.ac.uk>wrote:
> On 21 July 2010 13:51, Gaurav Chaturvedi <gauravchaturve...@gmail.com>
> wrote:
> > I got the point due to which problem is occurring.
> >
> > Please find the code below:
> >
> > if ((rc = usm_parse_security_parameters(secParams, remaining,
> > secEngineID, secEngineIDLen, ...
> >
> > After calling this function in API sequence "snmpv3_parse ---->
> > usm_process_in_msg'", the "secEngineID" extracted from data (received
> > through trap) is wrong. It gives some garbage value and incorrect length.
>
> What is the exact command that you are using to generate the trap?
> What are the values for secEngineID and secEngineIDLen that you are seeing?
>
> Dave
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
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
