|
uniqs
20 |
|
 |
|
 plencnerb
Premium Member
join:2000-09-25
53403-1242 |
to NetFixer
Re: [IPv6] IPv6 not implemented in my area yet?Ok, I get it now!  But, in some way, the cable modem itself must still be able to "pass" along to whatever device is connected to it (router like Netgear or Linksys, Windows Computer, Mac Computer, etc) the proper IP. If the cable modem itself cannot do that for an IPv6 IP, then you would have to replace the cable modem for one that can, correct? That is really the basis of my question, and I think what everyone is trying to figure out. I also agree that Comcast may not have "properly" done that on their "approved" cable modem list. Of course, this is all moot if Comcast has not rolled out IPv6 in your area yet. As far as I can tell, they have not for my area. I had NetDog  look into that for me, and (at least back on the 5th of June), they had not done so yet. But, I think what everyone is trying to figure out is what they, as customers of Comcast, have to modify or change on their end to get IPv6 to work in their own world once Comcast does roll it out. Questions like 1) Do I need to buy (or swap) my modem? 2) Do I need to replace my router, or update its firmware? Or, if you are running a Linux router (like I am...Smoothwall), do I need to apply some kind of mod or patch)? 3) What modifications do I need to make to my devices, and are they even supported? For some, this may require some money...if said user purchased a modem 5 years ago, and it needs to be replaced...that is money to spend..if they also have to replace their 10 year old router..and, if they have a computer running Windows 98, they may need to replace that, purchase a new OS, and so on. I would hate to find out that what I have currently does not work once things are finally all switched over. Then, trying to figure out what broke after the fact (Hey..I cannot connect..WTF!) would be a lot harder (I would think) then doing the up-front work to figure out if what I have WILL work once things are in place. If I don't have to replace my cable modem, or router, and just modify a few settings, then I'm good. However, if I do need to go purchase a new router (mine may be to old, and not getting an updated firmware from the MFG), I would like to know that ahead of time. --Brian | |  NetFixerFrom My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro
Pace 5268AC
TRENDnet TEW-829DRU
1 recommendation |
NetFixer
Premium Member
2012-Jun-19 5:23 am
A simple cable modem is a layer 2 device and media converter, it does not understand IPv4 or IPv6 for traffic passed between your network and the Internet anymore than a simple layer2 switch does. Do a traceroute to an internet server (such as www.google.com) from a device on your network, does your cable modem show up in that traceroute report? I would demonstrate that for you with both IPv4 and IPv6 examples, except that my "modem" does show up because it is a cable gateway, not a simple bridge. To hell with it, shown below are IPv4 and IPv6 traceroutes to www.google.com from the server that i am currently doing some maintenance on (perhaps it might still be useful):
C:\>tracert www.google.com
Tracing route to www.l.google.com [74.125.137.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms host6.dcs-net.net [75.146.8.46]
2 32 ms 20 ms 29 ms 96.191.160.1
3 9 ms 8 ms 9 ms xe-4-0-0-0-sur01.murfreesboro.tn.nash.comcast.net [68.85.50.125]
4 10 ms 10 ms 10 ms xe-3-1-2-0-ar03.nashville.tn.nash.comcast.net [68.85.174.17]
5 12 ms 127 ms 60 ms ae-3-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.148.69]
6 21 ms 29 ms 29 ms pos-2-1-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.90.101]
7 47 ms 18 ms 20 ms pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.86.86]
8 33 ms 19 ms 19 ms 75.149.231.86
9 18 ms 19 ms 19 ms 64.233.174.2
10 20 ms 18 ms 19 ms 66.249.94.6
11 18 ms 19 ms 19 ms 209.85.248.31
12 * * * Request timed out.
13 18 ms 20 ms 20 ms yh-in-f99.1e100.net [74.125.137.99]
Trace complete.
C:\>tracert -6 www.google.com
Tracing route to www.l.google.com [2001:4860:800a::67]
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 21 ms 21 ms 22 ms ge-7-2-ur02.s3ndigital.ga.atlanta.comcast.net [2001:558:fe12:1::1]
4 22 ms 24 ms 21 ms xe-2-0-1-0-ar01.d1stonemtn.ga.atlanta.comcast.net [2001:558:140:22::1]
5 46 ms 47 ms 47 ms pos-2-14-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f73d::1]
6 44 ms 46 ms 58 ms pos-1-1-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f589::2]
7 79 ms 33 ms 33 ms 2001:559::382
8 40 ms 34 ms 33 ms 2001:4860::1:0:3f7
9 68 ms 53 ms 144 ms 2001:4860::1:0:5db
10 56 ms 52 ms 52 ms 2001:4860::8:0:2f04
11 53 ms 51 ms 52 ms 2001:4860::2:0:a7
12 62 ms 53 ms 54 ms 2001:4860:0:1::10b
13 54 ms 53 ms 54 ms yx-in-x67.1e100.net [2001:4860:800a::67]
Trace complete.
The first hop for the IPv4 traceroute above is my SMCD3G-CCR cable gateway, and it shows up because it is a router, not just a simple bridge modem. That hop would likely be your Smoothwall box for your traceroutes. The second hop is Comcast's gateway for my connection. The first hop for the IPv6 traceroute above is my Comcast supplied Netgear WNR1000v2-VC wireless router which currently acts as my IPv4 NAT router for non server boxes, and as my IPv6 gateway for all devices. The second hop is Comcast's 6to4 relay server (which I must use because Comcast does not yet offer native IPv6 to my location). OK, shown below here are the same traceroutes from a Windows XP workstation (that I should have been using to do this anyway). Note that the only differences are that the IPv4 traceroute goes through the Netgear router, and then through the SMC router, and the Google IP addresses are different because Google uses load balancing:
C:\>tracert www.google.com
Tracing route to www.l.google.com [74.125.130.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 38 ms 19 ms 29 ms 96.191.160.1
4 10 ms 10 ms 9 ms xe-4-0-0-0-sur02.murfreesboro.tn.nash.comcast.net [68.85.50.129]
5 12 ms 10 ms 11 ms xe-5-1-3-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105]
6 18 ms 18 ms 19 ms pos-2-2-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.90.189]
7 19 ms 24 ms 23 ms pos-0-11-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.186]
8 18 ms 19 ms 18 ms 75.149.231.86
9 17 ms 18 ms 18 ms 72.14.239.100
10 19 ms 21 ms 20 ms 66.249.94.20
11 19 ms 19 ms 18 ms 209.85.254.247
12 * * * Request timed out.
13 19 ms 63 ms 18 ms gh-in-f103.1e100.net [74.125.130.103]
Trace complete.
C:\>tracert -6 www.google.com
Tracing route to www.l.google.com [2001:4860:800a::93]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 2002:4b92:829:0:a221:b7ff:fe9c:602
2 45 ms 21 ms 21 ms 2002:c058:6301::
3 22 ms 25 ms 20 ms ge-7-2-ur02.s3ndigital.ga.atlanta.comcast.net [2001:558:fe12:1::1]
4 23 ms 23 ms 21 ms xe-2-0-1-0-ar01.d1stonemtn.ga.atlanta.comcast.net [2001:558:140:22::1]
5 46 ms 49 ms 52 ms pos-2-12-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f73b::1]
6 46 ms 44 ms 43 ms pos-1-1-0-0-pe01.350ecermak.il.ibone.comcast.net [2001:558:0:f589::2]
7 32 ms 32 ms 35 ms 2001:559::382
8 34 ms 32 ms 34 ms 2001:4860::1:0:3f7
9 53 ms 54 ms 58 ms 2001:4860::1:0:5db
10 53 ms 51 ms 53 ms 2001:4860::8:0:2f04
11 59 ms 53 ms 53 ms 2001:4860::2:0:a7
12 58 ms 54 ms 56 ms 2001:4860:0:1::10b
13 52 ms 87 ms 53 ms yx-in-x93.1e100.net [2001:4860:800a::93]
Trace complete.
Perhaps my point that a standard cable modem does not show up in a traceroute is somewhat diluted since my cable "modem" does show up (but what shows up is the router's WAN IP address, not a cable modem IP address). But believe me, if I were using a cable modem instead of a cable gateway box, it would not show up, and it should not show up in your traceroutes. I don't specifically know what versions of Smoothwall do or don't support Comcast's DHCPv6 implementation, but you could probably start a new thread asking that question and get answers from someone using it with native IPv6 (since that is somewhat unrelated to this thread's topic). | | plencnerb
Premium Member
join:2000-09-25
53403-1242 |
NetFixer, I understood what you said about a Cable Modem being just a bridge. You did not need to show the trace route to me as you did. But, thanks for sharing anyway! And yes, any questions I have about my router I'll post in another thread, as that is off topic here. My question (and you did answer it) was with the cable modem specifically (and one that is not a combo cable modem / router or cable modem / wireless gateway). Are there cable modems out there that could have problems passing a IPv6 IP on to the device that is requesting it? From what you told me, the answer is no, as they are just a simple bridge...whatever data comes in to the Cable Modem via the coax will be passed (without issue) through the cable modem, and out the WAN port to whatever device is connected to it. With that being said, this statement is then true, correct? "It does not matter at all what cable modem you have as long as Comcast has it enabled in your area, as its not the cable modem that pulls an IP(be it an IPv4 IP or IPv6 IP)." If that statement is true, then why all the talk about "Does my cable modem support IPv6", and why has Comcast put up a page showing which Cable Modems "support" IPv6 with that checkmark? Are they just trying to confuse people, or force people to upgrade to new hardware, when they really don't need to? --Brian | | NetFixerFrom My Cold Dead Hands
Premium Member
join:2004-06-24
The Boro Netgear CM500
Pace 5268AC
TRENDnet TEW-829DRU
2 recommendations |
NetFixer
Premium Member
2012-Jun-19 9:28 am
My opinion would be that any cable modem that syncs and is supported by Comcast should be able to work with Comcast's DHCPv6 simply because as a layer 2 device it should not know or care what protocol is passing through it. Having said that, I certainly can not guarantee you that every cable modem would indeed function that way, because even though their primary function might be as a layer 2 device, there might be some internal functions that interact with the management interface that could impair its Internet usage. Plus, I suspect that in the not so distant future, Comcast may start requiring all modems to have an IPv6 management interface (since that is one big reason that Comcast is pushing IPv6). As for exactly what criterion Comcast uses for providing an IPv6 checkmark on their supported devices page, you will have to wait for a Comcast employee in the know for that answer. My best guess is that their primary criterion is management interface IPv6 compatibility, and they want to encourage customers to buy their own modems that have an IPv6 management interface, so that Comcast can pass that expense to the customer (and by indirectly implying that the modem must have the IPv6 checkmark, this goal will be easier to achieve). As always, [disclaimer]YMMV[/disclaimer].  | | |  jjmb
join:2009-12-01
USA |
to plencnerb
said by plencnerb:Ok, I get it now!
But, in some way, the cable modem itself must still be able to "pass" along to whatever device is connected to it (router like Netgear or Linksys, Windows Computer, Mac Computer, etc) the proper IP. If the cable modem itself cannot do that for an IPv6 IP, then you would have to replace the cable modem for one that can, correct?
[jjmb] if your modem does not currently support IPv6 you may need to replace the same. Like I said in an early post we work regularly to update this list based on available firmware from our vendors.
That is really the basis of my question, and I think what everyone is trying to figure out. I also agree that Comcast may not have "properly" done that on their "approved" cable modem list.
Of course, this is all moot if Comcast has not rolled out IPv6 in your area yet. As far as I can tell, they have not for my area. I had NetDog look into that for me, and (at least back on the 5th of June), they had not done so yet.
But, I think what everyone is trying to figure out is what they, as customers of Comcast, have to modify or change on their end to get IPv6 to work in their own world once Comcast does roll it out.
Questions like
1) Do I need to buy (or swap) my modem?
[jjmb] see above.
2) Do I need to replace my router, or update its firmware? Or, if you are running a Linux router (like I am...Smoothwall), do I need to apply some kind of mod or patch)?
[jjmb] router upgrades are likely required. We publish a list that we have tested, however, I get email often from folks who have other makes and models that work fine.
3) What modifications do I need to make to my devices, and are they even supported?
[jjmb] most popular operating systems support IPv6, Windows 7/8/Vista, MAC OS X Lion/Snow Leopard, Linux. *BSD. There is different functionality based on the OS.
For some, this may require some money...if said user purchased a modem 5 years ago, and it needs to be replaced...that is money to spend..if they also have to replace their 10 year old router..and, if they have a computer running Windows 98, they may need to replace that, purchase a new OS, and so on.
I would hate to find out that what I have currently does not work once things are finally all switched over. Then, trying to figure out what broke after the fact (Hey..I cannot connect..WTF!) would be a lot harder (I would think) then doing the up-front work to figure out if what I have WILL work once things are in place. If I don't have to replace my cable modem, or router, and just modify a few settings, then I'm good. However, if I do need to go purchase a new router (mine may be to old, and not getting an updated firmware from the MFG), I would like to know that ahead of time.
--Brian
| |
|
