• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

Strange IPv6 issue that WON'T GO AWAY.

Started by MeStinkBAD, June 01, 2010, 08:10:05 PM

Previous topic - Next topic

MeStinkBAD

I have an Airport Extreme (w/ IPv6 support). I have Cox HSI which includes an automatic tunnel configuration. And it works great!

IPv6 for Windows worked rather well too for a good many months... then BOOM I notice IPv6 not working. I go to investigate. I swear Windows is now trying to make a 6to6to4 tunnel. Well there is no such thing so obviously I'm nuts or Windows is crazy!

I'll show you the ipconfig info below.
Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . : ph.cox.net
       Description . . . . . . . . . . . : Intel(R) PRO/1000 EB Network Connection with I/O Acceleration #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00
       Dhcp Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IP Address. . . . . . . . . . . . : 10.0.1.111
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IP Address. . . . . . . . . . . . : 2002:44e2:1771:0:58fa:9d8e:1300:4863
       IP Address. . . . . . . . . . . . : 2002:44e2:1771:0:217:f2ff:fe05:c58d
       IP Address. . . . . . . . . . . . : ::58fa:9d8e:1300:4863                                  
       IP Address. . . . . . . . . . . . : ::217:f2ff:fe05:c58d
       IP Address. . . . . . . . . . . . : fe80::217:f2ff:fe05:c58d%4
       Default Gateway . . . . . . . . . : 10.0.1.1
                                           fe80::224:36ff:fe9e:9cc8%4
                                           fe80::223:12ff:fef8:9b15%4
       DHCP Server . . . . . . . . . . . : 10.0.1.1
       DNS Servers . . . . . . . . . . . : 10.0.1.1
                                           fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       Primary WINS Server . . . . . . . : 192.168.100.1
       Lease Obtained. . . . . . . . . . : Tuesday, June 01, 2010 12:06:01 PM
       Lease Expires . . . . . . . . . . : Tuesday, June 08, 2010 12:06:01 PM


The two IP addresses..
       IP Address. . . . . . . . . . . . : 2002:44e2:1771:0:58fa:9d8e:1300:4863
       IP Address. . . . . . . . . . . . : ::58fa:9d8e:1300:4863


Shouldn't be there.  They weren't there before when it worked. What is going on?

jimb

#1
Make sure your airport isn't doing some sort of 6to4 thing.  I think Windows will also try to do 6to4 under certain conditions (not really sure what those are though).

You can make sure it's turned off in windows by doing: netsh int ipv6 6to4 set state=disabled

It'd also help to see the output of these commands:

netsh int ipv6 show routes
netsh int ipv6 show addr level=verbose

cholzhauer

Quote
You can make sure it's turned off in windows by doing: netsh int ipv6 6to4 set state=disabled

You may need to drop the equals sign, so it looks like


netsh int ipv6 6to4 set state disabled