Hi Murray,
On Sat, Aug 30, 2014 at 04:39:47PM +0100, Murray Crane wrote:
I'm about ready to start seriously looking at
IPv6; threw away the terrible
BT Home Hub 3 and replaced it with a TP-Link that I have now noticed has
6to4 built in and I figure that might be enough for
"<strike>playing</strike>experimenting".
If you can't get (or don't want to pay to get) native IPv6 then I
would second the suggestion to use a tunnel broker like HE or SixXS.
Here's why:
http://en.wikipedia.org/wiki/6to4
"Due to the high levels of misconfigured hosts and poor
performance observed, an advisory about how 6to4 should be
deployed was published in August 2011."
The problem is that 6to4 relays are set up by organisations that you
have no relationship with, and are run with variable care. Trying to
use a broken 6to4 relay results in broken Internet, and you have no
one to talk to about that.
If you are going to tunnel, it would be best to do it with an
organisation that you have a relationship with, hence HE or SixXS.
Having said that, in the event of any problem SixXS will probably
just tell you to RTFM and HE will probably just ignore you, but at
least you'll know who to have the conversation with. :)
More seriously, HE and SixXS have a greater chance of working than
6to4.
Providing your own IPv6 tunnelling is also an option:
https://tools.bitfolk.com/wiki/IPv6/VPNs
(this article could do with more documented methiods than just
tincd)
although if your purpose in configuring IPv6 is partly to test your
VPS's IPv6 then it may not make sense to have your tunnel depend on
your VPS.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting