Re: Problem with snmptrap

On Wed, 2005-11-30 at 11:08 -0800, Wes Hardaker wrote:
> Ok...  I misdiagnosed the problem.  The problem is that snmptrap
> itself is complaining that the user doesn't exist, not the agent which
> is what I originally thought.
> 
> I do suspect a new bug.
> 
> I'm going to bet it stems from the delayed engineid probing introduced
> a while ago.  sigh.
> 
> It is definitely a new bug.  It works in 5.1.x code, but not 5.2.x...
> 

I have tried and it works with 5.2.1, but not with 5.2.2.

Also, I have tried the latest release 5.3.pre5 and I have problems when
sending all kind of alerts. Even v1 TRAP or V2c TRAP or INFORM are not
logged, snmptrapd receives them but some way, it discards them after
some VACM checks. I am using the simple configuration with
ro/rwcommunity in snmpd.conf. Is that not supported anymore? Should I
use only com2sec, group &co ...?

Kind regards,
Andrei Pisau

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQEVAwUAQ5VZRAlodUAtaLVoAQI/IwgAgfxSlA3rnGRUkZjGWy5CpL3IhEqJs+HA
yW/C0v6Roh3vB5JMueYLt5NFoyMyAEY1K7y5ilf13ssxXlaIxLyVpIGxHmQTuHUs
xsI8Mx8MTzLbiB89vbpHl24TKJ4bDUxGHIbxbrrQ5/1Ay4z/r9NDIujpyu4+HQQC
Pko2v178/dgM23FPI2osFCjSEol+pqYoEt53SZosZGLBZ8qyFNHMIdoc4VicoilT
cK8rS0EW+hHt7pKQPysYvVY4W3ktmIxOzYvffYGs+MJWsmS2Y8k77MCo5MxbMqCm
RjM89a7LWPF58fdUSWEWbRbqiRRDNXGtqcK9xLL2m7mH2tBxfe5aXw==
=HdJX
-----END PGP SIGNATURE-----

-- 
This message was scanned for spam and viruses by BitDefender.
For more information please visit http://www.bitdefender.com/