cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Can't Set a custom LAN IP

physx
Community Member

I tried to change LAN IP and range, but nothing changes when I click SAVE.

 

13 REPLIES 13

olavrb
Platinum Product Expert
Platinum Product Expert

What are you guys trying to save it to? It should be a RFC 1918 compliant adress, subnet mask of 24, and it shouldn't conflict with other address spaces used in your local network (if you run double NAT for instance).


I don't work for Google.

physx
Community Member

Trying to change from 192.168.86.1 to 192.168.1.1 then browser spins for a while, but when it comes back the IP has not changed.

olavrb
Platinum Product Expert
Platinum Product Expert

The LAN IP must be changed from the Google Home app like so:

But that does not work you say?

What other networking devices do you have in your network?

What's the WAN IP of the primary Nest Wifi puck: A typical WAN IP, or a typical LAN / RFC 1918 IP?


I don't work for Google.

physx
Community Member

Did that, but changes did not save.

physx
Community Member

Nest puck is 192.168.86.1

Disconnected all other devices from puck while trying to change to 192.168.1.1

olavrb
Platinum Product Expert
Platinum Product Expert

WAN IP, not LAN.


I don't work for Google.

physx
Community Member

192.168.12.xxx

olavrb
Platinum Product Expert
Platinum Product Expert

Alright. So you have double NAT, which is not recommended. And WAN IP might conflict with the LAN IP you are trying to set, based on whatever logic Google uses for validation. But only Google would know. Thus I escalated this thread.


I don't work for Google.

olavrb
Platinum Product Expert
Platinum Product Expert

While we await a response from Google: I see that you tagged iOS. There are some common problems when using iOS or iPadOS devices during setup and management in the Google Home app that you should make sure you avoid.

---

Make sure the device used for the setup process with the Google Home app have no VPN enabled/ connected; not any 3rd party product, nor the "Apple iCloud Private Relay" ( https://support.apple.com/en-us/HT212614 ).

Make sure the Google Home app has been granted permission for "local network access" ( https://support.google.com/chromecast/answer/7172427?hl=en ).

Make sure that proxy is set to disabled while connected to the Nest Wifi network ( https://www.expressvpn.com/support/troubleshooting/disable-proxy-safari/#ios ).

IPv6 on Nest Wifi has caused strange problems lately. One thing to try is to disable IPv6 ( https://support.google.com/googlenest/answer/6361450?hl=en ) while doing the changes, then leave IPv6 off or enable it again afterwards.

---

More things I thought of just now:

  • Have you set up any IP reservations in the Google Home app? Try to remove those first.
  • Have you tried to factory reset your Nest Wifi network and set it up from scratch, changing LAN IP as one of the first things, even before adding any more pucks? Worth trying in case there are some conflicting settings the Google Home app does not give any feedback about.

I don't work for Google.

Juni
Community Specialist
Community Specialist

Hi folks,

 

Sorry for the late response. I just wanted to follow up to see if you still need our help. Please let us know as we would be happy to answer any questions you may have.
 

Thanks,

Juni

physx
Community Member

still not working

Juni
Community Specialist
Community Specialist

Hi there,

 

Since the steps didn't work on your end, we'd be happy to take a look into this for you. Please fill up this form with all the needed information then let me know once done.


Best,

Juni

Juni
Community Specialist
Community Specialist

Hi physx,

 

We got your form — thanks for filling it out. Our team will reach out to you via email anytime soon. Please continue the conversation there as this thread will be locked after 24 hours.


Cheers,

Juni