- ripe-atlas - mailman.ripe.net

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

[dagstuhl seminar]: global measurements: practice and experience
by Bajpai, Vaibhav 12 May '16

12 May '16

Dear RIPE Atlas / MAT WG -- sorry for cross-posting. A SIGCOMM CCR article summarising the Dagstuhl seminar on ‘Global Measurements: Practice and Experience’ just came online [a]. Thought to share it with you: [a] http://www.sigcomm.org/sites/default/files/ccr/papers/2016/April/0000000-00… Background: ===================== We recently helped organise a Dagstuhl seminar on Global Measurements: Practice and Experience [b] from January 04 – 07, 2016. This was a followup of the seminar on Global Measurement Framework [c] which focused on the development of global Internet measurement platforms and associated metrics. [b] http://www.dagstuhl.de/16012 [c] http://www.dagstuhl.de/13472 The second seminar aimed at discussing the practical experience gained with building global measurement platforms. It brought together people who are actively involved in the design and maintenance of global measurement systems, who do research on the data delivered by global measurement systems, and who use data derived from global measurement systems in order to manage networks or services or as input for regulatory decisions. ===================== Best, Vaibhav =================================== Vaibhav Bajpai www.vaibhavbajpai.com Room 91, Research I School of Engineering and Sciences Jacobs University Bremen, Germany ===================================

1 0

Number of probes
by Marc Sanchez 11 May '16

11 May '16

I'm new in RIPE and I don't know it enough deeper. I need to check the state of several networks and I'm wondering how many probes should I need to measure a ping between two ASN. Could be enough using just one probe for each measurement? Sorry for the inconvenience. Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

probe congestion?
by Paul Vlaar 11 May '16

11 May '16

Hi all, while running a DNS UDM on a fixed set of (reused from a previous UDM) probes, I noticed the following. When I start 6 UDMs against the same set using the web UI, as a one-off measurement, starting "now", the RTTs for all of the measurements shoots up on all of the probes (500-1000+ ms). When I start the 6 tests individually, the RTTs are much lower, and close to what I'd expect them to be. It appears to me that when multiple UDMs are scheduled on the same probe, these should be run in serial, not parallel, in order to not run into congestion issues. Or am I simply expecting the wrong behaviour, and should I not schedule one-off measurements in parallel in the first place? ~paul

4 6

SixXS issues
by Alison Wheeler 11 May '16

11 May '16

I received my second probe* yesterday (different ASNs) and it is connects via SixXS for IPv6 as the ISP isn't supplying native v6 (despite repeatedly asking when they will catch up on something around for twenty years!). It booted fine and the appear no issues with the IPv4 connectivity but the v6 is going up and down every few minutes (for around the same period.) Not finding anything relevant after searching the forum (nor on google) I'm trying to discover why this might be. My other machines are not experiencing any difficulty with v6 connectivity and the probe is connected to the same 16-port switch as everything else. Suggestions of what to investigate next very welcome! * https://atlas.ripe.net/probes/28800/ Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

3 4

New on RIPE Labs: Using RIPE Atlas to Debug Network Connectivity Problems
by Mirjam Kuehne 10 May '16

10 May '16

Dear colleagues, Please find this new article by Stéphane Bortzmeyer on RIPE Labs where he explains how he used RIPE Atlas probes, the official RIP Atlas API and custom scripts, to debug network issues: https://labs.ripe.net/Members/stephane_bortzmeyer/using-ripe-atlas-to-debug… Kind regards, Mirjam Kuehne RIPE NCC

1 0

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