From michabailey at gmail.com Thu Feb 7 13:50:57 2019 From: michabailey at gmail.com (Micha Bailey) Date: Thu, 7 Feb 2019 14:50:57 +0200 Subject: [atlas] New on RIPE Labs: RIPE Atlas Probes: Delays in Distribution In-Reply-To: References: Message-ID: Any updates regarding v4, in terms of what the hardware is etc.? On Thu, Mar 29, 2018 at 5:58 PM Mirjam Kuehne wrote: > Dear colleagues, > > The good news: RIPE Atlas is growing both in terms of geographical > diversity and ASN coverage. What's more, RIPE Atlas is evolving, with a > new generation of probe hardware having already passed the test phase > and a pilot programme underway to assess the viability of VM anchors. > > The not so good news: With RIPE Atlas so much in demand, and with our > current provider having ceased manufacturing the probe hardware, we've > had to dramatically reduce the number of probes we're distributing. > > Please find more details on RIPE Labs: > > > https://labs.ripe.net/Members/alun_davies/ripe-atlas-probes-delays-in-distribution > > Kind regards, > Mirjam K?hne > RIPE NCC > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at ripe.net Thu Feb 7 13:59:26 2019 From: robert at ripe.net (Robert Kisteleki) Date: Thu, 7 Feb 2019 13:59:26 +0100 Subject: [atlas] New on RIPE Labs: RIPE Atlas Probes: Delays in Distribution In-Reply-To: References: Message-ID: <88f9223c-ae3d-7201-8bb2-44fdb3c39a4b@ripe.net> On 2019-02-07 13:50, Micha Bailey wrote: > Any updates regarding v4, in terms of what the hardware is etc.? Hello, We use the NanoPi NEO Plus2 as the v4 probe: https://www.friendlyarm.com/index.php?route=product/product&product_id=196 The firmware on it is essentially the same as on the older, v3 probes. Regards, Robert From michabailey at gmail.com Fri Feb 8 13:45:49 2019 From: michabailey at gmail.com (Micha Bailey) Date: Fri, 8 Feb 2019 14:45:49 +0200 Subject: [atlas] New on RIPE Labs: RIPE Atlas Probes: Delays in Distribution In-Reply-To: <88f9223c-ae3d-7201-8bb2-44fdb3c39a4b@ripe.net> References: <88f9223c-ae3d-7201-8bb2-44fdb3c39a4b@ripe.net> Message-ID: Interesting. This seems like a much higher power device. What are the actual power requirements? So far my probe has been powered from the USB port on the router, and I?m concerned that this may make the installation of future probes more difficult. On Thu, Feb 7, 2019 at 2:59 PM Robert Kisteleki wrote: > > > On 2019-02-07 13:50, Micha Bailey wrote: > > Any updates regarding v4, in terms of what the hardware is etc.? > > Hello, > > We use the NanoPi NEO Plus2 as the v4 probe: > https://www.friendlyarm.com/index.php?route=product/product&product_id=196 > > The firmware on it is essentially the same as on the older, v3 probes. > > Regards, > Robert > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philip.homburg at ripe.net Fri Feb 8 15:32:38 2019 From: philip.homburg at ripe.net (Philip Homburg) Date: Fri, 8 Feb 2019 15:32:38 +0100 Subject: [atlas] New on RIPE Labs: RIPE Atlas Probes: Delays in Distribution In-Reply-To: References: <88f9223c-ae3d-7201-8bb2-44fdb3c39a4b@ripe.net> Message-ID: <1b68a63e-6459-158b-122f-e01b74962cbe@ripe.net> On 2019/02/08 13:45 , Micha Bailey wrote: > Interesting. This seems like a much higher power device. What are the > actual power requirements? So far my probe has been powered from the USB > port on the router, and I?m concerned that this may make the > installation of future probes more difficult. The power requirements are quite reasonable when used as an Atlas probe. There should be no problem powering a v4 probe from a USB port. Philip From gert at space.net Fri Feb 8 15:43:17 2019 From: gert at space.net (Gert Doering) Date: Fri, 8 Feb 2019 15:43:17 +0100 Subject: [atlas] New on RIPE Labs: RIPE Atlas Probes: Delays in Distribution In-Reply-To: References: <88f9223c-ae3d-7201-8bb2-44fdb3c39a4b@ripe.net> Message-ID: <00HRVYZU.F9VBRCO0@mobil.space.net> Hi, On Fri, Feb 08, 2019 at 03:32:38PM +0100, Philip Homburg wrote: > On 2019/02/08 13:45 , Micha Bailey wrote: > > Interesting. This seems like a much higher power device. What are the > > actual power requirements? So far my probe has been powered from the USB > > port on the router, and I???m concerned that this may make the > > installation of future probes more difficult. > > The power requirements are quite reasonable when used as an Atlas probe. > There should be no problem powering a v4 probe from a USB port. My v4 probe is fed from an USB port on an older Mac Mini, with no adverse effects I can see. Gert Doering -- NetMaster -- 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From michael.reutter at gmail.com Fri Feb 8 15:47:56 2019 From: michael.reutter at gmail.com (Michael Reutter) Date: Fri, 8 Feb 2019 15:47:56 +0100 Subject: [atlas] New on RIPE Labs: RIPE Atlas Probes: Delays in Distribution In-Reply-To: References: Message-ID: Hello, are there any plans for the Future to exchange the existing V3 probes with V4 probes? Best regards Michael Mirjam Kuehne schrieb am Do. 29. M?rz 2018 um 16:58: > Dear colleagues, > [...] > Please find more details on RIPE Labs: > > > https://labs.ripe.net/Members/alun_davies/ripe-atlas-probes-delays-in-distribution > > Kind regards, > Mirjam K?hne > RIPE NCC > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ripe-atlas at braeburn.org Fri Feb 8 17:54:30 2019 From: ripe-atlas at braeburn.org (Jay Borkenhagen) Date: Fri, 8 Feb 2019 11:54:30 -0500 Subject: [atlas] shared fate for my two probes In-Reply-To: <23535.13247.626168.554752@oz.mt.att.com> References: <23535.13247.626168.554752@oz.mt.att.com> Message-ID: <23645.46150.816400.70086@oz.mt.att.com> Hi, Following up to my own note below to provide an update: On 23-November probe 11171 disconnected again, but this time probe 11203 -- recently moved to a port on a different ethernet switch -- did not. After the 23-November event I moved probe 11171 to a different switch as well, and neither probe has suffered a recurrence since then. So, it seems that one of my ethernet switches occasionally does something that these RIPE Atlas probes do not like. Whatever that is, none of my other devices connected to that switch seem to take notice. (Were the RIPE Atlas probe issues a warning of a switch that will soon fail? Dunno. :-) ) Thanks to all those who offered suggestions for possible causes or diagnostic methods. Jay B. On 16-November-2018, Jay Borkenhagen writes: > Hi, > > My two RIPE Atlas probes have been acting strangely over the past > several months. Very frequently I receive automatic notices from the > RIPE Atlas system that both of my probes have been "disconnected from > the RIPE Atlas infrastructure" essentially simultaneously. Here's the > history from 2018: > > probe 11171 2018-02-23 18:08:57 UTC. > probe 11203 2018-02-23 18:10:23 UTC. > > probe 11171 2018-06-21 04:32:15 UTC. > probe 11203 2018-06-21 04:30:59 UTC. > > probe 11171 2018-06-24 05:36:57 UTC. > probe 11203 2018-06-24 05:37:04 UTC. > > probe 11171 2018-07-31 20:25:27 UTC. > probe 11203 2018-07-31 20:25:32 UTC. > > probe 11171 2018-08-18 04:48:20 UTC. > > probe 11171 2018-09-15 02:31:26 UTC. > probe 11203 2018-09-15 02:31:28 UTC. > > probe 11171 2018-10-15 23:03:50 UTC. > probe 11203 2018-10-15 23:04:06 UTC. > > probe 11171 2018-11-16 14:42:28 UTC. > probe 11203 2018-11-16 14:42:33 UTC. > > (Those last three events are eerily periodic.) > > Each time when I am finally able to visit inspect the probes (both are > reported as "Firmware Version 4940 (1100)"), their LEDs are in the > same state: > > --------------- > > Looking at the units with the on/off LED to the left: > > (1) the left-most (on/off) LEDs are on steadily. > (2) the next LED is off. > the next two LEDs are flashing at different frequencies: > (3) the next flashes on approx. 48 times per minute > (4) the next flashes on approx. 110 times per minute > (5) the centers of the wide "WPS/RESET" LEDs are on steadily. > > --------------- > > Once these probes fail they remain offline until I try turning it off > and on again. > > The probes are powered similarly: the RIPE-provided USB cable is > plugged into an Apple iPhone USB power adapter, in turn plugged into a > standard US 120v / 60 Hz AC receptacle. However, the AC power > circuits feeding these receptacles come from two very different > sources which should not share fate. > > Until today both probes have been plugged into ports on the same Cisco > switch, but after today's disconnect I moved probe 11203 to a > different physical switch that has the same VLANs. > > None of my other equipment experiences any troubles around the times > when these events happen to my RIPE Atlas probes. > > In the past I have reported these events to atlas at ripe.net, but I > doubt that the causes cited (e.g. "the problem is with your dns") have > been accurate. (I do not blame the atlas at ripe.net folks who have > responded. Something strange is happening here, and I haven't yet > cracked it.) > > > I'm curious whether anyone else sees similar behaviors, or has > suggestions for ways to determine what is happening. > > Thanks! > > Jay B. > From lorenzo at google.com Sat Feb 9 07:21:13 2019 From: lorenzo at google.com (Lorenzo Colitti) Date: Sat, 9 Feb 2019 15:21:13 +0900 Subject: [atlas] "Cannot resolve" tag on IPv6-only network? Message-ID: My probe v1 is on an IPv6-only network with NAT64 and DNS64. In the web UI I see it's tagged with "cannot resolve A" and "cannot resolve AAAA". Are IPv6-only networks supported? Is this because the network doesn't have a DHCP server? Something else? -------------- next part -------------- An HTML attachment was scrubbed... URL: From anandb at ripe.net Sat Feb 9 09:26:02 2019 From: anandb at ripe.net (Anand Buddhdev) Date: Sat, 9 Feb 2019 09:26:02 +0100 Subject: [atlas] "Cannot resolve" tag on IPv6-only network? In-Reply-To: References: Message-ID: On 09/02/2019 07:21, Lorenzo Colitti wrote: Hi Lorenzo, > My probe v1 is on an IPv6-only network with NAT64 and DNS64. In the web UI > I see it's tagged with "cannot resolve A" and "cannot resolve AAAA". > > Are IPv6-only networks supported? Is this because the network doesn't have > a DHCP server? Something else? IPv6-only networks are certainly supported, but if the probe isn't aware of any DNS resolver, then it's not going to be able to do any of its own DNS lookups, and that's why it's been tagged with the "cannot resolve" tags. If you go to the "network" tab of your probe in the Atlas UI, you can define IPv6 resolvers for it. Regards, Anand From lorenzo at google.com Sat Feb 9 11:47:46 2019 From: lorenzo at google.com (Lorenzo Colitti) Date: Sat, 9 Feb 2019 19:47:46 +0900 Subject: [atlas] "Cannot resolve" tag on IPv6-only network? In-Reply-To: References: Message-ID: On Sat, Feb 9, 2019 at 5:26 PM Anand Buddhdev wrote: > > My probe v1 is on an IPv6-only network with NAT64 and DNS64. In the web > UI > > I see it's tagged with "cannot resolve A" and "cannot resolve AAAA". > > > > Are IPv6-only networks supported? Is this because the network doesn't > have > > a DHCP server? Something else? > > IPv6-only networks are certainly supported, but if the probe isn't aware > of any DNS resolver, then it's not going to be able to do any of its own > DNS lookups, and that's why it's been tagged with the "cannot resolve" > tags. > Hmm. The network announces IPv6 DNS servers via RDNSS, and as far as I know, they work. Does the probe support RDNSS? -------------- next part -------------- An HTML attachment was scrubbed... URL: From hank at efes.iucc.ac.il Tue Feb 12 17:22:15 2019 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Tue, 12 Feb 2019 18:22:15 +0200 Subject: [atlas] Intro presentation to RIPE ATLAS? In-Reply-To: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> Message-ID: <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> I have been invited to a large CS dept in a university to give a 40 minute intro into what is RIPE ATLAS, how does it work, how do you get credits, how many probes are there, what is an anchor, where are they located, how does the GUI work, what type of measurements can one do, etc.? Very very introductory - just to whet their appetite.? A basic intro to RIPE ATLAS. So I looked in: https://atlas.ripe.net/resources/training-and-materials/ and didn't find anything (PS the webinar link is broken). I am sure there must be some PPT/PDF presentation out there for this. Pointers? Thanks, Hank From hank at efes.iucc.ac.il Tue Feb 12 18:15:40 2019 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Tue, 12 Feb 2019 19:15:40 +0200 Subject: [atlas] Intro presentation to RIPE ATLAS? In-Reply-To: <15333930-3764-4C87-94D4-C3C60F7D5D99@dalam.nl> References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <15333930-3764-4C87-94D4-C3C60F7D5D99@dalam.nl> Message-ID: On 12/02/2019 18:48, Johan wrote: > Hi Hank, > >> On 12 Feb 2019, at 17:22, Hank Nussbacher > > wrote: >> >> I have been invited to a large CS dept in a university to give a 40 >> minute intro into >> what is RIPE ATLAS, how does it work, how do you get credits, how >> many probes >> are there, what is an anchor, where are they located, how does the >> GUI work, what type of measurements >> can one do, etc.? Very very introductory - just to whet their >> appetite.? A basic intro to RIPE ATLAS. >> So I looked in: >> https://atlas.ripe.net/resources/training-and-materials/ >> and didn't find anything (PS the webinar link is broken). >> I am sure there must be some PPT/PDF presentation out there for this. > > The PDF?s and Keynote can be found here: > https://www.ripe.net/support/training/material#mat I had looked at that - specifically: https://www.ripe.net/support/training/material/measurements-and-tools-training-course/measurements-and-tools-slides.ppt and started from slide 113-173 and found it a bit outdated (see slide 123). Anything else available? Thanks, Hank > > Kind regards, > Johan ter Beest > RIPE Atlas Team > >> Pointers? >> >> Thanks, >> Hank >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ripe at dalam.nl Tue Feb 12 17:48:25 2019 From: ripe at dalam.nl (Johan) Date: Tue, 12 Feb 2019 17:48:25 +0100 Subject: [atlas] Intro presentation to RIPE ATLAS? In-Reply-To: <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> Message-ID: <15333930-3764-4C87-94D4-C3C60F7D5D99@dalam.nl> Hi Hank, > On 12 Feb 2019, at 17:22, Hank Nussbacher wrote: > > I have been invited to a large CS dept in a university to give a 40 minute intro into > what is RIPE ATLAS, how does it work, how do you get credits, how many probes > are there, what is an anchor, where are they located, how does the GUI work, what type of measurements > can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. > So I looked in: > https://atlas.ripe.net/resources/training-and-materials/ > and didn't find anything (PS the webinar link is broken). > I am sure there must be some PPT/PDF presentation out there for this. The PDF?s and Keynote can be found here: https://www.ripe.net/support/training/material#mat Kind regards, Johan ter Beest RIPE Atlas Team > Pointers? > > Thanks, > Hank > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jterbeest at ripe.net Wed Feb 13 10:51:41 2019 From: jterbeest at ripe.net (Johan Ter Beest) Date: Wed, 13 Feb 2019 10:51:41 +0100 Subject: [atlas] Intro presentation to RIPE ATLAS? In-Reply-To: References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <15333930-3764-4C87-94D4-C3C60F7D5D99@dalam.nl> Message-ID: <6B8D878C-A106-4CE6-AF0A-416CFE7CD5F9@ripe.net> Hi, > On 12 Feb 2019, at 18:15, Hank Nussbacher wrote: > > On 12/02/2019 18:48, Johan wrote: >> Hi Hank, >> >>> On 12 Feb 2019, at 17:22, Hank Nussbacher > wrote: >>> >>> I have been invited to a large CS dept in a university to give a 40 minute intro into >>> what is RIPE ATLAS, how does it work, how do you get credits, how many probes >>> are there, what is an anchor, where are they located, how does the GUI work, what type of measurements >>> can one do, etc. Very very introductory - just to whet their appetite. A basic intro to RIPE ATLAS. >>> So I looked in: >>> https://atlas.ripe.net/resources/training-and-materials/ >>> and didn't find anything (PS the webinar link is broken). >>> I am sure there must be some PPT/PDF presentation out there for this. >> >> The PDF?s and Keynote can be found here: >> https://www.ripe.net/support/training/material#mat I had looked at that - specifically: > https://www.ripe.net/support/training/material/measurements-and-tools-training-course/measurements-and-tools-slides.ppt > and started from slide 113-173 and found it a bit outdated (see slide 123). > Anything else available? These are our current training course slides. We are working on a new training course which will be both up to date and more practical. However that won?t be available any time soon. Johan > Thanks, > > Hank > > > >> >> Kind regards, >> Johan ter Beest >> RIPE Atlas Team >> >>> Pointers? >>> >>> Thanks, >>> Hank >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lorenzo at google.com Thu Feb 14 12:46:31 2019 From: lorenzo at google.com (Lorenzo Colitti) Date: Thu, 14 Feb 2019 20:46:31 +0900 Subject: [atlas] "Cannot resolve" tag on IPv6-only network? In-Reply-To: References: Message-ID: On Sat, Feb 9, 2019 at 7:47 PM Lorenzo Colitti wrote: > IPv6-only networks are certainly supported, but if the probe isn't aware >> of any DNS resolver, then it's not going to be able to do any of its own >> DNS lookups, and that's why it's been tagged with the "cannot resolve" >> tags. >> > > Hmm. The network announces IPv6 DNS servers via RDNSS, and as far as I > know, they work. Does the probe support RDNSS? > I turned on IPv4 on that subnet and things started working again. That makes me think that the probe doesn't support RDNSS. Can anyone confirm or deny? Should I file a bug? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ripe at brite.cz Thu Feb 14 12:52:17 2019 From: ripe at brite.cz (ripe at brite.cz) Date: Thu, 14 Feb 2019 12:52:17 +0100 Subject: [atlas] =?utf-8?q?=22Cannot_resolve=22_tag_on_IPv6-only_network?= =?utf-8?q?=3F?= In-Reply-To: 000000007f010000320404758ce4 References: , , 000000007f010000320404758ce4 Message-ID: <20190214125217.94531321@centrum.cz> https://atlas.ripe.net/about/faq/#i-have-an-ipv6-only-network-will-the-probe-work-on-it says I have an IPv6-only network. Will the probe work on it? Yes. All probes can be configured statically with an IPv6 address, default router, DNS resolvers, etc. through the web UI. In addition, version 3 probes can be fully configured through router advertisements (support for RFC 6106 was added in firmware release 4680). There is at the moment no support for DHCPv6 (RFC 3315). Version 1 and 2 probes can obtain addresses and default routers through router advertisements, but cannot obtain DNS resolvers that way. For those probes, the DNS resolvers will have to be configured statically through the web UI. ______________________________________________________________ > Od: "Lorenzo Colitti" > Komu: "Anand Buddhdev" > Datum: 14.02.2019 12:47 > P?edm?t: Re: [atlas] "Cannot resolve" tag on IPv6-only network? > > CC: >On Sat, Feb 9, 2019 at 7:47 PM Lorenzo Colitti wrote: > >> IPv6-only networks are certainly supported, but if the probe isn't aware >>> of any DNS resolver, then it's not going to be able to do any of its own >>> DNS lookups, and that's why it's been tagged with the "cannot resolve" >>> tags. >>> >> >> Hmm. The network announces IPv6 DNS servers via RDNSS, and as far as I >> know, they work. Does the probe support RDNSS? >> > >I turned on IPv4 on that subnet and things started working again. That >makes me think that the probe doesn't support RDNSS. Can anyone confirm or >deny? Should I file a bug? > > From lorenzo at google.com Thu Feb 14 12:53:22 2019 From: lorenzo at google.com (Lorenzo Colitti) Date: Thu, 14 Feb 2019 20:53:22 +0900 Subject: [atlas] "Cannot resolve" tag on IPv6-only network? In-Reply-To: <20190214125217.94531321@centrum.cz> References: <20190214125217.94531321@centrum.cz> Message-ID: Ah, I should have RTFM. Thanks! On Thu, Feb 14, 2019 at 8:52 PM wrote: > > https://atlas.ripe.net/about/faq/#i-have-an-ipv6-only-network-will-the-probe-work-on-it > says > > I have an IPv6-only network. Will the probe work on it? > > Yes. All probes can be configured statically with an IPv6 address, default > router, DNS resolvers, etc. through the web UI. In addition, version 3 > probes can be fully configured through router advertisements (support for > RFC 6106 was added in firmware release 4680). There is at the moment no > support for DHCPv6 (RFC 3315). Version 1 and 2 probes can obtain addresses > and default routers through router advertisements, but cannot obtain DNS > resolvers that way. For those probes, the DNS resolvers will have to be > configured statically through the web UI. > > > > > > > ______________________________________________________________ > > Od: "Lorenzo Colitti" > > Komu: "Anand Buddhdev" > > Datum: 14.02.2019 12:47 > > P?edm?t: Re: [atlas] "Cannot resolve" tag on IPv6-only network? > > > > CC: > >On Sat, Feb 9, 2019 at 7:47 PM Lorenzo Colitti > wrote: > > > >> IPv6-only networks are certainly supported, but if the probe isn't aware > >>> of any DNS resolver, then it's not going to be able to do any of its > own > >>> DNS lookups, and that's why it's been tagged with the "cannot resolve" > >>> tags. > >>> > >> > >> Hmm. The network announces IPv6 DNS servers via RDNSS, and as far as I > >> know, they work. Does the probe support RDNSS? > >> > > > >I turned on IPv4 on that subnet and things started working again. That > >makes me think that the probe doesn't support RDNSS. Can anyone confirm or > >deny? Should I file a bug? > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hank at efes.iucc.ac.il Thu Feb 14 18:10:17 2019 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Thu, 14 Feb 2019 19:10:17 +0200 Subject: [atlas] Why has probe growth stagnated? In-Reply-To: <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> Message-ID: <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> On 12/02/2019 18:22, Hank Nussbacher wrote: As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes.? Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes? What are we doing wrong to entice users to install probes? Regards, Hank > I have been invited to a large CS dept in a university to give a 40 > minute intro into > what is RIPE ATLAS, how does it work, how do you get credits, how many > probes > are there, what is an anchor, where are they located, how does the GUI > work, what type of measurements > can one do, etc.? Very very introductory - just to whet their > appetite.? A basic intro to RIPE ATLAS. > So I looked in: > https://atlas.ripe.net/resources/training-and-materials/ > and didn't find anything (PS the webinar link is broken). > I am sure there must be some PPT/PDF presentation out there for this. > Pointers? > > Thanks, > Hank From james at cyberinvasion.net Thu Feb 14 18:13:56 2019 From: james at cyberinvasion.net (James Gannon) Date: Thu, 14 Feb 2019 17:13:56 +0000 Subject: [atlas] Why has probe growth stagnated? In-Reply-To: <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> Message-ID: Hard to get new probes these days. ?On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" wrote: On 12/02/2019 18:22, Hank Nussbacher wrote: As I am preparing my presentation I went to the stats page: https://atlas.ripe.net/results/maps/network-coverage/ and found that even user growth continues upward as well as number of anchor probes, the number of actual probes has more or less tapered off as of mid-2017 and ends close to 10,000 probes. Why is that? Since Nov 2015 when we passed the 9000 probe mark, probe growth is negligible. Why have all these new users (20,000 new uses since Nov 2015!) not added probes? What are we doing wrong to entice users to install probes? Regards, Hank > I have been invited to a large CS dept in a university to give a 40 > minute intro into > what is RIPE ATLAS, how does it work, how do you get credits, how many > probes > are there, what is an anchor, where are they located, how does the GUI > work, what type of measurements > can one do, etc. Very very introductory - just to whet their > appetite. A basic intro to RIPE ATLAS. > So I looked in: > https://atlas.ripe.net/resources/training-and-materials/ > and didn't find anything (PS the webinar link is broken). > I am sure there must be some PPT/PDF presentation out there for this. > Pointers? > > Thanks, > Hank From jared at puck.nether.net Thu Feb 14 20:22:36 2019 From: jared at puck.nether.net (Jared Mauch) Date: Thu, 14 Feb 2019 14:22:36 -0500 Subject: [atlas] Why has probe growth stagnated? In-Reply-To: References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> Message-ID: <9B70103B-F0AF-4FAF-A387-250AB816D082@puck.nether.net> I think it?s quite easy to get a VM these days as well, so the needs have perhaps changed somewhat. I know that hosting a VM anchor is a lot easier now, and people may have an easier time hosting a VM than a probe in some cases. - Jared > On Feb 14, 2019, at 12:13 PM, James Gannon wrote: > > Hard to get new probes these days. > > ?On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" wrote: > > On 12/02/2019 18:22, Hank Nussbacher wrote: > > As I am preparing my presentation I went to the stats page: > https://atlas.ripe.net/results/maps/network-coverage/ > and found that even user growth continues upward as well as number of > anchor probes, the number of actual probes has more or less tapered off > as of mid-2017 and ends close to 10,000 probes. Why is that? > Since Nov 2015 when we passed the 9000 probe mark, probe growth is > negligible. > Why have all these new users (20,000 new uses since Nov 2015!) not added > probes? > What are we doing wrong to entice users to install probes? > > Regards, > Hank > >> I have been invited to a large CS dept in a university to give a 40 >> minute intro into >> what is RIPE ATLAS, how does it work, how do you get credits, how many >> probes >> are there, what is an anchor, where are they located, how does the GUI >> work, what type of measurements >> can one do, etc. Very very introductory - just to whet their >> appetite. A basic intro to RIPE ATLAS. >> So I looked in: >> https://atlas.ripe.net/resources/training-and-materials/ >> and didn't find anything (PS the webinar link is broken). >> I am sure there must be some PPT/PDF presentation out there for this. >> Pointers? >> >> Thanks, >> Hank > > > > > From hjp at hjp.at Thu Feb 14 22:19:43 2019 From: hjp at hjp.at (Peter J. Holzer) Date: Thu, 14 Feb 2019 22:19:43 +0100 Subject: [atlas] Why has probe growth stagnated? In-Reply-To: <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> Message-ID: <20190214211943.6mrxz4j4v7xav7zi@hjp.at> On 2019-02-14 19:10:17 +0200, Hank Nussbacher wrote: > On 12/02/2019 18:22, Hank Nussbacher wrote: > > As I am preparing my presentation I went to the stats page: > https://atlas.ripe.net/results/maps/network-coverage/ > and found that even user growth continues upward as well as number of anchor > probes, the number of actual probes has more or less tapered off as of > mid-2017 and ends close to 10,000 probes.? Why is that? > Since Nov 2015 when we passed the 9000 probe mark, probe growth is > negligible. > Why have all these new users (20,000 new uses since Nov 2015!) not added > probes? The page also shows 11000 abandoned probes. Maybe there is an equilibrium between new probes being added and old ones being abandoned, but the user count keeps increasing because inactive users aren't detected? hp -- _ | Peter J. Holzer | we build much bigger, better disasters now |_|_) | | because we have much more sophisticated | | | hjp at hjp.at | management tools. __/ | http://www.hjp.at/ | -- Ross Anderson -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From philip.homburg at ripe.net Tue Feb 19 10:23:05 2019 From: philip.homburg at ripe.net (Philip Homburg) Date: Tue, 19 Feb 2019 10:23:05 +0100 Subject: [atlas] Issue with RIPE Atlas HTTP measurements Message-ID: We recently discovered an issue with RIPE Atlas HTTP measurements. In trying to fix an issue that caused the HTTP body size to be reported incorrectly, we inadvertently introduced a bug that prevents the measurement from working under certain conditions. This bug affects firmware release 4940 and the upcoming releases 4950 and 4960. The combination that fails is a recurring measurement after the first run with an HTTP server that returns the body as chunks. This means that one-off measurements are fine. Unfortunately, HTTP measurements that are part of anchoring measurements are affected. We will work to fix this issue in the first firmware release after 4960, which can be expected in the next couple of months. We apologise for the ongoing issue and will keep you informed as we work to resolve it. Philip From scg at gibbard.org Wed Feb 20 01:56:38 2019 From: scg at gibbard.org (scg at gibbard.org) Date: Tue, 19 Feb 2019 16:56:38 -0800 Subject: [atlas] Why has probe growth stagnated? In-Reply-To: <9B70103B-F0AF-4FAF-A387-250AB816D082@puck.nether.net> References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> <9B70103B-F0AF-4FAF-A387-250AB816D082@puck.nether.net> Message-ID: I think it?s worth first considering a couple questions: what is the goal here, and what are the constraints on meeting that goal? If the goal is ?lots and lots of probes in ever increasing numbers,? than spinning up lots of VM probes would be great. It would be an easy way to get probes in large numbers cheaply and efficiently. But if the goal is to do actual network performance measurements from the perspective of the end users who actually use the Internet, that doesn?t help much. Where Atlas really shines is in the huge number of measurement points on end user connections all over the world. Need to understand what the network looks like to users on some ISP in Venezuela? Atlas probably has a probe, and can tell you that. Here we get into an issue of the low hanging fruit being pretty saturated. For instance, I could plug in a probe at my house, but it would be the third Atlas probe on Comcast in Oakland, California, and wouldn?t really add anything (thus, I have a probe that I?ve been carrying around in my bag for the last few months waiting until I have time to plug it in somewhere more interesting). But there are still a lot of smaller ISPs that don?t have Atlas probes despite having enough end users for measurements to matter, probably because they don?t have any customers who are part of the global network operations community. It should be possible to get probes installed in a bunch of those, but it would require both available probe hardware and a targeted effort. My second question is what the constraints are on sending out new probes. Is there a shortage at the supplier, or is this just something that needs funding? -Steve > On Feb 14, 2019, at 11:22 AM, Jared Mauch wrote: > > I think it?s quite easy to get a VM these days as well, so the needs have perhaps changed somewhat. > > I know that hosting a VM anchor is a lot easier now, and people may have an easier time hosting a VM than a probe in some cases. > > - Jared > >> On Feb 14, 2019, at 12:13 PM, James Gannon wrote: >> >> Hard to get new probes these days. >> >> ?On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" wrote: >> >> On 12/02/2019 18:22, Hank Nussbacher wrote: >> >> As I am preparing my presentation I went to the stats page: >> https://atlas.ripe.net/results/maps/network-coverage/ >> and found that even user growth continues upward as well as number of >> anchor probes, the number of actual probes has more or less tapered off >> as of mid-2017 and ends close to 10,000 probes. Why is that? >> Since Nov 2015 when we passed the 9000 probe mark, probe growth is >> negligible. >> Why have all these new users (20,000 new uses since Nov 2015!) not added >> probes? >> What are we doing wrong to entice users to install probes? >> >> Regards, >> Hank >> >>> I have been invited to a large CS dept in a university to give a 40 >>> minute intro into >>> what is RIPE ATLAS, how does it work, how do you get credits, how many >>> probes >>> are there, what is an anchor, where are they located, how does the GUI >>> work, what type of measurements >>> can one do, etc. Very very introductory - just to whet their >>> appetite. A basic intro to RIPE ATLAS. >>> So I looked in: >>> https://atlas.ripe.net/resources/training-and-materials/ >>> and didn't find anything (PS the webinar link is broken). >>> I am sure there must be some PPT/PDF presentation out there for this. >>> Pointers? >>> >>> Thanks, >>> Hank >> >> >> >> >> > > From bryce at thenetworknerds.ca Wed Feb 20 02:27:25 2019 From: bryce at thenetworknerds.ca (Bryce Wilson) Date: Tue, 19 Feb 2019 17:27:25 -0800 Subject: [atlas] Why has probe growth stagnated? In-Reply-To: References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> <9B70103B-F0AF-4FAF-A387-250AB816D082@puck.nether.net> Message-ID: <7838E596-D18A-491C-BCCB-F2CD0D3EAC9B@thenetworknerds.ca> This is an interesting point to note. My local ISPs have many probes but the small ones don?t. It?s easy enough for me (and probably many others) to help people get more probes on those large ISPs but once there are a number of them with good uptime, it?s not as valuable. What is important is those smaller ISPs. Perhaps we should try and make some sort of ?official? (as in, on behalf of the RIPE Atlas rather than individually) contact with some of these smaller ISPs and see if they can help get probes in their end user networks. Thanks ~ Bryce Wilson, AS202313, EVIX AS137933 > On Feb 19, 2019, at 4:56 PM, scg at gibbard.org wrote: > > I think it?s worth first considering a couple questions: what is the goal here, and what are the constraints on meeting that goal? > > If the goal is ?lots and lots of probes in ever increasing numbers,? than spinning up lots of VM probes would be great. It would be an easy way to get probes in large numbers cheaply and efficiently. But if the goal is to do actual network performance measurements from the perspective of the end users who actually use the Internet, that doesn?t help much. > > Where Atlas really shines is in the huge number of measurement points on end user connections all over the world. Need to understand what the network looks like to users on some ISP in Venezuela? Atlas probably has a probe, and can tell you that. > > Here we get into an issue of the low hanging fruit being pretty saturated. For instance, I could plug in a probe at my house, but it would be the third Atlas probe on Comcast in Oakland, California, and wouldn?t really add anything (thus, I have a probe that I?ve been carrying around in my bag for the last few months waiting until I have time to plug it in somewhere more interesting). But there are still a lot of smaller ISPs that don?t have Atlas probes despite having enough end users for measurements to matter, probably because they don?t have any customers who are part of the global network operations community. It should be possible to get probes installed in a bunch of those, but it would require both available probe hardware and a targeted effort. > > My second question is what the constraints are on sending out new probes. Is there a shortage at the supplier, or is this just something that needs funding? > > -Steve > > >> On Feb 14, 2019, at 11:22 AM, Jared Mauch wrote: >> >> I think it?s quite easy to get a VM these days as well, so the needs have perhaps changed somewhat. >> >> I know that hosting a VM anchor is a lot easier now, and people may have an easier time hosting a VM than a probe in some cases. >> >> - Jared >> >>> On Feb 14, 2019, at 12:13 PM, James Gannon wrote: >>> >>> Hard to get new probes these days. >>> >>> ?On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" wrote: >>> >>> On 12/02/2019 18:22, Hank Nussbacher wrote: >>> >>> As I am preparing my presentation I went to the stats page: >>> https://atlas.ripe.net/results/maps/network-coverage/ >>> and found that even user growth continues upward as well as number of >>> anchor probes, the number of actual probes has more or less tapered off >>> as of mid-2017 and ends close to 10,000 probes. Why is that? >>> Since Nov 2015 when we passed the 9000 probe mark, probe growth is >>> negligible. >>> Why have all these new users (20,000 new uses since Nov 2015!) not added >>> probes? >>> What are we doing wrong to entice users to install probes? >>> >>> Regards, >>> Hank >>> >>>> I have been invited to a large CS dept in a university to give a 40 >>>> minute intro into >>>> what is RIPE ATLAS, how does it work, how do you get credits, how many >>>> probes >>>> are there, what is an anchor, where are they located, how does the GUI >>>> work, what type of measurements >>>> can one do, etc. Very very introductory - just to whet their >>>> appetite. A basic intro to RIPE ATLAS. >>>> So I looked in: >>>> https://atlas.ripe.net/resources/training-and-materials/ >>>> and didn't find anything (PS the webinar link is broken). >>>> I am sure there must be some PPT/PDF presentation out there for this. >>>> Pointers? >>>> >>>> Thanks, >>>> Hank >>> >>> >>> >>> >>> >> >> > From hank at efes.iucc.ac.il Wed Feb 20 05:52:28 2019 From: hank at efes.iucc.ac.il (Hank Nussbacher) Date: Wed, 20 Feb 2019 06:52:28 +0200 (IST) Subject: [atlas] Why has probe growth stagnated? In-Reply-To: References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> <9B70103B-F0AF-4FAF-A387-250AB816D082@puck.nether.net> Message-ID: On Tue, 19 Feb 2019, scg at gibbard.org wrote: ASN coverage is just 5.6%. That really doesn't give a complete global view for stats. Rather than return money to LIRs every year in their bill, why not state that any LIR running an active probe within their ASN will get a 50Euro credit on their bill? That alone would increase ASN footprint coverage quickly within RIPE. -Hank > I think it?s worth first considering a couple questions: what is the goal here, and what are the constraints on meeting that goal? > > If the goal is ?lots and lots of probes in ever increasing numbers,? than spinning up lots of VM probes would be great. It would be an easy way to get probes in large numbers cheaply and efficiently. But if the goal is to do actual network performance measurements from the perspective of the end users who actually use the Internet, that doesn?t help much. > > Where Atlas really shines is in the huge number of measurement points on end user connections all over the world. Need to understand what the network looks like to users on some ISP in Venezuela? Atlas probably has a probe, and can tell you that. > > Here we get into an issue of the low hanging fruit being pretty saturated. For instance, I could plug in a probe at my house, but it would be the third Atlas probe on Comcast in Oakland, California, and wouldn?t really add anything (thus, I have a probe that I?ve been carrying around in my bag for the last few months waiting until I have time to plug it in somewhere more interesting). But there are still a lot of smaller ISPs that don?t have Atlas probes despite having enough end users for measurements to matter, probably because they don?t have any customers who are part of the global network operations community. It should be possible to get probes installed in a bunch of those, but it would require both available probe hardware and a targeted effort. > > My second question is what the constraints are on sending out new probes. Is there a shortage at the supplier, or is this just something that needs funding? > > -Steve > > >> On Feb 14, 2019, at 11:22 AM, Jared Mauch wrote: >> >> I think it?s quite easy to get a VM these days as well, so the needs have perhaps changed somewhat. >> >> I know that hosting a VM anchor is a lot easier now, and people may have an easier time hosting a VM than a probe in some cases. >> >> - Jared >> >>> On Feb 14, 2019, at 12:13 PM, James Gannon wrote: >>> >>> Hard to get new probes these days. >>> >>> ?On 14.02.19, 18:10, "ripe-atlas on behalf of Hank Nussbacher" wrote: >>> >>> On 12/02/2019 18:22, Hank Nussbacher wrote: >>> >>> As I am preparing my presentation I went to the stats page: >>> https://atlas.ripe.net/results/maps/network-coverage/ >>> and found that even user growth continues upward as well as number of >>> anchor probes, the number of actual probes has more or less tapered off >>> as of mid-2017 and ends close to 10,000 probes. Why is that? >>> Since Nov 2015 when we passed the 9000 probe mark, probe growth is >>> negligible. >>> Why have all these new users (20,000 new uses since Nov 2015!) not added >>> probes? >>> What are we doing wrong to entice users to install probes? >>> >>> Regards, >>> Hank >>> >>>> I have been invited to a large CS dept in a university to give a 40 >>>> minute intro into >>>> what is RIPE ATLAS, how does it work, how do you get credits, how many >>>> probes >>>> are there, what is an anchor, where are they located, how does the GUI >>>> work, what type of measurements >>>> can one do, etc. Very very introductory - just to whet their >>>> appetite. A basic intro to RIPE ATLAS. >>>> So I looked in: >>>> https://atlas.ripe.net/resources/training-and-materials/ >>>> and didn't find anything (PS the webinar link is broken). >>>> I am sure there must be some PPT/PDF presentation out there for this. >>>> Pointers? >>>> >>>> Thanks, >>>> Hank >>> >>> >>> >>> >>> >> >> > From gert at space.net Wed Feb 20 09:36:05 2019 From: gert at space.net (Gert Doering) Date: Wed, 20 Feb 2019 09:36:05 +0100 Subject: [atlas] Why has probe growth stagnated? In-Reply-To: References: <77612006-db45-eb13-d78a-4bde4bf93f06@ripe.net> <2636f9d4-08e4-7338-ff89-fdaf0d234293@efes.iucc.ac.il> <0f2300e7-e73b-8e2d-8e72-f7cb74e712c6@efes.iucc.ac.il> <9B70103B-F0AF-4FAF-A387-250AB816D082@puck.nether.net> Message-ID: <20190220083605.GG71606@Space.Net> Hi, On Wed, Feb 20, 2019 at 06:52:28AM +0200, Hank Nussbacher wrote: > On Tue, 19 Feb 2019, scg at gibbard.org wrote: > > ASN coverage is just 5.6%. That really doesn't give a complete global > view for stats. Rather than return money to LIRs every year in their > bill, why not state that any LIR running an active probe within their ASN > will get a 50Euro credit on their bill? That alone would increase ASN > footprint coverage quickly within RIPE. I like that suggestion :-) (Not sure how that will pan out if we reach 50% of all LIRs, but to get from 5% to 20%, it might definitely be an idea) Gert Doering -- NetMaster -- 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From giotsas at hotmail.com Fri Feb 22 17:24:38 2019 From: giotsas at hotmail.com (Vasileios Giotsas) Date: Fri, 22 Feb 2019 16:24:38 +0000 Subject: [atlas] Time difference between results and update of measurement status Message-ID: I've seen that the status of a measurement is updated much later than when the measurement results become available. For instance, while the RTTs of a ping measurement are returned the status is still Ongoing for up to 3 minutes. Is there anything (such as sanity checks) that intervenes between the update of the results and and update of the measurement status, which may change the results? Or is it safe to assume that once the results are out the measurement status will eventually change to 'Stopped', just a bit later? Thanks! Vasileios -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at ripe.net Mon Feb 25 13:16:13 2019 From: robert at ripe.net (Robert Kisteleki) Date: Mon, 25 Feb 2019 13:16:13 +0100 Subject: [atlas] Time difference between results and update of measurement status In-Reply-To: References: Message-ID: On 2019-02-22 17:24, Vasileios Giotsas wrote: > I've seen that the status of a measurement is updated much later than > when the measurement results become available.? > For instance, while the RTTs of a ping measurement are returned the > status is still Ongoing for up to 3 minutes. > Is there anything (such as sanity checks) that intervenes between the > update of the results and and update of the measurement status, which > may change the results?? > Or is it safe to assume that once the results are out the measurement > status will eventually change to 'Stopped', just a bit later? > > Thanks! > Vasileios Hi, There's a loose relation between measurement stop time and when the last measurement results come in. Results can come after stop time (e.g. when some probes couldn't be told to stop measuring) and stop time can happen after the last results came in (e.g. in the case of one-offs). When the results are available for download is also a different dimension; there are multiple buffering points involved, and if one of them is clogged then the results can be delayed. This is normal, especially in the case of network partitioning or maintenance work, for example. Regards, Robert From mir at ripe.net Tue Feb 26 14:49:55 2019 From: mir at ripe.net (Mirjam Kuehne) Date: Tue, 26 Feb 2019 14:49:55 +0100 Subject: [atlas] New RIPE Atlas Version 4 Probes Message-ID: <4ffff97b-ed44-8634-bc87-349f05b18957@ripe.net> Dear colleagues, In part as a response to recent questions regarding the distribution of RIPE Atlas probes, we have prepared an article detailing the work we have been doing to get supply back on track: https://labs.ripe.net/Members/alun_davies/new-ripe-atlas-version-4-probes We hope that this article, in which we introduce the new generation of RIPE Atlas probes, will answer at least some of the questions that have arisen lately. We?d like to thank you all once again for your patience! Kind regards, Mirjam K?hne RIPE NCC