- ripe-atlas - mailman.ripe.net

Link aggregation for anchors?
by Tore Anderson 20 Jul '17

20 Jul '17

Hi, I was wondering if it is possible to connect our anchor in a fault tolerant fashion using 802.3ad link aggregation? This would allow us to perform serialised maintenance on the upstream switches without ever offlining the anchor. Tore

4 6

Trace and Ping measurements fail on Probe 15861
by ripe＠brite.cz 18 Jul '17

18 Jul '17

Hi team, recently I'm not able to run measurements on probe 15861 I am hosting at home. When I create a measurement with only this probe, it ends up in Failed status [measurements 9193416 9193417 9199824 for example]. When there is multiple probes in the measurement, probe 15861 ends up showing "No recent report available" [9193406 9192883]. Otherwise the probe has been online and does not show any anomalies. Any idea? Thank you Jiri

1 0

New RIPE Atlas Measurement Options
by Alun Davies 17 Jul '17

17 Jul '17

Dear all, The RIPE Atlas team have added a number of new measurement options on RIPE Atlas. Here’s an overview of the changes: DNS measurements timeout: allows the user to specify a custom timeout in milliseconds after which probes will stop waiting for a response from the DNS server use_macros: allows the use of special macro strings in the "query_argument" field, to create unique or easily distinguishable queries. The allowed macros are: $p the (integer) ID of the probe carrying out the measurement $r a random 16-digit hexadecimal string $t a Unix timestamp of the time that the probe carries out the DNS query SSLcert measurements hostname: specifies a hostname to send as a Server Name Indication (SNI), which is necessary for web servers which host multiple TLS domains on the same IP address. Ping measurements include_probe_id: include the probe ID as an ASCII string within the payload of ping measurements. Note: this is included in addition to other payload data. The changes are all included in the RIPE Atlas API reference: https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_Li… <https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_Li…> If you have any questions whatsoever about the new measurement options, do let us know. As always, we welcome suggestions for new features from RIPE Atlas users. Best regards, Alun Davies RIPE NCC Communications Department

1 0

Caching issues on the latest call
by Johan ter Beest 13 Jul '17

13 Jul '17

Dear all, Today we became aware of some caching issues on the latest API call (https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Latest_GET) In certain corner cases it was possible that an incomplete set of results for a logged-in user was cached for up to 24 hours. This did not apply to non logged-in users as the results are not cached in that case. A fix for this issue has been deployed and going forward the latest call will have a 1 minute cache regardless of whether the user is logged in or not. As caching is always tricky, we kindly ask that users will let us know if they experience anything out of the ordinary that might be related to this change. Kind regards, Johan ter Beest RIPE Atlas Team

1 0

half dead v1 probe ?
by Matthieu Herrb 13 Jul '17

13 Jul '17

Hi, Here at Tetaneutral.net we're hosting a V1 Atlas probe since 2012 or so. A few weeks ago it started beeing marked as unconnected on the ripe atlas page : https://atlas.ripe.net/probes/523/ Since it's a v1 probe, I can only power cycle it to try to reconnect it, which I've done a number of times now, without success. It's still answering to ping requests, both on its v4 and v6 addresses and I can see some traceroute-like trafic going out of it. It's marked as "firewall problems suspected", but we don't do any firewalling on it. On IPv4 it's on a 1:1 NAT, all ports are open and forwarded in both directions, and on V6 it's routed without any filtering. Also we haven't changed anything on our infrastructure around the time it became disconnected. I'm starting to suspect a firmware upgrade problem as the one mentionned by Alun Davis in https://www.ripe.net/ripe/mail/archives/ripe-atlas/2017-June/003329.html Any suggestion before I send it back and ask for a new one ? Thanks in advance, -- Matthieu Herrb

3 2

Probe does not request IPv4 address via DHCP
by Stanish Stanishev 11 Jul '17

11 Jul '17

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

3 9

New on RIPE Labs: Anchoring Measurements - Bringing Back the Balance
by Mirjam Kuehne 06 Jul '17

06 Jul '17

Dear colleagues, Please read on RIPE Labs how we're striking a balance between probes and anchors in RIPE Atlas anchoring measurements: https://labs.ripe.net/Members/alun_davies/balancing-act Kind regards, Mirjam Kühne RIPE NCC

1 0

[ripe-atlas-tools] Anyone had success with renderer aggregate_ping?
by Stephane Bortzmeyer 05 Jul '17

05 Jul '17

I cannot make the renderer aggregate_ping work: https://github.com/RIPE-NCC/ripe-atlas-tools/issues/186

1 0

New on RIPE Labs: Next Five Sponsored RIPE Atlas Anchors
by Mirjam Kuehne 04 Jul '17

04 Jul '17

Dear colleagues, The second phase of the RIPE NCC’s campaign to sponsor 15 RIPE Atlas anchors has been completed, with another five anchor hosts selected for sponsorship. We want to tell you about the new anchor hosts and also take a look at some related developments here at the RIPE NCC: https://labs.ripe.net/Members/alun_davies/next-five-sponsored-ripe-atlas-an… Kind regards, Mirjam Kühne RIPE NCC

1 0

Monthly probe report says it was down for the entire month
by James Andrewartha 03 Jul '17

03 Jul '17

Hi, I got my monthly probe report and oddly it says my probe was down for the entire month, rather than the 14d 6h 55m (47.63%) the website says. I've only just been able to reboot the probe (it didn't respond to ping at all), and it has come up with a new IP, but hasn't connected to the controller. Some things have updated with the new IP, eg p29530.probes.atlas.ripe.net but others like the local address are still showing the old IP. Should I try doing the recovery procedure? Thanks, James -------- Forwarded Message -------- Subject: Monthly probe report for CCGS Perth (#29530) Date: Sat, 1 Jul 2017 01:50:21 +0000 From: RIPE Atlas <no-reply(a)ripe.net> Reply-To: RIPE Atlas <no-reply(a)ripe.net> To: linuxadmin(a)ccgs.wa.edu.au Dear James Andrewartha, This is your monthly availability report for probe 29530 (CCGS Perth). Calculation interval : 2017-06-01 00:00:00 - 2017-07-01 00:00:00 Total Connected Time : 0d 00:00 Total Disconnected Time : 30d 00:00 Total Availability : 0.00% This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to receive reports about probe availability. If you would like to change this, or disable this reporting altogether, please go to https://atlas.ripe.net/probes/29530/, click the "Edit" button next to "Notifications", and use the form there to define what you want. Kind regards, RIPE Atlas Team

2 1

Re: [atlas] VM probes (was Re: Feature request for IP record route feature in RIPE Atlas)
by mostafa shahdadi 21 Jun '17

21 Jun '17

Sent from my iPad

1 0

atlas feature suggestion
by Geert Jan de Groot 20 Jun '17

20 Jun '17

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

1 0

Improvements to the RIPE Atlas measurement creation form
by Chris Amin 15 Jun '17

15 Jun '17

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

1 0

Firmware Update for RIPE Atlas V1 and V2 Probes
by Alun Davies 09 Jun '17

09 Jun '17

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

1 0

Anchors as target hosts for SLA
by Antonio Prado 06 Jun '17

06 Jun '17

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

3 3

Surplus RIPE Atlas credit offer
by Dan Jones 31 May '17

31 May '17

I have a large pool of unused credits if anyone needs any transferred to their account. I likely won't be using them so they should go to a good cause. Dan Jones

1 0

Three improvement suggestions
by Michael Oghia 31 May '17

31 May '17

Dear all, I have three suggestions for how to improve the Atlas program: 1. Set up an automatic transfer system? That way, if someone accrues credits they would like to transfer, we can set it up to do so automatically once we hit 1,000,000 credits (think of it as similar to a bank's auto-pay system). 2. A system where, if someone needs extra credits, they can automatically request them to be deducted (with those who opt-in) from someone like myself with unused / extra credits. 3. Email notifications of when we have accrued 1,000,000 credits (my apologies if this is already a feature). I say this because I don't use my credits, so I don't want them to go to waste. It would be much more efficient if someone who needed them could access them any time (assuming I already gave permission for that (opted-in)). Let me know if anyone needs clarification about my suggestions. Best, -Michael __________________ Michael J. Oghia EuroDIG 2017 focal point (WS 11 <http://eurodigwiki.org/wiki/WS_11_2017>) Independent #netgov consultant & editor Belgrade, Serbia Skype: mikeoghia Twitter <https://www.twitter.com/MikeOghia> *|* LinkedIn <https://www.linkedin.com/in/mikeoghia>

7 9

TLS tests with login.live.com
by Stephane Bortzmeyer 29 May '17

29 May '17

TLS tests from the Atlas probes work for me, for every server... *but* login.live.com, for which I always get timeouts (it works with other TLS clients). Measurement #8775150 if someone has an idea...

2 4

Need host with very large ping times
by Marat Khalili 29 May '17

29 May '17

I have an interesting problem: I need some host that doesn't mind being pinged but with several seconds of RTT (that's thousands milliseconds; from Moscow, but it probably doesn't matter). Amazingly, I could not easily find one. I even tried to ping-scan IP ranges of Antarctica, but those hosts that responded did so in fraction of a second. Not much luck with North Korea (mostly down), Taiwan (internet is much better than it used to be) and several other suspect countries. (Though I'm not sure my tests are correct, since firewall processing of such long response times is one of the things I'm trying to find out.) Is it possible to somehow find one using RIPE ATLAS, preferably without ping-scanning whole internet? Would be especially great if it responded to other types of ping beside ICMP. -- With Best Regards, Marat Khalili

6 9

challenges with reproducibility
by Bajpai, Vaibhav 28 May '17

28 May '17

Dear RIPE Atlas / MAT WG -- sorry for cross-posting. A few of us wrote a paper discussing challenges with ‘reproducibility’ of research and certain steps we can take to initiate a cultural change. This paper will appear at the SIGCOMM reproducibility workshop [b]; the paper is now available online [a]. Thought to share it along: [a] http://vaibhavbajpai.com/documents/papers/proceedings/reproducibility-sigco… [b] http://conferences.sigcomm.org/sigcomm/2017/workshop-reproducibility.html -- Vaibhav -------------------------- Vaibhav Bajpai www.vaibhavbajpai.com Postdoctoral Researcher TU Munich, Germany --------------------------

1 0

DNS and recursion
by Stephane Bortzmeyer 27 May '17

27 May '17

API v1 had a field recursion_desired when performing DNS measurements. If I remember correctly (but I cannot find the reference right now), it worked only when querying a specific name server, and not when using the probe's own resolver, to avoid cache snooping. API v2 has instead a set_rd_bit. Documentation <https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Measurement_Li…> does not indicate its default value. Anyway, my experience with the API is that the RD (Recursion Desired) bit is always set, whether with 'set_rd_bit': False or with 'set_rd_bit': True, and independant of use_probe_resolver. I can understand this choice for privacy reasons (RFC 7626, section 2.3). But, in that case, the documentation should be fixed. Anything I missed? (Here, a request by a probe, the + after the Query ID - here, 52379 - means the RD bit is set 12:22:23.170304 IP (tos 0x0, ttl 64, id 2287, offset 0, flags [DF], proto UDP (17), length 65) 192.168.2.8.45955 > 212.27.40.240.53: [udp sum ok] 52379+ AAAA? uucp.bortzmeyer.org. (37)

2 2

DNS measurement
by Stanish Stanishev 25 May '17

25 May '17

Hello, I am having troubles running a a DNS measurement against our DNS cache servers. I get Error: Timeout: 5000 every time I run such measurement. Please see measurement ID #8771668 for example. In this measurement I've selected the two anchors (ids 6262 and 6263) hosted by us (Vivacom) as the source and the target is one of our DNS cache servers - 212.39.90.42. There is no firewalls or other preventing our anchors from reaching the 212.39.90.42 and also the DNS cache server running on 212.39.90.42 is configured to serve queries from Anchors' IPs. What am I doing wrong ? Thanks, Stanish Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

RIPE Atlas V1 Probe Issue
by Alun Davies 18 May '17

18 May '17

Hello all, Due to an unfortunate bug in a recently released probe firmware (version 4760), a number of RIPE Atlas V1 probes are not currently able to connect to the network. The bug leads to excessive memory fragmentation which impacts that V1 probes because they have no MMU and only 8 MByte worth of memory. For reasons that are not yet clear, the issue has only affected well below half of the V1 probes. We are working on a new firmware that will correct this issue, but probes that will not connect will need to be returned to the RIPE NCC in order for the fix to be carried out. Once the new firmware is ready, users can either return their V1 probes to us to be fixed, or request a V3 probe instead. Thank you to Wilfred Woeber for reporting this and requesting an update on the current issue with the V1 probes. Cheers, Alun Davies RIPE NCC

4 4

Introducing blitzortung.org Network for Lightning and Thunderstorms in Real Time
by Jean-Michel Pouré 13 May '17

13 May '17

Dear Friends from RIPE community, This is my first post on the forum. I would like to point out to the community the existence of a free community providing a network device for Lightning and Thunderstorms in Real Time: http://blitzortung.org The device works the same as a RIPE probe, except that it collects information about lightning via radio and delivers the information to a central network of computers for data processing. If you are network specialist hosting very expensive network devices, it might be interesting for you to participate in the effort to build a free community and host a Blitzordnung device in your premisses. All information can be found on http://blitzortung.org and BlitzOrdnung forum : http://en.blitzortung.org/forum.php BlitzOrdnung coverage is good in Europe and North America, but BlitzOrdnung needs more devices in Africa/South America/China and Russia. All help is welcome and may save you a lot of money in lightning protection. Kind regards, Kellogs

1 0

Results of the DNS Measurements hackathon - article now published on RIPE Labs
by Vesna Manojlovic 11 May '17

11 May '17

Dear all, in April we held a fifth hackathon. Altho the topic was DNS, most of the projects were using RIPE Atlas data. Therefore, I invite you to check out the hackathon results, follow the links to the code, and enjoy the photos that attempt to transfer some of the atmosphere.. https://labs.ripe.net/Members/becha/results-dns-measurements-hackathon Please do take part: - use the tools/SW and let us know your experiences with it - modify the code & publish it again on GitHub - join our next hackathon - as a host, sponsor, or participant (date & location & topic to be announced soon!) Let me know in person if you are interested; and otherwise, post your comments or questions on the list, greetings from RIPE74, Vesna

1 0