- ripe-atlas - mailman.ripe.net

New on RIPE Labs: Measuring IP Connectivity with RIPE Atlas
by Mirjam Kuehne 26 Jun '20

26 Jun '20

Dear colleagues, During a hackathon Branimir Petricevi and his colleagues at Leaseweb wanted to measure network performance that most accurately simulates a customer's experience with a network. They used RIPE Atlas to do that. Find out more in this new RIPE Labs article: https://labs.ripe.net/Members/branimir_petricevic/measuring-ip-connectivity… Kind regards, Mirjam Kühne RIPE NCC

3 2

Unauthorised probe transfers
by Paul Eagles 24 Jun '20

24 Jun '20

Hello, I've just had 2 emails saying that 2 of my software probes (numbers 1000305 & 1000137) have been transferred to LeaseWeb NOC. Both these probes (and another) live on LeaseWeb VPSs (one in NL, one in USA) but I haven't started or authorised a transfer. Before I go and shout at then, how could this have happened? Checking in 'My Atlas' it does indeed no longer show these as being my problems. Why would the good people at RIPE allow transfer of 2 of my probes without my approval? Yours, Paul.

4 6

Who wants 52.4M credits?
by Paul Eagles 24 Jun '20

24 Jun '20

I've got 52.4M credits that I don't need. Does anyone want them? Cheers, Paul.

3 2

dead v1 probe
by Gert Doering 22 Jun '20

22 Jun '20

Hi, have there been software updates for v1 probes recently? I've heard about a few v1 probes that have died "just last week" - mine among them (#461), fell off the net with "Firewall Problems Suspected", but it's no longer even ARPing properly (= either it totally lost its config and wants DHCP now, which there isn't in this network, or it just died)... So knowing whether this is a more widespread issue and possible reasons would help me to decide how much effort to invest in debugging this. gert -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

10 12

RIPE Atlas Software Probes
by Philip Homburg 22 Jun '20

22 Jun '20

Dear colleagues, We are glad to announce that, after several months of development and testing, we are now accepting applications for RIPE Atlas software probes. With several different installation options to choose from, software probes provide future hosts a whole new way to get involved with RIPE Atlas. For more details, see our new article on RIPE Labs: https://labs.ripe.net/Members/alun_davies/ripe-atlas-software-probes Kind regards, Philip

18 37

Notifications
by Thomas Schäfer 18 Jun '20

18 Jun '20

Hello, is there a possibility to get notified if the probe has lost IPv6 connectivity? At the moment it seems to me, notification only works if the connection is down with both protocols. Regards, Thomas

5 5

Q/ if Id 2303 works as expected?
by Schaefer, Henry 11 Jun '20

11 Jun '20

Hi RIPE-Atlas team, my ripe probe 2303 shows as being up and running, it is connected in a NAT environment. The probe does not show data for the Built-Ins (e.g. No data available for 2303 / 1009 for this time period) as well as is not participating in measurements. Can you check/confirm that it is not broken or advise what I would need to do to make it work like other probes please? Thanks & Regards Henry Schaefer. [image: Verizon Business Ready] <http://www.verizon.com/business> Henry Schaefer Verizon Business Markets Elisabethstraße 29-31 12247 Berlin, Germany O +49 (0)30.7669.1525 | M +49.173.262.8459 henry.schaefer(a)de.verizon.com [image: Facebook] <http://www.facebook.com/verizon> [image: Twitter] <http://twitter.com/verizon> [image: Instagram] <http://www.instagram.com/verizon> ====================================================================== Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany - Amtsgericht Dortmund, HRB 14952 - Geschäftsführer: Detlef Eppig - Vorsitzender des Aufsichtsrats: Francesco de Maio

1 0

Turris SW probe - long time to connect
by Jan Pavlinec 04 Jun '20

04 Jun '20

Hello, Since this week based on report [1], [2] from Martin we were able to observe his issue, which he reported and by using Atlas SW Probe 5010 and older, we noticed that in CLI probe is running and that it is doing something, but on the RIPE website, it shows that probe is disconnected. Can you please check probes IDs (1000585, 1000243) and what it took so long to show that it is connected? Both of those probes were shown as connected at the same time - 20:22) on Tuesday? We noticed that in some cases if you were using the latest version 5020 and register a new probe, it is working within a few minutes. However, we pushed to all our Turris OS version updated Atlas SW Probe to version 5020 and some of our users noticed similar maybe the same behavior. A probe was running on the router, but it was disconnected for almost an hour (probe ID 1000036) The router is working in all cases, ping, dig connection is OK. I'm wondering if this issue isn't on server side. In reg_init_reply.txt were following data: WAIT TIMEOUT 115 Do you know how to debug it more? [1] https://forum.turris.cz/t/turris-os-5-0-0-is-released-in-hbt/12733/149 [2] https://github.com/RIPE-NCC/ripe-atlas-software-probe/issues/38 Looking forward to hearing from you, Jan

1 0

Feature request DNS DoH measurement
by Yang Yu 25 May '20

25 May '20

Hi, As DoH is getting more adoption, it would be interesting to have DoH query support on Atlas. With support added as an additional protocol for DNS measurement (currently TCP/UDP), most measurement creation/result parsing settings can be reused. Yang

3 3

anchor on a /32 network with on-link routing ?
by Matthieu Herrb 24 May '20

24 May '20

Hi, here at Tetaneutral.net we purchased an anchor with the idea to host it in our network. For IPv4 We are using /32 addresses everywhere, and do the routing by setting the 'on-link' flag on the default route. This configuration doesn't seem to be possible through the management interface. It complains that the gateway is not no the same network as the host and provides no way (as far as I can tell) to setup the 'on-link' flag. Apart from inserting another router in front of our anchor to let it use a narrower prefix, is there a way to set it up ? Or can this be considered for the future evolutions of the anchor software ? Thanks in advance. -- Matthieu Herrb

1 0