Windows 7 64bit, Media disconnected, not even pings

[artlav]

Hello.

I've tried to set up the tunnel service by HE, but had no luck so far.

The tunnel adapter always shows Media disconnected, i suppose that's not correct?
Pinging local IP6s work, but not the IP6 the HE gave me as the other end of the tunnel and gateway.

Obviously, no IP6 addresses are accessible.

My ISP is IPv6 aware, and i don't think they block protocol 41 (but it can be blocked somewhere way upstream "just in case" due to retadedness of local business practices. Is there any kind of a way to check? Google does not help much).
There are no routers on my part of the cable, only a hab.
I have a static external IP that can be used to access any service i set on the this system, and which is my endpoint on this side.

What can be wrong?


The stats:

Commands used, with several permutations after clean resets:

Code Select Expand


netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 91.206.***.*** 216.66.80.26
netsh interface ipv6 add address interface=IP6Tunnel 2001:470:1f08:143e::2
netsh interface ipv6 add route ::/0 interface=IP6Tunnel 2001:470:1f08:143e::1


ipconfig /all:

Code Select Expand


Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : kurkino.net.ru
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 00-50-22-E1-07-E0
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:1f09:143e::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::7570:5312:aa9e:7b84%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.0.92.34(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 4 февраля 2011 г. 13:18:57
   Lease Expires . . . . . . . . . . : 11 февраля 2011 г. 13:18:56
   Default Gateway . . . . . . . . . : 2001:470:1f08:143e::1
                                       10.0.92.1
   DHCP Server . . . . . . . . . . . : 127.0.0.1
   DHCPv6 IAID . . . . . . . . . . . : 244377274
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-7E-02-D5-90-E6-BA-15-36-E7

   DNS Servers . . . . . . . . . . . : 91.206.14.254
                                       91.206.15.254
                                       91.206.14.6
   NetBIOS over Tcpip. . . . . . . . : Enabled

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


route print:

Code Select Expand


===========================================================================
Interface List
11...00 50 22 e1 07 e0 ......Realtek PCIe GBE Family Controller
  1...........................Software Loopback Interface 1
18...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        10.0.92.1       10.0.92.34     20
         10.0.0.0        255.0.0.0        10.0.92.2       10.0.92.34     21
        10.0.92.0    255.255.255.0         On-link        10.0.92.34    276
       10.0.92.34  255.255.255.255         On-link        10.0.92.34    276
      10.0.92.255  255.255.255.255         On-link        10.0.92.34    276
       81.19.85.0    255.255.255.0        10.0.92.2       10.0.92.34     21
      91.206.14.0  255.255.255.192        10.0.92.2       10.0.92.34     21
        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        10.0.92.34     30
  169.254.255.255  255.255.255.255         On-link        10.0.92.34    276
     192.168.56.0    255.255.255.0         On-link      192.168.56.1    276
     192.168.56.1  255.255.255.255         On-link      192.168.56.1    276
   192.168.56.255  255.255.255.255         On-link      192.168.56.1    276
        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.56.1    276
        224.0.0.0        240.0.0.0         On-link        10.0.92.34    276
  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.56.1    276
  255.255.255.255  255.255.255.255         On-link        10.0.92.34    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
11    276 ::/0                     2001:470:1f08:143e::1
  1    306 ::1/128                  On-link
11    276 2001:470:1f09:143e::/64  On-link
11    276 2001:470:1f09:143e::2/128
                                    On-link
17    276 fe80::/64                On-link
11    276 fe80::/64                On-link
17    276 fe80::20:a2ba:9532:e321/128
                                    On-link
11    276 fe80::7570:5312:aa9e:7b84/128
                                    On-link
  1    306 ff00::/8                 On-link
17    276 ff00::/8                 On-link
11    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None


ping 2001:470:1f08:143e::1 does not reply.

Code Select Expand


Pinging 2001:470:1f08:143e::1 with 32 bytes of data:
Destination host unreachable.


[cholzhauer]

Because you didn't use your 10.x address to create the tunnel

Change your 91.206.x to 10.x

[artlav]

>>Because you didn't use your 10.x address to create the tunnel

Hm? That's a private network IP, the HE system won't even allow it.

[cholzhauer]

There's two different spots. 

On the HE website, you need to use your public address, whatever it is.

When you did this...

Code Select Expand


netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 91.206.***.*** 216.66.80.26
netsh interface ipv6 add address interface=IP6Tunnel 2001:470:1f08:143e::2
netsh interface ipv6 add route ::/0 interface=IP6Tunnel 2001:470:1f08:143e::1


You need to do this

Code Select Expand


netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 10.0.92.34 216.66.80.26
netsh interface ipv6 add address interface=IP6Tunnel 2001:470:1f08:143e::2
netsh interface ipv6 add route ::/0 interface=IP6Tunnel 2001:470:1f08:143e::1


Because you're behind a NAT device.

[artlav]

Okay, i removed it and tried with
netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 10.0.92.1 216.66.80.26
netsh interface ipv6 add address interface=IP6Tunnel 2001:470:1f08:143e::2

But there is no appreciable effect, it won't ping 2001:470:1f08:143e::1 still.

[artlav]

Oops, wrong address.
With netsh interface ipv6 add v6v4tunnel interface=IP6Tunnel 10.0.92.34 216.66.80.26 it seems to work!

[artlav]

Ok, i clean and reset later everything works, i can get to ipv6.google.
Thank you for help.

Why are these details not described in a FAQ or guidelines?
Or, have i missed them?

[cholzhauer]

They are, you missed them ;)

*NOTE* When behind a firewall appliance that passes protocol41, instead of using the IPv4 endpoint you provided to our broker, use the IPv4 address you get from your appliance's DHCP service.

This is below the commands you copied and pasted off the tunnel broker page

[artlav]

They are...
I guess "firewall appliance" didn't resolve into "ISP's NAT".

[artlav]

One more thing - whatever address i set, http://ipv6.whatismyipv6.com gives me 2001:470:1f08:143e::2 as mi IP6.
Is that normal?

[cholzhauer]

Did you leave that other address set on your LAN connection?  It should show whatever IP is on your LAN connection, but I can't say for sure because I don't use Windows as my tunnel router

Well, I take that back.  If I ping something from my tunnel router, the ping starts from my ::2 address even though I've assigned an IPv6 address to my Ethernet adapter.

So I'll say yes, that's normal.

You should keep the address assigned to your LAN connection though so you can route other traffic