New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Mine arrived today (US). Letting it adjust to room temp before plugging it in.
@jimaek: Beyond the ssh log@, is there a way to verify telemetry is being received successfully?
Depends on what you mean. You could try finding yourself in the probes list by figuring out your ISP+city combo. Other than that there's no way to see what tests you got using public tools
Thanks, that worked, executed a ping test to a particular city & ASN that matched mine:
"id": "fgYvZRvRLTn1ZGEZ",
"type": "ping",
"status": "finished",
"createdAt": "2023-01-14T03:26:56.914Z",
"updatedAt": "2023-01-14T03:26:58.377Z",
"probesCount": 1,
and saw this in the logs (via ssh logs@):
[2023-01-14 03:26:57] [DEBUG] [695] [general] ping request fgYvZRvRLTn1ZGEZ received
Got my probe in the mail! California here. Thanks @jimaek
Got my probe today! Can't wait to get this puppy set up.
Thanks @jimaek!
Got mine today! With 1 GlobalPing and 1 jsDeliver sticker.
Dhaka, Bangladesh
Already hooked up and serving requests.
To one specific host with GlobalPing I am getting "4 packets transmitted, 3 received, 25% packet loss"
ping id: "1zDIStyIdx2oj6MK". Using asn limiting and checking back log to ensure its from my probe.
However on my PC behind the same router I do not get any packet loss for that host.
We set lower timeouts, that's probably it. But please open a GitHub issue with more details to make sure there's no bug
I just received mine today via mail! Probe is up and running from Madaripur, Bangladesh. Thanks!
Probe is up, took a bit longer, needed to setup a isolated LAN.
Looks like its the first probe in Town, neat.
I just received mine today. It's now up and running from The Philippines
I just received mine today.
Indonesia. 👍🏾
got the probe I suppose it is safe running it on my home network?
Looks like first in my city then also I don't see any non-hosting isp for my country in the list thanks
Yes its safe. If you're not sure which probe is yours you can SSH to it and see the geo data it resolved to. If its wrong you can report it on Github
@jimaek is the free probe still available. I'm from Indonesia
Sure, submit the form and consider also hosting the docker container probe on available servers
@jimaek - I am thinking of configuring a Raspberry Pi Zero for this. I did some study and a simple bare-bone DietPi with Docker should be enough. But I am still sceptical about this whole idea.
Regarding the docker image, at least I can pull the last one and keep it stored, avoiding scenarios where your image template might get compromised in future.
But what if some big player decides to simply attack your whole network? Innocent volunteers without DDoS protection get caught in the middle of an online warfare. On one side there are good things, but on the other side there are so many worries too. Even this giveaway is not actually a giveaway, because this single-board-computer (or "probe", as you call it) it's for your project and your profits, it's not for the actual receiver. Your project could help humanity with those 100 interrogations per hour, but I don't think greedy corporations will like it; so more and more concerns keep popping in my head the more I think about it.
What kind of attack do you have in mind? Doing useless tests? There are rate-limiting mechanisms in place that will prevent that. The device itself also doesn't open any ports that could receive connections and create internet issues for the user.
Its a giveaway because I send a real device that can be reused for any other purposes for free (and it costs a lot of money to send 200+ of these) simply based on trust that you will use it to help the community. And there is no "profit" here, its for the benefit of everyone.
The larger the network the more useful the project and the data is for everyone involved. e.g. once the network is large enough we could start doing CDN and DNS services monitoring and provide all data for free. You would then know how Cloudflare compares to Bunny and Fastly and so on. With a nice public interface.
The only money transaction involved will be a motivation to donate to our GitHub Sponsors, which I believe is fair since it costs money to develop the product and maintain the infrastructure. But its still not profit, as in me making money, its about breaking even.
And of course a reminder, its completely optional to participate, if you dont trust the founders or the project then its totally ok to simply use it as a user without hosting anything. In this case you just wont get the benefit of higher limits that probe hosters would get.
Let me know what other concerns you have and I would happy to answer
Received my probe today (India) Actually, mine came with a customs duty fee of Rs 936 (11.5$). Nevertheless, it's online now. Feels good to be a part of your project @jimaek Thank you.
Thats weird that you had to pay so much
Sorry about that, and thanks for being a member!
@jimaek - Why Docker?
I tried to install on a RPi Zero and it does not work because there is no Docker image for ARM V6. I can see no software to compile from source, to avoid Docker either.
Wouldn't it be better to have some open-source software written in C or Python instead of a pulled Docker image? Besides the Docker image has about 400MB to download on every update.
Docker itself is not really relevant here, its just a container, it seems you are having issues with the supported architectures. You can see here https://github.com/jsdelivr/globalping-probe/pkgs/container/globalping-probe that we support linux/amd64, linux/arm/v7 and linux/arm64
v6 is 32bit, and we target 64bit as minimum.
Using containers simplifies many things, we dont have to worry about different outputs of different linux tools that could change between versions. We always know how a tool like curl or dig will behave because its part of the container. And updates become a lot easier, this way we dont have to worry about supporting legacy versions and can always assume that everyone has the latest version.
This makes development and maintenance a lot easier.
But even now you can still compile and run it without Docker. It should be as simple as this https://github.com/jsdelivr/globalping-probe#development (just connect to the prod API instead of a self-hosted instance)
Just note that you would have to handle updates yourself
Thank you for the great project.
This project is useful because Ripe Atlas doesn't allow http on the probe.
The hardware probe delivered to you guys seems to be nanopi neo v1.4.
This is 32-bit, but neo2 and plus2 are 64-bit, so it would be nice to have an image for 64-bit as well.
That way I can utilize the extra boards I have on hand.
--
Should work by default, let me know if it doesnt
I looked into this deeper and I admit I was a bit wrong about 32bit, I was miss-remembering the discussions we had about ARM support. 32bit should work (and 64bit as well), the issue was specifically the v6 version of ARM.
Its not supported by the base images we use and I believe there were other bugs as well.
https://github.com/jsdelivr/globalping-probe/actions/runs/4032901739/jobs/6933068728
Node.js does not ship binary builds for ARMv6 anymore.
You would have to build Node.js from source, which is still possible.
RPi Zero is sexy no more.
I sold all of them last year.
RPi Zero doesn't have wired network.
Even if you get Globalping or RIPE ATLAS working, the latency results would fluctuate too much due to 2.4 GHz signal interference.
Just curious , what arm board use in probe? Nanopi?
Or is just self build?
Thanks
It was mentioned in this thread; it is NanoPi Neo. You can get one for like $16. What bothers me is that a such low-end project can't be run on a Pi Zero or something older due to lack of compatibility with architecture of ARM v6. I am looking for ways to use old hardware in new projects, without buying new stuff - this is the beauty of low-end after all.
Anyway, it seems this project can run successfully even on some cheap small VPS from @Virmach or some other low-end provider. It does not necessarily need dedicated hardware for the job.
How can we view the logs in self hosted docker? I'm running it on my idle VPSes, finally found a way to use them 😅