Getting IPv6 Using Freenet6 on Debian
IPv6 is the successor to our current internet protocol, IPv4. It offers many new features, including vastly increased address space--128 bits vs. IPv4's measly 32 bits--easier autoconfiguration and better support for encryption, just to name a few. The Debian project has done a good job of making its distribution IPv6-ready. In this article, you'll learn how to setup a IPv6-over-IPv4 tunnel using the free Freenet6 tunnel service. Note that I'm assuming you're using Debian testing (woody) or unstable (sid) and understand how to install packages through apt. I'm also assuming you know a little bit about IPv6, such as what an address looks like.
Before beginning the tunnel, you'll need a publicly addressable IPv4 address on the machine you're using. Your kernel also must support IPv6; Debian's default kernels do support IPv6. If you're not sure if your kernel does support it, check for a /proc/sys/net/ipv6 directory. Also see if the output of ifconfig contains any IPv6 addresses, something like fe80::24f:49ff:fe07:2552 Make sure your firewall isn't blocking IPv6 tunnel packets, IP protocol 41 (ipv6) must not be blocked in either direction.
Once you've confirmed all of this, start the tunnel by installing the Freenet6 client software with apt. The Debian package is called Freenet6 and is available in both testing and unstable versions. Once it's installed, Freenet6 automatically gets a IPv6 address for you based on your existing IPv4 address; no configuration is required. That's right, everything will work right out of the box on most systems simply by installing Freenet6.
Note that this IPv6 address is tied to your IPv4 address, if the IPv4 address changes so does your IPv6 address. Fortunately, if you've used the standard Debian systems for your internet connection, such as the PPP packages and the included dhcp clients, Debian will automatically get a new IPv6 address for you if your IPv4 address changes.
To test your IPv6 connection, try pinging something with the ping6 program. If you find that you don't have ping6, install it with the iputils-ping package. Some hosts to try pinging include www.6bone.net and www.kame.net. If the pings aren't working, double-check that your firewall isn't blocking IPv6 packets. If the pings do work, next try connecting to www.kame.net with Lynx, Mozilla or Konqueror. These browsers have IPv6 support in Debian testing. If everything is still working correctly, there will be a "dancing kame" at the top of the page and a little message at the bottom. If it still says you're using IPv4, and the ping6 test worked fine, double-check that you're using the latest version of the browser.
Congratulations! You're on the next generation internet! If you have a network behind a Linux router, you can also provide IPv6 for the machines behind it using Freenet6 and the radvd. How to do it will be explained in an upcoming issue of Linux Journal.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Huge Package Overhaul for Debian and Ubuntu
- Home Automation with Raspberry Pi
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development