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

Vista+Linksys WRT54G router=no IPv6 tunnel connectivity

Started by a1pcfixer, September 06, 2010, 02:51:41 AM

Previous topic - Next topic

a1pcfixer

Quote from: lukec on September 07, 2010, 02:22:15 PM
Couple of suggestions...can you ping your router address?

run        netsh interface ipv6 show interface 8" (where 8 in the index number of your interface)

What is the status of"Neighbour Discovery" "NUD" "Router Discovery" ? These "should" be enabled ...

Regards
lukec

ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms


interface 8" (where 8 in the index number of your interface)
Where/how do I find that???

a1pcfixer

Quote from: cholzhauer on September 07, 2010, 03:49:44 PM

Look at post #14 from jimb

Did I do this right?.........

C:\>netsh int ipv6 delete interface IP6Tunnel


C:\>netsh int ipv6 show interface

Idx  Met   MTU   State        Name
---  ---  -----  -----------  -------------------
  1   50 4294967295  connected    Loopback Pseudo-Interface 1
  9   10   1280  disconnected  Local Area Connection* 10
  7   20   1500  connected    Local Area Connection
15   50   1280  disconnected  Local Area Connection* 11



netsh interface teredo
set state disabled
Ok.

netsh interface ipv6 a
dd v6v4tunnel IP6Tunnel 192.168.1.106 209.51.181.2

netsh interface ipv6 a
dd address IP6Tunnel 2001:470:1f10:91e::2
The object already exists.

netsh interface ipv6 a
dd route ::/0 IP6Tunnel 2001:470:1f10:91e::1
The object already exists.


C:\>netsh int ipv6 show interface

Idx  Met   MTU   State        Name
---  ---  -----  -----------  -------------------
  1   50 4294967295  connected    Loopback Pseudo-Interface 1
  9   10   1280  disconnected  Local Area Connection* 10
  7   20   1500  connected    Local Area Connection
15   50   1280  disconnected  Local Area Connection* 11
16   25   1280  connected    IP6Tunnel

cholzhauer

Quote
16   25   1280  connected    IP6Tunnel

At least it says connected.

What does ipconfig /all show?  As long as that static address is still on your NIC, everything "looks" like it should work

a1pcfixer

Quote from: cholzhauer on September 07, 2010, 05:56:17 PM

What does ipconfig /all show?  As long as that static address is still on your NIC, everything "looks" like it should work


ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : xxxxxxx-a
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : hsd1.in.comcast.net

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : hsd1.in.comcast.net
   Description . . . . . . . . . . . : Intel(R) 82562V-2 10/100 Network Connecti
on
   Physical Address. . . . . . . . . : 00-19-D1-7F-13-E2
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:1f11:91e::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::3d68:98ac:9f8b:fb0%7(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.106(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, September 07, 2010 2:49:31 PM
   Lease Expires . . . . . . . . . . : Wednesday, September 08, 2010 2:49:30 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 184555985
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-0F-91-B2-C3-00-19-D1-7F-13-E2

   DNS Servers . . . . . . . . . . . : 204.117.214.10
                                       204.97.212.10
                                       4.2.2.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 10:

   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* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : hsd1.in.comcast.net
   Description . . . . . . . . . . . : isatap.hsd1.in.comcast.net
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter IP6Tunnel:

   Connection-specific DNS Suffix  . : hsd1.in.comcast.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:1f10:435::2(Preferred)
   IPv6 Address. . . . . . . . . . . : 2001:470:1f10:91c::2(Preferred)
   IPv6 Address. . . . . . . . . . . : 2001:470:1f10:91e::2(Preferred)
   Link-local IPv6 Address . . . . . : fe80::88ba:f66b:380a:799%16(Preferred)
   Default Gateway . . . . . . . . . : 2001:470:1f10:435::1
                                       2001:470:1f10:91e::1
   DNS Servers . . . . . . . . . . . : 204.117.214.10
                                       204.97.212.10
                                       4.2.2.4
   NetBIOS over Tcpip. . . . . . . . : Disabled
   
   
   
   
   
   C:\>netstat -nr
=================================================================
Interface List
  7 ...00 19 d1 7f 13 e2 ...... Intel(R) 82562V-2 10/100 Network Connection
  1 ........................... Software Loopback Interface 1
  9 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
15 ...00 00 00 00 00 00 00 e0  isatap.hsd1.in.comcast.net
16 ...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      192.168.1.1    192.168.1.106     20
        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.1.0    255.255.255.0         On-link     192.168.1.106    276
    192.168.1.106  255.255.255.255         On-link     192.168.1.106    276
    192.168.1.255  255.255.255.255         On-link     192.168.1.106    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.1.106    276
  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.1.106    276
=================================================================
Persistent Routes:
  None

IPv6 Route Table
=================================================================
Active Routes:
If Metric Network Destination      Gateway
16    281 ::/0                     2001:470:1f10:435::1
16    281 ::/0                     2001:470:1f10:91e::1
  1    306 ::1/128                  On-link
16    281 2001:470:1f10:435::/64   On-link
16    281 2001:470:1f10:435::2/128 On-link
16    281 2001:470:1f10:91c::/64   On-link
16    281 2001:470:1f10:91c::2/128 On-link
16    281 2001:470:1f10:91e::/64   On-link
16    281 2001:470:1f10:91e::2/128 On-link
  7    276 2001:470:1f11:91e::/64   On-link
  7    276 2001:470:1f11:91e::2/128 On-link
  7    276 fe80::/64                On-link
16    281 fe80::/64                On-link
  7    276 fe80::3d68:98ac:9f8b:fb0/128
                                    On-link
16    281 fe80::88ba:f66b:380a:799/128
                                    On-link
  1    306 ff00::/8                 On-link
  7    276 ff00::/8                 On-link
16    281 ff00::/8                 On-link
=================================================================
Persistent Routes:
If Metric Network Destination      Gateway
  0 4294967295 ::/0                     2001:470:1f10:435::1
  0 4294967295 ::/0                     2001:470:1f10:91e::1
=================================================================



Somewhere along all these changes, my browser refreshing of this site went to a crawl.
Testing at.....  http://test-ipv6.com/   ......was also dead slow, and still showed only IPv4 connectivity, nothing for IPv6.

So, thanks to my handy-dandy ERU/NT utility, I've restored my registry back to when basic web browsing worked fast.
That has put me back to where I was before I tried all this IPv6 tunnel settings.

I still think my Linksys WRT54G router & firmware are the biggest bottleneck here.
Until I change that, I'm going to sit back.

A big thank-you to ALL who tried helping, I appreciate it!!!!

cholzhauer

One thing to keep in mind when you start messing with your router is that you need to pass protocol 41 to whatever is hosting your tunnel.  I don't know how your Linksys is configured right now, but if you're not letting ICMP and protocol 41 through, it won't work

a1pcfixer

My Linksys WRT54G is 'protocol 41' unaware. It only understands TCP & UDP.

Norton Security Suite however does provide support for protocol 41, and I assume Vista/Win7 firewall as well, which might be connected to 'Teredo'.

I just read up on newer cable modems, IPv6 capable , plus routers. My cable modem is rated for DOSCIS 2.0 only. Newer ones are DOSCIS 3.0 & are IPv6 capable. I'll probably need to eventually upgrade to a newer cable modem & router.

I feel the degree of effort to get a IPv6 tunnel working, should have been easier, but maybe it was just my own incompetence. Still, I thank you for your efforts to help me!

a1pcfixer

Quote from: cholzhauer on September 07, 2010, 06:50:07 PM
I don't know how your Linksys is configured right now, but if you're not letting ICMP and protocol 41 through, it won't work

My Linksys WRT54G (v.2.0) & it's firmware( v4.71.1, Hyperwrt 2.1b1 + Thibor15c) + my Motorola SB5101 cable modem (DOSCIS 2.0) are 'Protocol 41' unaware.

However, I have gotten an IPv6-in-UDP-IPv4 tunnel fully functional by using the GogoCLIENT Utility. A temporary fix, until I upgrade my router & modem.

abcs

a1pcfixer,

I use Road Runner with Brighthouse Networks, with a static IP for my connection 24.227.47.170 connected
to a Linksys WRT54G V2.0 Router firmware version v2.02.7. with a static IP on my PC with XP Pro SP3 of
192.168.1.2. Here is the setup routine I used:


netsh interface>ipv6
netsh interface ipv6>add v6v4tunnel IP6Tunnel 192.168.1.96 216.218.224.42
Ok.

netsh interface ipv6>add addr IP6Tunnel 2001:470:1f0e:835::2
Ok.

netsh interface ipv6>show interface
Querying active state...

Idx  Met   MTU    State         Name
---  ----  -----  ------------  -----
  9     1   1280  Connected     IP6Tunnel
  8     0   1500  Disconnected  Local Area Connection 3
  7     0   1500  Connected     VirtualBox Host-Only Network
  6     0   1500  Connected     Parallels Host-Guest Virtual NIC
  5     0   1500  Connected     Local Area Connection
  4     2   1280  Disconnected  Teredo Tunneling Pseudo-Interface
  3     1   1280  Connected     6to4 Pseudo-Interface
  2     1   1280  Connected     Automatic Tunneling Pseudo-Interface
  1     0   1500  Connected     Loopback Pseudo-Interface

netsh interface ipv6>set interface 9 forwarding=enabled
Ok.

netsh interface ipv6>set interface 5 forwarding=enabled advertise=enabled
Ok.

netsh interface ipv6>add address interface="Local Area Connection" address=2001:470:1f0e:835::1
Ok.

netsh interface ipv6>add route 2001:470:1f0e:835::/64 interface="Local Area Connection" publish=yes
Ok.

netsh interface ipv6>add route ::/0 "IP6Tunnel" 2001:470:1f0e:835::1 publish=yes
Ok.

netsh interface ipv6>ping6
The following command was not found: ping6.
netsh interface ipv6>..

netsh interface>..

netsh>..

netsh>..

netsh>exit

E:\Documents and Settings\Andy>ping6 2001:470:1f0e:853::1

Pinging 2001:470:1f0e:853::1
from 2001:470:1f0e:835::2 with 32 bytes of data:

Reply from 2001:470:1f0e:853::1: bytes=32 time=88ms
Reply from 2001:470:1f0e:853::1: bytes=32 time=87ms
Reply from 2001:470:1f0e:853::1: bytes=32 time=94ms
Reply from 2001:470:1f0e:853::1: bytes=32 time=87ms

Ping statistics for 2001:470:1f0e:853::1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 87ms, Maximum = 94ms, Average = 89ms

E:\Documents and Settings\Andy>ping6 ipv6.google.com

Pinging ipv6.l.google.com [2001:4860:800a::63]
from 2001:470:1f0e:835::2 with 32 bytes of data:

Reply from 2001:4860:800a::63: bytes=32 time=141ms
Reply from 2001:4860:800a::63: bytes=32 time=144ms
Reply from 2001:4860:800a::63: bytes=32 time=140ms
Reply from 2001:4860:800a::63: bytes=32 time=142ms

Ping statistics for 2001:4860:800a::63:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 140ms, Maximum = 144ms, Average = 141ms


And with this setup my HE Tunnel works fine behind this router, the only change I made on the PC was
in the adapters advanced firewall advanced ICMP settings was to enable every ICMP setting to get things
to work.

Note: I also tried a Linksys WRT54G V8 and that roouter was a no go.

ABCS