August 2014 - ripe-atlas - mailman.ripe.net

The Beta Version of the New DNSMON is Now Available
by Vesna Manojlovic 08 Sep '14

08 Sep '14

Dear colleagues, The DNS Monitoring Service (DNSMON) has been providing a comprehensive, objective and up-to-date overview of the quality of various global and regional DNS operators' services since 2003. We are in the process of integrating DNSMON within RIPE Atlas and the beta version of the new DNSMON is now publicly available: https://atlas.ripe.net/dnsmon We have also published a RIPE Labs article detailing what’s changed in the new DNSMON: https://labs.ripe.net/Members/fatemah_mafi/an-updated-dns-monitoring-service We invite you all to try the new service and provide your feedback. We’re confident that the new DNSMON will continue to meet your needs and hope that you'll be happy with the new features. Please send your comments and questions to the DNS Working Group Mailing List at dns-wg(a)ripe.net. Kind regards, Vesna Manojlovic Measurements Community Building RIPE NCC

7 10

S-IT Informationstechnologie Betreiber (DE) has joined RIPE Atlas anchors
by Michela Galante 25 Aug '14

25 Aug '14

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 de-cal-as39702 and it is hosted by S-IT Informationstechnologie Betreiber in Calw, Germany. With this anchor we reached a total of 70 online. 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

2 1

DigitalOcean has joined RIPE Atlas anchors
by Michela Galante 19 Aug '14

19 Aug '14

Dear RIPE Atlas users, We're happy to announce that two 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 are uk-slo-as202109 located in Slough, United Kingdom and us-sfo-as14061 located in San Francisco, United States, both hosted by DigitalOcean. Congratulations to DigitalOcean for bringing their two anchors 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, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Probe on a /31 or /32 IPv4 network
by Baptiste Jonglez 18 Aug '14

18 Aug '14

Hi, We would like to deploy our Atlas probe on a separate L2 network, but without having to spend 4 IPv4 addresses (i.e. a /30 network). Using a /31 would be nice, but the web UI doesn't allow it as static IPv4 configuration ("The Gateway address should be different from the ending network address"). Would it be possible to allow /31 in the web UI? I believe the probes themselves support it. Even nicer would be support for /32 networks, even though it is perhaps less usual. This can easily be done with iproute2 on Linux, assuming the probe is 192.0.2.48/32 and its gateway is 192.0.2.1: ip addr add 192.0.2.48/32 dev eth0 ip route add 192.0.2.1/32 dev eth0 ip route add default via 192.0.2.1 or even shorter: ip addr add 192.0.2.48/32 dev eth0 ip route add default via 192.0.2.1 onlink dev eth0 Using a gateway that is not on the same subnet doesn't sound very nice, but again, the goal is to avoid wasting precious IPv4 space. Thanks, Baptiste

4 4

measurment with endtime - faulty date
by gboonie 18 Aug '14

18 Aug '14

Hi, I noticed the last few days that when I create a new measurement with a end date and time next week that I get a failure message on the next screen. --- Your measurement will start ASAP. Your measurement will end at: Y-8-16 0:i UTC. and in the next screen: Enter a valid date/time. --- What I selected was: 2014-08-16 00:45 Multiple tests on 2 different Win7 PCs give the same result. Regards, Dave

2 4

atlas on a public subnet
by James Sink 14 Aug '14

14 Aug '14

Hello all, I just received my atlas probe and am about to deploy it. However I have a question about the subnet I am going to place it it on. Is it safe to put it on an unfiltered public ip? If not what ACL should I place on the interface? Thanks --- James Sink Network Engineer P: 800-477-1477 x: 813

2 2

Current crediting issues
by Robert Kisteleki 14 Aug '14

14 Aug '14

Dear All, We have reports of the Atlas billing process doing strange things at the moment. We're investigating these and will get back to you with more information. Regards, Robert

1 2

Upcoming "Measurements Tools" Workshop for LIRs: 19 September, in Amsterdam
by Vesna Manojlovic 12 Aug '14

12 Aug '14

Dear colleagues, Training Services, RIPEstat/RIPE Atlas developers and me will be giving a "Measurements Tools" Workshop on 19 September, in Amsterdam. Registration is possible for members of RIPE NCC via LIR Portal: https://lirportal.ripe.net/training/courses Below is the preliminary information about the workshop. If you know people who would be interested, please forward this to them. Regards, Vesna Target audience: LIRs (RIPE NCC members), network operators Goal of the Measurements Tools Workshop is to convey the benefits that the network operators can gain from using RIPE NCC tools, such as RIPEstat and RIPE Atlas - through practical exercises and hands-on approach. Prerequisites: RIPE NCC Access account; general knowledge about IP networking, DNS and BGP, as well as of one/any programming language. Workshop overview: RIPEstat topics: Basic: 1) finding the information about IP resources 2) comparing resources 3) finding anti-abuse information Advanced: embedding the widget using BGplay using command-line interface analysing events (examples of uses cases) personalizing RIPEstat RIPE Atlas topics: Basic: 1) creating a measurement 2) looking-up measurements data and analyzing the data 3) monitoring: setting-up status checks Advanced: member-specific services use cases by other people analysing information in Internet Traffic Maps take part in the community: share your code, distribute the probes, install anchors…

1 0

Probe suddenly lost IPv6 connectivity
by Ondřej Caletka 11 Aug '14

11 Aug '14

Hi, strange thing happened today. My probe v2 #3467 suddenly lost IPv6 connectivity and reconnected to the control server using IPv4. The probe does not even respond to ping6 ff02::1%eth1 sent from the router. I wonder what could cause such behavior. I will try to reboot the probe once I'll reach it. -- Ondřej Caletka

2 2

Probe 2092 shown as offline for a month
by David Precious 06 Aug '14

06 Aug '14

Hi there, My v1 probe #2092 has been showing as offline for a month, despite being powered up and pinging. Yesterday I power-cycled it, and it came back up and answers pings again, but the Atlas control panel still shows it as disconnected. Is there any troubleshooting I can do to get more information? I've verified that I can ping it from my internal network. There's no egress filtering which would be blocking it from talking outbound. I've just had my router log new outbound connections then power-cycled the probe again. I saw it successfully obtain an IP via DHCP (10:13:21), then 31 minutes later, connected to oneill.atlas.ripe.net (193.0.19.12) on port 443 (10:44:50) (UK times). I have verified that another box on the same network can connect to that IP & port: [davidp@columbia:~]$ telnet 193.0.19.12 443 Trying 193.0.19.12... Connected to 193.0.19.12. Escape character is '^]'. SSH-2.0-OpenSSH_5.3 Anything else I can do to provide more useful info? Cheers Dave P -- David Precious ("bigpresh") <davidp(a)preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github

2 4