From rustrict at gmail.com Sun Sep 1 11:41:29 2019 From: rustrict at gmail.com (Alexey Troshchanovich) Date: Sun, 1 Sep 2019 12:41:29 +0300 Subject: [atlas] User Tags missing [ProbeTag object] In-Reply-To: <07256d7d-d996-1fc8-3bf0-ea00b2390ee1@wanadoo.fr> References: <20190827131641.461BF6A8@centrum.cz> <7560a8c9-3e22-830d-b5ea-f23c3b75c2bc@ripe.net> <07256d7d-d996-1fc8-3bf0-ea00b2390ee1@wanadoo.fr> Message-ID: Hello team, Unfortunately, in "Messages" (https://atlas.ripe.net/messages/) system tags are still displayed as "ProbeTag object". Your probe #xxxxx was automatically tagged (or untagged) as "ProbeTag > object" > Could you also have a look at "Sponsored by: Sponsor object" in the list of anchors? Thank you. Alexey On Tue, Aug 27, 2019 at 6:09 PM yves croison wrote: > at home it's good I found my tags. > thank you > Le 27/08/2019 ? 15:48, Chris Amin a ?crit : > > Dear Jiri, > > Thanks for reporting this. It has now been fixed, so tags should display > as normal! > > Regards, > Chris Amin > RIPE NCC > > On 27/08/2019 13:16, ripe at brite.cz wrote: > > Hi team, > all User Tags on all probes I checked are showing string "ProbeTag object" only. > Please have a look. > > Thank you > Jiri > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hsalgado at nic.cl Mon Sep 2 16:37:35 2019 From: hsalgado at nic.cl (Hugo Salgado) Date: Mon, 2 Sep 2019 10:37:35 -0400 Subject: [atlas] Measurement with msm probe type isn't working In-Reply-To: References: <20190829143757.oe3brilo7rlfrr7z@nic.cl> Message-ID: <20190902143735.emuozp75ppa5m34q@nic.cl> Hi Jasper. I was told privately that was fixed, and can confirm it's working now! Thanks a lot for your promptly help. Best, Hugo On 12:15 30/08, Jasper den Hertog wrote: > hi Hugo, > > Thanks for this feedback, I can confirm this is a bug. I was able to reproduce this. > > You?ve hit (regression) bug, probably due to (massive) changes we have made to our backends recently. > > We have started figuring out what causes this and come up with a solution. I?ll keep you posted on progress we?re making. > > Sorry for the inconvenience this has caused, > > greetings, > > Jasper den Hertog > > > On 29 Aug 2019, at 16:37, Hugo Salgado wrote: > > > > Dear Atlas team. > > I have a script to launch a new measurement using an old measurement > > list of probes ids, using type:msm. This script worked ok several > > times (last time like 1 month ago), but now it gives me the error: > > > > {"error":{"detail":"There was a problem with your request","status":400,"title":"Bad > > Request","code":102,"errors":[{"source":{"pointer":"/probes/0/value"},"detail":"The > > measurement you selected for your probe request does not exist"}]}} > > > > However I still can see the old measurement on the web page! > > > > I solved it downloading the list of probes using a GET to > > https://atlas.ripe.net/api/v2/measurements//?fields=probes' > > and then giving the complete probes list to my script. > > > > Is there any recent change with the type:msm call? > > > > Thanks, > > > > Hugo > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From robert at ripe.net Tue Sep 3 09:57:46 2019 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 3 Sep 2019 09:57:46 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> Message-ID: <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> > Still no one has answered why ripe is using self signed certs for anchor > when they can use let's encrypt for free... TL;DR if the community prefers it we use LE (+TLSA). This comes with the expense of some one-time and ongoing operational work. Considering that anchors don't host any sensitive information, using self-signed certs (+TLSA) was so far considered good enough. Regards, Robert From mike.oghia at gmail.com Tue Sep 3 11:00:42 2019 From: mike.oghia at gmail.com (Michael J. Oghia) Date: Tue, 3 Sep 2019 11:00:42 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> Message-ID: Hi Robert, all: As a disclaimer, I'm not an engineer/programmer, so I don't know all the technical specifications. However, I am a big advocate for Let's Encrypt, and think it sends a strong message about the service they offer if the RIPE community and NCC endorses them for our networks and infrastructure. So, take my vote with a grain of salt, but I say let's do it (barring any kind of technical issue that I'm simply not aware of). Best, -Michael On Tue, Sep 3, 2019 at 9:58 AM Robert Kisteleki wrote: > > > Still no one has answered why ripe is using self signed certs for anchor > > when they can use let's encrypt for free... > > TL;DR if the community prefers it we use LE (+TLSA). > > This comes with the expense of some one-time and ongoing operational > work. Considering that anchors don't host any sensitive information, > using self-signed certs (+TLSA) was so far considered good enough. > > Regards, > Robert > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shane at time-travellers.org Tue Sep 3 11:17:39 2019 From: shane at time-travellers.org (Shane Kerr) Date: Tue, 3 Sep 2019 11:17:39 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> Message-ID: Robert, On 03/09/2019 09.57, Robert Kisteleki wrote: > >> Still no one has answered why ripe is using self signed certs for anchor >> when they can use let's encrypt for free... > > TL;DR if the community prefers it we use LE (+TLSA). > > This comes with the expense of some one-time and ongoing operational > work. Considering that anchors don't host any sensitive information, > using self-signed certs (+TLSA) was so far considered good enough. Sorry for asking this question so late in this thread, but what exactly are the certificates used for? The value of a certificate from a certificate authority is that you outsource the work of establishing a trust relationship. If you're connecting bits of networking infrastructure together, presumably one's provisioning tools can configure each component with exactly the secrets and trust needed, so self-signed certificates should be fine (or better, since the system is simpler and there is no dependency on external infrastructure). If the use case under discussion is to help RIPE anchor operators (or others) to see some status page on the anchor itself via a browser, then using a "real" certificate might make sense. Otherwise, I don't see the point. Cheers, -- Shane From robert at ripe.net Tue Sep 3 11:38:33 2019 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 3 Sep 2019 11:38:33 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> Message-ID: On 2019-09-03 11:17, Shane Kerr wrote: > Robert, > > On 03/09/2019 09.57, Robert Kisteleki wrote: >> >>> Still no one has answered why ripe is using self signed certs for anchor >>> when they can use let's encrypt for free... >> >> TL;DR if the community prefers it we use LE (+TLSA). >> >> This comes with the expense of some one-time and ongoing operational >> work. Considering that anchors don't host any sensitive information, >> using self-signed certs (+TLSA) was so far considered good enough. > > Sorry for asking this question so late in this thread, but what exactly > are the certificates used for? The anchors provide very basic services intended to help users who want to use the anchors as measurement targets. They answer incoming ping, DNS and HTTP(S) queries (see https://atlas.ripe.net/docs/anchors/). The HTTP(S) service can respond with pages of various sizes which is intended to help PMTUD tests for example. It's possible that someone would want to check the TLS certificate of the measured anchor, in which case a "proper" certificate may come handy. Regards, Robert From dfk at ripe.net Tue Sep 3 12:18:39 2019 From: dfk at ripe.net (Daniel Karrenberg) Date: Tue, 03 Sep 2019 12:18:39 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> Message-ID: <35175065-C024-402F-8B34-E3DA69088A2E@ripe.net> > On 3 Sep 2019, at 11:38, Robert Kisteleki wrote: > On 2019-09-03 11:17, Shane Kerr wrote: >> ? >> Sorry for asking this question so late in this thread, but what >> exactly >> are the certificates used for? > > The anchors provide very basic services intended to help users who > want > to use the anchors as measurement targets. They answer incoming ping, > DNS and HTTP(S) queries (see https://atlas.ripe.net/docs/anchors/). > The > HTTP(S) service can respond with pages of various sizes which is > intended to help PMTUD tests for example. > > It's possible that someone would want to check the TLS certificate of > the measured anchor, in which case a "proper" certificate may come > handy. > > Regards, > Robert Going back to J?hann, who brought this up: ?Using a self signed certificate in today's age act's as an indicator that the security on the device or server in use might be in question ? and thus can negatively impact the anchor hosting provider security grade, which may lead to anchors having to be removed from data centers to prevent them from negatively affect corporation's security ratings.? So we have devices that expose the https port and respond with a self signed cert. Any security audit will flag that. Rather than explain to the auditors that there is no ?real? http service here, it is a measurement device, ? J?hann suggests to put an acceptably signed cert there. To me this sounds like a no-brainer to make life easier for anchor hosts and not an ideological issue about which CA to use or about other methods of securing https. So can we deploy certs that will satisfy the security audit and get on with life? Daniel From abscoco at gmail.com Tue Sep 3 13:12:29 2019 From: abscoco at gmail.com (Sylvain BAYA) Date: Tue, 3 Sep 2019 12:12:29 +0100 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> Message-ID: <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> Hi all, Le 9/3/2019 ? 10:00 AM, Michael J. Oghia a ?crit?: > Hi Robert, all: > > As a disclaimer, I'm not an engineer/programmer, so I don't know all > the technical specifications. However, I am a big advocate for Let's > Encrypt, and think it sends a strong message about the service they > offer if the RIPE community and NCC endorses them for our networks and > infrastructure. So, take my vote I second this, and i also support the main *alert* raised by J?hann. ...i can add this : if there is a technical issue (not impossible) in using LE certs the same way the actual solution is used on RIPE Anchors, then perhaps, preferably, RIPE *should* contribute to fund whatever necessary to solve the problem on LE side or internally. ...so : where to take the money ?? simply reorientate a part of the money used for the actual solution :-/ Thanks. Shalom, --sb. > with a grain of salt, but I say let's do it (barring any kind of > technical issue that I'm simply not aware of).? > > Best, > -Michael > > > On Tue, Sep 3, 2019 at 9:58 AM Robert Kisteleki > wrote: > > > [...] > -- Regards, Sylvain B. __ Website : Wiki : Surveys : Subscribe to Mailing List : Mailing List's Archives : -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x0387408365AC8594.asc Type: application/pgp-keys Size: 4826 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From carsten at schiefner.de Tue Sep 3 13:24:23 2019 From: carsten at schiefner.de (Carsten Schiefner) Date: Tue, 3 Sep 2019 13:24:23 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> Message-ID: <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> Sylvain, all - On 03.09.2019 13:12, Sylvain BAYA wrote: > [...] > > ...i can add this : if there is a technical issue (not impossible) in > using LE certs the same > way the actual solution is used on RIPE Anchors, then perhaps, > preferably, RIPE *should* > contribute to fund whatever necessary to solve the problem on LE side or > internally. indeed there is: one way to use Letsencrypt certificates is to have them automagically renewd every 90 days or so. This works like a charm on my host. The tricky bit, however, comes if you want to use this very certificate in a TLSA RR as well: all of a sudden the RR points to a non-existing certificate when Letsencrypt's cron job has flipped the certificate. I haven't yet really gotten my head around it - but maybe the NCC could and would?! 8-) Chers, -C. From bjorn at mork.no Tue Sep 3 13:35:16 2019 From: bjorn at mork.no (=?utf-8?Q?Bj=C3=B8rn_Mork?=) Date: Tue, 03 Sep 2019 13:35:16 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> (Carsten Schiefner's message of "Tue, 3 Sep 2019 13:24:23 +0200") References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> Message-ID: <878sr5zk7f.fsf@miraculix.mork.no> Carsten Schiefner writes: > The tricky bit, however, comes if you want to use this very certificate > in a TLSA RR as well: all of a sudden the RR points to a non-existing > certificate when Letsencrypt's cron job has flipped the certificate. > > I haven't yet really gotten my head around it - but maybe the NCC could > and would?! 8-) You can renew Let's Encrypt certificates without changing the key. And if you use the recommended 3 1 1 TLSA records, then you don't have to change it unless the key is changed. Bj?rn From abscoco at gmail.com Tue Sep 3 13:55:38 2019 From: abscoco at gmail.com (Sylvain BAYA) Date: Tue, 3 Sep 2019 12:55:38 +0100 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> Message-ID: Hi all, Le 9/3/2019 ? 12:24 PM, Carsten Schiefner a ?crit?: > Sylvain, all - > > On 03.09.2019 13:12, Sylvain BAYA wrote: >> [...] > indeed there is: one way to use Letsencrypt certificates is to have them > automagically renewd every 90 days or so. > > This works like a charm on my host. > > The tricky bit, however, comes if you want to use this very certificate > in a TLSA RR as well: all of a sudden the RR points to a non-existing > certificate when Letsencrypt's cron job has flipped the certificate. Dear Carsten, Thanks for pointing this clear issue here :-) ...do you think it is a configuration issue or a technical (conceptual) one ? I suppose that you have already pointed it to the LE team :-/ > I haven't yet really gotten my head around it - but maybe the NCC could > and would?! 8-) ...you might have a great support now, if RIPE NCC accepts (if need be) to jump in ;-) Shalom, --sb. > Chers, > > -C. -- Regards, Sylvain B. __ Website : Wiki : Surveys : Subscribe to Mailing List : Mailing List's Archives : -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x0387408365AC8594.asc Type: application/pgp-keys Size: 4826 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From carsten at schiefner.de Tue Sep 3 14:34:10 2019 From: carsten at schiefner.de (Carsten Schiefner) Date: Tue, 3 Sep 2019 14:34:10 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <878sr5zk7f.fsf@miraculix.mork.no> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> <878sr5zk7f.fsf@miraculix.mork.no> Message-ID: <45E6D8BB-6DBC-424A-AF54-C7F45E680A32@schiefner.de> Hi Bj?rn, > Am 03.09.2019 um 13:35 schrieb Bj?rn Mork : >> The tricky bit, however, comes if you want to use this very certificate >> in a TLSA RR as well: all of a sudden the RR points to a non-existing >> certificate when Letsencrypt's cron job has flipped the certificate. >> >> [...] > > You can renew Let's Encrypt certificates without changing the key. And > if you use the recommended 3 1 1 TLSA records, then you don't have to > change it unless the key is changed. ah! :-) Would you have a specific pointer in mind you?d recommend and so like to share? Thanks & best, -C. From abscoco at gmail.com Tue Sep 3 14:49:41 2019 From: abscoco at gmail.com (Sylvain BAYA) Date: Tue, 3 Sep 2019 13:49:41 +0100 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <45E6D8BB-6DBC-424A-AF54-C7F45E680A32@schiefner.de> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> <878sr5zk7f.fsf@miraculix.mork.no> <45E6D8BB-6DBC-424A-AF54-C7F45E680A32@schiefner.de> Message-ID: <6d149e87-c6e6-41d3-85f1-8c25839e6f9c@gmail.com> Hi all, Le 9/3/2019 ? 1:34 PM, Carsten Schiefner a ?crit?: >>> [...] >> You can renew Let's Encrypt certificates without changing the key. And >> if you use the recommended 3 1 1 TLSA records, then you don't have to >> change it unless the key is changed. > ah! :-) > > Would you have a specific pointer in mind you?d recommend and so like to share? Dear Carsten, ...i've started to read this one. Hope you will find it relevant. Thanks. Shalom, --sb. > > Thanks & best, > > -C. > -- Regards, Sylvain B. __ Website : Wiki : Surveys : Subscribe to Mailing List : Mailing List's Archives : -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x0387408365AC8594.asc Type: application/pgp-keys Size: 4826 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From bjorn at mork.no Tue Sep 3 14:50:28 2019 From: bjorn at mork.no (=?utf-8?Q?Bj=C3=B8rn_Mork?=) Date: Tue, 03 Sep 2019 14:50:28 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <45E6D8BB-6DBC-424A-AF54-C7F45E680A32@schiefner.de> (Carsten Schiefner's message of "Tue, 3 Sep 2019 14:34:10 +0200") References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> <878sr5zk7f.fsf@miraculix.mork.no> <45E6D8BB-6DBC-424A-AF54-C7F45E680A32@schiefner.de> Message-ID: <87lfv5y25n.fsf@miraculix.mork.no> Carsten Schiefner writes: >> Am 03.09.2019 um 13:35 schrieb Bj?rn Mork : >>> The tricky bit, however, comes if you want to use this very certificate >>> in a TLSA RR as well: all of a sudden the RR points to a non-existing >>> certificate when Letsencrypt's cron job has flipped the certificate. >>> >>> [...] >> >> You can renew Let's Encrypt certificates without changing the key. And >> if you use the recommended 3 1 1 TLSA records, then you don't have to >> change it unless the key is changed. > > ah! :-) > > Would you have a specific pointer in mind you?d recommend and so like to share? I believe this covers it: https://community.letsencrypt.org/t/please-avoid-3-0-1-and-3-0-2-dane-tlsa-records-with-le-certificates/7022 And RFC 7671 is also a nice reference, especially if you want to roll keys. Bj?rn From jterbeest at ripe.net Tue Sep 3 14:51:41 2019 From: jterbeest at ripe.net (Johan ter Beest) Date: Tue, 3 Sep 2019 14:51:41 +0200 Subject: [atlas] User Tags missing [ProbeTag object] In-Reply-To: References: <20190827131641.461BF6A8@centrum.cz> <7560a8c9-3e22-830d-b5ea-f23c3b75c2bc@ripe.net> <07256d7d-d996-1fc8-3bf0-ea00b2390ee1@wanadoo.fr> Message-ID: Hi Alexey, > On 1 Sep 2019, at 11:41, Alexey Troshchanovich wrote: > > Hello team, > > Unfortunately, in "Messages" (https://atlas.ripe.net/messages/ ) system tags are still displayed as "ProbeTag object". > > Your probe #xxxxx was automatically tagged (or untagged) as "ProbeTag object" > > Could you also have a look at "Sponsored by: Sponsor object" in the list of anchors? These issues have now also been fixed, thank you for reporting :) Please note that in the case of the messages, you will still see ProbeTag object for the older entries, but newer entries should show the actual tag name again. The root cause of these issues was upgrading our code base from Python 2.7 to Python 3.6. They were only display issues as Python 3 handles unicode strings differently than Python 2 Kind regards, Johan ter Beest RIPE NCC > > Thank you. > > Alexey > > On Tue, Aug 27, 2019 at 6:09 PM yves croison > wrote: > at home it's good I found my tags. > thank you > Le 27/08/2019 ? 15:48, Chris Amin a ?crit : >> Dear Jiri, >> >> Thanks for reporting this. It has now been fixed, so tags should display >> as normal! >> >> Regards, >> Chris Amin >> RIPE NCC >> >> On 27/08/2019 13:16, ripe at brite.cz wrote: >>> Hi team, >>> all User Tags on all probes I checked are showing string "ProbeTag object" only. >>> Please have a look. >>> >>> Thank you >>> Jiri >>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2634 bytes Desc: not available URL: From carsten at schiefner.de Tue Sep 3 15:10:03 2019 From: carsten at schiefner.de (Carsten Schiefner) Date: Tue, 3 Sep 2019 15:10:03 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <45E6D8BB-6DBC-424A-AF54-C7F45E680A32@schiefner.de> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> <878sr5zk7f.fsf@miraculix.mork.no> <45E6D8BB-6DBC-424A-AF54-C7F45E680A32@schiefner.de> Message-ID: <3c483936-dd49-4821-a587-345b2ede9da2.maildroid@localhost> [https://community.letsencrypt.org/t/please-avoid-3-0-1-and-3-0-2-dane-tlsa-records-with-le-certificates/7022] Thanks, Sylvain and Bj?rn! -- Von meinem Android-Ger?t gesendet. -----Original Message----- From: Carsten Schiefner To: "Bj?rn Mork" Cc: ripe-atlas at ripe.net Sent: Di., 03 Sep. 2019 14:34 Subject: Re: [atlas] SSL Certificates for ripe anchors Hi Bj?rn, > Am 03.09.2019 um 13:35 schrieb Bj?rn Mork : >> The tricky bit, however, comes if you want to use this very certificate >> in a TLSA RR as well: all of a sudden the RR points to a non-existing >> certificate when Letsencrypt's cron job has flipped the certificate. >> >> [...] > > You can renew Let's Encrypt certificates without changing the key. And > if you use the recommended 3 1 1 TLSA records, then you don't have to > change it unless the key is changed. ah! :-) Would you have a specific pointer in mind you?d recommend and so like to share? Thanks & best, -C. From dfk at ripe.net Tue Sep 3 16:55:06 2019 From: dfk at ripe.net (Daniel Karrenberg) Date: Tue, 03 Sep 2019 16:55:06 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <3c483936-dd49-4821-a587-345b2ede9da2.maildroid@localhost> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <6a83ce88-de7a-a874-379e-664d08ac6302@gmail.com> <6e43255d-e57d-5b5e-e10e-b64c6cb45cab@schiefner.de> <878sr5zk7f.fsf@miraculix.mork.no> <45E6D8BB-6DBC-424A-AF54-C7F45E680A32@schiefner.de> <3c483936-dd49-4821-a587-345b2ede9da2.maildroid@localhost> Message-ID: On 3 Sep 2019, at 15:10, Carsten Schiefner wrote: > [https://community.letsencrypt.org/t/please-avoid-3-0-1-and-3-0-2-dane-tlsa-records-with-le-certificates/7022] > > Thanks, Sylvain and Bj?rn! And of course ?our own? Jan ?or? explains this quite well too: https://www.internetsociety.org/blog/2016/01/lets-encrypt-certificates-for-mail-servers-and-dane-part-1-of-2/ From randy at psg.com Tue Sep 3 17:03:33 2019 From: randy at psg.com (Randy Bush) Date: Tue, 03 Sep 2019 08:03:33 -0700 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> Message-ID: been using LE+TLSA for a loooong time. like 94 of us, i have recipies (for LE for sites w/o web services) if you need them. please do it. it's prudent. randy From robert at ripe.net Wed Sep 4 12:00:09 2019 From: robert at ripe.net (Robert Kisteleki) Date: Wed, 4 Sep 2019 12:00:09 +0200 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> Message-ID: <8bb5730d-9b65-c310-3199-41e070ffcbcd@ripe.net> On 2019-09-03 17:03, Randy Bush wrote: > been using LE+TLSA for a loooong time. like 94 of us, i have recipies > (for LE for sites w/o web services) if you need them. please do it. > it's prudent. > > randy Thank you Randy for the offer! We'll check what it takes to add this to the anchors, and report back soon. Regards, Robert From BECHA at ripe.net Wed Sep 4 17:04:08 2019 From: BECHA at ripe.net (Vesna Manojlovic) Date: Wed, 4 Sep 2019 17:04:08 +0200 Subject: [atlas] Apply for next RIPE NCC hackathons, in six locations! Message-ID: <444cf4d7-d765-a42b-9138-1e0e363612eb@ripe.net> Dear colleagues, as our tenth event, we are hosting our first IoT-themed hackathon (Internet of Things) on the weekend of 12-13 October in Rotterdam: https://labs.ripe.net/Members/becha/iot-hackathon-at-ripe-79-in-rotterdam This is planned for the weekend just before RIPE 79: http://ripe79.ripe.net You can apply at: https://www.ripe.net/participate/forms/apply/iot-hackathon-rotterdam-2019/ The application deadline is *9 September 2019*. Shortly after that, for the first time ever, we are holding the hackathon simultaneously in five connected 'nodes' across Europe: Delft, Dublin, Padua, Paris and Sarajevo! Topic is Quantum Internet, and dates 5 & 6 November. The first application deadline is *15 September 2019*. This will probably be extended due to the summer & academic holidays. You can find more information about the event on RIPE Labs: https://labs.ripe.net/Members/ulka_athale_1/take-part-in-pan-european-quantum-internet-hackathon You can apply at: https://www.ripe.net/participate/forms/apply/peqi/ Warm regards, Vesna Manojlovic Community Builder RIPE NCC From marcel.flores at verizondigitalmedia.com Wed Sep 4 18:04:20 2019 From: marcel.flores at verizondigitalmedia.com (Marcel Flores) Date: Wed, 4 Sep 2019 09:04:20 -0700 Subject: [atlas] SSL Certificates for ripe anchors In-Reply-To: <8bb5730d-9b65-c310-3199-41e070ffcbcd@ripe.net> References: <82d32656-fe5d-17c7-4dff-0212ea8c9b60@ripe.net> <16811fdc-55e0-bc07-6500-e2d40c82c064@nic.cz> <0B3E152F-6D39-4CFD-B52F-012E91E682BD@steffann.nl> <874l1ysdte.fsf@miraculix.mork.no> <93ccdf0a-b038-d55a-f15a-c7b0b5305751@ripe.net> <8bb5730d-9b65-c310-3199-41e070ffcbcd@ripe.net> Message-ID: Just to weigh in as both an Anchor host and a heavy Atlas user: we've found the self-signed certificates to be a non-issue. While I will not deny that they do show up in many internal security scans, self-signed certs fall well below other "issues" such as open ports, non-standard responses to version.bind queries, and strange traffic patterns. Such concerns are, however, mitigated by the understanding that the anchors are measurement points, and therefore may generate, and be subject to, non-standard (or perceived as traditionally insecure) behaviors. I can appreciate that there may be measurements (*i.e. *using the platform) that would be made easier with non-self-signed certificates, but I'm not sure I've seen that discussed here. -m On Wed, Sep 4, 2019 at 3:00 AM Robert Kisteleki wrote: > > On 2019-09-03 17:03, Randy Bush wrote: > > been using LE+TLSA for a loooong time. like 94 of us, i have recipies > > (for LE for sites w/o web services) if you need them. please do it. > > it's prudent. > > > > randy > > Thank you Randy for the offer! > > We'll check what it takes to add this to the anchors, and report back soon. > > Regards, > Robert > > -- *Marcel Flores, PhD* | Sr. Research Scientist research.verizondigitalmedia.com | AS15133 e: marcel.flores at verizondigitalmedia.com 13031 W Jefferson Blvd. Building 900, Los Angeles, CA 90094 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bortzmeyer at nic.fr Sun Sep 8 18:53:12 2019 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Sun, 8 Sep 2019 18:53:12 +0200 Subject: [atlas] DNS issue with Atlas or with the ISP? Message-ID: <20190908165311.6psia2rqiqxc2ovz@sources.org> RIPE Atlas Web site displays a lot of "undefined" for the tests in AS 3125. See for instance or But the DNS resolution from this AS seems to work. Checking the raw results in JSON, I see that we have a lot of failures on one IPv6 resolver: "dst_name": "fe80::a63e:51ff:fe77:e26", "error": { "socket": "connect failed Invalid argument" }, We do not see such IPv6 problem in other AS (see for instance ) I assume that the "connect failed Invalid argument" is the fault of the ISP, which advertises a wrong DNS resolver? Or is the Atlas probe unable to query link-local addresses for DNS resolution? Even if it is so, is it a good idea for the Atlas Web site to display "undefined" where the raw results show that other resolvers worked? From bortzmeyer at nic.fr Mon Sep 9 09:39:16 2019 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Mon, 9 Sep 2019 09:39:16 +0200 Subject: [atlas] DNS issue with Atlas or with the ISP? In-Reply-To: <20190908165311.6psia2rqiqxc2ovz@sources.org> References: <20190908165311.6psia2rqiqxc2ovz@sources.org> Message-ID: <20190909073915.kgl6r3ths33gutmf@nic.fr> On Sun, Sep 08, 2019 at 06:53:12PM +0200, Stephane Bortzmeyer wrote a message of 26 lines which said: > I assume that the "connect failed Invalid argument" is the fault of > the ISP, which advertises a wrong DNS resolver? Or is the Atlas probe > unable to query link-local addresses for DNS resolution? So, people have tested, and confirm that 1) this ISP advertises link-local address via RA 2) it works with all DNS clients, but the RIPE Atlas probes. Any idea? From bjorn at mork.no Mon Sep 9 12:25:38 2019 From: bjorn at mork.no (=?utf-8?Q?Bj=C3=B8rn_Mork?=) Date: Mon, 09 Sep 2019 12:25:38 +0200 Subject: [atlas] DNS issue with Atlas or with the ISP? In-Reply-To: <20190909073915.kgl6r3ths33gutmf@nic.fr> (Stephane Bortzmeyer's message of "Mon, 9 Sep 2019 09:39:16 +0200") References: <20190908165311.6psia2rqiqxc2ovz@sources.org> <20190909073915.kgl6r3ths33gutmf@nic.fr> Message-ID: <87tv9lwyu5.fsf@miraculix.mork.no> Stephane Bortzmeyer writes: > On Sun, Sep 08, 2019 at 06:53:12PM +0200, > Stephane Bortzmeyer wrote > a message of 26 lines which said: > >> I assume that the "connect failed Invalid argument" is the fault of >> the ISP, which advertises a wrong DNS resolver? Or is the Atlas probe >> unable to query link-local addresses for DNS resolution? > > So, people have tested, and confirm that 1) this ISP advertises > link-local address via RA 2) it works with all DNS clients, but the > RIPE Atlas probes. Any idea? The first thing to sort out is if the probe RDNSS handler is RFC8106 compliant. For an LL address to work, we obviously need to know which link. And this means that the handler must know that LL addresses are special. Quoting https://tools.ietf.org/html/rfc8106#section-5.1 : Note: The addresses for RDNSSes in the RDNSS option MAY be link-local addresses. Such link-local addresses SHOULD be registered in the Resolver Repository along with the corresponding link zone indices of the links that receive the RDNSS option(s) for them. The link-local addresses MAY be represented in the Resolver Repository with their link zone indices in the textual format for scoped addresses as described in [RFC4007]. When a resolver sends a DNS query message to an RDNSS identified by a link-local address, it MUST use the corresponding link. I looked quickly at an old copy of networking/rptra6.c, and it doesn't look like it is doing this. I could be wrong or it could be fixed in a more recent probe firmware. But this is where I'd start to look. BTW, I seriously doubt that *all* other DNS and RDNSS clients got this right. Advertising LL DNS servers seems unnecessary risky outside of the lab. How much does a global IPv6 address cost these days? Bj?rn From philip.homburg at ripe.net Mon Sep 9 13:06:48 2019 From: philip.homburg at ripe.net (Philip Homburg) Date: Mon, 9 Sep 2019 13:06:48 +0200 Subject: [atlas] DNS issue with Atlas or with the ISP? In-Reply-To: <20190909073915.kgl6r3ths33gutmf@nic.fr> References: <20190908165311.6psia2rqiqxc2ovz@sources.org> <20190909073915.kgl6r3ths33gutmf@nic.fr> Message-ID: <041f65f2-fb5d-7ff6-c8f0-d79fc9b47e4f@ripe.net> On 2019/09/09 9:39 , Stephane Bortzmeyer wrote: > So, people have tested, and confirm that 1) this ISP advertises > link-local address via RA 2) it works with all DNS clients, but the > RIPE Atlas probes. Any idea? I just tried a bare link local address with dig on FreeBSD and it failed. For some reason my attempts on a few linux VMs failed for completely different reasons. The problem is that for a link local address you need a scope. The Atlas measurement code doesn't know how to add one and the addresses in /etc/resolv.conf don't have one. I sort of knew that this was going to be a problem, but link local for the resolvers seems to be quite rare. I'll make a note to see if I can make it work somehow. Philip From bortzmeyer at nic.fr Mon Sep 9 13:18:44 2019 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Mon, 9 Sep 2019 13:18:44 +0200 Subject: [atlas] DNS issue with Atlas or with the ISP? In-Reply-To: <041f65f2-fb5d-7ff6-c8f0-d79fc9b47e4f@ripe.net> References: <20190908165311.6psia2rqiqxc2ovz@sources.org> <20190909073915.kgl6r3ths33gutmf@nic.fr> <041f65f2-fb5d-7ff6-c8f0-d79fc9b47e4f@ripe.net> Message-ID: <20190909111844.s7ew6ahknoa6pfr7@nic.fr> On Mon, Sep 09, 2019 at 01:06:48PM +0200, Philip Homburg wrote a message of 20 lines which said: > The problem is that for a link local address you need a scope. The > Atlas measurement code doesn't know how to add one and the addresses > in /etc/resolv.conf don't have one. I was, too, surprised that it works but some people tested with dig or drill (I assume it was on monohomed machines, which is the case of RIPE Atlas probes) and it worked. Note that RFC 8106 explicitely authorizes it: Note: The addresses for RDNSSes in the RDNSS option MAY be link-local addresses. Such link-local addresses SHOULD be registered in the Resolver Repository along with the corresponding link zone indices of the links that receive the RDNSS option(s) for them. The link-local addresses MAY be represented in the Resolver Repository with their link zone indices in the textual format for scoped addresses as described in [RFC4007]. When a resolver sends a DNS query message to an RDNSS identified by a link-local address, it MUST use the corresponding link. From bortzmeyer at nic.fr Mon Sep 9 16:48:19 2019 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Mon, 9 Sep 2019 16:48:19 +0200 Subject: [atlas] DNS issue with Atlas or with the ISP? In-Reply-To: <87tv9lwyu5.fsf@miraculix.mork.no> References: <20190908165311.6psia2rqiqxc2ovz@sources.org> <20190909073915.kgl6r3ths33gutmf@nic.fr> <87tv9lwyu5.fsf@miraculix.mork.no> Message-ID: <20190909144819.unijcv6fmm77hflo@nic.fr> On Mon, Sep 09, 2019 at 12:25:38PM +0200, Bj?rn Mork wrote a message of 42 lines which said: > BTW, I seriously doubt that *all* other DNS and RDNSS clients got this > right. Advertising LL DNS servers seems unnecessary risky outside of > the lab. I agree that it is risky, but I'm not the CTO of this specific ISP... Anyone knows an example of another big ISP doing that? Also, there is a *rumor* (not substantiated by hard facts) that DNS resolution at this ISP experiences trouble, but I have currently no solid proof. (I was trying to use the Atlas probes for that.) From rustrict at gmail.com Mon Sep 16 11:15:11 2019 From: rustrict at gmail.com (Alexey Troshchanovich) Date: Mon, 16 Sep 2019 12:15:11 +0300 Subject: [atlas] User Tags missing [ProbeTag object] In-Reply-To: References: <20190827131641.461BF6A8@centrum.cz> <7560a8c9-3e22-830d-b5ea-f23c3b75c2bc@ripe.net> <07256d7d-d996-1fc8-3bf0-ea00b2390ee1@wanadoo.fr> Message-ID: Hi Johan, thank you for fixing. Unfortunately, nothing has changed for me in "Messages". All new messages contain "ProbeTag object" :( For example, the last two entries on this page are: 2019-09-15 16:34:02 UTC Probe auto-tagged Your probe #xxxxx was automatically tagged as "ProbeTag object" 2019-09-14 16:32:49 UTC Probe auto-untagged Your probe #xxxxx was automatically untagged as "ProbeTag object" Could you please check again? Best regards, Alexey On Tue, Sep 3, 2019 at 3:51 PM Johan ter Beest wrote: > Hi Alexey, > > On 1 Sep 2019, at 11:41, Alexey Troshchanovich wrote: > > Hello team, > > Unfortunately, in "Messages" (https://atlas.ripe.net/messages/) system > tags are still displayed as "ProbeTag object". > > Your probe #xxxxx was automatically tagged (or untagged) as "ProbeTag >> object" >> > > Could you also have a look at "Sponsored by: Sponsor object" in the list > of anchors? > > > These issues have now also been fixed, thank you for reporting :) > > Please note that in the case of the messages, you will still see ProbeTag > object for the older entries, but newer entries should show the actual tag > name again. > > The root cause of these issues was upgrading our code base from Python 2.7 > to Python 3.6. They were only display issues as Python 3 handles unicode > strings differently than Python 2 > > Kind regards, > Johan ter Beest > RIPE NCC > > > Thank you. > > Alexey > > On Tue, Aug 27, 2019 at 6:09 PM yves croison > wrote: > >> at home it's good I found my tags. >> thank you >> Le 27/08/2019 ? 15:48, Chris Amin a ?crit : >> >> Dear Jiri, >> >> Thanks for reporting this. It has now been fixed, so tags should display >> as normal! >> >> Regards, >> Chris Amin >> RIPE NCC >> >> On 27/08/2019 13:16, ripe at brite.cz wrote: >> >> Hi team, >> all User Tags on all probes I checked are showing string "ProbeTag object" only. >> Please have a look. >> >> Thank you >> Jiri >> >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jterbeest at ripe.net Mon Sep 16 11:32:32 2019 From: jterbeest at ripe.net (Johan ter Beest) Date: Mon, 16 Sep 2019 11:32:32 +0200 Subject: [atlas] User Tags missing [ProbeTag object] In-Reply-To: References: <20190827131641.461BF6A8@centrum.cz> <7560a8c9-3e22-830d-b5ea-f23c3b75c2bc@ripe.net> <07256d7d-d996-1fc8-3bf0-ea00b2390ee1@wanadoo.fr> Message-ID: <7B49CCD7-12C1-43B4-9D1E-EBCDA8E7C79B@ripe.net> Hi Alexey, > On 16 Sep 2019, at 11:15, Alexey Troshchanovich wrote: > > Hi Johan, > > thank you for fixing. Unfortunately, nothing has changed for me in "Messages". All new messages contain "ProbeTag object" :( We updated the package but did not deploy it yet to the machines that update the tags, this has now been done so starting from the next run, the tags in Messages should look normal again. Apologies for the inconvenience. Kind regards, Johan ter Beest RIPE NCC > > For example, the last two entries on this page are: > > 2019-09-15 16:34:02 UTC > Probe auto-tagged > Your probe #xxxxx was automatically tagged as "ProbeTag object" > > > 2019-09-14 16:32:49 UTC > Probe auto-untagged > Your probe #xxxxx was automatically untagged as "ProbeTag object" > > Could you please check again? > > Best regards, > Alexey > > On Tue, Sep 3, 2019 at 3:51 PM Johan ter Beest > wrote: > Hi Alexey, > >> On 1 Sep 2019, at 11:41, Alexey Troshchanovich > wrote: >> >> Hello team, >> >> Unfortunately, in "Messages" (https://atlas.ripe.net/messages/ ) system tags are still displayed as "ProbeTag object". >> >> Your probe #xxxxx was automatically tagged (or untagged) as "ProbeTag object" >> >> Could you also have a look at "Sponsored by: Sponsor object" in the list of anchors? > > These issues have now also been fixed, thank you for reporting :) > > Please note that in the case of the messages, you will still see ProbeTag object for the older entries, but newer entries should show the actual tag name again. > > The root cause of these issues was upgrading our code base from Python 2.7 to Python 3.6. They were only display issues as Python 3 handles unicode strings differently than Python 2 > > Kind regards, > Johan ter Beest > RIPE NCC > >> >> Thank you. >> >> Alexey >> >> On Tue, Aug 27, 2019 at 6:09 PM yves croison > wrote: >> at home it's good I found my tags. >> thank you >> Le 27/08/2019 ? 15:48, Chris Amin a ?crit : >>> Dear Jiri, >>> >>> Thanks for reporting this. It has now been fixed, so tags should display >>> as normal! >>> >>> Regards, >>> Chris Amin >>> RIPE NCC >>> >>> On 27/08/2019 13:16, ripe at brite.cz wrote: >>>> Hi team, >>>> all User Tags on all probes I checked are showing string "ProbeTag object" only. >>>> Please have a look. >>>> >>>> Thank you >>>> Jiri >>>> >>>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2634 bytes Desc: not available URL: From rustrict at gmail.com Wed Sep 18 09:23:54 2019 From: rustrict at gmail.com (Alexey Troshchanovich) Date: Wed, 18 Sep 2019 10:23:54 +0300 Subject: [atlas] User Tags missing [ProbeTag object] In-Reply-To: <7B49CCD7-12C1-43B4-9D1E-EBCDA8E7C79B@ripe.net> References: <20190827131641.461BF6A8@centrum.cz> <7560a8c9-3e22-830d-b5ea-f23c3b75c2bc@ripe.net> <07256d7d-d996-1fc8-3bf0-ea00b2390ee1@wanadoo.fr> <7B49CCD7-12C1-43B4-9D1E-EBCDA8E7C79B@ripe.net> Message-ID: Hi Johan, Thank you very much. It's okay now. Best regards, Alexey On Mon, Sep 16, 2019 at 12:32 PM Johan ter Beest wrote: > Hi Alexey, > > > On 16 Sep 2019, at 11:15, Alexey Troshchanovich > wrote: > > Hi Johan, > > thank you for fixing. Unfortunately, nothing has changed for me in > "Messages". All new messages contain "ProbeTag object" :( > > > We updated the package but did not deploy it yet to the machines that > update the tags, this has now been done so starting from the next run, the > tags in Messages should look normal again. > > Apologies for the inconvenience. > > Kind regards, > Johan ter Beest > RIPE NCC > > > For example, the last two entries on this page are: > > 2019-09-15 16:34:02 UTC Probe auto-tagged Your probe #xxxxx was automatically tagged as "ProbeTag object" > 2019-09-14 16:32:49 UTC Probe auto-untagged Your probe #xxxxx was automatically untagged as "ProbeTag object" > > Could you please check again? > > Best regards, > Alexey > > On Tue, Sep 3, 2019 at 3:51 PM Johan ter Beest wrote: > >> Hi Alexey, >> >> On 1 Sep 2019, at 11:41, Alexey Troshchanovich >> wrote: >> >> Hello team, >> >> Unfortunately, in "Messages" (https://atlas.ripe.net/messages/) system >> tags are still displayed as "ProbeTag object". >> >> Your probe #xxxxx was automatically tagged (or untagged) as "ProbeTag >>> object" >>> >> >> Could you also have a look at "Sponsored by: Sponsor object" in the list >> of anchors? >> >> >> These issues have now also been fixed, thank you for reporting :) >> >> Please note that in the case of the messages, you will still see ProbeTag >> object for the older entries, but newer entries should show the actual tag >> name again. >> >> The root cause of these issues was upgrading our code base from Python >> 2.7 to Python 3.6. They were only display issues as Python 3 handles >> unicode strings differently than Python 2 >> >> Kind regards, >> Johan ter Beest >> RIPE NCC >> >> >> Thank you. >> >> Alexey >> >> On Tue, Aug 27, 2019 at 6:09 PM yves croison >> wrote: >> >>> at home it's good I found my tags. >>> thank you >>> Le 27/08/2019 ? 15:48, Chris Amin a ?crit : >>> >>> Dear Jiri, >>> >>> Thanks for reporting this. It has now been fixed, so tags should display >>> as normal! >>> >>> Regards, >>> Chris Amin >>> RIPE NCC >>> >>> On 27/08/2019 13:16, ripe at brite.cz wrote: >>> >>> Hi team, >>> all User Tags on all probes I checked are showing string "ProbeTag object" only. >>> Please have a look. >>> >>> Thank you >>> Jiri >>> >>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nitinder.mohan at helsinki.fi Thu Sep 26 14:59:02 2019 From: nitinder.mohan at helsinki.fi (Mohan, Nitinder) Date: Thu, 26 Sep 2019 12:59:02 +0000 Subject: [atlas] Requesting RIPE ATLAS credits for research Message-ID: Dear all, Greetings from Finland! I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). My RIPE NCC account is . Any help would be highly appreciated. Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki https://www.nitindermohan.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at cyberinvasion.net Thu Sep 26 15:05:36 2019 From: james at cyberinvasion.net (James Gannon) Date: Thu, 26 Sep 2019 13:05:36 +0000 Subject: [atlas] Requesting RIPE ATLAS credits for research Message-ID: <523EFBEE-11E0-4DF7-89F1-29CB7ECCF976@cyberinvasion.net> Sent you a million, have fun! From: ripe-atlas on behalf of "Mohan, Nitinder" Date: Thursday, 26 September 2019 at 08:59 To: "ripe-atlas at ripe.net" Subject: [atlas] Requesting RIPE ATLAS credits for research Dear all, Greetings from Finland! I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). My RIPE NCC account is . Any help would be highly appreciated. Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki https://www.nitindermohan.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.perzi at univie.ac.at Thu Sep 26 15:09:00 2019 From: michael.perzi at univie.ac.at (Michael Perzi) Date: Thu, 26 Sep 2019 15:09:00 +0200 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: <7F1361C1-025A-448F-B453-CE24509CF895@univie.ac.at> sent you 10 million, good luck! > On 26.09.2019, at 14:59, Mohan, Nitinder wrote: > > Dear all, > > Greetings from Finland! > > I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. > > My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). > > My RIPE NCC account is . > > Any help would be highly appreciated. > > Best Regards > > Nitinder Mohan > Ph.D. student > Department of Computer Science > University of Helsinki > https://www.nitindermohan.com/ From mrp at mrp.net Thu Sep 26 15:10:55 2019 From: mrp at mrp.net (Mark Prior) Date: Thu, 26 Sep 2019 22:40:55 +0930 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: <480c397b-d7f0-b9c4-d143-0ed447e8c968@mrp.net> Sent you one million. Have fun. Mark. On 26/9/19 22:29, Mohan, Nitinder wrote: > Dear all, > > Greetings from Finland! > > I am a Ph.D. student at the University of Helsinki, Finland. I am > currently involved in a research project which is taking a critical look > at the availability and reachability of datacenters from all (or most > of) cloud providers operating worldwide. The project requires me to > conduct large-scale PING measurements to compute servers hosted in these > datacenters. However, I am a new RIPE ATLAS user and do not have any > credits to set up a measurement. Also, unfortunately, the tight timeline > of the project makes earning credits over time infeasible. > > My only option is now to ask the community to help our research. I would > highly appreciate if anyone can generously offer us RIPE ATLAS credits > to kickstart our measurements (e.g. 1 million). > > My RIPE NCC account is . > > Any help would be highly appreciated. > > Best Regards > > > Nitinder Mohan > > Ph.D. student > > Department of Computer Science > > University of Helsinki > > https://www.nitindermohan.com/ > From nitinder.mohan at helsinki.fi Thu Sep 26 15:14:07 2019 From: nitinder.mohan at helsinki.fi (Mohan, Nitinder) Date: Thu, 26 Sep 2019 13:14:07 +0000 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: Thank you everyone for your kindness and generosity. Your contribution is highly appreciated ? We will surely share the findings of our work with the community later. Thank you! Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki https://www.nitindermohan.com/ ________________________________ From: ripe-atlas on behalf of Mohan, Nitinder Sent: Thursday, September 26, 2019 3:59 PM To: ripe-atlas at ripe.net Subject: [atlas] Requesting RIPE ATLAS credits for research Dear all, Greetings from Finland! I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). My RIPE NCC account is . Any help would be highly appreciated. Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki https://www.nitindermohan.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike.oghia at gmail.com Thu Sep 26 15:59:05 2019 From: mike.oghia at gmail.com (Michael J. Oghia) Date: Thu, 26 Sep 2019 15:59:05 +0200 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: If you need anything else Nitinder, just ask. So many of us have tons of unused credits, and in my time as a member of this community, I've seen nothing but pure generosity and collegiality from everyone. It's a pleasure to be part of this! Best, -Michael On Thu, Sep 26, 2019 at 3:14 PM Mohan, Nitinder wrote: > Thank you everyone for your kindness and generosity. Your contribution is > highly appreciated ? > > We will surely share the findings of our work with the community later. > > Thank you! > > Best Regards > > > Nitinder Mohan > > Ph.D. student > > Department of Computer Science > > University of Helsinki > > https://www.nitindermohan.com/ > > ------------------------------ > *From:* ripe-atlas on behalf of Mohan, > Nitinder > *Sent:* Thursday, September 26, 2019 3:59 PM > *To:* ripe-atlas at ripe.net > *Subject:* [atlas] Requesting RIPE ATLAS credits for research > > Dear all, > > Greetings from Finland! > > I am a Ph.D. student at the University of Helsinki, Finland. I am > currently involved in a research project which is taking a critical look at > the availability and reachability of datacenters from all (or most of) > cloud providers operating worldwide. The project requires me to conduct > large-scale PING measurements to compute servers hosted in these > datacenters. However, I am a new RIPE ATLAS user and do not have any > credits to set up a measurement. Also, unfortunately, the tight timeline of > the project makes earning credits over time infeasible. > > My only option is now to ask the community to help our research. I would > highly appreciate if anyone can generously offer us RIPE ATLAS credits to > kickstart our measurements (e.g. 1 million). > > My RIPE NCC account is . > > Any help would be highly appreciated. > > Best Regards > > > Nitinder Mohan > > Ph.D. student > > Department of Computer Science > > University of Helsinki > > https://www.nitindermohan.com/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dikshie at gmail.com Thu Sep 26 16:56:30 2019 From: dikshie at gmail.com (dikshie) Date: Thu, 26 Sep 2019 23:56:30 +0900 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: On Thu, Sep 26, 2019 at 9:59 PM Mohan, Nitinder wrote: > My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). > My RIPE NCC account is . I just sent 10 millions. Please check your account. Best, Dikshie From the.lists at mgm51.com Thu Sep 26 17:01:00 2019 From: the.lists at mgm51.com (Mike) Date: Thu, 26 Sep 2019 11:01:00 -0400 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: I'm a little late to the party, but... Another 5,000,000 are on the way! On 9/26/2019 8:59 AM, Mohan, Nitinder wrote: > Dear all, > > Greetings from Finland! > > I am a Ph.D. student at the University of Helsinki, Finland. I am > currently involved in a research project which is taking a critical look > at the availability and reachability of datacenters from all (or most > of) cloud providers operating worldwide. The project requires me to > conduct large-scale PING measurements to compute servers hosted in these > datacenters. However, I am a new RIPE ATLAS user and do not have any > credits to set up a measurement. Also, unfortunately, the tight timeline > of the project makes earning credits over time infeasible. > > My only option is now to ask the community to help our research. I would > highly appreciate if anyone can generously offer us RIPE ATLAS credits > to kickstart our measurements (e.g. 1 million). > > My RIPE NCC account is . > > Any help would be highly appreciated.? > > Best Regards > > > Nitinder Mohan > > Ph.D. student > > Department of Computer Science > > University of Helsinki > > https://www.nitindermohan.com/ > From dimmit at gmail.com Thu Sep 26 17:20:04 2019 From: dimmit at gmail.com (Jacomo DB Piccolini) Date: Thu, 26 Sep 2019 12:20:04 -0300 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: Hi Nitinder, 25.000.000 credits sent your way! Cheers, Jacomo Jacomo Piccolini Team Cymru https://www.team-cymru.com/ Work:+1-847-378-3370 On Thu, Sep 26, 2019 at 9:59 AM Mohan, Nitinder wrote: > > Dear all, > > Greetings from Finland! > > I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. > > My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). > > My RIPE NCC account is . > > Any help would be highly appreciated. > > Best Regards > > > Nitinder Mohan > > Ph.D. student > > Department of Computer Science > > University of Helsinki > > https://www.nitindermohan.com/ From firdavs.murodov at gmail.com Fri Sep 27 03:55:45 2019 From: firdavs.murodov at gmail.com (Firdavs Murodov) Date: Fri, 27 Sep 2019 06:55:45 +0500 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: Hi Nitinder, Sent 5 million just in case;) -- Firdavs Murodov System Administrator, Eastera Co. Ltd. Dushanbe, Tajikistan On Thu, Sep 26, 2019 at 5:59 PM Mohan, Nitinder wrote: > Dear all, > > Greetings from Finland! > > I am a Ph.D. student at the University of Helsinki, Finland. I am > currently involved in a research project which is taking a critical look at > the availability and reachability of datacenters from all (or most of) > cloud providers operating worldwide. The project requires me to conduct > large-scale PING measurements to compute servers hosted in these > datacenters. However, I am a new RIPE ATLAS user and do not have any > credits to set up a measurement. Also, unfortunately, the tight timeline of > the project makes earning credits over time infeasible. > > My only option is now to ask the community to help our research. I would > highly appreciate if anyone can generously offer us RIPE ATLAS credits to > kickstart our measurements (e.g. 1 million). > > My RIPE NCC account is . > > Any help would be highly appreciated. > > Best Regards > > > Nitinder Mohan > > Ph.D. student > > Department of Computer Science > > University of Helsinki > > https://www.nitindermohan.com/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From frederic.gargula at ip-max.net Thu Sep 26 15:15:17 2019 From: frederic.gargula at ip-max.net (Frederic Gargula) Date: Thu, 26 Sep 2019 15:15:17 +0200 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: Sent you 10 million, have fun! Fred Frederic Gargula IP-Max SA > On 26 Sep 2019, at 14:59, Mohan, Nitinder wrote: > > Dear all, > > Greetings from Finland! > > I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. > > My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). > > My RIPE NCC account is . > > Any help would be highly appreciated. > > Best Regards > > Nitinder Mohan > Ph.D. student > Department of Computer Science > University of Helsinki > https://www.nitindermohan.com/ From t.ottavi at medi.fr Fri Sep 27 10:06:55 2019 From: t.ottavi at medi.fr (Toussaint OTTAVI) Date: Fri, 27 Sep 2019 10:06:55 +0200 Subject: [atlas] Software probes ? Message-ID: <3f67d5cd-2c17-3ccd-d40f-0f8a711f98a7@medi.fr> Hi, I just saw a survey last June about software probes. I would be greatly interested by them. Can we have some news about this project ? I know I can deploy software anchors. But I'm on a tiny island. I have very few bandwidth, and it's very expensive; then I can't afford spending too much of it :-) Kind regards, -- *Toussaint OTTAVI* *MEDI INFORMATIQUE* Tel : 04 95 20 10 03 GSM : 06 10 28 41 72 Email : t.ottavi at medi.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From jared at puck.nether.net Fri Sep 27 10:36:15 2019 From: jared at puck.nether.net (Jared Mauch) Date: Fri, 27 Sep 2019 04:36:15 -0400 Subject: [atlas] Software probes ? In-Reply-To: <3f67d5cd-2c17-3ccd-d40f-0f8a711f98a7@medi.fr> References: <3f67d5cd-2c17-3ccd-d40f-0f8a711f98a7@medi.fr> Message-ID: <8E8E49FB-451E-49FD-9A7F-547A3B331178@puck.nether.net> I had written up instructions for the VM based anchor method of installing with KVM/QEMU. You need to apply for an anchor and be approved and then set it up for them. It's not that hard. https://labs.ripe.net/Members/kistel/outcome-of-the-ripe-atlas-anchor-vms-pilot Likely has the best info. Sent from my iCar > On Sep 27, 2019, at 4:22 AM, Toussaint OTTAVI wrote: > > ? Hi, > > I just saw a survey last June about software probes. I would be greatly interested by them. Can we have some news about this project ? > > I know I can deploy software anchors. But I'm on a tiny island. I have very few bandwidth, and it's very expensive; then I can't afford spending too much of it :-) > > Kind regards, > -- > Toussaint OTTAVI > MEDI INFORMATIQUE > Tel : 04 95 20 10 03 > GSM : 06 10 28 41 72 > Email : t.ottavi at medi.fr > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander at neilson.net.nz Fri Sep 27 10:54:01 2019 From: alexander at neilson.net.nz (Alexander Neilson) Date: Fri, 27 Sep 2019 20:54:01 +1200 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: Hi Nitinder. If you haven?t already contact the ripe atlas team and they can lift the limit on the number of nodes used and other restrictions to better allow point in time and frequent testing so if you wanted to see the impact of events that occur in routing during your testing. They have been very responsive when I made a similar request and it?s a great use of the resource. Regards Alexander Alexander Neilson Neilson Productions Limited 021 329 681 alexander at neilson.net.nz > On 27/09/2019, at 00:59, Mohan, Nitinder wrote: > > ? > Dear all, > > Greetings from Finland! > > I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. > > My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). > > My RIPE NCC account is . > > Any help would be highly appreciated. > > Best Regards > > Nitinder Mohan > Ph.D. student > Department of Computer Science > University of Helsinki > https://www.nitindermohan.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From t.ottavi at medi.fr Fri Sep 27 11:27:03 2019 From: t.ottavi at medi.fr (Toussaint OTTAVI) Date: Fri, 27 Sep 2019 11:27:03 +0200 Subject: [atlas] Software probes ? In-Reply-To: <8E8E49FB-451E-49FD-9A7F-547A3B331178@puck.nether.net> References: <3f67d5cd-2c17-3ccd-d40f-0f8a711f98a7@medi.fr> <8E8E49FB-451E-49FD-9A7F-547A3B331178@puck.nether.net> Message-ID: Thank you for your answer. I saw anchors are able to perform more measurements than probes, and collect larger amount of data. In my situation, bandwidth is scarse and expensive. With the amount I'm currently paying for 10M, I could get 1G of transit in a data center in Paris :-) Then, I can't afford spending too much bandwidth just for the community. That's the reason why I was interested in software probes, for simple measurements, not using more bandwidth than hardware probes. Kind regards, -- *Toussaint OTTAVI* *MEDI INFORMATIQUE* Tel : 04 95 20 10 03 GSM : 06 10 28 41 72 Email : t.ottavi at medi.fr Le 27/09/2019 ? 10:36, Jared Mauch a ?crit?: > I had written up instructions for the VM based anchor method of > installing with KVM/QEMU. You need to apply for an anchor and be > approved and then set it up for them. It's not that hard. > > https://labs.ripe.net/Members/kistel/outcome-of-the-ripe-atlas-anchor-vms-pilot > > Likely has the best info. > > Sent from my iCar > >> On Sep 27, 2019, at 4:22 AM, Toussaint OTTAVI wrote: >> >> ? Hi, >> >> I just saw a survey last June about software probes. I would be >> greatly interested by them. Can we have some news about this project ? >> >> I know I can deploy software anchors. But I'm on a tiny island. I >> have very few bandwidth, and it's very expensive; then I can't afford >> spending too much of it :-) >> >> Kind regards, >> -- >> *Toussaint OTTAVI* >> *MEDI INFORMATIQUE* >> Tel : 04 95 20 10 03 >> GSM : 06 10 28 41 72 >> Email : t.ottavi at medi.fr >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at ripe.net Fri Sep 27 11:42:49 2019 From: robert at ripe.net (Robert Kisteleki) Date: Fri, 27 Sep 2019 11:42:49 +0200 Subject: [atlas] Software probes ? In-Reply-To: <3f67d5cd-2c17-3ccd-d40f-0f8a711f98a7@medi.fr> References: <3f67d5cd-2c17-3ccd-d40f-0f8a711f98a7@medi.fr> Message-ID: Hello, Indeed we are working on software probes (installable software package that acts as a RIPE Atlas probe). We're making progress and I plan to make announcements about this at the upcoming RIPE meeting (RIPE 79 in Rotterdam, 14-18 October). Regards, Robert On 2019-09-27 10:06, Toussaint OTTAVI wrote: > Hi, > > I just saw a survey last June about software probes. I would be greatly > interested by them. Can we have some news about this project ? > > I know I can deploy software anchors. But I'm on a tiny island. I have > very few bandwidth, and it's very expensive; then I can't afford > spending too much of it :-) > > Kind regards, > -- > *Toussaint OTTAVI* > *MEDI INFORMATIQUE* > Tel : 04 95 20 10 03 > GSM : 06 10 28 41 72 > Email : t.ottavi at medi.fr > From t.ottavi at medi.fr Fri Sep 27 11:53:04 2019 From: t.ottavi at medi.fr (Toussaint OTTAVI) Date: Fri, 27 Sep 2019 11:53:04 +0200 Subject: [atlas] Software probes ? In-Reply-To: References: <3f67d5cd-2c17-3ccd-d40f-0f8a711f98a7@medi.fr> Message-ID: Le 27/09/2019 ? 11:42, Robert Kisteleki a ?crit?: > Indeed we are working on software probes (installable software package > that acts as a RIPE Atlas probe). We're making progress and I plan to > make announcements about this at the upcoming RIPE meeting (RIPE 79 in > Rotterdam, 14-18 October). Perfect, thank you. Kind regards, -- *Toussaint OTTAVI* *MEDI INFORMATIQUE* Tel : 04 95 20 10 03 GSM : 06 10 28 41 72 Email : t.ottavi at medi.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.dorner at outlook.com Sat Sep 28 13:35:24 2019 From: m.dorner at outlook.com (Michael Dorner) Date: Sat, 28 Sep 2019 11:35:24 +0000 Subject: [atlas] Requesting RIPE ATLAS credits for research In-Reply-To: References: Message-ID: Hi Nitinder, sent you 5 million, have fun ? Would be great to receive some results from this Project. BR, Michael ________________________________ Von: ripe-atlas im Auftrag von Mohan, Nitinder Gesendet: Thursday, September 26, 2019 2:59:02 PM An: ripe-atlas at ripe.net Betreff: [atlas] Requesting RIPE ATLAS credits for research Dear all, Greetings from Finland! I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). My RIPE NCC account is . Any help would be highly appreciated. Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki https://www.nitindermohan.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From gponikie at akamai.com Mon Sep 30 03:26:43 2019 From: gponikie at akamai.com (Ponikierski, Grzegorz) Date: Mon, 30 Sep 2019 01:26:43 +0000 Subject: [atlas] Requesting RIPE ATLAS credits for research Message-ID: <173C1185-D055-4F1C-B3FB-E30B2738E989@akamai.com> I sent you some more so you can use more than just pings (traceroutes are expensive). When you finish don't forget to publish results on RIPE Labs :D Regards, Grzegorz From: "Mohan, Nitinder" Date: Thursday 2019-09-26 at 14:59 To: "ripe-atlas at ripe.net" Subject: [atlas] Requesting RIPE ATLAS credits for research Dear all, Greetings from Finland! I am a Ph.D. student at the University of Helsinki, Finland. I am currently involved in a research project which is taking a critical look at the availability and reachability of datacenters from all (or most of) cloud providers operating worldwide. The project requires me to conduct large-scale PING measurements to compute servers hosted in these datacenters. However, I am a new RIPE ATLAS user and do not have any credits to set up a measurement. Also, unfortunately, the tight timeline of the project makes earning credits over time infeasible. My only option is now to ask the community to help our research. I would highly appreciate if anyone can generously offer us RIPE ATLAS credits to kickstart our measurements (e.g. 1 million). My RIPE NCC account is . Any help would be highly appreciated. Best Regards Nitinder Mohan Ph.D. student Department of Computer Science University of Helsinki https://www.nitindermohan.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kiran.gunana at colruytgroup.com Mon Sep 30 08:15:41 2019 From: kiran.gunana at colruytgroup.com (kiran.gunana at colruytgroup.com) Date: Mon, 30 Sep 2019 08:15:41 +0200 (CEST) Subject: [atlas] credits not getting updated com243.209.765 Message-ID: <-1443571085.989815.1569824141217.JavaMail.was@svpapc06> Hello Ripe, Probe which I am using is up and running since more than few months, however I dont see any credits being added up, I am afraid I would loose all my credits and will end up with no monitoring for the services I am depended on. Can you please do the needfull asap ? Thanks & Regards, Kiran Gunana Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert at ripe.net Mon Sep 30 12:00:43 2019 From: robert at ripe.net (Robert Kisteleki) Date: Mon, 30 Sep 2019 12:00:43 +0200 Subject: [atlas] credits not getting updated com243.209.765 In-Reply-To: <-1443571085.989815.1569824141217.JavaMail.was@svpapc06> References: <-1443571085.989815.1569824141217.JavaMail.was@svpapc06> Message-ID: <7aa4a6ee-843d-6b01-53f2-ee311290f337@ripe.net> Hi, We don't have problems with crediting/debiting in general. Please send me details (probe ID, since when you think you have the issue) in private so I can check. Regards, Robert On 2019-09-30 08:15, kiran.gunana at colruytgroup.com wrote: > Hello Ripe, > > Probe which I am using is up and running since more than few months, > however I dont see any credits being added up, I am afraid I would loose > all my credits and will end up with no monitoring for the services I am > depended on. > > Can you please do the needfull asap ? > > Thanks & Regards, > Kiran Gunana > > > > > / > > Dit bericht is onderworpen aan de voorwaarden beschikbaar op _onze > website _ > > Ce message est soumis aux conditions disponibles sur _notre site web > _ > > This message is subject to the terms and conditions available on _our > website _ > > / From kiran.gunana at colruytgroup.com Mon Sep 30 12:15:29 2019 From: kiran.gunana at colruytgroup.com (kiran.gunana at colruytgroup.com) Date: Mon, 30 Sep 2019 12:15:29 +0200 (CEST) Subject: [atlas] credits not getting updated com243.249.483 Message-ID: <899641299.999543.1569838529396.JavaMail.was@svpapc06> Hello Robert, Thanks alot for the quick help robert !! Probe ID : 32256, Also check the attachement for the image of probe in our possession. rg, kiran. ----- Original Message: com243.247.331 --------------------------------- From: Robert Kisteleki (robert at ripe.net) To: kiran.gunana at colruytgroup.com, ripe-atlas at ripe.net Subject: Re: [atlas] credits not getting updated com243.209.765 Date: 30 September 2019 (12:00) Hi, We don't have problems with crediting/debiting in general. Please send me details (probe ID, since when you think you have the issue) in private so I can check. Regards, Robert On 2019-09-30 08:15, kiran.gunana at colruytgroup.com wrote: > Hello Ripe, > > Probe which I am using is up and running since more than few months, > however I dont see any credits being added up, I am afraid I would loose > all my credits and will end up with no monitoring for the services I am > depended on. > > Can you please do the needfull asap ? > > Thanks & Regards, > Kiran Gunana > > > > > / > > Dit bericht is onderworpen aan de voorwaarden beschikbaar op _onze > website _ > > Ce message est soumis aux conditions disponibles sur _notre site web > _ > > This message is subject to the terms and conditions available on _our > website _ > > / Dit bericht is onderworpen aan de voorwaarden beschikbaar op onze website Ce message est soumis aux conditions disponibles sur notre site web This message is subject to the terms and conditions available on our website -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ripe_probe_colruyt.pdf Type: application/pdf Size: 449361 bytes Desc: not available URL: