You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
NetPulse as an import source: real port-to-port links from OpenWrt routers
#604
I maintain NetPulse (AGPL-3.0), a self-hosted read-only monitor for networks built on OpenWrt and GL.iNet. It reads what the routers already know: bridge FDB, LLDP, per-port counters, wireless clients with band and signal, roaming events, WireGuard peers.
Reason I am here: #367 asks for LLDP link discovery and it is still open. In the networks NetPulse covers that data already exists, with the real port name on each end and its negotiated speed, because it comes from the LLDP neighbour table and the FDB rather than from a scan.
Two shapes, pick whichever fits or tell me neither does:
A NetPulse import next to your Proxmox, Zigbee and Z-Wave ones, pulling from /api/topology and /api/devices. Typed nodes, edges carrying the port on each side, the rest landing in Pending for you to approve.
A pusher on my side that posts nodes and edges into your REST API, so your rack "Import links" seeds patches from real wiring instead of from a diagram someone drew.
I am not asking you to build it. Tell me which shape fits and I do the work on mine.
Posting under Ideas because #438 did the same for an integration, happy to move it to an issue with the enhancement label if that is what you prefer.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I maintain NetPulse (AGPL-3.0), a self-hosted read-only monitor for networks built on OpenWrt and GL.iNet. It reads what the routers already know: bridge FDB, LLDP, per-port counters, wireless clients with band and signal, roaming events, WireGuard peers.
Reason I am here: #367 asks for LLDP link discovery and it is still open. In the networks NetPulse covers that data already exists, with the real port name on each end and its negotiated speed, because it comes from the LLDP neighbour table and the FDB rather than from a scan.
Two shapes, pick whichever fits or tell me neither does:
/api/topologyand/api/devices. Typed nodes, edges carrying the port on each side, the rest landing in Pending for you to approve.I am not asking you to build it. Tell me which shape fits and I do the work on mine.
Posting under Ideas because #438 did the same for an integration, happy to move it to an issue with the
enhancementlabel if that is what you prefer.All reactions