- ripe-atlas - mailman.ripe.net

Online hackathon: Internet Health Measurements & COVID-19
by Vesna Manojlovic 08 Apr '20

08 Apr '20

Dear all, just like many other organisations, RIPE NCC is having a COVID-19 focused hackathon with very broad goal: measuring Internet health, while focusing on RIPE Atlas, RIS & OONI data. In the third week of our online event, we have a very open, very lose collective: no registration, no prizes, no deadlines... Our results are currently mostly data-visualizations & analysis: https://labs.ripe.net/covid19 To join: * read about active projects on EtherPad, and contribute: https://pad.riseup.net/p/ripe-ncc-corona-hackathon-keep * join Jitsi for video conferencing: https://jitsi.hamburg.freifunk.net/WiseGeeseUniteCarefully * chat here: slack.ooni.org / #oon-dev (also bridged to IRC) Incremental reports are added to this article: https://labs.ripe.net/Members/becha/hackathons-in-the-time-of-corona Our next call will be on Tuesday 14. April at 11:30 AM CEST (on Jitsi) If you'd like to join one of the many other hackathons, look here: https://wiki.techinc.nl/User:Becha/COVID-19#Hackathons Stay safe, stay @ home, stay healthy... Kind regards, Vesna

1 0

No Atlas today: bad gateway
by Stephane Bortzmeyer 31 Mar '20

31 Mar '20

https://atlas.ripe.net/ 502 Bad Gateway nginx/1.16.1 COVID-19 on the server?

5 6

Re: [atlas] Probe 2285 is disconnected (Randy/Bainbridge Comcast)
by Randy Bush 21 Mar '20

21 Mar '20

i keep getting these > Your probe 2285 has been disconnected from the RIPE Atlas > infrastructure since 2020-03-18 06:43:44 UTC. status shows it down but i can ping6 the probe, and from the local gateway, i can ping4 it's natted address psg.com:/usr/home/randy> ping6 2601:600:c680:2fe:220:4aff:fee0:246d PING6(56=40+8+8 bytes) 2001:418:1::62 --> 2601:600:c680:2fe:220:4aff:fee0:246d 16 bytes from 2601:600:c680:2fe:220:4aff:fee0:246d, icmp_seq=0 hlim=56 time=13.533 ms 16 bytes from 2601:600:c680:2fe:220:4aff:fee0:246d, icmp_seq=1 hlim=56 time=12.370 ms root@wrt-biwa:~# ping 192.168.0.27 PING 192.168.0.27 (192.168.0.27): 56 data bytes 64 bytes from 192.168.0.27: seq=0 ttl=64 time=0.921 ms 64 bytes from 192.168.0.27: seq=1 ttl=64 time=0.701 ms network tab shows a long history of very short disconnects there is a strat 1 sitting on the same lan, and a lot of chimers out in the world think the strat 1 is preferred. no, that is not a definitive test in any way, but it's all i can think of at my current caffeine level. comcast? modem? v1 probe? how to better diagnose? randy

2 2

Cross-connecting Communities : hackathon about the Internet health
by Vesna Manojlovic 20 Mar '20

20 Mar '20

Dear colleagues, please join our virtual hackathon: https://labs.ripe.net/Members/becha/hackathons-in-the-time-of-corona Regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

Probe 2177 disconnected since Tuesday
by Werner Wiethege 20 Mar '20

20 Mar '20

The green light is on and the orange light flashes but I don't see any network traffic from it. The port LED on the switch lights up when the cable is plugged in. I have disconnected it and plugged it in again after a few hours but that didn't change anything. Werner

4 7

Software probe using port 8080
by Paul Eagles 13 Mar '20

13 Mar '20

Hi, Is there any way to change the ports that the software probes use? Port 8080 is used by the probe which conflicts with another piece of software I wanted to use. Looking in the processes I saw this: atlas 843 0.0 0.2 50348 5992 ? S 10:15 0:00 /usr/bin/ssh -o ServerAliveInterval 60 -o StrictHostKeyChecking yes -o UserKnownHostsFile /var/atlas-probe/.ssh/known_hosts -R 50948:127.0.0.1:2023 -L 8080:127.0.0.1:8080 -i /var/atlas-probe/etc/probe_key -p 443 atlas(a)ctr-fsn01.atlas.ripe.net KEEP I had to kill the PID in order to run the other software I need so at present this new software probe is down. I'd like to start it up again but can't unless I can control which port the SSH tunnel is using. Thanks, Pauil.

3 3

Software probes offline since updating to 5010-3
by Paul Eagles 12 Mar '20

12 Mar '20

Hi all, About an hour ago I updated my 4 software probes (1000136, 1000137, 1000149 & 1000177) to 5010-3 from 5010-1 and they're all still showing as offline. For each probe I went through and updated the keys within a minute or so of the installation finishing so I don't think that's the problem. It shouldn't be an internet connection issue, they're all using the same connection as they were prior to the update and prior to the update all 4 probes were connected OK. Plus I have a physical probe at home in the same location as one of the software probes and that physical probe is showing as online. One of the software probes has been rebooted but that didn't seem to make any difference. Checking the running processes on the host everything appears OK, I see 2 instances of the ATLAS binary running. Am I missing something or just being impatient? Cheers, Paul.

2 2

(not) disconnected probes
by Romain Fontugne 11 Mar '20

11 Mar '20

Hi, I found that the following probes are reported disconnected for several hours a day, more or less at the same time, but all their built-in measurements are there and seem normal: https://atlas.ripe.net/probes/32639/#!tab-network https://atlas.ripe.net/probes/28818/#!tab-network https://atlas.ripe.net/probes/19107/#!tab-network https://atlas.ripe.net/probes/14831/#!tab-network https://atlas.ripe.net/probes/11982/#!tab-network These probes are in different ISPs and locations in Japan. Any idea why this is happening? something funky on the controllers side? Thanks, Romain

2 4

New on RIPE Labs: What’s the Deal with IPv6 Link-Local Addresses?
by Philip Homburg 11 Mar '20

11 Mar '20

Dear colleagues, Stephen Strowes, Emile Aben and I published a new article on RIPE Labs on how link-local addresses in IPv6, and specifically the '%eth0'-part of link-local addresses, can have an impact on RIPE Atlas measurements. https://labs.ripe.net/Members/philip_homburg/whats-the-deal-with-ipv6-link-… We think this will be an interesting read for network operators and others who are using RIPE Atlas measurement data or are interested in IPv6. Kind regards, Philip Homburg RIPE NCC

1 0

Broken traffic graphs in latest firmware (5010)
by Philip Homburg 10 Mar '20

10 Mar '20

Hi, A change in the RIPE Atlas probe code to make reporting traffic statistics optional in software probes (and disabled by default) has the unfortunate side-effect that reporting of traffic statistics is now disabled on Version 3 and Version 4 hardware probes, as well as all anchors. This change was rolled out in firmware version 5010. Unfortunately, this effect was not spotted during testing. We will roll out a new firmware release that corrects this issue in coming weeks. Philip

1 0