IPv6, Linode & Stats
June 21, 2011
Yesterday, I talked about some of the work I did in the weekend server overhaul. One of those tasks I wanted to talk about a little more was the addition of native IPv6 because I feel very strongly that IPv6 is important, not just to this blog, but to the future of the internet. I’m very excited that Linode offered native IPv6 in its datacenters as early as May and I’m sorry I missed that for World IPv6 Day. Linode even has a full FAQ just for IPv6. What I’d wish they’d add is a little section to the effect of “Is IPv6 easy to use?” in which case the answer is a resounding “Yes!". Most popular server applications, such as Apache, require zero effort to get IPv6 compatible.
IPv6: Backwater hick to bleeding edge – in a weekend?!
July 14, 2010
So last week, I didn’t know a whole lot about IPv6 (backwater hick — slow and behind the times). After spending a long weekend delving into the world of it, I find out that I’m basically on the bleeding edge already… and that makes me sad. How can I go from not even having used IPv6 to the bleeding edge in a few days? As it turns out, there isn’t much of a distance to go.
Two new sites: Where's Gibson & IPv6 Wiki
July 13, 2010
So the Snowulf Network of websites has grown by two over the last week. Normally, I try not to add too many sites to my belt as it tends to make for a lot of administration. In these particular cases I have to make an exception. Let me explain briefly why I brought these two new sites about.
IPv6: Getting functional DHCPv6 and Route Advertising together
July 9, 2010
If you’re not into IPv6, but you’re a networking person — you may want to avert you eyes. This next piece of information is going to cause you pain: DHCPv6 does not support/allow you to send default gateway. This is “by design”. Does your brain hurt yet? I know mine did when I first found this out. This seems to be the most bass-ackwards thing I’ve ever heard of, but then again IPv6 is different. I’m sure there is logic behind this decision, I just don’t understand enough of the details of IPv6 (yet) to comprehend that logic. What does this mean for you? In short: You need both DHCPv6 and route advertising.
Getting underway with IPv6
July 6, 2010
So let me start off by saying, I’m not new to the world of networking. I’ve been doing this for a long while now. I had a Linux box running as a router on a PPPoE DSL line back before you could even buy a home “router” (IE Linksys). Heck, I had the network running before Pac Bell even had tech support that could handle the concept of more than one computer on a DSL line (and let me tell you, mentioning the word “Linux” around them was hilarious). You’d think that since I’ve been doing this for so long, I must have experience with IPv6… but I don’t. There are a few reasons for this: A) No ISP or server host I’ve ever used has provided IPv6 addresses B) IPv6 has really only started to “pick up” in the last 2-3 years and most importantly C) I’ve never had a need. If you don’t have the need or the access, why bother putting the effort into trying to fight it? Besides, while IPv6 introduces a lot more features into the core stack than just more addresses, I expected it to work mostly the same on a basic level. As it turns out that only seems to be the case in the server world, at home that is not exactly the case.