From thinkofit at gmail.com Tue Jun 6 18:48:33 2017 From: thinkofit at gmail.com (Antonio Prado) Date: Tue, 6 Jun 2017 18:48:33 +0200 Subject: [atlas] Anchors as target hosts for SLA Message-ID: <0ac5e446-cd81-cf17-5510-436ca213074f@gmail.com> hi, do you think could be a good idea to use Ripe Atlas Anchors as target hosts for measuring respect of SLA terms of an Internet transit? SLA example This Internet transit should meet the following criteria: average round trip delay (echo request, echo reply) toward $NEAREST_ATLAS_ANCHOR should be less than 100ms on a 10k packets stream of pings; packet loss equal or less than 0.02% pros, cons, recommendations? thank you -- antonio From gert at space.net Tue Jun 6 19:03:33 2017 From: gert at space.net (Gert Doering) Date: Tue, 6 Jun 2017 19:03:33 +0200 Subject: [atlas] Anchors as target hosts for SLA In-Reply-To: <0ac5e446-cd81-cf17-5510-436ca213074f@gmail.com> References: <0ac5e446-cd81-cf17-5510-436ca213074f@gmail.com> Message-ID: <20170606170333.GC45648@Space.Net> Hi, On Tue, Jun 06, 2017 at 06:48:33PM +0200, Antonio Prado wrote: > This Internet transit should meet the following criteria: > > average round trip delay (echo request, echo reply) toward > $NEAREST_ATLAS_ANCHOR should be less than 100ms on a 10k packets stream > of pings; packet loss equal or less than 0.02% > > pros, cons, recommendations? Too simple. What if that anchor is down, or the anchor host network has a network bottleneck towards the transit provider you are using? So you need something that averages over multiple anchors - we used to do that via TTM ("if our TTM hosts can reach more than 80% of all other TTM hosts, we declare the Internet to be in good working condition" - note the "80%", because something is always down somewhere) but haven't come around to define & implement something based on ATLAS yet. With the large amount of anchors nowadays, just using the anchor matrix is actually quite similar to what TTM had, just better... :-) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From thinkofit at gmail.com Tue Jun 6 19:46:42 2017 From: thinkofit at gmail.com (Antonio Prado) Date: Tue, 6 Jun 2017 19:46:42 +0200 Subject: [atlas] Anchors as target hosts for SLA In-Reply-To: <20170606170333.GC45648@Space.Net> References: <0ac5e446-cd81-cf17-5510-436ca213074f@gmail.com> <20170606170333.GC45648@Space.Net> Message-ID: <0a178152-ca40-a17f-e1c1-2f9bc438014d@gmail.com> On 6/6/17 7:03 PM, Gert Doering wrote: > Too simple. What if that anchor is down, or the anchor host network has > a network bottleneck towards the transit provider you are using? well, I selected two anchors placed in two different NAPs where all ISPs in my scenario are present. so, not a big concern if one anchor is down. the other issue about possible bottlenecks is not applicable in that context. > So you need something that averages over multiple anchors - we used to > do that via TTM ("if our TTM hosts can reach more than 80% of all other > TTM hosts, we declare the Internet to be in good working condition" - note > the "80%", because something is always down somewhere) but haven't come > around to define & implement something based on ATLAS yet. I like the idea and it should definitely be the way to go. thank you -- antonio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: OpenPGP digital signature URL: From colin at spakka.net Tue Jun 6 20:05:04 2017 From: colin at spakka.net (Colin Petrie) Date: Tue, 6 Jun 2017 20:05:04 +0200 Subject: [atlas] Anchors as target hosts for SLA In-Reply-To: <20170606170333.GC45648@Space.Net> References: <0ac5e446-cd81-cf17-5510-436ca213074f@gmail.com> <20170606170333.GC45648@Space.Net> Message-ID: <1b96cea7-d86c-a0e4-136e-d31d8e93a3d4@spakka.net> On 06/06/2017 19:03, Gert Doering wrote: > On Tue, Jun 06, 2017 at 06:48:33PM +0200, Antonio Prado wrote: >> This Internet transit should meet the following criteria: >> >> average round trip delay (echo request, echo reply) toward >> $NEAREST_ATLAS_ANCHOR should be less than 100ms on a 10k packets stream >> of pings; packet loss equal or less than 0.02% >> >> pros, cons, recommendations? > > Too simple. What if that anchor is down, or the anchor host network has > a network bottleneck towards the transit provider you are using? > > So you need something that averages over multiple anchors - we used to > do that via TTM ("if our TTM hosts can reach more than 80% of all other > TTM hosts, we declare the Internet to be in good working condition" - note > the "80%", because something is always down somewhere) but haven't come > around to define & implement something based on ATLAS yet. You could also check the new stability system-tags on the anchors. That way you only compare with the anchors that are believed to currently have 'good' reachability. Cheers, Colin From stanish.stanishev at vivacom.bg Thu Jun 8 16:39:30 2017 From: stanish.stanishev at vivacom.bg (Stanish Stanishev) Date: Thu, 08 Jun 2017 16:39:30 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP Message-ID: Hello, My probe(ID 16372) has disconnected from the Atlas network and in the Status I see USB flash corrupted. I did the troubleshooting - power off the probe, remove the USB, power on the probe, waited 10 mins, plugged brand new 4G USB. Several times with no success, So I decided to do a traffic capture of the uplink port where the probe is connected to. According to the capture the probe does not send DHCP requests. It sends only IPv6 traffic - Multicast Listener reports and Neighbor solicitation. Hence not getting IP address. I did several restarts - no change. Anybody has seen this issue before ? Any hints how to deal with such issue ? Thanks Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From adavies at ripe.net Fri Jun 9 11:45:29 2017 From: adavies at ripe.net (Alun Davies) Date: Fri, 9 Jun 2017 11:45:29 +0200 Subject: [atlas] Firmware Update for RIPE Atlas V1 and V2 Probes Message-ID: Dear all, We?re currently in the process of deploying a new firmware update for RIPE Atlas V1 and V2 probes. The update provides a fix for a bug that caused around 15% of RIPE Atlas V1 probes to disconnect. As of the time of writing, the update is at approximately 60% deployment. If you?ve been unable to reconnect your RIPE Atlas V1 probe, you can return it to the following address to be fixed. If you?d like the probe to be returned to you afterwards, please let us know. Alternatively, we?d encourage you to apply for a V3 probe. RIPE NCC P.O. Box 10096 1001EB Amsterdam The Netherlands We?d like to take this opportunity to thank all probe hosts for your ongoing efforts in supporting RIPE Atlas. Cheers, 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 philip.homburg at ripe.net Fri Jun 9 14:12:00 2017 From: philip.homburg at ripe.net (Philip Homburg) Date: Fri, 9 Jun 2017 14:12:00 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP In-Reply-To: References: Message-ID: <2d9e2bd9-06e8-3fae-fd5b-12405dd30eee@ripe.net> Hi, On 2017/06/08 16:39 , Stanish Stanishev wrote: > So I decided to do a traffic capture of the uplink port where the probe is connected to. According to the capture the probe does not send DHCP requests. It sends only IPv6 traffic - Multicast Listener reports and Neighbor solicitation. Hence not getting IP address. > I did several restarts - no change. > > Anybody has seen this issue before ? > Any hints how to deal with such issue ? There seems to be a very rare condition where in the config on the built-in flash DHCP gets disabled. I noticed that some time ago and added code to newer firmwares to check for this condition and re-enable DHCP. The best way to fix this is to place the probe in a network that offers IPv6. Philip From stanish.stanishev at vivacom.bg Mon Jun 12 13:55:56 2017 From: stanish.stanishev at vivacom.bg (Stanish Stanishev) Date: Mon, 12 Jun 2017 13:55:56 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP In-Reply-To: <2d9e2bd9-06e8-3fae-fd5b-12405dd30eee@ripe.net> Message-ID: Hello, Philip, Today I connected the probe to IPv6 network. Below is what happened: 1. After boot probe got IPv6 address 2a01:5a8:2:5:6666:b3ff:fec5:fa6. 2. I did a traffic capture and saw the probe connected to 2001:67c:2e8:11::c100:1319 (woolsey.ipv6.atlas.ripe.net) and there was a short communication via SSL. 3. Then the probe became silent. I waited ten minutes and plugged a new USB stick however the probe did not try to connect ATLAS infrastructure anymore. Note: The router assigns recursive DNS servers (2001:4860:4860::8888 2001:4860:4860::8844) via ICMP6 Option 25 in Router Advertisement messages. I have also tried to assign DNS servers via the RIPE Probe Management Web Interface but no difference, Thank You Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From philip.homburg at ripe.net Tue Jun 13 10:53:45 2017 From: philip.homburg at ripe.net (Philip Homburg) Date: Tue, 13 Jun 2017 10:53:45 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP In-Reply-To: References: Message-ID: <42f498d7-5ad8-6ae3-2b9f-e34ef23dda23@ripe.net> On 2017/06/12 13:55 , Stanish Stanishev wrote: > Note: The router assigns recursive DNS servers (2001:4860:4860::8888 2001:4860:4860::8844) via ICMP6 Option 25 in Router Advertisement messages. > I have also tried to assign DNS servers via the RIPE Probe Management Web Interface but no difference, There are some limitations when the probe is running from its internal flash. Fortunately, there is a way around that. The probe is now connected. Philip From stanish.stanishev at vivacom.bg Tue Jun 13 14:07:26 2017 From: stanish.stanishev at vivacom.bg (Stanish Stanishev) Date: Tue, 13 Jun 2017 14:07:26 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP In-Reply-To: <42f498d7-5ad8-6ae3-2b9f-e34ef23dda23@ripe.net> Message-ID: Ah, Thank you so much for the support. May I ask you to share what did you do in order to make the probe connect again to the Atlas ? Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From philip.homburg at ripe.net Wed Jun 14 09:10:34 2017 From: philip.homburg at ripe.net (Philip Homburg) Date: Wed, 14 Jun 2017 09:10:34 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP In-Reply-To: References: Message-ID: On 2017/06/13 14:07 , Stanish Stanishev wrote: > Ah, Thank you so much for the support. > May I ask you to share what did you do in order to make the probe connect again to the Atlas ? Normally the probe receives the name of a controller to connect to. If the probe doesn't have access to DNS resolvers then it cannot connect. We have a trick to provide the probe with either an IPv4 or an IPv6 literal. In theory the system will detect that the probe has troubles resolving DNS and will switch to that automatically. We have to figure out why that didn't happen for your probe. But it can also be activated manually. Philip From camin at ripe.net Thu Jun 15 11:00:39 2017 From: camin at ripe.net (Chris Amin) Date: Thu, 15 Jun 2017 11:00:39 +0200 Subject: [atlas] Improvements to the RIPE Atlas measurement creation form Message-ID: Dear all, We?ve made some changes to the interface for creating measurements on the RIPE Atlas website (https://atlas.ripe.net/measurements/form/) that will make it both faster and more responsive. Users should also see similar improvements in the user interface for monitoring and configuring domains with DomainMON (https://atlas.ripe.net/domainmon/). The changes were made possible by switching to the public measurement API (https://atlas.ripe.net/docs/api/v2/manual/). Concurrently with this, we also improved the error reporting in the API to make it easier to find out the cause of errors. This API change is backwards compatible and is documented in the API manual (https://atlas.ripe.net/docs/api/v2/manual/overview/error_messages.html). Whilst we do not expect the transition to cause any issues, we kindly ask that users let us know if they experience anything out of the ordinary that might be related to the change. Best regards, 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 GeertJan.deGroot at xs4all.nl Tue Jun 20 23:50:23 2017 From: GeertJan.deGroot at xs4all.nl (Geert Jan de Groot) Date: Tue, 20 Jun 2017 23:50:23 +0200 Subject: [atlas] atlas feature suggestion Message-ID: <3d3d31ce-42db-b9e5-abea-3cf08b96b3c6@xs4all.nl> Hi, On the portal: > Notifications > Notify me at my registration address if this probe is down for more than 600 minutes. This doesn't seem to take into account that a probe may be dual-stacked (v4 and v6) and just one of these protocols may fail w/o the other one failing as well (this is a problem with my CPE, but I'm not touching that box until the temperature in the lab has dropped to sensible values) In any case, if v6 dies but v4 still works, the probe doesn't complain. Perhaps this should be flagged separately? How are we doing on testing silent v6-failures in general? Happy eyeballs make a lot of breakage invisible.. Geert Jan From mostafa.shahdadi at icloud.com Wed Jun 21 00:29:15 2017 From: mostafa.shahdadi at icloud.com (mostafa shahdadi) Date: Wed, 21 Jun 2017 02:59:15 +0430 Subject: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas) Message-ID: <0001AF3E-F221-4DBF-A357-36C087B50366@icloud.com> Sent from my iPad From mir at ripe.net Fri Jun 23 11:44:09 2017 From: mir at ripe.net (Mirjam Kuehne) Date: Fri, 23 Jun 2017 11:44:09 +0200 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: References: Message-ID: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> Dear colleagues, In this article we present a new way to access the dataset on the RIPE Atlas platform. Instead of fetching individual results from measurements using the available APIs, you can now download files containing public measurements for a given day. Please find more details on RIPE Labs: https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data-archives Kind regards, Mirjam K?hne RIPE NCC From colinj at mx5.org.uk Fri Jun 23 12:05:21 2017 From: colinj at mx5.org.uk (Colin Johnston) Date: Fri, 23 Jun 2017 11:05:21 +0100 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> Message-ID: link for download does NOT seem to work for me at present ? at: https://ftp.ripe.net/ripe/atlas/data Colin > On 23 Jun 2017, at 10:44, Mirjam Kuehne wrote: > > > Dear colleagues, > > In this article we present a new way to access the dataset on the RIPE > Atlas platform. Instead of fetching individual results from measurements > using the available APIs, you can now download files containing public > measurements for a given day. > > Please find more details on RIPE Labs: > > https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data-archives > > Kind regards, > Mirjam K?hne > RIPE NCC > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mir at ripe.net Fri Jun 23 12:11:18 2017 From: mir at ripe.net (Mirjam Kuehne) Date: Fri, 23 Jun 2017 12:11:18 +0200 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> Message-ID: works for me. mir On 23/06/17 12:05, Colin Johnston wrote: > link for download does NOT seem to work for me at present ? > at: https://ftp.ripe.net/ripe/atlas/data > * > * > * > * > *Colin* > * > * >> On 23 Jun 2017, at 10:44, Mirjam Kuehne > > wrote: >> >> >> Dear colleagues, >> >> In this article we present a new way to access the dataset on the RIPE >> Atlas platform. Instead of fetching individual results from measurements >> using the available APIs, you can now download files containing public >> measurements for a given day. >> >> Please find more details on RIPE Labs: >> >> https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data-archives >> >> Kind regards, >> Mirjam K?hne >> RIPE NCC >> > From mir at ripe.net Fri Jun 23 12:13:40 2017 From: mir at ripe.net (Mirjam Kuehne) Date: Fri, 23 Jun 2017 12:13:40 +0200 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> Message-ID: <88d92152-3e78-d2a9-75dd-526de3c9b4d0@ripe.net> Dear Colin, Sorry for the brief response below. I thought this was an internal mail :-) It seems that the link only works from inside our network. We will look into this and will get back to you . Sorry about this. Kind regards, Mirjam Kuhne RIPE NCC On 23/06/17 12:11, Mirjam Kuehne wrote: > works for me. > > mir > > On 23/06/17 12:05, Colin Johnston wrote: >> link for download does NOT seem to work for me at present ? >> at: https://ftp.ripe.net/ripe/atlas/data >> * >> * >> * >> * >> *Colin* >> * >> * >>> On 23 Jun 2017, at 10:44, Mirjam Kuehne >> > wrote: >>> >>> >>> Dear colleagues, >>> >>> In this article we present a new way to access the dataset on the RIPE >>> Atlas platform. Instead of fetching individual results from measurements >>> using the available APIs, you can now download files containing public >>> measurements for a given day. >>> >>> Please find more details on RIPE Labs: >>> >>> https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data-archives >>> >>> Kind regards, >>> Mirjam K?hne >>> RIPE NCC >>> >> > From mkh at rqc.ru Fri Jun 23 12:16:52 2017 From: mkh at rqc.ru (Marat Khalili) Date: Fri, 23 Jun 2017 13:16:52 +0300 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> Message-ID: Does NOT work for me. HTTP and FTP work, HTTPS doesn't. -- With Best Regards, Marat Khalili On 23/06/17 13:11, Mirjam Kuehne wrote: > works for me. > > mir > > On 23/06/17 12:05, Colin Johnston wrote: >> link for download does NOT seem to work for me at present ? >> at: https://ftp.ripe.net/ripe/atlas/data >> * >> * >> * >> * >> *Colin* >> * >> * >>> On 23 Jun 2017, at 10:44, Mirjam Kuehne >> > wrote: >>> >>> >>> Dear colleagues, >>> >>> In this article we present a new way to access the dataset on the RIPE >>> Atlas platform. Instead of fetching individual results from measurements >>> using the available APIs, you can now download files containing public >>> measurements for a given day. >>> >>> Please find more details on RIPE Labs: >>> >>> https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data-archives >>> >>> Kind regards, >>> Mirjam K?hne >>> RIPE NCC >>> > From mcandela at ripe.net Fri Jun 23 12:17:05 2017 From: mcandela at ripe.net (Massimo Candela) Date: Fri, 23 Jun 2017 12:17:05 +0200 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: <88d92152-3e78-d2a9-75dd-526de3c9b4d0@ripe.net> References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> <88d92152-3e78-d2a9-75dd-526de3c9b4d0@ripe.net> Message-ID: <53DCCE02-B127-4318-B074-37D27F8E763B@ripe.net> Hi Colin, We are fixing this. The problem is only on https. Try ftp://ftp.ripe.net/ripe/atlas/data in the meanwhile. Ciao, Massimo > On 23 Jun 2017, at 12:13, Mirjam Kuehne wrote: > > Dear Colin, > > Sorry for the brief response below. I thought this was an internal mail :-) > > It seems that the link only works from inside our network. We will look > into this and will get back to you . Sorry about this. > > Kind regards, > Mirjam Kuhne > RIPE NCC > > > On 23/06/17 12:11, Mirjam Kuehne wrote: >> works for me. >> >> mir >> >> On 23/06/17 12:05, Colin Johnston wrote: >>> link for download does NOT seem to work for me at present ? >>> at: https://ftp.ripe.net/ripe/atlas/data >>> * >>> * >>> * >>> * >>> *Colin* >>> * >>> * >>>> On 23 Jun 2017, at 10:44, Mirjam Kuehne >>> > wrote: >>>> >>>> >>>> Dear colleagues, >>>> >>>> In this article we present a new way to access the dataset on the RIPE >>>> Atlas platform. Instead of fetching individual results from measurements >>>> using the available APIs, you can now download files containing public >>>> measurements for a given day. >>>> >>>> Please find more details on RIPE Labs: >>>> >>>> https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data-archives >>>> >>>> Kind regards, >>>> Mirjam K?hne >>>> RIPE NCC >>>> >>> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dfk at ripe.net Fri Jun 23 12:17:31 2017 From: dfk at ripe.net (Daniel Karrenberg) Date: Fri, 23 Jun 2017 12:17:31 +0200 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> Message-ID: <1216339a-b0e0-1ca4-241c-3372faea66e5@ripe.net> >From just another user: For me it is strange. It always works with an FTP client. But in Firefox it does not work for me from outside the NCC. Maybe a load balancer or firewall issue? Until that is resolved I suggest to use an FTP client. Daniel On 23.06.17 12:11 , Mirjam Kuehne wrote: > works for me. > > mir > > On 23/06/17 12:05, Colin Johnston wrote: >> link for download does NOT seem to work for me at present ? >> at: https://ftp.ripe.net/ripe/atlas/data >> * >> * >> * >> * >> *Colin* >> * >> * >>> On 23 Jun 2017, at 10:44, Mirjam Kuehne >> > wrote: >>> >>> >>> Dear colleagues, >>> >>> In this article we present a new way to access the dataset on the RIPE >>> Atlas platform. Instead of fetching individual results from measurements >>> using the available APIs, you can now download files containing public >>> measurements for a given day. >>> >>> Please find more details on RIPE Labs: >>> >>> https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data-archives >>> >>> Kind regards, >>> Mirjam K?hne >>> RIPE NCC >>> >> > > > From yakimus at voks.ua Fri Jun 23 12:16:11 2017 From: yakimus at voks.ua (Yakimus // VOKS support) Date: Fri, 23 Jun 2017 13:16:11 +0300 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> <88d92152-3e78-d2a9-75dd-526de3c9b4d0@ripe.net> Message-ID: <16aa01d2ec09$bd46a4b0$a8a8a8c0@yakim> Hi, Mirjam! Fri, 23 Jun 2017 12:13:40 +0200 you wrote: MK> Sorry for the brief response below. I thought this was an internal mail MK> :-) Seems that link was misprinted, use ftp instead of https: ftp://ftp.ripe.net/ripe/atlas/data MK> It seems that the link only works from inside our network. We will look MK> into this and will get back to you . Sorry about this. MK> Kind regards, MK> Mirjam Kuhne MK> RIPE NCC -- Best regards, Yakimus // VOKS LTD. From colinj at mx5.org.uk Fri Jun 23 12:35:05 2017 From: colinj at mx5.org.uk (Colin Johnston) Date: Fri, 23 Jun 2017 11:35:05 +0100 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: <53DCCE02-B127-4318-B074-37D27F8E763B@ripe.net> References: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> <88d92152-3e78-d2a9-75dd-526de3c9b4d0@ripe.net> <53DCCE02-B127-4318-B074-37D27F8E763B@ripe.net> Message-ID: <92A51CB6-7E94-4859-9708-E656F76F6192@mx5.org.uk> Thanks, works via ftp ok, parallel ftp works ok it seems Colin > On 23 Jun 2017, at 11:17, Massimo Candela wrote: > > Hi Colin, > > We are fixing this. The problem is only on https. > Try ftp://ftp.ripe.net/ripe/atlas/data in the meanwhile. > > Ciao, > Massimo > > > >> On 23 Jun 2017, at 12:13, Mirjam Kuehne > wrote: >> >> Dear Colin, >> >> Sorry for the brief response below. I thought this was an internal mail :-) >> >> It seems that the link only works from inside our network. We will look >> into this and will get back to you . Sorry about this. >> >> Kind regards, >> Mirjam Kuhne >> RIPE NCC >> >> >> On 23/06/17 12:11, Mirjam Kuehne wrote: >>> works for me. >>> >>> mir >>> >>> On 23/06/17 12:05, Colin Johnston wrote: >>>> link for download does NOT seem to work for me at present ? >>>> at: https://ftp.ripe.net/ripe/atlas/data >>>> * >>>> * >>>> * >>>> * >>>> *Colin* >>>> * >>>> * >>>>> On 23 Jun 2017, at 10:44, Mirjam Kuehne >>>>> >> wrote: >>>>> >>>>> >>>>> Dear colleagues, >>>>> >>>>> In this article we present a new way to access the dataset on the RIPE >>>>> Atlas platform. Instead of fetching individual results from measurements >>>>> using the available APIs, you can now download files containing public >>>>> measurements for a given day. >>>>> >>>>> Please find more details on RIPE Labs: >>>>> >>>>> https://labs.ripe.net/Members/petros_gigis/announcing-daily-ripe-atlas-data-archives >>>>> >>>>> Kind regards, >>>>> Mirjam K?hne >>>>> RIPE NCC >>>>> >>>> >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stanish.stanishev at vivacom.bg Fri Jun 23 16:34:23 2017 From: stanish.stanishev at vivacom.bg (Stanish Stanishev) Date: Fri, 23 Jun 2017 16:34:23 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP In-Reply-To: Message-ID: Hello, Thank you for the details. Do I need to assist you somehow for finding the reason, why the automatic way for providing the probe with literal did not happen ? Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From philip.homburg at ripe.net Fri Jun 23 16:39:51 2017 From: philip.homburg at ripe.net (Philip Homburg) Date: Fri, 23 Jun 2017 16:39:51 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP In-Reply-To: References: Message-ID: <9aff98c9-d7d4-49a0-d4fd-e31aac76f164@ripe.net> On 2017/06/23 16:34 , Stanish Stanishev wrote: > Thank you for the details. > Do I need to assist you somehow for finding the reason, why the automatic way for providing the probe with literal did not happen ? Thanks for the offer. We already found the reason and this situation should now be covered. Philip From stanish.stanishev at vivacom.bg Fri Jun 23 16:40:40 2017 From: stanish.stanishev at vivacom.bg (Stanish Stanishev) Date: Fri, 23 Jun 2017 16:40:40 +0200 Subject: [atlas] Probe does not request IPv4 address via DHCP In-Reply-To: <9aff98c9-d7d4-49a0-d4fd-e31aac76f164@ripe.net> Message-ID: OK. Thanks ;-) S, Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From gkigkis at ics.forth.gr Fri Jun 23 17:04:46 2017 From: gkigkis at ics.forth.gr (Petros Gigis) Date: Fri, 23 Jun 2017 17:04:46 +0200 Subject: [atlas] New on RIPE Labs: Announcing Daily RIPE Atlas Data Archives In-Reply-To: <44c53d16-f2f8-6130-986f-10bc897fb4d1@ripe.net> Message-ID: Hi all, As I wrote on the RIPE Labs article this is a prototype so we can still change the format of the files and split or merge the various files. If you have feedback on this prototype service, now is the time to send us your comments. Our plan is to transform this into a production service once we've taken all your comments into account. Thank you in advance. Best regards, Petros Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum