New problem solver

 • 

54 Messages

Friday, March 20th, 2026 1:38 AM

My IPV6 prefix delegation seems to have broken again

My Mikrotik router which has been working for ages can't get a prefix now.

I tried a reboot of the modem as well as a hard power cycle, same issue.

Firmware is: CGA4332COM_8.2p8s1_PROD_sey

Oldest First
Selected Oldest First

Official Employee

 • 

36 Messages

1 month ago

Thanks for reaching out @rob__jr! We appreciate you for confirming what steps you've already taken. We’ll need to take a closer look at the account. Please send us a direct message with your full name, business name, full address, and last four digits of your account number or full phone number linked to the business account. To send a Direct Message:
 
• Click "Sign In" if necessary 
• Click the "Direct Messaging" icon in the top right corner
• Click the "New message" (pencil and paper) icon 
• The "To:" line prompts you to "Type the name of a person". Instead, type "Comcast Business" there 
• - As you are typing a drop-down list appears. Select "Comcast Business" from that list 
• - An "Comcast Business" graphic replaces the "To:" line 
• Type your message in the text area near the bottom of the window 
• Press Enter to send it

New problem solver

 • 

54 Messages

1 month ago

Done!  Thanks for the instructions.

New Contributor

 • 

12 Messages

27 days ago

This is the same issue discussed in the previous thread, which I just ran into again myself a few days ago.

https://forums.businesshelp.comcast.com/conversations/ipv6/prefix-delegation-disabled/690fa973a2c50219bf21c6e6?commentId=69b8616d58321463f4f99350

This was originally caused by a defective series of firmware updates they pushed to many modems last year, and then they decided to roll it back.

Then apparently sometime in the past week, they started to roll these broken updates out again.

As such, once more, IPv6 is now broken for me too.

(edited)

Official Employee

 • 

12 Messages

Hello @derek_k I am sorry to hear tha tyour IPv6 is also not working. I would love to take a look and see what is going on.  Please send us a direct message with your full name, business name, full address, and last four digits of your account number or full phone number linked to the business account. To send a Direct Message:
 
• Click "Sign In" if necessary 
• Click the "Direct Messaging" icon in the top right corner
• Click the "New message" (pencil and paper) icon 
• The "To:" line prompts you to "Type the name of a person". Instead, type "Comcast Business" there 
• - As you are typing a drop-down list appears. Select "Comcast Business" from that list 
• - An "Comcast Business" graphic replaces the "To:" line 
• Type your message in the text area near the bottom of the window 
• Press Enter to send it

New problem solver

 • 

54 Messages

19 days ago

Thank you Derek.  I got my case closed without a contact.  Opened a new one 3 days ago, waiting for contact.  Will call tomorrow at lunch if no contact in the morning.  This is so disheartening.

New Contributor

 • 

12 Messages

I followed up with the private message (as suggested above) a week ago, they keep claiming a support ticket was opened and someone will get back to me, but I see no evidence that anything has actually happened.  No tickets on my account, nobody has gotten back to me, and my modem is still on "CGA4332COM_8.2p8s1_PROD_sey".

Maybe if enough of us start complaining again, they'll finally notice.

New problem solver

 • 

54 Messages

16 days ago

I've now had 2 tickets closed on this with no actual call from a human.  I'm now on the phone, again for something that should be a simple fix.  Can someone Please escalate this at Comcast?

New problem solver

 • 

54 Messages

Well I've got this working again.....after doing a packet sniff I did see the PDs coming in, even on this firmware.  I played around with firewall rules a bit and it started working.  Not sure why I suddenly need a new firewall rule, but....

New Contributor

 • 

12 Messages

@rob__jr​ Now I'm wondering if I should try playing around with this a bit again myself.

When my modem first updated, I noticed the PDs did come through.  The problem was that the modem simply refused to actually pass IPv6 traffic coming from those PD subnets.  What firewall changes did you end up making?

(Broken IPv6 is very disruptive to general usability of the network, which is why I've had it disabled since first running into this issue again.)

New Contributor

 • 

12 Messages

Good news!  I just tried again (turned on IPv6 on my firewall, let it delegate the prefixes) and it seems like IPv6 is now working correctly again.  My firmware hasn't updated.  Not sure what really happened here, but I'm glad its resolved.

Of course given how often my IPv6 prefix seems to change (they don't seem to understand the concept of "static" IPs once IPv6 gets involved), its entirely possible that something caused them to not like the prefix I was getting a few weeks ago.