can't access IPv6 internet :(

[SUSTipv6]

Hi
iam trying to create Tunnel from my windows 7 machine to H.E, I followed the configuration given but nothing work.
>>>>>
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 196.1.209.105 216.66.84.42
netsh interface ipv6 add address IP6Tunnel 2001:470:1f12:4c7::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:1f12:4c7::1

>>>>>
notices that am not using the global IPv4 address 196.1.209.105 directly, my PC under NAT so and am using 172.27.150.201 IPv4 that referenced to the global IPv4.

please heeeeeelp :((

[cholzhauer]

If you're behind a NAT, you need to use your NAT address to make the tunnel.  So, change your 196 address to your 172 address and try again

[SUSTipv6]

thanks cholzhauer for replay
but i already did this and used the 172 address as source address for the tunnel. but still nothing works.

is there is any issues for my being behind the NAT, or would you please show my an example of doing the configuration on windows 7 for my case???

thanks man :)

[cholzhauer]

you have the correct commands, but you HAVE to use the 172 address..forget all about the 196 address for now.

Is your firewall passing protocol 41 traffic to you?  If it's not, you need to make it.  Unfortunately, I do not know of a way to test if it is or not.

When you say "nothing works" what do you mean? What did you try and do after running those commands?

[SUSTipv6]

172 had been forgotten  :)

OK , i did tried to ping the ipv6 address of the other part of the tunnel but it failed with request timed out. but i can see my Tunnel interface IPs of course.

it may be dump question but about the 201 ipv4 address that referenced to the global ip address, should i assign it to the wireless NIC i used to connect through it to my network or assign it only to the Tunnel interface.

and am not sure about protocol 41 on the firewall, and I'll check it, but is there any other probably problems cause this.

thank man, thanks a lot   :)

[cholzhauer]

Gotcha.  That means that the tunnel is not up.

I don't know what 201 IPv4 address you're talking about...did you mean the 2001 IPv6 address?  You should assign an address from your routed /64 to your interfaces, but we'll get to that later

At this point, as long as you've used your NAT address to create the tunnel, we're down to protocol 41.  You could try removing the IP6Tunnel interface, rebooting, and re-creating just to rule it out.

[SUSTipv6]

sorry for not clearing info. i meant to say 172.27.150.201 ip address that referenced to the global ip address i used to create the tunnel, should i assign it to the real interface card or  assign it to the Tunnel interface only. i hope you understand my point because i can figure it out myself.

thank for this valuable info. am applying it right know :)

[cholzhauer]

Now I'm really confused.  Why don't you make me a list of all ip addresses and what interface they go to, and tell me what your os is, and I'll get you the commands you need to run

[SUSTipv6]

Hi cholzhauer

sorry for late reply, i did contact my network admin. and he fixed the firewall problem, i tried again but same "request timed out".

here are my configurations:
>ipconfig /all

Wireless Lan Adapter:
ip address 196.1.209.12
mask 255.255.255.0
ipv6 address 2001::10

Tunnel adapter IP6Tunnel:
media state               :media  disconnected   
description                 :Microsoft direct point-to-point adapter
DHCP enable                :no
autoconfiguration enabled   :yes

>>>>
my tunnel details :
        Server IPv4 address:    216.66.84.42
   Server IPv6 address:    2001:470:1f12:4c7::1/64
   Client IPv4 address:    196.1.209.105
   Client IPv6 address:    2001:470:1f12:4c7::2/64 
>>>>>

is it about "media disconnected" on the tunnel adapter??

[SUSTipv6]

just to ensure
>>>>>>>>>>>>>>>>>>>>>
C:\Users\MUTAZ>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : MUTAZ-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Mixed
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : sustech.edu

Ethernet adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Anchorfree HSS Adapter
   Physical Address. . . . . . . . . : 00-FF-A9-CE-85-30
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : sustech.edu
   Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
   Physical Address. . . . . . . . . : 00-24-81-41-97-4C
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : sustech.edu
   Description . . . . . . . . . . . : Intel(R) WiFi Link 5100 AGN
   Physical Address. . . . . . . . . : 00-21-6B-9E-FF-D2
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001::10(Preferred)
   Link-local IPv6 Address . . . . . : fe80::d513:25d9:b746:912b%11(Preferred)
   IPv4 Address. . . . . . . . . . . : 172.27.150.143(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Thursday, December 30, 2010 2:41:26 AM
   Lease Expires . . . . . . . . . . : Thursday, December 30, 2010 8:41:25 AM
   Default Gateway . . . . . . . . . : 172.27.150.254
   DHCP Server . . . . . . . . . . . : 172.27.150.254
   DHCPv6 IAID . . . . . . . . . . . : 184557931
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-2A-88-D8-00-24-81-41-97-4C

   DNS Servers . . . . . . . . . . . : 196.1.209.76
                                       196.29.170.206
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.sustech.edu:

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

Tunnel adapter isatap.{A9CE8530-795D-4203-9881-3C456BDC423C}:

   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 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
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

[cholzhauer]

OK, so you're behind a NAT, so we need to use that address.  You didn't mention your OS, so I'll assume Vista/7

use this

Code Select Expand


netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 172.27.150.143 216.66.84.42
netsh interface ipv6 add address IP6Tunnel  2001:470:1f12:4c7::2
netsh interface ipv6 add route ::/0 IP6Tunnel  2001:470:1f12:4c7::1


Now, we also need to assign an IPv6 address to your Wireless adapter.  I don't know where that 2001::10 came from in your first post, but I don't see it in the output of ipconfig, so I'll ignore it.

I don't know what your routed /64 is, but it's probably something like 2001:470:1f11:4c7::/64.  So we'll take an address out of there and add it to your connection.  Let's use 2001:470:1f11:4c7::1.  Add that to your interface the same way you would a static IPv4 address, but choose the IPv6 stack instead.

If your tunnel still doesn't work, ask your network admin about protocol 41  (remember port != protocol)

[SUSTipv6]

thank a lot, I post more info about my problem on this topic http://www.tunnelbroker.net/forums/index.php?topic=1364.0.
my OS is windows 7 . after what you said I start to think it's only because of the firewall.

thanks, and I'll see what I can do about that.