Difference between revisions of "IPv6"
ReMARKable (Talk | contribs) m |
ReMARKable (Talk | contribs) m |
||
| Line 70: | Line 70: | ||
'''Tunnelbroker problems''' | '''Tunnelbroker problems''' | ||
| + | |||
When you expect troubles with the freenet6.net tunnelbroker, please check [http://gogonet.gogo6.com/page/service-status their status page] | When you expect troubles with the freenet6.net tunnelbroker, please check [http://gogonet.gogo6.com/page/service-status their status page] | ||
Revision as of 21:58, 9 May 2011
Contents
What is IPv6
IPv6 is a version of the Internet Protocol (IP) that is designed to succeed Internet Protocol version 4 (IPv4). The reason to switch to IPv6 is the shortage of IPv4 numbers. The most important feature of IPv6 is a much larger address space than in IPv4. The length of an IPv6 address is 128 bits, compared to 32 bits in IPv4. The address space therefore supports 2128 (or approximately 340 undecillion or 3.4×1038) addresses. (see also [1])
When do we need IPv6
February 2011 IANA (Global IP registrar) ran out of IPv4 space to hand out to the RIRs (Regional IP Registrars). The fist RIR to ran out of IPv4 numbers was APNIC (Asia/Pacific/Australia) in April 2011. Ripe (Europe) is expected to be the next to run out of IPv4 space (expected September 2011). When a RIR runs out of space ISPs within their region cannot obtain new IPv4-addresses anymore, so their stack will run out too. From that point on ISPs has to take countermeasures for their customers to deliver Internet connectivity over IPv6. Some ISPs would deliver their services over NATted IPv4, but in a few years all ISPs has to deliver IPv6 natively.
For the customers who have a working Internet connection right now, don't worry, you IPv4 address will not disappear on short term. More likely is that your connection will be upgraded somewhere in time to dual-stack (IPv4+IPv6). This may still take years for that to happen.
Why do I want to use IPv6
As IPv4 has no future anymore and there is no doubt IPv6 is the next generation IP protocol, why not. The problem is ISP's are very slow in delivering IPv6 to their customers and hardware vendors are even slower, even when most hardware can do IPv6, the software is not ready for IPv6.
Why does the WDlxTV support IPv6
As WD is not supporting IPv6, we have to. We need to support the future IP protocol as we want our WD-player to last longer then the IPv4 protocol.
How can I enable IPv6 on the WDlxTV
First of all you need to have WDlxTV firmware version 5.0 or higher. There are 2 ways of using IPv6, native or tunneled. Native can only be used when your ISP hands you out native IPv6.
Native connection
When your ISP hands out native IPv6 addresses and you didn't receive yours yet, ask for it! Your router must also support IPv6. When everything is IPv6 ready, you can just switch on IPv6 in the web-GUI or in the configfile by setting the IPv6=ON. The WDlxTV will now listen to your routers IPv6 Router Advertisement to obtain an IPv6 address. This is called Stateless Address Auto Configuration (SLAAC).
Tunneled connection
IPv6 is setup over an IPv4 tunnel. In order to make it as simple as possible for the WDlxTV users we have chosen Freenet6.net tunnel-broker. All you need is the IPv6.app.bin loaded on the USB-stick and fill in the setting in the Web-GUI. The tunnel will be setup automatically and the WDlxTV can now communicate over IPv6 as well.
When your WDlxTV is bringing IPv6 to your house, why not take this opportunity and let the WDlxTV become your IPv6 router. This can easily be done by creating a Freenet6 account and use the settings in the GUI and select the RA (Router Advertisement) option. Now the WDlxTV will setup an IPv6 tunnel over IPv4, receives a /56 from the tunnel-broker and hands out a /64 to ETH0. All you devices on the same LAN which are IPv6 aware will now receive an IPv6 address.
Beware: By using a tunnel the firewall on your router is bypassed for the IPv6 traffic. The tunnel is legitimate and therefor the IPv6 packets within the tunnel will not be inspected anymore. IPv6 is not using NAT, so the IPv6 address your WDlxTV is getting is public IPv6 space. So beware you are running a firewall on your PC's and change your password on the WD (telnet and GUI).
Troubleshooting
What can you check when the IPv6.app.bin is not working
For native IPv6:
- ifconfig
This should show both fe80:: address as well as 2 x 2xxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx address (even 3 when you use fixed IPv6 too). 1 address is generated out of your MAC-address, 1 address is a temporarily address. THe fe80:: address is a link-local address and is always needed by IPv6. This is a non-routable IPv6 address.
Messages from the startup script can be found in /tmp/messages
For tunneled IPv6:
- Ifconfig
This should show 3 interfaces, eth0, lo and a tunnel interface. This tunneled interface can be called tun (when the WDlxTV is behind NAT) or sit0.
Other information can be found in:
- tail /tmp/IPv6/gogoc.log - cat /tmp/messages | grep IPv6 - ps | grep IPv6
This last command should show gogoc (and radvd when RA is enabled). To see if the router-advertisements are advertised you can type radvdump on the CLI to see the output. This can take a while. Press CTRL-C to exit radvdump.
Generic IPv6 tools:
- ping6 - traceroute6 - route -6
Tunnelbroker problems
When you expect troubles with the freenet6.net tunnelbroker, please check their status page
