Google WiFi port forwarding woes

[tech_fatigue]

I can't create a functional port forwarding rule on my network. I've read countless support threads concerning port forwarding on G wifi and nothing works.

• Confirmed bridge mode on the modem/router - no double NAT situation
• Verified port forwarding permissions with my ISP.
• Tested all three Google Wifi points that came in the pack as the main router.
• Disabled mesh network functionality.
• Reserved DHCP addresses for client devices on which I tested port forwarding.
• Attempted port forwarding to various devices (Macbook, NAS, Windows laptop, Android).
• Experiment with TCP, UDP, and both protocols.
• Tried single port and port range forwarding.
• Toggled IPv6 settings as suggested in some forums.
• Ensured MAC randomization is disabled on all client devices.
• Performed at least 5 whole network factory resets.

I create the rule, hit save, test the rule using various port checker tools online - it's always closed.

Anything I'm missing ?

Many thanks

[ByronP · Accepted solution]

Hi tech_fatigue,

Thank you for posting in the community. I'm sorry that you're unable to create a port forwarding rule for your Google Wi-Fi Points. I understand how frustrating this can be. I really appreciate all the steps you've tried to troubleshoot the situation. Let's work together to find a solution.

Before I begin, I need to ask a few questions for further assistance:

• Have you verified the port numbers you used from your Internet Service Provider (ISP) or router manufacturer?
• Do you have any upstream routers not in bridge mode?
• Are you able to access your service locally?
• What device are you trying to do port forwarding with?
• Is the device you're trying to port forward connected to a guest network?
• If yes, port forwarding isn't available for users that connect to the guest network.

Please keep me posted. I look forward to your response.

Regards,

Byron

[tech_fatigue]

Hi Byron, thanks for taking the time to chip in 🙂 

• Have you verified the port numbers you used from your Internet Service Provider (ISP) or router manufacturer?
  • I've tried with "normal" ports (21, 23, 110 etc), and "eccentric ports" (5500, 40505, random)
• Do you have any upstream routers not in bridge mode?
  • No, the only thing I have upstream is the ISP's modem/router, set to bridge mode
• Are you able to access your service locally?
  • Yes
• What device are you trying to do port forwarding with?
  • A NAS, I also tried on another server and tested with my macbook
• Is the device you're trying to port forward connected to a guest network?
  • No, I don't have a guest network. The NAS is hardwired to the unmanaged switch. Other devices are all on the main network
• If yes, port forwarding isn't available for users that connect to the guest network.

Thanks !

[ByronP]

Hi tech_fatigue,

Thank you for your response.

Based on your answers, do the following:

• Please confirm if there were any major outages that recently happened in the area. Outages may cause some lines to disrupt.
• Try to reboot the Google WiFi device. Depending on the model, here are the steps to restart Nest Wifi or Google Wifi devices.

Also, another suggestion is to perform a 2-minute power cycle. Please do the following:

1. Disconnect the modem from its power source.
2. Unplug the Ethernet cable and power cord from the parent point.
3. Remove the power cord from the child point.
4. Leave everything unplugged for 2 minutes.
   • Start a timer to track.
   • Check the make and model of the modem, and make sure there isn't a backup battery. If there’s a backup battery, ask the customer to remove the battery; otherwise, it won't perform a power cycle.
5. Connect the power cable to the modem and allow the modem to fully turn on before proceeding.This process can take up to a minute.
   • All light indicators should be solid colors.
   • Connect the Ethernet cable, then the power cable, to the parent point. Wait until the modem is fully back online.
6. Connect the power cable to the child point(s).

Let me know how it goes and keep me posted.

Regards,

Byron

[tech_fatigue]

Hi Byron, 

There hasn't been any outage in the area. I've been trying to setup port forwarding for more than a year now with no success. 

I just tried another 2 min power cycle and get the same results - still can't forward ports.

Thank you

[ByronP]

Hi tech_fatigue,

Thank you for your response.

Please do the following:

Check if the upstream router isn't in bridge mode.

This can be checked by viewing the WAN IP of the Google WiFi that is connected to the upstream router. If it starts with either 10.0.X.X, 172.16.X.X, or 192.168.x.x, then it's a private IP address. It indicates an upstream router that isn't in bridge mode since it assigned a private IP.

If so, the upstream router’s firewall is more than likely to block the port forwarding rules set by the Google WiFi. If this is the case, you can try the following three solutions:

• Connect the Google WiFi that is connected to the upstream router to a Demilitarized Zone (DMZ) created by the upstream router.
• Set a reserved IP for the Google WiFi that is connected to the upstream router, and forward the ports that need to be opened to the IP of the parent device in the upstream router.
• Set the upstream modem a router combo to bridge mode. If a standalone router, we can remove it from the topology of the network.
• Each router is different; please check the make and model of the router and do a Google search to find a manual with instructions.

If you aren't comfortable performing this, you can reach out to your ISP, who typically can perform this over the phone.

Note: If the service runs on a Windows computer, you may need to open the ports in the Windows firewall or Windows Defenders as well.

Let me know how it goes and keep me posted.

Regards,

Byron

[tech_fatigue]

Hi Byron, 

My google wifi WAN ip is not an local address. The upstream router is already in bridge mode. 

Thank you

[ByronP]

Hi tech_fatigue,

Thank you for your response and the detailed picture.

Based on your information provided, please do the following:

Please confirm if you're able to access the service locally.

If so, then there may be an upstream router that blocks the packets or the service isn’t configured properly for external connections.

• You can ping or navigate to: <LAN IP>:port.
• As an example, you can use the LAN IP address of 192.168.86.102 with the forwarded port 4500. 
  • Ex: 192.168.86.102:4500

Note: In most cases, if the device can't be reached on a given port locally, the device itself needs to be configured to accept connections on that port. However, some devices (example: Xbox) do not respond to HTTP or ping requests.

• If you try to navigate to a local service using a web address instead of the LAN IP, then this is unsupported as it uses internal DNS.

Let me know how it goes and keep me posted.

Regards,

Byron

[tech_fatigue]

Hi Byron, 

I can access the server locally on the configured port : 5050.

[ByronP]

Hi tech_fatigue,

Thank you for your response. I really appreciate the effort and detailed information related to this concern. Let's find together a solution.

Based on the information provided. The team would like to learn more about this behavior. When you get a chance, please fill out this form and let us know when you’re finished. We’ll have someone reach out to you via email from there.

Let me know if you have any further questions.

Regards,

Byron

[mrayner09]

Were you able to resolve this? I'm having a similar issue.

[tech_fatigue]

Yeah I was, and this is very shameful but this was a user error. I'm the user. I made the error. I thought you could just open a port in your router and test it from a website (portchecker.co) and it would work, but there needs to be a service on the host that uses this port. I'm a fool. 

[mrayner09]

That makes two of us. I was doing the same exact thing. Got it figured out now. Thanks.

[ByronP]

Hi tech_fatigue,

Thank you for your response. I'm glad that it was resolved.

If you still need assistance, don't hesitate to reach out to the community.

Regards,

Byron