- ripe-atlas - mailman.ripe.net

New on RIPE Labs: RIPE Atlas on the Go
by Mirjam Kuehne 15 Nov '17

15 Nov '17

Dear colleagues, Ollivier Robert just released a tool that provides access to the RIPE Atlas API in Go. Please find more details on RIPE Labs: https://labs.ripe.net/Members/ollivier_robert/ripe-atlas-on-the-go Kind regards, Mirjam Kühne RIPE NCC

1 0

New vendor for RIPE Atlas v3 anchors
by Alun Davies 15 Nov '17

15 Nov '17

Dear all, Meconet, the latest addition to our list of vendors for RIPE Atlas v3 anchors, is offering the new anchor hardware fully assembled with 3 years warranty. The RIPE Atlas anchor from Meconet comes in a 19” chassis with integrated power supply: https://shop.meconet.de/a/117330?language=en <https://shop.meconet.de/a/117330?language=en> Whilst Meconet is currently the only one offering the device fully assembled, there are other vendors listed on the following page: https://atlas.ripe.net/get-involved/become-an-anchor-host/ <https://atlas.ripe.net/get-involved/become-an-anchor-host/> Updated information on the latest generation of RIPE Atlas anchors can be found in the following RIPE Labs article: https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors <https://labs.ripe.net/Members/alun_davies/introducing-ripe-atlas-v3-anchors> Best regards, Alun Davies RIPE NCC

4 3

Running RIPE probe VM
by Evgeniy Sudyr 14 Nov '17

14 Nov '17

Hello All, I'm interesting for running RIPE probe on VM or Docker container. Any chance to get this idea real? -- With regards, Eugene Sudyr

2 2

A Go library to talk to RIPE Atlas
by Stephane Bortzmeyer 14 Nov '17

14 Nov '17

https://blog.keltia.net/2017/11/13/ripe-atlas-is-usable-dot-dot-dot/ [Still a bit rough...]

1 0

Probe disconnected – cold reboot required (ctr-ams08)
by Christian Schrötter 13 Nov '17

13 Nov '17

Hello Atlas-Users! Do you have any problems with your probes today? Mine disconnected two times in the last ~15 hours and never came back online. Internet is stable and SD-card looks ok. I had to force a cold restart to get it back online. Strange thing, it's the first time in two years. Old uptime was 99 days... :-/ -- With kind regards, Christian Schrötter

1 0

New on RIPE Labs: Verfploeter: Broad and Load-aware Anycast Mapping
by Mirjam Kuehne 13 Nov '17

13 Nov '17

Dear colleagues, Here is a summary of a research paper written by Wes Hardaker, Wouter de Vries and Ricardo Schmidt: Verfploeter: Broad and Load-aware Anycast Mapping IP anycast provides DNS operators and CDNs with automatic fail-over and reduced latency by breaking the Internet into catchments, each served by a different anycast site. https://labs.ripe.net/Members/wouter_de_vries/verfploeter-broad-and-load-aw… Kind regards, Mirjam Kühne RIPE NCC

1 0

Recent TLS supported by probes?
by Stephane Bortzmeyer 13 Nov '17

13 Nov '17

I cannot get the certificate for <https://dns-resolver.yeti.eu.org/> (measurement #10174881): "alert" is "{u'description': 40, u'level': 2}". It works with other, more "mainstream", HTTPS sites (see #10174883). I suspect this is because the probes don't handle the recent TLS stuff. Can anyone confirm or infirm?

2 1

Atlas Measurements
by Tom Glass 13 Nov '17

13 Nov '17

Hello all, Hope you are having a great weekend. I just stopped by to ask if you guys would know where/if I can add new probes to an existing measurement. A new probe has appeared in the area we are monitoring and I was hoping there was a way of adding it without recreating the measurement? Cheers, all, Tom

2 1

Odd queries from probe
by Jared Mauch 10 Nov '17

10 Nov '17

While doing some debugging of my home network, I noticed some odd queries from the probe, namely this one: 02:28:36.921622 IP6 fe80::a2f3:c1ff:fec4:479f.51123 > 2001:558:feed::2.53: 23808+ A? 12920.atlas.ripe.net.b61065696c194ac3. (55) Is this some captive portal/wildcarding detection, or perhaps some other software issue? curious, - Jared

2 1

IPv4 leading zeroes and weird interface behaviour
by Max Grobecker 30 Oct '17

30 Oct '17

Hello, is there - by standard - a definition on how to represent an IPv4 address? I have (for example) the IP address "73.0.255.229", which can IMHO also be written as "073.000.255.229" as the leading zeroes are not giving any changes to the binary representation of this address. Am I right on this? But: When I lookup this IP address on https://stat.ripe.net/073.000.255.229 the first octet is internally getting swapped to "59". This can be explained, if you take "073" as an octal value and convert it to a decimal value. It is definitely a octal-to-decimal conversion thing, as for example also the value "010" is getting replaced by "8" and so on. Now I'm puzzled: Of course, writing IPv4 octets with leading zeroes is not very common. But: Is it officially prohibited or discouraged? This weird conversion also happens inside the "geoiplookup" tool by MaxMind and I'm not sure if I'm going to be the moron in this story or if I found the same bug inside multiple softwares at once ;-) Thanks and greetings from Wuppertal Max

8 7