dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1352

EmoHobo
join:2010-07-16

EmoHobo

Member

[IPv6] Did my Modem suddenly become IPv6 enabled?

The typical style IP address has been changed to something like 2607:f8b0:4009:809:1000

So what does this mean for devices I have networked into my system and also why is my first hop now suddenly about 30 ms compared to the >1 ms it was before, this is all new to me so sorry about the dumb questions.

Anno
@98.244.224.x

1 recommendation

Anno

Anon

[IPv6] Re: Did my Modem suddenly become IPv6 enabled?

That is IPv6 as you say.

Don't worry about what your first hop says.

What does your final hop say vs. before?

Ping ipv4.google.com and ipv6.google.com

Are the results within 5ms of each other? If so you are fine.

If not it could just be they are taking different routes which happens on the internet. Not ALL your data will ride IPv6, only places that support it.

For example if you play games nothing will change, they are all still IPv4 etc.

EmoHobo
join:2010-07-16

EmoHobo

Member

Oh thank you for informing me, there was a difference, but if it won't effect gaming, that's all I really care about.

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

1 edit

2 recommendations

NetFixer to EmoHobo

Premium Member

to EmoHobo

Re: Did my Modem suddenly become IPv6 enabled?

said by EmoHobo:

why is my first hop now suddenly about 30 ms compared to the >1 ms it was before,

Your first hop should still be to your local router, and using IPv6 vs IPv4 should not significantly change the transit time to a local router. What brand/model of modem and router are you using? Is your "modem" actually your router as well? Try doing a tracert (traceroute if you don't run Windows) to ipv4.google.com and ipv6.google.com and see what your first hop transit time looks like. Here is what it looks like from the Windows PC I am using to make this post:
C:\>tracert ipv4.google.com
 
Tracing route to ipv4.l.google.com [74.125.196.139]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  gw1.dcs-net.lan [192.168.9.254]
  2     9 ms     9 ms     9 ms  107.3.232.1
  3     8 ms     8 ms     8 ms  xe-10-0-0-32767-sur04.murfreesboro.tn.nash.comcast.net [68.86.151.53]
  4    13 ms    10 ms    10 ms  xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105]
  5    19 ms    19 ms    19 ms  he-3-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.94.69]
  6    24 ms    18 ms    19 ms  as15169-1-c.56marietta.ga.ibone.comcast.net [23.30.206.146]
  7    18 ms    17 ms    17 ms  72.14.233.56
  8    17 ms    17 ms    17 ms  66.249.94.24
  9    18 ms    17 ms    17 ms  209.85.248.31
 10     *        *        *     Request timed out.
 11    18 ms    18 ms    17 ms  yk-in-f139.1e100.net [74.125.196.139]
 
Trace complete.
 
C:\>tracert ipv6.google.com
 
Tracing route to ipv6.l.google.com [2607:f8b0:4002:c07::66]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  2601:5:1f00:3b01:1e7e:e5ff:fe4c:e6ff
  2     8 ms     8 ms     9 ms  2001:558:6016:3e::1
  3     8 ms     8 ms     8 ms  xe-10-0-0-32767-sur03.murfreesboro.tn.nash.comcast.net [2001:558:162:93::1]
  4    10 ms     9 ms     9 ms  xe-2-0-9-0-ar03.nashville.tn.nash.comcast.net [2001:558:160:57::1]
  5    22 ms    23 ms    23 ms  he-1-5-0-0-11-cr01.seattle.wa.ibone.comcast.net [2001:558:0:f790::1]
  6    23 ms    21 ms    22 ms  he-0-10-0-0-pe04.350ecermak.il.ibone.comcast.net [2001:558:0:f8cc::2]
  7    21 ms    21 ms    21 ms  as15169-5-c.350ecermak.il.ibone.comcast.net [2001:559::37a]
  8    37 ms    23 ms    22 ms  2001:4860::1:0:92e
  9    22 ms    21 ms    22 ms  2001:4860::8:0:5901
 10    29 ms    30 ms    37 ms  2001:4860::8:0:52bb
 11    30 ms    29 ms    29 ms  2001:4860::2:0:878b
 12     *        *        *     Request timed out.
 13    30 ms    33 ms    29 ms  yk-in-x66.1e100.net [2607:f8b0:4002:c07::66]
 
Trace complete.
 
And you will notice that the first hop transit time did not change because all connections still go through the same local router. The second outbound hop also did not change significantly because I still go through the same Comcast CMTS router. In general, there should not be a significant difference between IPv4 and IPv6 transit times when the devices are using the same physical equipment; and what you are reporting does not sound right for a native dual stack IPv4/IPv6 connection.

If you go to »test-ipv6.com/ do you get a 10/10 status report? Does the test result page show any message about using an IPv6 tunnel, or that IPv4 and IPv6 are not using the same ISP? Here are my results:



EmoHobo
join:2010-07-16

1 recommendation

EmoHobo

Member

Re: [IPv6] Did my Modem suddenly become IPv6 enabled?

Click for full size
It looks like the ipv6 is for whatever reason skipping the first step, which is in my case a modem and router all in one gateway, it is a Technicolor TC8305c

NetFixer
From My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU

2 edits

1 recommendation

NetFixer

Premium Member

said by EmoHobo:

It looks like the ipv6 is for whatever reason skipping the first step, which is in my case a modem and router all in one gateway, it is a Technicolor TC8305c

I can not imagine what the TC8305c (or your PC's IPv6 stack) could be doing with a native IPv6 connection that would make the TC8305c invisible on an outbound traceroute (you should at least see a *  *  *  Request timed out message). And since I can't see the results of a traceroute from your PC (or the PC's or the gateway's IPv6 config/status), I am not going to attempt to make any guesses, except to ask if possibly you are running the TC8305c in bridge mode (since I can't see your PC's IPv6 address, I have no way of knowing if it got it from your local TC8305C router, or directly from Comcast's DHCP server)

All I can suggest is that if you start to notice any significant problems now that IPv6 has been activated in your gateway, you can either disable IPv6 in attached devices or look for a way to disable it in the gateway (normally disabling IPv6 in a router is easy, but Comcast likes to make things difficult or impossible for users of their leased gateway boxes).