- ripe-atlas - mailman.ripe.net

New on RIPE Labs: RIPE Atlas WiFi Measurements
by Robert Kisteleki 13 Nov '15

13 Nov '15

Dear colleagues, We're thinking about implementing WiFi measurements in RIPE Atlas, and we want to know what you think. There are several different ways we could do this - find out more on RIPE Labs and then take our poll to make your voice heard! https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-wifi-measure… Kind regards, Mirjam Kuehne & Robert Kisteleki RIPE NCC

2 1

edst 193.0.0.228 in traceroute results
by Yang Yu 13 Nov '15

13 Nov '15

Hello, In https://atlas.ripe.net/measurements/2928258, I did a UDP traceroute. "edst":"193.0.0.228" from first hop and second hop somehow showed up in the results after the last hop that responded to traceroute, which should have been a reply to buil-in measurement to tt01.ripe.net. And under maps tab the result is presented with the first 2 hops showing up after several non-responding hops. Is this a bug? I actually see it happening quite often in atlas traceroute results with firmware > 4680. Another example is https://atlas.ripe.net/measurements/2928262 >>> https://atlas.ripe.net/docs/bugs/ 2015-03-04 Before firmware 4680, traceroute could experience interference from other measurements. In general, periodic traceroutes did not interfere with other periodic traceroutes, but could experience interference from one-off traceroutes. Typically, this interference will show up in the 'edst' field. This problem was fixed in 4680. Thanks. Yang

1 0

Feature request for IP record route feature in RIPE Atlas
by Pavel Odintsov 11 Nov '15

11 Nov '15

Hello, dear Atlas Team! As host of RIPE Anchor #6111 I have some feedback about your awesome service! Thanks for your Great Job in measuring Internet! I would like to ask very important feature for measuring reverse trace route. I'm speaking about IP record route option which could track up to 9 hops of reverse path. I want to know path to my hosts from networks who haven't RIPE Atlas. Actually I could not implement this feature due to 9 hop restriction in IP header. But RIPE Atlas offer really huge coverage over the World and we could reach really any host with <7 hops. But we haven't this feature in RIPE Atlas. Finally with this feature we could build full adjacently map over all the World. I have checked implementation details here https://labs.ripe.net/Members/philip_homburg/ripe-atlas-measurements-source… Looks like we need to build separate libevent based toolkit for this task or add this feature to ping tool. But unfortunately I could not find any docs about deploy of RIPE source code for development. Could you share some information? -- Sincerely yours, Pavel Odintsov

14 34

RIPE Atlas anchor self assembly
by Michela Galante 10 Nov '15

10 Nov '15

Hi everyone, Some people on this list have been asking about the possibility of purchasing hardware for a RIPE Atlas anchor by themselves and assembling it. This is indeed possible. However we do not recommend it because if the assembled hardware is not exactly to our specifications, we will not be able to use it as an anchor. If you still wish to assemble an anchor by yourself, you can find step by step instructions here: https://atlas.ripe.net/docs/anchor-installation/ Please, note that you do need more than the Soekris box. The anchor consists of: • Soekris Net6501-70 board • 1U 19-inch rack-mounted case • Intel SSD 525 or 530 series 240GB mSATA SSD More requirements are listed here: https://atlas.ripe.net/get-involved/become-an-anchor-host/ If you have more questions about anchors, please email to atlas(a)ripe.net and we will be very happy to help you. Best regards, Michela Galante Measurements Community Building RIPE NCC

5 4

Sharing credits with colleagues
by Oliver Haake 10 Nov '15

10 Nov '15

Hey there, I'm very curious if you guys have an ETA for the "Sharing credits with colleagues" feature. Any ideas? Cheers, Oliver

3 4

Read on RIPE Labs about the newest features & the community efforts
by Vesna Manojlovic 05 Nov '15

05 Nov '15

Dear colleagues, There are a number of interesting new features and enhancements for RIPE Atlas users. Learn how you can put them to use: https://labs.ripe.net/Members/kistel/ripe-atlas-update-http-measurements-cl… Regards, Vesna

3 2

ntp built-in measurements?
by Bajpai, Vaibhav 04 Nov '15

04 Nov '15

Dear RIPE Atlas, Do the probes not run (new) NTP measurements as built-in measurements? — I was glancing over the measurement data pushed by my probe, but I do not see any NTP measurement data. Although, when I try to provision a UDM, I do get an option to schedule an NTP measurement. Thanks! Best, Vaibhav ===================================================== Vaibhav Bajpai Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com =====================================================

3 4

Question about the hardware
by Micha Bailey 30 Oct '15

30 Oct '15

I just got my Probe, and I was wondering what the thought/planning process was when they were designed. Why use a $40 wireless router/access point? I would have thought that cheaper options would be available that provide the requirements (processor and a network port).

3 3

Next week: webinar on "Advanced RIPE Atlas Usage"
by Michela Galante 29 Oct '15

29 Oct '15

Dear colleagues, On Thursday 5 November, 1:30 PM Amsterdam time we are hosting, for the 4th time, webinar on "Advanced RIPE Atlas Usage", aiming to teach network operators how to use RIPE Atlas measurements for network monitoring and troubleshooting. Register now at: https://lirportal.ripe.net/training/register/courseCode/WEB20150046 Web-registration is *only* possible for LIRs (RIPE NCC members). Non-members of RIPE NCC (people who do not have "Reg-ID") can email training(a)ripe.net and be manually registered. More details below. -------------------------- https://www.ripe.net/support/training/learn-online/webinars/advanced-ripe-a… This is part of the series of interactive on-line learning sessions, that give you the opportunity to learn and interact with trainers without leaving your desk, as well as for hands-on practice, and to get your questions answered by developers. Learn how to: - Use RIPE Atlas measurements for network monitoring and troubleshooting - Use API calls for measurement creation - Integrate RIPE Atlas with existing monitoring systems Webinars start at 12:30 UTC, and take about one hour. ----------------------------- We look forward to seeing you online. Kind regards, Michela Galante and Vesna Manojlovic RIPE NCC

1 0

'new set wizzard' broken?
by newsboonie 29 Oct '15

29 Oct '15

Hi, It seems the 'new set wizzard' for selecting probes is not working anymore. It does show the map but the input box is missing. Is it just me or is it broken? Thanks, Dave

2 2

Leaseweb Network (US, Manassas and San Francisco) have joined RIPE Atlas anchors
by Michela Galante 28 Oct '15

28 Oct '15

Dear RIPE Atlas users, We're happy to announce that two more RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors, both hosted by Leaseweb Network in United States, are: us-mnz-as30633, in Manassas (Virginia) us-sfo-as7203, in San Francisco (California) Congratulations to Leaseweb Network for their third and fourth anchor online! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards these anchors from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

GEMNET LLC (Ulaanbaatar, Mongolia) has joined RIPE Atlas Anchors
by Michela Galante 28 Oct '15

28 Oct '15

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called mn-uln-as45204 and it is hosted by GEMNET LLC in Ulaanbaatar, Mongolia. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team atlas(a)ripe.net

4 3

Probe not appearing in the Atlas
by Ismael Carmona 28 Oct '15

28 Oct '15

Hello, We have the probe #24142, it gets DHCP fine (91.123.100.8) and we can ping it and see with sflow that it perform requests to external servers but we cannot find it online in the atlas. We already tried rebooting it. Any idea how we can make it appear online in the atlas page? Thank you, Ismael

3 2

traceroute - view latest results
by gboonie 27 Oct '15

27 Oct '15

What should the blue 'i' do at the right side of a traceroute measurement? Hovering over it shows a 'view lastest results' message. For example in this measurement: https://atlas.ripe.net/measurements/2845726/#!probes I'm hoping it will soon display all the hops of a traceroute. Just like the traceroutes of the built-in measurements. Just like: Thanks, Dave

4 5

filter ping results by AS
by Sebastian Neuner 26 Oct '15

26 Oct '15

Hi there, I'm currently trying to figure out, how I can get all ping results to(/from) my AS within a certain time frame, to run some statistics. The REST-API documentation [0] states, that measurements can be filtered by dst_asn, but it doesn't seem to influence the results I'm getting: > filter: { > 'start_time__gt': 1445231337, > 'type': 'ping', > 'dst_asn': 553 > } > > dst_asn dst_name > -------------------------------------------- > 2607 sk-bts-as2607.anchors.atlas.ripe.net > 2602 lu-lux-as2602.anchors.atlas.ripe.net > 16154 88.213.204.251 > 1853 at-vie-as1853.anchors.atlas.ripe.net > 8608 195.18.114.5 > 32475 www.siteground.com > 12322 78.194.137.59 > None ch-zrh-as559.anchors.atlas.ripe.net Also, why do some measurements have no dst_asn? Regards, Sebastian [0] https://atlas.ripe.net/docs/rest/

2 7

Private Probes: What's the Point
by Jonathan Brewer 24 Oct '15

24 Oct '15

Hi All, I've run into a few probes marked private, and when I've found & asked the owners, they didn't realise they'd done anything restrictive or harmful to researchers by marking their probes private. Intrigued at this phenomena, I had a look at the probe metadata. Right now I think there are 1,534 Atlas probes that are active and connected to the network, but marked private. What's the point of having private probes in the network? Do their hosts still earn credits they can use on public probes? Should they be? Are private probe hosts helping the project? The FAQ says nothing about private probes, so I thought I would ask here. Thanks, Jon

8 12

Anchors and NTP back to the future
by Stephane Bortzmeyer 23 Oct '15

23 Oct '15

Some anchors appear to be reachable with NTP but most of them are not. I guess it means the anchor always has a NTP server (and I assume it is on purpose) but many networks filter it. What is the good recommanded practice? Specially in the light of the Back to the Future attack <http://www.cs.bu.edu/~goldbe/NTPattack.html>

1 0

Public vs. Non-Public Probes
by Vesna Manojlovic 22 Oct '15

22 Oct '15

Hi Jonathan and others, Thanks for bringing this point up again. I hope others will feel free to join in the discussion. As Wilfried mentioned, we did have a discussion about public and non-public probes some time ago. Here are the relevant posts: RIPE Labs article proposing making RIPE Atlas probes and measurements more public: https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-p… Discussion on the ripe-atlas list: https://www.ripe.net/ripe/mail/archives/mat-wg/2013-December/000399.html Conclusion: https://www.ripe.net/ripe/mail/archives/mat-wg/2014-March/000436.html Consequences: new terms & conditions, with more clarification on this topic: https://labs.ripe.net/Members/becha/ripe-atlas-moving-to-production-service & https://atlas.ripe.net/legal/terms-conditions/ As you can see from the discussions above, some RIPE Atlas users felt it was important to retain the choice of marking their probes “non-public”. We do encourage all RIPE Atlas users to mark their probes “public” for the greatest benefit to the community, and the majority of probes are public. However, non-public probes are still used both for built-in measurements and user-defined measurements; they are just not listed on the web or API. Once a user decides to plug a probe into their network, IP address information can no longer remain "private". This is why we prefer to refer to them as “non-public” probes rather than truly “private” probes. Of course, we care very much about protecting probe hosts’ privacy and we never make personal information like email addresses or MAC addresses public. There is some more information about this in the FAQs on the RIPE Atlas website under the answers to "Will my IP address show up in measurements done by my probe?” and "Is the measurement data made public?”, but the RIPE Labs article referenced above contains the most detailed information on the topic. Thanks again for your thoughts on this, and please let us know if you have any other questions or comments. Regards, Vesna

2 1

Prove v3 not connecting after powercyle
by Jeroen Bogers 20 Oct '15

20 Oct '15

Hi all, Two days ago I had to powercycle some of my network equipment, including my Atlas V3 probe. After the powercycle, the probe did not come back online. After booting, the first and second light (power and the one next to it) remain lit (not blinking). This is not a state that is listed in the FAQ: https://atlas.ripe.net/about/faq/#what-do-the-lights-on-the-side-of-the-pro… The only status that comes close is the 'Running from built-in flash' state, but led 2 should be blinking then? Does someone here have an idea what is wrong with my probe (and how to fix it)? I already tried connecting it to a different network port and power source, but this did not make any difference. The switch port the probe is connected to does light up, so the Ethernet port seems to be functioning. With kind regards, Jeroen Bogers

1 0

[Feature Request] Show probe address on failure notifications
by Brian Rak 16 Oct '15

16 Oct '15

I recently received one an email indicating one of my probes is offline: This is the second reminder that your probe (#20689 ) is not connected to our infrastructure and has been disconnected since 2015-09-14 09:37 UTC. Could you please check whether everything is set up correctly on your side? If it is, and your probe is still reported as disconnected when you log in at https://atlas.ripe.net, please reply to this email so that we can follow up. Is there any way these can be modified to include further information (like the probe's address, or basically anything about it)? Probe 20689 means nothing to me, so I have to log in to take a look at exactly what it is, and where I need to go to fix it.

2 2

New on RIPE Labs: Researching F-root Anycast Placement Using RIPE Atlas
by Michela Galante 14 Oct '15

14 Oct '15

Dear colleagues, Please find a new article on RIPE Labs: https://labs.ripe.net/Members/ray_bellis/researching-f-root-anycast-placeme… In order to expand the reach of F-root, Ray Bellis looked at where queries to F-root are coming from and where it would make most sense to place new nodes. As a first step, Ray looked at the existing nodes to see how they behave and if there is anything that can be improved. He used RIPE Atlas to do this. Kind regards, Michela Galante RIPE NCC

1 0

More built in IPv6 tests
by Brzozowski, John 12 Oct '15

12 Oct '15

Would it be possible to include some new built in measurements for the following: * IPv6 only capable * IPv6 preferred (and perhaps IPv6 capable, this is different than IPv6 only capable above) * Compare IPv4 and IPv6 performance over HTTP John +1-484-962-0060 -----Original Message----- From: ripe-atlas <ripe-atlas-bounces(a)ripe.net> on behalf of Robert Kisteleki <robert(a)ripe.net> Organization: RIPE NCC Date: Sunday, October 11, 2015 at 05:04 To: Alarig Le Lay <alarig(a)grifon.fr>, "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: Re: [atlas] IPv6 only >On 2015-10-10 20:15, Alarig Le Lay wrote: >> Hi, >> >> Are the probes able to run on an IPv6 only network? I’ve configured one >> and left the default IPv4 configuration (i.e. DHCP) but the probe is not >> marked as running in the web interface. >> >> Regards, > >Hi, > >The short answer is yes, the longer one is in the FAQ: >https://atlas.ripe.net/about/faq/#i-have-an-ipv6-only-network-will-the-pro >be-work-on-it > >Regards, >Robert > >

1 0

IPv6 only
by Alarig Le Lay 11 Oct '15

11 Oct '15

Hi, Are the probes able to run on an IPv6 only network? I’ve configured one and left the default IPv4 configuration (i.e. DHCP) but the probe is not marked as running in the web interface. Regards, -- Alarig Le Lay

2 1

3rd generation probe doesn't appear as online
by Thiago Ayub 08 Oct '15

08 Oct '15

Hi, I receive a week ago our first probe but I'm unable to make it appear as online at the website. I can see it requests DHCP, it gets an IP address (NATed), it does some measurements (like HTTP and NTP) successufly but at atlas.ripe.net it is listed as 'Never online'. It rebooted around 3 times in the last week and each time was kept as least 24h in a row with no power down or cable disconnect. The MAC ADDRESS at the website matches with the MAC ADDRESS labeled in the probe. How should I proceed to get this fixed? Best regards, Thiago Ayub

7 9

Permanent private measurement
by Lorenzo Colitti 08 Oct '15

08 Oct '15

Hi Atlas folks, I'd like to use my probe to monitor the status of my home Internet connection by continuously pinging my ISP's network (which is not the first or second hop in traceroute, but something like the sixth) and perhaps www.google.com. Is there a way to do this easily using the existing UI and tools? I couldn't find any existing measurements for this. I can look at the built-in v4 and v6 measurements for K-root, which is normally very close to me, but that's not 100% representative of the status of my Internet connection because it also measures the peering exchange link between my ISP and K-root. Cheers, Lorenzo

4 6