Print

[micro]

I am currently having issue with setting up a IPv6 tunnel on my Windows Server 2008 box, using the example configurations provided on the website. When I attempt to ping a IPv6 address 2001:4860:4860::8888 (Google DNS server), it always timeout. I have already tried to troubleshoot the issue myself for a several days without any real results. Really hope if you guys could help me out here...

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Haruna
   Primary Dns Suffix  . . . . . . . : kekesoft.org
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : kekesoft.org

PPP adapter RAS (Dial In) Interface:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : RAS (Dial In) Interface
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.2.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 320113696
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-9A-22-BD-00-50-56-02-E7-BB

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
   Physical Address. . . . . . . . . : 00-50-56-02-E7-BB
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 94.23.153.225(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . : 176.31.247.254
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter IP6Tunnel:

   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
   IPv6 Address. . . . . . . . . . . : 2001:470:1f12:65::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::8d61:d41a:6cd:841f%12(Preferred)
   Default Gateway . . . . . . . . . : 2001:470:1f12:65::1
   DNS Servers . . . . . . . . . . . : 8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Administrator>route print
===========================================================================
Interface List
 19...........................RAS (Dial In) Interface
 11...00 50 56 02 e7 bb ......Intel(R) PRO/1000 MT Network Connection
  1...........................Software Loopback Interface 1
 12...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   176.31.247.254    94.23.153.225    266
    94.23.153.225  255.255.255.255         On-link     94.23.153.225    266
        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
    192.168.2.100  255.255.255.255         On-link     192.168.2.100    306
        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     94.23.153.225    266
        224.0.0.0        240.0.0.0         On-link     192.168.2.100    306
  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     94.23.153.225    266
  255.255.255.255  255.255.255.255         On-link     192.168.2.100    306
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0   176.31.247.254  Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 12    356 ::/0                     2001:470:1f12:65::1
  1    306 ::1/128                  On-link
 12    356 2001:470:1f12:65::/64    On-link
 12    356 2001:470:1f12:65::2/128  On-link
 12   1100 2002::/16                On-link
 12    356 fe80::/64                On-link
 12    356 fe80::8d61:d41a:6cd:841f/128
                                    On-link
  1    306 ff00::/8                 On-link
 19    306 ff00::/8                 On-link
 12    356 ff00::/8                 On-link
===========================================================================
Persistent Routes:
 If Metric Network Destination      Gateway
  0 4294967295 ::/0                     2001:470:1f12:65::1
===========================================================================

netsh interface ipv6>show inter

Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
  1          50  4294967295  connected     Loopback Pseudo-Interface 1
 19          50        1400  connected     RAS (Dial In) Interface
 12         100        1280  connected     IP6Tunnel

netsh interface ipv6>show addresses

Interface 1: Loopback Pseudo-Interface 1

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Other      Preferred     infinite   infinite ::1

Interface 12: IP6Tunnel

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Manual     Preferred     infinite   infinite 2001:470:1f12:65::2
Other      Preferred     infinite   infinite fe80::8d61:d41a:6cd:841f%12

netsh interface ipv6>show interfaces

Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
  1          50  4294967295  connected     Loopback Pseudo-Interface 1
 19          50        1400  connected     RAS (Dial In) Interface
 12         100        1280  connected     IP6Tunnel

netsh interface ipv6>show route

Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ---  ------------------------  ---  ------------------------
No       Manual    256  ::/0                       12  2001:470:1f12:65::1
No       Manual    256  ::1/128                     1  Loopback Pseudo-Interface
 1
No       Manual    256  2001:470:1f12:65::/64      12  IP6Tunnel
No       Manual    256  2001:470:1f12:65::2/128    12  IP6Tunnel
Yes      Manual    1000  2002::/16                  12  IP6Tunnel
No       Manual    256  fe80::/64                  12  IP6Tunnel
No       Manual    256  fe80::8d61:d41a:6cd:841f/128   12  IP6Tunnel
No       Manual    256  ff00::/8                    1  Loopback Pseudo-Interface
 1
No       Manual    256  ff00::/8                   19  RAS (Dial In) Interface
No       Manual    256  ff00::/8                   12  IP6Tunnel

[cholzhauer]

There isn't any mention of IPv6 for your LAN connection...is IPv6 enabled on it?

[micro]

There isn't any mention of IPv6 for your LAN connection...is IPv6 enabled on it?

It was disabled, since I am expecting IPv6 packets would use the HE IPv6 Tunnel, not the LAN interface. It is now enabled on the LAN interface, but it didn't make any difference.

[cholzhauer]

I don't think your tunnel is up

Code: [Select]

C:\Users\cholzhauer>ping 2001:470:1f12:65::2

Pinging 2001:470:1f12:65::2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2001:470:1f12:65::2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\cholzhauer>


[micro]

I don't think your tunnel is up

Code: [Select]

C:\Users\cholzhauer>ping 2001:470:1f12:65::2

Pinging 2001:470:1f12:65::2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2001:470:1f12:65::2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\cholzhauer>


I know, that's the whole point...

[cholzhauer]

Are you behind a firewall that's blocking protocol 41? Is your ISP blocking protocol41?

[micro]

Might as well upload this.

[micro]

Are you behind a firewall that's blocking protocol 41? Is your ISP blocking protocol41?

In order to troubleshoot the issue I have already disabled the firewall completely. And I highly doubt ISP is blocking anything, since it is dedicated box hosted by OVH.

[micro]

When I was capturing packets on Wireshark while I was pinging the Google website, I noticed something really odd. There were no packets going to the far-end tunnel endpoint at all.

[cholzhauer]

I think you have the wrong filter...you're filtering on port, not protocol

[micro]

I think you have the wrong filter...you're filtering on port, not protocol

Even if the port filters are wrong, the ip.addr filter should capture have got the tunneling packets anyway.