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

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

Need Some Help

Started by flyinonice, December 26, 2012, 12:27:20 AM

Previous topic - Next topic

flyinonice

Hello all,
I am currently on Windows 7 Ultimate 64bit.  I signed up for a tunnel and can't seem to get it to work. I am behind a Belkin F5D8233-4v3 router with the ICMP ping block turned off.  The example config online showed the following items to be put into the command prompt, which I have already done (the 192.168.2.2 is my second attempt, the first attempt had my actual public IP not the one the router assigned me. Neither have worked):
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.2.2 66.220.18.42
netsh interface ipv6 add address IP6Tunnel 2001:470:c:2e1::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:c:2e1::1

Below is my ipconfig /all
Microsoft Windows [Version 6.1.7601]
  Host Name . . . . . . . . . . . . : John-THINK
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : Belkin

Ethernet adapter Local Area Connection* 17:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Juniper Network Connect Virtual Adapter
  Physical Address. . . . . . . . . : 00-FF-B0-5B-6A-06
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

  Connection-specific DNS Suffix  . : Belkin
  Description . . . . . . . . . . . : 1x1 11b/g/n Wireless LAN PCI Express Half
Mini Card Adapter
  Physical Address. . . . . . . . . : D0-DF-9A-72-D1-DE
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::a40e:4a55:1e9a:44ce%15(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : Wednesday, December 26, 2012 12:17:00 AM
  Lease Expires . . . . . . . . . . : Saturday, February 01, 2149 7:52:31 AM
  Default Gateway . . . . . . . . . : 192.168.2.1
  DHCP Server . . . . . . . . . . . : 192.168.2.1
  DHCPv6 IAID . . . . . . . . . . . : 382787482
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-C5-D3-23-F0-DE-F1-78-07-F5

  DNS Servers . . . . . . . . . . . : 192.168.2.1
  NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{62396AA6-B62A-4BC7-9DE0-80E150D3CF74}:

  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 isatap.Belkin:

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

Tunnel adapter IP6Tunnel:

  Connection-specific DNS Suffix  . : Belkin
  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:c:2e1::2(Preferred)
  Link-local IPv6 Address . . . . . : fe80::8da9:bea1:a5ee:af11%16(Preferred)
  Default Gateway . . . . . . . . . : 2001:470:c:2e1::1
  DNS Servers . . . . . . . . . . . : 192.168.2.1
  NetBIOS over Tcpip. . . . . . . . : Disabled

Below is my route print
===========================================================================
Interface List
25...00 ff b0 5b 6a 06 ......Juniper Network Connect Virtual Adapter
15...d0 df 9a 72 d1 de ......1x1 11b/g/n Wireless LAN PCI Express Half Mini
d Adapter
 1...........................Software Loopback Interface 1
26...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
27...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
16...00 00 00 00 00 00 00 e0 Microsoft Direct Point-to-point Adapater
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
         0.0.0.0          0.0.0.0      192.168.2.1      192.168.2.2     25
       127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
       127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
 127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
     169.254.0.0      255.255.0.0         On-link       192.168.2.2    306
 169.254.255.255  255.255.255.255         On-link       192.168.2.2    281
     192.168.2.0    255.255.255.0         On-link       192.168.2.2    281
     192.168.2.2  255.255.255.255         On-link       192.168.2.2    281
   192.168.2.255  255.255.255.255         On-link       192.168.2.2    281
       224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
       224.0.0.0        240.0.0.0         On-link       192.168.2.2    281
 255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
 255.255.255.255  255.255.255.255         On-link       192.168.2.2    281
===========================================================================
Persistent Routes:
 Network Address          Netmask  Gateway Address  Metric
     169.254.0.0      255.255.0.0     192.168.1.18       1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
16    286 ::/0                     2001:470:c:2e1::1
 1    306 ::1/128                  On-link
16    286 2001:470:c:2e1::/64      On-link
16    286 2001:470:c:2e1::2/128    On-link
15    281 fe80::/64                On-link
16    286 fe80::/64                On-link
16    286 fe80::8da9:bea1:a5ee:af11/128
                                   On-link
15    281 fe80::a40e:4a55:1e9a:44ce/128
                                   On-link
 1    306 ff00::/8                 On-link
15    281 ff00::/8                 On-link
16    286 ff00::/8                 On-link
===========================================================================
Persistent Routes:
If Metric Network Destination      Gateway
 0 4294967295 ::/0                     2001:470:c:2e1::1
===========================================================================

Is there anyway you all can help me get this going?  I am technical enough, but if you can in your responses tell me exactly what you want me to do.  I have read over some of the threads and gotten lost in the responses so I just wanted to put that out there now to limit confusion. I have already tried DMZ and it doesn't remedy the situation.

cholzhauer

your router is probably blocking protocol 41. To confirm/refute this, use something like wireshark and look for packets being sent to and from your dlink.

flyinonice

Ok, what specifically am I looking for in wireshark?  Do I need to try and visit an ipv6 website or should I see it regardless?

cholzhauer


that would work, but ping would be easier.  you need to look for the outbound packet and then look for the return packet being sent back to you

flyinonice

I didn't have any luck pinging an ipv6 site.  Below is my wireshark data for that period of time.  I will note that gogo6 allowed me to connect to ipv6 websites. Don't know if that means my router is capable and I just fudged up my setup somehow or it is a different way to handle the ipv6 websites, but I thought I would note it. I would prefer not to use that and get this setup.

cholzhauer

That's because gogo6 doesn't require your router to pass protool41

flyinonice

#6
Ok that makes sense.  So did the capture I attached help to figure out what is going on?

EDIT: I definitely don't know what to look for on my wireshark.  I pinged, it obviously didn't work, but beyond that I can't decipher how to determine it was protocol 41 as the culprit.