T

Thursday, October 19th, 2023 4:12 PM

Closed

ipv6 connectivity down in the Portland, OR area?

Hello,

I have a setup with a Motorola MB8611 and Mikrotik router.

I'm configured for both IPv4 and IPv6. I request a /60 prefix, and assign a /64 to my local LAN.

This has been working for a long time. As of this morning, my router is getting a valid /128 IPv6 address, and I'm also getting the correct/valid delegation, but attempting to connect to any IPv6 address just times out.

IPv4 connectivity is just fine.

From everything I'm seeing, this looks like it's a problem on the Xfinity side. Anybody from Xfinity able to jump in and check if IPv6 is working currently in the Portland area?

Thanks,

Tim

Problem Solver

 • 

1.5K Messages

2 years ago

In my market (upper mid-west), they used to let you hint for a /60 but that ended some time ago.  Now you'll just get a /64 on the  (and track) WAN.  I found hinting for a /60 results in no IPV6, so I'm not sure what the deal is there.  You should just be able to hint, even that's not what you end up with and have it work -- well for one IPV6 configured subnet tracking the interface, but the only way I can get it to work is to just hint for the /64 and call it even with one subnet able to do IPV4/IPV6 and the others just doing IPV4 only.

Annoying?  Yeah.  There isn't any documentation I can find for their IPV6 implementation, so I dunno.      

(edited)

5 Messages

@flatlander3​, thanks, yes, I had heard that there had been changes to PD in some markets.

AFAICT, that hasn't happened here (yet). The gateway is getting a valid /128 IPv6 address and I'm getting a /60 back that also looks valid (and similar to what I have seen before).

Regardless, the testing I'm doing is directly from the /128 on the gateway, so even if the delegation request had failed, I should still be able to ping directly from the gateway, but everything just times out.

I suppose I'll have to try to make a support request, but I don't think the front line folks are going to have any clue how to troubleshoot this. They'll just tell me to reboot (and, just for completeness, I already did reboot everything). Given that IPv4 is working, it's pretty obvious that basic functionality is there.

Official Employee

 • 

1.2K Messages

Hello, @tenortim. Thank you for reaching out over Xfinity Forums for support, you have reached out to the right place for assistance in regard to your IPv6 connection concern. Please let me know if you're still experiencing issues and I can investigate further. 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

5 Messages

@XfinityJustinC​ sorry for the delay in replying.

Yes, I am still unable to achieve any IPv6 connectivity from my home.

I have tried reverting to a single /64 PD request but it makes no difference.

I'm seeing the delegation itself work correctly, but I'm unable to communicate and in my "ipv6 neighbor list" on the outbound side connected to the modem, all of the neighbor lookups for IPv6 addresses are in "failed" state with the exception of one solitary link-local (fe80:) address.

Official Employee

 • 

1.8K Messages

@tenortim, I'm wondering if you need to upgrade your gateway firmware or hardware. Are you able to check on an update with your Motorola Modem?  

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

5 Messages

@XfinityAngie​ I don't believe that I am allowed to update the modem firmware. Everything I am reading including on the Motorola site is that XFinity control firmware upgrades of attached devices.

The Mikrotik router is fully up-to-date, and I should note that the firmware/software versions that are running on them are identical to when this was working, which makes me think that the change happened externally.

forum icon

New to the Community?

Start Here