U

Visitor

 • 

21 Messages

Saturday, January 28th, 2023 1:30 AM

Closed

ip6 bridge mode

My XB8 stopped responding to ipv6 solicit messages when in bridge mode. That happened sometime yesterday or the day before. It works fine when the modem is not in bridge mode although what changed in that case is that it responds with "No prefix available" when the router requests prefix delegation /60. I tried with all lengths between 56 and 64 and the response is universally - no prefix available. But at least when not in bridge mode, I get v6 IP. When in bridge mode, the modem doesn't respond anymore to dhcp6 solicit messages anymore. Can someone help?

Problem Solver

 • 

1.4K Messages

2 years ago

@user_079458 Hello and thank you for reaching out. Have you tried to do any modem resets to see if resetting the modem will help fix the issue or possibly doing a factory reset? 

Visitor

 • 

21 Messages

@XfinityAbbie​ Yes, multiple restarts including factory resets. Today an Xfinity technician came and tried to help. Replaced the XB8 modem with XB7 modem and the problem is still there. Took a picture of a tcpdump dumps that shows successful request/reply when the modem is not in bridge mode and also just the requests without reply when the modem is in bridge mode. I hope someone would be able to make sense of it. 

Although at that point it is very easy for someone at Xfinity to try to reproduce. If everything works - I would be glad to have my modem replaced with one that has been verified working properly. If not - then that could be a starting point to figure out what is the problem. It may also be a regional problem if you haven't heard from anyone else. I doubt that many people care to put their modem in bridge mode and then care about ipv6.

Official Employee

 • 

1.2K Messages

With the modem working as intended when configured with our recommended (Non-Bridge Mode) settings, the issue you are experiencing is outside our demarcation. We recommend using the modem with our recommended settings. If you are using bridge mode, it could be due to any of the additional third-party networking equipment you may have connected to the local network. Have you ruled out the router as a potential culprit to the issue?

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

Visitor

 • 

21 Messages

I get it that non-bridge mode is recommended. But is bridge mode supported even at a bare minimum with ipv6? Can you state that this is the case? I heard multiple times that it could be due to my networking equipment. I ran tcpdump on the network interface on my side and showed that your modem responds to dhcpv6 solicit message when bridge mode is off and by just turning bridge mode on your modem stops responding to dhcpv6 solicit msg. Would you say that this rules the problem being on my side? This is capturing the bytes sent over ethernet and is about the simplest thing I can do to show that you are having a problem. Same exact setup was working just four days ago without changes on my side. 

An additional clue that shows that you did something on your side is that your modem doesn't provide ipv6 network through prefix delegation anymore even when the modem has bridge mode off. Before Wednesday it was providing a 60-bit prefix network. I don't care much about this - it is just a clue that something changed on your side.

Having dealt with the Xfinity customer - I asked for the technician.

So I was hoping that the technician will come, switch the modem to bridge mode, connect an Xfinity owned device (any device, regardless of what it is - laptop, router...) and show ipv6 connectivity working. They couldn't do that. I guess they were not prepared to do it that which is fine. But at the very least I would expect someone from Xfinity to follow up next week and confirm that they tested this with such and such device and is working. And then I can get the same device and replicate the setup. Is that too much to ask?

New Problem Solver

 • 

318 Messages

Bridge mode should not change the modem's functionality other than disabling the built-in router function in the gateway. If this issue only happens when bridge mode is enabled is likely the router and other equipment are causing the problem. If the issue is happening whether bridge mode is enabled or disabled then that would definitely be something we would want to dig into further to see why it is happening when you are just using our gateway and have no outside equipment for your service. 

I no longer work for Comcast.

Visitor

 • 

21 Messages

What I'm saying here is that enabling bridge mode doesn't only disable the built-in router function. It entirely prevents any ipv6 connectivity and any device (external router) from using your modem with ipv6. Isn't there some minimum level of assurance that when bridge mode is enabled there is at least one ipv6 device that is supported or at the very least tested by your QA team that it works? This is all that I'm asking. What is it? I was expecting the technician to come, switch the bridge mode on, plug some Xfinity test device and say - see, you have ipv6 connectivity so our modem works fine with at least one device - our test one. They couldn't do that. 

Visitor

 • 

21 Messages

2 years ago

I figured out how to make ipv6 work with the Xfinity modem in bridge mode (or with any third party modem I guess too).

The MAC address of the WAN Ethernet adapter that my router has (and that connects to the cable modem's ethernet) starts with 00:07:43 which is a prefix assigned to Chelsio and used for their adapters. When I tried a MAC address overwrite with an address that starts with A8:20:66 (prefix owned by Apple) then everything started working. With bridge mode and without bridge mode. My router now gets a response to the dhcp6 solicit requests and even gets a /60 prefix. Interestingly, the v4 IP now is very different than the one I was getting before. That may or may not be related.

So it isn't clear if Xfinity blocks somehow certain MAC addresses or they just use different back-end systems based on the client's MAC (and it happens that one works and another doesn't). Would be amazing if the support people clarify this and say if there are any MAC address based blacklists so clients know what to do.

(edited)

forum icon

New to the Community?

Start Here