Forum Discussion

Birdman5589's avatar
Birdman5589
New Contributor
9 years ago

IPv6 connection issues for Google Play Services

For about a week, my Galaxy Note 5 has been having issues updating and launching applications when connected to Wi-Fi. I tried resetting the phone thinking something was messed up there. After that did not resolve the issues, I started looking closer at what was not working. It appeared that only applications the used Google Play Games service and updates contacting the Google Play Services were not working. So I started looking into the router. Whenever there was an issue, the following log entry would be created.

DoS attack] AIF:Dropped INPUT packet: PROTO:ICMPv6 SPT: DPT: 1 Tuesday, 08 Mar 2016 18:42:46 ff02:0000:0000:0000:0000:0000:0000:0001 fe80:0000:0000:0000:7281:05ff:fe2c:f5d9

The first address is the target and the second is the source. The second is the IPv6 address assigned to the Note 5. The first address is the multicast group if I am not mistaken.

So it appears the there is an address with the IPv6 multicast that is preventing connecting to the Google Play Services.

I have a C6300 hardware revision 3.0 with firmware 1.02.20

c6300
connection issues

25 Replies

Sort By
Replies have been turned off for this discussion
  • Tecknowhelp's avatar
    Tecknowhelp
    Valued Contributor II
    9 years ago

    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. 

  • Birdman5589's avatar
    Birdman5589
    New Contributor
    9 years ago
    Thanks for the response.
    Yes. I do have a C6300 modem/router combination unit. It does work with IPv6. The test page you provided passes all the test. I am also able to ping the public Google IPv6 addresses from my Windows PC. I also tried disabling Ipv4 on my computer (i.e. force only IPv6) and I am able to connect to sites with known IPv6 support. As you stated, I cannot find any IPv6 information in the manual or within the settings. I do not know if it is a limitation of the firmware that Cox pushes but I can confirm that v1.02.20 is not the latest firmware from Netgear.
    Just to try, I disabled the router functionality of the C6300 and used a different device as the router. This did not change the behavior at all. I also ensured that there were no firewall settings that would block the multicast range. Additionally, I tried to put the Note 5 in the DMZ. The same error still occurs in the log:
    Description Count Last Occurrence Target Source
    [DoS attack] AIF:Dropped INPUT packet: PROTO:ICMPv6 SPT: DPT: 75 Sunday, 13 Mar 2016 17:06:03 ff02:0000:0000:0000:0000:0000:0000:0001 fe80:0000:0000:0000:7281:05ff:fe2c:f5d9

    This is something that really has me baffled. There has been no setting changes or firmware updates between the time it was working and now. I have having a hard time trying to figure out where the issue could be on the C6300 or if it is a Cox problem. It worked at one point with this setup. I just am not sure where to even look from here.

  • Becky's avatar
    Becky
    Moderator
    9 years ago
    Hi Birdman,

    I'm not sure these log entries have anything to do with your inability to connect to the Google Play Game Service. Your PC generates normal multicast traffic that does not get forwarded outside of your LAN by your router. This type of traffic can be ignored. The fe80:0000:0000:0000:7281:05ff:fe2c:f5d9 IP is a non-routable, link-local IPv6 address on your network. Are you sure this is the IP of the Galaxy Note 5? Does the Galaxy have any network diagnostic tools?

    Have you checked with the Google Play Help Center (https://support.google.com/googleplay/#topic=3364260) to see if there are any known compatibility issues or alerts?

  • John_Burroughs's avatar
    John_Burroughs
    New Contributor
    9 years ago

    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

  • Birdman5589's avatar
    Birdman5589
    New Contributor
    9 years ago

    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. 

  • Birdman5589's avatar
    Birdman5589
    New Contributor
    9 years ago

    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. 

  • Birdman5589's avatar
    Birdman5589
    New Contributor
    9 years ago

    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? 

  • Birdman5589's avatar
    Birdman5589
    New Contributor
    9 years ago

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