problems after certifying tunnel

[annoyingspore]

I set up a tunnel on fedora linux and he.net says it was ok, but now says it isnt, it seems to be broken. the Ipv4 VPN tunnel works, but i cannot ping6 from any of my windows or linux boxes to each other, or to he.net. I have tried to set ufw and iptables to forward packets, echo requests, etc, and checked the routing table. I will give an example:

my local /64 is obviously 2001:470:1f11:835:: , and my tunnel 2001:470:1f10:835::2

here is an ubuntu box:

eth0      Link encap:Ethernet  HWaddr 00:90:27:7b:ed:a9 
          inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::290:27ff:fe7b:eda9/64 Scope:Link
          inet6 addr: 2001:470:1f11:835::70/64 Scope:Global

Kernel IPv6 routing table
Destination                    Next Hop                   Flag Met Ref Use If
2001:470:1f11:835::/64         ::                         U    256 0     1 eth0
2001:470:1f11:835::/64         ::                         U    256 0     1 eth2
fe80::/64                                ::                         U    256 0     0 eth0
fe80::/64                                ::                         U    256 0     0 eth2
::/0                           2001:470:1f11:835::5       UG   1   0   597 eth0
::/0                           2001:470:1f11:835::5       UG   1   0     0 eth2

obviously, that isnt all of it, just relevant part. ::5 is the fedora box with tunnel.

also, shouldnt i be able to ping6 the other end of the tunnel, from 2001:470:1f10:835::2 to ::1 ?
I should say, it seems to be the same problem whether using VPN or not.

here are some example tests:

traceroute to 2001:470:1f11:835::5 (2001:470:1f11:835::5), 30 hops max, 80 byte packets
 1  2001:470:1f11:835::70 (2001:470:1f11:835::70)  3002.709 ms !H  3002.681 ms !H  3002.648 ms !H

PING 2001:470:1f11:835::5(2001:470:1f11:835::5) 56 data bytes
From 2001:470:1f11:835::70 icmp_seq=1 Destination unreachable: Address unreachable

strangely
PING 2001:470:1f11:835::55(2001:470:1f11:835::55) 56 data bytes
which is another ethernet card on same fedora machine gives nothing at all.

[cholzhauer]

did it ever work?  what commands did you use to setup the tunnel?

[annoyingspore]

the commands to set it up are the normal ones listed on the tunnelbroker website. i put them in rc.local and created the he-ipv6 tunnel. sorry, i didnt list that. this one is through a VPN, so the endpoint is static.
Also I just made another tunnel on a d-link dir-601 router. you can do it right from the local web-based setup screen. this one is not a VPN, so must use local router address 192.168.0.1 as endpoint, i am pretty sure. this does not work either.
so strange that it worked before, and yes i did update the endpoint address on tunnelbroker website.

[annoyingspore]

this one is so simple, i dont know how it cant work.
on windows i have: static IP: 2001:470:1f11:744::112/64, gateway 2001:470:1f11:744::1, which is d-link router.
on router: IPv6 in IPv4 tunnel:
                         remote IP's are normal, local IPv4 192.168.0.2, which it gets from modem (diamond multimedia supramax on ATT DSL).
         d-link router says:
IPv6 Connection Type :     IPv6 in IPv4 Tunnel
Network Status :     Connected
WAN IPv6 Address :     2001:470:1f10:744::2/64
IPv6 Default Gateway :     2001:470:1f10:744::1
LAN IPv6 Address :     2001:470:1f11:744::1/64
LAN IPv6 Link-Local Address :     fe80::1eaf:f7ff:fed9:e187/64
Primary DNS Address :     2001:470:20::2

he.net certification says:  You do not appear to be using an IPv6 capable connection.

http://test-ipv6.com/ says:  No IPv6 address detected.

[annoyingspore]

I am having this other really dumb problem. IPv6 doesnt even work on my local net. on windows 7 I just put in manually 2001:470:etc::12 , the gateway 2001:etc:1 (the dlink DIR-601 router) , which is set as above. windows tells me : IPv6 Connectivity        no network access". Are older switches a problem with IPv6? I have a dlink DES-3226L and a Gateway 7401. Actually I just tried it going straight from windows 7 to the DIR-601 and same problem.

[annoyingspore]

about that question:

no, 2001:470:1f11:744::1 is my router. 2001:470:1f10:744::1 would be he.nets gateway. 2001:470:1f10:744::2 my end of the tunnel. i was told to use the local 1F11 address as the router for other computers on the network.

I have also noticed that, using my DES-601 router as a stateful DHCPv6 server, my windows 7 IPv6 auto-config wont pick it up, but if i use stateless IPv6, it does seem to set it to a proper IPv6 address, but didnt set the default gateway.