- ripe-atlas - mailman.ripe.net

Probe seems DoA
by Benoit Lelievre 03 Jul '18

03 Jul '18

Yesterday I received two v3 probes. While the first one took a while to update and connect the second one is showing a different behaviour. When I plug it in the reset light flashes for about 10 second but then the second LED lights up solid and it seems like the probe is frozen. It doesn't even request an IP address from my DHCP server. The FAQ doesn't list what only having LEDs 1 and 2 on solid means and I'm concerned that this probe is bricked. Any advice on what I should do with this probe? Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 3

New on RIPE Labs: Outcome of the RIPE Atlas Anchor VMs Pilot
by Mirjam Kuehne 02 Jul '18

02 Jul '18

Dear colleagues, The pilot we ran to assess the feasibility of involving virtual machines in the pool of RIPE Atlas anchors is complete and the results are good. Please find more details on RIPE Labs: https://labs.ripe.net/Members/kistel/outcome-of-the-ripe-atlas-anchor-vms-p… Kind regards, Mirjam Kühne RIPE NCC

1 0

Probe connection not holding
by Andre Heinrichs 01 Jul '18

01 Jul '18

Hi everyone, Another day, another weird effect. My probe (29384) keeps losing its connection to the Atlas systems. That seems to happen since the backend problems from Saturday were fixed. I also noticed that my probe switched from ctr-nue13 which it was always connected with to ctr-ams15 after 18 June and yesterday it got connected to ctr-ams14 but lost that connection again quite fast. My questions again: is that (probes getting disconnected all the time) something anyone else sees? Is there something on Atlas‘ side wrong or has my probe somehow lost the ability to stay connected for periods of more than a couple of minutes? There are again no obvious problems with my internet connection. TIA, Andre

2 2

Problems with the RIPE Atlas backend systems
by Anand Buddhdev 30 Jun '18

30 Jun '18

Hi folks, We have some problems with the RIPE Atlas back-end systems. I don't yet know the cause, or when things will be fixed, but this is just to let you know that we're working on it. Regards, Anand Buddhdev RIPE NCC

2 1

Re: [atlas] again: Probe offline, network appears okay
by Steffen Scholz 30 Jun '18

30 Jun '18

Hi, just to confirm, I seem to be having the same problem. My probe was shown as disconnected while the LEDs on the device indicated otherwise. After performing a power cycle it's not reconnecting anymore. Regards, Steffen Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

Re: [atlas] again: Probe offline, network appears okay
by Michael H 30 Jun '18

30 Jun '18

Hi. I've had the same problems from time to time. Mostly after a power loss or power disconnect. In the end I had to replace the drive to end this frequent behaviour. This article brought me to success: https://atlas.ripe.net/docs/troubleshoot-probe-issues/ Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

again: Probe offline, network appears okay
by Andre Heinrichs 29 Jun '18

29 Jun '18

Ho everyone, I'm again seeing the problem that Atlas doesn't see my probe as connected although my network shows no problems. I just tried restarting the probe and now the probe sees itself unable to connect. Is there a known problem somewhere, anyone else seeing this behavior or is it something weird on my end? TIA, Andre

1 0

More probes with incorrect location
by Ponikierski, Grzegorz 29 Jun '18

29 Jun '18

Hi! I was making some measurements for Comcast and found 3 probes with incorrect location. Can we fix it? ;) Probe #25030 - probe description and traceroute from this probe suggests California but Atlas map shows Florida. I think it should be California. Traceroute from 25030 towards something in California. ----------------- 1 - 192.168.2.1 NA None NA 0.454ms 2 - 96.120.88.149 7922 None COMCAST-7922 - Comcast Cable Communications, LLC, US 9.291ms 3 - 68.87.196.117 7922 be-20022-rur02.santaclara.ca.sfba.comcast.net COMCAST-7922 - Comcast Cable Communications, LLC, US 8.880ms [...] Probe #32240 - probe description suggests Caribean, map the same but traceroute suggest something in North-East of US. I think that traceroute is right. Traceroute from 32240 towards something in Ashburn. ----------------- 1 - 192.168.109.1 NA None NA 0.446ms 2 - 10.0.0.1 NA None NA 1.670ms 3 - 96.120.64.153 7922 None COMCAST-7922 - Comcast Cable Communications, LLC, US 9.171ms 4 - 96.108.56.17 7922 None COMCAST-7922 - Comcast Cable Communications, LLC, US 9.776ms 5 - 68.85.106.69 7922 be-50-ar01.needham.ma.boston.comcast.net COMCAST-7922 - Comcast Cable Communications, LLC, US 10.496ms 6 - 68.86.90.173 7922 be-1003-pe02.onesummer.ma.ibone.comcast.net COMCAST-7922 - Comcast Cable Communications, LLC, US 9.908ms [...] Probe #22575 - probe description and map suggests UK but traceroute clearly shows it's in Seattle. I think that traceroute is right. Traceroute from 22575 towards something in Seattle. ----------------- 1 - 10.20.30.1 NA None NA 0.519ms 2 - 96.120.100.81 7922 None COMCAST-7922 - Comcast Cable Communications, LLC, US 11.700ms 3 - 68.87.206.221 7922 po-118-rur201.bellevue.wa.seattle.comcast.net COMCAST-7922 - Comcast Cable Communications, LLC, US 9.210ms [...] Regards, Grzegorz

1 0

Error: Only anchors may be targeted.
by Mozafary Mohammad 28 Jun '18

28 Jun '18

Hello I've got "Only anchors may be targeted." on HTTP measurement creation.Any body can advise what the problem is? Thanks

8 9

Re: [atlas] Probe offline, Network appears okay
by Andi Meuli 18 Jun '18

18 Jun '18

Oh, nice. After several reboots and switching to a different USB power device it finally works again!? :-) Don't know what's different, but at least here in my company's network it is running well. -Andi Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 3