I spent some time in the United States last month. Equipped with SIM cards from both Tele2 Sweden (MCCMNC 24007) and Telenor Norway (MCCMNC 24201), I set out to test IPv6 while roaming, as I usually do while abroad.
I attended the Netnod Tech Meeting 2017 in Stockholm earlier this week. As I usually do when when going abroad, I spent some time testing to what extent IPv6 works while roaming in the various PLMNs I have access to.
I spent this weekend in Czechia. As I usually do when when going abroad, I spent some time testing to what extent IPv6 works while roaming in the various PLMNs I have access to.
UPDATE 2018-12-01: The parts about missing IPv6 support in this post is outdated, see this post for updated information.
When I created this blog a couple of years ago, I was disappointed to find out that the GitHub Pages service (GHP) did not support IPv6. This was due to the fact that GHP’s CDN provider Fastly didn’t support IPv6.
Earlier this week I visited the United Kingdom to attend the excellent UKNOF36 meeting.
I briefly visited Belgium and Romania last month. Using SIM cards from Tele 2 Sweden and Telenor Norway, both of which support the dual-stack
IPV6PDP context types, I spent some time testing whether or not I was able to get working IPv6 Internet connectivity while roaming in the various available PLMNs.
UPDATE 2017-10-15: The information in this post is outdated, see this post for an updated version.
The other day, I noticed with great interest that my PlayStation 4 was using IPv6 to communicate with the Internet. I’m fairly certain that this behaviour is new, so I decided to investigate.
I’m very pleased to report that my SIIT-DC RFCs were published by the IETF last week. If you’re interested in learning how to operate an IPv6-only data centre while ensuring that IPv4-only Internet users will remain able to access the services hosted in it, you should really check them out.
2016 is soon approaching. In this post I’ll take a look in the rear-view mirror to see how well we did in Norway with regards to IPv6 deployment in 2015. I focus on the status on the end-user side of things, that is, the extent of IPv6 deployment amongst Norwegian ISPs. This is due to the fact that my employer Redpill Linpro mainly provide managed services to content providers, so the traffic entering our dual-stacked data centres can only tell a story about how the ISPs are doing.
Here at Redpill Linpro we make extensive use of network booting to provision software onto our servers. Many of our servers don’t even have local storage - they boot from the network every time they start up. Others use network boot in order to install an operating system to local storage. The days when we were running around in our data centres with USB or optical install media are long gone, and we’re definitively not looking back.
One of the few remaining IPv4-only services here at Redpill Linpro is our provisioning infrastructure, which is based on PXE network booting. I’ve long wanted to do something about that. Now that more and more servers are shipping with UEFI support, I am finally in a position to start looking at it.
Here at Redpill Linpro we’re big fans of the Varnish Cache. We tend to put Varnish in front of almost every web site that we operate for our customers, which goes a long way toward ensuring that they respond blazingly fast - even though the applications themselves might not always be designed with speed or scalability in mind.
This post provides a step-by-step guide on how to take a residential gateway running OpenWrt, installing the software from the Hnet project on it, and finally converting it to be a full-fledged Homenet router. The post is quite long, but don’t let that put you off - it’s only because I go through the process in minute detail. The entire conversion process shouldn’t take you more than 10-15 minutes.
The other day one of my colleagues at Redpill Linpro asked me to help him figure out why a web cache server started responding slowly during a traffic peak. My colleague was scratching his head over the problem, because although the traffic level was unusually high for the server in question, it was nowhere close to saturating the server’s 10 Gb/s of available network bandwidth:
Today’s residential home networks are quite simple. They usually have a single Internet connection, which is plugged in to the WAN port of a residential gateway. The gateway will typically feature a few wired Ethernet ports and a wireless access point, which are in most cases bridged together to form a single layer-2 LAN segment. The LAN segment is configured with private IPv4 addresses; in order to let the hosts and devices on the LAN segment to communicate with the IPv4 Internet, the gateway will perform IPv4 NAT.
Since 2012 I have been voting with my wallet, opting to only use mobile providers that give me IPv6 connectivity. To begin with, I was a customer of Network Norway. They were kind enough to include me in their IPv6-only pilot with DNS64 and NAT64. Unfortunately, Network Norway’s fate was to be acquired multiple times, causing their IPv6 pilot to lose momentum due to the loss of key technical personnel. The IPv6 pilot has not yet transitioned to a production service.
UPDATE 2017-07-31: The information in this post is no longer accurate; GitHub Pages and Fastly now do support IPv6.
So I’ve finally created my own blog, and you’ve found it, somehow. Congratulations! Expect only posts about technology - networking, data centres, open source software, reports from conferences I attend, et cetera. Essentially, various stuff I play around with both at home and at my workplace Redpill Linpro.
subscribe via RSS