Based in Amsterdam, The Netherlands
Articles
Likes on articles
I wrote the articles collected here during my time as community builder of the RIPE NCC and the maintainer and editor of RIPE Labs. I have since taken on a new role serving as the Chair of the RIPE Community. You can reach my new profile via the website link below.
• 8 min read
This article is based on a lightning talk Matthew Luckie of CAIDA presented at the recent NANOG 54 meeting of work done in conjunction with Amogh Dhamdhere and Bradley Huffaker. The article is structured around a number of hypotheses about the state of IPv6 deployment and the IPv6 capability of net…
• 5 min read
One year after we released the interactive graph to show the percentage of ASes announcing IPv6 prefixes, we looked at the progress made since then.
• 1 min read
On Monday, 20 February, we discovered that the application servers belonging to the labs.ripe.net production cluster were compromised over the weekend. We investigated this and found no evidence that any harm was done to the servers.
• 4 min read
2011 was an interesting year for IPv4. But did we see a big run on the remaining IPv4 address space? See some statistics and analysis below.
• 5 min read
The RIPE NCC preforms audits of the Local Internet Registries contact data and resource registration data maintained by the LIR. In 2011 around 400 audits were opened and as of 17 January 2012 270 have been completed. In this article you can find some statistics and results of these audits.
• 3 min read
The RIPE NCC has been assigning 32-bit Autonomous System Numbers for quite some time now. In this article we're showing a number of statistics and some analysis.
• 5 min read
World IPv6 Day took place on 8 June 2011. The RIPE NCC did a number of measurements both before and during World IPv6 Day. We've done an initial analysis of the data and would like to share our first impressions and results with you.
• 2 min read
How do we know which addresses are still unallocated or unassigned? Find below a proposal to include unallocated address space in the statistics files the Regional Internet Registries publish daily.
• 5 min read
This article summarises the first RIPEstat demo session that took place today, 25th January 2011. At the end of the article are the dates of the next demos, and options for providing feedback.
“dear :how to use bgp rpki server?”
Sylow, can you please clarify your question. Is it related to the article above?
“Thanks for the post! Solution 1 solved the problem of my probe.”
Thanks for letting us know, Stefan. I am glad to hear your probe works again.
“How to do this ?”
Hi Lisa, can you please clarify your question. What exactly are you trying to do? Thank you.
“hello, I have found that there is a problem with class of CombinePcapInputFormat about the version on github,maybe the constructor function is wrong.The version 1.1 is right. Now I need to change some code to fit my application.So that I need the right source code.Could you help me? would you put the version 1.1 on github ?Or would you email me the source code of version 1.1?My email adress is yxm1348@163.com. Thanks a lot. Yimi”
Dear Yimi, the author informs me that the version 1.1 is here in source: https://github.com/RIPE-NCC/hadoop-pcap/releases/tag/1.1 and as binary in the repository as described here: https://github.com/RIPE-NCC/hadoop-pcap I hope this helps.
“I'm interested in addressing the issues that have come up on my V1 probe, but it's unclear how to go about doing so.”
Hi Owen, Can you please send this as a ticket to atlas@ripe.net so we can respond in more detail. Please also mention the 12 characters printed under the MAC address of the probe. Thank you.
“Let me suggest one other hypothesis based on experience. There appear to be two types of USB storage failures, ones that can be overcome by the unplug, remove USB stick, plug in, reinsert USB stick procedure and ones in which the USB stick itself get trashed so that it can no longer be formatted, etc. The former issue is just an annoyance, but the annoyance is cumulative: if the probe disconnects once, whomever is hosting it is likely to go to the trouble to get it back up. After several times, the motivation to bring it back up and do it quickly may diminish. The latter issue is more serious, at least for those of us who do not keep an inventory of USB sticks in the appropriate size on hand, because the process is to spend a fair amount of time determining that resetting / reloading the USB stick won't work, finding time to go to the store or order a USB stick and wait for it to arrive, and then set the probe up again. Once sure, twice maybe, but, after running through three or four USB sticks, I'd guess that the odds of a probe being reconnected go down rapidly. Suggestion: provide a way for people to record when they have applied the "corrupt file system" fix, when they have replaced a USB stick, and what size and brand they have replaced it with. Wrt the latter, the data in the article probably don't show what USB stick is in a connected probe, only what kind of stick you shipped it with.”
Hi John, Thanks for constructive thoughts and your suggestion. We keep track of failure rates for various versions of RIPE Atlas probes to a certain extend. You can see some of this anlysis in this earlier article on RIPE Labs: https://labs.ripe.net/Members/philip_homburg/further-analysis-of-ripe-atlas-version-3-probe. Ultimately the best solution might be to look at completely different hardware. This is on our roadmap but will take some time to investigate.
“Hello. I need to contact admin. Thank you.”
Please contact labs@ripe.net.
“I had also this issue: with normal reboot didn't get a IP. without USB the probe gets again a IP but plugin the USB didn't solve the issue. The probe was still "not connected". the info in SoS were coming quickly. I had to reboot later several times with the USB. Now is OK. I hope for a long time .....”
Hi Jean-Michel, thanks for letting us know. We're working on a more long-term solution. Please also see this RIPE Labs article in that context: https://labs.ripe.net/Members/kistel/ripe-atlas-countering-hardware-issues-with-better-firmware
“Great (and a good answer to the people who would like the packets to stay inside human borders) but small typo: the IETF working group on DNS privacy is DPRIVE, not DPRIV.”
Oops. Fixed. Thanks, Stéphane.
“The link to the SURFnet website is broken :(”
Hi Sander, Thanks for pointing this out. I found it and updated the link. Mirjam
Showing 44 comment(s)