• Todas as comunidades
    • Todas as comunidades
    • Fóruns
    • Idéias
    • Blogs
Avançado

O que você está procurando? Pergunte a um especialista!

Kudos1 Stats

Google hardware use with TP-Link

Hello all. For those of you who are experiencing frequent wifi disconnects and are using Google hardware/software and on TP-link this article is for you. It MAY explain some of the issues you are seeing in certain circumstances on Core.

https://www.neowin.net/news/googles-hardware-and-software-causing-wi-fi-disconnects

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.437 / NCSP 22.17.0.183 / Norton Core v.282 on Android 1.93

Respostas

Kudos0

Re: Google hardware use with TP-Link

So I find this really interesting.  We are an Android phone household w/Google Home & Chromecast, among countless other devices (Amazon Echo, Hue, Nest, etc).  Perhaps these logs Norton is collecting need to look for Android/Google devices?

Putting all of this together, I found the other user who discussed a hot Core an interesting conversation as well.  I noted that it seemed most every time wifi went down and I had to manually restart the Core, the Core was warm/hotter than normal.  It made me think that the firmware Norton released possibly had some sort of memory leak, in which case the hardware would either run out of memory or overheat attempting to process, similar to what can occur w/hardware and peripherals in PCs.  Which is possible, regardless of the following.

From http://www.tp-link.com/us/faq-2050.html 

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.

Generally, you will need to perform a reboot to release the memory to solve this issue.  You may also try disabling the “Cast” feature on your Android device to help mitigate the issue until an update is released to permanently fix this issue on the device itself.

Is it possible that this issue is causing the Core to run out of memory or fail in an attempt to process all of this activity?  

Now the only thing I can say is the Core has failed and gone down while NO ONE is in the house. i.e no Android phones in the house.  So unless a Google Home or Chromecast wakes itself up and causes this, I'm not sure then if that's the actual issue plaguing everyone around here, but it is something to at least consider that may be effecting it in addition, regardless.

p.s. Anyone know the date when this alleged problematic Android update released?  So far couldn't find a date stated.

Kudos0

Re: Google hardware use with TP-Link

I cannot find a reference to WHEN the issue began or with which update. The issue is....Cast devices when awaken from sleep will have gathered a serious blast of data packets stored while in sleep mode. Thus overloading bandwidth and causing devices to function warmer than normal. The best thing is disconnect these devices from  your network until such time Google Play has released a fix.

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.437 / NCSP 22.17.0.183 / Norton Core v.282 on Android 1.93
Kudos0

Re: Google hardware use with TP-Link

  1. Linksys: https://community.linksys.com/t5/Wireless-Routers/WRT32x-and-WRT3200ACM-WiFi-Issues/m-p/1260725#M346085
  2. Netgear: https://community.netgear.com/t5/Orbi/OrbiOS-2-1-1/td-p/1476960
  3. TP-Link: http://forum.tp-link.com/showthread.php?101240-Archer-C1200-v2-management-interface-and-Wifi-dies-after-a-little-while
  4. https://forum.synology.com/enu/viewtopic.php?f=265&t=137668
  • From Tp-Link: Following initial research and investigation, our Engineering Team is confident that they've determined one of the key origins of the issue. From what we have gathered so far, the issue appears to be related to some recent releases of Android OS and Google Apps. This issue stems from these devices' "Cast" feature, which sends MDNS multicast discovery packets in order to 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 the "sleep mode", and could exceed more than 100,000 packets in a short amount of time. 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.
  •  
  • From Linksys: I will keep the overall description short here, but this firmware incorporates a new WLAN driver that will help mitigate an issue that was discovered where Android devices coming in and out of sleep mode would crash the Wireless Network.

https://productforums.google.com/forum/#!topic/googlehome/lssgm7TjgGs;context-place=forum/googlehome

Kudos0

Re: Google hardware use with TP-Link

I have a question regarding the Google casting problem that was affecting the WiFi networks.  Shouldn't this activity have been detected by the Core and quarantined that device before it shut down the Wifi network?

Kudos0

Re: Google hardware use with TP-Link

Good question MannyT. Logically Core should sense the large traffic bursts as a DDoS and terminate its connection to the device in question vice the carrier. I suppose since the port scans associated with that aren't detected Core thinks the ISP dropped and requires a reboot instead.

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.437 / NCSP 22.17.0.183 / Norton Core v.282 on Android 1.93
Kudos0

Re: Google hardware use with TP-Link

Google has released a fix for their Google Play service regarding this issue. https://www.neowin.net/news/google-fixes-bug-that-had-caused-wi-fi-disconnections

Cheers

Retired military (Navy 1980-2002) AO1 (AW) Aviation Warfare Specialist "From DOS to Windows10 what a journey it has been" / MS Certified Professional / Windows 10 Professional x 64 version 1809 / build 17763.437 / NCSP 22.17.0.183 / Norton Core v.282 on Android 1.93

This thread is closed from further comment. Please visit the forum to start a new thread.