Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Pages: [1] 2

Author Topic: Explorer test - web browser not seeing ipv6  (Read 13121 times)

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Explorer test - web browser not seeing ipv6
« on: August 03, 2010, 10:52:22 PM »

Ok I've got a tunnel over PPTP...

I tested it...

Code: [Select]
C:\Users\Don>tracert -6 ipv6.he.net

Tracing route to ipv6.he.net [2001:470:0:64::2]
over a maximum of 30 hops:

  1   166 ms   171 ms   167 ms  2002:c058:6301::1
  2   170 ms   169 ms   169 ms  gige-g4-12.core1.lax1.he.net [2001:470:0:14e::1]

  3   164 ms   169 ms   178 ms  10gigabitethernet2-2.core1.fmt2.he.net [2001:470
:0:18d::1]
  4   241 ms   251 ms   169 ms  gige-g4-18.core1.fmt1.ipv6.he.net [2001:470:0:2d
::1]
  5   219 ms   171 ms   178 ms  ipv6.he.net [2001:470:0:64::2]

Trace complete.

http://ipv6.he.net/certification/validate-explorer.php says:  Your reported Internet Protocol Address is: 184.104.87.104

This is the IPv4 address that the pptp tunnel delivered.

I tried using opera as suggested by someone else but fail.

Not sure what I'm doing wrong to make the web broswers see the right ip?

Suggestions?

Cheers Don

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1709
Re: Explorer test - web browser not seeing ipv6
« Reply #1 on: August 03, 2010, 11:15:10 PM »

The fun of using 6to4/teredo on dual-stacked pages is that the browser will simply prefer v4. Try not using 6to4 (2002::/16), and instead use the HE tunnel and you should be fine.
« Last Edit: August 04, 2010, 12:23:17 AM by broquea »
Logged

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Re: Explorer test - web browser not seeing ipv6
« Reply #2 on: August 04, 2010, 12:10:22 AM »

The fun of using 6to4/teredo on dual-stacked pages is that the browser will simply prefer v4.

Ok that I understand. :)

Quote
Try not using 6to4 (2002::/16), and the HE tunnel, and you should be fine.

Ok that I don't understand...

How do I not use the tunnel?  What configuration should I be using?  What should I be reading that I haven't read yet?

Thanks for the help.

Cheers Don

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1709
Re: Explorer test - web browser not seeing ipv6
« Reply #3 on: August 04, 2010, 12:14:56 AM »

Sorry should have been "and instead use the HE tunnel"
Logged

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Re: Explorer test - web browser not seeing ipv6
« Reply #4 on: August 04, 2010, 12:17:21 AM »

Ok that makes more sense...  I'll have a look at that now then :)

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Re: Explorer test - web browser not seeing ipv6
« Reply #5 on: August 04, 2010, 12:27:04 AM »

No, fail...

Ran
Code: [Select]
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 121.73.114.171 66.220.18.42
netsh interface ipv6 add address IP6Tunnel 2001:470:c:8e3::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:c:8e3::1

ipconfig:
Code: [Select]

C:\Users\Don>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

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

Ethernet adapter Bluetooth Network Connection:

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

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : pointclark.net
   Link-local IPv6 Address . . . . . : fe80::f8a7:52a0:d56b:948b%9
   IPv4 Address. . . . . . . . . . . : 192.168.2.100
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.2.1

Ethernet adapter Local Area Connection:

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

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::d88e:f271:4599:6208%22
   IPv4 Address. . . . . . . . . . . : 192.168.56.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

route print:

Code: [Select]
IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 22    276 fe80::/64                On-link
  9    281 fe80::/64                On-link
 22    276 fe80::d88e:f271:4599:6208/128
                                    On-link
  9    281 fe80::f8a7:52a0:d56b:948b/128
                                    On-link
  1    306 ff00::/8                 On-link
 22    276 ff00::/8                 On-link
  9    281 ff00::/8                 On-link
===========================================================================

I'm still missing something aren't it?

Cheers Don

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1709
Re: Explorer test - web browser not seeing ipv6
« Reply #6 on: August 04, 2010, 12:31:24 AM »

Underneath the example commands is a *NOTE* about using your RFC1918 address if you are behind NAT. Try removing the interface then run the commands again but with the internal IP and not the IPv4 endpoint.
Logged

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Re: Explorer test - web browser not seeing ipv6
« Reply #7 on: August 04, 2010, 12:54:28 AM »

Underneath the example commands is a *NOTE* about using your RFC1918 address if you are behind NAT. Try removing the interface then run the commands again but with the internal IP and not the IPv4 endpoint.

Opps... sorry, should have read the page more closely.

How do I remove the interface? 

I've been googling netsh (new to that as well sorry)...  I'm also not quite sure how to identify which is the right interface to remove.

Code: [Select]
C:\Users\Don>netsh interface ip show addresses

Configuration for interface "Local Area Connection 2"
    DHCP enabled:                         Yes
    InterfaceMetric:                      30

Configuration for interface "Bluetooth Network Connection"
    DHCP enabled:                         Yes
    InterfaceMetric:                      50

Configuration for interface "Wireless Network Connection"
    DHCP enabled:                         Yes
    IP Address:                           192.168.2.100
    Subnet Prefix:                        192.168.2.0/24 (mask 255.255.255.0)
    Default Gateway:                      192.168.2.1
    Gateway Metric:                       0
    InterfaceMetric:                      25

Configuration for interface "Local Area Connection"
    DHCP enabled:                         Yes
    InterfaceMetric:                      10

Configuration for interface "Local Area Connection 3"
    DHCP enabled:                         No
    IP Address:                           192.168.56.1
    Subnet Prefix:                        192.168.56.0/24 (mask 255.255.255.0)
    InterfaceMetric:                      20

Configuration for interface "Loopback Pseudo-Interface 1"
    DHCP enabled:                         No
    IP Address:                           127.0.0.1
    Subnet Prefix:                        127.0.0.0/8 (mask 255.0.0.0)
    InterfaceMetric:                      50

At a guess I'm suspecting "Local Area Connection 3" but it's not showing the v6 address.

Sorry to be such a knob here. :)

Cheers Don

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Re: Explorer test - web browser not seeing ipv6
« Reply #8 on: August 04, 2010, 01:19:01 AM »

Ok I think I'm getting closer...

Code: [Select]
>netsh interface ipv6 delete interface IP6Tunnel
to remove the tunnel...

Then...
Code: [Select]
netsh interface teredo set state disabled
netsh interface ipv6 add v6v4tunnel IP6Tunnel 192.168.2.100 66.220.18.42
netsh interface ipv6 add address IP6Tunnel 2001:470:c:8e3::2
netsh interface ipv6 add route ::/0 IP6Tunnel 2001:470:c:8e3::1

Is that right?  or did I replace the wrong end point?

I tired this then ping -6 2001:470:c:8e3::1 (the gateway?) but got no answer...

Then I went back to opera again to do the exam test but that failed.

Cheers Don

cholzhauer

  • Hero Member
  • *****
  • Posts: 2686
Re: Explorer test - web browser not seeing ipv6
« Reply #9 on: August 04, 2010, 04:58:25 AM »

Have you assigned an address out of your routed /64 or /48 to your local area interface?

What's the output of ipconfig /all and netstat -nr ?
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1709
Re: Explorer test - web browser not seeing ipv6
« Reply #10 on: August 04, 2010, 07:48:44 AM »

There is a chance that:

1) you need to put your Windows machine in the DMZ of the NAT appliance it is behind
2) your NAT appliance doesn't forward Protocol 41 (not port) to hosts behind it
Logged

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Re: Explorer test - web browser not seeing ipv6
« Reply #11 on: August 04, 2010, 03:07:55 PM »

Have you assigned an address out of your routed /64 or /48 to your local area interface?
No, I didn't know I had to...
Quote
What's the output of ipconfig /all and netstat -nr ?

Code: [Select]
C:\Users\Don>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Don-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : pointclark.net

Ethernet adapter Local Area Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : TAP-Win32 Adapter V9
   Physical Address. . . . . . . . . : 00-FF-65-48-25-BC
   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. . . . . . . . . : 00-1E-37-DE-88-1D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : pointclark.net
   Description . . . . . . . . . . . : Broadcom 802.11a/b/g WLAN
   Physical Address. . . . . . . . . : 00-21-00-08-27-5A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f8a7:52a0:d56b:948b%9(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.2.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, 4 August 2010 3:12:58 p.m.
   Lease Expires . . . . . . . . . . : Thursday, 5 August 2010 8:17:17 p.m.
   Default Gateway . . . . . . . . . : 192.168.2.1
   DHCP Server . . . . . . . . . . . : 192.168.2.1
   DHCPv6 IAID . . . . . . . . . . . : 301998336
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-86-EA-D7-00-1E-68-41-72-5B

   DNS Servers . . . . . . . . . . . : 192.168.2.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
   Physical Address. . . . . . . . . : 00-1E-68-41-72-5B
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection 3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
   Physical Address. . . . . . . . . : 08-00-27-00-00-C1
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::d88e:f271:4599:6208%22(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

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

Tunnel adapter IP6Tunnel:

   Connection-specific DNS Suffix  . : pointclark.net
   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:c:8e3::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::24fd:cf0:dfb2:d969%12(Preferred)
   Default Gateway . . . . . . . . . : 2001:470:c:8e3::1
   DNS Servers . . . . . . . . . . . : 192.168.2.1
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{C29FDE9E-E144-4195-BBBB-CA7431FB5
654}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 16:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 10:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{654825BC-ACE0-4F95-9660-AB79B1824
DEF}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 19:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{B5FD66AE-873B-458A-B3DC-0C753086D
2B5}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 20:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{BE571522-4184-4566-BF4D-EF00CC0A8
C94}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Don>

Code: [Select]
C:\Users\Don>netstat -nr
===========================================================================
Interface List
 14 ...00 ff 65 48 25 bc ...... TAP-Win32 Adapter V9
 11 ...00 1e 37 de 88 1d ...... Bluetooth Device (Personal Area Network)
  9 ...00 21 00 08 27 5a ...... Broadcom 802.11a/b/g WLAN
  8 ...00 1e 68 41 72 5b ...... NVIDIA nForce Networking Controller
 22 ...08 00 27 00 00 c1 ...... VirtualBox Host-Only Ethernet Adapter
  1 ........................... Software Loopback Interface 1
 18 ...00 00 00 00 00 00 00 e0  Microsoft ISATAP Adapter
 12 ...00 00 00 00 00 00 00 e0  Microsoft Direct Point-to-point Adapater
 17 ...00 00 00 00 00 00 00 e0  isatap.{C29FDE9E-E144-4195-BBBB-CA7431FB5654}
 13 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
 24 ...00 00 00 00 00 00 00 e0  isatap.{654825BC-ACE0-4F95-9660-AB79B1824DEF}
 23 ...00 00 00 00 00 00 00 e0  isatap.{B5FD66AE-873B-458A-B3DC-0C753086D2B5}
 25 ...00 00 00 00 00 00 00 e0  isatap.{BE571522-4184-4566-BF4D-EF00CC0A8C94}
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.2.1    192.168.2.100     25
        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.0    255.255.255.0         On-link     192.168.2.100    281
    192.168.2.100  255.255.255.255         On-link     192.168.2.100    281
    192.168.2.255  255.255.255.255         On-link     192.168.2.100    281
     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    281
        224.0.0.0        240.0.0.0         On-link     192.168.2.100    286
  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     192.168.2.100    281
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 12    286 ::/0                     2001:470:c:8e3::1
  1    306 ::1/128                  On-link
 12    286 2001:470:c:8e3::/64      On-link
 12    286 2001:470:c:8e3::2/128    On-link
 22    276 fe80::/64                On-link
  9    281 fe80::/64                On-link
 12    286 fe80::/64                On-link
 12    286 fe80::24fd:cf0:dfb2:d969/128
                                    On-link
 22    276 fe80::d88e:f271:4599:6208/128
                                    On-link
  9    281 fe80::f8a7:52a0:d56b:948b/128
                                    On-link
  1    306 ff00::/8                 On-link
 22    276 ff00::/8                 On-link
  9    281 ff00::/8                 On-link
 12    286 ff00::/8                 On-link
===========================================================================
Persistent Routes:
 If Metric Network Destination      Gateway
  0 4294967295 ::/0                     2001:470:c:8e3::1
===========================================================================

C:\Users\Don>

How do I assign an ip?

Cheers Don

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Re: Explorer test - web browser not seeing ipv6
« Reply #12 on: August 04, 2010, 03:13:36 PM »

There is a chance that:

1) you need to put your Windows machine in the DMZ of the NAT appliance it is behind
2) your NAT appliance doesn't forward Protocol 41 (not port) to hosts behind it

Morning...

Not on a NAT appliance.

Ok we've got a Linux box and 3 windows machines with some wifi and a couple of switches...

Code: [Select]
CableModem<-->eth0-LinuxBox-eth1<-->wifiAP<-->VistaLaptop(*2)/XpDesktop
eth0 gets a public IPv4 address that's static.

The linux box is running ClarkConnect3.2 (based on Centos~4 iirc).

My next thinking is to just terminate the tunnel on a linux vm and have a play from there, but I'd kinda like to get this working just because it should work and I'd like to understand the constraints.

Cheers Don

cholzhauer

  • Hero Member
  • *****
  • Posts: 2686
Re: Explorer test - web browser not seeing ipv6
« Reply #13 on: August 04, 2010, 04:24:53 PM »

So your tunnel is on the Cent OS box?  Easy peasy.   Do you have the tunnel online?  If not, we need to get that working.

After that, you need to assign an IP v6 address to your local area connection...if you don't have that, Windows won't be able to do much.  Easiest way to add it is through the GUI via the control panel (same way you'd add a static IPv4 address, just chose the IPv6 stack instead)  Best way to do this is run RA (router advertisements) on your linux machine and distribute addresses that way, that way you don't need to deal with static addresses in windows)  Again, use your routed /64 or select a /64 out of your /48 (if you took it)

Logged

thinkdesignprint

  • Newbie
  • *
  • Posts: 17
Re: Explorer test - web browser not seeing ipv6
« Reply #14 on: August 04, 2010, 04:38:03 PM »

So your tunnel is on the Cent OS box?
No.  I was trying to terminate the tunnel on my vista box.  (CableModem<>LinuxBox<>Wifi<>VistaDonPC)

Not idea if protocol41 is supported.

It does seam that termination on the linux box would make more sense.  However I'd also kinda like to know why what I've been doing isn't working.  I suspect its the protocol41 issue and am guessing that I could spend some time chasing that out of ClarkConnect3.2 (which is now end of life - hence a waste of time?).

Quote
  Easy peasy.   Do you have the tunnel online? 
No.

Quote
If not, we need to get that working.

yes

Quote
After that, you need to assign an IP v6 address to your local area connection...if you don't have that, Windows won't be able to do much.  Easiest way to add it is through the GUI via the control panel (same way you'd add a static IPv4 address, just chose the IPv6 stack instead) 
Ok that makes perfect sense.

Quote
Best way to do this is run RA (router advertisements) on your linux machine and distribute addresses that way, that way you don't need to deal with static addresses in windows)  Again, use your routed /64 or select a /64 out of your /48 (if you took it)

Nice... I'm off to man the radvd stuff

I got the /64 tunnel.

Thanks for the help... I'll work on that :)

Cheers Don
Pages: [1] 2