Hi Dave, Thanks a lot for your quick answer.
The first stage of the process was making tests generating the traps manually. And it worked fine. In order to generate the traps, I was executing the following command: bash# snmptrap -v3 -u usmuser -X passwd -A passwd localhost IF-MIB::linkDown IF-MIB::ifIndex.1 IF-MIB::ifOperStatus.1 i 2 IF_MIB::ifAdminStatus.1 i 2 I was able to receive these traps by the 'snmptrapd -f -Lo -Dusm'. At this very moment, I was trying to send the traps by unplugging the network cable and configure the configuration files properly. Regarding your suggestions: When I only leave the createUser and one authUser line in snmptrapd.conf, I get the following line at the log: ---------------------%<--------------------------------------- trace: netsnmp_udp_getSecName(): snmpUDPDomain.c, 1215: netsnmp_udp_getSecName: no com2sec entries trace: vacm_check_view(): mibgroup/mibII/vacm_conf.c, 1385: mibII/vacm_vars: vacm_in_view: No security name found ---------------------%<--------------------------------------- Any clue? Thanks again! Regards, Ricardo El lun, 05-03-2007 a las 16:44 +0000, Dave Shield escribió: > On 05/03/07, Ricardo Marin Vinuesa <[EMAIL PROTECTED]> wrote: > > I am trying to configure my computer (an Ubuntu Computer with net-snmp > > version 5.4) to send traps whenever the network interface is switched > > and/or off and when it is connected and disconnected. > > > > Until now, I have not managed to reveice this traps in v3, although I'm > > receiving them in v2. > > [sniiip] > > > As it can be extracted from the log, the trap for snmpv2 is correctly > > received, but the trap for v3 is not received because there is some > > problem when authenticating the Security User Name. > > > > Do you have any clue about this problem? > > Things to try: > > - simplify the snmptrapd.conf file as much as possible > (try with just the 'createUser' line and *one* "authuser" line) > > - can you successfully receive an SNMPv3 trap sent using 'snmptrap'? > (with the same settings as in your snmpd.conf file) > > - try with both "snmptrap" (i.e. simple trap) and "snmptrap -Ci" (inform) > Does that make any difference? > > - try with "authuser ... noauth" and "snmptrap ... -l noAuthNoPriv" > Does that make any difference? > If so, then try working your way up through the security levels. > > Once you've got things working with manually-generated notifications, > then you should be able to translate this into the snmpd.conf settings. > But I'd start by taking snmpd out of the equation. > > Dave ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
