dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
9

newview
Ex .. Ex .. Exactly
Premium Member
join:2001-10-01
Parsonsburg, MD

newview to whfsdude

Premium Member

to whfsdude

Re: [IPv6] IPv6 not implemented in my area yet?

said by whfsdude:

Just checking but what modem do you have?

Motorola SB5100
Is it necessary for the modem to be IPv6 capable?

owlyn
MVM
join:2004-06-05
Newtown, PA
Netgear CM2050V
Netgear RBRE960
Netgear RBSE960

owlyn

MVM

Change Manual Configuration to 6to4 Tunnel (assuming it's there, which I suspect it is). Everything else will probably fill in automatically. Your modem does not need to be IPV6 capable for this configuration. I use 6to4, which is what Comcast recommends, and it works perfectly with my Arris TM602G non-IPV6 capable modem. I get 10/10 scores on the Comcast IPV6 test site. My iPhone (which I connect by WiFi) gets an iIPV6 address from my router, as does my PC and work notebook. I don't think my TV does, as I think it is not IPV6 capable, but that doesn't matter, as my router will handle those issues.

NathanO
join:2008-08-21
Seattle, WA
Ubiquiti UniFi AP-AC-HD
Ubiquiti UDM-Pro

1 recommendation

NathanO

Member

I wouldn't really encourage the use of tunnels at this point, it will be soon enough that you'll have native IPv6. At this point, there is no advantage to running a tunnel unless you have some specific need for IPv6 only content.

OP: I believe you do need a modem that is marked IPv6 compatible on »mydeviceinfo.comcast.net ··· 1&sc=211

SHoTTa35
@optonline.net

SHoTTa35

Anon

Few things:

1 - You do need a better modem, you have an older modem that doesn't support, or well ISPs don't support IPv6 on it so you'll need one from the list above.

2 - Your area needs to have it too which it could but since you have the wrong modem you'll never know

3 - I have that modem too and you can use Hurricane Electric if you want IPv6. You wont get 6to4 with that router though as it's not one of the supported options. No big deal IMO. 6rd is supported though IIRC.

So with all that said, wait till you find out if IPv6 is available in your area, or you can check it kinda by finding out your CMTS MAC address (within your modem logs). From then if you have a CISCO CMTS then you don't have IPv6 at all and be done. IF it's Arris then maybe - If so though you should in 90 days or something according to Comcast. So on that day with the right modem and with your router set to Automatic, you'll just get IPv6 oneday without even doing a thing.

whfsdude
Premium Member
join:2003-04-05
Washington, DC

whfsdude

Premium Member

said by SHoTTa35 :

Few things:

1 - You do need a better modem, you have an older modem that doesn't support, or well ISPs don't support IPv6 on it so you'll need one from the list above.

You should upgrade the modem to at least a DOCSIS 3 model. Even though there is a spec via cable labs, I've yet to hear of any DOCSIS 2 users getting v6.

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

EG to NathanO

Premium Member

to NathanO
said by NathanO:

I wouldn't really encourage the use of tunnels at this point, it will be soon enough that you'll have native IPv6. At this point, there is no advantage to running a tunnel unless you have some specific need for IPv6 only content.

Heartily agree with this ! Tunnels add overhead.

owlyn
MVM
join:2004-06-05
Newtown, PA
Netgear CM2050V
Netgear RBRE960
Netgear RBSE960

owlyn

MVM

said by EG:

said by NathanO:

I wouldn't really encourage the use of tunnels at this point, it will be soon enough that you'll have native IPv6. At this point, there is no advantage to running a tunnel unless you have some specific need for IPv6 only content.

Heartily agree with this ! Tunnels add overhead.

Not sure what kind of overhead you are referring to. Here are my results using 6to4 tunnel. Anything faster would pretty much have to break the speed of light:

Test with IPv4 DNS record
ok (0.286s) using ipv4

Test with IPv6 DNS record
ok (0.298s) using ipv6

Test with Dual Stack DNS record
ok (0.215s) using ipv4

Test for Dual Stack DNS and large packet
ok (0.143s) using ipv4

Test IPv4 without DNS
ok (0.138s) using ipv4

Test IPv6 without DNS
ok (0.141s) using ipv6

Test IPv6 large packet
ok (2.427s) using ipv6

Test if your ISP's DNS server uses IPv6
ok (0.227s) using ipv4

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

NetFixer

Premium Member

said by owlyn:

said by EG:

said by NathanO:

I wouldn't really encourage the use of tunnels at this point, it will be soon enough that you'll have native IPv6. At this point, there is no advantage to running a tunnel unless you have some specific need for IPv6 only content.

Heartily agree with this ! Tunnels add overhead.

Not sure what kind of overhead you are referring to. Here are my results using 6to4 tunnel. Anything faster would pretty much have to break the speed of light:

...

Try running these tests:


C:\>tracert www.google.com
 
Tracing route to www.l.google.com [74.125.134.103]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  ap2.dcs-net [192.168.9.10]
  2    <1 ms    <1 ms    <1 ms  host6.dcs-net.net [75.146.8.46]
  3    30 ms    20 ms    34 ms  96.191.160.1
  4     9 ms     8 ms     8 ms  xe-4-0-0-0-sur02.murfreesboro.tn.nash.comcast.net [68.85.50.129]
  5    11 ms    10 ms    11 ms  xe-5-1-3-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105]
  6    20 ms    19 ms    18 ms  pos-2-2-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.90.189]
  7    21 ms    20 ms    20 ms  pos-0-3-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.87.134]
  8    19 ms    18 ms    19 ms  75.149.231.86
  9    18 ms    19 ms    19 ms  64.233.174.2
 10    19 ms    19 ms    19 ms  66.249.94.6
 11    20 ms    19 ms    21 ms  72.14.239.127
 12     *        *        *     Request timed out.
 13    20 ms    20 ms    20 ms  gg-in-f103.1e100.net [74.125.134.103]
 
Trace complete.
 
C:\>tracert -6 www.google.com
 
Tracing route to www.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    24 ms    21 ms    37 ms  2002:c058:6301::
  3    21 ms    21 ms    20 ms  ge-7-2-ur02.s3ndigital.ga.atlanta.comcast.net [2001:558:fe12:1::1]
  4    22 ms    23 ms    22 ms  xe-2-0-1-0-ar01.d1stonemtn.ga.atlanta.comcast.net [2001:558:140:22::1]
  5    46 ms    47 ms    48 ms  pos-3-4-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f78b::1]
  6    45 ms    45 ms    45 ms  pos-1-6-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f5e0::2]
  7    33 ms    33 ms    33 ms  2001:559::382
  8    33 ms    34 ms    33 ms  2001:4860::1:0:3f7
  9    53 ms    52 ms    78 ms  2001:4860::1:0:5db
 10    92 ms    64 ms    56 ms  2001:4860::8:0:2f04
 11    52 ms    54 ms    58 ms  2001:4860::2:0:a7
 12    64 ms    56 ms    52 ms  2001:4860:0:1::109
 13    54 ms    54 ms    53 ms  yx-in-x63.1e100.net [2001:4860:800a::63]
 
Trace complete.
 
 


»ipv6-test.com/speedtest/


Madtown
Premium Member
join:2008-04-26
93637-2905

Madtown to whfsdude

Premium Member

to whfsdude
said by whfsdude:

said by SHoTTa35 :

Few things:

1 - You do need a better modem, you have an older modem that doesn't support, or well ISPs don't support IPv6 on it so you'll need one from the list above.

You should upgrade the modem to at least a DOCSIS 3 model. Even though there is a spec via cable labs, I've yet to hear of any DOCSIS 2 users getting v6.

»www.amazon.com/Motorola- ··· 04XC6GJ0

dslcreature
Premium Member
join:2010-07-10
Seattle, WA

dslcreature to SHoTTa35

Premium Member

to SHoTTa35
said by SHoTTa35 :

3 - I have that modem too and you can use Hurricane Electric if you want IPv6. You wont get 6to4 with that router though as it's not one of the supported options. No big deal IMO. 6rd is supported though IIRC.

Until IPv6 comes to town the HE tunnels are amazing. Latency soo low I have trouble believing it's a "tunnel".


Pinging www.l.google.com [74.125.127.103] with 32 bytes of data:
Reply from 74.125.127.103: bytes=32 time=22ms TTL=52
Reply from 74.125.127.103: bytes=32 time=23ms TTL=52

Pinging www.l.google.com [2001:4860:8005::69] with 32 bytes of data:
Reply from 2001:4860:8005::69: time=24ms
Reply from 2001:4860:8005::69: time=23ms