Hello there!
I've got a probe #20190 (https://atlas.ripe.net/probes/20190/) and it shows
disconnected status it Atlas Web UI.
I've tried to reboot the probe, it gets the IP address from my router via
DHCP and i can ping it, the probe opens TCP connection to 193.0.19.25:443
and that's it.
The question: how do i make it connect to Atlas again?
--
~~~
WBR,
Vitalii Turovets
Software Engineer
VITU-RIPE
Hello, I started working with RIPE Atlas last week, when I made a script to create a one-off ping measurement between two specific probes (which I ping to check if they were working). I used Cousteau API, by default I sent 3 packets and I had 5 seconds of timeout. I got the results one time and then it stopped working. I changed the timeout to 3 or 4 minutes and while waiting for the callback function to execute I checked on the webpage and I can see the results for every measure I launched.
So I see the results on the page but they don't get to the stream and the callback function is never called. I also saw the status changed from "ongoing" to "stopped" several minutes after I've seen the results; which leads me to another question, when a measurement stops?, why if I already have the results of a ping (that is the only thing I've launched) it's still running?
I tried with Cousteau and also directly with socketIO but it has the same behavior. When I took off the parameters "packets=1,interval=60" of the request (leaving default values), I got the result with Cousteau API, but not with the socket directly. When I run it again it didn't work, so it looks like it works one of 20 times. Is there something I could do or am I doing something wrong?
Thank you,
Florencia.
Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
Dear colleagues,
recently, some of the third version of RIPE Atlas probes have had an
issue with their USB sticks.
We're still investigating what may be causing this issue,
and in the meantime we have a possible solution, outlined in this RIPE
Labs article (and below in the email)
https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-pro…
These steps might not be a surprise to the users on this list,
but on the 4th of July we reached out to almost 5000 hosts of
"abandoned" probes, and we see immediate positive results!
As you can see from some screenshots I quickly made,
number of active probes have increased - from 8883 on 1st July,
to 9323 this morning. Allowing for normal fluctuations,
this is still a considerable increase -- and we are grateful!
Thank you for all the effort that you put into keeping the
RIPE Atlas network strong by keeping your probes connected.
Kind regards,
Vesna (and the RIPE Atlas team)
===
Steps to power-cycle probe without USB stick:
1. Unplug the probe from its power source
2. Remove the USB stick from the probe
3. Plug in the probe WITHOUT the USB stick
4. Wait for ten minutes
5. Insert the USB stick
After an hour, check SOS-messages & "Status" tab
Note: Only on a network with working DHCP.
If you have configured probe to use static IP,
this setting would be lost if trying the steps.
If this didn't help, try using a new, brand-name USB stick that is at
least 4GB in size (it does not need any preparation but its contents
will be erased so make sure it does not store anything crucial)
If the problem is still there, please contact us at atlas(a)ripe.net
Hi all!
I'm new to RIPE Atlas, and right now using it for educational purposes
:)) lately I've seen that some of my traceroute measurements do not have
RTT. although it's not completely ignored by the hop (I get the data
like from, size, ttl), but only rtt is missing :))
any idea how, why and when does this happen? :)
for a live example, check Measurement #4458653. 48th probe's 11th hop's
1st query (counting from zero, btw) does not have rtt :)
thanks in advance!
side question: is there an (un)official IRC channel? :)
--
Antranig Vartanian | PGP Key ID : 0xDAB81456
https://antranigv.am | https://cert.am
(* do one thing and do it well *)
Hello,
I've been hosting a probe for quite sometimes and now that APIv2 is out, I've writing a Go library to access it. Is there a development server I could hit instead of the regular one in order to clutter the DB with temporary/trash measurements?
Thanks.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto(a)keltia.net
In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/
I received a report from one of our security monitoring systems about
one of our probes (#17846) - https://atlas.ripe.net/probes/17846/ which
appears to be infected with Tinba:
> Security incident #1 - Tinba infection
> Involved internal Hosts:
> atlas-probe.cc.biu.ac.il 132.70.248.150 spotted since
> 2016-06-30
> 23:58:54 till 2016-07-01 05:01:20
> Malicious activities found:
> Tinba infection
> related indication of compromise:
> Communication with CnC
> 192.112.36.4
> 192.203.230.10
> 192.228.79.201
> 192.33.4.12
> 192.36.148.17
> 193.0.14.129
> 198.41.0.4
> 198.97.190.53
> 199.7.83.42
> 199.7.91.13
> 202.12.27.33
Should we be worried?
Thanks,
Hank
Hi
I am trying to add a couple of new measurements, however it has been
"...calculating" for about an hour now.
Is there a known issue?
Many Thanks
Steve P
--
Steve Pointer
spointer(a)humdai.net
