 JTCAlways Mount A Scratch Monkey join:2002-01-09 USA | It's about time!
W00t!
Just threw my hat into the ring.
HE works well for this, but it would be nice to not have to run my v6 traffic out through a tunnel. -- All hardware sucks, all software sucks, some just suck more than others | |
|
 |  Reviews:
·Comcast
| Re: It's about time! said by JTC:W00t! Just threw my hat into the ring. HE works well for this, but it would be nice to not have to run my v6 traffic out through a tunnel. Agreed on HE (I started with HE; now I use SixxS' AICCU, primarily because of the direct support by 'buntu for AICCU).
The reason we have to use tunnels is due to a lack of public Teredo servers (Windows XP and later includes a native dual IPv4/IPv6 stack starting with XP's Service Pack 2; Teredo is the preferred method for V6-within-V4 tunnels in XP, Vista, or 7, though all three can support native/pure V6). There is support in third-party router firmware (notably OpenWRT, especially with the X-WRT extensions) for configuring residential routers as tunnel endpoints (either HE or SixxS) and creating a dual-stack home LAN (my WRT54GS is configured in this fashion). With the router handling things, as long as the OS in question supports V6 (Windows XP and later, Linux 2.6.x kernels and newer, Solaris/OpenSolaris, most BSDs, and MacOS 10.4 and newer) you're ready to rock. | |
|
 |  |  |
 |  |
 Reviews:
·Comcast
| Well, well, well! This actually confirms several announcements by Comcast over the past six months regarding their plans for IPv6. The problem with IPv6 deployment outside of business is non-computer devices (game consoles in particular, but also including MIDs) that are non-IPv6-compliant/ready.
I signed up for the trial, as I've been kicking around IPv6 here for almost a year (first via Hurricane Electric's free tunnelbroker, and now with SixxS' free tunnel service). | |
|
 |  | | Re: Well, well, well! What is likely to happen is that your home router will be IPv6 but will still use IPv4 on the interior side. That will make the transition easier for consumers. Still, we would all need to buy a router with that capability. | |
|
 |  |  Reviews:
·Comcast
| Re: Well, well, well! said by jjeffeory:What is likely to happen is that your home router will be IPv6 but will still use IPv4 on the interior side. That will make the transition easier for consumers. Still, we would all need to buy a router with that capability. That capability is in quite a few home routers today (albeit with third-party firmware for the most part), including several routers from Linksys and Netgear (including some models supplied to Comcast as part of the Wireless Networking promotion, and several older routers, such as the WRT54GS V.2), so that is mostly a non-issue. The computers are even less of an issue, as I pointed out. | |
|
 |  |  |  1 edit | Re: Well, well, well! It may be in some routers, but the majority of routers older than a few years aren't going to have this feature. The last time I bought a router was 5 or so years ago. The firmware has been updated several times, but there's no ipv6 support. I dunno, some people just don't want to keep upgrading ALL of their equipment every 3 years or so. Most people buy a tv or other consumer electronic device and keep it for at least 10 or so years... They expect it to work for a very long time and don't want to keep giving corporations money for "the same thing" ( from their perspective). | |
|
 |  |  |  |  Reviews:
·Comcast
| Re: Well, well, well! If you are referring to the Linksys WRT54GS, it supports IPv6 tunnels, but not with Linksys firmware. The WRT54G and GS (those that do NOT run VxWorks) can alternatively run Tomato, DD-WRT, or OpenWRT firmware, all of which support IPv6 (I have a V.2 GS that I personally upgraded to OpenWRT; the router itself dates to 2005, but the firmware is less than two months old). | |
|
 |  |  jjmb join:2009-12-01 USA | said by jjeffeory:What is likely to happen is that your home router will be IPv6 but will still use IPv4 on the interior side. That will make the transition easier for consumers. Still, we would all need to buy a router with that capability. Actually one of our trials in Phase #2, the native, dual stack will leverage home routers/gateways that support native, dual stack into the home not just to the edge of the home.
As we approach this phase will share additional information.
John | |
|
 |  |  |
 | | way to go comcast! as much as I hate the thought of actually going to comcast I like the speed and the thought that they are actually playing with IPv6 -- sbcglobal.net speedtest result 11/11/09 - 5256kbps | |
|
 |  r81984Fair and BalancedPremium join:2001-11-14 Katy, TX | Re: way to go comcast! IPv6 provides you with no extra benefit as a customer. Don't forget they have a 250GB a month cap. -- Republicans: less fiscally conservative than that other party. | |
|
 |  |  |
 |  |  dvd536as Mr. Pink as they comePremium join:2001-04-27 Phoenix, AZ kudos:4 | said by r81984:IPv6 provides you with no extra benefit as a customer. Don't forget they have a 250GB a month cap. So does IPv4  -- When I gez aju zavateh na nalechoo more new yonooz tonigh molinigh - Ken Lee | |
|
 |  |  brad join:2007-09-06 Etobicoke, ON | said by r81984:IPv6 provides you with no extra benefit as a customer. I'm a customer and it benefits me.
You fail. | |
|
 |  |  |  r81984Fair and BalancedPremium join:2001-11-14 Katy, TX Reviews:
·AT&T U-Verse
·AT&T DSL Service
·row44
1 edit | Re: way to go comcast! said by brad:said by r81984:IPv6 provides you with no extra benefit as a customer. I'm a customer and it benefits me. You fail. Please tell me how?? What benefit do you get over IPv4? -- Republicans: less fiscally conservative than that other party. | |
|
 |  |  |  |  | | Re: way to go comcast! No More NAT and public IPs for all your devices. | |
|
 |  |  |  |  |  r81984Fair and BalancedPremium join:2001-11-14 Katy, TX Reviews:
·AT&T U-Verse
·AT&T DSL Service
·row44
1 edit | Re: way to go comcast! said by Napsterbater:No More NAT and public IPs for all your devices. When I had comcast I had a public IP. Comcast did not use NAT. I had NAT on my home network which was not a problem at all.
Now we will see if comcast will give static subnets which will take away their current revenue source for making you pay extra for static IPs. If they have dynamic subnets then your home network will be screwed if you wanted to use static IP address. You will have to use IPv4 behind a router to be able to keep static IPs on your home network.
I could see them making you pay extra for static subnet to get static IPs on IPv6 which means if you want static IPs on your LAN you will be forced to pay. -- Republicans: less fiscally conservative than that other party. | |
|
 |  |  |  |  |  |  Reviews:
·VOIPo
·Windstream
·BroadVoice
| Re: way to go comcast! With IPv6 Every device on your LAN will get a Public IP.
No More port forwarding.
Now there is two way it could be implemented.
1. You have a router (or the modem act as the router) and it gets a "WAN" IP and then you have your own subnet
or
2. you hook up with a switch and all you devices get IPs that way.
Thanks to link local address you can have you LAN and WAN on the same broadcast domain. -- ASUS M4A79T Deluxe | AMD Phenom II x3 720 BE AM3 w/4 Cores @ 3.41Ghz(OC) | 4Gb DDR3 Memory @ 1600mhz | Sapphire ATI HD4870 1GB 800mhz/1000mhz(OC) | 2x500GB HDD's Raid 0 | Windows 7 Ultimate x64 Build 7600 (RTM) | Windstream DSL 12m (14.9m Sync)/766k | |
|
 |  |  |  |  |  |  |  |
 |  |  |  |  |  |  |  |  Reviews:
·VOIPo
·Windstream
·BroadVoice
| Re: way to go comcast! You do have local IPs they are called Link local IPs They only work in the same broadcast domain though so a tad different then the LAN IPs of IPv4, since you can not route them at all.
AFAIK there is no way to have a dynamic subnet behind a router that would be assigned from the provider, It would have to be a static subnet, Altough from you ISP's address pool.
but if you use a switch only (or a transparent firewall) all the local client could receive IPs via DHCPv6 or auto-configuration.
Again depend on how they implement it. -- ASUS M4A79T Deluxe | AMD Phenom II x3 720 BE AM3 w/4 Cores @ 3.41Ghz(OC) | 4Gb DDR3 Memory @ 1600mhz | Sapphire ATI HD4870 1GB 800mhz/1000mhz(OC) | 2x500GB HDD's Raid 0 | Windows 7 Ultimate x64 Build 7600 (RTM) | Windstream DSL 12m (14.9m Sync)/766k | |
|
 |  |  |  |  |  |  |  |  |  jjmb join:2009-12-01 USA | Re: way to go comcast! said by Napsterbater:You do have local IPs they are called Link local IPs They only work in the same broadcast domain though so a tad different then the LAN IPs of IPv4, since you can not route them at all. AFAIK there is no way to have a dynamic subnet behind a router that would be assigned from the provider, It would have to be a static subnet, Altough from you ISP's address pool. but if you use a switch only (or a transparent firewall) all the local client could receive IPs via DHCPv6 or auto-configuration. Again depend on how they implement it. I posted something a few minutes ago. There is a standardized mechanism that providers can leverage to delegate IPv6 prefixes to subscribers/users. RFC3633 defines that mechanism in case you are interested. This mechanism does in fact leverage DHCPv6 (RFC3315) to delegate IPv6 prefixes using the providers DHCPv6 infrastructure.
John | |
|
 |  |  |  |  |  |  |  |  |  2 edits | Re: way to go comcast! Ah did not know that was part on DHCPv6, I stand corrected.
Thanks for the info. | |
|
 |  |  |  |  |  |  |  jjmb join:2009-12-01 USA | said by Napsterbater:With IPv6 Every device on your LAN will get a Public IP. No More port forwarding. Now there is two way it could be implemented. 1. You have a router (or the modem act as the router) and it gets a "WAN" IP and then you have your own subnet or 2. you hook up with a switch and all you devices get IPs that way. Thanks to link local address you can have you LAN and WAN on the same broadcast domain. In cases where a single standalone CPE like a PC running Vista/7 is connected to a cable modem directly the PC would likely gets IPv6 address just like it gets its IPv4 address from the ISP DHCP server.
In the cases where the home network is IPv6 capable (native, dual stack support in the home router/gateway) the router/gateway could be delegated an IPv6 prefix (RFC3633) for use within the home.
John | |
|
 |  |  |  |  |  |  ThrowDemsOutIf you can't convince 'em, confuse 'emPremium join:2002-03-03 Mullica Hill, NJ kudos:4 | said by r81984: You will have to use IPv4 behind a router to be able to keep static IPs on your home network. Initially, that will be what the large majority of customers will continue to do. Use a router that will handle IPV4 on home network side and IPV6 on the Comcast Network side. | |
|
 |  |  |  |  |  | | I have to agree with r81984. it changes nothing worth talking about for me. I don't even know if I was all my devices with public ip's. Do you have NAT problems or your router or something? | |
|
 |  |  |  |  |
 |  |  AVonGaussPremium,MVM join:2007-11-01 Boynton Beach, FL | said by r81984:IPv6 provides you with no extra benefit as a customer. The fact that IPv6 does not use any type of NAT scheme alone makes it beneficial to customers. | |
|
 |  |  |  jjmb join:2009-12-01 USA | Re: way to go comcast! said by AVonGauss:said by r81984:IPv6 provides you with no extra benefit as a customer. The fact that IPv6 does not use any type of NAT scheme alone makes it beneficial to customers. Not requiring NAT is often cited as one of the main benefits of IPv6.
John | |
|
 swhx7Premium join:2006-07-23 Elbonia Reviews:
·RoadRunner Cable
| kudos to comcast It looks like they're doing this right. I've always heard bad things about Comcast, but here they have informative FAQs and offer to cooperate with customers to make this necessary change work.
On my ISP, Roadrunner:
said by search on RR site : Key words: ipv6 Please refine your search and try again - no matches found.
| |
|
 |  | | Re: kudos to comcast Good work, Comcast ! Thanks. | |
|
 |  |  |
 |  |
 |  |  RobIn Deo speramus, God Bless the USAPremium join:2001-08-25 Kendall, FL kudos:2 | Re: kudos to comcast said by r81984:The bad things you have heard about Comcast are true. They are large company that is truely disconnected from their customers, I couldn't agree more! Being the leading company in the U.S. that is installing DOCSIS 3.0, then upgrading customers from 6/1 to 12/2 and 8/2 to 16/2 for free is wrong! Clearly they are disconnected from their customers and have no interest in their customers. -- CheckSite.us | YourIP.us | Reverseip.us | |
|
 |  |  jus10 join:2009-08-04 Sterling, VA Reviews:
·Comcast
| said by r81984:The only reason they HAVE to implement IPv6 is IPv4 addresses are running out and everything they have from your phone, to each set top box, to your cable modem needs it's own IP address. When you multiply that by the number of customers they either have then they have no choice but to go to at least a hybrid IPv6/IPv4 system or to do some fun network setups to share IPs. Um, So What? This would appear to be a case where Comcast's goals/desires and plans intersecting with a group of their customers and doesn't hurt their other customers. If they are deploying IPv6 for their on reasons and I still benefit, I still benefit. You could make the same argument about DS3 rollout. It benefits Comcast and me.
Judging by the later plans, where I see this going is that customers will be able to have their own IPv6 addresses natively, and share ipv4 addresses. Hopefully by the time we get there, the world is more much of a ipv6 everything place.
With flying cars ... | |
|
 iansltx join:2007-02-19 Golden, CO kudos:2 Reviews:
·Comcast
·Verizon Online DSL
| I'm in...maybe... For now all my equipment is IPv6 compliant (Ambit D3 modem, WRT310N with DD-WRT) however I'll be switching back to a D2 modem now that I've downgraded to 12/2. $80 is too much for internet for me, so while I'm signing up for the trial I may not have the right modem when the time comes. | |
|
 |  maartenaElmoPremium join:2002-05-10 Orange, CA kudos:1 | Re: I'm in...maybe... When you downgrade to 12/2, why give up the D3 modem? Your downgraded speeds will still work with the new modem. -- "I reject your reality and substitute my own!" | |
|
 |  |  iansltx join:2007-02-19 Golden, CO kudos:2 | Re: I'm in...maybe... Because I'm renting the modem for $5 + tax per month and I have a Zoom 5241 modem that's mine and doesn't cost $5 per month. | |
|
 |  |  |  |
 | | Do they also plan $5 per ip as well Do they also plan $5 per ip as well?
If the tv side can make a lot by renting hardware whats stopping the internet side doing the same with outlet type fees. just replace outlet with a ip. | |
|
 |  See 8 replies to this post |
|
 dvd536as Mr. Pink as they comePremium join:2001-04-27 Phoenix, AZ kudos:4 | I Wonder. . . . . How many things this is going to break. | |
|
 |  tubbynetreminds me of the danse russePremium,MVM join:2008-01-16 Chandler, AZ | Re: I Wonder. . . . . said by dvd536:How many things this is going to break. i am not sure what you're getting at. many service providers have already been thinking about the ipv6 transition (and many have ipv6 functionality in the core). the issue is that there are many major manufacturers that don't *fully* support ipv6 in the same way that ipv4 is supported. service providers (especially those of small mpls-based networks) often implement "non-standard" solutions in order to provide value-added services to their customers. in doing so, they implement route-leaking, vrf importation, security measures, etc that aren't supported fully in ipv6, or its not supported *in hardware* (meaning the ipv6 packets must be punted to the supervisor/route-processor for software handling, rather than being able to be switching using something similar to cisco express forwarding (cef) in hardware).
as i see it, comcast makes no mention of going "fully ipv6" in the core, but offering ipv6 to the customer endpoints via dhcpv6 and then providing a typical 6-to-4 tunnel at some point before it hits the core - allowing existing infrastructure to be used.
will this affect a few things - sure. cpe has to support ipv6. comcast has to work out the bugs on each of their respective markets to make sure that everything works as promised. this is the point of a "trial". its not like their going cold-turkey.
q. -- "...if I in my north room dance naked, grotesquely before my mirror waving my shirt round my head and singing softly to myself..." | |
|
 |  |  jjmb join:2009-12-01 USA | Re: I Wonder. . . . . said by tubbynet:said by dvd536:How many things this is going to break. i am not sure what you're getting at. many service providers have already been thinking about the ipv6 transition (and many have ipv6 functionality in the core). the issue is that there are many major manufacturers that don't *fully* support ipv6 in the same way that ipv4 is supported. service providers (especially those of small mpls-based networks) often implement "non-standard" solutions in order to provide value-added services to their customers. in doing so, they implement route-leaking, vrf importation, security measures, etc that aren't supported fully in ipv6, or its not supported *in hardware* (meaning the ipv6 packets must be punted to the supervisor/route-processor for software handling, rather than being able to be switching using something similar to cisco express forwarding (cef) in hardware). as i see it, comcast makes no mention of going "fully ipv6" in the core, but offering ipv6 to the customer endpoints via dhcpv6 and then providing a typical 6-to-4 tunnel at some point before it hits the core - allowing existing infrastructure to be used. will this affect a few things - sure. cpe has to support ipv6. comcast has to work out the bugs on each of their respective markets to make sure that everything works as promised. this is the point of a "trial". its not like their going cold-turkey. q. Excellent points.
FWIW - the Comcast core network fully supports IPv6 and is native, dual-stack.
John | |
|
 |  |  |  tubbynetreminds me of the danse russePremium,MVM join:2008-01-16 Chandler, AZ | Re: I Wonder. . . . . said by jjmb:FWIW - the Comcast core network fully supports IPv6 and is native, dual-stack. i assume in transit, when you're just passing packets, its of no concern. i've just read a lot about the troubles that service providers are experiencing on their pe routers as they import native ipv6 into vrfs/coloring mpls labels. there is a lot left to be desired on brand c's ipv6 manipulation and mangling, however, it will come in due time. it just means that service provider (smaller, mpls-based) will not be able to maintain the same value-added services/one-offs for customers in ipv6 space as they have in ipv4.
q. -- "...if I in my north room dance naked, grotesquely before my mirror waving my shirt round my head and singing softly to myself..." | |
|
 |  brad join:2007-09-06 Etobicoke, ON | said by dvd536:How many things this is going to break. Or fix all the stuff broken by god awful NAT. | |
|
 |  |
 jack bGone FishingPremium,MVM join:2000-09-08 Cape Cod kudos:1 | No IPv6 I tried installing TCP/IP protocol IPv6 and get an error: XP Pro SP3 | |
|
 |  | | Re: No IPv6 What an amazingly verbose error message! This will certainly help troubleshoot things!
Ok serious time. Run "ipv6 install" in a command prompt and you should get some more details. | |
|
 |  |  jack bGone FishingPremium,MVM join:2000-09-08 Cape Cod kudos:1 1 edit | Re: No IPv6 I tried that earlier, too. No joy.
Upon further review, I found a solution: I Ran: esentutl /p %windir%\security\Database\secedit.sdb
Then ran ipv6 install and the install succeeded. I think. TCP/IPv6 Properties button is grayed out. -- ~Help Find a Cure for Cancer~ ~Proud Member of Team Discovery ~ | |
|
 |  |  |  jjmb join:2009-12-01 USA | Re: No IPv6 said by jack b:I tried that earlier, too. No joy. Upon further review, I found a solution: I Ran: esentutl /p %windir%\security\Database\secedit.sdbThen ran ipv6 install and the install succeeded. I think. TCP/IPv6 Properties button is grayed out. If you Google this error you will find the commands to run from the DOS prompt to correct the error and complete the installation of IPv6.
John | |
|
 |  |  |  |  jack bGone FishingPremium,MVM join:2000-09-08 Cape Cod kudos:1 | Re: No IPv6 Hi John, I haven't resolved the IPv6 properties gray button detail, if it even is a solvable issue in XP.
From IPCONFIG /ALL, I see IPv6 DNS servers, and 2 IPv6 tunnel adapter address entries, and in NETSTAT there are IPv6 TCP services "listening" on ports 135 and 1025.
It looks like it's working. I'll fill out a trial application. -- ~Help Find a Cure for Cancer~ ~Proud Member of Team Discovery ~ | |
|
 |  heat84Bit Torrent Apologist join:2004-03-11 Fort Lauderdale, FL 2 edits |  Why do programmers make error messages like that? Are they retarded or do they just wanna screw with us? Its actually 2 programmers to blame right? One wrote the error message template(Could not add the requested component: The error is:) and another wrote the error message itself(An extended error has occured). -- Bit Torrent is my DVR. | |
|
 RARPSL join:1999-12-08 Suffern, NY | 2^128 Addresses Claim is inaccurate/misleading
The Descriptions states "IPv4 uses 32-bit addresses and can support around 4 billion IP addresses, while IPv6 supports 2 to the 128th power of IP addresses (read: lots)."
While this is true, it is also misleading. The low 64 bits are used to designate the MAC Address of the NIC's Ethernet interface. Also, what is handed to the user is an IPv6/48 address (the equivalent of the current IPv4/32 given to the user). Thus the user has 16 bits of addressing on their LAN. | |
|
 |  See 18 replies to this post |
|
 heat84Bit Torrent Apologist join:2004-03-11 Fort Lauderdale, FL 1 edit | Where'd you guys learn about IPv6? How come they never taught me about this in ITT-Tech's CNS program? About all we learned about IPv6 was that it exists and it supports exponentially more IP addresses. I've learned a little more about it on my own here and other places on the internet. I'm in the ISS program now. Maybe I'll learn more about it in the next 2 years.
What schools did you guys go to to get to be experts on it? -- Bit Torrent is my DVR. | |
|
 |  MADx join:2005-05-25 Richmond, IN Reviews:
·Comcast
| Re: Where'd you guys learn about IPv6? Don't feel bad heat84, I'm in the same boat. I don't think ITT - CNS programs are prepare to teach IPV6 yet, especially in smaller two year colleges. It's best to read about it on your own time, I do this every time I see technology begin to change in a new direction. | |
|
 |  |  ncherryPremium join:2003-07-13 Monroe Township, NJ | Re: Where'd you guys learn about IPv6? Welcome to the network/computer field, understand that you'll be do that for the rest of you life (learning new things on you own) and you'll probably go far. | |
|
 |  |  |  | | Re: Where'd you guys learn about IPv6? Agreed. I've read countless books and articles on IPv6, and I still don't understand it. That's why I jumped on the beta trial. I want to figure it out before anyone else does :-P | |
|
 |  |  |  |  ncherryPremium join:2003-07-13 Monroe Township, NJ | Re: Where'd you guys learn about IPv6? I've done something similar, I've enable IPv6 (and IPv4 also, dual stack) on my WRT54G's (OpenWRT x2), my servers and a couple of Windows machines. I'm working on getting my WGT634U (OpenWRT) setup with IPv6. So far the IPv6 stack seems to work better than the IPv4 stack (it's a little bit faster, lower latency) on my Linux servers and WAPs. So far I haven't really done much DHCP with IPv6 but I'll need that too. I bought 2 IPv6 books but gave up on buying more books because the RFCs are changing at such a fast rate. But the books were still a good starting point. Basically, start using the technology, search the internet (but don't trust the information to be current or right) and make mistakes. You'll learn best by doing and making mistakes.
So far I don't have the resources to run a firewall on my OpenWRT/Firewall boxes (only 16M of RAM on the WRT54G boxes) so no open Internet IPv6 at this time. I hope to resolve that this weekend when I tear apart my WGT634U router and install the latest and greatest OpenWRT software. Then it's time to build the proper ip6tables for the firewall. Worse comes to worse I can take an embedded x86 and put OpenWRT on it but I'd rather save that box for something else.
I've been keeping my notes on my Home IPv6 Networking page. Understand that these are just my notes and may be unintelligible. I also need to update it with the Comcast latest information -- Neil Cherry Linux Home Automation Linux HA Blog Author: Linux Smart Homes For Dummies
| |
|
 |  |  |  |  |  | | Re: Where'd you guys learn about IPv6? It's a great page, thanks for making it! It's starting to make sense to me now... | |
|
 dagg join:2001-03-25 Galt, CA | finally someone is actually doing something... i signed up. some of you are not quite up to speed on the why part of IPv6. its not supposed to be of direct benefit to you as an end user. its meant to resolve the problem that we are running out of IP space in IPv4. there are added benefits beyond this, but they are more of a side effect.
also, the rest of the world is not yet on IPv6 so really, NAT is still a real issue and translation between IPv4 and IPv6 will im sure cause some kind of weird unexpected problems that someone had not really thought of in the real world.
but this is why you have trials like this in order to hammer out such issues. | |
|
 |
|