snmpwalk v3 returns timeout whilst v1 works just fine.

[Mariano E. <mar...@gm...>]

*NET-SNMP version:  5.6.2.1*
*OS: MacOS Catalina*


Hello everyone! So given the subject of this email, I believe the issue
lies in the authentication settings most likely?

I'm simply running sudo snmpwalk -v3 -t 10 -u testuser -a MD5 -A
password123 -l authNoPriv -n v3context -x DES 127.0.0.1 system

only to receive the following error:

sess_process_packet: resending message id#1238060702 reqid#1528862053
rp_reqid#1528862053 rp_msgid#1238060702 len 141
transport:send: 141 bytes to UDP: [127.0.0.1]:161->[0.0.0.0]:0
trace: netsnmp_udpbase_send(): transports/snmpUDPBaseDomain.c, 333:
netsnmp_udp: send 141 bytes from 0x7f9a4b809973 to UDP:
[127.0.0.1]:161->[0.0.0.0]:0 on fd 3
trace: snmp_sess_select_info2_flags(): snmp_api.c, 6328:
sess_select: for all sessions: 3 (to in 1709773839.024516 sec)
verbose:sess_select: timer due in 1.999962 sec
verbose:sess_select: setting timer to 1.999962 sec, clear block (was 1)
trace: snmp_synch_input(): snmp_client.c, 176:
snmp_synch: Response (ReqID: 1528862053 - Cmd 161)
Timeout: No Response from 127.0.0.1


I've googled to no avail but I can't simply get to the bottom of this issue.

At some point I've noticed something about the Engine-ID, I have no idea
how to retrieve this (all attempts from Google examples returned the same
timeout error).

As you can see, I've also tried increasing the timeout period, but that did
not work.

Any points would be greatly appreciated!