Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Windows 7 x64 & tunnelbroker  (Read 12807 times)

fcpk

  • Newbie
  • *
  • Posts: 3
Windows 7 x64 & tunnelbroker
« on: April 26, 2011, 02:55:30 PM »

Can't seem to get it to work:
The netsh commands run successfully but the interface stays at:
Tunnel adapter IP6Tunnel:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Any ideas? I know the tunnel can work since my linux vm can use it fine, so protocol 41 does go through.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2699
Re: Windows 7 x64 & tunnelbroker
« Reply #1 on: April 26, 2011, 03:07:06 PM »

can you post the commands you used and the output of ipconfig /all please?
Logged

fcpk

  • Newbie
  • *
  • Posts: 3
Re: Windows 7 x64 & tunnelbroker
« Reply #2 on: April 26, 2011, 03:11:17 PM »

To set it:
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 89.101.178.26 216.66.80.26
netsh interface ipv6 add address IP6Tunnel 2001:470:1f08:181a::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f08:181a::1

C:\Users\DeathWolf>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Natsuki
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : chello.ie

Ethernet adapter Local Area Connection 4:

   Connection-specific DNS Suffix  . : chello.ie
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 1C-6F-65-3F-85-EA
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2002:5965:b21a:0:f9ba:dff6:bc90:c7a3(Preferred)
   Temporary IPv6 Address. . . . . . : 2002:5965:b21a:0:61e7:74c6:c829:8b2f(Preferred)
   Link-local IPv6 Address . . . . . : fe80::f9ba:dff6:bc90:c7a3%20(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.101(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : April 26, 2011 02:45:27
   Lease Expires . . . . . . . . . . : April 27, 2011 21:58:28
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
   Physical Address. . . . . . . . . : 00-50-56-C0-00-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f0b5:fa85:4ad5:3834%16(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.10.10.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 352342102
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-67-75-3F-90-E6-BA-F0-52-A3
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.WRVS4400Nv2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter IP6Tunnel:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Direct Point-to-point Adapater
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{1A6A3D1E-05D1-44D8-9585-095273743FCD}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2699
Re: Windows 7 x64 & tunnelbroker
« Reply #3 on: April 26, 2011, 03:18:03 PM »

the two things that jump out at me are that you need to substitute your nat address for the public address in the commands that he gave you and you also need to get rid of the 6to4 address you have assigned and use an address from your routed /64
Logged

fcpk

  • Newbie
  • *
  • Posts: 3
Re: Windows 7 x64 & tunnelbroker
« Reply #4 on: April 26, 2011, 03:35:03 PM »

netsh interface ipv6 del address IP6Tunnel 2001:470:1f08:181a::2
netsh interface ipv6 del route ::/0 IP6Tunnel 2001:470:1f08:181a::1
netsh interface ipv6 delete interface IP6Tunnel
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.1.101 216.66.80.26
netsh interface ipv6 add address IP6Tunnel 2001:470:1f08:181a::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f08:181a::1

and then assigned 2001:470:1f08:181a::3 to the 192.168.1.101 interface;) and it works perfectly! thanks!
Logged

ingber

  • Lester Ingber
  • Newbie
  • *
  • Posts: 9
  • Lester Ingber
    • Lester Ingber's Archive
Re: Windows 7 x64 & tunnelbroker
« Reply #5 on: May 28, 2011, 08:03:42 AM »

Hi.  Could you give the specific netsh command you used to
"and then assigned 2001:470:1f08:181a::32001:470:1f08:181a::3 to the 192.168.1.101 interface;)" ?
Do you mean that you essentially set 2001:470:1f08:181a::3 as a gateway in the 192.168.1.101 network adapter under the Advanced tab?

I assume then, starting just after the tunnelbroker tunnel is created to your router, you would issue?:
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.1.101 216.66.80.26
netsh interface ipv6 add address IP6Tunnel 2001:470:1f08:181a::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f08:181a::1
netsh interface ... (the above command)

I too have a set of netsh commands given after my tunnel was created, on my Win7 Ultimate x64 PC, which I have not yet issued as I'm concerned about how to reset this if I wanted to later.

I assume that, with more than 1 PC on the router, the local address (I have static private ipv4 addresses for all PC's)
the 2 netsh commands with 192.168.1.101 would be run with these different private addresses?  I.e., there should be no problem with multiple PCs using the same tunnel?

Right now, on my D-Link DIR-825 router, I can ping ipv6.google.com just fine, but cannot access that site from my WIn7 (chrome) browser.   (On a remote Linode VPS, which has true ipv6 running, I can access that site just fine.)

Thanks.

Lester
« Last Edit: May 28, 2011, 11:11:42 AM by ingber »
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2699
Re: Windows 7 x64 & tunnelbroker
« Reply #6 on: May 28, 2011, 07:27:01 PM »

To add an address to an interface you just do a

Code: [Select]
netsh interface ipv6 add address IP6Tunnel 2001:470:1f08:181a::2

And change IP6 tunnel to the interface you want

Quote
I assume that, with more than 1 PC on the router, the local address (I have static private ipv4 addresses for all PC's)
the 2 netsh commands with 192.168.1.101 would be run with these different private addresses?  I.e., there should be no problem with multiple PCs using the same tunnel?

I'm sort of confused by this.  You can use Router Advertisements or DHCP to assign addresses for multiple computers.

Oh, fcpk, you shouldn't use that ::3 address you did.  It may work, but HE doesn't delegate DNS for those addresses (because it's part of your tunnel /64)  You should pull an address from your routed /64 (check your tunnel page for details) and use that
Logged

ingber

  • Lester Ingber
  • Newbie
  • *
  • Posts: 9
  • Lester Ingber
    • Lester Ingber's Archive
Re: Windows 7 x64 & tunnelbroker
« Reply #7 on: May 29, 2011, 08:22:29 AM »

cholzhauer:

Yes, this seems to work.  That is, from two PCs behind the router I now can reach http://ipv6.google.com .  I didn't understand why there would be a 5th netsh command; apparently there is not, as the command you cited,
netsh interface ipv6 add address IP6Tunnel 2001:470:1f08:181a::2
was already included in fcpk's first post.

I notice that http://test-ipv6.com gives me the same report as before I had this tunnel:
10/10   for your IPv4 stability and readiness, when publishers offer both IPv4 and IPv6
0/10   for your IPv6 stability and readiness, when publishers are forced to go IPv6 only
I guess that is expected since I am using a tunnel?  I am using OpenDNS ipv6 name servers
2620:0:ccc::2
2620:0:ccd::2
Are these OK, or should I use (only) the one provided by tunnelbroker
2001:470:20::2

I have a query on the addresses assigned to me by tunnelbroker.   The address I used in my netsh commands, which seem to work, is under the section IPv6 Tunnel Endpoints.  There is another (assign /48) address under the section Routed IPv6 Prefixes, which I assume is just for my information, not used in any of my settings?

My Client IPv4 Address is assigned DHCP by my ISP.  (I understand that the instructions that work require my local private IPv4 address in the 2nd netsh command.)  That usually stays for quite a awhile, but when that changes, I assume my tunnelbroker setting must also be changed.  There is a page pointed to by a popup,
https://ipv4.tunnelbroker.net/ipv4_end.php
that has the info
Usage: https://ipv4.tunnelbroker.net/ipv4_end.php?ip=IPV4ADDR&pass=MD5PASS&apikey=USERID&tid=TUNNELID
 -or-: https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID (auto-detect IP)
       https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID&ip=IPV4ADDR
Is this the method I would use to change the IPS IPv4 address when they change it?

Is there any other service that can do this automatically?  For example, I use OpenDNS's client software that automatically updates my ISP IPv4 address.  Or, do you suggest some other command line to run the above https address/command on some schedule?

Thanks.

Lester
« Last Edit: May 29, 2011, 08:33:43 AM by ingber »
Logged

ingber

  • Lester Ingber
  • Newbie
  • *
  • Posts: 9
  • Lester Ingber
    • Lester Ingber's Archive
Re: Windows 7 x64 & tunnelbroker
« Reply #8 on: May 29, 2011, 02:13:08 PM »

P.S.

I have written a scheduled script that polls http://myip.dnsomatic.com/ and only then uses `elinks -dump "https://ipv4.tunnelbroker.net/ipv4_end.php?ip=AUTO&...` if the ISPs IPv4 address changes.  It would be nice if this could be set with the OpenDNS client, but that is not available at this time.

I guess the ipv6 connection can be slow and not available quickly at times; there was a Linode post on some cases.  Right now, http://test-ipv6.com and http://testipv6.com both report 10/10 for both ipv4 and ipv6 stability.

I cannot the md5sum form of the https ISP ipv4 address to work,
https://ipv4.tunnelbroker.net/ipv4_end.php?ip=AUTO&pass=MD5PASS&apikey=USERID&tid=TUNNELID
but the second form works OK
https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID&ip=AUTO

Lester
« Last Edit: May 29, 2011, 02:57:23 PM by ingber »
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2699
Re: Windows 7 x64 & tunnelbroker
« Reply #9 on: May 30, 2011, 06:30:25 AM »

As long as OpenDNS does IPv6 lookups, they'll work fine

You don't need the /48 unless you have multiple subnets to cover.
Logged