Hardwire Google Nest Wifi routers, Google Wifi points and other devices

Google Nest Wifi and Google Wifi are mesh Wi-Fi systems and do not need to be physically wired together via Ethernet cables to provide whole-home coverage. However, if you prefer to connect directly to your Google Nest Wifi router or Google Wifi point, here are some possible setups.

  • Chain multiple Google Nest Wifi routers and/or multiple Google Wifi points together.
  • Connect devices like a computer or TV directly into the LAN port of your Google Nest Wifi router or Google Wifi point. You can connect additional devices by adding LAN ports with a switch.
  • Use 3rd party routers as part of your network.

Note:

  • Do not connect any devices (like a computer, switch, or another Wifi point) to a Google Nest Wifi router or Google Wifi point until after setup.
  • Google Nest Wifi routers cannot be connected to OnHub devices. 
  • Google Nest Wifi points cannot be hardwired.

Supported setups:

Use multiple Google Nest Wifi routers, Google Wifi points, and/or OnHub devices

 Note: In the following diagrams, "→" means to connect via wired Ethernet.

(✓) Modem → Google Nest Wifi router or Primary Wifi point → Google Wifi point or another Nest Wifi router

  1. Modem’s LAN port connects to Google Nest Wifi router or a primary Wifi point’s WAN port  via wired Ethernet
  2. Google Nest Wifi router or primary Wifi point's LAN port connects to another Google Nest Wifi router or Google Wifi point's WAN or LAN port via wired Ethernet

You can chain multiple Google Nest Wifi routers or Google Wifi points via wired Ethernet.

(✓) Modem → Google Nest Wifi router or primary Wifi point → Google Nest Wifi router or Google Wifi point → Google Nest Wifi router or Google Wifi point → and so on...

Include a switch downstream of the Google Nest Wifi router or primary Wifi point

Learn more about using switches with Google Nest Wifi or Google Wifi devices. 

 Note: In the following diagrams, "→" means to connect via wired Ethernet.

(✓) Modem → Google Nest Wifi router or primary Wifi point→ Switch → Google Wifi point(s)

  1. Modem’s LAN port connects to Google Nest Wifi router or primary Wifi point’s WAN port  via wired Ethernet
  2. Primary Wifi point’s LAN port connects to switch’s WAN or uplink port via wired Ethernet
  3. Switch’s LAN port(s) connects to any Google Wifi point's WAN port via wired Ethernet

Switches and Google Wifi points may be connected in any order (as long as they're downstream of the Google Nest Wifi router or primary Wifi point) and you may connect several of these devices via wired Ethernet. Connecting downstream is important as it allows the Google Nest Wifi router or primary Wifi point to manage the downstream Wifi points over the wired Ethernet.

(✓) Modem → Google Nest Wifi router or primary Wifi point → Switch → Google Nest Wifi router or Google Wifi point

                                                                                                                             → Google Nest Wifi router or Google Wifi point

(✓) Modem → Google Nest Wifi router or primary Wifi point → Google Wifi point → Switch → Google Wifi point

                                                                                                                                                                  → Google Wifi point

Include a 3rd party router upstream of the primary Wifi point (Not recommended)
TIP: Instead of buying a new switch, it might be possible to use a 3rd party router as a switch. To do this, set the 3rd party router in bridge mode and disable its Wi-Fi functions. Refer to the 3rd party router manual on how to do this.
 Note: In the following diagram, "→" means to connect via wired Ethernet.

(✓) Modem → 3rd party router → Google Nest Wifi router or primary Wifi point → Google Wifi point

  1. Modem’s LAN port connects to 3rd party router’s WAN port via wired Ethernet
  2. 3rd party router’s LAN port connects to the Google Nest Wifi router or primary Wifi point's WAN port via wired Ethernet
  3. Google Nest Wifi router or primary Wifi point's LAN port connects to any Google Wifi point's WAN port via wired Ethernet (or via a switch as shown above)
With this configuration, you may run into Double NAT, which isn't necessarily a problem. But if it is causing problems, we recommend putting your 3rd party router in bridge mode. Once in bridge mode, you may choose whether or not to turn Wi-Fi off on your 3rd party router.

What NOT to do:

Wire a Google Nest Wifi router or primary Wifi point to other points in the same switch

 Note: In the following diagrams, "→" means to connect via wired Ethernet.

(X) Modem → Switch → Router or primary Wifi point

                                       → Google Wifi point

(X) Modem → 3rd party router → Switch → Google Nest Wifi router or primary Wifi point

                                                                         → Google Wifi point

  1. Modem’s LAN port connects to Switch’s WAN or uplink port via wired Ethernet
  2. Switch’s LAN ports connect to both a primary Wifi point and another Google Wifi point’s WAN ports point via wired Ethernet

For correct operation as a mesh point, a Google Nest or Google Wifi point should be on the network address subnet that is created by the primary router. This means the Wifi point should always be wired downstream from the primary.  In the diagrams above, the reason the mesh won’t work is because the Google Wifi point is unable to get an IP address from the primary router. Rather, both, the primary router and the Wifi point get IP addresses from the upstream modem and so the Google Nest Wifi router or primary Wifi point isn’t able to form the mesh with the Wifi point.

For correct operation, the router or primary Wifi point should either be plugged in between the modem and the switch, or the point should be plugged in downstream of the router or primary Wifi point.

(✓) Modem → Google Nest Wifi router or primary Wifi point→ Switch → Google Wifi point

(✓) Modem → Switch → Router or primary Wifi point → Google Wifi point

Wire Google Nest Wifi routers or primary Wifi points and Google Wifi points into the same 3rd party router

 Note: In the following diagrams, "→" means to connect via wired Ethernet.

(X) Modem → 3rd party router → Google Nest Wifi router or primary Wifi point

                                                       → Google Wifi point

  1. Modem’s LAN port connects to 3rd party router’s WAN port via wired Ethernet

  2. 3rd party router’s LAN ports connect to both a Google Nest Wifi router or primary Wifi point and another Google Wifi point’s WAN ports via wired Ethernet

This is a similar concept as the switch example above. In this example, the Google Wifi point should be plugged in downstream of the Google Nest Wifi router or primary Wifi point instead:

(✓) Modem → 3rd party router → Google Nest Wifi router or primary Wifi point → Google Wifi point

Wire a 3rd party router downstream of the Google Nest Wifi router or primary Wifi point

 Note: In the following diagrams, "→" means to connect via wired Ethernet. 

(X) Modem → Google Nest Wifi router or primary Wifi point → 3rd party router → Google Wifi point

  1. Modem’s LAN port connects to Google Nest Wifi router or primary Wifi point’s WAN port via wired Ethernet
  2. Google Nest Wifi router or primary Wifi point’s LAN port connects to 3rd party router’s WAN port via wired Ethernet
  3. 3rd party router’s LAN port connects to Google Wifi point’s WAN port via wired Ethernet

In this case, if the 3rd party router is not in bridge mode (i.e., NAT is still active), any wired or wireless clients (including the Google Wifi point) may not be able to communicate with the Google Nest Wifi router or primary Wifi point as the 3rd party router NAT will create a separate subnet.

In order to work as desired, the 3rd party router should be set to bridge mode, replaced with a switch, or else removed from the system:

(✓) Modem → Google Nest Wifi router or primary Wifi point → Google Wifi point

(✓) Modem → Google Nest Wifi router or primary Wifi point→ Switch → Google Wifi point

Was this helpful?
How can we improve it?