IPv6 connection issues for Google Play Services

Not even one nibble or suggestion yet?

Can you confirm the model number? Sure not R6300? C6300 is a gateway and I did not know those worked with IPv6. Are you getting a valid IPv6 and block? Test here. I don't even see IPv6 options in the manual. 

Looks like your firewall is block a incoming IPv6 packet for 254.44.245.217 which is a multicast traffic as you said. Looks like the Galaxy Note 5 application is trying to use IPv6 multicast traffic and your gateway/router can't handle it. If you have a router instead of a gateway, and it had a IPv6 firewall, you could add a exception rule for multicast traffic range. 

If your looking for a dirty fix, try putting your Galaxy Note 5 in the DMZ. Small security risk but a android phone is not that suspect-able to attack that it needs the SPI firewall. See page 44 of manual above is right router and is a option you want to consider. 

No response from anybody from Cox yet? Really? 

Hi,

I had the same issue that you are having. Please disable the wi-fi on your phone, download DNset from the google play store. If you click the box to have it automatically start and re-enable your wi-fi, you will be good to go.

thanks,

John

Thanks for the suggestion. While this is a workaround, it is not a final solution. Everything works fine on the phones WiFi if I am connected to any other network than using my Cox services. I can use another phone as a hotspot (AT&T or Verizon) and there is no issue connecting to the any of the Google update or play services. But that will use up data plans on the phones so the internet that I pay for through Cox needs to be addressed. 

You are correct. I was mistaken as the IPv6 address was very similar and I misread it when comparing to the logs.

This does not appear to be an issue with the phone or the Google services. I can use another phone as a hotspot (AT&T or Verizon) and there is no issue connecting to the any of the Google update or play services. But that will use up data plans on the phones so the internet that I pay for through Cox needs to be addressed. 

Maybe this is not an issue with the IPv6 traffic as I originally thought. However it does appear to be an ISP issue of some sort. Whether that is on the back-end or with the firmware in the modem, I cannot say. Either way, a solution needs to be found. 

I am wondering if this in an MTU issue. If I lower my MTU on the router to 1400 (instead of the default 1500) I have better results with connecting to some but not all services. 

Perhaps an issue with PMTUD? 

This is still not resolved. The lack of engagement from Cox is really ridiculous. 

Created an account just to let you know you aren't alone.  I have been having this issue for about a week now, and yesterday realized that it may be an issue with my Wi-Fi.  Out of curiosity, and I am not sure this will solve it at all, but does Cox have you running the most recent firmware on your modem/router?  Mine is a bit out-dated.  Might try calling them today to get it updated and see if that solves the problem.  I have contributed to a Verizon forum dealing with the same issue.  You can find it here: https://community.verizonwireless.com/thread/907567?start=20&tstart=0.  Same username there as well.  Hope someone gets this sorted soon, because I kind of feel like I am getting the run around from every single company at this point.

Called Cox tech support today and was referred to Netgear.  So I am going to try them next.  So far Samsung, Google, Cox are no help.  Need to try Verizon still and will try Netgear shortly.  Fingers crossed.

Thanks for the information. I worked with Verizon as well over the phone. I went through the whole process of resting the phone and even using some special device recovery software from Verizon/Samsung but it did not resolve the issue. 

I am running the latest firmware supported by Cox but not the latest one that Netgear has. I do not know why I am unable to control the firmware on my own device. If this ends up being a firmware issue then this comes back to Cox needing to support it. 

Called Netgear the other day as suggested by the Cox tech I spoke with.  The Netgear rep seemed eager to help but then tried to sell me two years of service/support for close to $200.  Not happening.  That was the end of that.  He couldn't update my firmware (which still seems to be an instance behind according to http://kb.netgear.com/app/answers/detail/a_id/25477/~/current-firmware-version-for-netgear-cable-modem-routers.  Sadly, when I had called Cox, the tech I had spoken with also stated he could not update the firmware, which leaves me curious as to who actually can, because I know I cant.

Called Verizon yesterday as well and the tech there was the first helpful person I got in touch with.  He elevated the issue to the engineering team and said he would likely get in touch with me over the next few days to get more information.  Sounds to me like I might actually get some help on this finally.  Will keep you posted.

The Galaxy Note 5 is the only Android device that I have to test with. I do not appear to be having issues with any other devices. However, I do not believe that any of my other devices currently use IPv6 in any significant manner. Additionally, I have tested with the Note 5 through other networks that support IPv6 and have not experienced the issues observed with my Cox service with my Netgear modem/router.

If Netgear has an updated firmware, is Cox even testing that can be used? I understand not pushing approved firmware but is it even going through the approval process?