Carlos E. R. wrote:
On 2015-01-12 14:13, Andrei Borzenkov wrote:
On Mon, Jan 12, 2015 at 3:54 PM, Carlos E. R. <> wrote:
I simply have:
authCommunity log,execute,net public authCommunity log,execute,net private
I thought that would write things to the log.
No, it simply enables snmptrapd to perform selected actions for selected community strings. How exactly it performs these actions is defined by other options.
As I have no idea what strings the router may send (the documentation doesn't say), I can't write any action.
Sure you can - just use the default to log everything. A traphandler called by snmptrapd is given four lines on stdin: hostname ipaddress oid1 value1 oid2 value2 See "man snmptrapd.conf", section "traphandle". net-snmp also comes with sample scripts etc.
Or the router is not sending things, despite the hit on the firewall log.
You have configured the router where to send the snmp traps? There might also be settings wrt which traps to send. "tcpdump -p 162" might also show you the traps.
(the tutorial example logs are dated "1999-11-12", so they are a decade and a half old)
SNMP is not a rapidly changing topic. Also, like Andrei said, configuring an snmp setup is not for the faint of heart. It is not overly user-friendly. I can't help with the logging, I've never bothered setting it up. Our SNMP monitor writes everything to a database. -- Per Jessen, Zürich (5.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org