Ok so HE is doing the right thing for all intents and purposes, it's just a case of those that came up with IPv6 did another stupid thing *sigh*

This along with the /64 per subnet which is also stupid, there is really no need for more then /112 at most since thats about when a lot of switches tend to start hitting MAC limits, obviously this can be increased but for most home users is there a real need, I doubt it.

In fact a /120 or less would be far better, especially now that DHCPv6 software is available, when I last seriously played with IPv6 a few years ago it wasn't.

The reason I'm suggesting this of course is because I don't want to end up where we are now with IPv6 needing to move to IPv8 or whatever they come up with next just because there is a shortage of IP space due to stupid allocation ideas of the people designing these things not living in the real world.

If things were issued on a /128 basis for the PtP and then a /120 issued a single /64 alone would support 36,028,797,018,963,968 tunnels + routed subnets.

The way things are currently going, if every server today that has at least 1 IPv4 address was allocated a /64 and on top of that every home network getting a /64 to the router and a /48 how long before they start talking about us running about of IPv6 addresses?

I haven't done the math but at the current estimated rate IPv4 addresses are being consumed, IPv6 addresses would be gone in a similar time frame.

Not to seem ungrateful and what not but I can't help but think that a /64 for a Point to Point link and a /48 for what most people only need a /64 at most for is a little wasteful, although I can see how on the other hand this would give he.net a massive amount of IP space which would drop off as ISPs and colo places start allocating native IP space so hmmm....

I don't know what caused this is, or why this occured or what was going on, but the moment I set an AAAA glue record on a domain that I wasn't planning to setup a website on an AAAA record, from then on my Xubuntu laptop for the most part no longer seemed to request A records when I tried to go to the website.

The only way I seemed to get my computer to request A records again was to remove the IPv6 address from DNS.

Does anyone know if this behaviour was really what was supposed to happen?

This was on a Xen virtual hosting and I'm not entirely sure if it's something I've done or something they've done or .... I have a similar Xen hosting I'm planning to play around with in future, just haven't gotten there yet but here's the problem.

Both linux examples on the tunnel info page failed, eg:

# ip link set he-ipv6 up
RTNETLINK answers: Invalid argument

Yet when I 'apt-get install tspc' there was a tunnel up and running no problem at all so I knew some combination of commands would work, in the end it turns out all I needed to do was 'ifconfig he-ipv6 up' and the rest of the ipv6 commands would work fine, I have no idea why ip link set he-ipv6 up wouldn't.

Hope this saves someone some time that ends up in the same situation.