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

Problems with Tunnel (can anyone help??)

Started by dwalker85, May 31, 2013, 06:03:46 AM

Previous topic - Next topic

dwalker85

Hi Everyone,

I'm having problems trying to get the tunnel to work, here is my attempts;

When i could not get the tunnel working i tried gogo6 client at http://www.gogo6.com/freenet6

It setup with no problems & used IPv6-in-UDP-IPv4 Tunnel (NAT Traversal)

I could not tell if my router supports protocol 41

My Tunnel Details;

IPv6 Tunnel Endpoints
Server IPv4 Address:216.66.80.26
Server IPv6 Address:2001:470:1f08:8d1::1/64
Client IPv4 Address:176.24.194.38
Client IPv6 Address:2001:470:1f08:8d1::2/64
Routed IPv6 Prefixes
Routed /64:2001:470:1f09:8d1::/64


I first ran the following on my pc (Winxp)

ipv6 install
ipv6 rtu ::/0 2/::216.66.80.26 pub
ipv6 adu 2/2001:470:1f08:8d1::2


Then i tried

netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.0.5 216.66.80.26
netsh interface ipv6 add address IP6Tunnel 2001:470:1f08:8d1::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f08:8d1::1


After that i tried

netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.0.5 216.66.80.26
netsh interface ipv6 add address IP6Tunnel 2001:470:1f08:8d1::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f08:8d1::1
netsh interface ipv6>add route 2001:470:1f09:8d1::/64 Local Area Connection publish=yes


I then ran show route

C:\Documents and Settings\david>netsh interface ipv6 show route
Querying active state...

Publish  Type       Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ----  ------------------------  ---  ---------------------
no       Manual       1  ::/0                        7  2001:470:1f08:8d1::1
yes      Manual       1  ::/0                        2  ::216.66.80.26
no       Autoconf    10  2001::/32                   6  Teredo Tunneling Pseudo-Interface


Then show interface

C:\Documents and Settings\david>netsh interface ipv6 show interface
Querying active state...

Idx  Met   MTU    State         Name
---  ----  -----  ------------  -----
  7     1   1280  Connected     IP6Tunnel
  6     2   1280  Connected     Teredo Tunneling Pseudo-Interface
  5     0   1280  Disconnected  Local Area Connection 4
  4     0   1500  Connected     Local Area Connection
  3     1   1280  Connected     6to4 Pseudo-Interface
  2     1   1280  Connected     Automatic Tunneling Pseudo-Interface
  1     0   1500  Connected     Loopback Pseudo-Interface


Then i tried to ping ipv6.google.com it said timed out or unreachable

C:\Documents and Settings\david>ping -6 ipv6.google.com

Pinging ipv6.l.google.com [2a00:1450:400c:c03::63] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2a00:1450:400c:c03::63:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


I then fired up GoGo Client running as IPv6-in-UDP-IPv4 Tunnel (NAT Traversal) as tried to ping ipv6.google.com again

C:\Documents and Settings\david>ping -6 ipv6.google.com

Pinging ipv6.l.google.com [2a00:1450:400c:c03::63] with 32 bytes of data:

Reply from 2a00:1450:400c:c03::63: time=185ms
Reply from 2a00:1450:400c:c03::63: time=299ms
Reply from 2a00:1450:400c:c03::63: time=212ms
Reply from 2a00:1450:400c:c03::63: time=157ms

Ping statistics for 2a00:1450:400c:c03::63:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 157ms, Maximum = 299ms, Average = 213ms


It works with GoGo client without any router changes

I would like to try & get the he tunnel to work if possible

Can anyone possibly help me please??

Thanks in advance

David

snarked

Where are you telling the device that does your IPv4 NAT to deliver the protocol 41 packets to your machine ending in ".5"?

dwalker85

I am entering 192.168.0.5 in the DMZ of my router but it does not seem to make any difference

David

cholzhauer

Quote from: dwalker85 on June 01, 2013, 01:48:02 AM
I am entering 192.168.0.5 in the DMZ of my router but it does not seem to make any difference


Sometimes, depending on the router, that doesn't do anything.

You should fire up something like wireshark and look to see what's happening when your tunnel isn't working.  If you don't see return proto41 packets, you'll know that's your issue.

What router do you have?


dwalker85

Hi cholzhauer,

My router is a sky sr1001 (sky uk broadcaster/broadband provider)

I have wireshank installed how will i know what are the proto41 packets?

David

cholzhauer


dwalker85

Thanks cholzhauer,

Will now run wireshark & let you know the outcome

David

dwalker85

I have run wireshark with ip6 tunnel & see this message often;

icmp  Destination unreachable (port unreachable)

I do not see any thing about protocol 41

Show interface


C:\Documents and Settings\david>netsh interface ipv6 show interface
Querying active state...

Idx  Met   MTU    State         Name
---  ----  -----  ------------  -----
  7     1   1280  Connected     IP6Tunnel
  6     2   1280  Disconnected  Teredo Tunneling Pseudo-Interface
  5     0   1280  Disconnected  Local Area Connection 4
  4     0   1500  Connected     Local Area Connection
  3     1   1280  Connected     6to4 Pseudo-Interface
  2     1   1280  Connected     Automatic Tunneling Pseudo-Interface
  1     0   1500  Connected     Loopback Pseudo-Interface


Ping

C:\Documents and Settings\david>ping -6 ipv6.google.com

Pinging ipv6.l.google.com [2a00:1450:400c:c00::6a] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2a00:1450:400c:c00::6a:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


Show Route

C:\Documents and Settings\david>netsh interface ipv6 show route
Querying active state...

Publish  Type       Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ----  ------------------------  ---  ---------------------
yes      Manual       0  2001:470:1f09:8d1::/64      4  Local Area Connection
yes      Manual       1  ::/0                        7  2001:470:1f08:8d1::1


IPConfig

C:\Documents and Settings\david>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : Home
        IP Address. . . . . . . . . . . . : 192.168.0.5
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : 2001:470:1f09:8d1:648e:85a6:937:e932

        IP Address. . . . . . . . . . . . : 2001:470:1f09:8d1:216:76ff:fe2c:b8f7

        IP Address. . . . . . . . . . . . : 2001:470:1f08:8d1::1
        IP Address. . . . . . . . . . . . : fe80::216:76ff:fe2c:b8f7%4
        Default Gateway . . . . . . . . . : 192.168.0.1

Ethernet adapter Local Area Connection 4:

        Media State . . . . . . . . . . . : Media disconnected

Tunnel adapter IP6Tunnel:

        Connection-specific DNS Suffix  . : Home
        IP Address. . . . . . . . . . . . : 2001:470:1f08:8d1::2
        IP Address. . . . . . . . . . . . : fe80::7:c0a8:5%7
        Default Gateway . . . . . . . . . : 2001:470:1f08:8d1::1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%6
        Default Gateway . . . . . . . . . :

Tunnel adapter Automatic Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . : Home
        IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.5%2
        Default Gateway . . . . . . . . . :



So does this mean my router does not support Protocol 41 or is there any more tests i could run.

Could i forward the port(s) for the tunnel to get round the problem??

David

cholzhauer

Remember, port =! protocol...forwarding ports won't help anything.

You should be seeing some protocol41 traffic...you should be seeing the traffic generated by your computer.  I have to assume that your router doesn't support protocol41, but I can't say for sure.

Why don't you try with an OS that isn't ten years old?

dwalker85

Hi,

Thanks Cholzhauer,

I did see traffic generated by my computer, but i did not see anything saying protocol 41 or IP6Tunnel

My 2 pc's are still running windows xp (yes i know it is obsolete & old) , so i would say my router does not support protocol 41 (the router was only released Jan 2013)

That would explain why IPv6-in-UDP-IPv4 Tunnel (NAT Traversal) from gogo6 works as it does not rely on the  router supporting protocol 41, but works on udp ports i think??

David