6to4 - Why is it so Bad?
In a previous article we measured that a large percentage of 6to4 connections fail. In this article we show our attempts to find out why these connections fail.
Emile Aben
Based in Amsterdam, NL
98
Articles
414
Likes on articles
Based in Amsterdam, NL
I'm a system architect/research coordinator at the RIPE NCC, where I work in the science group. I'm a chemist by training, but have been working since 1998 on Internet related things, as a sysadmin, security consultant, web developer and researcher. I am interested in technology changes (like IPv6 deployment), Internet measurement, data analysis, data visualisation, sustainability and security. I'd like to bring research and operations closer together, ie. do research that is operationally relevant. When I'm not working I like to make music (electric guitar, bass and drums), do sports (swimming, (inline) skating, bouldering, soccer), and try to be a good parent.
Website: https://www.caida.org/~emile
RIPE Atlas - the iPad Drawing
This article is about the lottery of an iPad for people hosting RIPE Atlas probes. As an extra motivator for people to keep their probes up as much as possible, the lottery drawing is weighted based on probe-uptime.
6to4 - How Bad is it Really?
At the recent RIPE 61 meeting in Rome and at earlier meetings, we heard that connectivity over 6to4 is not very dependable, which hampers IPv6 deployment. I wondered how bad it really is and started measuring it. This article describes what I measured and shows the results. Spoiler: It's pretty bad.
IPv6 RIPEness - The List of 4-star LIRs
Following up from the IPv6 RIPEness graphs we published earlier, those Local Internet Registries (LIRs) that fulfill all 4 IPv6 RIPEness criteria are now listed on the RIPE NCC web site.
Interesting Graph - Networks with IPv6 over Time
This infographic shows the percentage of networks (autonomous systems) that are IPv6 enabled from 2004 up until now. The interactive graph allows for comparison between IPv6 deployment in countries, and groups of countries.
Interesting Graph - IPv6 Performance
This graph shows IPv6 performance as measured to www.ripe.net. These measurements show performance of native IPv6 on average being very close to IPv4.
IPv6 RIPEness - the Sequel
As a follow-up to the article IPv6 RIPEness of LIRs, we did more analysis based on LIR signup year, size and the industry sector that the LIR operates in.
Interesting Graph - IPv6 and RIPE 60
We measured the number of web clients connected to www.ripe.net during the RIPE 60 meeting in Prague. The results are shown in this graph.
Interesting Graph - IPv6 RIPEness Movie
After creating a rating system, in which RIPE NCC members can get up to four “stars” for IPv6 services, depending on certain criteria, we now looked at the increase of IPv6 RIPEness over time. See this illustrated in this movie.
Interesting Graphs - Priming Queries to the Root Servers
There was a slight increase in the number of sources that issue priming queries to DNS root servers seen on 18 March 2010, right after the introduction of a signed .arpa zone. See here an analysis and some graphs.
“@emileaben Rather than standardizing human-readable output format, why not emitting a standard structured format, separating the network part (traceroute) and the visualisation part (a tool using the structured output format). Such a format already exists, in RFC 5388. I let you do the same in JSON :-)”
thanks for the interest in the topic Stephane. You hit the nail on the head, the main idea was to standardise a structured format for traceroute. I notice a lack of enthusiasm for RFC5388, probably due to it's verbosity. quick test shows that gzip compression of RFC5388-style results would need 3x more storage relative to plain-text traceroute results. But the RFC is likely very useful to see if we cover all bases in a slimmer structured output format.
One other activity that may be worth mentioning here: We organised a get-together for traceroute implementers. As many traceroute implementations do things slightly different, a bit more coordination can help in making things more consistent, for instance in output formats.
“I'm trying to work with the ixp-jedi tool. In this step: ## measure.py This script runs one-off measurements for the probes specified in _probeset.json_ and stores their results in _measurementset.json_ This uses the RIPE Atlas measurement API for measurement creation, And it needs a valid measurement creation API key in ~ / .atlas / auth When trying to execute the script ./measure.py I get the following and I do not know how to solve it. Authentication file /root/.atlas/auth not found Please, I need your help.”
hi, thanks for trying to use the tool. i hope the docs on github are clear enough: https://github.com/emileaben/ixp-country-jedi/#measurepy --- This script runs one-off measurements for the probes specified in probeset.json and stores their results in measurementset.json This uses the RIPE Atlas measurement API for measurement creation, and it needs a valid measurement creation API key in ~/.atlas/auth . For more information on RIPE Atlas API keys see https://atlas.ripe.net/docs/keys/ --- if not let me know how to improve that. if you are interested in country-level monthy runs. these are available at: http://sg-pub.ripe.net/emile/ixp-country-jedi/history/
“Hi, Is there a way to download multiple days dataset without having to do them individually? Also do you have any API's which will permit me to download the datasets using wget?”
Hi Meenakshi, I think you'll have to download the files individually. I think, if your RIPE Access account doesn't have 2 factor authentication, you can use wget to download the files with the --user and --password options.
While we were busy pushing this post out, it looks like the Gambian Internet was restored, roughly around 12h UTC on 2 December. RIPE Atlas probes came online again, and we see 6 out of 7 ASNs in RIS data again.
Showing 15 comment(s)