Skip to content

NetPulse v2.53.0

Latest

Choose a tag to compare

@github-actions github-actions released this 15 Nov 23:24
d0336dc

Ten things that were quietly wrong now tell the truth, and the fleet card stops guessing.

  • The status of an agent upgrade, a WireGuard transfer and the traffic of a unit all came from the wrong place: a failed agent upgrade left its download behind, the 30 d transfer was a hardcoded fallback, and the traffic chart summed every physical interface instead of the WAN (#2037, #2017, #2048, reported by @edwardally and @fsolak47).
  • Graphs and the numbers under them now share the same window, and the 24 h and 7 d views carry four times the points they had (#2046, #2047, @fsolak47).
  • SNMPv3 arrives, and a switch no longer reports its CPU interface as a front-panel port (#2042, #2009, @Bann-DEV).
  • A unit's health score stops carrying a WireGuard penalty on routers that have no SSH access (#2041, @LemurTech).

Added

  • SNMPv3 (USM) support for polled devices (#2042).
  • Per-peer WireGuard counters are persisted, so the 30 d transfer is measured instead of estimated (#2019).
  • The 24 h traffic chart draws 96 points instead of 24, and 7 d draws 28 instead of 7 (#2046).
  • The unit information card shows the agent version and whether it is behind the embedded one (#2007).
  • A guide for contributors who want to translate NetPulse into their language (#2031).

Changed

  • The traffic summary below the graphs follows the range selected in the chart instead of a fixed window (#2047).
  • WAN traffic comes from the WAN interfaces only, so the totals stop double counting bridges and VLANs (#2048).
  • The integrations page and the README platform table list OPNsense, which the app has offered for a while (#2025, #2028).
  • The offline hint of an integration no longer names RouterOS for every vendor, and the raw poll error is shown as it arrives (#2039).

Fixed

  • A failed agent upgrade removes the downloaded binary and its staging file on every exit path (#2037).
  • The WireGuard "Transfer 30 d" widget shows the real peer transfer instead of a hardcoded fallback, and only falls back to wg0 when the listing ran on the router itself (#2017, #2041).
  • A single-port access point no longer labels a port as WAN when the board declares none, and a declared WAN survives when the uplink is a bridge member (#2033, #2034).
  • A MAC with no lease data stops being labelled as a static reservation while online and as expired once it leaves (#2029).
  • A host with virtual interfaces is no longer badged as a switch (#2032).
  • The topology map only offers the detail link on nodes that actually navigate (#2049).
  • Rack profiles seeded before 2.51.0 show live ports and offer to clean the LAG and virtual ports that stayed behind (#2010).
  • A scheduled config backup served by an agent logs as scheduled, like the ones the server runs (#2011).

Thanks

  • @fsolak47 for #2046, #2047, #2048 and #2049: four reports that turned into more graph resolution, range-aligned numbers, WAN counters and a topology link that does nothing. The traffic screens were one person looking carefully.
  • @crowedavid for #2007 and #2011, the agent version in the unit card and the inconsistent journal entry, and for the port captures behind the two agent fixes in this release.
  • @Bann-DEV for #2009 and #2010, which put the switch CPU interface back where it belongs and made old rack profiles usable again.
  • @edwardally for #2017, the WireGuard widget that had been showing the same number for months.
  • @LemurTech for #2041, a health score penalised forever by an interface that did not exist.

Full changelog: https://github.com/gnacho/netpulse/blob/main/CHANGELOG.md