Does the Google MDNS packet issue still exists ?

Home Forums Computers (software & hardware) Others Does the Google MDNS packet issue still exists ?

This topic contains 0 replies, has 1 voice, and was last updated by UK Sentinel UK Sentinel 2 months ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #4377
    UK Sentinel
    UK Sentinel
    Moderator

    If you use Google Home devices, they may still be problematic.  Google Home, Google Home Mini, Google Home Hub crashing wifi routers.

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

    Known Issue: Slow Wi-Fi performance with Android and Chromecast built-in devices
    We’re aware of an issue where Chromecast built-in devices may be affecting Wi-Fi network performance Summary of Issue.

    (Some are reporting that even though Google have released  firmware fixes, the issue still remains or a newer problem has resulted due to the Google updates)

    In certain situations, a bug in the Cast software on Android phones may incorrectly send a large amount of network traffic which can slow down or temporarily impact Wi-Fi networks. The specific impact to the network will vary depending on the router.Who is impacted?

    People with an Android phone and a Chromecast built-in device (such as a Chromecast or Google Home device) on the same Wi-Fi network may experience this issue.

    Google plans to release a fix today for a problem that has been disrupting WiFi performance for some users that have either a Chromecast or a Home device on their network. The problem first surfaced when people reported their Google Home Max was crashing their TP-Link Archer C1200 router. It has since been determined that the problem is not confined to the Home Max or TP-Link routers.

    After their router was singled out as having a problem, TP-Link’s engineers dug into what was causing the C1200 to crash. They discovered the problem is rooted in recent versions of the Android operating system and some of Google’s apps.  Here’s their explanation of what’s going wrong.

    ‘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 [are] 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’.

    Google dug further and discovered that the core of the problem lies in the Cast software on Android phones. The problem can manifest when an Android phone is on the same WiFi network as a device with Cast built in such as a Home smart speaker or a Chromecast. How the combo affects WiFi performance varies with different routers. Some routers are unaffected, others crash or become unstable.

    https://support.google.com/googlenest/thread/1408816?hl=en

    • This topic was modified 2 months ago by UK Sentinel UK Sentinel.

    In a completely sane world, madness is the only freedom (J.G.Ballard).

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.