wip/zino 2.5.2 NetBSD

Interface-centric (+eBGP++) multi-user SNMP-based network monitor

System: NetBSD
Repository: pkgsrc-wip
Maintainer: [email protected]
Last update: 2026-10-16
Commit: 29e09cc0b7
License: apache-2.0
Categories: wip, net

Description

Zino Is Not OpenView.

Zino is an SNMP network based monitor that began its life at Uninett in the mid 1990s. It was a home-grown system written in Tcl, specifically to monitor the state of the routers of the Norwegian national research network (NREN). This is a re-implementation of the server side of this system in Python.

Here's a quote about its features from the README file of the original Tcl codebase and which is re-implemented here:

o Trap-driven polling; receives and interprets traps. o Periodic status polling (by default low frequency). o A simplistic event handling system. o A simple SMTP-like client/server protocol.

Development of Zino 2.0 is fully sponsored by NORDUnet, on behalf of all the nordic NRENs.

Install

From pkgsrc-wip (no binary package):

cd /usr/pkgsrc/wip/zino && make install clean

Dependencies

Build dependencies 1

devel/py-setuptools

Run dependencies 6

No port depends on this one.

Commit history 2

Date Commit Credits Log message

2026-10-16 29e09cc0b7 Adam Ciarciński Forget Python 3.10

2026-09-14

8a827566b5

Havard Eidnes

zino: update to version 2.5.2.

Pkgsrc changes: * version-bump + checksums + minor adjust of dependencies. Upstream changes: - Added explanation section to documentation covering Zino's history, core concepts, and technical architecture ([#435](https://github.com/Uninett/zino/issues/435)) - Added documentation for cuRitz, with screenshots. ([#568](https://github.com/Uninett/zino/issues/568)) - `--user` and the `process.user` setting now accept a numeric `UID` or `UID:GID` or, as previously, a user name, so Zino can drop privileges to a UID that has no entry in `/etc/passwd` (e.g. inside a container) - BGP sessions that go down are reported again. On routers that send Zino an SNMP trap when a session drops, the drop was only written to the log and never turned into an event, so the outage …