I searched for playstation on the Xfinity Forum and it looks like others are experiencing similar issues: https://forums.xfinity.com/conversations/your-home-network/sony-playstation-5/63f44c2f42546f76d9f305...
Unfortunately, I don't have a PS5 (or any modern gaming system) so I can't test this or offer any assistance.
@bozoli fwiw, here's an article on the Playstation 5 and its use of IPV6:
IPv6 support in the PlayStation 5 | ~tore (toreanderson.github.io)
It would be far better if Sony wrote a meaningful description of how the Playstation 5 used IPV6, but, apparently not. Searching thru the Playstation site turns up zero items on IPV6. So be it.
Can you have a quick look at that article. I'm wondering, if, when you're having trouble online, if the Playstation 5 continues to display an IPV6 address at the top of the View Connection Status page of the network settings, as shown in that article? Maybe the IPV6 path fails at some point but the Playstation continues to display an IPV6 address??
If you suspect any issues with IPV6, on a pc or laptop, run the following command:
tracert -6 www.google.com
What you're looking for is a continuous trace, from the modem out to google. You might end up with a time out here or there, but, the trace should complete all the way to the end target which is google.
If the trace only shows the modem and then times out from there, or it shows the modem and CMTS (hop #2) and then times out from there, that indicates a problem at the CMTS, specifically with the CMTS IPV6 configuration. Rogers has a long but little known history of CMTS IPV6 configuration problems. This relates to the path data in a trace for example that is returned from the CMTS to the device. This problem is hard to detect if you don't know about it and harder yet to convince anyone at Rogers that there's an issue with the CMTS. You need to be talking with a Level II tech if you find that there is an issue with the IPV6 return data. The Level I techs and field techs will not understand what you're talking about. What usually happens is that the transmitted data travels out beyond the CMTS to the end target, but, the return data is blocked at the CMTS by a faulty configuration. The end result is that the trace will appear to timeout. Same with any IPV6 data from any other server. Of course there may be other ways for the IPV6 data to fail at the CMTS, but the effect might be the same, that the data fails appears to fail at the CMTS. The CMTS will issue an IPV6 address to the modem or router, which in turn manages / negotiates the IPV6 addresses for each device. Its more likely that the CMTS issues the IPV6 prefix and the devices on the network determine their full IPV6 address when they have the required prefix. So, you can have a full IPV6 address for the devices on the network, but, the CMTS will not allow any IPV6 data to return to the device.
Now if this was occurring, I'd expect you to see issues with other devices. That will depend on the ability of the device to fallback to IPV4 operation. Cell Phones have an issue with this, specifically with What's App and Google services (?). Its been a while since this has come up so I don't remember the list of apps that are affected, and its not all cell phones. I think Google Pixels are prone to this, but, again I don't remember the specifics. In the case of cell phones running via wifi, if IPV6 is available they will use IPV6. If IPV6 path to or from the external server fails at some point the phone is supposed to failover to IPV4. Some phones don't do this successfully, and as a result the applications will fail. That's an IPV6 failure and a failure of the phone to fall back to IPV4, not an application failure.
So, keep this in mind and go hunting for a CMTS IPV6 failure. I don't know what will happen with a connected pc or laptop. If you run an ipconfig command, it should show either an IPV6 preferred address or an IPV4 preferred address. Even without a real IPV6 address available, the ipconfig or ipconfig/all command will show a local IPV6 address. That's not a true "online" address. The question here is whether or not the modem will fail the IPV6 address deliberately if its detects a problem with the IPV6 path? Does it even detect a problem? If it doesn't, then any device that relies on the modem to supply an IPV6 address will set the priority in the device as IPV6 first, IPV4 second. If the device is smart enough to detect an issue, then it will fall back to IPV4 on its own. If its not smart enough, then it will continue to attempt to use IPV6. So, its possible that devices such as a laptop or pc are smart enough to figure this out, but the Playstation isn't.
I hope you can follow what I'm saying here. There are a few parts to this, where devices may have their own capability to fall back to IPV4, without indicating that there's an IPV6 failure. They will continue to chug along using IPV4 and might continue to show an IPV6 address as the priority address.
So, you need to go hunting outside of the network by using a trace command and possibly a ping command. If there was an IPV6 failure at the CMTS, I would expect the IPV6 test at test-ipv6.com to fail, without being able to tell you why or where the failure is occurring.
Edit: If you swap back to an older modem such as the Hitron CODA-4582, you will have to change the Router Mode from Dual to IPV4. The default Router mode is Dual mode, IPV6 and IPV4. That's how it will boot up. After the modem is set up and running, navigate to the Gateway Function and change the Router Mode from Dual to IPV4 only. Save the changes. The modem will take two to three minutes to change to IPV4 mode only. Even with that change, reboot the modem, which is located at Administration .... Device Reset .... Reboot. While the modem is rebooting, reboot the Playstation as well so that it only has an IPV4 address after the reboot. It will probably show a link local IPV6 address which is typical as it won't have the Rogers IPV6 prefix available.
Greetings @Tad!
Thank you for your contributions to our Community! 🙌 I'm saddened to hear about what occured when you called in. It's most certainly not the type of experience we want you to be having. I know firsthand how imperative it is to ensure you stay connected and we're here to help!
I just want to mention that we have a plethora of ways to connect with us aside from calling in via phone. You can connect with us via the following platforms.
Alternatively, feel free to connect with us by sending a private message @CommunityHelps and we'll be happy to have a gander for you. Feel free to check out this blog if you're not familiar with our PM system.
Regards,
RogersJo
-
8768 views
-
11 Likes
-
-
