Repository navigation
Replies: 1 comment 1 reply
|
Thank you juflo for the thoughtful write-up. A good part of this already exists today, as built-in integrations behind a common fleet model rather than a plugin SDK. NetPulse currently normalizes data from several source types: OpenWrt over SSH (the deepest one), RouterOS as a first-class fleet type (merged recently via #939, a hand-rolled binary API client with zero new dependencies), switches over SNMP (including LLDP MIB for topology), the agent path for managed fleets, and service integrations like AdGuard and Proxmox. Each source maps onto the same normalized model (device info, WAN status, interfaces, clients, traffic), which is close to the capability set you describe. What I do not plan in the near term is a loadable plugin mechanism. NetPulse ships as a single self-contained Go binary, and dynamic plugins fight that. The pattern for new hardware is a built-in integration following the RouterOS one as reference: implement the source against the normalized model, add the config surface, cover it with tests. Your ISP router with a local HTTP API fits that pattern well. If you want to move it forward, open an issue with the device model and API details (endpoints, auth scheme), or keep discussing it here. For prior art on community-driven integrations, the UniFi discussion (#1055) is the place where that one lives. |
Uh oh!
There was an error while loading. Please reload this page.
Hi!
First of all, thanks for the great work on NetPulse!
I was wondering whether you would consider introducing an extensible architecture to support third-party routers and network devices, beyond the current OpenWrt-focused approach.
For example, it could be based on a common interface for device providers, allowing integrations to retrieve and normalize device information from different sources, such as:
Each integration could implement a common set of capabilities, such as retrieving device information, WAN status, network interfaces, connected clients, and traffic statistics, whenever supported by the device.
This would allow community contributors to add support for their own hardware without having to modify large parts of the NetPulse core. Ideally, integrations could be developed and maintained independently, although built-in integrations would also be a perfectly reasonable starting point.
My personal use case is the router of my provider. It exposes a local HTTP API, and I would like to make its information available in NetPulse alongside my OpenWrt access points.
I believe this could also benefit users running other platforms, such as UniFi, MikroTik, OPNsense, or ISP-provided routers, and encourage community contributions.
Would an architecture along these lines fit within NetPulse's long-term direction? If so, would you prefer a generic device-provider interface, a plugin mechanism, or simply a set of built-in integrations following a common abstraction?
Thanks for your thoughts!
All reactions