Hi Dave, Thanks for replying. I canceled my subscription to the list after this project ended, so I did not see any other messages if there were any.
It seems that both the trap destination and the admin users' password hash are stored in the same table. Indeed I specified explicit engineID for each trap destination to avoid this problem and to allow different passwords for same usernames (on different trap receivers for instance). I thought of this as a workaround so I did not post it here... It seems like a bug that by defining a trap destination I can actually change the connection password. The trap receiver is irrelevant because this happens even when there is no trap receiver. As soon as the first trap is being sent out -- whether successfully or not, whether a receiver received it or not, the connection password is changed. I used this "explicit engineID" workaround and completed the project, so I, personally, do not need any more help with this, but if this interests anyone else I will be happy to help. Thanks! - Dave On Wed, Jul 22, 2009 at 04:53:19PM +0100, Dave Shield wrote: > 2009/6/25 Mike Ayers <mike_ay...@tvworks.com>: > > >> My /etc/snmp/pvgsnmpd.conf contains the following 2 lines only: > >> ########################### > >> sysservices 1 > >> rwuser admin noauth > >> ########################### > >> > >> And before running the agent for the first time I wrote the > >> following to my /var/lib/net-snmp/pvgsnmpd.conf : > >> ########################### > >> createUser admin MD5 "administrator" > >> ########################### > > > > Whoa! That's two "admin" users > > > Errr... no. > That's the correct configuration (assuming that the second > file is in the persistent configuration directory - I'd normally > expect this to be in /var/net-snmp/snmpd.conf). > > The createUser line is used to define the name of an SNMPv3 > user (including algorithm and password information). The rwuser > line is used to specify what access this user should have. > Both entries are necessary. > > > It does sound as if something odd is going on in general, > but there's nothing wrong with these particular entries. > > > I haven't had a chance to look at the trapsess behaviour yet, > but my guess is that this might need to specify an explicit > engineID for correct operation. > Dave - it would be useful to have some details about how > you have configured users on the trap receiver. > SNMPv3 notifications are notoriously difficult to get right! > See http://www.net-snmp.org/wiki/index.php/TUT:snmptrap_SNMPv3 > for more information. > > > Dave > -- EE 77 7F 30 4A 64 2E C5 83 5F E7 49 A6 82 29 BA ~. .~ Tk Open Systems =}-----------------------------------------------ooO--U--Ooo-------------{= - d...@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il - ------------------------------------------------------------------------------ _______________________________________________ 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
