Hello all.
Another thing that I'm interested in doing is auditing of SETs (ie when
a USM user sets a particular OID, log the username and source IP address
of the packet along with the OID which was set.)
These OIDs are registered via AgentX, and in trying to get this auditing
to work it doesn't
Thanks Dave.
So, possible solutions to this are:
1) move MIBs into the agent itself, and not use AgentX
2) modify AgentX itself to pass this information through
3) something else?
Alex
On Fri, 2007-02-09 at 11:35 +, Dave Shield wrote:
On 09/02/07, Alex Jones [EMAIL PROTECTED] wrote
Hello,
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, but it doesn't look like this is possible without making
modifications to the source. I have
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 +, Dave Shield wrote:
On 08/02/07, Alex Jones
Hello All,
I'm writing an agentx application with th 5.2.1 tree that needs to modify the v3 passwords as well as the access control in the persistent file. The problem is that the master agent needs this info as I understand it. Is there a clean way of getting this info to the master agent?
