April 2016 - ripe-atlas - mailman.ripe.net

Plan to Implement RIPE Atlas WiFi Measurements
by Robert Kisteleki 09 Oct '17

09 Oct '17

Dear colleagues, We wanted to update the community and let you know that we plan to start work on the proposed experiment with WiFi measurements in mid-2016. As we communicated in a recent RIPE Labs article, we will work with GÉANT as a test partner to learn more about the operational effects of introducing WiFi measurements to the RIPE Atlas system, in addition to the benefits we believe this could provide for the entire RIPE Atlas community. Please see the article for more details if you are interested: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-wifi-measure… We will continue to update you once we’ve begun work on this plan, and we welcome your comments in the meantime. Regards, Robert Kisteleki RIPE NCC

3 3

RIPE Atlas Interface Hackathon, 21-22 May, Copenhagen
by Vesna Manojlovic 23 Jan '17

23 Jan '17

Dear colleagues, Calling all front-end developers, UI designers, network operators and other enthusiastic coders! The next RIPE Atlas hackathon takes place 21-22 May in Copenhagen, the weekend before the RIPE 72 Meeting. We're looking for creative thinkers to help us develop new interfaces for RIPE Atlas. All source code developed during the hackathon will be publicly licensed and available on GitHub, and will be free for the entire community to use. -------------------- How to Apply -------------------- Interested? Learn more and apply online today! https://atlas.ripe.net/hackathon/Interface/?pk_campaign=hackathon&pk_kwd=li… *The application deadline is 23 March* Please note that we are unfortunately unable to provide travel or accommodation funding. We look forward to seeing you there! Regards, Vesna and the RIPE Atlas Team

1 4

Probe marked as offline, but it's online...
by Christian Schrötter 10 Nov '16

10 Nov '16

Hello Atlas users! I've connected my probe to a new network environment, to test everything before the big migration starts. It came up again immediately and displayed it's new network details at the WebUI. For the first time there was an IPv6-ULA prefix visible. The router (OpenWrt 15.05) supports full IPv6 via tunnel, but it's not advertised to the probe's VLAN and blocked by firewall rules. Everything seems to work, good! I've switched it off/on for several times, went back to the old router/modem and powered it on again. After some hours I've checked the WebUI again: My probe is offline! :-( I've tested it again on the new router: Offline! Once again on the old setup: Offline! Untouched default router/modem from my ISP: Offline! Current LED status: (from 1-5; power to button) > on > off > slow blink > on > on SOS-DNS-history from Wireshark: (switch port mirrored to my analysis interface) > Standard query 0x0002 AAAA U.*************.sos.atlas.ripe.net > Standard query response 0x0002 AAAA 2001:67c:2e8:11::c100:1337 > Standard query 0x0003 A U.*************.sos.atlas.ripe.net > Standard query response 0x0003 A 193.0.19.55 The probe is online and communicates with many servers. Looks like the built-in tests are running fine. There is NTP, DNS, ICMP, UDP and HTTP traffic. But it's still offline at the WebUI. I've double and triple checked everything on my side. Any ideas what's going wrong? -- With kind regards, Christian Schrötter

2 4

Fwd: Probe 2317 is down (home fibre)
by Colin Johnston 25 Jul '16

25 Jul '16

seems fine to me ? dont have connectivity to ripe site though from BT network range in uk what is telia upto ? Colins-iMac:~ colinj$ traceroute www.ripe.net traceroute to www.ripe.net (193.0.6.139), 64 hops max, 52 byte packets 1 bthomehub (192.168.1.254) 1.913 ms 1.078 ms 1.078 ms 2 * * * 3 * * * 4 31.55.185.196 (31.55.185.196) 16.187 ms 15.477 ms 15.443 ms 5 195.99.127.142 (195.99.127.142) 15.557 ms 195.99.127.130 (195.99.127.130) 16.274 ms 195.99.127.128 (195.99.127.128) 16.602 ms 6 vhsaccess2-pos1-0.faraday.fixed.bt.net (195.99.127.9) 16.979 ms 16.611 ms 195.99.127.25 (195.99.127.25) 17.097 ms 7 166-49-211-240.eu.bt.net (166.49.211.240) 16.413 ms 166-49-211-236.eu.bt.net (166.49.211.236) 16.225 ms 166-49-211-238.eu.bt.net (166.49.211.238) 15.821 ms 8 213.248.82.249 (213.248.82.249) 16.880 ms 15.785 ms 15.470 ms 9 ldn-bb2-link.telia.net (62.115.137.194) 16.633 ms 213.248.82.249 (213.248.82.249) 15.631 ms 15.400 ms 10 ldn-bb3-link.telia.net (80.91.248.90) 15.776 ms ldn-bb2-link.telia.net (213.155.136.62) 16.815 ms adm-bb4-link.telia.net (62.115.142.221) 22.936 ms 11 adm-b2-link.telia.net (62.115.141.51) 25.759 ms adm-b2-link.telia.net (80.91.253.182) 22.263 ms adm-b2-link.telia.net (62.115.141.17) 21.979 ms 12 adm-b2-link.telia.net (80.91.253.182) 22.481 ms adm-b2-link.telia.net (62.115.141.9) 22.344 ms adm-b2-link.telia.net (62.115.141.63) 27.606 ms Colin > Begin forwarded message: > > From: RIPE Atlas (no reply) <no-reply(a)ripe.net> > Subject: Probe 2317 is down (home fibre) > Date: 21 June 2015 20:30:07 BST > To: colinj(a)mx5.org.uk > > Dear Dear colin johnston, > > Your probe 2317 has been disconnected since 2015-06-21 18:49:16 UTC. > > This is an automatically generated email from RIPE Atlas. It was sent to you because you asked to be notified if your probe becomes disconnected for more than 30 minutes. > > If you want to change this, or disable this notification altogether, please go to https://atlas.ripe.net/probes/2317/, and click the "edit" button under "Notifications". > > Kind regards, > > RIPE Atlas Team > atlas(a)ripe.net

5 7

USB drive
by Michael Ionescu 13 May '16

13 May '16

Hi all, I have a probe that's been down for several days now. I did contact RIPE about it, but support has been superficial. I also didn't yet find the level of technical detail I need in the information on the website and in this list's archives. The 8GB drive, when reformatted on a windows box with FAT32 as per support instructions, surprisingly only comes out with a 1GB partition. Inspecting the drive under linux, I find multiple partitions, with only the first containing an a fat32 filesystem: Platte /dev/sdc: 7927 MByte, 7927234560 Byte 244 Köpfe, 62 Sektoren/Spur, 1023 Zylinder, zusammen 15482880 Sektoren Einheiten = Sektoren von 1 × 512 = 512 Bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Festplattenidentifikation: 0xc3072e18 Gerät boot. Anfang Ende Blöcke Id System /dev/sdc1 2048 2099199 1048576 b W95 FAT32 /dev/sdc2 2099200 4196351 1048576 83 Linux /dev/sdc3 4196352 6293503 1048576 83 Linux On first glance, the others contain ext2 filesystems # fsck -N /dev/sdc? fsck von util-linux 2.20.1 [/sbin/fsck.vfat (1) -- /dev/sdc1] fsck.vfat /dev/sdc1 [/sbin/fsck.ext2 (2) -- /dev/sdc2] fsck.ext2 /dev/sdc2 [/sbin/fsck.ext2 (3) -- /dev/sdc3] fsck.ext2 /dev/sdc3 but on further inspections do not contain a valid magic number in their superblocks, so they are effectively unformatted. I would therefore suspect that they are not being used by the probe. Now the question: What is the correct layout supposed to look like (primary/secondary, size, ID, FS-type)? I would like to get my probe back up and running. Bonus question: What can I expect to find in point of files/data on the drive, that would tell me whether the probe was working correctly until I cut power and removed the drive? Thanks, Michael

3 6

LatencyMON Widget Y axis in milliseconds
by Marat Khalili 10 May '16

10 May '16

I'm using LatencyMON <https://atlas.ripe.net/docs/tools-latencymon/> widget to monitor my network performance. It's very convenient. Unfortunately, it always loads with latency shown in %% (of what?), not in milliseconds, so I have to make one extra click in order to view actual milliseconds. Is there some hidden switch that would make milliseconds the default? Shouldn't it be initially default in the first place? -- With Best Regards, Marat Khalili

2 4

An article/FAQ entry about probe troubleshooting
by Ondřej Caletka 02 May '16

02 May '16

Hi all, it seems that failing probes are getting more and more to be an issue, possibly due to USB flash drive failure. I think it would be nice if there was an article / FAQ entry with some official troubleshooting procedures, so we could just send a link to anybody complaining about non functional probe. Is there something like this on the roadmap? Perhaps we as the community could make something up: - how to check whether the port probe is connected to has proper IP and DNS parameters and is allowed to establish a SSH session to TCP port 443 in the Internet (beware of DPI firewalls that allow HTTPS but not SSH over 443) - how to check the LED status and the SOS list at the probe page (the current LED explanation in the FAQ is too techy and even power users like me still don't understand all presented states :) ) - how to diagnose USB flash drive failure, how to force reformatting the flash drive and how to replace it with a new one What do you think? Cheers, Ondřej Caletka CESNET

9 11

Atlas probe down and probe replacement
by Vladimir-M. Obelic 01 May '16

01 May '16

After a power outage i'm not getting the probe up. It's not even trying DHCP. What is the procedure for a probe replacement? Thanks Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 4

New on RIPE Labs: How Elasticsearch and Kibana Help us Analyse RIPE Atlas Data Logs
by Mirjam Kuehne 29 Apr '16

29 Apr '16

Dear colleagues, RIPE Atlas backend applications run on more than 40 servers. Each day these machines can produce thousands of application logs of any kind of severity level. In order to be able to track down serious errors, warnings or even unusual behaviour, we decided some time ago to try Elasticsearch as a logging sink. In this article we will look at the design of such a system and describe how we can easily make sense from an ocean of logs: https://labs.ripe.net/Members/andreas_strikos/how-elasticsearch-and-kibana-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Failure Rate on Atlas Probes
by Jonathan Brewer 23 Apr '16

23 Apr '16

Hi All, What's the known failure rate of Atlas probes, and the mean time before failure? At a guess 20% or more of the probes I've been working with have failed within their first year of deployment. Sometimes they come back with a power cycle, sometimes they don't. Regards, Jon

1 0

Probe not received
by rgnr＠riseup.net 22 Apr '16

22 Apr '16

Hey, as the subject says. It's been 4 weeks now and nothing has arrived. Any clues what to do? regards Bernd

2 1

Led WPS / RESET
by Anthony 22 Apr '16

22 Apr '16

Hello everyone, I had a power outage, so I had to reboot my box and my probe, but now the LED button "WPS / RESET" lights is this normal? Before it off extinct. thank you in advance

2 4

New on RIPE Labs: Looking at IXPs in Berlin with RIPE Atlas
by Vesna Manojlovic 21 Apr '16

21 Apr '16

Dear colleagues, The IXP country jedi tool described in earlier RIPE Labs articles, can now also be used to analyse the situation in a specific city. This time we look at Berlin, Germany: https://labs.ripe.net/Members/mirjam/using-ripe-atlas-to-look-at-ixps-in-be… Regards, Vesna

1 0

Probe status / self-help
by Robert Kisteleki 20 Apr '16

20 Apr '16

Dear All, Today we released a new feature intended to help the probe hosts detecting, understanding and fixing various issued related to probes. You should be able to see a new "Status" tab on your probe page. This is where we explain various conditions, such as USB problems, non-working IPv6 or DNS resolutions quirks. Please note that this bit is in early stages (officially labeled as beta). We believe it works in general, however for now it only explains various system tags that mark error conditions. It will have more features in the future. It is also intended to be a place where we can add features that explain, for example, "your probe behaves differently than the rest" or "path MTU issues detected" or such. We think this will be a useful feature to hosts. Let us know if you have specific suggestions for improvement. Regards, Robert Kisteleki RIPE NCC

3 2

*-capable ≠ *-works + *-doesnt-work
by Bajpai, Vaibhav 20 Apr '16

20 Apr '16

Hello, I am looking at the probe API data for connected probes (status = 1) for day = 20160418 system-ipv6-capable = 3556 system-ipv6-works = 2995 system-ipv6-doesnt-work = 710 Why is system-ipv6-works + system-ipv6-doesnt-work > system-ipv6-capable? system-ipv4-capable = 9336 system-ipv4-works = 9187 system-ipv4-doesnt-work = 67 Why is system-ipv4-works + system-ipv4-doesnt-work < system-ipv4-capable? Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================

2 2

Question
by Anthony 19 Apr '16

19 Apr '16

Hello, I would have wanted to know if my graphs probe appears well is how well does the measures not? For you everything is ok or not? : https://atlas.ripe.net/probes/27379/ thank you in advance

2 2

RIPE Atlas CLI Toolset now available on NLNOG RING
by Vesna Manojlovic 19 Apr '16

19 Apr '16

Dear colleagues, in the spirit of cooperation between the monitoring & measuring platforms, I am happy to announce: RIPE Atlas CLI Toolset have been installed on RING! If you are already participating in NLNOG RING, now you can use RIPE Atlas CLI Toolset for "quick & dirty" access to RIPE Atlas measurements & probes. More info about RING: https://ring.nlnog.net RING nodes are also available as targets through RIPE Atlas web interface for measurements creation: https://atlas.ripe.net/targets/ringnodes/list/ https://atlas.ripe.net/targets/ringnodes/map/ Regards, Vesna Reminder about CLI tools: Source: https://github.com/RIPE-NCC/ripe-atlas-tools/ Documentation: https://ripe-atlas-tools.readthedocs.org/ In addition to "raw install", tools are also packaged in many distros: OpenBSD, FreeBSD, Gentoo, Arch, Debian and Ubuntu (in progress: Fedora, Windows). Examples of usage of RIPE Atlas CLI tools on RING: ripe@ripe01:~$ ripe-atlas report 1001 --probes 1 20 bytes from probe #1 212.238.160.244 to 193.0.14.129 (193.0.14.129): ttl=59 times:6.658, 6.591, 6.298, ripe@ripe01:~$ ripe-atlas measurements --af 6 --status ongoing --limit 15 --search nlnog Filters: Search: nlnog Af: 6 Status in: (2,) Id Type Description Status ================================================================================ 1027844 traceroute Jump Ongoing 1027846 traceroute Clara DE Ongoing 1037103 ping tenet01.ring.nlnog.net Ongoing 1404594 ping RedpillLinpro-v6 Ongoing 1596748 ping world4you01.ring.nlnog.net Ongoing 1688325 ping ping6 on amazon03 Ongoing 3678270 traceroute Traceroute measurement to bluezonejordan01 Ongoing ================================================================================ Showing 7 of 7 total measurements ripe@ripe01:~$ ripe-atlas configure --setauthorisation.create=7b4c-xxxx ripe@ripe01:~$ ripe-atlas measure ping --target ping.xs4all.nl Looking good! Your measurement was created and details about it can be found here: https://atlas.ripe.net/measurements/3671547/ Connecting to stream... 48 bytes from probe #6174 217.10.140.74 to 194.109.6.8 (194.109.6.8): ttl=56 times:8.849, 8.781, 8.78, 48 bytes from probe #26941 88.85.47.152 to 194.109.6.8 (194.109.6.8): ttl=55 times:74.372, 74.487, 74.748, 48 bytes from probe #24596 176.144.180.224 to 194.109.6.8 (194.109.6.8): ttl=57 times:45.418, 45.249, 45.5, 48 bytes from probe #6187 196.10.54.135 to 194.109.6.8 (194.109.6.8): ttl=56 times:155.65, 155.58, 155.668, 48 bytes from probe #3207 37.49.102.93 to 194.109.6.8 (194.109.6.8): ttl=50 times:24.4, 27.627, 21.95, 48 bytes from probe #6186 82.195.72.11 to 194.109.6.8 (194.109.6.8): ttl=58 times:7.087, 7.101, 7.052, ... Read more about it on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/announcing-the-cli-tool…

1 0

API filtering for looking at measurements?
by Baptiste Jonglez 18 Apr '16

18 Apr '16

Hi, I would like to find measurements matching some specific conditions, so I tried to use the measurement API documented here: https://atlas.ripe.net/docs/rest/ However, filters don't seem to have the intended effect. For instance, I tried to restrict to a specific range of starting time: https://atlas.ripe.net/api/v1/measurement/?start_time__gte=1443654000&start… but looking at the first result (measurement ID 1411440), its start time is 1564618500, which is way outside of the requested range. Similarly when filtering by type: https://atlas.ripe.net/api/v1/measurement/?type=2 type=2 is supposed to be IPv4 traceroute, but the first result is measurement ID 1001, which is an IPv4 ping. Am I using the API incorrectly, or is there a bug somewhere? Thanks, Baptiste

2 2

Open ports?
by Anthony 15 Apr '16

15 Apr '16

Hello, I received my probe today and I had to disable the firewall for my box that appears connected to the site. I reactivated and after all the work area, but I would have liked to know what need had to open? How to know if everything is ok? Sorry for my English, thank you in advance

4 5

Incorrect probe connection information?
by Max Mühlbronner 13 Apr '16

13 Apr '16

Hi, I think there is a small bug/issue with the statistics of the probe (Tab : "Network") : Connection Information Time Connected Percent Last Week 9d 10h 2m 100.00% Last Month 55d 10h 2m 100.00% How could it be that Last Month my probe was connected for 55 days? (It's only a single probe) Any idea? Best Regards Max M.

3 3

Introducing the RIPE Forum
by Vesna Manojlovic 12 Apr '16

12 Apr '16

Dear colleagues, There’s a new way to participate on the RIPE Atlas mailing list! We are introducing the RIPE Forum, a web-based interface for reading and sending emails on RIPE community mailing lists. We developed the RIPE Forum in-house based on feedback we received from members of the RIPE community who wanted the option to interact and share information in a more modern way. But it’s important to note that this new interface is completely optional – those who like using the established mailing list system can continue on as they always have, and won’t notice any difference. RIPE Atlas mailing list will be the first one. We have plans to make the RIPE Forum available for other RIPE Community mailings lists after the RIPE 72 Meeting in May. If you’re interested, you can start using it here: https://www.ripe.net/participate/mail/forum/ We created a special mailing list for testing purposes, so that any conversations about the platform itself can be contained there without disrupting the regular flow of discussions on the RIPE Atlas mailing list. Feel free to send test messages and try out the RIPE Forum on this special list: https://www.ripe.net/participate/mail/forum/ripe-forum-test Learn more how the forum works and the background of the project: https://labs.ripe.net/Members/marco_schmidt/introducing-the-ripe-forum The forum is still in "beta" status – there are likely still some bugs and we are continuously working to improve things, so please keep that in mind while exploring the forum. You can give your feedback by clicking on the “Report a bug” button on the forum, or leave a comment on the above RIPE Labs article. We hope you’ll enjoy the RIPE Forum, and look forward to your feedback! Kind regards, Vesna Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 2

change stop date?
by gboonie 11 Apr '16

11 Apr '16

Hi, In the past, when you scheduled a measurement for some weeks, you could change the end date. This does not seem possible any more. Is that intentional? Could that be changed please? Also, can't we change measurements to private anymore? The field is there to show that it is public, but changing does not seem possible anymore. Thanks, Dave

1 0

Local network checks
by Alison Wheeler 11 Apr '16

11 Apr '16

Recently my probe stopped responding to RIPE even though it was pingable through the local network. Putting aside what the cause might have been* is there any way to 're-awaken' or cycle in some way a probe without physical access to it? (* sfaict it didn't restart when the USB socket on the server it takes power from was remotely restarted) Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 9

Failing 4GB USB on v3 probes?
by Phillip Remaker 11 Apr '16

11 Apr '16

So far, I have had two of the SanDisk Cruzer 4GB drives (SDCZ33) fail, and I think I have two other ML-3020 (v3) devices with the same fate. Case #1, the drive fell into read only one. Case #2, the drive identifies to the USB, but read of block 0 (capacity) fails. The first time I called SanDisk and jumped through their hundred hoops to replace it.They were reluctant since I couldn't produce a receipt. This time, I just grabbed an old 8GB USB and dropped it in. Looks like it only uses 3GB. Does Atlas plan to pursue warranty claim, or is this an acceptable failure level for the probes?

2 1

Flow-id of built-in traceroute measurement
by Wenqin SHAO 08 Apr '16

08 Apr '16

Dear list, I have some questions concerning the flow-id of built-in traceroute measurements and are seeking for your help. As many of you may have already noticed, the flow-id of the built-in traceroute measurement periodically varies form 0 to 15, in a circular manner. With this behaviour, it is supposed to reveal the diversity of underlying IP paths. In the case that there are more than 16 unique IP paths between a source and destination pair, could this scheme reveal all of these IP paths? If it can, which leads to more than one IP paths per flow-id? Is it normal, from a load balancer point of view? If it can not, then why not a wider range of flow-id (more nuances in header hash results), say [0, 63]? Is it related to common realisation of load balancer? Many thanks in advance. Best regards, Wenqin ==== Wenqin SHAO PhD Candidate Telecom ParisTech

2 2

Scheduling a test for all probes?
by Jared Mauch 06 Apr '16

06 Apr '16

Is there a way to schedule a one-off test on all the probes to be run “at a leisurely pace”, eg: looking up a specific DNS QNAME? (I’ll call it a lazy query/scheduling). - Jared

3 2

Research using RIPE Atlas probes: How Pingable are the Pingables?
by Vesna Manojlovic 05 Apr '16

05 Apr '16

Dear colleagues, take a look at how the "pingable:" and "ping-hdl:" attributes have been adopted in the last five years and how reachable the pingable addresses registered in the RIPE Database are when pinged from RIPE Atlas. Spoiler alert: It could be better. Please find the details on RIPE Labs: https://labs.ripe.net/Members/wilhelm/how-pingable-are-the-pingables Kind regards, Vesna

1 0

Credits sharing and other new features
by Vesna Manojlovic 04 Apr '16

04 Apr '16

Dear colleagues, many of you have been asking for the credits sharing options, and now we have added two new ways that you can go about it: - standing orders - share access - and the transfers are still possible too All about credits: https://atlas.ripe.net/docs/credits/ In addition to that, in the past few months, we've added some other new features and functionality to RIPE Atlas, including making the DNSMON code available on GitHub for personal use, displaying IPv4 vs IPv6 comparisons in LatencyMON, and new limits on probes per measurement and results per day. Learn more about the latest updates on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-altas-update-dnsmo… Regards, Vesna

2 1

Re: [atlas] [ripe.net #1204062] request to add three more ccTLDs to, DNSMON: CR, SG, and TW
by Romeo Zwart 04 Apr '16

04 Apr '16

Hi Peter, You have recently requested to have three ccTLD zones be added to DNSMON. Unfortunately, since the zones do not fall into the RIPE service region and the zone owners are not members of the RIPE NCC, the request does not qualify according to ripe-661. If the zone owners do wish their zones to be monitored by DNSMON we need to ask them to become members of the RIPE NCC. Alternatively they could argument an exception for their case with the DNS working group. Apologies for the confusion. Feel free to contact us if you have further questions. Kind regards, Romeo -------- Forwarded Message -------- Subject: Re: [ripe.net #1204062] request to add three more ccTLDs to DNSMON: CR, SG, and TW Date: Mon, 04 Apr 2016 10:39:21 +0200 From: pk(a)denic.de <atlas(a)ripe.net> Reply-To: atlas(a)ripe.net CC: becha(a)ripe.net, mgalante(a)ripe.net Hi Alastair, On Thu, Mar 31, 2016 at 11:40:48AM +0200, Alastair Strachan wrote: > Could you please provide me with the points of contact who gave you their consent for an independent verification? sure, we'll dig it out of our ticketing system. Regards, Peter

1 0

probe tagged as "system: Firewall problem suspected"
by sarah.wassermann＠student.ulg.ac.be 02 Apr '16

02 Apr '16

Hi, I have (once again) problems with my probe (probeID: 24102). This time, it got tagged as "system: Firewall problem suspected". The strange thing is that I did not touch anything on my router when this happened and did not change any other configuration... This probe is located in Luxembourg. I now brought it to Belgium and plugged it into the router I have here. Nothing changed. Furthermore, here in Belgium, its 3rd light is slowly blinking, which let's suppose that it gets tuck in the network-testing phase. Anybody knows how to fix this? (I already had some problems with that probe ("system: Hardware problem suspected") but I could solve them thanks to a hint given by a user.) My worst problem is that, due to this issue, we have difficulties earning enough credits for our research... So I would be really happy if this problem could be solved easily :( Thanks! Sarah

4 8

Implementing structured error reports ("Problem Details for HTTP APIs")?
by Stephane Bortzmeyer 01 Apr '16

01 Apr '16

Hello, IETF approved the future RFC draft-ietf-appsawg-http-problem "Problem Details for HTTP APIs" which standardize structured error reports (in JSON) to add machine-readable information to HTTP error codes. Would it be a good idea to convert current Atlas reports ({"error":{"status":400,"code":104,"detail":"__all__: Your selected prefix is not covered by our network.","title":"Bad Request"}}) to the new and standard format?

3 4