Add support for receiving SNMP traps through a multiplexer #362
Labels
enhancement
New feature or request
post-zino2.0
These are features Zino1 does not have, but might be desired later
Rationale
As mentioned in Håvard Eidnes' comments in #173, there is often a limit to how many trap receivers that can be meaningfully configured in any one router.
For this reason (and other reasons), the legacy Zino does not actually provide its own SNMP trap listener, but instead connects to an SNMP trap multiplexer service (
straps
, ornmtrapd
in later incarnations, a part of the Scotty framework, I think). The trap multiplexer receives the actual trap messages, and multiplexes them to a UNIX socket that multiple processes can read from. Under this model, Zino never has to be started as a privileged user, only the trap multiplexer does.This model is not currently supported by Zino 2. It provides its own trap listener, as we wanted it to be as standalone as possible, without introducing dependencies to the older Tcl-based tools.
However, Zino 2 could be extended to also support some kind of trap multiplexer, whether it be
straps
/nmtrapd
or something else.Some implementation considerations
nmtrapd
will add an extra header to an SNMP trap message before passing it on to a UNIX socket. This header typically contains information about the originators IP address and the length of the incoming packet.The text was updated successfully, but these errors were encountered: