Hi Dave,
Thanks for your response so far.
Actually, the final problem is in comparing the engine-id received in UDP
packet with that in user database.
If I send engine-id using command:
snmptrap -e *0x0102030405* -v 3 -u administrator -a MD5 -A mypassword -l
authNoPriv -d localhost 42 coldStart
I am running Net-SNMP 5.5 on an AIX 5.3 OS system.
When I try to get the tcpConnTable (1.3.6.1.2.1.6.13.1)
Net-SNMP responds with OID for 1.3.6.1.2.1.6.14.1
snmpd.log trace shows:
Received SNMP packet(s) from UDP: [1xx.yy.245.143]:1147->[0.0.0.0]
GETNEXT message
-- TCP-MIB::tcpConnState
On 21 July 2010 16:08, Thazhai Arasan wrote:
> here i have attached the function for write_method pointer. you can see
> "SNMPconfSetSectionKey" function in COMMIT action.
What format does "SNMPconfSetSectionKey" expect the IP address to be in?
Remember that the value provided via SNMP is a
Ok,
here i have attached the function for write_method pointer. you can see
"SNMPconfSetSectionKey" function in COMMIT action.
I cant set the value through SNMP-SET tool . I assumed that IP value is
assigned in var_val pointer.
But the value is not settable.
But if i hard-code the
On 21 July 2010 15:10, Thazhai Arasan wrote:
> But when i set this (var_val) value in COMMIT action, it wont set the new
> value. The value is not set. But when i hard-coded the some values instead
> of (var_val) in function, it is set. can you please tell me the reason.
Short answer - no. I
Thank you Dave,
I unterstood u_char * var_val, is for new value ,
But when i set this (var_val) value in COMMIT action, it wont set the new
value. The value is not set. But when i hard-coded the some values instead
of (var_val) in function, it is set. can you please tell me the reason.
re
Hi Dave,
Thanks for your polite response.
The actual value contains the characters I cannot type using keyboard and
even can't copy (like 5 squares). So, it is very difficult to provide you
the same.
But, I know this is some bytes before the correct value. I will soon find it
out and will let you
On 21 July 2010 14:07, Gaurav Chaturvedi wrote:
> 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.
But *what* garbage value?
It is extr
On 21 July 2010 14:23, Thazhai Arasan wrote:
> u_char * var_val,
This contains a pointer to the new value.
(Just cast it to the appropriate type)
> u_char var_val_type,
This contains the ASN1 type of the new value.
> size_t var_val_len,
This contai
On 21 July 2010 14:22, Gaurav Chaturvedi wrote:
> The actual value contains the characters I cannot type using keyboard and
> even can't copy (like 5 squares). So, it is very difficult to provide you
> the same.
The engine ID is a binary string, so I wouldn't expect it to be printable.
But you sh
Hi,
I need your help regarding SNMP-SET function, I am using one function
for write_method pointer. If i pass any value (integer, string, etc) through
snmpset tool, where we can get the pass values(integer, string, etc).
suppose if i use : snmpset -v2c -c private 192.168.1.2 [O.I.D
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 valu
On 21 July 2010 13:51, Gaurav Chaturvedi 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_
Hi,
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,
&boots_uint, &time_uint,
secName, secNameLen,
signature, &signature_length,
salt,
Hi Dave,
Now I am registering the tokens using:
register_config_handler(app, "usmUser",
usm_parse_config_usmUser, NULL, NULL);
register_config_handler(app, "createUser",
usm_parse_create_usmUser, NULL,
"username [-e ENGINEID] (MD5|SHA) authpassphrase [DES
[privpas
Hi
I got a question on compiling net-snmp from source with my own openssl
libaries.
If I build net-snmp, for example with openssl version 0.9.8o, and on the system
i am using net-snmp openssl version 0.9.8g is installed, which version of
openssl would e.g an snmpget -v 3 command use? The vers
16 matches
Mail list logo
