Does anyone know how the Google wi-fi device discovers the list of devices for the port forwarding list?
I'm trying to setup up port forwarding on a wired device, but it doesn't appear in the device list. Even when I've reserved an IP for it.
I was eventually able to set up a port forward for my device, but I still have no idea where my google wifi router gets its list of forward-able devices from. So I imagine I would have the same problem again in the future.
We have an article that talks about how port forwarding works. That article is found here: https://bit.ly/2VFhZ5S.
Looking it over, it appears that it depends on the range you're working with. Some of the options available will depend on specific devices. I'm happy to see that you got it sorted out, but if you have any issues down the line, we'll definitely be happy to help out.
The problem is, that the device is only in the list if the DHCP has assigned the address to it, if the device has set a static IP, even if it is in the desired subnetmask it will not show up, and therefore it is impossible to assign a port forwarding rule.
We'd need to be able to manually add an IP for a Port forwarding rule
It appears that all of the Google WiFi solutions (Google WiFi, Nest WiFi, Nest WiFi Pro) are only acceptable for mundane installations that don't require any customization or modification beyond just simple connections. Anything more complicated than connecting a cellphone to the WiFi is more than these devices can handle reliably.
The article doesn't give any indication of how Google Nest learns what devices are on it's local subnet, because whatever way it's currently using, it's suboptimal.
Please please please just add the feature to allow us to add NAT rules manually, we're not children.
As an update for you all, I wanted to let you know that we have a firmware update coming out now. Some people may have already received the update, but most will see it coming still. Everyone will have it before the end of April. If you receive that update and don't see an improvement in your issues here, please let me know and we can keep looking into things.
Hey Jeff, I'm in the same boat with a device that won't show. Device is fine and accessible across the network but simply doesn't appear. I'm wondering if the issue is the fact that it's not a physical device. I have a NAS running on a physical device, with an Emby instance running on a different IP address off of that server. The network can find the physical device, but unlike every other router I've ever dealt with you can't manually type an IP address in port forwarding. I can't be the only one with this issue. In the old Google Wi-Fi app I was able to type the address in and it worked perfectly...
I still have the issue of device not showing up in the list. With the recent app update, the previous port forwarding rules are lost, so I can’t create a new port forwarding rule until I find the device in the list and I am not able to write a custom rule or find the device to set a static Ip or create port forwarding. Frustrating, thinking of returning the the best Wi-Fi devices
Hello Jeff i have a issue.
Normally, I can configure the ports with the google home app following the steps that I have no failures with most devices. The problem is when I tried to open the ports of my raspberry pi 4 that was working for me for a few days, until one day the port was closed, unconfiguring itself, and now it does not appear in the list of devices to be able to reconfigure it. I have tried to change the IP, reinstall it, echo protocol (opening ports 7 and 9 of my raspi 4). But none of this has managed to solve it.
Can you help me?
I have the same issue, where my device has static ip but doesnt show up in the list, so I cant port forward to static ip. Just allow a way to write custom port forwarding rule to a specific/static ip address .
2 raspberry pi devices do not show up on list for choosing. Used to work fine with Google Wifi app but does not now that wifi was moved to Google home. Probably returning to my old Apple router
This is a problem with google wifi. The old google wifi app was way better. The google home app has turned an at home tech geeks wifi dream into an utter nightmare. Why doesnt it let me make a custom port forward with my own info? It never sees my IP cameras. It does ot see my desktop unless i fight with it. Ready to go with something thats more customizable after they took away my ability to do power user level stuff. Help google, stop breaking stuff that works!
In case it helps - I solved the issue for myself (and it was a bit ridiculous). Google Wifi simply doesn't play nice with anything assigned a static IP. Apparently this was my issue. I had to reset my server to connect via DHCP, then I had to login to the server and ping www.google.com. While it was pinging actively on the network, Google Wifi could pick up the device and I quickly set a reserved address and forwarding rules. Then I logged back into my device and changed from DHCP back to a new static IP (the address I was given while in DHCP). Some people had success pinging without setting to DHCP, but that didn't work for me.
Thanks for posting ― let's sort this out.
Give these steps a try:
It requires a device reboot(with a 2 minute off time because magical electricity keeps services in memory for an arbitrary length of time) for a device IP address to appear in a list.
This sounds like utter nonsense. It is not a viable way too manage port forwarding configuration.
I raised this issue 10 months ago and since then lots of people have expressed that they have exactly the same issue, but you want to close the ticket because you think you solved it by telling us to "try turning it off and on again"?
Not really the help I was looking for. What I hoped/expected was something like:
- we've looked at the the source code for the device and it seems that the ARP tables are only updated every 15 minutes. You'll need to wait for that long for any newly attached devices to appear.
- I've looked at the development backlog and manual setting of port forward rules is in teh list, but it is not expected to be added for another 6 months.
These kind of answers will require you to go and raise the issue with the product technical team. Maybe you could do that before tell us to "try turning it off and on again".
I look forward to hearing what the product developers suggest.
The issue is not resolved, as so many others have mentioned , we need ability to manually add static ip addressed to resolve this issue.
not sure why you are planning to lock the thread. There have been at least three other threads on the same issue that have been locked, without solving the issue .
We hear you and we apologize if this thread was closed sooner than you would have liked. As Community Specialists, we occasionally do a bit of housekeeping to keep the conversations in our community fresh and relevant. This includes locking threads after a period of inactivity.
@landoman1, thanks for sharing the step that helped resolve your issue.
Thanks for posting and sorry for the trouble. Let’s see what’s going on.
A few questions: what specific devices are you trying to port forward? Also, is there a specific reason why you need to port forward them? What do you see on the Google Home app when you try to add the static IP?
The devices are arduino programmed microcontrollers that serve a webpage when requested. One is an ESP32 and the other a WemosD1. One is used for home automation of a TV lift, and the other a weather station.
I want to port forward so that they can be accessed externally from the internet, rather than just at home on the local network. Accessing the devices while on the local network works fine.
When I go to the port forward settings in the Google Home app, many devices appear, but not these two which also have static IPs on the local network. If there was ability to enter an IP address manually, or the devices appeared in the list, I'd be able to add them to the port forwarding rules and thus connect to them from the other side of the router.
I was having this issue with a new Laptop on my network, I allowed the device to operate on the network for some time and it has been reset once or twice in that time and the device is now finally showing in my port forwarding options. I did change settings on my laptop to be discoverable on a private network. Not sure what but something worked. Now I have an open Nat.
I'm sorry to hear that you're still having an issue with your Nest WIfi. We'd like to take a deeper look into this — could you fill out this form and let us know once you're done?