My /64 is reachable but /48 is not

[trevorwarwick]

I've got no connectivity from IPv6 hosts on my home network to the IPv6 internet. It was working fine up until today when I started experimenting with DDNS updates for my IPv4 endpoint address (which I couldn't actually get to work yet either, but that's for another day).

My tunnel is up, but reachability to my /48 isn't working any more.

From my home router, using a source address from my HE tunnel /64 range, I can ping various IPv6 addresses (HE, Google...) successfully.   However, if I ping using a source address from my /48 prefix, it doesn't work.

Doing a traceroute to my tunnel endpoint address on the /64 from elsewhere on the IPv6 internet works successfully, but if I traceroute to an address on my /48, the last entry from the traceroute is:

8  *  *   gige-gbge0.tserv5.lon1.ipv6.he.net (2001:470:0:67::2) !U

So it looks like although my tunnel is up, HE doesn't think my /48 is reachable.  I don't believe it's anything at my end, I've checked ACLs etc., but would be happy to be proved wrong...

[broquea]

Tunnels are rebuilding and verified that they are correct. Once that finishes, then the /48s get configured.