- ripe-atlas - mailman.ripe.net

Result delivery issues - 2021-05-11
by Robert Kisteleki 11 May '21

11 May '21

Dear All, The RIPE Atlas result storage backend started experiencing issues today at around 3am (CEST). The team is working on resolving the issue; we'll provide an update when more information is available. The result streaming feature is not affected, it is still delivering results in real-time. Regards, Robert Kisteleki

2 2

Scheduler adding extra probes for some measurements
by Chris Amin 07 May '21

07 May '21

Dear colleagues, We have fixed a bug in the RIPE Atlas scheduler which caused extra probes to be added to some ongoing measurements. This bug affected many users who submitted "removal" requests using the REST API from 2021-03-23, and in some cases caused a large increase in the consumption of credits due to the extra generated measurement results. This bug has now been fixed, and the affected accounts have been credited with approximately 125% of the erroneous overpayment. My apologies for any inconvenience caused. Please let me know if you have any further questions or issues. Kind regards, Chris Amin RIPE NCC

1 0

Rapidly decreasing credits
by ms 07 May '21

07 May '21

Hi, Recently, looks like since beginning of April, my credits started dropping exponentially. I'm only running a ping measurement at the moment. Any changes to the credit system I missed? Cheers, ms

2 1

research support: credits/limits for DSCP marking measurements
by Stephen Strowes 07 May '21

07 May '21

Hi, One more RIPE Atlas research support request: this time on DSCP marking/bleaching from as many vantage points as possible. This one feeds into the IETF tsvwg, and is pretty applicable to operators in the RIPE community also. In short: they have one target host, and they want to test 3 DSCP codepoints with traceroutes from as many probes as possible. This is not an ongoing study. They'll run a pretty typical traceroute config from as many probes as possible once for each DSCP they're interested in, and they'd like to do it as rapidly as possible. This is simplest as three one-off measurements. Could you: - bump their credit allowance if necessary - bump the number of probes allowed per measurement to some high number; as close to "all probes" as possible? The account they're using is ana(a)erg.abdn.ac.uk <mailto:ana@erg.abdn.ac.uk> Cheers, S. -------- Forwarded Message -------- Subject: Re: Can you help perform a large-scale ATLAS measurement campaign? Date: Tue, 4 May 2021 19:48:40 +0100 From: ana(a)netstat.org.uk To: Stephen Strowes <sds(a)ripe.net> Hi Stephen, > Would you like to run (e.g.) thousands of probes to the target with > all DSCP values as rapidly as possible, or would you run multiple > measurements with 1,000 probes each over a longer period? > Thousands of probes as rapidly as possible, but each DSCP is a separate measurement (so 3 separate measurements). I don’t expect to repeat them over a longer period. > > Either way, the credit cost will likely be the same, but the Atlas > folks may need to modify other limits to accommodate the measurements. > Your current account settings should be visible at > https://atlas.ripe.net/atlas/user/ > The only limit that worries me there is: Maximum number of probes per measurement:1,000 It doesn’t look like these measurements will hit the other limits. > Also: Is this email address the one to add credits to? > The account uses email address ana(a)erg.abdn.ac.uk <mailto:ana@erg.abdn.ac.uk>, rather than this one. Thanks again! Ana

3 3

Error for getting measurement results from an api
by Sanaa GHANDI 30 Apr '21

30 Apr '21

Hello, I would like to use the Ripe api : /api/v2/measurements/{msm_id}/participation-requests/{source_id}/. for getting measurement results, but I keep getting the following error (in the picture). Here is the website of the different apis: https://atlas.ripe.net/docs/api/v2/reference/#!/measurements/Type_0_1_2_3_4… Is it due to my key? Knowing that I have already used it to create measurements and get measurement results and in other apis from Ripe. Concerning the example below, I have checked the measurement ID and that the probe in the source ID figures among the participant probes. I don't quiet see the source of the problem, do you have any ideas about this? Thank you, Cheers, Sanaa

1 0

Satellite based "last mile" and Atlas probes
by Eric Kuhnke 27 Apr '21

27 Apr '21

Hello all, I am running what I believe to be the only probe on a Starlink satellite connection right now: https://atlas.ripe.net/probes/1001821/ Is anyone aware of a list of probe ID numbers which are definitively known to be on some form of satellite-based access technology? I am thinking of, for instance, sites on consumer grade geostationary VSATs, more serious VSATs, or in island nations which are not known to have any submarine cables. The reason why I am searching for such a list is that I intend to consume some of my accumulated credits to run periodic one-off measurements of latency, traceroutes and other things to quantify improvements in satellite based latency and other performance metrics over time. And to quantify what it looks like when an ISP previously dependent on geostationary (min 495ms latency) gains access to either terrestrial/submarine fiber, or a lower latency low earth orbit based service. The best information I can find right now is to manually pick probes which never show below geostationary latency to a first hop in any traceroute, and are located on the probes map in certain island locations. It's a bit more time consuming to manually search for probes in continental locations which are on a VSAT (for instance if anyone knows of a probe on a VSAT terminal in a remote part of Wyoming, USA, let me know...).

14 37

RIPE Atlas CLI tools docker image
by Anurag Bhatia 26 Apr '21

26 Apr '21

Hello everyone, A little while ago I put RIPE Atlas CLI tools docker image based on alpine. - https://hub.docker.com/r/anuragbhatia/ripe-atlas-tools It stores the API keys at ~/.config on the host (and that is mounted inside the container). Dockerfile can be found here <https://github.com/anuragbhatia/ripe-atlas-tools/blob/master/Dockerfile> and one can use it to build image locally if intended to. *Example usage: * docker run --rm -v ~/.config:/root/.config -it anuragbhatia/ripe-atlas-tools ripe-atlas measure traceroute --from-country IN --target he.net One can set an alias in the local shell to make it appear almost like a locally installed setup. E.g on fish: anurag@Anurags-MacBook-Pro ~> alias ripe-atlas='docker run --rm -v ~/.config:/root/.config -it anuragbhatia/ripe-atlas-tools ripe-atlas' anurag@Anurags-MacBook-Pro ~> funcsave ripe-atlas anurag@Anurags-MacBook-Pro ~> Thus the reduces syntax is alias becomes: ripe-atlas measure traceroute --from-country IN --target he.net Please do share if anyone has any feedback. -- Anurag Bhatia anuragbhatia.com

1 0

Filtering measurements
by Sanaa GHANDI 23 Apr '21

23 Apr '21

Hello, I hope you are all doing well. I have a few questions concerning the measurements selection, and I am interested only on the anchoring mesh measurements. In fact, for optimisation issues, I would like to be able to select only measurements of interest: For example, I want to get the results coming from sources: X and Y, and targeting the anchor 6771. Now I can get the measures targeting the anchor 6771 using this code from Altas Cousteau ################################################################## from ripe.atlas.cousteau import MeasurementRequest filters = {'tags': ['anchoring','mesh',6771] } measurements = MeasurementRequest(**filters) #################################################################### But I have no idea of how to make a filter on the sources as well, since all we can access through the measurements are the number of anchors requested and not their ids. Do you know a way to get access to the sources of a measurement via Atlas Cousteau or another Ripe Tool ? Thank you -- Sanaa

4 4

Custom box and bag
by Slite 22 Apr '21

22 Apr '21

Hello, Have a nice day. Does your company needs any Custom packaging box/bags for your products? We are Chinese supplier who can produce customized packaging/bag with custom logo. Dear,we have cartons,cardboard box,plastic box,metal tin box,paper bag,plastic bag,non-woven bag ... to pack your products. Then tell me which one you want,I will give you best price with good service. Any of your reply will be appreciated. Looking forward to your reply. Best regards, Slite Contact Email: slite(a)slcpackage.com What's app: 0086 15314679598SLC-PACKAGE CO. LTDwww.slcpackage.com www.slcpackages.comContact Person: Slite Cao Address:1406, No 11,Dongyue Huayuan,Nancheng,Xinluo,Longyan,Fujian,China If you no longer wish to receive mail from us, you can <http://tracking.littleindustrial.info/tracking/unsubscribe?d=hV-G-DkT38mtq2…> Unsubscribe

1 0

Request for credits for research
by Mohan, Nitinder 20 Apr '21

20 Apr '21

Dear RIPE community, I hope you are all safe and sound. I am a Postdoctoral fellow at the Technical University of Munich, Germany. We are currently working on an ongoing research project which aims to analyze the availability and reachability of cloud data centers globally. The first work of our work will appear in ACM HotNets 2020 titled "Pruning Edge Research with Latency Shears" (http://conferences.sigcomm.org/hotnets/2020/program.html) We are currently preparing the camera-ready version of the paper and will share it with the community by hosting it (and the associated dataset) publicly soon. We are currently planing to submit the second leg of our work to a conference with submission deadline a month. In order to complete all set of measurements for required analysis, we are scheduling very large-scale measurements over the platform which has burned through almost all our credits and left us in need. I have always found the RIPE Atlas community to be helpful and generous towards research and I am hoping that you could support our research by donating us some of your spare credits. Your help will be highly appreciated. My RIPE account is nitinder.mohan(a)helsinki.fi Thanks and Regards Nitinder Mohan Postdoctoral Fellow Technical University of Munich, Germany <http://www.cs.helsinki.fi/u/nmohan/>https://www.nitindermohan.com/

15 18

Feature request for Validated Timestamps
by Will 15 Apr '21

15 Apr '21

I was starting to work on a mapping measurement project where I wanted to delegate measurements to remote machines. There are a number of schemes that have been used where a not fully trusted node can come away from a measurement with a record that can be used to verify that it actually made the measurement. Many of these make use of a time stamp signed by the "server" as a way to prevent replaying old measurements. Things that have been done with this feature also include tlsnotary[1], which works with web servers where the "server random" bytes of the tls handshake includes the server timestamp (the default for openssl). The implementation of ssl currently used by probes does not appear to include the timestamp in the server hello. Another approach would be to add a "roughtime" service on probes Interested to hear if there would be willingness to have probe software support something in this direction. [1] https://tlsnotary.org/ --Will

5 9

Spurious "would violate your maximum daily spending limit"
by Stephane Bortzmeyer 07 Apr '21

07 Apr '21

I receive a: {"error":{"detail":"There was a problem with your request","status":400,"title":"Bad Request","code":102,"errors":[{"source":{"pointer":""},"detail":"Executing this measurement request would violate your maximum daily spending limit of 1000000.0 credits. Please stop some of your currently running measurements and try again."} from the API. The request is: {'is_oneoff': True, 'definitions': [{'description': 'DNS resolution of use-application-dns.net./A from AS #3215', 'af': 4, 'type': 'dns', 'query_argument': 'use-application-dns.net.', 'query_class': 'IN', 'query_type': 'A', 'set_rd_bit': True, 'protocol': 'UDP', 'use_probe_resolver': True}], 'probes': [{'requested': 100, 'type': 'asn', 'value': '3215', 'tags': {'include': ['system-ipv4-works', 'system-resolves-a-correctly', 'system-resolves Which is very small. I run this sort of requests frequently. My daily expenditure is small (13,680 credits). Why is it rejected?

3 5

What to do with broken v1 probe?
by Lorenzo Colitti 30 Mar '21

30 Mar '21

Fellow atlas users, After more than 10 years (!) of 99% uptime (see below), my probe v1 appears to have given up the ghost. When connected to power, the lights still come on, but after a few seconds link bounces, and it never sends any packets. Any idea what to do? Should I just apply for a new probe? Are new probes being given out these days? Cheers, Lorenzo ---------- Forwarded message --------- From: RIPE Atlas <no-reply(a)ripe.net> Date: Tue, Nov 24, 2020 at 9:59 PM Subject: Congratulations! Your RIPE Atlas probe 333 is 10 years old! To: Lorenzo Colitti <lorenzo(a)colitti.com> Dear Lorenzo Colitti, It's your probe's birthday today !! To celebrate that fact, we are giving you 9869024 credits to use for scheduling your own measurements. In the last 10 years your probe was connected for 99% of the time. Happy measuring and thank you on behalf of everyone at the RIPE NCC and the other RIPE Atlas users. The RIPE Atlas Team

7 6

Re: [atlas] Probe location obfuscation
by Ponikierski, Grzegorz 26 Mar '21

26 Mar '21

I would add to it additional problem that some hosts obfuscate probe location even more. For example you can find probes which in reality are located in US but are marked as CN or probes which are in reality in Wisconsin but are marked in California. Of course these are extreme cases. I guess most hosts just put a pin with probe location just somewhere around where it's locate as long it's in the same city. I don't remember, as a host of 3 probes, to get any precise recommendations how to mark probe location. Personally I just put a pin in city district where probe is locate. Regards, Grzegorz From: "Mccherry, Paul (Student)" <p.mccherry(a)lancaster.ac.uk> Date: Thursday 2021-03-25 at 11:20 To: "ripe-atlas(a)ripe.net" <ripe-atlas(a)ripe.net> Subject: [atlas] Probe location obfuscation Can anyone confirm the geo-location obfuscation of probes as being up to 1km as per https://atlas.ripe.net/about/faq/#are-the-locations-of-probes-made-public<https://urldefense.com/v3/__https:/atlas.ripe.net/about/faq/*are-the-locati…> I am a Phd student carrying out research on the RIPE atlas platform and an early result seems to indicate 1 probe has an obfuscation of 10km distance but this may be an anomaly or perhaps something not taken into account as yet.

10 13

Unused Probes (was: What to do with broken v1 probe?)
by Sylvain Baya 25 Mar '21

25 Mar '21

{change the subject [0]} Dear all, Hope you are doing well! Le lun. 22 mars 2021 10:35, Estelmann, Christian <c.estelmann(a)gmx.net> a écrit : > Is there a possibility to return no longer used probes? Hi Christian, Thanks for your email brother. ...imho, it's a very useful idea! Within one [1] of our NOG's activities we have included the recovery of unused probes ; but maybe we should have tried it the other side...by asking probe's hosters to send it to an other volunteer or to us, if they become unable to keep it online... __ [1]: FR <https://www.cmnog.cm/dokuwiki/IdeasAndProjects:Projects:AtlasCM> I have one which was homed at a now closed location. Someone else could > give it a new home. > ...i suggest that you write to your ccNOG's mailinglist to find the nearest volunteer who could want to host your protected probe ;-) ...hope this could help. Blessed thursday! __ [0]: <https://lists.ripe.net/pipermail/ripe-atlas/2021-March/004638.html> Shalom --sb. > Greeting, > Christian > > Am 21. März 2021 17:14:57 MEZ schrieb Chriztoffer Hansen <ch(a)ntrv.dk>: > >On Sun, 21 Mar 2021 at 08:18, Lorenzo Colitti via ripe-atlas wrote: > >> After more than 10 years (!) of 99% uptime (see below), my probe v1 > >appears to have given up the ghost. [...] > >Cheers, > >Chriztoffer > > -- -- Best Regards ! __ baya.sylvain[AT cmNOG DOT cm]|<www.cmnog.cm/dokuwiki> Subscribe to Mailing List: <lists.cmnog.cm/mailman/listinfo/cmnog/> __ #‎LASAINTEBIBLE‬|#‎Romains15‬:33«Que LE ‪#‎DIEU‬ de ‪#‎Paix‬ soit avec vous tous! ‪#‎Amen‬!» ‪#‎MaPrière‬ est que tu naisses de nouveau. #Chrétiennement‬ «Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!»(#Psaumes42:2)

1 0

Probe location obfuscation
by Mccherry, Paul (Student) 25 Mar '21

25 Mar '21

Can anyone confirm the geo-location obfuscation of probes as being up to 1km as per https://atlas.ripe.net/about/faq/#are-the-locations-of-probes-made-public I am a Phd student carrying out research on the RIPE atlas platform and an early result seems to indicate 1 probe has an obfuscation of 10km distance but this may be an anomaly or perhaps something not taken into account as yet.

1 0

Probe #1000165 showed as down in tab#status
by Jacques Lavignotte 02 Mar '21

02 Mar '21

Dear RIPE NCC crew, Some diag below : # systemctl status atlas mars 02 11:12:43 melusine.eu.org ATLAS[32011]: Do a controller INIT mars 02 11:12:43 melusine.eu.org ATLAS[32011]: Controller init -p 443 atlas(a)ctr-fsn01.atlas.ripe.net INIT mars 02 11:12:43 melusine.eu.org ATLAS[32011]: 255 controller INIT exit with error Probe seems down since scheduled machine reboot this night. Help for fixing welcome, Merci, Jacques -- GnuPg : 156520BBC8F5B1E3 Because privacy matters. « Quand est-ce qu'on mange ? » AD (c) (tm)

5 6

Join the RIPE NCC Open House: Internet in Turkey: 24 February 2021, 11:00 UTC
by Vesna Manojlovic 26 Feb '21

26 Feb '21

Dar all, You're invited for an open discussion with the RIPE NCC about the Internet in Turkey! We are hosting a RIPE NCC Open House for our members and other Internet stakeholders in Turkey on Wednesday, 24 February at 11:00 - 12:30 UTC and invite you to join the discussion. The RIPE NCC Open House is a ninety minute remote session where RIPE NCC staff, community members and industry experts can meet up and share insights, feedback and support. https://www.ripe.net/participate/meetings/open-house This session is focusing on the Turkish Internet community. We will be discussing various topics including: * The state of the Internet in Turkey and across our service region * How RIPE NCC tools and measurements can help operators (RIPE Atlas, RIPEstat, RIPEIPmap, etc.) * Improvements that the RIPE NCC can make to help operators in Turkey * IPv6 deployment * Local community development and the support available from the RIPE NCC Want to join in? Register for the RIPE NCC Open House https://meeting-registration.ripe.net/meeting-pub/registration?0&meetingId=… Looking forward to seeing you online! Regards, Vesna Manojlovic Community Builder RIPE NCC

2 3

New on RIPE Labs: RIPE Atlas Big Data is Back
by Alun Davies 23 Feb '21

23 Feb '21

Dear colleagues, At the beginning of the year, RIPE Atlas users started encountering delays in data retrieval and an overall drop in the responsiveness of the system. With service having gone back to normal earlier this month, we take a look at what caused the problem and what we're doing prevent it from happening again: https://labs.ripe.net/Members/paul_de_weerd/ripe-atlas-big-data-is-back Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Re: [atlas] [mat-wg] RIPE Atlas testing of reserved IPv4 addresses
by Robert Kisteleki 18 Feb '21

18 Feb '21

Dear All, A little bit of poking since there were no reactions to this question on the MAT mailing list. Before embarking on evaluating what it takes for RIPE Atlas to contribute to this, I'd like to ask for some input from the community; is this something we should spend energy on? More specifically, would it be worthwhile for us to spend time on evaluating the cost of / implementing such measurements in RIPE Atlas? Regards, Robert Kisteleki On 2021-01-26 08:28, Seth David Schoen wrote: > Hi mat-wg, > > I'm Seth, formerly a staff technologist at EFF and one of the > co-developers of Let's Encrypt and Certbot. > > Recently, I've been working with John Gilmore on the IPv4 Unicast > Extensions Project, which aims to make some of the IPv4 address blocks > that were reserved in the 1980s and 1990s (and that continue to be unused, > or nearly so) available for addressing and routing on the Internet. > > This project involves many different kinds of work, including writing > software patches to make various OSes and devices willing to generate > and accept packets to reserved addresses, writing Internet-Drafts to > describe addressing policy changes with IETF, testing devices to see how > they actually treat such packets, talking to various constituencies > about these proposals, and working with the Internet measurement > community to understand how the Internet as a whole treats packets to or > from currently-reserved address ranges, and how that treatment evolves > over time. > > Two prominent examples that are already supported by Linux hosts are the > netblocks 0/8 ("this network") and 240/4 ("experimental"/"future use"). > According to Internet standards created in the 1980s and still in > effect, these address ranges cannot be allocated and should not be > assigned to hosts or used on the public Internet. However, several key > implementations started allowing 240/4 addresses about 11 years ago > during an earlier IETF attempt to open up that netblock, including > Linux, Android, macOS, iOS, and Solaris. In 2019, Linux kernel version > 5.3 allowed ordinary unicast use of 0/8. Today, there are rumors that > various organizations are currently using such reserved addresses as > unofficial RFC 1918-like private address space, without formal policy > coordination with anyone. (There is even some public documentation from > Google suggesting making private use of 240/4.) > > I participated in the Atlas probe deployathon in November and > successfully got a probe up and running. I have also been talking to > a few RIPE people about our interests and managed to confirm that > (regardless of their underlying OS or network treatment) the Atlas > software probes will reject probing any reserved address space, while > the backend infrastructure will refuse to ask probes to connect to it. > > So, I'm here to introduce our project and ask the community's view about > removing these restrictions so that such addresses can actually be > probed and measured. We understand and hope that the majority of such > tests would currently result in errors. Even the errors themselves > could be interesting: for example, we would like to know how often > routing to reserved address ranges fails on a probe host, versus on the > probe host's first-hop router, versus inside of ISP infrastructure. We > would also like to see how this changes over time as a result of OS > software changes that roll out into the field. We would also like to > see whether we can detect unofficial use of particular reserved address > ranges as private address space. Our medium-term goal is to advertise > global routes to portions of these reserved address spaces, and use the > probes to assess how well those routes propagate through the Internet, > and find where blockages occur. Clearly, we can't do this until both > the probe firmware, and the central dispatcher, allow tests to these > addresses. Our long-term goal is to have these addresses treated as > ordinary unicast addresses by all nodes, including Atlas probes, so the > Atlas changes to remove the restrictions would be useful permanent > changes. > >

12 16

RIPE Atlas Measurements packets sent number not always 16
by Debora Marettek 17 Feb '21

17 Feb '21

Dear RIPE NCC, for my ping measurements, I incremented the number of sent packets to 16. Now I noticed that in the measurement with the ID 28779821, the probes didn't always send 16 packets, sometimes, albeit rarely, only 7 or 3. Below you see an extract of the packets_sent data of Probe 52673. Now I wanted to ask what could possibly be the reason for that phenomena. Kind regards, Debora Probe: 52673 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 5, 1, 9, 16, 16, 16, 14, 16, 16, 16, 16, 8, 13, 6, 7, 6, 6, 16, 16, 12, 16, 16, 16, 16, 16, 10, 11, 10, 7, 6, 16, 4, 16, 16, 16, 16, 4, 7, 15, 6, 9, 12, 11, 7, 8, 11, 6, 5, 13, 13, 13, 5, 10, 16, 16, 7, 7, 9, 7, 7, 7, 9, 16, 16, 11, 4, 7, 16, 7, 2, 8, 16, 4, 6, 8, 16, 7, 8, 6, 5, 8, 8, 9, 8, 7, 4, 3, 10, 1, 2, 11, 6, 16, 8, 12, 6, 11, 10, 11, 8, 12, 12, 12, 11, 8, 16, 6, 5, 5, 9, 10, 6, 10, 7, 9, 10, 9, 11, 8, 8, 11, 7, 12, 7, 11, 9, 13, 2, 10, 12, 10, 7, 9, 16, 13, 5, 4, 7, 8, 6, 5, 7, 6, 7, 9, 9, 9, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 4, 9, 4, 6, 8, 6, 11, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, 16, <https://atlas.ripe.net/measurements/28931367/>

1 0

Re: [atlas] Updating probe ssh pub keys via API PUT/PATCH requests
by Chriztoffer Hansen 15 Feb '21

15 Feb '21

Hi RIPE Atlas, Was reading through the documentation yesterday... Is there a specific reason why it is NOT possible to update probe (ssh) pub keys via authenticated API PUT/PATCH requests? https://beta-docs.atlas.ripe.net/apis/metadata-reference/ -- Best regards, Chriztoffer Hansen

3 3

Measurement Result Broken
by r.sommese＠utwente.nl 10 Feb '21

10 Feb '21

Hi everyone, I am getting trouble getting results for ping measurements. Looking at the web portal and JSON results, they are both empty. Measurement ID: 29049476 I also checked from the account of a colleague, same story. There is something broken in the pipeline? Best, Raffaele Sommese

5 5

Is there a way to de-register a long dead probe?
by Kyriacos Sakkas 09 Feb '21

09 Feb '21

Hi All, Can't seem to find a way to just mark a long dead probe as such. Thanks, Kyriacos

3 6

atlas probe down : ID 35603
by MAYER Hans 08 Feb '21

08 Feb '21

Dear All, Our Atlas probe with ID 35603 is down since about 6 days. It’s a V3 probe. Model: TL-MR3020(UN) Ver: 1.9 ; S/N: 2176197008302. When I realised it this atlas probe was not ping-able. ( due to a power outage ) I followed the instructions https://labs.ripe.net/Members/philip_homburg/troubleshooting-ripe-atlas-pro… with solution 1. Unfortunately it didn’t work. During the time without USB stick the probe was on the network reachable, getting the IP from DHCP. But later on, it wasn’t ping-able. So I tried solution 2. I took a different USB stick as described. After a while the probe is now ping-able. ( 2001:628:21f0:911:c225:e9ff:fea8:6530 , 147.125.100.34 , DNS name: ripencc.iiasa.ac.at<http://ripencc.iiasa.ac.at> ) But when I go to https://atlas.ripe.net/probes/35603/ I see it is offline. The web page says „no flash drive“ and „trying to connect“. What else can I do ? It seems, that the TP-Link device itself isn’t broken. Shall I try with a different USB stick. (a third one) I took a 64MB USB stick. Was this maybe too big ? I saw the original stick had only 1 MB. The documentation says it should have at least 4GB. Any ideas ? Any feedback is welcome. Kind regards Hans -- Ing. Dipl.-Ing. Hans Mayer Systems Analyst Network Unix Security Team (NUST) Information and Communication Technologies (ICT) International Institute for Applied Systems Analysis (IIASA) Schlossplatz 1 A-2361 Laxenburg, Austria Phone: +43 2236 807 Ext 215 Mobile: +43 676 83 807 215 Web: http://www.iiasa.ac.at E-Mail: hans.mayer(a)iiasa.at<mailto:hans.mayer@iiasa.at> Note: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it.

2 6