24 Feb
2022
24 Feb
'22
2:19 p.m.
Chris and I are talking again, thanks all. But I would like to open the inspection to
everyone here, so I’ve set a few things up.
First, since the P2P protocol itself is layered on top of TCP/IP, it’s pretty easy to at
least query the P2P network through the Decentralized Wireless Alliance’s public database
of the blockchain. You can access it at etl.dewi.org <http://etl.dewi.org/>.
https://etl.dewi.org/question/2382-amprnet-hotspots-public
<https://etl.dewi.org/question/2382-amprnet-hotspots-public>
From here, it’s a task of going through the result set and checking TCP/IP connectivity to
the port in question and observing the P2P stream header:
% telnet 44.92.55.204 44158
Trying 44.92.55.204...
Connected to 44.92.55.204.
Escape character is '^]'.
/multistream/1.0.0
On 2022-02-24, at 10:32, Paul Sladen
<44net(a)paul.sladen.org> wrote:
On Thu, 24 Feb 2022, Chris Smith via 44Net wrote:
provide information on how [to] monitor it, ...
contact me off list ...
Chris, Jeremy,
Taking this off-list (again?) sounds like a receipe for further
mis-understanding and mis-communication. It would seem more sensible
to keep this on-list. Being on-list helps to keep things civilised,
and polite, and benefits that other people can chip in as well.
Jeremy: please can you post a Shell one-liner, or other short script
that allows a definite list of Helium nodes (under 44.x) to be
automatically re-generated.
On 24 Feb 2022, at 17:41, Jeremy Cooper via 44Net
<44net(a)mailman.ampr.org> wrote:
> Can we discuss this here, as a group?
Hope so,
-Paul