- ripe-atlas - mailman.ripe.net

Probe didn't get static IP address
by Walid Ben Ali 29 Dec '17

29 Dec '17

Dear ripe Atlas support, My probe ID 26099<https://atlas.ripe.net/probes/26099/> didn't reconize the static IP adress. Knowing that it worked for days. Today I just tried to know if it is a network problem or a probe issu, I just conenct it into DHCP and the probe works., I also pluged my Laptop to the netwok with the static IP address (in order to know if it is a network issu) and also the network ork perfectly, I even surfed on the RIPE NCC web site without any pb. So please RIPE Atlas support, could you bring me some help? I returned back the probe to the nework, the static specified IP is kept, (with the DNS and submask and so on), but the probe didn't work. Looking for your support Many thanks

1 0

New on RIPE Labs: Plan of Action for RIPE Atlas Anchor VMs
by Mirjam Kuehne 27 Dec '17

27 Dec '17

Dear colleagues, Members of the RIPE Atlas community have asked us to implement RIPE Atlas vantage points as Virtual Machines (VMs). In order to address these requests, we came up with a plan of action: https://labs.ripe.net/Members/kistel/plan-of-action-for-ripe-atlas-anchor-v… Kind regards, Mirjam Kühne RIPE NCC

4 3

Probe disconnects every 2 hours
by Daniel AJ Sokolov 21 Dec '17

21 Dec '17

Hello, the logs for my probe (version 1) show that is has been disconnecting very regularly every 2 hours. The uptimes are always +/- 1 hour 50 minutes, followed by a disconnect period of 5, 8, or 11 minutes. Out of my last 25 connects, 20 are like that. 3 have double the uptime (about 3 hours and 50 minutes), only one has almost 24 hours, and the current one is 6 hours and counting. The disconnects there were, again, 5, 8, or 11 minutes. However, I to not notice similar disconnects as a user of the same network. I sometimes listen to online streams for more then 2 hours without interruption. I work on my computer for more than 2 hours and don't notice these interruptions of my internet access. It's all IPv4; no IPv6 here. The controller is ctr-fnc01. What could be the cause of these log entries? BR Daniel AJ

2 3

Any recommendations on how I can get ATLAS admins to reset my two-step verification?
by Jan Galkowski 20 Dec '17

20 Dec '17

Hi I have an ATLAS probe, long connected with a lot of credits. I have a RIPE NCC account, where the email and passcode are both recognized. Unfortunately, I apparently also have two-step verification set up. I don't recall doing that, but, then, it's probably my memory is at fault. And I do not know where, if anywhere, I put the notes for the 32 bit "emergency" code. The guidance at the site is to reach out to the ATLAS administrations in this situation for, I presume a reset. I have looked for additional information, and opened tickets. Unfortunately, the link to the FAQ describing this security facility is "404", and the tickets have gone acknowledged by the ticketing system, but not responded to. My interest is keen, because I was hoping to get some measurements research done by the start of the New Year. Alas. I have things I can do towards this, but has anyone else been in a similar situation? Advice? Thanks very much, Merry Newtonmas, and best wishes for the New Year. - Jan Galkowski, Westwood, MA.

2 2

Second Part of RIPE Atlas as IoT Devices - The RIPE Atlas Architecture
by Mirjam Kuehne 19 Dec '17

19 Dec '17

Dear colleagues, Here is the second part of the story about RIPE Atlas as IoT Devices. This time we we give some insights into the overall architecture of the RIPE Atlas network and how we manage secure communication with our probe flock. https://labs.ripe.net/Members/kistel/ripe-atlas-architecture-how-we-manage-… Kind regards, Mirjam Kühne RIPE NCC

1 0

Missing servers in DNSMON
by Chris Amin 13 Dec '17

13 Dec '17

Dear colleagues, It was recently brought to our attention that a small number of name servers were not being included in the visualisations on DNSMON. This issue has now been fixed, but you may notice a gap between mid-September and mid-December when visualising large time ranges for the affected servers. Apologies for any confusion or inconvenience caused. The affected zones and nameservers are: hk. - 203.119.87.218 xn--j6w193g. - 203.119.87.218 il. - 128.139.35.5 il. - 194.146.106.122 il. - 2001:67c:1010:31::53 mx. - 2001:13c7:7000::1 pl. - 2001:1a68:0:17::238 pl. - 2001:a10:121:1::156 pl. - 2a00:4120:8000:2::186 Kind regards, Chris Amin RIPE NCC

1 0

New on RIPE Labs: Measuring Network Behaviour with RIPE Atlas
by Mirjam Kuehne 08 Dec '17

08 Dec '17

Dear colleagues, In this article Marcel Flores and Stephen McQuistin describe how they used RIPE Atlas to understand the network behaviours their end-users are experiencing: https://labs.ripe.net/Members/verizon_digital/seeing-the-world-with-ripe-at… Kind regards, Mirjam Kühne RIPE NCC

1 0

ULA detected by probe?
by JORDI PALET MARTINEZ 06 Dec '17

06 Dec '17

Hi, I’ve two probes in two networks, with exactly the same config in both routers (which are the same, using LEDE). ULA is NOT configured in the router and no other device in the network can see the ULA. However, one of the probes, shows the TAG “IPv6 ULA” And Addresses fd3f:4830:fd21:0:220:4aff:febf:ffaf/64 2001:…. How is that possible and how to clean up it? Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

2 1

Problem with new Openipmap
by Klaus Darilion 06 Dec '17

06 Dec '17

Hi! I just noticed the new interface of Openipmap. Nice, but unfortunately not as useful as the old one: 1. clicking on the graph does not show the trace 2. it does not show 50 traces as the last one (I need plenty of traceroutes for network optimization, not only 10) 3. there should be a possibillity to mark a location as wrong. E.g. see https://atlas.ripe.net/measurements/10418213/#!openipmap Openipmap display Warsaw as target where all this traces terminate in New York as this IP address is an Anycast IP address and therefore it must no be mapped to a single location. hence, for Anycast IPs there should be feature to mark the IP as Anycast. Then the final target is usually the location of the IP address before. regards Klaus

3 2

Effect of "Resolve on Probe"-option
by Tim Wattenberg 04 Dec '17

04 Dec '17

Hi everyone, I think I don’t quite understand the effect of the „Resolve on Probe“ option when creating a measurement. The form says it forces the probe to do DNS resolution, the API reference says that it indicates that a name should be resolved (using DNS) on the probe otherwise it will be resolved on the RIPE Atlas servers. Could someone explain what this means for example if I have a simple measurement for querying the A record of a given domain via the probe’s resolvers? Thanks, Tim

4 4