- ripe-atlas - mailman.ripe.net

Columns in Web UI for measurement results can't be sorted
by Evgeniy S. 31 Jan '19

31 Jan '19

Hi, I can't sort by any column in measurement results for traceroute (worked before by mouse click). [image: Screen Shot 2019-01-31 at 2.14.52 PM.png] There is my measurement results page short link https://goo.gl/iQrxWC -- -- With regards, Eugene Sudyr

1 0

Bug in DNS client subnet measurement
by Philip Homburg 31 Jan '19

31 Jan '19

Hi, We got a bug report that using the DNS client subnet option in a measurement results in a form error. It turns out that probe firmware version 4940 will send a malformed DNS query. Code cleanup related to other changes fixes this issue in the upcoming firmware. We expect to release the new firmware in about one month from now. Philip

1 0

Probe v1 disconnecting every 2 hours
by Hugh Saunders 30 Jan '19

30 Jan '19

Hey All, My probe v1 (id:65[1]) has started disconnecting roughly every 2 hours. I read a previous post[2] that said this may be related to power, so changed the USB power supply to one that provides 1A (the FAQ says the need 500ma) but no improvement. I don't notice connectivity issues every couple of hours with any other devices on the same switch. Any suggestions welcome :) Thanks. [1] https://atlas.ripe.net/probes/65/ [2] https://www.ripe.net/participate/mail/forum/ripe-atlas/PDI1MDc1YjM1LTA5MTct… -- Hugh Saunders

5 5

DNSEC Tag for Probes
by Philippe Mächler 28 Jan '19

28 Jan '19

Hello RIPE Atlas Users I’d like to some measurements about DNSSEC with RIPE Atlas and need a way to check if the probe does DNSSEC validation The docs mention the system-tags e.g resolvs A and resolvs AAAA. Is there something like “system: does DNSSEC validation” if not, is there any other way or is this on the roadmap? 😊 Freundliche Grüsse / best regards Philippe Mächler

1 0

Making a bunch of tests/measurements to a single destination is 'tedious'
by Christopher Morrow 24 Jan '19

24 Jan '19

howdy! So, if I have a dns server somewhere and I want to make a bunch of measurements: "how does NYC see my dns?" (pick N probes near NYC) "How does DEN see my dns?" (pick N probes near DEN) "How does LHR see my dns?" (pick N probes near LHR) "how does ...." ...you get the idea... I'm trying to characterize my service from a 'user' perspective by large Metropolis, well within N km of that metropolis anyway :) but across ~70 or so metros, in v4 and v6 and with authoritative and non-authoritative queries with each test running for 4 days so i can see some daily cycles in traffic patterns/etc. The number of measurements is large in total, breaking up by 3-4 metropolis chunks is super tedious :( Can I request an API key (or some other thing) which can make that sort of request happen for all my measurements in one go? The thing I'm probing is very able to handle a few extra thousand queries per second.. and I'd only be hurting myself i get my estimate wrong :) thanks! -chris

3 4

New on RIPE Labs: RIPE Atlas Anchors 400+
by Alun Davies 24 Jan '19

24 Jan '19

Dear colleagues, We have published an article looking at how the quick uptake in RIPE Atlas VM anchors and other developments have helped us hit 400 connected anchors. https://labs.ripe.net/Members/alun_davies/ripe-atlas-anchors-400 <https://labs.ripe.net/Members/alun_davies/ripe-atlas-anchors-400> Kind regards, Alun Davies RIPE NCC

1 0

Probe questions - reporting clearly busticated probe configs?
by Christopher Morrow 23 Jan '19

23 Jan '19

Howdy! I've been running a few measurements over the last while and looked at the raw results like: [{"dst_name":"2001:4860:4860::8844","error":{"socket":"connect failed Network is unreachable"},"from":"fd84:d527:5183:0:a2f3:c1ff:fec4:63a8","fw":4940,"group_id":18903906,"lts":21,"msm_id":18903906,"msm_name":"Tdig","prb_id":13635,".... "from":"2001:db8:4447:0:eade:27ff:fec9:7134","fw":4940,"group_id":18903906,"lts":7,"msm_id":18903906,"msm_name":"Tdig","prb_id":26725,"...] I'm curious if/how atlas reports back to probe owners: "Hey, your ipv6 connectivity is implausible/impossible" since, at least for: https://atlas.ripe.net/probes/26725/#!tab-network and: https://atlas.ripe.net/probes/13635/#!tab-network there's no way their v6 addresses can work... (one is documentation prefix the other is ULA I think?) I suppose test requestors should check the ipv6 prefix to see if it's at least plausibly correct until some signal back to the owners can be attempted?

5 8

Re: [atlas] IPv6 Doesn't Work
by ripe＠brite.cz 22 Jan '19

22 Jan '19

Hi, you pointed me to the right way. I enabled IPv6 on my Windows Laptop and it show the same symptoms - it receives an IPv6 address but is not able to reach any IPv6 target. My setup looks like this: Atlas Probe > Ubiquiti airRouter > provider's WIFI AP When I connect my laptop stright to the provider's WIFI AP then IPv6 works all fine. When I connect to LAN port of my airRouter, it receives an IPv6 address but is not able to reach any IPv6 target. So the point of failure seems to be my router. It is set to Bridge mode with WIFI as a client, connected to provider's AP. Per the Manual: ---------------------------------------------------------- Bridge In Bridge mode, the AirRouter forwards all network management and data packets from one network interface to the other without any intelligent routing. For simple applications this provides an efficient and fully transparent network solution. WLAN (wireless) and LAN (Ethernet) interfaces belong to the same network segment and share the same IP address space. WLAN and LAN interfaces form the virtual bridge interface while acting as the bridge ports. The bridge has assigned IP settings for management purposes. ---------------------------------------------------------- The Bridge management interface shows following addresses assigned: 10.0.0.29 2A00:1028:8D1C:90DA:DE9F:DBFF:FE5C:632B/64 FE80::DE9F:DBFF:FE5C:632B/64 I would think the Bridge mode should not interfere the traffic in any way. I have read only access to the provider's AP - it is cheap router with IPv4 NAT and IPv6 interfaces. It shows an IPv6 address [starting with 2a00:1028:] on its WAN IPv6, LAN IPv6, IPv6 Default Gateway, IPv6 DNS server, etc. As I said, when I connect laptop stright to the provider's AP, IPv6 works. I'm unable to to setup my airRouter for IPv6 to work. It supports IPv6, but in bridge mode it has no settings available. I tried multiple factory resets, with various settings, and also tried to switch the airRouter to SOHO Router mode, then there is IPv6 Enable checkbox. While it is checked, I tried various settings, such as SLAAC, DHCPv6, etc. No go. Looks the IPv6 support in this router is broken. It's a pity I cannot connect Atlas Probe v3 stright to the provider's WIFI eventhough it has WIFI hardware onboard. There is no way I could connect stright by LAN cable to the provider. It looks for now I have to leave the Probe live with IPv6 broken. Cheers Jiri ______________________________________________________________ > Od: "Stephen D. Strowes" <sds(a)ripe.net> > Komu: ripe(a)brite.cz, ripe-atlas(a)ripe.net > Datum: 22.01.2019 10:51 > Předmět: Re: [atlas] IPv6 Doesn't Work > >Hi, > >On 19/01/2019 17:26, ripe(a)brite.cz wrote: >> Traceroute to 2001:503:ba3e::2:30 (2001:503:ba3e::2:30), 40 byte packets >> 1 * 2a00:1028:8d1c:90da:220:4aff:fee0:2026 dynamic-2a00-1028-8d1c-90da-0220-4aff-fee0-2026.ipv6.broadband.iol.cz AS5610 2191.889ms !H 3010.564ms !H > > From `man traceroute6`: > > > !H Address unreachable > > The host address is not reachable for some other reasons, >particularly a link- > > layer failure (e.g. Neighbor discovery failure). > >Obviously that's not great! > >The probe has a v6 address, so it's solicited and received some network >config when it was booted or when your network config changed a couple >days ago. Question is, what happened next. > >Guessing around the symptoms, if it's not receiving subsequent periodic >RAs (either the router isn't sending them or something is preventing the >probe from receiving them), then its local routing state will expire. > >Questions I'd try and answer are: when you connect a device to the same >network, does it a) receive a v6 network & generate an address, then b) >does v6 work immediately after that, and c) does it fail after a while? > > >S. > > > > >> >> ______________________________________________________________ >>> Od: ripe(a)brite.cz >>> Komu: ripe-atlas(a)ripe.net >>> Datum: 19.01.2019 17:23 >>> Předmět: Re: [atlas] IPv6 Doesn't Work >>> >>> No filtering here. Furthermore it seems the Atlas Probe is not able to get anywhere out via IPv6 too. >>> I'm wondering is the Gateway setting correct? [Gateway(s) fe80::1] >>> >>> --------------------------------- >>> Peter Eckel lists at eckel-edv.de >>> Sat Jan 19 11:26:33 CET 2019 >>> >>> Hi Jiri, >>> >>> for me it looks like you're not reachable indeed: >>> >>>> pete at charon.net.hindenburgring.com> traceroute inet6 2a00:1028:8d1c:90da:220:4aff:fee0:2026 >>>> traceroute6 to 2a00:1028:8d1c:90da:220:4aff:fee0:2026 (2a00:1028:8d1c:90da:220:4aff:fee0:2026) from <xxx>, 64 hops max, 12 byte packets >>>> [...] >>>> 3 2a00:19e0:ffff:fffc::1 (2a00:19e0:ffff:fffc::1) 23.579 ms 23.308 ms 23.495 ms >>>> 4 2a00:19e0:ffff:ffff::3 (2a00:19e0:ffff:ffff::3) 29.521 ms 29.738 ms 29.822 ms >>>> 5 ae0-401.fra10.core-backbone.com (2a01:4a0:1338:2::1) 30.063 ms 29.215 ms 36.436 ms >>>> 6 ae2-2001.nbg30.core-backbone.com (2a01:4a0:0:2001::1) 32.540 ms 31.789 ms 51.790 ms >>>> 7 ae1-2053.prg10.core-backbone.com (2a01:4a0:0:2053::22) 37.175 ms 36.355 ms 35.141 ms >>>> 8 nix4-ipv6.pater.iol.cz (2001:7f8:14::29:1) 39.033 ms 36.891 ms 37.997 ms >>>> 9 dynamic-2a00-1028-0001-0160-0000-0000-0000-0002.ipv6.broadband.iol.cz (2a00:1028:1:160::2) 38.403 ms 41.560 ms 37.239 ms >>>> 10 dynamic-2a00-1028-0001-02a5-0000-0000-0000-0002.ipv6.broadband.iol.cz (2a00:1028:1:2a5::2) 37.214 ms 50.273 ms 51.604 ms >>>> 11 * * * >>>> 12 dynamic-2a00-1028-8d1c-90d8-0000-0000-0000-0001.ipv6.broadband.iol.cz (2a00:1028:8d1c:90d8::1) 44.291 ms 58.819 ms 49.810 ms >>>> 13 * * * >>>> 14 * * * >>>> 15 * * * >>>> 16 * * * >>>> 17 * * * >>>> 18 * * * >>>> 19 * * * >>>> [...] >>> Are you by any chance filtering ICMPv6 on your ingress router? >>> >>> Regards, >>> >>> Peter. >>> >>> >>> >> > >

1 0

Re: [atlas] IPv6 Doesn't Work
by ripe＠brite.cz 22 Jan '19

22 Jan '19

all the IPv6 traceroutes go like this: Latest Traceroute Result for Measurement #2009 2019-01-19 15:25 UTC Traceroute to 2001:503:ba3e::2:30 (2001:503:ba3e::2:30), 40 byte packets 1 * 2a00:1028:8d1c:90da:220:4aff:fee0:2026 dynamic-2a00-1028-8d1c-90da-0220-4aff-fee0-2026.ipv6.broadband.iol.cz AS5610 2191.889ms !H 3010.564ms !H ______________________________________________________________ > Od: ripe(a)brite.cz > Komu: ripe-atlas(a)ripe.net > Datum: 19.01.2019 17:23 > Předmět: Re: [atlas] IPv6 Doesn't Work > >No filtering here. Furthermore it seems the Atlas Probe is not able to get anywhere out via IPv6 too. >I'm wondering is the Gateway setting correct? [Gateway(s) fe80::1] > >--------------------------------- >Peter Eckel lists at eckel-edv.de >Sat Jan 19 11:26:33 CET 2019 > >Hi Jiri, > >for me it looks like you're not reachable indeed: > >> pete at charon.net.hindenburgring.com> traceroute inet6 2a00:1028:8d1c:90da:220:4aff:fee0:2026 >> traceroute6 to 2a00:1028:8d1c:90da:220:4aff:fee0:2026 (2a00:1028:8d1c:90da:220:4aff:fee0:2026) from <xxx>, 64 hops max, 12 byte packets >> [...] >> 3 2a00:19e0:ffff:fffc::1 (2a00:19e0:ffff:fffc::1) 23.579 ms 23.308 ms 23.495 ms >> 4 2a00:19e0:ffff:ffff::3 (2a00:19e0:ffff:ffff::3) 29.521 ms 29.738 ms 29.822 ms >> 5 ae0-401.fra10.core-backbone.com (2a01:4a0:1338:2::1) 30.063 ms 29.215 ms 36.436 ms >> 6 ae2-2001.nbg30.core-backbone.com (2a01:4a0:0:2001::1) 32.540 ms 31.789 ms 51.790 ms >> 7 ae1-2053.prg10.core-backbone.com (2a01:4a0:0:2053::22) 37.175 ms 36.355 ms 35.141 ms >> 8 nix4-ipv6.pater.iol.cz (2001:7f8:14::29:1) 39.033 ms 36.891 ms 37.997 ms >> 9 dynamic-2a00-1028-0001-0160-0000-0000-0000-0002.ipv6.broadband.iol.cz (2a00:1028:1:160::2) 38.403 ms 41.560 ms 37.239 ms >> 10 dynamic-2a00-1028-0001-02a5-0000-0000-0000-0002.ipv6.broadband.iol.cz (2a00:1028:1:2a5::2) 37.214 ms 50.273 ms 51.604 ms >> 11 * * * >> 12 dynamic-2a00-1028-8d1c-90d8-0000-0000-0000-0001.ipv6.broadband.iol.cz (2a00:1028:8d1c:90d8::1) 44.291 ms 58.819 ms 49.810 ms >> 13 * * * >> 14 * * * >> 15 * * * >> 16 * * * >> 17 * * * >> 18 * * * >> 19 * * * >> [...] > >Are you by any chance filtering ICMPv6 on your ingress router? > >Regards, > > Peter. > > >

2 1

Probe firmware source code
by Evgeniy S. 21 Jan '19

21 Jan '19

Dear community let me ask if probe os and services (aka firmware) source code available in public? Where I find it if yes, and why it's not public if not available? -- -- With regards, Eugene S

3 3

Re: [atlas] IPv6 Doesn't Work
by ripe＠brite.cz 19 Jan '19

19 Jan '19

No filtering here. Furthermore it seems the Atlas Probe is not able to get anywhere out via IPv6 too. I'm wondering is the Gateway setting correct? [Gateway(s) fe80::1] --------------------------------- Peter Eckel lists at eckel-edv.de Sat Jan 19 11:26:33 CET 2019 Hi Jiri, for me it looks like you're not reachable indeed: > pete at charon.net.hindenburgring.com> traceroute inet6 2a00:1028:8d1c:90da:220:4aff:fee0:2026 > traceroute6 to 2a00:1028:8d1c:90da:220:4aff:fee0:2026 (2a00:1028:8d1c:90da:220:4aff:fee0:2026) from <xxx>, 64 hops max, 12 byte packets > [...] > 3 2a00:19e0:ffff:fffc::1 (2a00:19e0:ffff:fffc::1) 23.579 ms 23.308 ms 23.495 ms > 4 2a00:19e0:ffff:ffff::3 (2a00:19e0:ffff:ffff::3) 29.521 ms 29.738 ms 29.822 ms > 5 ae0-401.fra10.core-backbone.com (2a01:4a0:1338:2::1) 30.063 ms 29.215 ms 36.436 ms > 6 ae2-2001.nbg30.core-backbone.com (2a01:4a0:0:2001::1) 32.540 ms 31.789 ms 51.790 ms > 7 ae1-2053.prg10.core-backbone.com (2a01:4a0:0:2053::22) 37.175 ms 36.355 ms 35.141 ms > 8 nix4-ipv6.pater.iol.cz (2001:7f8:14::29:1) 39.033 ms 36.891 ms 37.997 ms > 9 dynamic-2a00-1028-0001-0160-0000-0000-0000-0002.ipv6.broadband.iol.cz (2a00:1028:1:160::2) 38.403 ms 41.560 ms 37.239 ms > 10 dynamic-2a00-1028-0001-02a5-0000-0000-0000-0002.ipv6.broadband.iol.cz (2a00:1028:1:2a5::2) 37.214 ms 50.273 ms 51.604 ms > 11 * * * > 12 dynamic-2a00-1028-8d1c-90d8-0000-0000-0000-0001.ipv6.broadband.iol.cz (2a00:1028:8d1c:90d8::1) 44.291 ms 58.819 ms 49.810 ms > 13 * * * > 14 * * * > 15 * * * > 16 * * * > 17 * * * > 18 * * * > 19 * * * > [...] Are you by any chance filtering ICMPv6 on your ingress router? Regards, Peter.

1 0

IPv6 Doesn't Work
by ripe＠brite.cz 19 Jan '19

19 Jan '19

Hi, I have Probe #2413 here, it shows label " IPv6 Doesn't Work". It has IPv6 address assigned: IPv6 Current Configuration Addresses 2a00:1028:8d1c:90da:220:4aff:fee0:2026/64 ASN 5610 Gateway(s) fe80::1 I'm not sure what's the issue. My provider provides IPv6, but I personally don't use IPv6 on any of my devices. I read https://atlas.ripe.net/about/faq/#i-have-an-ipv6-only-network-will-the-prob… but in this case it is not IPv6 only. I tried to give it static config but I couldn't find out what config to use. Any idea? Thanks Jiri

2 1

credit differences between probes?
by Christopher Morrow 18 Jan '19

18 Jan '19

howdy! (long time listener, first time caller...) I have some probes deployed, and for some period of time I was accruing credits at about the same rate per day per probe. Recently (last week or so?) I noticed that I now accrue at one rate for 1 device and a different rate for 2 other devices. The devices have been up for at least the last 24hrs: morrowc-fios 4 days, 5 hours 21.6k morrowc-comcast 1 week, 2 days 65.7k Atlas@deteque-IAD 3 weeks 21.6k (unsure why the fios one bobbled...but it's still be up for ~4days) Is this expected? or maybe I'm just in some wonky space with the accruals anyway?

3 6

New on RIPE Labs: Redesigning the RIPE Atlas Measurement Details Page
by Alun Davies 17 Jan '19

17 Jan '19

Dear colleagues, Today we published an article on some of the changes we’ve made to the RIPE Atlas measurement details page. The redesign follows work we’ve been doing to move over to a new back-end storage solution for RIPE Atlas measurement metadata. Click the link to find out more: https://labs.ripe.net/Members/jasper_den_hertog/new-design-and-functionalit… <https://labs.ripe.net/Members/jasper_den_hertog/new-design-and-functionalit…> Kind regards, Alun Davies RIPE NCC

1 0

Data in the Internet Maps
by Davey Song(宋林健) 21 Dec '18

21 Dec '18

Hi Atlas people, <I did not receive mails from this list months ago. I hope it still works.> I’m writing to ask about the Data repo in the intnernet maps. For example I would like to study the DNS root RTT statistics in this page : https://atlas.ripe.net/results/maps/rtt-fixed/ Where and How should I get the access to this data. Best regards, Davey

3 6

testing DNS flag day compatibility
by Petr Špaček 19 Dec '18

19 Dec '18

Hello everyone, this is follow-up from RIPE 77 hallway discussion, sorry for delay. We are looking for ways to test DNS flag day [1] compatibility from client networks. Objective is to test hypothesis that most breakage happens on authoritative side of DNS. In other words, we would like to test that DNS recursive infrastructure and client networks do not significantly influence compatibility. That would help to provide precise information for network operators who will have to deal with DNS flag day. Problem here is that RIPE Atlas does not allow to send all types of queries [2] required for full test. It was discussed at length that Atlas team has its reasons for not sending random blobs to random IP addresses, which is understood. Question here is: Can we find a middle ground to allow greater variety of valid DNS queries without forcing Atlas team to reimplement everything? My notes from meeting mention two approaches for further dicussion: a) User provides command line arguments for well-known tool dig, which gets executed in controlled environment ("as part of RIPE Atlas infrastructure") and generates query packet/blob. This blob generated by dig is then used as payload so use cannot ship anything but syntactically valid DNS packet. b) User provides blob for payload, which is then analyzed by packet parser of choice (BIND/ldns/Knot DNS/all of them). The payload can be sent out only if packet parsers do not find out any problem/blob is syntactically valid. These two approaches can also be combined to guard again quirks in either component. c) <propose your own here> What do you think? Is there a way to allow greater flexibility to Atlas DNS? [1] https://dnsflagday.net/ [2] https://gitlab.isc.org/isc-projects/DNS-Compliance-Testing/blob/master/genr… -- Petr Špaček @ CZ.NIC

2 4

Long response times using one-off measurements with old probes
by Moritz Muller 17 Dec '18

17 Dec '18

Hi, I would like to point you to a discussion on the DNS-OARC mailing list: https://lists.dns-oarc.net/pipermail/dns-operations/2018-December/018196.ht… One of the operators at .ca noticed that old probes report way higher response times using DNS CHAOS queries (300% or more) (see also [3]). After some digging, we came to the conclusion that this has to do with the fact that he is carrying out “one-off” measurements. When carrying out the same query for a longer time, we cannot observe this delay. The issues seems to be that one-off measurements are scheduled at probes using a different library than measurements that run for a longer period (“eooqd” instead of “eperd”). Some small additional delays have been documented before on the RIPE Atlas website and in research papers [1, 2], but the big delay with one off measurements was new to me. Also to others? Is our assumption correct that the scheduler is the culprit? Moritz [1] https://dl.acm.org/citation.cfm?doid=2805789.2805796 [2] https://clarinet.u-strasbg.fr/~pelsser/publications/Holterbach-ripe-atlas-s… [3] https://atlas.ripe.net/measurements/18086197/#!probes

2 3

API is sluggish
by Ponikierski, Grzegorz 11 Dec '18

11 Dec '18

Hi all! Did you notice that for last few days API is super slow to response. It takes something like few minutes to get reply. Do you observe any issue with Atlas infrastructure? What details I should provide to help with troubleshoot? Regards, Grzegorz

2 3

DNS Measurement Grouping by NSID
by Klaus Darilion 30 Nov '18

30 Nov '18

Hi! IIRC, the map of the DNS measurement allowed to group the dataset by NSID. Was this feature removed? OR is it now somewhere else? I.e.: https://atlas.ripe.net/measurements/17175212/?filter=&diversity-picker=3&ag… Thanks Klaus

4 6

Minor change to Atlas anchor DNS resolver configuration
by Anand Buddhdev 28 Nov '18

28 Nov '18

Dear colleagues, Each RIPE Atlas anchor runs a DNS resolver. This resolver is configured as the primary resolver for the anchor, with the following directive at the top of the resolver configuration (/etc/resolv.conf): nameserver 127.0.0.1 For ease of configuration management, we are changing this directive to: nameserver ::1 This change will not affect DNS resolution on the anchors in any way. However, any measurement that does DNS lookups using the anchor's primary resolver will contain "::1" instead of "127.0.0.1" in "src_addr" field of results. If you're using any code to parse such results, and specifically looking for "127.0.0.1", you'll need to adjust your code to also look for "::1". Regards, Anand Buddhdev RIPE NCC

1 0

no measurements
by Teun Vink 20 Nov '18

20 Nov '18

Hi, Are there any problems with the Atlas backend? All requests are answered with {u'info': u'Something went wrong with our back-end', u'type': u'redis- fail'} I don't see any working measurements in our webportal as well. Best regards, -- Teun Vink BIT | teun(a)bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE

2 3

New on RIPE Labs: Announcing RIPE Atlas VM Anchors
by Alun Davies 12 Nov '18

12 Nov '18

Dear colleagues, We just this morning published an article announcing that, as of today, we are accepting applications for anyone interested in hosting RIPE Atlas VM anchors. The article points you to all the information you’ll need to apply for and install a virtual anchor: https://labs.ripe.net/Members/alun_davies/announcing-ripe-atlas-vm-anchors <https://labs.ripe.net/Members/alun_davies/ripe-atlas-anchor-vms> Kind regards, Alun Davies RIPE NCC

5 6

Temporary problem with RIPE Atlas measurement creation
by Chris Amin 01 Nov '18

01 Nov '18

Dear RIPE Atlas users, Due to a complication during a deploy, there was a problem scheduling RIPE Atlas measurements from approximately 12:50 to 14:14 UTC. Most new measurements created during this time will not have been scheduled properly. The issue is now fixed for new measurements, so if your measurements didn't work during this time you can try to create them again and it should work. Apologies for any inconvenience caused. Regard, Chris Amin RIPE NCC

1 0

Delays over the weekend
by Robert Kisteleki 29 Oct '18

29 Oct '18

Dear all, Some of you have noticed that there were delays in how RIPE Atlas behaved, starting on Saturday. This happened because of an issue deep in the bowels of the infrastructure which caused tasks (including measurement requests) to pile up. We believe the issue has been resolved by now, though we're still investigating the root cause of the issue. We apologise for the inconvenience this caused. Regards, Robert Kisteleki RIPE Atlas team

1 0

New set - wizard improvements suggestion
by Evgeniy S. 24 Oct '18

24 Oct '18

Dear All, finally we are using our ripe probes to monitor our resources from mobile networks. I found that current "new set - wizard" functionality is lacking some useful extra filters using: 1) "User tags" - then I can tag my mobile probes and select only mobile network probes from the list. 2) mine, favorites, sponsored, ambassadorships It will be also nice to request to tag mobile network probes for users who run them. Any feedback is appreciated. I'm also interesting for getting in touch with people who have probes installed in mobile networks to make tests / comparing to our setup. -- With regards, Eugene

1 0

Relocating a probe
by Gary Gapinski 20 Oct '18

20 Oct '18

Hello: I currently host a probe (#14102) at my residence. I will soon move to a new residence about 450 miles from the current location. Such a move will necessarily alter measurements obtained relative to past ones (as well as ASN, geolocation, etc.). Should the existing probe identity be retired in favor of a new identity? (And if so how might that be accomplished?) Regards, Gary

2 2

WG: Probe 1198 is disconnected (Keck.US)
by Cornelius Keck 08 Oct '18

08 Oct '18

Power outage. Repair ETA not yet available. Thx for the heads-up. Gesendet von meinem BlackBerry 10-Smartphone. Originalnachricht Von: RIPE Atlas (no reply) <no-reply(a)ripe.net> Gesendet: Sonntag, 7. Oktober 2018 16:30 An: ckeck(a)texoma.net Antwort an: RIPE Atlas (no reply) Betreff: Probe 1198 is disconnected (Keck.US) Dear Cornelius Keck, Your probe 1198 has been disconnected from the RIPE Atlas infrastructure since 2018-10-07 21:05:06 UTC. You may be able to learn more about the possible cause from the "Status" tab on your probe's information page: https://atlas.ripe.net/probes/1198/#!tab-status Probes are tagged with suspected problems every four hours, so if there is nothing listed under the Status tab and your probe has just gone offline, please check back in a few hours, as more information may be available. If you need further assistance or have any questions, please contact us at atlas(a)ripe.net. Kind regards, RIPE Atlas Team ********** This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 15 minutes. If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/1198/, and click the "edit" button under "Notifications".

1 0

Definition of Commercial Use
by Mic Szillat 04 Oct '18

04 Oct '18

Hi folks, I have a discussion in my company about the definition of commercial use. Can we please get an official confirmation whether our typical usage of Atlas is covered by the terms of service? We occasionally use Atlas to debug network connectivity between our systems and those of our customers. We answer support requests and confirm or deny network issues based on the data collected. We do not give customers access to the measurement interface. Thanks, Mic

3 3

New on RIPE Labs: Measuring Anycast DNS Services Using RIPE Atlas
by Mirjam Kuehne 01 Oct '18

01 Oct '18

Dear colleagues, Please find this step-by-step guide contributed by Kenneth Finnegan on RIPE Labs on how to use RIPE Atlas to measure the world-wide performance of Anycast DNS services: https://labs.ripe.net/Members/kenneth_finnegan/measuring-anycast-dns-servic… Kind regards, Mirjam Kühne RIPE NCC

1 0

Extended CHAOS queries
by Moritz Muller 24 Sep '18

24 Sep '18

Hi all, I was wondering if it would be possible to extend the supported CHAOS TXT query arguments to trustanchor.unbound. and trustanchor.server? This would enable RIPE Atlas probes to measure which DNSSEC Trust Anchors Unbound and PowerDNS resolvers have configured (if they support this query). Cheers, Moritz

1 0

Is there a max running measurement number for a user
by Yihao Jia 30 Aug '18

30 Aug '18

Dear all, Is there a max running measurement number for a user? I try to launch about 800 measurements, but only about 150 of them succeed and keep running, while another 650 fail with the description "overlimited denied" one of the fail measurement is: https://atlas.ripe.net/measurements/15302198/ Do you know what's the reason I failed? (btw, I am wondering how to check the reason why a measurement is failed by the measurement id?) Many thanks, Yihao

3 2

Re: [atlas] Looking for advise and temporarily limits increment for research
by Alan Walker 30 Aug '18

30 Aug '18

https://www.ripe.net/participate/mail/forum/ripe-atlas/PENBTDZlRWUzUlR4ai1q… Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

The three generations of the Atlas probes : technical details
by BELLAFKIH hayat 30 Aug '18

30 Aug '18

Hi, I hope validate some details about the Atlas probes. I try to get these details by consulting the resources: 1. https://atlas.ripe.net/docs/probe-v1/ 2. https://atlas.ripe.net/docs/probe-v2/ 3. https://atlas.ripe.net/docs/probe-v3/ But no technical details given. By reading some presentations, I create the table bellow. Now, I hope if you can validate these details and complete the information about the CPU. It will be good if you can add the technical details for each generation of the probes. Thanks in advance. *Hayat BELLAFKIH*

3 3

need help in RIPE atlas credits
by Yihao Jia 28 Aug '18

28 Aug '18

Dear all, I am Yihao, a Ph.D. student at Tsinghua University. Right now I plan to start an experiment with the RIPE atlas, but I don't have enough credits to fulfill the whole process. I am writing this letter to inquire if anyone can share some credits with me. (like 1 Million) Appreciate! (My RIPE atlas account: yhjia.03(a)gmail.com) Many thanks, Yihao Tsinghua University

5 6

Getting More Traffic for Probe
by Eren Türkay 27 Aug '18

27 Aug '18

Hello, I am running a probe [0] at my home and I have 240Mbit connection from my provider. When I look at the graphs, this probe is basically sitting idle doing nothing! I can spare 20Mbit/s easily for measurements to keep the usage. However, I do not know how to achieve that. Is it possible to attract more traffic to my probe? I'm sure there is some algorithm involved to distribute the work so if you can please get me some more work, I'd be pleased [obviously more credits to spare :)] [0] https://atlas.ripe.net/probes/31252/ Regards, -- . 73! DE TA1AET http://erenturkay.com/

4 5

Probe for mobile network
by Evgeniy Sudyr 25 Aug '18

25 Aug '18

We have developed mobile application and we are interesting for making measurements from our customer''s networks using ripe atlas probes. I found no probes from interesting ASN, that's why I'm looking for a way to host own probes (we do have already) and connect it to interesting MNO networks using some USB sticks or even mobile phones (to use as 3G / LTE modem). Obviously we want to make less points of failure in between RIPE probe and mobile modem. Any luck to get USB sticks working with RIPE probe without some router in between? -- With regards, Eugene Sudyr

1 0

Looking for an AS8560 contact
by Robert Kisteleki 22 Aug '18

22 Aug '18

Hello, We're looking for a contact in the RIPE Atlas context from AS8560 (oneandone.net). There's a (probably runaway) script hammering our gates. Thank you, Robert Kisteleki for the RIPE Atlas team

1 0

Failled to get traceroute results from the id 5151
by BELLAFKIH hayat 16 Aug '18

16 Aug '18

Hi all, I am trying to get traceroute results for the measurements id 5151 ( https://atlas.ripe.net/measurements/5151/) by using python module : Python client for RIPE ATLAS API, for period october 2016. For many days ( eg : 19, 20) in this period, the operation is failled. I got Killed ! I found that the reason of having Killed when running a python script is related to the ressources limits. Any helps? *Hayat BELLAFKIH*

1 0

Probe limit per measurement
by Schomp, Kyle 08 Aug '18

08 Aug '18

Hi all, I'm trying to use Ripe Atlas for monitoring a production system. I've hit the 1k maximum probes per measurement limit, however. I realize I could just split up the task among multiple measurements to stay under the 1k probes max, but that seems sort of hack-ish and possibly less efficient for the platform. Is it possible to get the limits increased? Thanks! -kyle

2 1

Processing RIPE Atlas data as Big Data
by BELLAFKIH hayat 24 Jul '18

24 Jul '18

Dear RIPE Atlas users, I am studying the processing of the data collected by the probes as a Big Data problem. For instance, one hour of traceroute data count for 500 Mo (bzip2), so 7 Go of data in text format. Can you share with me how you deal with these data in practice. are you using a super machine, Big Data tools? best regards, Hayat

2 1

Looking for advise and temporarily limits increment for research
by Yihao Jia 22 Jul '18

22 Jul '18

To whom it may help, My name is Yihao. I am a Ph.D. student. Recently I am doing a research with RIPE Atlas. However, my research requires many measurements in a short period, which breaks several rules of the Rate Limits. Since I really like and in hurry to use Atlas to support my research, is there any advice I can get from this? I'd like to describe why it would be necessary for my research. And if possible, may I get a temporarily limit increment for 10 days? Many thanks, Yihao Jia

3 3

Re: [atlas] Need help: launching a periodical atlas measurement
by Stephane Bortzmeyer 19 Jul '18

19 Jul '18

On Thu, Jul 19, 2018 at 10:47:54AM -0500, Yihao Jia <yhjia03(a)gmail.com> wrote a message of 192 lines which said: > I am a little confused because all example on documents is one-off. I guess > error might happen around "is_oneoff", "interval", "spread". > source code for this test is below and in the attachment. "is_oneoff" is off by default. "interval" is documented as "In normal (not one-off) measurements, this value represents the number of seconds between measurements by a single probe." I never tried "spread". I don't know the exact JSON you sent but this one worked (5 minutes, 1 minute between each test): {'definitions': [{'target': 'fr-ilm-as57119.anchors.atlas.ripe.net', 'af': 4, 'interval': 60, 'packets': 1, 'type': 'ping', 'description': 'Ping fr-ilm-as57119.anchors.atlas.ripe.net'}], 'start_time': 1532026200, 'stop_time': 1532026500, 'probes': [{'requested': 1, 'type': 'area', 'value': 'WW'}]} And it gave this measurement: https://atlas.ripe.net/measurements/15297080/

1 0

Inquiry: RIPE Atlas credits M Fung
by Matthew Fung 19 Jul '18

19 Jul '18

Hello, My name is Matthew, I am an undergrad studying CS at University of British Columbia. I've recently discovered the work done by RIPE and I'm really interested in using Atlas for a research project. I am wondering if anyone is willing to share credits in order to make this possible. I aim to use no more than 1M credits. (My user info is included below) Thanks, Matthew Fung RIPE ID: y6c0b(a)ugrad.cs.ubc.ca

2 1

Global Traceroute
by Steve Gibbard 19 Jul '18

19 Jul '18

I wrote front-end to traceroute from the RIPE Atlas probes. It looks like a standard looking glass — you select a probe by location and AS number, enter a destination, and it does a traceroute. It’s on the web at https://www.globaltraceroute.com. If this looks useful, please check it out and tell me what you think. One of the things I've found frustrating when troubleshooting routing problems was the lack of information about inbound paths. Various measurement systems would tell me when performance was bad. Traceroutes from my own network would tell me what path traffic to a destination was taking outbound. Flow systems would tell me what interface inbound traffic was coming in on, and sometimes what peer it was coming through. But determining the full path inbound traffic was taking — why users of some ISP in Asia were having their traffic show up at one of my POPs in Europe, for instance, was much more difficult. I’ve been using looking glasses and commercial performance monitoring systems that allow traceroutes from their probes, but those often weren’t where the end users were. RIPE Atlas did have probes where a lot of my end users were, so I started configuring one time measurements on RIPE Atlas whenever I needed a traceroute from a simulated end user. But finding a suitable probe and configuring the measurement was too cumbersome to do when I wasn’t pretty desperate. This is my attempt to solve that problem. Thanks, Steve

6 7

For help: launching a periodical atlas measurement
by Yihao Jia 19 Jul '18

19 Jul '18

Dear all, I am so sorry for using a screenshot for my last email. And I'd like to redescribe the problem I have. I'd like to launch a periodic Ping measurement (with python). It starts at UTC-now to (for example) 5 minutes later. I'd like the probe do the Ping test in every 1 minute. Thus I can have 5 results in this measurement. I am a little confused because all example on documents is one-off. I guess error might happen around "is_oneoff", "interval", "spread". source code for this test is below and in the attachment. Could you help me in checking where I get wrong? Many thanks, Yihao ---------------------------------------------------------------------------------------------- from datetime import datetime, timedelta from ripe.atlas.cousteau import ( Ping, AtlasSource, AtlasCreateRequest ) ATLAS_API_KEY = "" source2 = AtlasSource( requested=1, type="probes", value="35704" ) ping = Ping( af=4, target="202.112.51.179", description="Test for periodic Ping test", packets=1, ) def request(): atlas_request = AtlasCreateRequest( start_time=datetime.utcnow(), stop_time=(datetime.utcnow() + timedelta(minutes=5)), key=ATLAS_API_KEY, measurements=[ping], sources=[source2], is_oneoff=False, interval=60, spread=60 ) (is_success, response) = atlas_request.create() return is_success, response if __name__ == '__main__': is_success, response = request()

1 0

Need help in launching a periodical atlas measurement
by Yihao Jia 19 Jul '18

19 Jul '18

Dear all, I am in trouble with launching a periodical Ping measurement. [image: image.png] my script is like this, but my measurement always fails. I tried several times with different modification on "interval" and "spread". [image: image.png] one failed example can be reviewed here: https://atlas.ripe.net/measurements/15282285/ It works well when I launch a one-off measurement, but every time I try to launch a periodic measurement with the setting above, it fails all the time. it probably because the "is_oneoff", "interval", "spread" is set wrong, but I can't find a good example for it. The idea of this test measurement is to start a Ping test every 1 minute, from UTC-now to 5 minutes later. Thus, I'd like to have 5-set result in this measurement. Could you help me check where I set wrong? Many thanks, Yihao

3 2

DNS measurement using the Probe's resolvers
by Rami Al-Dalky 18 Jul '18

18 Jul '18

Hi Everyone, I have a question about using the probe's list of resolvers when creating a DNS measurement. It is unclear to me whether the probe would send the query to all resolvers at the same time or not! Also, does the probe send the query to all resolvers in its list or to a subset of those resolvers? Is DNS eyeball implemented in the probes? Sincerely, Rami

3 2

Transfer Anchor ownership
by Clément Hertling (Wxcafé) 17 Jul '18

17 Jul '18

Hi, We have an anchor at the company I work for that has been associated with the wrong RIPE Atlas account. We're trying to move it from that (personal) atlas account to a shared netops account, but can't find a way to do this. Is there a way to do this ourselves, or can someone from RIPE Atlas do it for us? Cheers, -- Clément 'wxcafé' Hertling

2 1

Wrong TLSA for stat.ripe.net
by Alarig Le Lay 10 Jul '18

10 Jul '18

Hi, Since one week or so, I have a TLSA validation error for stat.ripe.net on TCP/443 at each time I visit https://atlas.ripe.net/ and I have the same result from the RIPE nlnog node: alarig@airmure ~ % echo '' | openssl s_client -connect atlas.ripe.net:443 2>/dev/null | openssl x509 -in /dev/stdin -fingerprint -sha256 | grep SHA256 | sed 's/://g' | cut -d '=' -f 2 8248E13AB5CA3BACAC63F15B831DA32F2CD54973EDF74E69B6A614B7295C02B4 alarig@airmure ~ % dig +short -t TLSA _443._tcp.atlas.ripe.net | awk '{ print $4 $5 }' 8248E13AB5CA3BACAC63F15B831DA32F2CD54973EDF74E69B6A614B7295C02B4 alarig@airmure ~ % echo '' | openssl s_client -connect stat.ripe.net:443 2>/dev/null | openssl x509 -in /dev/stdin -fingerprint -sha256 | grep SHA256 | sed 's/://g' | cut -d '=' -f 2 2A2B939449E847374121D4846E3117F23A0283C7B2818ED96C91D2808ABE4C0E alarig@airmure ~ % dig +short -t TLSA _443._tcp.stat.ripe.net | awk '{ print $4 $5 }' E3DC43427AA9F62D1E07BBE108AF62BEE84A454DB579FD57A4FFDFFD5A23E576 grifon@ripe01:~$ echo '' | openssl s_client -connect stat.ripe.net:443 2>/dev/null | openssl x509 -in /dev/stdin -fingerprint -sha256 | grep SHA256 | sed 's/://g' | cut -d '=' -f 2 2A2B939449E847374121D4846E3117F23A0283C7B2818ED96C91D2808ABE4C0E grifon@ripe01:~$ dig +short -t TLSA _443._tcp.stat.ripe.net | awk '{ print $4 $5 }' E3DC43427AA9F62D1E07BBE108AF62BEE84A454DB579FD57A4FFDFFD5A23E576 The commands are ugly but work on atlas.ripe.net. Could you please update it? Regards, -- Alarig Le Lay

1 0

New on RIPE Labs: Comparing Virtual and Metal RIPE Atlas Anchors
by Mirjam Kuehne 04 Jul '18

04 Jul '18

Dear colleagues, We compared performance between virtual and physical RIPE Atlas anchors. Please find the results on RIPE Labs: https://labs.ripe.net/Members/stephen_strowes/comparing-virtual-and-metal-r… Kind regards, Mirjam Kühne RIPE NCC

1 0