Thanks a lot Bill.
I will use the inbuf variable to send a trap(will use a dummy custom MIB
table) using sendv2_trap().
Thanks for the help.
Regards,
Gowtham
On Sun, Sep 29, 2019, 20:57 Bill Fenner wrote:
> On Sat, Sep 28, 2019 at 10:14 AM Thommandra Gowtham <
> trgowtham...@gmail.com>
On Sat, Sep 28, 2019 at 10:14 AM Thommandra Gowtham
wrote:
> Thank you Bill for your response.
>
> When you said that I have configured two separate features, can you
> explain? How else can we get a logmatch trap by just one directive?
>
You currently can not. That is how I imagine the feature
Thank you Bill for your response.
When you said that I have configured two separate features, can you
explain? How else can we get a logmatch trap by just one directive?
For b), which part of the code has the actual string that is matched? I can
probably use it to raise a trap if needed.
I have
Hi Gowtham,
Please file your request at https://github.com/net-snmp/net-snmp/issues .
The reason the info is not present in the trap is because you have
configured two separate features:
1. count log file matches in the logMatch table - note that there is no
place in this table for a list of
Hi Jeff,
Can I get a response for the request?
Thanks,
Gowtham
On Sat, Sep 7, 2019 at 9:23 AM Thommandra Gowtham
wrote:
> Jeff,
>
> Thanks for your reply.
>
> It was a deliberate mail to net-snmp-coders. Because, I knew about the
> pattern matching but that would not suffice because we get a
Jeff,
Thanks for your reply.
It was a deliberate mail to net-snmp-coders. Because, I knew about the
pattern matching but that would not suffice because we get a trap like
below when we give a '.*' in pattern
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (3022) 0:00:30.22
On 9/5/19 10:58 PM, Thommandra Gowtham wrote:
> - How can we get more information in a logmatch trap other than the
> pattern matched?
Making your pattern match more text should do the trick. For example:
logmatch loginFailure /var/log/auth.log 30 Failed password for .*
BTW, this kind of
