Hello all, I’m sorry to escalate this back to the list, but I’d like to report that there is still significant commercial abuse of AMPRNet allocated subnets in violation of the AMPRNet Terms-of-Service and nothing appears to have been done about it, despite my repeated attempts to raise the issue with the abuse@ampr.org mailto:abuse@ampr.org mailbox.
There are some 260 Helium Hotspot miners using the address space 44.144.124.0/23 to earn monetary rewards on the Helium cryptocurrency blockchain. While I am a fan of Helium and have managed to make it my full-time job, I am not a fan of seeing the AMPRNet address allocations be abused this way.
Can we discuss this here, as a group?
73, Jeremy
Hi Jeremy,
Can you elaborate on how you find out the IP's please? I'm wondering because I looked at the sites and maps and can't find any relation to an IP anywhere.
73
Ruben ON3RVH
-----Original Message----- From: 44Net 44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org On Behalf Of Jeremy Cooper via 44Net Sent: Thursday, February 24, 2022 18:41 To: 44Net general discussion 44net@mailman.ampr.org Cc: Jeremy Cooper jeremy.ampr@baymoo.org Subject: [44net] Continued commercial abuse of AMPRNet in Belgium
Hello all, I’m sorry to escalate this back to the list, but I’d like to report that there is still significant commercial abuse of AMPRNet allocated subnets in violation of the AMPRNet Terms-of-Service and nothing appears to have been done about it, despite my repeated attempts to raise the issue with the abuse@ampr.org mailto:abuse@ampr.org mailbox.
There are some 260 Helium Hotspot miners using the address space 44.144.124.0/23 to earn monetary rewards on the Helium cryptocurrency blockchain. While I am a fan of Helium and have managed to make it my full-time job, I am not a fan of seeing the AMPRNet address allocations be abused this way.
Can we discuss this here, as a group?
73, Jeremy
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Hi Jeremy,
We exchanged several emails regarding this in December and I said that I would look into it, which I did. I was assured by the responsible party that the practice would stop. However I have no way of monitoring this and have to take the word of the person I spoke to that this is the case.
As you work for Helium I also asked you to provide information on how I could access the information myself so I could monitor it, but received no further reply from you (my last email to you was on December 5th).
So if you want to contact me off list and provide details of how I can monitor this usage I am happy to look at it again. TBH I am not really sure why you felt it necessary to engage a public list without first contacting me and asking for an update?
Kind Regards, Chris - G1FEF
On 24 Feb 2022, at 17:41, Jeremy Cooper via 44Net 44net@mailman.ampr.org wrote:
Hello all, I’m sorry to escalate this back to the list, but I’d like to report that there is still significant commercial abuse of AMPRNet allocated subnets in violation of the AMPRNet Terms-of-Service and nothing appears to have been done about it, despite my repeated attempts to raise the issue with the abuse@ampr.org mailto:abuse@ampr.org mailbox.
There are some 260 Helium Hotspot miners using the address space 44.144.124.0/23 to earn monetary rewards on the Helium cryptocurrency blockchain. While I am a fan of Helium and have managed to make it my full-time job, I am not a fan of seeing the AMPRNet address allocations be abused this way.
Can we discuss this here, as a group?
73, Jeremy
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
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@mailman.ampr.org wrote:
Can we discuss this here, as a group?
Hope so,
-Paul
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@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@mailman.ampr.org wrote:
Can we discuss this here, as a group?
Hope so,
-Paul
Jeremy, with which account should we log in? Because we are asked to log into the metabase.
73
Ruben ON3RVH
-----Original Message----- From: 44Net 44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org On Behalf Of Jeremy Cooper via 44Net Sent: Thursday, February 24, 2022 21:19 To: Paul Sladen 44net@paul.sladen.org Cc: Jeremy Cooper jeremy.ampr@baymoo.org; 44Net 44net@mailman.ampr.org Subject: Re: [44net] Continued commercial abuse of AMPRNet in Belgium
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@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@mailman.ampr.org wrote:
Can we discuss this here, as a group?
Hope so,
-Paul
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I also don't know how to login to the etl.dewi.org link shared.
However, I was able to run a shodan.io search for "multistream net:44.0.0.0/9" and get this list (all seem to use TCP port 44158): 44.92.55.234 44.108.10.34 44.92.55.204 44.108.10.22 44.108.10.42
On Thu, 24 Feb 2022 at 12:39, Ruben ON3RVH via 44Net 44net@mailman.ampr.org wrote:
Jeremy, with which account should we log in? Because we are asked to log into the metabase.
73
Ruben ON3RVH
-----Original Message----- From: 44Net 44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org On Behalf Of Jeremy Cooper via 44Net Sent: Thursday, February 24, 2022 21:19 To: Paul Sladen 44net@paul.sladen.org Cc: Jeremy Cooper jeremy.ampr@baymoo.org; 44Net 44net@mailman.ampr.org Subject: Re: [44net] Continued commercial abuse of AMPRNet in Belgium
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@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@mailman.ampr.org wrote:
Can we discuss this here, as a group?
Hope so,
-Paul
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Chris Smith -
Jeremy Cooper -
Jonathan Lassoff -
Paul Sladen -
Ruben ON3RVH