Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: I can't get my regular tunnel to work  (Read 6239 times)

GoldVision

  • Newbie
  • *
  • Posts: 2
I can't get my regular tunnel to work
« on: March 30, 2012, 04:29:06 AM »

I've created a regular tunnel and implemented the necessary configuration through the command line but i can't get it to work.
I've deleted my IP6Tunnel interface many times and applied the config again, applied ipconfig /release & renew but it doesnt seem to do the trick.

This is the configuration i've used:

netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.50.100 216.66.84.46
netsh interface ipv6 add address IP6Tunnel 2001:470:1f14:4f4::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f14:4f4::1


cmd output:

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::591b:8d67:a09c:109e%11
   IPv4 Address. . . . . . . . . . . : 192.168.50.100
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.50.1

Tunnel adapter isatap.{031BFA84-A3AC-4126-8AF9-1EA2F5D5E2F3}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter IP6Tunnel:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:470:1f14:4f4::2
   Link-local IPv6 Address . . . . . : fe80::81c7:7616:259e:543a%17
   Default Gateway . . . . . . . . . : 2001:470:1f14:4f4::1



I have no clue what im doing wrong.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: I can't get my regular tunnel to work
« Reply #1 on: March 30, 2012, 05:14:07 AM »

You're behind NAT...is your router/firewall passing protocol 41 traffic?
Logged

GoldVision

  • Newbie
  • *
  • Posts: 2
Re: I can't get my regular tunnel to work
« Reply #2 on: March 30, 2012, 08:51:34 AM »

My router doesnt have a built-in firewall for as far as i know.
its a sweex 54G wireless broadband router, as far as i know it doesnt have any ipv6 configurable options.
I wouldnt know if its forwarding port 41 traffic, im guessing this isnt the case by default?

What do i need to do to make this happen?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2732
Re: I can't get my regular tunnel to work
« Reply #3 on: March 30, 2012, 09:54:33 AM »

Not port, protocol

Port != protocol

Ask Google.  Something is doing NAT translation for you....whatever that something is needs to pass protocol41
Logged

kasperd

  • Founder, Netiter ApS
  • Hero Member
  • *****
  • Posts: 964
Re: I can't get my regular tunnel to work
« Reply #4 on: March 30, 2012, 03:02:26 PM »

As already mentioned, check the NAT settings. In addition to that check that the tunnel configuration on the HE end points to your public IPv4 address.

Once you have checked those two things, I suggest you try running tcpdump or wireshark on the physical interface while you try to ping 2001:470:20::2.
Logged

fbroillet

  • Newbie
  • *
  • Posts: 1
Re: I can't get my regular tunnel to work
« Reply #5 on: April 01, 2012, 10:02:14 AM »

Hi all,

Sorry but I have also some difficulties to make my v6v4 tunnel correctly working.

I send the following commands:

netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 82.220.1.199 216.66.80.98
netsh interface ipv6 add address IP6Tunnel 2001:470:25:794::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:25:794::1

Finally here output of my ipconfig /all:

C:\Users\fbr.EB-QUAL>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : IBMFBR
   Primary Dns Suffix  . . . . . . . : eb-qual.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : eb-lab.local

Ethernet adapter Local Area Connection* 17:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Juniper Network Connect Virtual Adapter
   Physical Address. . . . . . . . . : 00-FF-68-09-BD-88
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Mobile Broadband adapter Mobile Broadband Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : F3507g Mobile Broadband Driver
   Physical Address. . . . . . . . . : 02-80-37-EC-02-00
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82567LM Gigabit Network Connection
   Physical Address. . . . . . . . . : 00-24-7E-E0-47-F7
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
   Physical Address. . . . . . . . . : 00-21-6A-82-73-D9
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : 0C-60-76-86-CB-1E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) WiFi Link 5300 AGN
   Physical Address. . . . . . . . . : 00-21-6A-82-73-D8
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::9940:794e:3dd1:920d%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.39(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : dimanche 1 avril 2012 09:18:22
   Lease Expires . . . . . . . . . . : lundi 2 avril 2012 09:18:21
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 218112362
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-AB-46-F0-00-24-7E-E0-47-F7
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{429F089A-A352-46FA-B14C-7BA3A5F7F60E}:

   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.{D3314152-0DFF-4E1E-A051-2F37026418DD}:

   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

Tunnel adapter isatap.{7A22FEBB-9C85-43E1-8F0D-452F46C3F4F8}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   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.{C473E0FF-3E3E-4E8D-9C0F-045FF54D17F0}:

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

Tunnel adapter isatap.{C507E263-AF92-41E0-9EFC-0D3DF807EB91}:

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

Tunnel adapter isatap.{79A92F47-59F9-4106-852C-DD5EA032A341}:

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


Is it also related to NAT ? I tried to forward TCP Port 41 to my laptop on my DSL Router ... no success

I'm using both Wireless and wired interfaces (at home & in the office).

Thanks for your help

Have a nice day

Cheers

Fabien
« Last Edit: April 01, 2012, 12:26:39 PM by fbroillet »
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1735
Re: I can't get my regular tunnel to work
« Reply #6 on: April 01, 2012, 12:31:55 PM »

Read the note under the example config that you copy and pasted on the broker's site, it'll save you time.
Quote
NOTE: When behind a firewall appliance that passes protocol 41, use the IPv4 address you get from your appliance's DHCP service instead of the IPv4 endpoint you provided to our broker.

change
Code: [Select]
netsh interface ipv6 add v6v4tunnel IP6Tunnel 82.220.1.199 216.66.80.98
to
Code: [Select]
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.1.39 216.66.80.98
Forwarding TCP/UDP ports has NOTHING to do with Protocol 41
« Last Edit: April 01, 2012, 02:16:40 PM by broquea »
Logged