Hurricane Electric's IPv6 Tunnel Broker Forums

General IPv6 Topics => IPv6 Basics & Questions & General Chatter => Topic started by: marke50 on January 18, 2014, 05:19:30 AM

Title: ipv6 readyness check
Post by: marke50 on January 18, 2014, 05:19:30 AM
I had followed all of the steps for setting up the tunnel and ipv6 6 was working but now its not.
I've tried recreating tunnel but I still can't get to any ipv6 sites and test show that I don't have an ipv6 address

any ideas?
Title: Re: ipv6 readyness check
Post by: cholzhauer on January 18, 2014, 05:22:05 AM
Several

What's your config look like?
Title: Re: ipv6 readyness check
Post by: marke50 on January 18, 2014, 06:48:09 AM
thanks for helping but which config are you referring to?
please give me suggestions on what to run to get the config you are looking for
Title: Re: ipv6 readyness check
Post by: cholzhauer on January 18, 2014, 06:50:40 AM
How did you create your tunnel?

What does ipconfig/config show?
Title: Re: ipv6 readyness check
Post by: marke50 on January 18, 2014, 07:02:32 AM
It appears that I'm not getting an ipv6 address


IPv6 Tunnel Endpoints
Server IPv4 Address:209.51.161.14
Server IPv6 Address:2001:470:1f06:3::1/64
Client IPv4 Address:98.19.217.174
Client IPv6 Address:2001:470:1f06:3::2/64



Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6205
   Physical Address. . . . . . . . . : 6C-88-14-15-F8-EC
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::70ef:67cc:220b:c1f9%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.254.4(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, January 18, 2014 9:12:57 AM
   Lease Expires . . . . . . . . . . : Sunday, July 11, 2021 12:12:57 AM
   Default Gateway . . . . . . . . . : 192.168.254.254
   DHCP Server . . . . . . . . . . . : 192.168.254.254
   DHCPv6 IAID . . . . . . . . . . . : 377764427
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-D2-24-60-3C-97-0E-70-9E-2B
   DNS Servers . . . . . . . . . . . : 192.168.254.254
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter IP6Tunnel:

   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::ec82:5890:129f:aebc%29(Preferred)
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.254.254
   NetBIOS over Tcpip. . . . . . . . : Disabled
Title: Re: ipv6 readyness check
Post by: cholzhauer on January 18, 2014, 07:04:39 AM
What commands did you use to create the tunnel?
Title: Re: ipv6 readyness check
Post by: marke50 on January 18, 2014, 07:09:31 AM
This worked he first time setup the tunnel
I thought it was because the ISP changed IP's but even after I tried to correct that it didn't work


The windows 7 command

netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 192.168.254.4 98.19.217.174
netsh interface ipv6 add address IP6Tunnel 2001:470:1f06:3::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f06:3::1
Title: Re: ipv6 readyness check
Post by: cholzhauer on January 18, 2014, 07:11:05 AM
If the ip changed did you fix it on the he page?
Title: Re: ipv6 readyness check
Post by: marke50 on January 18, 2014, 07:16:08 AM
Maybe I should try again but 98.19.217.174 is my ip address

Title: Re: ipv6 readyness check
Post by: marke50 on January 18, 2014, 07:19:49 AM
If I run the command again this is what I get

C:\Users\*******>netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 98.19.217.174 209.51.161.14
You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control
 Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.



C:\Users\*******>netsh interface ipv6 add address IP6Tunnel 2001:470:1f06:3::2


C:\Users\********>netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f06:3::1
Ok.
Title: Re: ipv6 readyness check
Post by: marke50 on January 18, 2014, 09:23:07 AM
Quote
Several

Can I get a few of the several idea?

thanks

Title: Re: ipv6 readyness check
Post by: cholzhauer on January 18, 2014, 10:04:05 AM
Remove your tunnel and start again.  I don't remember the exact command, but it's something like netsh int ipv6 reset, but you'll want to Google to make sure.

Make sure that ip is on your account page in the tunnel broker webpage
Title: Re: ipv6 readyness check
Post by: marke50 on January 18, 2014, 07:33:27 PM
I removed the old tunnel and created a new and ran it again but it's still not working

I'm reaching for straws but should the DNS ip be a ipv4 address


Tunnel adapter IP6Tunnel:

   Connection-specific DNS Suffix  . : Home
   Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:1f06:3::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::5d65:2a2:6235:bba3%31(Preferred)
   Default Gateway . . . . . . . . . : 2001:470:1f06:3::1
   DNS Servers . . . . . . . . . . . : 192.168.254.254
   NetBIOS over Tcpip. . . . . . . . : Disabled
Title: Re: ipv6 readyness check
Post by: cholzhauer on January 19, 2014, 08:13:36 AM
DNS doesn't matter.

Here's things you need to make sure are working:
1) Make sure you have the correct IP address of your router set on http://tunnelbroker.com   You mentioned yours changed.  Update it here
2) Allow ICMP; make sure your ISP is not blocking it.
3) Allow Protcol 41.  Make sure your ISP is not blocking it.
4) You're behind a NAT; use the NAT address of the device you want to host the tunnel on instead of your public IP.
Title: Re: ipv6 readyness check
Post by: kasperd on January 19, 2014, 10:10:45 AM
I'm reaching for straws but should the DNS ip be a ipv4 address
Using an IPv4 address for DNS is a good idea until you are sure the tunnel is working. There is still a possibility that the DNS server provided by your ISP is unable to do AAAA lookups. Buggy DNS servers have been seen exhibit all sorts of weird behaviour, when queried for dual stack domains.

If you are unsure if the DNS server is working correctly, then identify v4-only, v6-only, and dual stack domains you can use for testing. For each of those three possibilities you should check that the DNS server gives you correct results when you ask for the A record first and then the AAAA record afterwards, and vice-versa. Since caching can affect the outcome, you need some part of the domain, you can vary and still get the same results. I have a few domains, you can use:
random.he.i11.test-ipv6.easyv6.net
random.he.i32.test-ipv6.easyv6.net
random.he.i42.test-ipv6.easyv6.net
Just substitute a new value instead of random for each test. For example you could use 90td8t to test lookup of A record first and AAAA record afterwards and you could use zwg5cy to test lookup of AAAA record first and A record afterwards.
Title: Re: ipv6 readyness check
Post by: marke50 on January 19, 2014, 04:42:54 PM
 I recreated the tunnel made the adjustment and this is what I get.


Link-Layer Address                 : 192.168.254.4
Remote Link-Layer Address          : 209.51.161.58

My IP address 192.168.254.4
IPv6 Tunnel Endpoints
Server IPv4 Address:209.51.161.58  I can ping

add address IP6Tunnel 2001:470:4:c0::2/64  I can ping
add route ::/0 IP6Tunnel 2001:470:4:c0::1/64 I can't ping

Interface IP6Tunnel Parameters
----------------------------------------------
IfLuid                             : tunnel_6
IfIndex                            : 30
State                              : connected
Metric                             : 25
Link MTU                           : 1280 bytes
Reachable Time                     : 18500 ms
Base Reachable Time                : 30000 ms
Retransmission Interval            : 1000 ms
DAD Transmits                      : 1
Site Prefix Length                 : 64
Site Id                            : 1
Forwarding                         : disabled
Advertising                        : disabled
Neighbor Discovery                 : disabled
Neighbor Unreachability Detection  : disabled
Router Discovery                   : disabled
Managed Address Configuration      : disabled
Other Stateful Configuration       : disabled
Weak Host Sends                    : disabled
Weak Host Receives                 : disabled
Use Automatic Metric               : enabled
Ignore Default Routes              : disabled
Advertised Router Lifetime         : 1800 seconds
Advertise Default Route            : disabled
Current Hop Limit                  : 0
Force ARPND Wake up patterns       : disabled
Directed MAC Wake up patterns      : disabled
Link-Layer Address                 : 192.168.254.4
Remote Link-Layer Address          : 209.51.161.58



Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ---  ------------------------  ---  ------------------------
No       Manual    256  ::/0                       30  2001:470:1f06:3::1
No       Manual    256  ::/0                       30  IP6Tunnel
No       Manual    256  ::/0                       30  2001:470:4:c0::1
No       Manual    256  ::1/128                     1  Loopback Pseudo-Interface 1
No       Manual    256  2001:470:4:c0::/64         30  IP6Tunnel
No       Manual    256  2001:470:4:c0::2/128       30  IP6Tunnel
No       Manual    256  fe80::/64                  30  IP6Tunnel
No       Manual    256  fe80::/64                  11  Local Area Connection
No       Manual    256  fe80::/64                  14  Wireless Network Connection
No       Manual    256  fe80::/64                  29  Bluetooth Network Connection 2
No       Manual    256  fe80::/64                  16  Wireless Network Connection 2
No       Manual    256  fe80::5efe:192.168.254.4/128   31  isatap.Home
No       Manual    256  fe80::39e1:e3bc:493d:6038/128   30  IP6Tunnel
No       Manual    256  fe80::70ef:67cc:220b:c1f9/128   14  Wireless Network Connection
No       Manual    256  fe80::7186:9273:8716:fded/128   16  Wireless Network Connection 2
No       Manual    256  fe80::a94d:2c26:4978:fa1f/128   29  Bluetooth Network Connection 2
No       Manual    256  fe80::d532:8a1b:9a7:c687/128   11  Local Area Connection
No       Manual    256  ff00::/8                    1  Loopback Pseudo-Interface 1
No       Manual    256  ff00::/8                   30  IP6Tunnel
No       Manual    256  ff00::/8                   11  Local Area Connection
No       Manual    256  ff00::/8                   14  Wireless Network Connection
No       Manual    256  ff00::/8                   29  Bluetooth Network Connection 2
No       Manual    256  ff00::/8                   16  Wireless Network Connection 2
Title: Re: ipv6 readyness check
Post by: cholzhauer on January 20, 2014, 07:21:59 AM
Yeah I'm unable to ping your end point.

Assuming you did everything else correctly, your ISP must be blocking protocol 41.  Ask them and see what they say.
Title: Re: ipv6 readyness check
Post by: marke50 on January 21, 2014, 05:05:20 PM
All ports are open
Title: Re: ipv6 readyness check
Post by: broquea on January 21, 2014, 05:08:18 PM
protocol != port