These photo's might help you figure out the problem.
just a guess but when you log into Tunnelbroker and check your settings for your tunnel do you have your current and correct ipv4 address there?
But HE isn't using 6rd...
An EA4500 or E4200v2 are able to setup a tunnel with HE.
IPv6 - Automatic: Disabled.
6rd Tunnel: Manual Configuration.
Prefix: the Routed /64 addres without the ::/64.
Prefix length: 64.
Border Relay: the Server IPv4 Address.
IPv4 Address Mask Length: 32.
Click: Save Settings.
Be sure your ISP IPv4 address is still correctly registered at HE.
Same for the E2500 if the firmware has been updated to a version that supports IPv6 - see http://www.tunnelbroker.net/forums/index.php?topic=1850.msg16216#msg16216 (http://www.tunnelbroker.net/forums/index.php?topic=1850.msg16216#msg16216)
Quote from: valkenbw on January 06, 2013, 04:17:19 AM
An EA4500 or E4200v2 are able to setup a tunnel with HE.
IPv6 - Automatic: Disabled.
6rd Tunnel: Manual Configuration.
Prefix: the Routed /64 addres without the ::/64.
Prefix length: 64.
Border Relay: the Server IPv4 Address.
IPv4 Address Mask Length: 32.
Click: Save Settings.
Be sure your ISP IPv4 address is still correctly registered at HE.
Sorry to dig up an oldie but having a few issues
Prefix: the Routed /64 address without the ::/64.when I tried this is just told me I had an invalid address, I had to add the :: at the end.
and more over, it won't work. can't connect to any ipv6 addresses.
checked and rechecked my tunnel details and they are correct..
any ideas?
Quote from: Esgargoth on May 19, 2013, 08:53:04 AMany ideas?
My first guess is you got something wrong in the configuration. If you post a screenshot of the configuration, we can probably figure it out.
Server IPV4 Address : 216.66.80.26
Routed /64: 2001:470:1f09:b4b::/64
Tunnel was only set up recently.
Cheers
cannot post pics so linking to outside web.
http://homepage.ntlworld.com/esgargoth/random/connex 1.jpg (http://homepage.ntlworld.com/esgargoth/random/connex%201.jpg)
http://homepage.ntlworld.com/esgargoth/random/connex 2.jpg (http://homepage.ntlworld.com/esgargoth/random/connex%202.jpg)
Quote from: Esgargoth on May 20, 2013, 03:06:58 AM
Server IPV4 Address : 216.66.80.26
Routed /64: 2001:470:1f09:b4b::/64
Tunnel was only set up recently.
Could you try temporarily setting your tunnel server as 80.167.222.169 and then try to ping 2001:470:28:940:f015:4a71:c958:1ffd. That way we can see if you can even get protocol 41 packets out.
C:\Users\David>ping -6 2001:470:28:940:f015:4a71:c958:1ffd
Pinging 2001:470:28:940:f015:4a71:c958:1ffd with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
Ping statistics for 2001:470:28:940:f015:4a71:c958:1ffd:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
That's a no then..
that was changing the server to specified ip.
the netsh protocols that HE provide I assume only apply if making the tunnel from the computer not from the router. correct?
Quote from: Esgargoth on May 20, 2013, 04:41:10 AMPING: transmit failed. General failure.
Sounds like your computer does not have any IPv6 address. I guess this means either that the router is not advertising itself as an IPv6 router on the LAN, or IPv6 is disabled on the computer. Check the local network tab in the router configuration.
I did receive some pings on 2001:470:28:940:f015:4a71:c958:1ffd. They came from a gogo6 address, I suppose that was somebody else.
Quote from: Esgargoth on May 20, 2013, 04:41:10 AMthe netsh protocols that HE provide I assume only apply if making the tunnel from the computer not from the router. correct?
Assuming those are commands to setup the tunnel, then it is correct, that they only apply if the computer is the tunnel endpoint.
When using a router as the tunnel endpoint, then you obviously need to configure the tunnel on the router. You may still need to enable IPv6 on the computer. There may exist systems, where enabling IPv6 can be done with a simple netsh command.
Hi sorry for the delay, the pings received were from a ipv6 application that I have called gogo6
however I had that disabled when attempting the pings the second time
I have given up on this for the time being as I am too busy with work.
Thanks for the help however.
i'll be back at it in a few months