Repository navigation
You know these communities better than I do: where should NetPulse be told about? #2035
Replies: 4 comments 1 reply
|
What is wonderful of this tool is also the same thing that scares me. This is not a "common user" tool. This is something more. And this is nice, but is also a problem, because it makes very hard to have a fixed use case. And honestly this is where i see the limit of Openpulse today. Just as an example, some of us have no wireguard. Some have on-off remote clients with all traffic through the local gateway. Some have site2site tunnels. Some with all traffic through the local gateway, some with only some subnets. And maybe there is also a layer2 tunnel on that wireguard. Or multiple of them. And the topology should be different in any case. (again: just an example) |
|
I'll answer the "who" before the "where", because I think it decides where to post. NetPulse isn't for everyone, and that's fine. It assumes you already know what a bridge, a VLAN and an FDB are. Someone who just wants their Wi-Fi to work won't install a fleet monitor. The user it fits is someone who already runs a handful of boxes and wants to see them. I came from that side — I went looking for a lightweight project to monitor my own gear, not the other way around. That population is growing faster than it looks. The AI wave is putting more hardware in homes — compute to run models, storage to keep local data — and that is lowering the cost of a home network, in money and in effort. The cheap OpenWrt-derived NAS systems are one example of where the Chinese home market is heading: more boxes per home, and more people who need exactly this and have the basics to use it. The concrete place I'd start is the iStoreOS community. I run iStoreOS myself — an OpenWrt variant that's been growing NAS features of its own — and its official community is 酷友社 (KoolCenter, koolcenter.com). Around it there's a wave of emerging Chinese NAS vendors building their own systems on the same base. Their users fit three ways: they tend to have more devices to manage, they have the technical ability to run this, and increasingly they can use AI to write the code that fixes their own problems. Bringing them in would speed up iteration: more varied hardware in the wild, more real-device reports, and more people who can turn a bug into a PR instead of just a complaint. A post from someone who runs it on their own rack lands better there than one from you. I'm happy to write a short Chinese intro for 酷友社 showing my real fleet — gateway, three APs, a NAS, a few switches — and what the topology and the SNMP switch views actually look like, then link back here. |
|
@Bann-DEV, that is the framing I was missing, and I am taking it as the rule: the post should talk to people who already run a handful of boxes and want to see them, not to the general public. Which also answers @MassiPi's worry, in a way. The app does not need a fixed use case, but a post does. @MassiPi, your example is fair and it is the hard part. Site to site, a layer 2 tunnel, only some subnets routed: today the topology shows what the devices declare and leaves the rest unknown instead of guessing, which is honest but is not an answer to your case. If the models are going to be modelled properly, that deserves its own thread rather than getting lost inside this one, and I would rather have it there with your diagrams than as a side note here. Concretely, what I take from both: post where I can answer questions myself and where the audience already runs this gear, starting with the OpenWrt forum and the self-hosted places, and keep the curated lists for when the project can defend its place there. No mass posting, and no dropping a link from an account that disappears. If it turns out I am wrong about a community, I would rather find out in a thread than in silence. And the offer stands for everyone here. A post from someone who runs it weighs more than one from me. If any of you would rather write it, say so and I will answer every question in the thread the same day. |
|
Yes, I am Chinese :) Which is also why the Chinese panel matters to me: I have been running my own translation on my fleet since 2.49.x, and I would rather it lived upstream than in my private build. Update on the where: 酷友社 (KoolCenter) has gone read-only for some reason, no idea when it comes back. So the plan grew a second leg. iStoreOS itself is open source: https://github.com/istoreos/istoreos, worth a look when you have a minute. I am thinking of asking them to take NetPulse as a plugin in their software center. That would put it in front of exactly the crowd we described, forum or no forum. And the prerequisite is already moving: #2069 + #2070, the full app-UI Chinese catalog (2670/2670 keys) with the plumbing, native-reviewed. Once it lands, the post or the plugin page can show a real Chinese panel. I will link whatever comes first back here, so questions reach you where you can answer them the same day. |
Uh oh!
There was an error while loading. Please reload this page.
This thread is not about a release. It is one thing I want to say and another one I want to ask, and the ask is short.
Before asking, what you have done. Everyone who has opened an issue or sent a pull request:
Two things exist because you asked for them.
One is SNMP. The poller is from late August, before most of you were here, but what works today with real switches has been shaped by you. @crowedavid with client detection from the FDB, ifSpeed on 2.5G ports and the quirks of each vendor. @Bann-DEV with FastPath temperature read from the private MIB, ENTITY-MIB for firmware and model, and MikroTik temperature from the health table. A switch showing ports, neighbours and temperature instead of showing up empty is your work.
The other is everything outside OpenWrt. RouterOS, Asuswrt, OPNsense, UniFi, BBOX and fn were not in the first release. They are here because someone here had the hardware and the patience to report what it answered. Each one brought people to the repo who would not have found it otherwise.
And now the only thing I ask: help me get it in front of more people. Tell me where you hang out with your gear and whether it makes sense to talk about it there, or post it yourselves, because a post from someone who uses it weighs more than one from me. And if any way of reaching the people with the problem crosses your mind, drop it here without overthinking it. The best ideas in this project have come from a throwaway comment.
That is all. Thanks for the work these months, it has been a lot.
All reactions