My experience: Syslog-functionality != snmp-trap.
Syslog listens on port 514 UDP per default, snmp-traps are sent to port 162 UDP. When i configure Dude's syslog-server to listen on this port 162, the incoming traps are not readable (messed up).

Well I keep seeing old posts from over 2 years ago saying that trap support is coming soon. And then every time I try to find info about it everyone goes all quiet on me like I'm harry potter and have just said Voldemont or something.

Well I keep seeing old posts from over 2 years ago saying that trap support is coming soon. And then every time I try to find info about it everyone goes all quiet on me like I'm harry potter and have just said Voldemont or something.

Like great wizard once said, ROS support for SNMP traps is not late, it'll be delivered to us precisely when they mean to.

8 ) Start "Net-SNMP Trap Handler" or C:\usr\bin\snmptrapd.exe (the last one for debug)
9) The default net SNMP installation has only basic MIB's for Traps. To add more traps for different equipement consult yourself on http://www.net-snmp.org/ how to add new MIB's support.
10) Read net-snmp documentation to make it more secure or setup firewall.

You do not have the required permissions to view the files attached to this post.

I am trying to make a snmptrap log but i have some problems. I uncomment the debug part of the .py and I get the snmptraplog.txt with correct information but i have nothing in my trap log in Dude.
Is this solution only for the 4.x beta? (I dont have the enable check in the notification creation panel)

This is a big missing feature and this thread is old. When will this feature be added? Adding another piece of software into the mix is a bit ridiculous. Can we please get support for SNMP traps in The Dude?