I have setup the freenet6 Tunnel broker and it was working great. I have gotten my ipv6 block from them and have the tunnel broker up and online. I configured ipv6 DHCP for the block given and assigned the internal NIC with the first IP in that block. I tested it with the Test IPv6 web site when first setup and everything was green. I just now tested it again and it is failing. I can ping the internal IPv6 Gateway 2001:5C0:150F:6300::1 and can ping my tunnel broker IP 2001:5C0:1000:B::94BB. I can not however ping ipv6.google.com. The network they assigned to me is 2001:5C0:110C:9200::/56
The below is one of the clients that received the IPv6 from DHCP and IPv4 is static assigned
Any ideas what happen to make this break? I don't recall making any changes
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : SERVER
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home.markandbeth.net
check your tunnel broker IP again. You'll noticed they changed it. Not sure why they are doing this, but mine changed so often that setting IPv6 DHCP is useless. Hope someone has some idea why freenet6 keeps changing
Yep I see that now. Good catch. We may need to have some e-mail notice to administrator when astaro detects the change. I was under the impression that when you signed up that it would not change and only when you don't create an account it would change. This sucks
Freenet6 can be used in two modes: authenticated or anonymous. In authenticated mode, the IPv6 address and prefix are assigned permanently to a user and do not change when the user moves to a new IPv4 address. In anonymous mode, the IPv6 address changes with the IPv4 address.
In authenticated mode, two methods are available to perform the authentication: simple authentication or encrypted authentication. With simple authentication, the userID and password are sent in clear text; with encrypted authentication (MD5), SASL-DIGEST-MD5 is used to encrypt the account information.
I have terminated a Hurricane Electric tunnel on a spare router, and it works well. They automatically assign a /64, but when you create your tunnel there is a check box for a /48. The assignment does not change as long as your don't delete the tunnel. You can have upto five tunnels for free.
Judging from your ipconfig /all it appears that this is for a server running at home? If you don't have a spare Cisco router, you can use a cheap D-link. The DIR-632 is a good router for about $60, and it has great IPv6 support, including manually configured tunnels.
Also, it might be better to use prefix advertisements instead of DHCPv6 depending on your needs.