dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
4715
share rss forum feed

Manco9

join:2012-06-08

[IPv6] IPV6 Issues

Hello!

I've been a long time lurker and finally joined.

I'm having problems with IPv6. I seem to be be getting an intermittent connection it comes and it goes. This morning I had a connection now I don't. Its been this way since it was implemented.

I'm on Windows 7 running a Netgear WNDR3700v1 router. I have it set to auto-detect and it goes to a 6to4 tunnel. I even tried the solutions given in some other threads and upgraded the firmware 1.0.16.98dnsNA and still no joy. If I set the internet connection to DHCP in the IPv6 tab I get no IPv6 addresses for WAN or LAN.

At first I thought the problem was my modem I had a Arris TM402 I think. I was due a new docsis 3.0 modem so I went to my local Com cast office and they gave me a Arris TG862 Telephony Gateway and still the same thing.

Even when I have IPv6 connectivity my browser still prefers IPv4 according to the various IPv6 test sites.I checked about:config in Firefox and network.dns.disableIPv6 is set to false.

Any Ideas?

Thanks in advance!



NetDog
Premium,VIP
join:2002-03-04
Parker, CO
kudos:77
Reviews:
·Comcast

Ok first check with »mydeviceinfo.comcast.net/ and make sure your modem supports IPv6 on the CPE. I am thinking both of those models do not. Second PM me your cable modem mac and I will see if the CMTS your on supports v6. Most likely your doing a tunnel somewhere right now, do you have it setup for 6to4?

Expand your moderator at work


Streetlight

join:2005-11-07
Colorado Springs, CO
reply to Manco9

Re: [IPv6] IPV6 Issues

Take a look at the thread:

»[IPv6] Netgear WNDR3700v1 and Ipv6 Issues

Particularly important are the posts by Gerard1234 and MartinC on the 2nd page of the thread about the rebooting of modem and router with attention to unplugging and replugging the internet cable.

Worked for me.
--
There is nothing more deceptive than an obvious fact.

Sherlock Holmes in
The Boscombe Valley Mystery
A. C. Doyle
Strand Magazine, October 1891


Manco9

join:2012-06-08
reply to Manco9

said by NetDog:

Ok first check with »mydeviceinfo.comcast.net/ and make sure your modem supports IPv6 on the CPE. I am thinking both of those models do not. Second PM me your cable modem mac and I will see if the CMTS your on supports v6. Most likely your doing a tunnel somewhere right now, do you have it setup for 6to4?

I saw that mydevice info.I printed it out and took it with me when I went to get the modem. There is no check next to IPv6. I asked them about that and they said it just wasn't certified yet but it should work?!

It's on auto-detect and indicates 6to4.


NetDog
Premium,VIP
join:2002-03-04
Parker, CO
kudos:77
Reviews:
·Comcast

said by Manco9:

I asked them about that and they said it just wasn't certified yet but it should work?!

Who is them? Just would like to know who told you that..


NetDog
Premium,VIP
join:2002-03-04
Parker, CO
kudos:77
reply to Manco9

The CMTS your connected to is a Cisco CMTS, so it isnt supported for native dual-stack at this time. So the 6to4 is the best option at this time.



nightwalker
Nightwalker

join:1999-08-07
Chicago, IL
reply to Manco9

It's not Comcast or your modem or your gateway. Windows7 has a built-in 6to4 support that seems to be available on-demand. Comcast support for ipv6 will assign you a physical IP and isn't available nationwide yet.

You can test your local availability with a site such as:
»test-ipv6.com/

C:\>ping -6 ipv6.google.com

Pinging ipv6.l.google.com [2607:f8b0:400f:800::1010] with 32 bytes of data:
Request timed out.
Reply from 2607:f8b0:400f:800::1010: time=32ms
Reply from 2607:f8b0:400f:800::1010: time=32ms
Reply from 2607:f8b0:400f:800::1010: time=32ms

Ping statistics for 2607:f8b0:400f:800::1010:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 32ms, Average = 32ms
--
»www.reverse.net


Manco9

join:2012-06-08

1 edit
reply to NetDog

said by NetDog:

said by Manco9:

I asked them about that and they said it just wasn't certified yet but it should work?!

Who is them? Just would like to know who told you that..

The customer service rep or are they tellers they have manning the windows inside? I should have known they didn't know much. When I was making the exchange I asked about Arris modems and the guy said the only model they have is "Gateway" as if that were the brand name. There was a woman with him too saying the only brand they have is "Gateway".

When I got the box I realized they were talking about telephony gateway.

Can't say I like it. When I got it home I couldn't figure out how to turn off the wireless functionality eventually I found out you have to call Comcast to get it turned off. Also there's no standby button like on my old modem.

Does Comcast have different modems for different areas?

I would have liked to buy my own modem but Comcast does my phones too and you can't seem to buy telephony models anywhere retail.

said by NetDog:

The CMTS your connected to is a Cisco CMTS, so it isnt supported for native dual-stack at this time. So the 6to4 is the best option at this time.

Okay but should the IPv6 functionality go in and out the way it does?

Thanks for the replies.

Manco9

join:2012-06-08
reply to nightwalker

said by nightwalker:

It's not Comcast or your modem or your gateway. Windows7 has a built-in 6to4 support that seems to be available on-demand. Comcast support for ipv6 will assign you a physical IP and isn't available nationwide yet.

You can test your local availability with a site such as:
»test-ipv6.com/

C:\>ping -6 ipv6.google.com
Pinging ipv6.l.google.com [2607:f8b0:400f:800::1010] with 32 bytes of data:
Request timed out.
Reply from 2607:f8b0:400f:800::1010: time=32ms
Reply from 2607:f8b0:400f:800::1010: time=32ms
Reply from 2607:f8b0:400f:800::1010: time=32ms

Ping statistics for 2607:f8b0:400f:800::1010:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 32ms, Average = 32ms

I've run that test before with my old modem and the new one. I get 7/10 on the first part 10/10 on the second.

On the Comcast IPv6 test I score 10/10 on both parts.

C:\>ping -6 ipv6.google.com
Pinging ipv6.l.google.com [2001:4860:800a::68] with 32 bytes of data:
Reply from 2001:4860:800a::68: time=42ms
Reply from 2001:4860:800a::68: time=42ms
Reply from 2001:4860:800a::68: time=41ms
Reply from 2001:4860:800a::68: time=41ms

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

C:\>ping ipv6.google.com
Pinging ipv6.l.google.com [2607:f8b0:4002:802::1013] with 32 bytes of data:
Reply from 2607:f8b0:4002:802::1013: time=42ms
Reply from 2607:f8b0:4002:802::1013: time=44ms
Reply from 2607:f8b0:4002:802::1013: time=40ms
Reply from 2607:f8b0:4002:802::1013: time=43ms

Ping statistics for 2607:f8b0:4002:802::1013:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 44ms, Average = 42ms

What's the difference between these two pings? I know the addresses are different.


EG
The wings of love
Premium
join:2006-11-18
Union, NJ
kudos:9

Did you deliberately use different domain names ? They resolved to different IP addresses which directed to two different servers possibly in different geographic areas. Likely due to CDN and load balancing.


Gerard1234

join:2012-04-03
reply to Manco9

Comcast wants you to think they are the only ones who can turn it off. But you can too remember to type in at the SSID: TIMEOUT.



NetFixer
Snarl For The Camera Please
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage

1 edit
reply to Manco9

said by Manco9:

C:\>ping -6 ipv6.google.com
Pinging ipv6.l.google.com [2001:4860:800a::68] with 32 bytes of data:
Reply from 2001:4860:800a::68: time=42ms
Reply from 2001:4860:800a::68: time=42ms
Reply from 2001:4860:800a::68: time=41ms
Reply from 2001:4860:800a::68: time=41ms

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

C:\>ping ipv6.google.com
Pinging ipv6.l.google.com [2607:f8b0:4002:802::1013] with 32 bytes of data:
Reply from 2607:f8b0:4002:802::1013: time=42ms
Reply from 2607:f8b0:4002:802::1013: time=44ms
Reply from 2607:f8b0:4002:802::1013: time=40ms
Reply from 2607:f8b0:4002:802::1013: time=43ms

Ping statistics for 2607:f8b0:4002:802::1013:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 44ms, Average = 42ms

What's the difference between these two pings? I know the addresses are different.

One way to help find out is to use tracert instead of ping. I just did that by using "tracert" and "tracert-6" twice (for a total of four traceroutes) to the same Google hostname. Comcast's 6to4 tunnel route is similar for each traceroute until it actually reaches a Google device.

C:\>tracert ipv6.google.com
 
Tracing route to ipv6.l.google.com [2001:4860:800a::69]
over a maximum of 30 hops:
 
  1     1 ms    <1 ms    <1 ms  2002:4b92:829:0:a221:b7ff:fe9c:602
  2    21 ms    22 ms    22 ms  2002:c058:6301::
  3    22 ms    21 ms    21 ms  ge-7-2-ur02.s3ndigital.ga.atlanta.comcast.net [2001:558:fe12:1::1]
  4    22 ms    21 ms    21 ms  xe-2-0-1-0-ar01.d1stonemtn.ga.atlanta.comcast.net [2001:558:140:22::1]
  5    44 ms    47 ms    63 ms  pos-2-14-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f73d::1]
  6    45 ms    43 ms    43 ms  pos-1-8-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f5e9::2]
  7    33 ms    33 ms    62 ms  2001:559::382
  8    71 ms    35 ms    33 ms  2001:4860::1:0:3f7
  9    58 ms    54 ms    56 ms  2001:4860::1:0:5db
 10    55 ms    53 ms    73 ms  2001:4860::8:0:2f03
 11    69 ms     *       71 ms  2001:4860::2:0:a7
 12    81 ms    81 ms    67 ms  2001:4860:0:1::10b
 13    64 ms    56 ms    56 ms  yx-in-x69.1e100.net [2001:4860:800a::69]
 
Trace complete.
 
C:\>tracert -6 ipv6.google.com
 
Tracing route to ipv6.l.google.com [2607:f8b0:4002:802::1012]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  2002:4b92:829:0:a221:b7ff:fe9c:602
  2    24 ms    20 ms    21 ms  2002:c058:6301::
  3    21 ms    23 ms    23 ms  ge-7-2-ur02.s3ndigital.ga.atlanta.comcast.net [2001:558:fe12:1::1]
  4    22 ms    23 ms    23 ms  xe-2-0-1-0-ar01.d1stonemtn.ga.atlanta.comcast.net [2001:558:140:22::1]
  5    44 ms    45 ms    47 ms  pos-2-13-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f73c::1]
  6    44 ms    43 ms    43 ms  pos-1-5-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f5df::2]
  7    31 ms    32 ms    31 ms  2001:559::382
  8    33 ms    33 ms    39 ms  2001:4860::1:0:92e
  9    67 ms    35 ms    34 ms  2001:4860::8:0:2fea
 10    52 ms    72 ms    67 ms  2001:4860::1:0:489
 11    58 ms    55 ms     *     2001:4860:0:1::164
 12    69 ms    77 ms     *     atl14s08-in-x12.1e100.net [2607:f8b0:4002:802::1012]
 13    61 ms    57 ms     *     atl14s08-in-x12.1e100.net [2607:f8b0:4002:802::1012]
 14    56 ms    54 ms    71 ms  atl14s08-in-x12.1e100.net [2607:f8b0:4002:802::1012]
 
Trace complete.
 
C:\>tracert ipv6.google.com
 
Tracing route to ipv6.l.google.com [2607:f8b0:4002:802::1010]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  2002:4b92:829:0:a221:b7ff:fe9c:602
  2    22 ms    21 ms    21 ms  2002:c058:6301::
  3    20 ms    21 ms    22 ms  ge-7-2-ur02.s3ndigital.ga.atlanta.comcast.net [2001:558:fe12:1::1]
  4    22 ms    39 ms    22 ms  xe-2-0-1-0-ar01.d1stonemtn.ga.atlanta.comcast.net [2001:558:140:22::1]
  5    45 ms    44 ms    44 ms  pos-3-4-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f78b::1]
  6    44 ms    43 ms    45 ms  pos-0-13-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f5fe::2]
  7    34 ms    33 ms    32 ms  2001:559::382
  8   132 ms    33 ms    34 ms  2001:4860::1:0:92e
  9    32 ms    34 ms    32 ms  2001:4860::8:0:2fea
 10    58 ms    57 ms    93 ms  2001:4860::1:0:489
 11     *       66 ms     *     2001:4860:0:1::164
 12    68 ms    63 ms    57 ms  atl14s08-in-x10.1e100.net [2607:f8b0:4002:802::1010]
 
Trace complete.
 
C:\>tracert -6 ipv6.google.com
 
Tracing route to ipv6.l.google.com [2001:4860:800a::63]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  2002:4b92:829:0:a221:b7ff:fe9c:602
  2    21 ms    21 ms    21 ms  2002:c058:6301::
  3    22 ms    22 ms    21 ms  ge-7-2-ur02.s3ndigital.ga.atlanta.comcast.net [2001:558:fe12:1::1]
  4    22 ms    23 ms    21 ms  xe-2-0-1-0-ar01.d1stonemtn.ga.atlanta.comcast.net [2001:558:140:22::1]
  5    46 ms    43 ms    43 ms  pos-2-13-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f73c::1]
  6    45 ms    43 ms    43 ms  pos-1-1-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f589::2]
  7    36 ms    65 ms    35 ms  2001:559::382
  8    33 ms    33 ms    34 ms  2001:4860::1:0:3f7
  9    56 ms    55 ms    54 ms  2001:4860::1:0:5db
 10    73 ms    67 ms    63 ms  2001:4860::8:0:2f03
 11    63 ms    57 ms    56 ms  2001:4860::2:0:a7
 12    55 ms   112 ms    80 ms  2001:4860:0:1::109
 13    79 ms    76 ms    60 ms  yx-in-x63.1e100.net [2001:4860:800a::63]
 
Trace complete.
 
 


The answer is that Google simply appears to be using load balancing, and that is further confirmed by the multiple nslookup commands shown below:


C:\>nslookup -type=AAAA ipv6.google.com
*** Can't find server name for address 192.168.9.10: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.9.10
 
Non-authoritative answer:
ipv6.google.com canonical name = ipv6.l.google.com
ipv6.l.google.com       AAAA IPv6 address = 2607:f8b0:4002:802::1013
 
C:\>nslookup -type=AAAA ipv6.google.com
*** Can't find server name for address 192.168.9.10: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.9.10
 
Non-authoritative answer:
ipv6.google.com canonical name = ipv6.l.google.com
ipv6.l.google.com       AAAA IPv6 address = 2607:f8b0:4002:802::1014
 
C:\>nslookup -type=AAAA ipv6.google.com
*** Can't find server name for address 192.168.9.10: Non-existent domain
*** Default servers are not available
Server:  UnKnown
Address:  192.168.9.10
 
Non-authoritative answer:
ipv6.google.com canonical name = ipv6.l.google.com
ipv6.l.google.com       AAAA IPv6 address = 2001:4860:800a::63
 
 
 


--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower


NetFixer
Snarl For The Camera Please
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage
reply to Manco9

said by Manco9:

said by NetDog:

Ok first check with »mydeviceinfo.comcast.net/ and make sure your modem supports IPv6 on the CPE. I am thinking both of those models do not. Second PM me your cable modem mac and I will see if the CMTS your on supports v6. Most likely your doing a tunnel somewhere right now, do you have it setup for 6to4?

I saw that mydevice info.I printed it out and took it with me when I went to get the modem. There is no check next to IPv6. I asked them about that and they said it just wasn't certified yet but it should work?!

It's on auto-detect and indicates 6to4.

         
said by Manco9:

said by NetDog:

The CMTS your connected to is a Cisco CMTS, so it isnt supported for native dual-stack at this time. So the 6to4 is the best option at this time.

Okay but should the IPv6 functionality go in and out the way it does?

Try changing your router to 6to4 (if it allows you to do that) instead of using auto detect, and see if that helps with losing IPv6 functionality.
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower


whfsdude
Premium
join:2003-04-05
Washington, DC
Reviews:
·Comcast
reply to Manco9

said by Manco9:

Even when I have IPv6 connectivity my browser still prefers IPv4 according to the various IPv6 test sites.I checked about:config in Firefox and network.dns.disableIPv6 is set to false.

6to4 is a best effort transition technology and should only be used to reach IPv6 only hosts.

Therefore, if a host you're trying to reach is dual stacked (it has v4/v6), it will always prefer v4 when using 6to4. See rfc3484 - »tools.ietf.org/html/rfc3484

tl;dr IPv4 always preferred > 6to4. 6to4 only preferred when system you are trying to connect to is v6 only.

Manco9

join:2012-06-08
reply to NetDog

Again thanks for the replies everyone! After putting the router on 6to4 instead of auto-detect yesterday I haven't lost ipv6 connectivity.

said by NetDog:

The CMTS your connected to is a Cisco CMTS, so it isnt supported for native dual-stack at this time. So the 6to4 is the best option at this time.

Thanks you. How will I be able to tell when it does support IPv6?

Also when it does I can put my router on DHCP instead of 6to4 right?


NetDog
Premium,VIP
join:2002-03-04
Parker, CO
kudos:77
Reviews:
·Comcast

said by Manco9:

Again thanks for the replies everyone! After putting the router on 6to4 instead of auto-detect yesterday I haven't lost ipv6 connectivity.

Thanks you. How will I be able to tell when it does support IPv6?

Also when it does I can put my router on DHCP instead of 6to4 right?

First question: Keep an eye on »www.comcast6.net for Cisco CMTS updates. We are also working on a app\webpage to tell the users if they are on a v6 supported CMTS or not.

Second question: you are correct it should be as simple as changing from a 6to4 setup to a DHCPv6 setup.


56885201
Ain't Nothin' But A Hound Dawg
Premium
join:2005-05-01
Dawg House

said by NetDog:

said by Manco9:

Again thanks for the replies everyone! After putting the router on 6to4 instead of auto-detect yesterday I haven't lost ipv6 connectivity.

Thanks you. How will I be able to tell when it does support IPv6?

Also when it does I can put my router on DHCP instead of 6to4 right?

First question: Keep an eye on »www.comcast6.net for Cisco CMTS updates. We are also working on a app\webpage to tell the users if they are on a v6 supported CMTS or not.

Second question: you are correct it should be as simple as changing from a 6to4 setup to a DHCPv6 setup.

I have a Comcast issued Netgear WNR1000v2-VC with the latest V1.2.2.56NA IPv6 compatible firmware. It is currently working just fine using Comcast's 6to4 relay, but I notice that this router is no longer listed as IPv6 compatible on »mydeviceinfo.comcast.net/?homegateway . It used to be listed there, does its removal from that list mean that I will not be able to use it for native IPv6 when Comcast enables it at my location?
--
Some days you're the dog; some days you're the hydrant.


whfsdude
Premium
join:2003-04-05
Washington, DC
Reviews:
·Comcast
reply to nightwalker

said by nightwalker:

Windows7 has a built-in 6to4 support that seems to be available on-demand. Comcast support for ipv6 will assign you a physical IP and isn't available nationwide yet.

6to4 doesn't work behind NAT. I think you're thinking of Teredo here.

voiptalk

join:2010-04-10
Gainesville, VA
reply to EG

said by whfsdude:

6to4 doesn't work behind NAT. I think you're thinking of Teredo here.

6to4 does work behind NAT. As long as you are able to configure your firewall to forward "protocol 41".

EDIT: Ops! 6in4 does.


56885201
Ain't Nothin' But A Hound Dawg
Premium
join:2005-05-01
Dawg House

1 edit
reply to whfsdude

said by whfsdude:

said by nightwalker:

Windows7 has a built-in 6to4 support that seems to be available on-demand. Comcast support for ipv6 will assign you a physical IP and isn't available nationwide yet.

6to4 doesn't work behind NAT. I think you're thinking of Teredo here.

Interesting. I am on a Windows XP PC behind a WNR1000v2-VC NAT router that is using the Comcast 6t04 relay, and IPv6 seems to be working just fine for me (with the MS Teredo explicitly disabled):





C:\>netsh int ipv6 show int
Querying active state...
 
Idx  Met   MTU    State         Name
---  ----  -----  ------------  -----
  7     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
 
C:\>netsh int ipv6 show teredo
Teredo Parameters
---------------------------------------------
Type                    : default
Server Name             : default
Client Refresh Interval : default
Client Port             : default
State                   : offline
Error                   : none
 
C:\>netsh int ipv6 show addr
Querying active state...
 
Interface 7: Local Area Connection
 
Addr Type  DAD State  Valid Life   Pref. Life   Address
---------  ---------- ------------ ------------ -----------------------------
Temporary  Preferred        37m11s        1m42s 2002:XXXX:XXXX:XXXX:,,,
Temporary  Deprecated       37m11s           0s 2002:XXXX:XXXX:XXXX:,,,
Public     Preferred        37m11s       27m11s 2002:XXXX:XXXX:XXXX:,,,
Link       Preferred      infinite     infinite fe80::XXXX:XXXX:XXXX:,,,
 
Interface 2: Automatic Tunneling Pseudo-Interface
 
Addr Type  DAD State  Valid Life   Pref. Life   Address
---------  ---------- ------------ ------------ -----------------------------
Link       Preferred      infinite     infinite fe80::5efe:10.224.87.199
Link       Preferred      infinite     infinite fe80::5efe:192.168.9.100
 
Interface 1: Loopback Pseudo-Interface
 
Addr Type  DAD State  Valid Life   Pref. Life   Address
---------  ---------- ------------ ------------ -----------------------------
Loopback   Preferred      infinite     infinite ::1
Link       Preferred      infinite     infinite fe80::1
 
C:\>tracert -6 ipv6.google.com
 
Tracing route to ipv6.l.google.com [2607:f8b0:4002:802::1012]
over a maximum of 30 hops:
 
  1     1 ms    <1 ms    <1 ms  2002:XXXX:XXXX:XXXX:,,,
  2    21 ms    21 ms    22 ms  2002:c058:6301::
  3    22 ms    21 ms    21 ms  ge-7-2-ur02.s3ndigital.ga.atlanta.comcast.net [2001:558:fe12:1::1]
  4    26 ms    24 ms    22 ms  xe-2-0-1-0-ar01.d1stonemtn.ga.atlanta.comcast.net [2001:558:140:22::1]
  5    46 ms    43 ms    59 ms  pos-2-14-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f73d::1]
  6    47 ms    46 ms    46 ms  pos-1-0-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f588::2]
  7    34 ms    33 ms    31 ms  2001:559::382
  8    59 ms    32 ms    31 ms  2001:4860::1:0:3f7
  9    33 ms    57 ms    52 ms  2001:4860::1:0:5db
 10    54 ms    67 ms    53 ms  2001:4860::1:0:489
 11   107 ms    52 ms    52 ms  2001:4860:0:1::164
 12    61 ms    52 ms    54 ms  atl14s08-in-x12.1e100.net [2607:f8b0:4002:802::1012]
 
Trace complete.
 
 


--
Some days you're the dog; some days you're the hydrant.

34764170

join:2007-09-06
Etobicoke, ON

said by 56885201:

Interesting. I am on a Windows XP PC behind a WNR1000v2-VC NAT router that is using the Comcast 6t04 relay, and IPv6 seems to be working just fine for me (with the MS Teredo explicitly disabled):

Your network setup is not setup as he described. It would if you have an IPv4 router (using NAT) with your IPv6 router sitting behind that or what is more common an individual host (Windows, an open source UNIX, etc.) host with a user wanting to use 6to4 through a router without IPv6 support and that will not work.


56885201
Ain't Nothin' But A Hound Dawg
Premium
join:2005-05-01
Dawg House

said by 34764170:

said by 56885201:

Interesting. I am on a Windows XP PC behind a WNR1000v2-VC NAT router that is using the Comcast 6t04 relay, and IPv6 seems to be working just fine for me (with the MS Teredo explicitly disabled):

Your network setup is not setup as he described. It would if you have an IPv4 router (using NAT) with your IPv6 router sitting behind that or what is more common an individual host (Windows, an open source UNIX, etc.) host with a user wanting to use 6to4 through a router without IPv6 support and that will not work.

My post was in response to the statement below that in no way describes any particular network topology other than being behind a NAT router:

said by whfsdude:

6to4 doesn't work behind NAT. I think you're thinking of Teredo here.

And, if you follow the post chain back, you will see that remark was a reply to another post that referenced the OP's network topology. The OP's network topology is very similar to mine (a NAT router using a 6to4 tunnel to reach Comcast's 6to4 relay).
--
Some days you're the dog; some days you're the hydrant.

34764170

join:2007-09-06
Etobicoke, ON

1 recommendation

said by 56885201:

My post was in response to the statement below that in no way describes any particular network topology other than being behind a NAT router:

said by whfsdude:

6to4 doesn't work behind NAT. I think you're thinking of Teredo here.

And, if you follow the post chain back, you will see that remark was a reply to another post that referenced the OP's network topology. The OP's network topology is very similar to mine (a NAT router using a 6to4 tunnel to reach Comcast's 6to4 relay).

When he says "behind NAT" and also mentions Teredo that does imply a particular network topology and it is not as you have described. His post was in reference to a particular setup of 6to4 which is not how you have things setup.


56885201
Ain't Nothin' But A Hound Dawg
Premium
join:2005-05-01
Dawg House

said by 34764170:

said by 56885201:

My post was in response to the statement below that in no way describes any particular network topology other than being behind a NAT router:

said by whfsdude:

6to4 doesn't work behind NAT. I think you're thinking of Teredo here.

And, if you follow the post chain back, you will see that remark was a reply to another post that referenced the OP's network topology. The OP's network topology is very similar to mine (a NAT router using a 6to4 tunnel to reach Comcast's 6to4 relay).

When he says "behind NAT" and also mentions Teredo that does imply a particular network topology and it is not as you have described. His post was in reference to a particular setup of 6to4 which is not how you have things setup.

You might want to consider going back and actually reading the posts in this thread, and see for yourself that the OP is running behind a NAT router with 6to4 enabled (just like me), and the OP's configuration is what this thread is about, not some imaginary network that only you see (and are discussing).

FWIW, since you obviously overlooked that post (and probably won't bother to look again), the OP's problem was fixed by enabling 6to4 instead of using auto config in the router (because the OP's connection does not yet have native IPv6 enabled):

said by Manco9:

Again thanks for the replies everyone! After putting the router on 6to4 instead of auto-detect yesterday I haven't lost ipv6 connectivity.

--
Some days you're the dog; some days you're the hydrant.


Mike Wolf

join:2009-05-24
Beachwood, NJ
kudos:3

1 recommendation

reply to NetDog

When is the Comcast speedtest site going to reflect the IPv6 change?



whfsdude
Premium
join:2003-04-05
Washington, DC
Reviews:
·Comcast
reply to 56885201

said by 56885201:

Interesting. I am on a Windows XP PC behind a WNR1000v2-VC NAT router that is using the Comcast 6t04 relay, and IPv6 seems to be working just fine for me (with the MS Teredo explicitly disabled):

I understand your router is doing 6to4 and announcing it (just like it would with ULA. or a unicast global).

My point was more to the fact that the poster had said Windows was using the built in 6to4 adapter. This is where Windows itself open a 6to4 tunnel. This is incorrect as it cannot be done behind NAT which should probably be pointed out so others browsing don't go enable 6to4 behind their router.


NetFixer
Snarl For The Camera Please
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage

1 edit

1 recommendation

reply to 34764170

said by 34764170:

said by 56885201:

My post was in response to the statement below that in no way describes any particular network topology other than being behind a NAT router:

said by whfsdude:

6to4 doesn't work behind NAT. I think you're thinking of Teredo here.

And, if you follow the post chain back, you will see that remark was a reply to another post that referenced the OP's network topology. The OP's network topology is very similar to mine (a NAT router using a 6to4 tunnel to reach Comcast's 6to4 relay).

When he says "behind NAT" and also mentions Teredo that does imply a particular network topology and it is not as you have described. His post was in reference to a particular setup of 6to4 which is not how you have things setup.

I think that you and Coon Dawg are just arguing semantics. I see your theoretical point, but the point that Coon Dawg is trying to make is that the OP is indeed running behind a Netgear router that is using 6to4 (enabling 6to4 in the router is what fixed the problem that triggered this thread).

--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower


56885201
Ain't Nothin' But A Hound Dawg
Premium
join:2005-05-01
Dawg House

1 recommendation

reply to whfsdude

said by whfsdude:

said by 56885201:

Interesting. I am on a Windows XP PC behind a WNR1000v2-VC NAT router that is using the Comcast 6t04 relay, and IPv6 seems to be working just fine for me (with the MS Teredo explicitly disabled):

I understand your router is doing 6to4 and announcing it (just like it would with ULA. or a unicast global).

My point was more to the fact that the poster had said Windows was using the built in 6to4 adapter. This is where Windows itself open a 6to4 tunnel. This is incorrect as it cannot be done behind NAT which should probably be pointed out so others browsing don't go enable 6to4 behind their router.

Ahh, OK. Thank you for the clarification.
--
Some days you're the dog; some days you're the hydrant.


Mike Wolf

join:2009-05-24
Beachwood, NJ
kudos:3
reply to NetDog

Not sure if this is considered an issue or not but I used to get an IPv6 address that had a lease time of 4 days which is the same length as my IPv4 address. Now the past few days I'm only getting a 60 minute lease time for IPv6. Anyone else seeing that?