new google mesh

[phantm]

I just purchased a google router and point. Tonight I went into my rogers modem and turned off wifi for that and plugged in the google router. My google home application found the device and set it up. It then asked me if there was any other devices and I went and setup the point. After both these were completed I went around and rejoined the lights/google minis/google hub/ and wireless laptops. Everything went extremely smooth.
Then I was in my living room and I went to sign on to plex to watch a movie and it said that the server wasnt found. I went in and verified it was on and then did some digging.

It seems the the google mesh has configured itself on 192.168.86.x when my home network is on 192.168.0.x

I have gone into the settings of the google mesh and attempted to change the ip address but after hitting save and going out of the screen and back in the numbers have reverted.

I know that I could open up the octet with a subnet change, but that seems kind of a silly thing to have to do on a home network. 

One other thing that I noticed is that the WAN setting is on DHCP and showing a WAN IP of 192.168.0.196 which seems to indicate it got passed the correct address from the modem.

Any thoughts?

Thanks all

[olavrb]

The primary Google/ Nest Wifi point will act as a regular NAT router by default. Short answer is to add more LAN ports to the primary puck (https://support.google.com/googlenest/answer/6274262?hl=en) and bridge your modem (https://support.google.com/googlenest/answer/6277579?hl=en).

There are a lot of topics about this if you need more info.

[Tatsquare]

Confirms what I tried to do   New Google Mesh (GM) router and 2 points working ok with Xfinity modem/router in router mode. No problem  To reduce RF clutter and potential confusion, enabled Bridge mode on Xfinity modem/router.  Google router stopped working, not happy.  Reversed all and everyone happy.  What is needed to make Xfinity Bridge mode work with GM?

[olavrb]

Nest Wifi should pick up the changed WAN IP address when bridging the modem, as it uses DHCP by default, but my experience as well is that it doesn't. Or if it does, it's very slow. Try to restart your Nest Wifi network a few times, maybe it picks up the change.

Here is relevant doc:

• https://support.google.com/googlenest/answer/6246630?hl=en

You could try to connect your PC to Nest Wifi after bridging the modem, then go to following address in your browser to see what WAN IP it report it's using:

• http://192.168.86.1/api/v1/status

Before bridging it should be a local IP address (known as RFC 1918). When bridged, it should be a global IP address.

In a similar case probably a year ago, new WAN ip, but due to new ISP at home, I ended up factory reseting my Nest Wifi and set it up from scratch.

Edit: Related thread:

• https://www.reddit.com/r/GoogleWiFi/comments/a9v4d4/google_wifi_doesnt_work_with_modem_in_bridge_mod...

[Tatsquare]

Thanks.  On target support. Happy Holidays.

[olavrb]

Glad to help!

Thanks, you too. 🙂

[Jeff]

Hi, everyone.

It looks like olavrb was able to sort this out with phantm and get things resolved. Before I close up the thread, I just wanted to do one quick check to make sure we're all set here. If anyone needs anything else, just let me know.

Thanks!

[Jeff]

Hi, everyone.
Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.
Thanks.

[Tatsquare]

thanks, Jeff.

My Google Mesh is working OK.  You or someone else posted that the Xfinity modems do NOT work in the Bridge Mode with Google Nest (or perhaps ANY mesh network) - certainly confirmed my experience.  So I have just said "that's the way it is."   I have seen no particular degradation in Google Nest network from the simultaneously operating Xfinity wifi RF.  You'd prefer to clean up the wifi environment but I am not surprised if Xfinity ignores that.

[Jeff]

Thanks for the update, Tatsquare. Hopefully everything keeps working well for you, but if you have any issues going forward, please feel free to open up a new thread. For now, I'll go ahead and close this one.

Thanks!