From camin at ripe.net Thu Nov 1 14:21:57 2018 From: camin at ripe.net (Chris Amin) Date: Thu, 1 Nov 2018 14:21:57 +0100 Subject: [atlas] Temporary problem with RIPE Atlas measurement creation Message-ID: <11fa4e6e-5a95-e2e4-cb83-43a0356d6e0c@ripe.net> Dear RIPE Atlas users, Due to a complication during a deploy, there was a problem scheduling RIPE Atlas measurements from approximately 12:50 to 14:14 UTC. Most new measurements created during this time will not have been scheduled properly. The issue is now fixed for new measurements, so if your measurements didn't work during this time you can try to create them again and it should work. Apologies for any inconvenience caused. Regard, Chris Amin RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From klaus.mailinglists at pernau.at Thu Nov 8 10:35:04 2018 From: klaus.mailinglists at pernau.at (Klaus Darilion) Date: Thu, 8 Nov 2018 10:35:04 +0100 Subject: [atlas] DNS Measurement Grouping by NSID Message-ID: Hi! IIRC, the map of the DNS measurement allowed to group the dataset by NSID. Was this feature removed? OR is it now somewhere else? I.e.: https://atlas.ripe.net/measurements/17175212/?filter=&diversity-picker=3&aggregator=#!map Thanks Klaus From adavies at ripe.net Thu Nov 8 15:35:45 2018 From: adavies at ripe.net (Alun Davies) Date: Thu, 8 Nov 2018 15:35:45 +0100 Subject: [atlas] New on RIPE Labs: Announcing RIPE Atlas VM Anchors Message-ID: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> Dear colleagues, We just this morning published an article announcing that, as of today, we are accepting applications for anyone interested in hosting RIPE Atlas VM anchors. The article points you to all the information you?ll need to apply for and install a virtual anchor: https://labs.ripe.net/Members/alun_davies/announcing-ripe-atlas-vm-anchors Kind regards, Alun Davies RIPE NCC -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2607 bytes Desc: not available URL: From emil at emilstahl.dk Fri Nov 9 11:55:05 2018 From: emil at emilstahl.dk (Emil Stahl Pedersen) Date: Fri, 9 Nov 2018 11:55:05 +0100 Subject: [atlas] New on RIPE Labs: Announcing RIPE Atlas VM Anchors In-Reply-To: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> References: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> Message-ID: Great! We would like to apply, however the Apply to become a RIPE Atlas VM anchor host button does not work/nothing happens? Med venlig hilsen / Best regards Emil Stahl Pedersen Den tor. 8. nov. 2018 kl. 15.35 skrev Alun Davies : > Dear colleagues, > > We just this morning published an article announcing that, as of today, we > are accepting applications for anyone interested in hosting RIPE Atlas VM > anchors. The article points you to all the information you?ll need to apply > for and install a virtual anchor: > > https://labs.ripe.net/Members/alun_davies/announcing-ripe-atlas-vm-anchors > > > Kind regards, > Alun Davies > RIPE NCC > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mgalante at ripe.net Fri Nov 9 12:07:27 2018 From: mgalante at ripe.net (Michela Galante) Date: Fri, 9 Nov 2018 12:07:27 +0100 Subject: [atlas] New on RIPE Labs: Announcing RIPE Atlas VM Anchors In-Reply-To: References: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> Message-ID: <5542CE02-157B-4FC8-BB78-47AAC8D843B7@ripe.net> Hi Emil, Thank you for reporting it. The button works again now. You can go ahead and apply! Best regards, Michela Michela Galante RIPE NCC > On 9 Nov 2018, at 11:55, Emil Stahl Pedersen wrote: > > Great! We would like to apply, however the Apply to become a RIPE Atlas VM anchor host button does not work/nothing happens? > > Med venlig hilsen / Best regards > Emil Stahl Pedersen > > > Den tor. 8. nov. 2018 kl. 15.35 skrev Alun Davies : > Dear colleagues, > > We just this morning published an article announcing that, as of today, we are accepting applications for anyone interested in hosting RIPE Atlas VM anchors. The article points you to all the information you?ll need to apply for and install a virtual anchor: > > https://labs.ripe.net/Members/alun_davies/announcing-ripe-atlas-vm-anchors > > Kind regards, > Alun Davies > RIPE NCC From emil at emilstahl.dk Fri Nov 9 14:03:07 2018 From: emil at emilstahl.dk (Emil Stahl Pedersen) Date: Fri, 9 Nov 2018 14:03:07 +0100 Subject: [atlas] New on RIPE Labs: Announcing RIPE Atlas VM Anchors In-Reply-To: <5542CE02-157B-4FC8-BB78-47AAC8D843B7@ripe.net> References: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> <5542CE02-157B-4FC8-BB78-47AAC8D843B7@ripe.net> Message-ID: Thanks! Med venlig hilsen / Best regards Emil Stahl Pedersen Den fre. 9. nov. 2018 kl. 12.07 skrev Michela Galante : > Hi Emil, > > Thank you for reporting it. > The button works again now. You can go ahead and apply! > > Best regards, > Michela > > Michela Galante > RIPE NCC > > > On 9 Nov 2018, at 11:55, Emil Stahl Pedersen wrote: > > > > Great! We would like to apply, however the Apply to become a RIPE Atlas > VM anchor host button does not work/nothing happens? > > > > Med venlig hilsen / Best regards > > Emil Stahl Pedersen > > > > > > Den tor. 8. nov. 2018 kl. 15.35 skrev Alun Davies : > > Dear colleagues, > > > > We just this morning published an article announcing that, as of today, > we are accepting applications for anyone interested in hosting RIPE Atlas > VM anchors. The article points you to all the information you?ll need to > apply for and install a virtual anchor: > > > > > https://labs.ripe.net/Members/alun_davies/announcing-ripe-atlas-vm-anchors > > > > Kind regards, > > Alun Davies > > RIPE NCC > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From netravnen at gmail.com Mon Nov 12 10:11:18 2018 From: netravnen at gmail.com (Christoffer Hansen) Date: Mon, 12 Nov 2018 10:11:18 +0100 Subject: [atlas] New on RIPE Labs: Announcing RIPE Atlas VM Anchors In-Reply-To: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> References: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> Message-ID: <36251558-253b-ea67-6323-43144427a099@gmail.com> Hi Alun, (bcc'ed: atlas@) First. Thanks for sharing. Many months I have been looking forward to this first step in the direction of running the ATLAS network with only hardware units. Second. I know the RIPE NCC Atlas Team|Group is also looking into ways of providing the Atlas Probe as a VM option of sorts. I do not know how far this process is at the moment. But hoping you could share an overall status on this, too? E.g. current considerations, projects goals reached + not reached etc. Kind regards, Christoffer On 08/11/2018 15:35, Alun Davies wrote: > Dear colleagues, > > We just this morning published an article announcing that, as of today, > we are accepting applications for anyone interested in hosting RIPE > Atlas VM anchors. The article points you to all the information you?ll > need to apply for and install a virtual anchor: > > https://labs.ripe.net/Members/alun_davies/announcing-ripe-atlas-vm-anchors > > > Kind regards, > Alun Davies > RIPE NCC -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From robert at ripe.net Mon Nov 12 14:04:50 2018 From: robert at ripe.net (Robert Kisteleki) Date: Mon, 12 Nov 2018 14:04:50 +0100 Subject: [atlas] New on RIPE Labs: Announcing RIPE Atlas VM Anchors In-Reply-To: <36251558-253b-ea67-6323-43144427a099@gmail.com> References: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> <36251558-253b-ea67-6323-43144427a099@gmail.com> Message-ID: <84608118-0133-9c08-6dc6-682fbaa204c2@ripe.net> On 2018-11-12 10:11, Christoffer Hansen wrote: > Hi Alun, > (bcc'ed: atlas@) > > First. Thanks for sharing. Many months I have been looking forward to > this first step in the direction of running the ATLAS network with only > hardware units. > > Second. I know the RIPE NCC Atlas Team|Group is also looking into ways > of providing the Atlas Probe as a VM option of sorts. I do not know how > far this process is at the moment. But hoping you could share an overall > status on this, too? > E.g. current considerations, projects goals reached + not reached etc. > > Kind regards, > Christoffer Hello, We are indeed looking at what it takes to do RIPE Atlas "software probes". From the hosts' perspective this is likely going to be a software package, or docker image, or such, that one can install on an existing device. >From our perspective this is a different approach from what we have so far (hardware-only probes), so deciding on if and how to expand to this area is not a trivial question. VM anchors are simpler in this regard. As of now we're checking what software probes would change in terms of how we manage our infratructure and reviewing/verifying the related processes. I expect that we'll do some kind of pilot early next year, then decide if this is indeed a desired direction for RIPE Atlas. I hope that answers your question. Let me know if you need me to elaboration more. Regards, Robert Kisteleki for the RIPE Atlas team From netravnen at gmail.com Mon Nov 12 15:13:45 2018 From: netravnen at gmail.com (Christoffer Hansen) Date: Mon, 12 Nov 2018 15:13:45 +0100 Subject: [atlas] New on RIPE Labs: Announcing RIPE Atlas VM Anchors In-Reply-To: <84608118-0133-9c08-6dc6-682fbaa204c2@ripe.net> References: <12BA4CA0-E53B-4BA6-AE56-93D691BED25A@ripe.net> <36251558-253b-ea67-6323-43144427a099@gmail.com> <84608118-0133-9c08-6dc6-682fbaa204c2@ripe.net> Message-ID: <0e601b39-4acd-20b1-bc1b-89b4756d40c3@gmail.com> On 12/11/2018 14:04, Robert Kisteleki wrote: > We are indeed looking at what it takes to do RIPE Atlas "software > probes". From the hosts' perspective this is likely going to be a > software package, or docker image, or such, that one can install on an > existing device. I suggest looking into snap packages, too. As part of your evaluation on the distribution method of 'software probes'. The plus regarding snap packages is they are automatically updated without the need for user actions. (The auto-update functionality being a core design principle with the snap package manager.) Resulting in always up-to-date 'software probes' running on $ENDUSER machines. > From our perspective this is a different approach from what we have so > far (hardware-only probes), so deciding on if and how to expand to this > area is not a trivial question. VM anchors are simpler in this regard. > > As of now we're checking what software probes would change in terms of > how we manage our infratructure and reviewing/verifying the related > processes. I expect that we'll do some kind of pilot early next year, > then decide if this is indeed a desired direction for RIPE Atlas. > > I hope that answers your question. Let me know if you need me to > elaboration more. Kind regards, Christoffer -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From ripe-atlas at braeburn.org Fri Nov 16 22:16:47 2018 From: ripe-atlas at braeburn.org (Jay Borkenhagen) Date: Fri, 16 Nov 2018 16:16:47 -0500 Subject: [atlas] shared fate for my two probes Message-ID: <23535.13247.626168.554752@oz.mt.att.com> 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 philip.homburg at ripe.net Mon Nov 19 16:28:56 2018 From: philip.homburg at ripe.net (Philip Homburg) Date: Mon, 19 Nov 2018 16:28:56 +0100 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: <812c8df2-78af-d9ed-5891-ba14153af7bd@ripe.net> On 2018/11/16 22:16 , Jay Borkenhagen wrote: > probe 11171 2018-11-16 14:42:28 UTC. > probe 11203 2018-11-16 14:42:33 UTC. Both probes lost all internet connectivity for a couple of hours. I have no idea what happened but Atlas traceroutes stop at hop 1 (and don't even reach the local router). Philip From ripe-atlas at braeburn.org Mon Nov 19 17:53:54 2018 From: ripe-atlas at braeburn.org (Jay Borkenhagen) Date: Mon, 19 Nov 2018 11:53:54 -0500 Subject: [atlas] shared fate for my two probes In-Reply-To: <812c8df2-78af-d9ed-5891-ba14153af7bd@ripe.net> References: <23535.13247.626168.554752@oz.mt.att.com> <812c8df2-78af-d9ed-5891-ba14153af7bd@ripe.net> Message-ID: <23538.60066.573356.723929@oz.mt.att.com> Philip Homburg writes: > On 2018/11/16 22:16 , Jay Borkenhagen wrote: > > > probe 11171 2018-11-16 14:42:28 UTC. > > probe 11203 2018-11-16 14:42:33 UTC. > > Both probes lost all internet connectivity for a couple of hours. I have > no idea what happened but Atlas traceroutes stop at hop 1 (and don't > even reach the local router). > Yes, but the problem was not with the networking infrastructure: like I have reported each time, none of my other equipment has had any connectivity troubles at these times, and both probes remained inaccessible until power-cycled, when immediately they are fine again. The "couple of hours" you cite start when the issue begins, and ends only when I arrive to power-cycle them. The only sort of thing that makes any sense to me is that something occurs that triggers the probes and only the probes to lose their minds. Possibly an electrical power aberration or a networking hiccup sends the probes into a state that they cannot recover from on their own. But even the 'power aberration' explanation seems unlikely, since the two power feeds are dis-similar enough that I would not expect any surge or whatever that hits one to hit them both, and to hit in a way that only RIPE Atlas probes are affected. Has anyone else experienced electrical power disruptions that send RIPE Atlas probes into a state like the one I described in my initial message, while no other nearby equipment notices any problem? Thanks. From steamruler at gmail.com Tue Nov 20 09:04:05 2018 From: steamruler at gmail.com (Sebastian Johansson) Date: Tue, 20 Nov 2018 09:04:05 +0100 Subject: [atlas] shared fate for my two probes In-Reply-To: <23538.60066.573356.723929@oz.mt.att.com> References: <23535.13247.626168.554752@oz.mt.att.com> <812c8df2-78af-d9ed-5891-ba14153af7bd@ripe.net> <23538.60066.573356.723929@oz.mt.att.com> Message-ID: My V3 probe would semi-randomly drop connection for a few minutes before I moved it to another part of the apartment. Sounds kinda stupid, I know, but are your probes physically located near each other? Can you move them? Could be that they are more sensitive to stray RF than your other equipment. On Mon, Nov 19, 2018 at 5:54 PM Jay Borkenhagen wrote: > > Philip Homburg writes: > > On 2018/11/16 22:16 , Jay Borkenhagen wrote: > > > > > probe 11171 2018-11-16 14:42:28 UTC. > > > probe 11203 2018-11-16 14:42:33 UTC. > > > > Both probes lost all internet connectivity for a couple of hours. I have > > no idea what happened but Atlas traceroutes stop at hop 1 (and don't > > even reach the local router). > > > > Yes, but the problem was not with the networking infrastructure: like > I have reported each time, none of my other equipment has had any > connectivity troubles at these times, and both probes remained > inaccessible until power-cycled, when immediately they are fine > again. The "couple of hours" you cite start when the issue begins, > and ends only when I arrive to power-cycle them. > > The only sort of thing that makes any sense to me is that something > occurs that triggers the probes and only the probes to lose their > minds. Possibly an electrical power aberration or a networking hiccup > sends the probes into a state that they cannot recover from on their > own. But even the 'power aberration' explanation seems unlikely, > since the two power feeds are dis-similar enough that I would not > expect any surge or whatever that hits one to hit them both, and to > hit in a way that only RIPE Atlas probes are affected. > > Has anyone else experienced electrical power disruptions that send > RIPE Atlas probes into a state like the one I described in my initial > message, while no other nearby equipment notices any problem? > > Thanks. > > From teun at bit.nl Tue Nov 20 10:29:27 2018 From: teun at bit.nl (Teun Vink) Date: Tue, 20 Nov 2018 10:29:27 +0100 Subject: [atlas] no measurements Message-ID: <9d5485660ef67e6884d2b5809d5ff07da5524540.camel@bit.nl> Hi, Are there any problems with the Atlas backend? All requests are answered with {u'info': u'Something went wrong with our back-end', u'type': u'redis- fail'} I don't see any working measurements in our webportal as well. Best regards, -- Teun Vink BIT | teun at bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE From mcandela at ripe.net Tue Nov 20 10:34:13 2018 From: mcandela at ripe.net (Massimo Candela) Date: Tue, 20 Nov 2018 10:34:13 +0100 Subject: [atlas] no measurements In-Reply-To: <9d5485660ef67e6884d2b5809d5ff07da5524540.camel@bit.nl> References: <9d5485660ef67e6884d2b5809d5ff07da5524540.camel@bit.nl> Message-ID: <5e784982-709e-7374-89cb-b968cced1209@ripe.net> Hello Teun, We are having a problem with our streaming platform. Our OPS team is working on it and it will be fixed soon. When the issue will be solved, I will send an update on the list. Sorry for the inconvenience. Best regards, Massimo Candela RIPE NCC On 20/11/2018 10:29, Teun Vink wrote: > Hi, > > Are there any problems with the Atlas backend? All requests are > answered with > > {u'info': u'Something went wrong with our back-end', u'type': u'redis- > fail'} > > I don't see any working measurements in our webportal as well. > > Best regards, From mcandela at ripe.net Tue Nov 20 10:57:50 2018 From: mcandela at ripe.net (Massimo Candela) Date: Tue, 20 Nov 2018 10:57:50 +0100 Subject: [atlas] no measurements In-Reply-To: <5e784982-709e-7374-89cb-b968cced1209@ripe.net> References: <9d5485660ef67e6884d2b5809d5ff07da5524540.camel@bit.nl> <5e784982-709e-7374-89cb-b968cced1209@ripe.net> Message-ID: The issue with the RIPE Atlas streaming has been fixed. Best regards, Massimo Candela RIPE NCC On 20/11/2018 10:34, Massimo Candela wrote: > Hello Teun, > > We are having a problem with our streaming platform. Our OPS team is > working on it and it will be fixed soon. > > When the issue will be solved, I will send an update on the list. > > Sorry for the inconvenience. > > Best regards, > Massimo Candela > RIPE NCC > > > On 20/11/2018 10:29, Teun Vink wrote: >> Hi, >> >> Are there any problems with the Atlas backend? All requests are >> answered with >> >> {u'info': u'Something went wrong with our back-end', u'type': u'redis- >> fail'} >> >> I don't see any working measurements in our webportal as well. >> >> Best regards, > > From philip.homburg at ripe.net Tue Nov 20 11:08:40 2018 From: philip.homburg at ripe.net (Philip Homburg) Date: Tue, 20 Nov 2018 11:08:40 +0100 Subject: [atlas] shared fate for my two probes In-Reply-To: <23538.60066.573356.723929@oz.mt.att.com> References: <23535.13247.626168.554752@oz.mt.att.com> <812c8df2-78af-d9ed-5891-ba14153af7bd@ripe.net> <23538.60066.573356.723929@oz.mt.att.com> Message-ID: On 2018/11/19 17:53 , Jay Borkenhagen wrote: > Philip Homburg writes: > > On 2018/11/16 22:16 , Jay Borkenhagen wrote: > > > > > probe 11171 2018-11-16 14:42:28 UTC. > > > probe 11203 2018-11-16 14:42:33 UTC. > > > > Both probes lost all internet connectivity for a couple of hours. I have > > no idea what happened but Atlas traceroutes stop at hop 1 (and don't > > even reach the local router). > > > > Yes, but the problem was not with the networking infrastructure: For me the most obvious approach is to put the probes behind a switch that supports port mirroring and look at the actual traffic during this period. The fact that it happens to both probes at the same time makes it very unlikely that it is a probe specific hardware problem. I'm not aware of any bugs in the Linux kernel that would affect IPv4 and IPv6 at the same time. So the obvious next step is to check what actually goes over the wire. From teun at bit.nl Tue Nov 20 13:40:41 2018 From: teun at bit.nl (Teun Vink) Date: Tue, 20 Nov 2018 13:40:41 +0100 Subject: [atlas] no measurements In-Reply-To: References: <9d5485660ef67e6884d2b5809d5ff07da5524540.camel@bit.nl> <5e784982-709e-7374-89cb-b968cced1209@ripe.net> Message-ID: On Tue, 2018-11-20 at 10:57 +0100, Massimo Candela wrote: > The issue with the RIPE Atlas streaming has been fixed. > Thanks, everything's looking fine again :) Best regards, -- Teun Vink BIT | teun at bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE From hsalgado at nic.cl Tue Nov 20 21:38:49 2018 From: hsalgado at nic.cl (Hugo =?iso-8859-1?Q?Salgado-Hern=E1ndez?=) Date: Tue, 20 Nov 2018 17:38:49 -0300 Subject: [atlas] DNS Measurement Grouping by NSID In-Reply-To: References: Message-ID: <20181120203849.nzhopvk4gatpnu2p@nic.cl> On 10:35 08/11, Klaus Darilion wrote: > Hi! > > IIRC, the map of the DNS measurement allowed to group the dataset by NSID. > Was this feature removed? OR is it now somewhere else? I.e.: +1 It was very useful! Hugo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From jdenhertog at ripe.net Wed Nov 21 11:17:41 2018 From: jdenhertog at ripe.net (Jasper den Hertog) Date: Wed, 21 Nov 2018 11:17:41 +0100 Subject: [atlas] DNS Measurement Grouping by NSID In-Reply-To: <20181120203849.nzhopvk4gatpnu2p@nic.cl> References: <20181120203849.nzhopvk4gatpnu2p@nic.cl> Message-ID: <4866D155-6B36-44EA-B93D-11C3AA6A92F4@ripe.net> hi RIPE Atlas people, This feature was disabled per accident. It has been revived, greetings, Jasper den Hertog RIPE Atlas team > On 20 Nov 2018, at 21:38, Hugo Salgado-Hern?ndez wrote: > > On 10:35 08/11, Klaus Darilion wrote: >> Hi! >> >> IIRC, the map of the DNS measurement allowed to group the dataset by NSID. >> Was this feature removed? OR is it now somewhere else? I.e.: > > +1 > It was very useful! > > Hugo > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2619 bytes Desc: not available URL: From bjorn at mork.no Wed Nov 21 13:02:14 2018 From: bjorn at mork.no (=?utf-8?Q?Bj=C3=B8rn_Mork?=) Date: Wed, 21 Nov 2018 13:02:14 +0100 Subject: [atlas] DNS Measurement Grouping by NSID In-Reply-To: <4866D155-6B36-44EA-B93D-11C3AA6A92F4@ripe.net> (Jasper den Hertog's message of "Wed, 21 Nov 2018 11:17:41 +0100") References: <20181120203849.nzhopvk4gatpnu2p@nic.cl> <4866D155-6B36-44EA-B93D-11C3AA6A92F4@ripe.net> Message-ID: <877eh68wqh.fsf@miraculix.mork.no> Jasper den Hertog writes: > This feature was disabled per accident. It has been revived, I believe there used to be a NSID column in the last results listed on the "Probes" tab of DNS measurements too? Was this also removed by accident? Or is my memory failing me? Bj?rn From hsalgado at nic.cl Wed Nov 21 14:27:18 2018 From: hsalgado at nic.cl (Hugo =?iso-8859-1?Q?Salgado-Hern=E1ndez?=) Date: Wed, 21 Nov 2018 10:27:18 -0300 Subject: [atlas] DNS Measurement Grouping by NSID In-Reply-To: <877eh68wqh.fsf@miraculix.mork.no> References: <20181120203849.nzhopvk4gatpnu2p@nic.cl> <4866D155-6B36-44EA-B93D-11C3AA6A92F4@ripe.net> <877eh68wqh.fsf@miraculix.mork.no> Message-ID: <20181121132715.ot76crphzfjzkk3m@nic.cl> On 13:02 21/11, Bj?rn Mork wrote: > Jasper den Hertog writes: > > > This feature was disabled per accident. It has been revived, > > I believe there used to be a NSID column in the last results listed on > the "Probes" tab of DNS measurements too? Was this also removed by > accident? Or is my memory failing me? Mmm I don't think so. I remember only the map filter. Thanks Jasper! Hugo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From klaus.mailinglists at pernau.at Fri Nov 23 11:47:03 2018 From: klaus.mailinglists at pernau.at (Klaus Darilion) Date: Fri, 23 Nov 2018 11:47:03 +0100 Subject: [atlas] DNS Measurement Grouping by NSID In-Reply-To: <4866D155-6B36-44EA-B93D-11C3AA6A92F4@ripe.net> References: <20181120203849.nzhopvk4gatpnu2p@nic.cl> <4866D155-6B36-44EA-B93D-11C3AA6A92F4@ripe.net> Message-ID: <4c364e0b-64c9-b500-d68b-d8254e4efbcd@pernau.at> Thanks Klaus Am 21.11.2018 um 11:17 schrieb Jasper den Hertog: > hi RIPE Atlas people, > > This feature was disabled per accident. It has been revived, > > greetings, > > Jasper den Hertog > RIPE Atlas team > > > >> On 20 Nov 2018, at 21:38, Hugo Salgado-Hern?ndez wrote: >> >> On 10:35 08/11, Klaus Darilion wrote: >>> Hi! >>> >>> IIRC, the map of the DNS measurement allowed to group the dataset by NSID. >>> Was this feature removed? OR is it now somewhere else? I.e.: >> >> +1 >> It was very useful! >> >> Hugo >> > From anandb at ripe.net Wed Nov 28 14:34:51 2018 From: anandb at ripe.net (Anand Buddhdev) Date: Wed, 28 Nov 2018 14:34:51 +0100 Subject: [atlas] Minor change to Atlas anchor DNS resolver configuration Message-ID: Dear colleagues, Each RIPE Atlas anchor runs a DNS resolver. This resolver is configured as the primary resolver for the anchor, with the following directive at the top of the resolver configuration (/etc/resolv.conf): nameserver 127.0.0.1 For ease of configuration management, we are changing this directive to: nameserver ::1 This change will not affect DNS resolution on the anchors in any way. However, any measurement that does DNS lookups using the anchor's primary resolver will contain "::1" instead of "127.0.0.1" in "src_addr" field of results. If you're using any code to parse such results, and specifically looking for "127.0.0.1", you'll need to adjust your code to also look for "::1". Regards, Anand Buddhdev RIPE NCC From klaus.mailinglists at pernau.at Fri Nov 30 08:30:57 2018 From: klaus.mailinglists at pernau.at (Klaus Darilion) Date: Fri, 30 Nov 2018 08:30:57 +0100 Subject: [atlas] DNS Measurement Grouping by NSID In-Reply-To: <4866D155-6B36-44EA-B93D-11C3AA6A92F4@ripe.net> References: <20181120203849.nzhopvk4gatpnu2p@nic.cl> <4866D155-6B36-44EA-B93D-11C3AA6A92F4@ripe.net> Message-ID: <46483628-b83d-23a5-e2dd-6a353a507a7c@pernau.at> There is stilll an issue: it does not work to select NSID and then enter the aggregator (and pressing Enter or whatever). After entering an aggregator, I have to change the dataset for the aggregator to become active. regards Klaus Am 21.11.2018 um 11:17 schrieb Jasper den Hertog: > hi RIPE Atlas people, > > This feature was disabled per accident. It has been revived, > > greetings, > > Jasper den Hertog > RIPE Atlas team > > > >> On 20 Nov 2018, at 21:38, Hugo Salgado-Hern?ndez wrote: >> >> On 10:35 08/11, Klaus Darilion wrote: >>> Hi! >>> >>> IIRC, the map of the DNS measurement allowed to group the dataset by NSID. >>> Was this feature removed? OR is it now somewhere else? I.e.: >> >> +1 >> It was very useful! >> >> Hugo >> >