

NetDog

Premium Member

join:2002-03-04

Parker, CO 2 recommendations NetDog Premium Member [IPv6] Customer Owned Devices with Business Services Users that have Comcast Business Services with a customer owned device noticed v6 has been enabled for some time now. They have also noticed they can only receive a /64-/60. We are in the process of changing the prefix size they will be receiving to a /56 currently they receive /64-/60. Over the next week the provisioning system will be updated, the current prefix will be deactivated so their router can receive a new prefix of /56.



User doesn't need to do anything unless they have a static addresses assigned to devices..



The process will be as follows:



Comcast will deactivate the current lease

Update the business class of service for customer owned devices

When the customer's router does a renew, it will receive a new /56 prefix



train_wreck

slow this bird down

join:2013-10-04

Antioch, TN 1 recommendation train_wreck Member great!



i'm guessing that if my router needs a prefix length specified in its DHCPv6 client, i need to change it to /56?



NetDog

Premium Member

join:2002-03-04

Parker, CO 2 recommendations NetDog Premium Member said by train_wreck: great!



i'm guessing that if my router needs a prefix length specified in its DHCPv6 client, i need to change it to /56? you will receive a /56 no matter what, we will not honor the hint of less then /56 or greater then /56 Nopeyou will receive a /56 no matter what, we will not honor the hint of less then /56 or greater then /56



train_wreck

slow this bird down

join:2013-10-04

Antioch, TN Cisco ASA 5506

Cisco DPC3939

1 recommendation train_wreck Member said by NetDog: Nope you will receive a /56 no matter what, we will not honor the hint of less then /56 or greater then /56 word. that's magical.



tshirt

Premium Member

join:2004-07-11

Snohomish, WA 1 recommendation tshirt to NetDog

Premium Member to NetDog

Are you planning to roll over all the residential v6 at some point too, or should we just ask individually

currently stuck on a /64, not in a great hurry, not sure why I would need a /60



NetDog

Premium Member

join:2002-03-04

Parker, CO 2 recommendations NetDog Premium Member residential can get up to a /60 with the prefix hint.. As of right now no.. Business customers should have received a /56 from the start so this is more of clean-up..



tshirt

Premium Member

join:2004-07-11

Snohomish, WA 1 recommendation tshirt Premium Member said by NetDog: residential can get up to a /60 with the prefix hint.. Do we still need to have you kill the existing lease? or will a reboot with the hint do it alone?



NetFixer

From My Cold Dead Hands

Premium Member

join:2004-06-24

The Boro ·Comcast XFINITY

·AT&T DSL

Netgear CM500

Pace 5268AC

TRENDnet TEW-829DRU

1 recommendation NetFixer to NetDog

Premium Member to NetDog





And speaking of having multiple routers on-line at the same time -- will every router that is directly attached to a BCI connection get a /56 prefix? That is a lot of address space for me to try to use up. It will be interesting to see how this works (considering how iffy the /60 prefix assignment is). I was not aware that Comcast's DHCP server(s) kept records of attached CPE devices and matched them to user accounts. If that is the case, I must have confused the hell out of the DHCP bean counters over the years as I have changed routers and/or MAC addresses, had multiple routers attached at the same time, temporarily tested routers for customers, etc. Comcast must think that I have a small warehouse full of routers.And speaking of having multiple routers on-line at the same time -- will every router that is directly attached to a BCI connection get a /56 prefix? That is a lot of address space for me to try to use up.



NetDog

Premium Member

join:2002-03-04

Parker, CO 2 recommendations NetDog to tshirt

Premium Member to tshirt

said by tshirt: Do we still need to have you kill the existing lease? or will a reboot with the hint do it alone? Yep A) I disable the Lease or B) you change your DUID..

NetDog 3 recommendations NetDog to NetFixer

Premium Member to NetFixer

said by NetFixer: And speaking of having multiple routers on-line at the same time -- will every router that is directly attached to a BCI connection get a /56 prefix? That is a lot of address space for me to try to use up. Your allowed 5 MAC's on a BCI connection so (5 IPv4, 5 IPv6 /128 and 5 IPv6 /56)



camper

just visiting this planet

Premium Member

join:2010-03-21

Bethel, CT 1 recommendation camper to NetFixer

Premium Member to NetFixer

said by NetFixer: ..(considering how iffy the /60 prefix assignment is)..

On the residential side, I've had zero problems with the /60 prefix delegation. It renews on time, every time.



Of course, I don't have all the fun playing musical chairs with MAC addresses and routers that you have. On the residential side, I've had zero problems with the /60 prefix delegation. It renews on time, every time.Of course, I don't have all the fun playing musical chairs with MAC addresses and routers that you have.

neufuse

join:2006-12-06

James Creek, PA 1 recommendation neufuse to NetDog

Member to NetDog

what about enterprise customers? We've heard nothing about IPv6 on our end yet... and when we signed up the sales person and techs that did the fiber install told us don't even ask about it

biomesh

Premium Member

join:2006-07-08

Tomball, TX 1 recommendation biomesh to NetDog

Premium Member to NetDog

Just restarted my DHCPv6 client on my Mikrotik router and it picked up the /56 with no issues.



NetDog

Premium Member

join:2002-03-04

Parker, CO 1 recommendation NetDog to neufuse

Premium Member to neufuse

said by neufuse: what about enterprise customers? We've heard nothing about IPv6 on our end yet... and when we signed up the sales person and techs that did the fiber install told us don't even ask about it What service the E505? it already has v6.. PM me your email address and I will look into it..

NetDog 1 recommendation NetDog to biomesh

Premium Member to biomesh

said by biomesh: Just restarted my DHCPv6 client on my Mikrotik router and it picked up the /56 with no issues. Sweet.. Glad to hear it..

neufuse

join:2006-12-06

James Creek, PA 951.6 36.1

1 recommendation neufuse to NetDog

Member to NetDog

no no, I mean the Enterprise services, not consumer services / business class services... we have an EDI line from Comcast Enterprise.. when we did our survey for service we submitted our IP block requests and asked about IPv6 they told us not to ask about it.. when the service was installed the setup crew from Comcast that came out to set up our PRI and Ciena box told us the same thing, don't even ask about it. so we assumed enterprise services aren't IPv6 ready yet

quesix

join:2005-12-19

Cary, IL 1 recommendation quesix to NetDog

Member to NetDog

We've had IPv6 on EDI for years here, but are providing our own IPv4 and IPv6 blocks from ARIN via BGP. Sounds like static assignments are not yet being given out for IPv6 even with this update, as you are talking DHCP-PD as usual.



train_wreck

slow this bird down

join:2013-10-04

Antioch, TN Cisco ASA 5506

Cisco DPC3939

1 recommendation train_wreck to NetDog

Member to NetDog





Oct 28 16:53:12 Gateway dhcp6c[22636]: client6_send: send request to ff02::1:2%external Oct 28 16:53:12 Gateway dhcp6c[22636]: dhcp6_reset_timer: reset a timer on external, state=REQUEST, timeo=0, retrans=1028 Oct 28 16:53:12 Gateway dhcp6c[22636]: client6_recv: receive reply from fe80::201:5cff:fe3f:d241%external on external Oct 28 16:53:12 Gateway dhcp6c[22636]: dhcp6_get_options: get DHCP option client ID, len 14 Oct 28 16:53:12 Gateway dhcp6c[22636]: DUID: 00:01:00:01:1b:de:85:bc:a0:36:9f:14:01:ec Oct 28 16:53:12 Gateway dhcp6c[22636]: dhcp6_get_options: get DHCP option server ID, len 14 Oct 28 16:53:12 Gateway dhcp6c[22636]: DUID: 00:01:00:01:15:5d:94:a6:14:fe:b5:cf:15:b0 Oct 28 16:53:12 Gateway dhcp6c[22636]: dhcp6_get_options: get DHCP option IA_PD, len 41 Oct 28 16:53:12 Gateway dhcp6c[22636]: IA_PD: ID=1, T1=172800, T2=276480 Oct 28 16:53:12 Gateway dhcp6c[22636]: copyin_option: get DHCP option IA_PD prefix, len 25 Oct 28 16:53:12 Gateway dhcp6c[22636]: copyin_option: IA_PD prefix: 2601:5:1480:1900::/56 pltime=345600 vltime=345600 Oct 28 16:53:12 Gateway dhcp6c[22636]: dhcp6_get_options: get DHCP option DNS, len 32 Oct 28 16:53:12 Gateway dhcp6c[22636]: info_printf: nameserver[0] 2001:558:feed::1 Oct 28 16:53:12 Gateway dhcp6c[22636]: info_printf: nameserver[1] 2001:558:feed::2 Oct 28 16:53:12 Gateway dhcp6c[22636]: client6_recvreply: executes /etc/wide-dhcpv6/ra.sh Oct 28 16:53:15 Gateway radvd[22645]: [Oct 28 16:53:15] radvd (22645): version 2.8 started Oct 28 16:53:15 Gateway dhcp6c[22636]: client6_script: script "/etc/wide-dhcpv6/ra.sh" terminated Oct 28 16:53:15 Gateway dhcp6c[22636]: get_ia: make an IA: PD-1 Oct 28 16:53:15 Gateway dhcp6c[22636]: update_prefix: create a prefix 2601:5:1480:1900::/56 pltime=345600, vltime=345600 Oct 28 16:53:15 Gateway dhcp6c[22636]: ifaddrconf: add an address 2601:5:1480:1901:a236:9fff:fe14:1ed/60 on internal Oct 28 16:53:15 Gateway dhcp6c[22636]: dhcp6_remove_event: removing an event on external, state=REQUEST Oct 28 16:53:15 Gateway dhcp6c[22636]: dhcp6_remove_event: removing server (ID: 00:01:00:01:15:5d:94:a6:14:fe:b5:cf:15:b0) Oct 28 16:53:15 Gateway dhcp6c[22636]: dhcp6_remove_event: removing server (ID: 00:01:00:01:15:9c:b1:8e:84:2b:2b:fc:98:bb) Oct 28 16:53:15 Gateway dhcp6c[22636]: client6_recvreply: got an expected reply, sleeping. yep, got it here too



NetFixer

From My Cold Dead Hands

Premium Member

join:2004-06-24

The Boro ·Comcast XFINITY

·AT&T DSL

Netgear CM500

Pace 5268AC

TRENDnet TEW-829DRU

1 recommendation NetFixer Premium Member





D-Link DIR655-B1







D-Link EBR2310-C1

Since Nashville and Murfreesboro share a lot of common Comcast infrastructure I thought that perhaps the /56 prefix might be active here too. So I did a release/renew for IPv6 on both of my currently active routers, but I only get /64 for both of them (I stopped getting a /60 for my DIR655 several months ago, and changing WAN MAC/DUID made no difference):



NetDog

Premium Member

join:2002-03-04

Parker, CO NetDog to neufuse

Premium Member to neufuse

said by neufuse: no no, I mean the Enterprise services, not consumer services / business class services... Ping me your contact info and I will take a look and see what I can do..

NetDog 1 recommendation NetDog Premium Member The changes are model specific over the next couple of nights.. so the TM722G, CM820A and others last night.. more models tonight, up till Thursday night..



NetFixer

From My Cold Dead Hands

Premium Member

join:2004-06-24

The Boro ·Comcast XFINITY

·AT&T DSL

Netgear CM500

Pace 5268AC

TRENDnet TEW-829DRU

1 recommendation NetFixer Premium Member said by NetDog: The changes are model specific over the next couple of nights.. so the TM722G, CM820A and others last night..



I hope that these new /56 prefixes are as stable and long lasting as the most recent /64 prefixes I was assigned -- those prefixes lasted for several months and made it through several CMTS maintenance cycles and power outages (something that previously had not been the case).



I am now tempted to once again put my retired Netgear WNR1000v2-VC guest router back into service to see if this new /56 prefix policy might have accidentally fixed the classic Netgear DHCPv6 lease renewal problem in that router (if I can talk myself into the cable and equipment shuffling that will require). Were there actual (config file?) changes made to the customer owned modems, or was this strictly a behind the curtain database update? Either way, it looks as if they did the updating for the Motorola SB6121 (and/or the D-Link DIR655 and EBR2310 if the router model matters) last night/this morning. I did a release/renew cycle about an hour ago, and both my primary DIR655 and the auxiliary EBR2310 (whose only IPv6 device is a RIPE Atlas probe) now have /56 prefixes.I hope that these new /56 prefixes are as stable and long lasting as the most recent /64 prefixes I was assigned -- those prefixes lasted for several months and made it through several CMTS maintenance cycles and power outages (something that previously had not been the case).I am now tempted to once again put my retired Netgear WNR1000v2-VC guest router back into service to see if this new /56 prefix policy might have accidentally fixed the classic Netgear DHCPv6 lease renewal problem in that router (if I can talk myself into the cable and equipment shuffling that will require).



NetDog

Premium Member

join:2002-03-04

Parker, CO 1 recommendation NetDog Premium Member All changes have been completed.. All devices are done.. If you have BCI service with a customer owned device.. Have fun with the /56..

NetDog 1 recommendation NetDog to NetFixer

Premium Member to NetFixer

said by NetFixer: Were there actual (config file?) changes made to the customer owned modems, or was this strictly a behind the curtain database update? said by NetFixer: I hope that these new /56 prefixes are as stable and long lasting as the most recent /64 prefixes I was assigned -- those prefixes lasted for several months and made it through several CMTS maintenance cycles and power outages (something that previously had not been the case). This is completed on the DHCP server per CoS (Class of Service)..They are coming from the same scope as the other so yep you should be good to go.. Only Stable v6 with has a different scope range when that becomes available.



NetFixer

From My Cold Dead Hands

Premium Member

join:2004-06-24

The Boro ·Comcast XFINITY

·AT&T DSL

Netgear CM500

Pace 5268AC

TRENDnet TEW-829DRU

1 recommendation NetFixer Premium Member said by NetDog: said by NetFixer: I hope that these new /56 prefixes are as stable and long lasting as the most recent /64 prefixes I was assigned -- those prefixes lasted for several months and made it through several CMTS maintenance cycles and power outages (something that previously had not been the case). They are coming from the same scope as the other so yep you should be good to go.. Only Stable v6 with has a different scope range when that becomes available. Interesting about the new IP addresses coming from the same scope (and the /48 portion of the prefix is indeed the same). However, I just noticed that » www.comcast6.net no longer tells me that I am on a Comcast dual stack connection (nor does it display either an IPv4 or an IPv6 addresses). Is this just a coincidence (and comcast6.net is simply malfunctioning), or is it possibly related to the new /56 prefix? FWIW, I see no other IPv6 related problems -- just with comcast6.net.



NetDog

Premium Member

join:2002-03-04

Parker, CO 1 recommendation NetDog Premium Member said by NetFixer: Is this just a coincidence (and comcast6.net is simply malfunctioning), or is it possibly related to the new /56 prefix? FWIW, I see no other IPv6 related problems -- just with comcast6.net. If you see other issues ping me.. try a traceroute or ping to www.comcast6.net..



NetFixer

From My Cold Dead Hands

Premium Member

join:2004-06-24

The Boro ·Comcast XFINITY

·AT&T DSL

Netgear CM500

Pace 5268AC

TRENDnet TEW-829DRU

1 recommendation NetFixer Premium Member said by NetDog: If you see other issues ping me.. try a traceroute or ping to www.comcast6.net.



C:\>ping www.comcast6.net Pinging comcast6.g.comcast.net [2001:558:fc00:100:f816:3eff:fea3:1f57] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 2001:558:fc00:100:f816:3eff:fea3:1f57: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\>tracert www.comcast6.net Tracing route to comcast6.g.comcast.net [2001:558:fc00:100:f816:3eff:fea3:1f57] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 2601:5:1f00:3b01:1e7e:e5ff:fe4c:e6ff 2 9 ms 8 ms 27 ms 2001:558:6016:3e::1 3 10 ms 9 ms 27 ms xe-10-0-1-32767-sur03.murfreesboro.tn.nash.comcast.net [2001:558:162:98::1] 4 9 ms 19 ms 35 ms xe-2-0-9-0-ar03.nashville.tn.nash.comcast.net [2001:558:160:57::1] 5 26 ms 23 ms 23 ms he-2-14-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f76f::1] 6 51 ms 51 ms 51 ms he-3-7-0-0-ar01.woburn.ma.boston.comcast.net [2001:558:0:f681::2] 7 52 ms 51 ms 52 ms he-0-15-0-0-ar01.needham.ma.boston.comcast.net [2001:558:200:2a9::1] 8 49 ms 50 ms 50 ms 2001:558:200:13a::2 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 ^C C:\>ping -4 www.comcast6.net Pinging comcast6.g.comcast.net [96.119.1.235] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 96.119.1.235: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\>tracert -4 www.comcast6.net Tracing route to comcast6.g.comcast.net [96.119.1.235] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms gw1.dcs-net.lan [192.168.9.254] 2 10 ms 9 ms 8 ms 107.3.232.1 3 13 ms 7 ms 10 ms xe-10-0-0-32767-sur04.murfreesboro.tn.nash.comcast.net [68.86.151.53] 4 10 ms 10 ms 11 ms xe-0-0-11-0-ar01.goodslettvll.tn.nash.comcast.net [162.151.9.65] 5 20 ms 19 ms 19 ms he-5-6-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.89] 6 30 ms 30 ms 31 ms he-0-6-0-0-cr02.chicago.il.ibone.comcast.net [68.86.86.245] 7 32 ms 32 ms 35 ms be-10406-cr01.350ecermak.il.ibone.comcast.net [68.86.84.210] 8 57 ms 59 ms 59 ms he-3-5-0-0-ar01.woburn.ma.boston.comcast.net [68.86.95.26] 9 69 ms 59 ms 59 ms he-1-3-0-0-ar01.needham.ma.boston.comcast.net [69.139.221.205] 10 58 ms 57 ms 58 ms te-8-1-ur01.easthampton.ct.hartford.comcast.net [68.87.182.34] 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 ^C



IPv6 and IPv4 pings and traceroutes time out. I can reach the web site with a browser, but the IPv6 information that is normally at the top of the page is just not there:



NetDog

Premium Member

join:2002-03-04

Parker, CO 1 recommendation NetDog Premium Member said by NetFixer: IPv6 and IPv4 pings and traceroutes time out. I can reach the web site with a browser, but the IPv6 information that is normally at the top of the page is just not there: Looks like an website issue.. Great, I will look into this in the AM..