Adding a 2nd Google Nest Wifi Router to Existing Nest Router backhauled via Ethernet

[tomn68]

I have a Google Nest Router + two satellites.  I also have 3 older Google Wifi pucks in the house. The wifi speed I'm getting in the office is about half of what I get when near the router. 

My question is, can I backhaul via ethernet to the office with one of the Google Wifi pucks or buy another Nest router (they're inexpensive now) and also using the ethernet ports.

Ideally, the unit in the office would provide wifi as well as a wired connection to a PC.

I've read posts that I THINK are saying that's not really possible where the puck or 2nd Nest router wired backhauling will not then allow that unit to be part of the mesh. Do I have that right? 

[MichaelP]

Hello @tomn68 

Yes, you can connect one of your existing Google WiFi units as a new secondary/point via Ethernet. When doing this, it's important that it be connected to a network rooted in the primary Nest WiFi Router unit's LAN Ethernet port (not connected to the "outer" network your primary Nest WiFi Router unit's WAN Ethernet port is connected to). When you do this, it will provide WiFi service as part of your network to devices in the area. What you may have read is that when connecting a secondary via Ethernet, it withdraws from the wireless mesh interconnect wireless secondaries use to connect to each other and the primary. But, that hidden mesh network is only necessary for wireless secondaries. I ran a wired-only Google WiFi system with three nodes for years, and it works nicely, providing similar WiFi performance for devices near any of the secondaries and the primary.

If you do this, and have one or more Ethernet switches connected through your Nest WiFi Router unit's LAN Ethernet port, make sure they are inexpensive, unmanaged switches rather than "smart" / managed switches, which can cause problems due to "loop detection" features.

One more thing you asked about – when you connect the Google WiFi unit via Ethernet, you can use the other port to connect a wired device nearby, since, on secondaries, both ports are bridged together. However, I personally prefer putting at least a small, inexpensive, unmanaged Ethernet switch at the end of the cable run to that remote location (e.g., your office), and then connect the Google WiFi unit and one or more devices in that area directly to that switch. You may have a printer, for example, that you want to connect via higher performance Ethernet. I find this provides a bit better performance and better reliability than relying on the (software) bridging through the two ports on a secondary Google WiFi unit.

Here's a support article with more details: https://support.google.com/googlenest/answer/7215624?hl=en 

[tomn68]

Thanks. Just to make sure I understand...  

What I have currently:

Modem -> Nest router -> unmanaged switch -> Other devices  

I also have a bunch of secondary Nests and Google Wifi Pucks in my mesh once of which is in my office.

Then suggested...

Modem -> Nest-Unmanaged router -> unmanaged switch -> Small Unmanaged Switch->Office Google Wifi WAN port (and then also computer/printer into the small unmanaged switch - and needing to set the puck to be wired)

I think that's what you're saying, right?

Then what I was unclear on is that I think you're saying that this Google Wifi puck in the office will provide wifi to the office but it won't be part of the mesh meaning if it sits between the Nest router and another point on the other side of the house that the nest router will have a long jump to connect to the other unit because the office puck won't be part of the mesh extending out across the house. 

Do I have this right?

[MichaelP]

Yes, that setup should work fine – modem –> Nest WiFi Router –> unmanaged switch –> small unmanaged switch –> Google WiFi (plus other office devices connected to the small unmanaged switch).

The interaction between wired and wireless secondaries is actually rather complicated. But, the simplified explanation is this: a wired secondary does not act like a base station for more distant wireless-only secondaries.

But, it turns out that doesn't really matter, because multi-hop topologies in pure wireless mesh networks are extremely unlikely anyway. That distant wireless secondary is already talking directly to the primary at fairly low speed, and converting an intermediate secondary from wireless to wired isn't going to change that. Wireless nodes select a "next hop" based on what gets their packets to the destination using the fewest hops possible – even if that means slowing way down to get through. So, for traffic headed to the internet (for example), if a secondary can get through to the primary in one hop, then that's what it will do, even if other wireless secondaries are in between. There's only one channel for all of this, so multiple hops would require sending the data over that channel multiple times anyway. So, it wouldn't necessarily be any faster.

This is why the optimal placement for these systems is to have the primary as close to the center of the home as possible with secondaries no more than one or two rooms away from there in any direction (including above and below). You want them all to be close enough to get a strong 5GHz connection for themselves. From there, they will provide 2.4GHz and 5GHz coverage to more distant client devices. Attempting to build a multi-hop topology generally results in poor performance.

Wiring secondaries does let you place a secondary further away, though – including in outbuildings. Because it is talking to the primary via Ethernet instead of the wireless mesh. So, it sidesteps all of the constraints.

[tomn68]

Great explanation.  I wish I could get my primary router to the center of the house. Problem is modem is in the family room and not center of the house.  I'll have to think about how I could that. But I think the speed I'm getting throughout the house will be good enough. Currently the Home app reports "Great Connection" on each of them so I guess that's good.

[MichaelP]

Just a thought – the primary doesn't have to be close to the modem. It just needs to be connected to it via its WAN Ethernet port. So, if you have a longer cable run that you can repurpose, it would let you move the primary. The problem with that is getting another cable back to your core distribution switch fed from the primary's LAN Ethernet port. But, getting a "great" rating on a mesh test is a good sign that maybe you don't need to change anything (other than wiring your office secondary).