OK, so now I'm getting a bit confused regarding configuration file locations.
I added a new user using the command line. It added lines in /var/net-snmp/snmpd.conf and /usr/local/share/snmp/snmpd.conf (whiwh is what the command snmpd -Dread_config -H 2>&1 | grep "Reading" | sort -u gives me, to my stupefaction) but after restarting the agent the user was unknown, so I placed those lines in /etc/snmp/snmpd.conf. The user was then recognised but the lines did not disappear from any of those files. On top of this, I'm trying to follow the advice given to place the password not on the CLI but in ~/snmp.conf but to no avail as it seems. Daniel -----Message d'origine----- De : dave.shi...@gmail.com [mailto:dave.shi...@gmail.com] De la part de Dave Shield Envoyé : jeudi 7 juin 2012 10:41 À : Chayvialle, Daniel (External) Cc : net-snmp-users@lists.sourceforge.net Objet : Re: Stuck in the way of quering a private MIB (extension using perl) On 7 June 2012 09:30, Chayvialle, Daniel (External) <daniel.chayvialle.exter...@cassidian.com> wrote: > BTW I don't have any /var/net-snmp/snmpd.conf file but IIRC this tool > temporarily > added the adequate line in the file /var/lib/snmp/snmpd.conf OK - Debian may well have moved the location of the persistent file to fit in with their File Heirarchy policy. > Following your last comments, I have 2 questions: > - what is noAuthNoPriv to be used for? Typically, this is not used with SNMPv3. noAuthNoPriv is essentially no different to community-based SNMP. They are both "believe me when I say that I'm X" If you're using SNMPv3, then this is normally to take advantage of the increased security, i.e. "I'm X, and here's my ID". That requires authentication - auth (or authPriv) > - you suggest that I first continue with accessing my MIB by extending > the agent before trying to go back to SNMP v3? It doesn't really matter. As long as you do one at a time. Get SNMPv3 working, and then look at extending the agent. Or get your extension working, and then look at using SNMPv3. What you don't want to do is switch to SNMPv3 *and* use this to query your extension. Because if it doesn't work (when it doesn't work), you won't know whether the problem lies in the SNMPv3 setup, or the MIB extension. Solve one problem at a time. It's invariably faster in the long run. Dave ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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
