- ripe-atlas - mailman.ripe.net

Re: [atlas] Probe is down but does send DNS according tot SOS history
by gboonie 21 May '16

21 May '16

No. Everything seemed normal except that it was down. All tags like "IPv4 works" etc. were there. The only thing was that the status was down. So I pulled the power, pulled USB, replaced the power. Went to brush my teeth and came back to replace USB and went to bed around 23:30 (21:30UTC) A few hours (!) later the probe came back to live. The power for the probe comes from the modem. That might be a possible cause, I'm thinking. Could the developers please see if the probe can indicate power shortage? Could it get some recovering mechanism built in? Op 21-5-2016 om 01:14 schreef Phillip Remaker: > Does it have the "Hardware Problem Suspected" tag? It may have a > failing USB sick and can only get up far enough to send SOS messages. > > On Fri, May 20, 2016 at 1:13 PM, gboonie <gboonie(a)gmail.com > <mailto:gboonie@gmail.com>> wrote: > > Hi, > > How can it be that the status of a probe is down while I see > current DNS requests in the SOS list without any remarks in the > 'info' column? Even the power-up time is increasing. > > If the probe can send DNS requests, why does it not have some > mechanism to recover? Seem not too hard to make it reboot if it's > status is down. > > Thanks, > Dave > > > > >

1 0

Re: [atlas] USB drive more harmful than helpful?
by Joe Provo 20 May '16

20 May '16

Fwiw, I always power directly from an outlet, never tributary on the USB. I've yet to have such fails, so my anecdata aligns with the underpower theory. On May 20, 2016 15:08, "Phillip Remaker" <remaker(a)gmail.com> wrote: So I have a few theories. I have now had 3 different USB sticks fail on me: Two Sandisk 4GB SDCZ33 and one cheap generic 8GB replacement. The power draw of the TP-Link system + USB is probably more than the opportunistic USB ports they get plugged in to. An underpowered probe runs great MOST of the time, but a flash bit write is probably the highest power strain and Flash can get really unhappy with power interrupts, based on this SSD research: https://www.usenix.org/system/files/conference/fast13/fast13-final80.pdf I usually use a 500mA or 800mA supply, or tap a nearby router USB port in that range. I suspect the system may demand 1200mA or more. When most flash sticks get errored out enough, they permanently fail into a read only mode, or become fully unreadable. Read-only mode can be reset on some models, but it is not recommended by the vendor. At least one of the failed SANdisk units I had was stuck in a read-only mode. Also, probes may be subjected to ungraceful power down situations, depending on where they are stationed. That can also be a flash drive killer. I don't think we are hitting the write limits of the sticks. I suspect the units are often in underpowered or ungraceful pwoer-down situations, or the USB flash itself is not responding gracefully to poweroff situations. I don't suppose RIPE buys enough USB sticks to get to talk to engineers at SanDISK? I know the newer Raspberry Pi will report when it is in an underpowered situation. Can the TP-Link detect and warn when underpowered? What is the minimum power recommended for TP-Link + USB? Also, are there any USB sticks that have lower power needs and are more robust in low power IoT situations? Is anyone trying to post-mortem the failed sticks? On Fri, May 20, 2016 at 10:03 AM, Gert Doering <gert(a)space.net> wrote: > Hi, > > On Fri, May 20, 2016 at 04:10:47PM +0200, Philip Homburg wrote: > > We have no clear idea why they fail. It seems that time to failure is > > highly variable. > > Can you correlate tests-until-failure or data-written-until-failure? > > One of mine has failed at least two times now, and it could be that > people just *love* to run tests from 3320... > > My gen 1 probe in 5539 has never had *any* issues. > > gert > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 >

1 0

Probe is down but does send DNS according tot SOS history
by gboonie 20 May '16

20 May '16

Hi, How can it be that the status of a probe is down while I see current DNS requests in the SOS list without any remarks in the 'info' column? Even the power-up time is increasing. If the probe can send DNS requests, why does it not have some mechanism to recover? Seem not too hard to make it reboot if it's status is down. Thanks, Dave

1 0

New on RIPE Labs: There Is Gold in This Stream - Sifting Through Used RIPE Atlas Traceroute Results
by Mirjam Kühne 20 May '16

20 May '16

Dear colleagues, Please find a new article on RIPE Labs demonstrating the value of the results collected by RIPE Atlas independent of the original purpose for collecting them. Using all traceroute results from a particular day as an example, we first show that near real-time analysis of the result stream is feasible. Then we show that this has great potential for studying the packet layer of the Internet in general and for providing tools to network operators in particular. All this suggests a large and diverse potential for further work. https://labs.ripe.net/Members/dfk/there-is-gold-in-this-stream?pk_campaign=… Kind regards, Mirjam Kuehne RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

Replacing flash key
by Marat Khalili 20 May '16

20 May '16

My V3 probe (26656) disconnected yesterday, simple reboots didn't help. Suspecting problem with USB key I first tried to replace it with a new one. I took bog standard Transcend JetFlash 350 8Gb right out of the wrapping and inserted it into a started probe 10 minutes after boot. Did not format the flash key or alter it in any way, because someone previously said that it is not necessary. Unfortunately, probe did not come up, and the flash key seems unchanged after approximately 1 hour wait. What should I do to switch to a new flash key? Also, did someone tried connecting HDDs/SSDs, shouldn't they work better? (Probe did appear after I inserted previously used flash key into it, but I suspect problem will re-occur in the future, so I'd like to know a way to fix it more permanently.) -- With Best Regards, Marat Khalili

4 9

evaluating ripe atlas
by Rafal.Jankowski＠thomsonreuters.com 19 May '16

19 May '16

Dear Ripe Atlas Users, I would like to evaluate ripe atlas features. Is there any quick and simple way to earn credits? From what I can see becoming sponsorship begins from 1000 EUR which is above my budget for evaluating the tool. Hosting probe is not something feasible for me at the moment. Is there any option to buy credits for something like 100 EUR? Also I wanted to see webinar recording https://www.youtube.com/watch?v=oJMFGuM0kMo linked on https://atlas.ripe.net/resources/training-and-materials/ but it seems to be unavailable. Regards, Rafał ________________________________ This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website.<http://site.thomsonreuters.com/site/disclosures/>

6 5

probe coverage map?
by Bajpai, Vaibhav 18 May '16

18 May '16

Hello, What happened to the probe coverage map that showed number of probes at different level of details depending on the zoomed-in state of the map? — I have an earlier screenshot [a] (2015) to explain what I mean. It was a very nice plot. [a] http://i.imgur.com/d0tI1qP.png I was looking for a probe coverage map to put in one of my slides. I ended up using [b], but I miss [a]. [b] https://www-static.ripe.net/static/rnd-ui/atlas/static/page/img/allprobes.p… Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================

4 5

New on RIPE Labs: Pinpointing Delay and Forwarding Anomalies using RIPE Atlas Built-in Measurements
by Mirjam Kuehne 18 May '16

18 May '16

Dear colleagues, Detecting network disruptions is a recurring problem. Clearly locating performance degradation is an important step in debugging and subsequently fixing connectivity issues. In this new RIPE Labs article the authors propose a set of complementary methods to detect network disruptions from traceroute measurements created by RIPE Atlas Built-In Measurements: https://labs.ripe.net/Members/romain_fontugne/pinpointing-delay-and-forward… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Adding additional probes to existing measurement or exchange them
by Annika Wickert 18 May '16

18 May '16

Hi everybody, I just stumbled across this problem, that I want to exchange probes on a actual running measurement because some of the probes I defined 2weeks ago went offline. And I want other probes to take over their job. Is that possible in any way? Cheers, Annika Wickert

2 2

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