Google Home and Chromcast killing wifi

[Chungerz]

If you have a Google home and/or Chromecast device, it may be the cause of your wifi dropouts.

 

It seems to affect people who have android phones and google home and/or chromecast devices connected to their home wifi network.  Initial reports mentions that the router being used is the TP-Link Archer C7 router, but it has been found that other routers including Synology, Netgear, Linksys and Asus are also affected

 

"This issue stems from these devices' "Cast" feature, which sends MDNS multicast discovery packets in order to discover and keep a live connection with Google products such as Google Home. These packets normally sent in a 20-second interval. However, we have discovered that the devices will sometimes broadcast a large amount of these packets at a very high speed in a short amount of time. This occurs when the device is awakened from its "sleep" state, and could exceed more than 100,000 packets. The longer your device is in "sleep", the larger this packet burst will be. This issue may eventually cause some of router's primary features to shut down - including wireless connectivity."

 

Source: https://www.gizmodo.com.au/2018/01/your-chromecast-or-google-home-might-be-screwing-up-your-wi-fi/

Source: https://www.cnet.com/how-to/how-to-keep-google-home-chromecast-from-killing-your-wi-fi/

Source: https://9to5google.com/2018/01/15/google-chromecast-home-wifi-outage/

Source: http://www.androidpolice.com/2018/01/14/google-home-max-appears-killing-wifi-networks/

 

Google forums also point to Google devices killing home wifi :

 

https://productforums.google.com/forum/#!msg/googlehome/MmnsVnSxdQc/qBJF2KJ1AQAJ

 

The issue has been confirmed with google:

 

https://support.google.com/googlehome/answer/7634752

 

The fix appears to be an update to Google Play Services version 11.9.75 (you may have to sign up for the beta program to get this version)

 

[ItsMitch]

3 minutes ago, Chungerz said:

The fix appears to be an update to Google Play Services version 11.9.75 (you may have to sign up for the beta program to get this version)

 

It's no longer under Beta Program, it got fixed last night.

Quote

The team has identified the issue and is actively releasing a fix, which will start rolling out via a Google Play services update this Thursday, January 18.

 

[ShredBird]

Pretty interesting little bug.  I've got nothing but Android phones in my house, a Google Home and an Nvidia Shield all utilizing Google Cast.  Can't say I've noticed any slow downs, but nonetheless, I'll be happy that it gets fixed.

[MrRemnant]

2 minutes ago, Chungerz said:

If you have a Google home and/or Chromecast device, it may be the cause of your wifi dropouts.

 

It seems to affect people who have android phones and google home and/or chromecast devices connected to their home wifi network.  Initial reports mentions that the router being used is the TP-Link Archer C7 router, but it has been found that other routers including Synology, Netgear, Linksys and Asus are also affected

 

"This issue stems from these devices' "Cast" feature, which sends MDNS multicast discovery packets in order to discover and keep a live connection with Google products such as Google Home. These packets normally sent in a 20-second interval. However, we have discovered that the devices will sometimes broadcast a large amount of these packets at a very high speed in a short amount of time. This occurs when the device is awakened from its "sleep" state, and could exceed more than 100,000 packets. The longer your device is in "sleep", the larger this packet burst will be. This issue may eventually cause some of router's primary features to shut down - including wireless connectivity."

 

Source: https://www.gizmodo.com.au/2018/01/your-chromecast-or-google-home-might-be-screwing-up-your-wi-fi/

Source: https://www.cnet.com/how-to/how-to-keep-google-home-chromecast-from-killing-your-wi-fi/

Source: https://9to5google.com/2018/01/15/google-chromecast-home-wifi-outage/

Source: http://www.androidpolice.com/2018/01/14/google-home-max-appears-killing-wifi-networks/

 

Google forums also point to Google devices killing home wifi :

 

https://productforums.google.com/forum/#!msg/googlehome/MmnsVnSxdQc/qBJF2KJ1AQAJ

 

The issue has been confirmed with google:

 

https://support.google.com/googlehome/answer/7634752

 

The fix appears to be an update to Google Play Services version 11.9.75 (you may have to sign up for the beta program to get this version)

 

Well... I don’t have this but my WiFi’s still $h!t. 

[Chungerz]

6 minutes ago, SC2Mitch said:

It's no longer under Beta Program, it got fixed last night.

 

yeah i thought it was a bit weird, they mentioned they released but but the update didn't get to me, i still had the update in Nov, so i signed up to the beta and got it.

[Dabombinable]

So effectively they would send out a mini DNS attack to the router if left asleep too long.

[Chungerz]

17 minutes ago, Dabombinable said:

So effectively they would send out a mini DNS attack to the router if left asleep too long.

more like a DOS attack if your android phone is asleep for too long which is sending burst packets to the router when it wakes. The number of packets being sent is proportional to the time it has been asleep.

[Dabombinable]

7 minutes ago, Chungerz said:

more like a DOS attack if your android phone is asleep for too long which is sending burst packets to the router when it wakes. The number of packets being sent is proportional to the time it has been asleep.

I meant DOS. Still haven't had my morning coffee.

[Cheezdoodlez]

Hm. My girlfriends routers disconnects all Wi-Fi connections after like 10-20seconds when we're trying to cast stuff to her chromecast and then bounce on and off in 10-20seconds intervals before shutting down for 30+minutes after a couple of minutes. I've blamed her craptastic ISP-provided router but maybe it's the Chromecast that's causing these issues? If so good news I guess.

[mynameisjuan]

I have logging emailed to me on my router and I have been seeing DOS protection logs for months. Couldnt figure out what caused it but good to know.