Hruške, jabuke, jablane, čežane.

As Tomaž writes, there is another possibility of acquiring IPv6 connectivity, the so called tunnel brokers.

There’s aiccu, which is a tunnel client. It’s not completely plug’n'play, since you need to be registered user at one of the tunnel brokers.

Then there’s tspc, which Tomaž already mentioned. It works out of the box, except in some really restricted environments, where the firewall blocks nearly all UDP traffic. The downside compared to 6to4 is you get a different IP every time you connect, that packets are always routed through a tunnel server and the lantency is quite high.

Next is Miredo (also packaged in Debian), which is a Teredo protocol implementation. Teredo was originally developed at Microsoft and is enabled in Windows Vista by default, though it may be inactive. Teredo has teredo servers, teredo relays and teredo clients. Serves are used for ICMPv6 and when establishing tunnel and therefore do not need much bandwidth, the real IPv6 traffic is passed through relays.

Microsoft predicts ISPs and other large network providers will setup Teredo relays in order not to route local traffic out and back. This would actually enable the best possible way for transition to IPv6, slow and distributed. With Vista out and with out of the box support for IPv6, it’s only matter of time when home routers and other network appliances will start supporting IPv6. Not to mention that IPv6 has really improved support for multicast, effectively eliminating need for P2P applications (e.g. Octoshape, that our national television has used) to provide straming video.

To finish this, while tspc works, it’s probably not the best. I’ve tried pinging ftp.hr.debian.org (which has real IPv6 and is not using 6to4) and gotten lower latency with 6to4, and suprisingly, even lower with Miredo. It might seem useful to route 6to4 addresses via 6to4 and all other via miredo tunnel.

Comments are closed.