- ripe-atlas - mailman.ripe.net

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