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.

Google Wifi Port forward static IP

hons
Community Member

Hi,

In my network I have 3 Google Wifi meshed devices. Those are connected through a wired unmanaged switch.

Now I have a device in my network that has a static IP set in its configuration to 192.168.86.200 (Not in my DHCP range which is from 192.168.86.20-199). I can ping it on the network, but I can't see it in the App so I'm unable to forward a specific port to that device.

Is there a possibility to add a Port forwarding rule without "seeing" the device as such in the app?

9 REPLIES 9

olavrb
Platinum Product Expert
Platinum Product Expert

How have you wired it all up, like this?

olavrb_0-1678119429552.png

You need to be able to see the device in the Google Home app in order to add port forwarding rules.

Worst case, try to factory reset Nest Wifi and set up from scratch. Reuse existing network name (SSID) and password, then devices should automagically reconnect. Not ideal, but can fix issues like you are facing.


I don't work for Google.

hons
Community Member

I see all the other devices in my network. Unfortunately this devices IP cannot be set by the DHCP, but it is required to have a static IP. So I set that static IP to something that is within the range of my subnet mask.
Router 192.168.86.1
DHCP Range 192.168.86.199
Subnet Mask 255.255.255.0
An that device in question 192.168.86.200

I can even ping it, but Google Home does not see it

 

olavrb
Platinum Product Expert
Platinum Product Expert

I too have devices outside the DHCP scope, but I set a DHCP reservation before adding a port forwarding rule, maybe that's what you should do.

I have 192.168.86.10-255 as DHCP pool, set my NAS to 192.168.86.5 using DHCP reservation, then added a port forwarding rule to it.


I don't work for Google.

hons
Community Member

The problem is, that my devices IP is not set by the DHCP, but set statically on the device, so it is not shown in the home app for (i guess) that reason.
I don't see a solution as long as it is not possible to set a port forwarding rule for (arbitrary) IP adresses from the Home app

olavrb
Platinum Product Expert
Platinum Product Expert

I have no further recommendations to provide.

Summarized: Make sure it's all wired up like the diagram in my first reply shows. And try to do a DHCP reservation from the Google Home app.


I don't work for Google.

hons
Community Member

Fortunately I do have a device in my network that already has a nginx running. So I forward all the interesting traffic to that device which is seen in the Home app and from there then to my static device. Here in more detail

AbigailF
Community Specialist
Community Specialist

Hey folks, 

Thanks for lending a hand, @olavrb.
@hons, I wanted to follow up and see if you are still in need of any help. Please let me know if you are still having any concerns or questions from here, as I would be happy to take a closer look and assist you further.

Thanks,
Abi

hons
Community Member

Hi Abi,

I answered already on the other thread that I was participating to find a solution to this problem. Currently as said I'm using an auxiliary device like a raspberry in the network to forward traffic to devices that I don't see on the google home app. It should be possible for a routing system to setup port forwarding rules as needed... However, I send a feedback to Google as u suggested. Next time I need to buy such devices I'll do more research on my needs and buy something (else) according t what I need 🙂

AbigailF
Community Specialist
Community Specialist

Hello hons,


Thanks again for sending in your feedback. If you have a new question, you can always reach out to us by creating a new thread. I’ll be closing this thread in 24 hours.


Best,
Abi