After Factory reset port forward don't work.

[RaymondDay61]

I had port forwarding working for years on my Google Wi-Fi.

But then got a Verizon Internet Gateway and plug the Ethernet to the Google Wi-Fi I could not get the port forward to work so switch back and the 4 Google Wi-Fi's were all off line. I had to make a new home name and reset them to Factory default.

Now port forward don't work but what is good one of the Google Wi-Fi's is staying up now. Before every 2 or 3 days it was off line and had to unplug the power and back in and then on line for 2 or 3 days again. That is fix now after a Factory reset and then had to set it all up again. This time used another Wi-Fi name. So had to get all the Wi-Fi things back on line with the new name took weeks.

So I put my server to static IP 192.168.86.109 and the DHCP server in Google Wi-Fi up to 192.168.86.108 and I could not pick it to do port forward then. I had to reboot my server and it seen it for a little while so I cold pick it to port forward it.

But now it don't see it's IP just it's name and mac address in the port forward on the cell phone.

If I do a nmap to see all the open ports on my WAN it don't see it. I am trying to open port 443 the https port. So I go and open port 80 to another LAN server and then nmap will see both them on Google Wi-Fi.

Here is the nmap with my IP removed. The 1st one did not add port 80 the 2nd nmap I did and then it shows the 443 port too but filtered not open!

One time on a Google Wi-Fi reboot I had my IP on my Google chrome and my server home page came up for a little till google Wi-Fi came back up then blocked it again.

Don't get why this is not working now.

Home some one can help. I did a 3 times not help on the Google Wi-Fi app to Google with screen show and stuff on my cellphone but they don't get back with you.

So trying on this Google community now.

-Raymond Day

[RaymondDay61]

I set my server back to DHCP so Google Wi-Fi can pick it from the list and I put it in "IP reservations" Now in Port Management it sees it good but still the port 443 is filtered not open!

[RaymondDay61]

I put a tp-link router ER605 between my Google Wi-Fi and cable modem. Plug my server in the DR605 port 1 and open port 443 to it. It was getting the same Filtered not open. I got on my server and apache was not running. So I started it and then the port went open.

So I removed that router between them and put the cable modem right on the Google WiFi again.

It sees my server so I open port 80 all so.

I can go to it's LAN IP with http and https but Google Wi-Fi still says Filtered for both ports 80 and 443 http and https.

I rebooted them all too the Google Wi-Fi, the cable modem and my server.

Still filtered.

It looks like this:

Not shown: 996 closed ports
PORT STATE SERVICE
80/tcp filtered http
443/tcp filtered https
8080/tcp open http-proxy
8081/tcp open blackice-icecap

Is there some setting that will put them to open and not filtered?

-Raymond Day

[RaymondDay61 · Accepted solution]

I ended up putting a tp-link router ER605 between the Google Wi-Fi and cable modem. Then plug the ethernet to my server in that router. With a PC in one of the 5 Ethernet ports of that router plug in a laptop and the open port worked then after some setting to open it.

Not shown: 997 closed ports
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
1723/tcp open pptp

Got Wi-Fi on my server to my LAN or Google Wi-Fi so I can still get to it on my LAN now. It has 2 IP's now. One for WAN and one for LAN. The Ethernet is the WAN one.

Hope Google can fix this junk have to do this to get it to work.

-Raymond Day

[EdwardT]

Hi RaymondDay61,

Thanks for posting. I'm sorry that you had an issue with port forwarding. Thanks for sharing all the steps that you tried to get it to work. We appreciate people who are keen on sharing with us their thoughts.  We're always looking for ways to improve and we'll take this as feedback. Let us know if you have any questions — we'd be happy to help.

Thanks,

Edward

[RaymondDay61]

I typed to soon about the tp-link router ER605 it did not work for port forward after about a day. I guess when it renewed the IP's.

Worked on it a lot and could not get port forward to work.

It was easy with Google Wi-Fi or get hub hard to know what they name it now.

So I went out to BestBuy and bought another one. One of the small ones.

Set it up between my main Google Wi-Fi and cable modem and it worked. The port forward just works.

Guess it did not work on the old system because it's a true mesh system now. Before when I started just had one and then added them later and the port forward I could add and take away and all ways worked.

Only one problem I think it was the last one I put up would not stay up for maybe 2 days. It would go off line and I would have to unplug in and back in then it get back on line. I even put a smart switch on it's power.

But now it's staying up like the rest.

The new one I did not set it up as a mesh but on it's own. The port forward has been working for about 3 days now.

But if it don't work on a mesh system why not gray it out so can not pick it? Maybe because it works if you start as a none mesh with one and add ones later but then the port forward still work when you add them as a mesh system later.

I don't get why it can do port forward when it's a mess system any way. Some one just don't know how to program it or is it a hardware limit?

-Raymond Day