Nest Wifi Pro point slow on 6e over wireless backhaul.

[Lidelse]

So I have a nest wifi pro nest with 3 points. One main on the first floor that gets basically 900plus Mbps of the 1Gbps advertised of my fiber internet going into it. Wifi 6e connections on that point hit 600 to 700 Mbps. I have a wired backhaul point that gets over 600 Mbps and connections 300ish Mbps to 400Mbps on 6e and over 200 Mbps on wifi 5 in the basement. I also have a third point on wifi backhaul upstairs one level and one room over or so from the main point and it's getting just under 300 Mbps speed. This fluctuates obviously. The wifi 5 and 6e and ethernet connections only get 250 to like 330 Mbps depending on the fluctuation. The mesh tests all come back as great in Google home. This is something that has only happened since the latest firmware update 3.73.424613. I picked android as a platform, but it also happened on windows. My Chromecast that is running android tv 12 and using wifi 5 on 5ghz band usually has higher speeds by about 100 Mbps than android 15 on a phone or tablet does using wifi 6e on the offending point. Windows also matches the Android phone and tablet speeds both on wifi 6e and ethernet which makes me think something is off about the wireless backhaul now. I have done a factory reset. One of just that point, and one of the entire mesh. The problem persists. If it matters, I am running the public preview build of Google home on android. I know 250 to 300 something Mbps is not sluggish. But when I was getting 450 Mbps from this point via wireless backhaul before it would be great to get it again. On the devices that support it.

Any advice? 

[Lidelse]

As an addendum. If I unplug that wireless point. And connect to the main point I connect by 5ghz wifi 6 not 6e and get 593 Mbps down 329bps up roght next to where the wireless backhaul using point is. How? Is it not using wifi 6 or 6e for backhaul now? 

[catheryn]

Hello @Lidelse,

Thanks for posting in the community, I do apologize for the inconvenience you are having with your Nest WiFi points. 

I understand that the main issue here is that the issue seems to be related to a significant drop in Wi-Fi speeds on your Nest Wifi Pro mesh network after the latest firmware update. Despite trying various troubleshooting steps like factory resets and checking network settings, the problem persists. Also, I do appreciate your efforts. 

If you need to connect multiple hard-line devices after bridging a modem and router combo, you can use a switch connected to one of the primary or child points to gain additional Ethernet ports. Avoid plugging a switch directly into the modem. Doing so would place the additional devices on a separate network, making them inaccessible to other devices on your main network.

How much speed are you receiving on your modem? 

You need to do 2 speed test in a day to see if its consistent or not

If you got the same speed on the 2 test, we will need to try with the ethernet backhaul mesh

Important: Things to remember about using Ethernet to connect Wifi points:

• If your child point is connected to the parent point's LAN port via Ethernet, that Ethernet link will always be used.
• If there's a router that's not in bridge mode between the parent and child points, they might not be able to communicate.
• If there's a switch between the parent and child points, it might block Spanning Tree Protocol (STP) packets, causing performance issues. You can solve this by enabling Bridge Protocol Data Unit (BPDU) flooding on the switch.
• If you're using a 10/100 switch, a Cat 5 Ethernet cable, or a defective cable between the parent and child points, the mesh test might show lower results than if you used Wi-Fi.
• Avoid connecting devices like computers, switches, or other WiFi points directly to your Nest WiFi router or primary Google WiFi point during setup.

Let me know how this goes, and we can explore further steps to ensure your devices are working as expected.

Thanks, 

Catheryn. 

[Lidelse]

So I don’t actually need to connect hardline stuff to the point upstairs that is having the issue. I just tried it for troubleshooting. I have 1 unmanaged gigabit ethernet switch on the main point. But I always unplug it when I do a factory reset and connect the wired point in the basement through the switch after the mesh is set up it is a tp link sg105. However the basement point is not truly the problem.

There are no other routers on the network. 

This is a metronet fiber internet connection with Nokia modem inside and the ont going into the modem. The modem goes directly into the main nest wifi pro point. 

Now I did do yet another factory reset with nothing attached. And the upstairs point while still slow on wifi 6e 6ghz seems to be getting about 550 Mbps download and 600 up if you are either on wifi 6 restricting windows to 5ghz band or if your phone somehow connects to 5gh wifi 6 there instead of 6e. Which is like 300 Mbps down now and 350ish up. Mind you I get the same speed on wifi 6 next to the upstairs point if it is unplugged and I’m connected to the main point on the main floor.

I have done multiple speed tests every day for two weeks. On the end devices, and the one on Google home for the wifi. The main point consistently pulls 950 to 980 Mbs up and down from the modem as I have a 1 Gbps up/down fiber connection so that is as exoected. 

All ethernet cables in the system are at least cat 6. The one from the modem to the main point is cat 7 but was bought for future proofing more than current need.

I still get over 700 Mbps down over wifi 6e on the main point when I am on the main floor and closer to that point.

I am concerned now it may not be the firmware because this one point (the upstairs one) is out in the open and at least once a day is giving the yellow blinking light saying bad signal. Moving it around in that room doesn’t really change the speeds I get either. Right now it is on a table with nothing else behind and in front of nothing.  

[catheryn]

Hi @Lidelse, 

Thanks for your reply and the additional information.

A loose, damaged, or old Ethernet cable can cause several issues, including dropped packets and slow speeds. Also, it's important to be sure to use the correct port for the best performance. 

Now, we want to ensure all cables are either Cat5e or Cat6. Cat5 cables are only capable of speeds up to 100 Mbps, while Cat5e and Cat6 are capable of 1,000 Mbps. If you don't have enough Cat5e/Cat6 cables for your whole network, make sure that the connection from the Nest WiFi to the modem is using a Cat5e or Cat6 cable. Ideally, use the cable that was included with the unit for this.

• If mesh network over Ethernet: If the points are connected over Ethernet, we want to ensure child points are connected to the parent point (or switch) through the LAN port, not the WAN port. This may seem counter-intuitive, but the WAN port emulates a LAN port in child-mode, which means it has more overhead and is unable to process information as quickly as using the LAN port directly.
• If connected to the upstream router: We also want to make sure the primary WiFi point is connected to the upstream router correctly. Specifically, we want to ensure we are going from the WAN (green with a globe icon) port from the WiFi unit to the first LAN port on your router, not the WAN port, which is usually separated from the other LAN ports.  

Keep me updated to gather more information and assist you further. 

Thanks, 

Catheryn.