Reserving IP addresses for FUTURE WiFi Pro devices-

[OtisBme]

I have devices that do not have dhcp mode and require having addresses set internally before connection to the LAN.  Google home presumes that the device is ALREADY active on the LAN  before creation of a reserved static address for that device. If I use an IP address that I know to be free, will the Nest wifi pro router see it and allow that address when connected, and THEN allow me to reserve that address?

[Dan_A]

Hi OtisBme,

Thanks for posting. Unfortunately, Google Nest Wifi Pro does not offer the flexibility to set a static IP address before the device joins the network. Your observation about Google Home app assuming the device is already active is accurate. It presents a challenge for manually configuring devices that require static IP addresses before connecting.

While using a known-free IP address might seem logical, the Nest Wifi Pro prioritizes DHCP assignments and might not honor manually configured static addresses unless the device is already connected. This can lead to conflicts and potential network issues.

Here are a couple of alternative approaches you can consider:

1. Temporary DHCP Lease:

• Connect the device using DHCP temporarily.
• Once connected, access the device's configuration interface and note the dynamically assigned IP address.
• Use the Google Home app to create a static IP reservation for that specific IP address. This binds the address to the device's MAC address, ensuring it gets the same address whenever it connects.
• Disconnect and reconnect the device. It should now receive the reserved static IP address. This may or may not work.

2. Manual Configuration with Separate Router:

• If the above approach doesn't work or is inconvenient, consider using a separate router or switch with manual IP address assignment capabilities.
• Connect the device to the separate router and assign the desired static IP address.
• Connect the separate router to the Nest Wifi Pro network. This way, the device retains its static IP address while being part of the broader network managed by Nest Wifi Pro.

Additional Notes:

• Ensure the static IP address you choose is within the correct subnet of your Nest Wifi Pro network.
• Avoid using IP addresses reserved for network functions (e.g., gateway, subnet mask) or already assigned to other devices.
• Consult the device's manual or manufacturer's support for specific instructions on accessing its configuration interface and setting a static IP address.

By exploring these options, you can somewhat overcome the limitations of manually assigning static IP addresses before connecting with Nest Wifi Pro and successfully configuring your devices. All these are helpful options, but they are not fully recommended by Google.

For more information, check out this helpful guide: DHCP IP reservation or Set a Static IP address for a device.

Best,

Dan

[OtisBme]

Dan- Thanks for the detailed response. Your first suggestion matches the solution I used. It does work if you disconnect the device, set its fixed IP, then re-connect it.

I guess it is pointless to ask, since you cannot reserve an address for a single device unless it is already on the network, but it really should be possible to reserve a range of unassigned IP addresses, sort of a "keep out" zone for dhcp. this would allow re-connecting fixed-IP devices with the confidence that Nest has not given its address to another already. I won't even try.

Google could do a lot to improve this process. If you hit the "add-IP- reservation plus sign", you are given a random list of current dhcp clients, but it ONLY lists the name and MAC address of each. it really should present this list in ascending IP address order and list the current IP address for each. often as not. the name is "unknown, so it takes a lot of eye strain and inference to even locate the device you are after. 

THEN- when you pull up the list of existing address reservations, it presents the devices in random order and lists ONLY the IP address, omitting the MAC!! Again, it should be sorted by ascending IP address and include the MAC address. Just moronic, I guess the IT crew at Google does not want to make things too easy for mere mortals.

Yes, you can and should go through the list of devices and give each meaningful names, but even that is a way too awkward process. I have many dozens of devices on my LAN that are affected by these issues.  Come ON already, Google!!!-  Otis

[Dan_A]

Hi Otis,

We understand that it would be a very useful feature, and we appreciate you sharing your thoughts with us. Rest assured that we're always looking for ways to improve. In the meantime, you can send feedback about it. Let us know if you have other questions or concerns, we are here to help.

Kind regards,

Dan