topic Re: Google Wifi Pro Nat Loopback issue in Nest Wifi

Google Wifi Pro Nat Loopback issue

Fred190 — Sat, 10 Dec 2022 20:03:05 GMT

I have a Synology Nas on my network that I access from both inside and outside my Lan depending on where I am. I use a domain address (boxname.synology.xxx.me) with port forwarding set in my google pro router. When I am inside my Lan using Nat loopback (also called Nat hairpin) I can access the NAS using the DN address.

The Nas and one of my Access points are hardwired via a unmanaged switch into the Lan port of the router.

I have discovered if both my computer and the NAS is on the hardwired side of the router Nat loopback does not work. This includes using a wireless connection to the hardwired AP point. If either or both are connected to the main router via wireless Nat loopback works.

If I use the internal IP address rather than the domain name I can access it ok with both on the hardwired side.

Not sure if this is a feature or a bug?

Re: Google Wifi Pro Nat Loopback issue

olavrb — Sat, 10 Dec 2022 22:03:34 GMT

It doesn't seem NAT loopback ever worked flawlessly with Google Wifi or Nest Wifi either, but it seems it worked a bit better.

https://www.google.com/search?q=%28site%3Agooglenestcommunity.com%2Ft5%2FNest-Wifi+OR+site%3Areddit.com%2Fr%2Fgooglewifi+OR+site%3Areddit.com%2Fr%2Fnestwifi+OR+site%3Areddit.com%2Fr%2FOnHub%29+%28%22nat+loopback%22OR%22hairpin+nat%22%29+%28%22nest+wifi+pro%22%29

The port forwarding support article even has a little section about NAT loopback, so seems like a feature they intend Nest Wifi to have:

https://support.google.com/googlenest/answer/6274503?hl=en

I haven't seen any aknowledgement from Google, no commitment to do anything about it.

---

Use local IP while on LAN, host a DNS server like pi-hole and override DNS, or get a different Wi-Fi system.

Re: Google Wifi Pro Nat Loopback issue

e9d1n4 — Sun, 11 Dec 2022 17:28:00 GMT

Thanks for the suggestions (having a similar problem here). I've started running a local DNS and that works for most purposes, but most of my web browsers are set up to use DNS over HTTPS and so here it isn't as simple as changing DNS settings via DHCP. I have started a ticket with support but Google has gone silent. I'm hoping it gets fixed with the next firmware.

Re: Google Wifi Pro Nat Loopback issue

Fred190 — Tue, 13 Dec 2022 03:39:06 GMT

Update: I added another access point today in my garage using the home app as required. It first rebooted the router and all the access points and then it did a firmware update. I think it only updated the new access point but not positive. My router is running 1.63.324946 which was released in November and should have already been on the router. After all of this Nat Loopback no longer works at all. I did not physically change anything else beside adding the new access point. I also check to be sure my Wan IP address did not change.

Re: Google Wifi Pro Nat Loopback issue

AbigailF — Tue, 27 Dec 2022 20:57:42 GMT

Hey folks,

Thanks for lending a hand, @olavrb.
@e9d1n4, we'd like to check on your case. Could you provide the case ID number from your interaction with our Google support? We'll wait for your update.
@Fred190, are you still having the same issue? Let us know so we can continue to help out.

Best,
Abi

Re: Google Wifi Pro Nat Loopback issue

Fred190 — Tue, 27 Dec 2022 21:06:39 GMT

AbigailF, I returned my Nest pro and went back to my previous mesh routers. I was also having random speed and connection issues. The 6G backhaul did not agree with my home's geometry. I set up a wired backhaul but that would randomly switch back to wireless with poor speeds. Could easily been a wire quality issue but I was not going to rerun it due to where it was routed. Thanks for the offer of help.

Re: Google Wifi Pro Nat Loopback issue

e9d1n4 — Tue, 27 Dec 2022 21:17:53 GMT

Thank you @AbigailF . My case number is: 7-0483000033668

Re: Google Wifi Pro Nat Loopback issue

AbigailF — Tue, 27 Dec 2022 23:58:19 GMT

Hi everyone,

@Fred190, we're sad to see you go. If ever you change your mind, we're here to help

@e9d1n4, thanks for the details. I’ve sent a follow-up to the senior support handling your case. Keep your lines open as they will be replying to your email shortly. Let me know if you have any other questions or clarifications for now.

Thanks,

Abi

Re: Google Wifi Pro Nat Loopback issue

AbigailF — Sun, 01 Jan 2023 00:31:21 GMT

Hey folks,

We’d like to check in again in case you have any further questions or concerns. Feel free to reply to this thread and we’ll help you out.

Best,
Abi

Re: Google Wifi Pro Nat Loopback issue

Destynn — Sun, 01 Jan 2023 04:39:52 GMT

Can Google just fix the issue?

I have the same issue with Nat Loopback and accessing my server from inside the network. However, I've discovered that when I have only one Nest WiFi pro running and the second WiFi pro is unplugged, I can access my home server. To troubleshoot this, I plugged the second WiFi pro back in, checked if my phone was wirelessly connected to the main router(which is was), and I can access the server via Nat Loopback(as intended), however when I walked to the other side of the house and it wirelessly switches to the second WiFi pro, I am again not able to see the server. I am set up as wired backhaul to the main router. .... ONT -> GWiFiPro-> unman. Switch ->GWiFiPro .... Would really like a fix from Google. This worked on the last 2 versions Google WiFi and Nest WiFi. This being a pro (and yes this is anything but a pro version of WiFi available to consumers) it should at least support hairpining.

Re: Google Wifi Pro Nat Loopback issue

e9d1n4 — Sun, 01 Jan 2023 05:53:44 GMT

updating here ... Google support did follow up and we have tested a few additional things. So far nothing has worked. Did a factory reset and swapped the primary with one of the points. Same result. I also moved to a different subnet.

I've heard that, similar to @Destynn, it can work if running from a primary router ... this likely explains why I remember it working now and then (I think this suggests secondaries are the ones failing at hairpinning).

My system is configured as follows: AT&T fiber/modem --> AT&T router (bridged) --> WiFi Pro primary; WiFi Pro secondary 1 --> unmanaged switch --> devices hosting external services; WiFi Pro secondary 2 --> unmanaged switch --> various other devices. I imagine the routing might work properly if the service hosting devices were wired to the primary, but unfortunately that is in my kitchen. I'm currently on firmware version 1.63.327820.

Is this kind of configuration (hosting externally accessible services connected to a secondary; functional loopback from secondary) working for anyone?

Re: Google Wifi Pro Nat Loopback issue

Phiro — Mon, 02 Jan 2023 03:50:10 GMT

Has there been any update to this issue? I upgraded my home setup from the google wifi system to the next wifi pro a few days ago, and I am also having nat loopback/hairpin issues over wired connections (it works fine over wifi). The nest router and the two points are all on the same version firmware, 1.63.327820, which appears to be the latest released/ga firmware as of Jan 1st 2023.

Re: Google Wifi Pro Nat Loopback issue

p_x_g — Wed, 04 Jan 2023 20:00:41 GMT

I also wish for this NAT loopback to work and it does not.

Re: Google Wifi Pro Nat Loopback issue

dankots — Wed, 11 Jan 2023 15:24:58 GMT

Any news on this? I have the same configuration and the same issue.

Re: Google Wifi Pro Nat Loopback issue

e9d1n4 — Wed, 11 Jan 2023 16:55:58 GMT

They had me try a few things like factory resetting, using a different network (subnet) and swapping the primary for a secondary but I haven't heard anything again since. I've started running a pihole DNS now and it seems a good enough workaround (with the additional benefit of not seeing all the ads), but I haven't yet completed the workaround with DoH for my browsers. I'm hoping for a firmware fix for the WiFi Pro but don't know when to expect it. I do like the pihole effect though and will probably keep that even after the fix comes through for the router.

Re: Google Wifi Pro Nat Loopback issue

dankots — Wed, 11 Jan 2023 17:32:28 GMT

I've got a pihole already, but I don't think that's a solution for me. I've got a reverse proxy terminating an https, with a certificate for the public IP address. so just mapping the domain name to an internal address won't work, right?

Re: Google Wifi Pro Nat Loopback issue

e9d1n4 — Wed, 11 Jan 2023 18:32:13 GMT

That is similar to my setup - I map the domain name(s) to the internal address for the reverse proxy LAN address rather than to the hosted service directly. The proxy (nginx in my case) doesn't care that the request came from the LAN and provides the expected certificate as it would for a WAN connection.

Re: Google Wifi Pro Nat Loopback issue

dankots — Thu, 12 Jan 2023 00:34:33 GMT

OMG it works! thank you soooo much.

Re: Google Wifi Pro Nat Loopback issue

Jhonleanmel — Thu, 12 Jan 2023 18:58:57 GMT

Hi everyone,

dankots, awesome — glad to hear that your issue is fixed.

To all, I suggest trying what e9d1n4 suggested.

Keep us posted.

Best,

Mel

Re: Google Wifi Pro Nat Loopback issue

dankots — Thu, 12 Jan 2023 19:05:16 GMT

This is NOT a valid solution to Google Wifi not working. Not everyone can spin up their own DNS. 😛

Google still needs to fix NAT loopback!