Google Nest Wifi with wired Ethernet Backhaul to 2 Google WiFi pucks has slow wired upload speeds

[Esteban4u]

I have Verizon FIOS gigabit internet with 1000/1000 speeds. My Google Nest WiFi mesh system is wired like so: Verizon Modem --> Google Nest Wifi router --> TP-Link Unmanaged Switch (TL-SG108E) --> 2 Google WiFi Pucks --> computers connected via ethernet at each puck. The Google Nest Wifi router, switch and Google WiFi pucks all have wired backhaul to each other via Cat 6 ethernet cables. When I test from either wired computer using either speedtest.net or fast.com, I get 400 to 850 mbps (varies wildly with every test) down and .05 to 5 mbps up. This is nowhere near the 900/900 I get when I bypass the Google Nest Wifi router altogether and plug an ethernet cable from one of the wired computers directly to the Verizon Modem. I've also tried bypassing the Google WiFi pucks and switch and had my wired computers connect directly to the Google Nest Wifi router via cat 6 ethernet, I still get the same slow upload speeds. Strangely, when I have the normally wired computers connect via wireless, I get 75 to 150 mbps both down and up. I've tried rebooting the Verizon modem, rebooting the Google Nest Wifi router, rebooting the entire network, turning off preferred activities in the Google Home app and making sure there are no devices being prioritized. My Google Nest Wifi router is currently on firmware version 14150.376.32. Not sure what do at this point, but it's getting difficult to watch Youtube videos and video conference for work. I don't want to change to another WiFi mesh system as I'm a fan of Google products but seeing how so many people in this community are having similar connectivity issues like this, it getting harder to justify staying with Google networking products.

[olavrb]

Your switch has features that might conflict with Nest Wifi, most relevant here is QoS and loop protection/ detection. See specs:

• https://www.tp-link.com/us/business-networking/easy-smart-switch/tl-sg108e/

See if you can get that disabled, if not get a truly unmanaged, dumb switch.

With that fast internet speeds, the QoS (fq_codel) on Nest Wifi should turn itself off, but I don't know the threshold exactly. One more thing to try is to disable all preferred activities inside the Google Home app -> Wi-Fi (icon) -> Settings (icon).

[Esteban4u]

Hi thanks for the reply. I've already tried bypassing my network switch by connecting a cat 6 ethernet cable from my computer to the Nest WiFi router itself. I still get the same slow upload speed.

[Esteban4u]

Forgot to mention I've also  disabled all preferred activities in the home app.

[olavrb]

Ok. You haven't set a priority device either? Then, other than factory resetting and setting up from scratch, I'm out of ideas for what to try with Nest Wifi. I get close to 900/900mbps with my Nest Wifi router by wire, also through a Netgear GS108 switch.

The modem, is it in bridge mode? Or do you run double NAT?

[Esteban4u]

Yup, no priority devices. The modem is just a modem, not router / switch combo, so no double NAT. I may do a factory reset, but I'll have to do it when the wife and kids aren't home or there will be a chaos of bitching and moaning that I'll have to deal with.

[Esteban4u]

I ended up performing a factory reset on the Google Nest WiFi router and that finally fixed the slow download speeds.

[Jeff]

Hey Esteban4u,

I'm happy to see that you're having better performance since resetting your setup. I wanted to check in and see if you were ok marking this as resolved or if you wanted to wait and monitor things for a little bit first. Also, let me know if you had any other questions or needs.

Thanks,
Jeff

[Jeff]

Hey Esteban4u,

I just wanted to follow up once more to see if you were still needing some help here. If so, just let us know.

Thanks,
Jeff

[Jeff]

Hey everyone,

It looks like we've slowed down here. We'll be closing up the thread in the next day unless anyone else has any input or needs anything else. If so, just let me know and we can keep this open a bit longer.

Thanks,
Jeff