Thanks for the response Dave. The only issue with this is that we'd like to know the username and source IP address of the offending packet.
It doesn't look like this is available from the AUTH_FAIL trap. Alex On Thu, 2007-02-08 at 22:53 +0000, Dave Shield wrote: > On 08/02/07, Alex Jones <[EMAIL PROTECTED]> wrote: > > We have proprietary MIBS in place which use AgentX to register > > themselves with the snmpd running on the same box. > > > > We would like to receive notifications when an authentication failure > > occurs > > The AgentX protocol does not support the sending of notifications > from the master agent to a subagent. It's designed to work the > other way round. > > > The obvious approach would be for your subagent application to > open a second listening socket, and configure the master agent > to use this as one of the trap destinations. > You application would then receive SNMP traps/notifications > including the authentication failure reports. > > Note that this would be completely separate from the AgentX > activity. Your application would effectively be acting in two > completely different roles - just merged into a single binary. > > That's how I'd attack this, anyway. > > Dave ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
