
The Curious Case of 128.0/16
The prefix 128.0/16 is filtered in Juniper devices up to and including JUNOS software version 11.1. We looked at three ways to get a rough estimate on how much filtering of 128.0/16 is going on on the Internet.
Based in Amsterdam, NL
Articles
Likes on articles
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
The prefix 128.0/16 is filtered in Juniper devices up to and including JUNOS software version 11.1. We looked at three ways to get a rough estimate on how much filtering of 128.0/16 is going on on the Internet.
Often when looking at IPv6 deployment statistics, the size of the organisation or the network is not taken into account. In this article, we look at IPv6 deployment of Local Internet Registries (LIRs) per country in correlation with the size of the LIR.
In this article we look at two "Happy Eyeballs" implementations, that aim to reduce degraded user experience as the result of broken dual-stack configurations. We call this degraded user experience "Unhappy Eyeballs". The Chrome web browser implementation seems to succeed in this aim, while Apple's…
This weekend the NANOG mailing list was abuzz about an F-root IPv6 route leak, that resulted in the F-root DNS server instance located in Bejing, China, being queried from outside of China. This normally doesn't happen, as this instance is advertised with the BGP attribute NO_EXPORT, which means it…
During World IPv6 day we measured the performance of IPv4 and IPv6 between 40 vantage points and 46 World IPv6 Day participants and other dual-stacked sites. If one has to pick a winner, then the old protocol, IPv4, would win, but IPv6 often shows comparable or better performance.
In this article we'll look at some of the more long-term effects of World IPv6 Day, as seen in our measurements a number of weeks after the event itself.
As already stated by us and others, World IPv6 Day on 8 June, was a big success. No major issues came to light, and most minor issues that surfaced were resolved, and as such were a useful learning experience. In this article we provide details on some of the events we observed by looking at our me…
World IPv6 Day is on 8 June 2011. On this day, a lot of organisations, including some of the most popular ones like Google, Yahoo and Facebook, are going to provide IPv6 addresses for AAAA queries for their websites. This will make content available over IPv6 for one full day. Since DNS responses a…
The RIPE NCC is doing some measurements for World IPv6 Day. One of them is the IPv6 eye chart, a web page that allows you to test your connectivity to selected dual-stacked web sites and World IPv6 participants. The goal is to see if an end user has connectivity problems to dual-stacked websites. T…
As announced earlier, the RIPE NCC is going to measure World IPv6 Day. This article details the measurements we intend to do.
“@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)