Google Nest Wifi Router unable to acquire IPv6 - How to set up prefix delegation?

[Yoms]

Hi,

I have 1 Google Nest Wifi Router + 2 access points. The mesh network has been configured and is working OK in IPv4. But I need to use IPv6 because an application depends on it (OQEE app by French ISP "Free").

The issue I face is that my Google Nest Wifi Router is unable to acquire an IPv6 prefix.

• The Nest router is connected to my ISP's router via RJ45/Ethernet
• My ISP's router (Freebox Mini) runs in "Bridge" mode, so it's basically just a modem now
• My ISP's router allows enabling/disabling DHCPv6 (I tried both)
• The IPv6 option is enabled in my Google Home app's advanced settings
• This issue is related to my local network, not the guest's

I’ve read that Google WiFi needs to get an IPv6 prefix delegation from my ISP's router. Is that something I have to configure manually? Or is it something that should have been done automatically?

In my ISP's router (Freebox Mini) configuration page, I can:

• Enable/Disable the IPv6 firewall
• Enable/Disable DHCPv6  (as mentioned above)
• Force the use of DNS IPv6 servers
• Configure IPv6 prefix delegation (a prefix is displayed and below I can configure a Next Hop so that the Nest Wifi Router manages this subnet - If I understood correctly)

Could you please walk me through this so that I may configure the IPv6 prefix delegation and get IPv6 working properly on my network?

Thanks.

Kind regards,

[guibua]

Exact same situation here.

Would love to have a solution...

[Yoms]

What I've tried so far is to obtain the Google Nest's WAN IPv6 from the list of the devices connected to my ISP's router, and then fill its value into a "Next Hop" field. It's not working. I repeated the operation with DHCPv6 disabled. Still not working.

[guibua]

Did exactly the same. 
The Google router does not seem to get  an ipv6 address from Free (I tried bridge mode and double NAT). 
One strange thing is that it looks like some devices are attributed ipv6 addresses by the Google WiFi (when I look at the info on some devices in the Google Home app) but they do not show it when in the device itself (typically my iPhone) I look at the network info…
I am also trying to get OQEE to work on my Apple TVs. 

[Yoms]

Let's wait for someone from Google Nest support team to hop in and try to answer us.

[captainemre16]

Bu

[LucaGabrielli]

Ciao,

Google Nest has always has severe issues with IPv6. we tried to make it work at my university in our lab to no avail. We had speciallst network engineers looking into it and they couldn't find a solution.

I also have one at home and never got it to work (my ISP, LENFIBER, Italy, says Ipv6 is functional but that my Nest is rejecting it. LENFIBER claims that all customers with google nest who complain about Ipv6 have this problem).

You can find on google support many complaint about it, from different ISPs (BT, comcast, UPC...) , but strangely, google delete them. see some examples here where the search engine finds the thread but when you click on them, google says they are deleted. Are they trying to hide something?

You can still find them in the search engine, but when you click on the post, google says it's deleted:

https://support.google.com/googlenest/search?q=Nest+Ipv6

LG

PS,  I wonder how long yoms's thread will last before Google will delete it!

#Nest #IPv6

[Yoms]

Can someone from Google please share a solution?

Thanks.

[Yoms]

Anyone, Google?

[Yoms]

Great customer support Google ☹️

[Yoms]

What a poor support...

[Jeff]

Hey, Yoms.
Sorry for the late response here, but I wanted to check in to see if you were still having this issue and to see if you have done any additional troubleshooting so far. If you still need help, let me know and I'll be happy to work on this with you.
Thanks.

[Jeff]

Hi, guys.

I know Yoms didn't chime back in yet, and that's ok. I can see that's definitely an issue that is affecting a good number of users. There are other threads out there as well where we're tracking the same issue and feeding back info to our internal teams. I really do hope to hear of a fix soon and I will keep you all updated as I know more.

Thanks.

[guibua]

Many thanks for the heads up.

Eagerly waiting for the fix!

[Jeff]

Hey, everyone.

We have a lot of new reports that I'm noticing and I'm still keeping an eye on things. Unfortunately I still don't have news of when a fix might be ready, but I'm hoping to hear something sooner than later. I know this is frustrating for all of you. I'll share when I know more.

Thanks.

[Kurt2]

Is this true? after a lot of help and testing, we have found that Google Wifi will not work as a sub-router handing out ipv6 addresses to client machines.

this was also confirmed by Google who stated it was not supported and only way for ipv6 to work was by having the GW as the main router and not installed as sub-router.

While being used as a sub-router with GW wan set to dhcp, GW will not pick up the addressing and prefix properly and thus not allow ipv6 to work.

[thargy]

Exact same issue on Google Wifi Pro, 1 year later...

[guibua]

I will let Yoms answer.

As for me, the problem is still there...

[LucaGabrielli]

Hi Guiba,

Can you write the answer to everybody?

[guibua]

I guess it is a misunderstanding : I have no solution and I am still not able to get ipv6 through my Google Nest/Wifi...

[iccrew98]

It doesn't work on Nest Wifi. I set up another network for my office on IPv6 and it works flawlessly.  For being a leading edge tech company, their devices seem way behind. 

[pdp11]

Am another user in the same boat. Connect a laptop with Ethernet straight to my provider's cable modem (Shaw in Canada). Instantly receive both IPv4 and IPv6 addresses (both on Windows 10 and MacOS). Test-ipv6.com confirms IPv6 functioning on the Shaw network.

Then connect with the same Ethernet to my Google Nest WiFi LAN port (with IPv6 turned on). No IPv6 address provided (tested both on Windows 10 and MacOS). Same result with a WiFi connection.

Clearly IPv6 broken on Google Nest. Shame for a company that seems dedicated to the deployment of IPv6.

[nop]

Same here. Waiting for a fix.

[natman]

Only way for now is, run Google WiFi as bridged mode(Under Device Mode -> Bridge mode).  In this way, ISP model/router will handle the DHCP and  routing.

[MikeDoent]

I got the exact same problem no ipv6. My ISP is a freebox mini 4K in router mode and under it i got a nest wifi with a bridge...

[MikeDoent]

I tried to put my ISP router on bridge mode so the nest wifi is the only one in charge and on my Android tv I got both ipv4 and IPv6 but it seems that the box only use the ipv4 so I got an error IPv6 needed on the Oqee app.

I turned off ipv6 on my two Nvidia shields and it worked for one of them.

If I turn off ipv6 the box used the IPv6 .... That's weird.

Does anyone from Google able to send us an ETA of the fix of our bug.  I saw on the web that another nest wifi was on the work. It will be cool to fix our error first no ?

[Blackspear]

1 year later and it's still amateur hour with Google Nest Wifi unable to be used with IPv6; that's shockingly bad support for such a large company.

[MikeDoent]

For me when I launch the nest hub I got for a few seconds IPv6 adress on multiple devices.

But when I wait ipv4 replaces all adresses

[guibua]

Guys!

I had given up any hope this would work some day…

I checked by pure chance tonight and I have IPV6 up and running now!

I did not do anything, I guess there had been a firmware update (I could not find any notification of the latest update in the Google Home app though… for information, my devices are running software version 14250.43.81) or an update on my internet provider side (Free in France)…

So check your network, you might have a nice surprise. 

[Blackspear]

You wrote software version 14250.43.81

Did you mean 14150.43.81?  As this is what I am on, and the issue remains.

[guibua]

Yes 14150.43.81 sorry for the typo.
(I am running double NAT and I remember following some internet instruction to set up properly some "next hop" on the ISP router)

[guibua]

ah... it looks like the situation is a little bit more complicated :

 - https://test-ipv6.com shows 0/10  on my iPhone and my Mac, I have 10/10 on my iPad

- https://ipv6test.google.com says "No problem detected" but that "You don’t have IPv6, but you shouldn’t have problems on websites that add IPv6 support." on both my Mac and my iPhone. It says "Yes, looks like you're using IPv6 already." on my iPad.

 - the application that required IPv6 to run (Oqee) is working fine on both AppleTVs

All of those are on the same (mesh) network. All my Google Wifi devices are running the same software. On my iPad, I cannot access IPv6 details (same on AppleTVs) : it definitely looks like everything is still not yet completely fine...

[sombrabr]

Here I am still having the problem, unfortunately 😞

[Avvakun]

Same problem from Argentina, Telecom ISP. 😞 Come on Google.!!!!

[captainemre16]

#

[MikeDoent]

Hi, I still don't have IPv6 working on the nest wifi.

I found that for a few minutes my Android tv show me a IPv6 and the app I wanna use (oqee) work.

And then suddenly I got a new ipv4 adress and everything stop working..... Any fix ???

[Shorkly]

Still NO IPv6 with upgrade 14150.376.32. 

Nest behind a freebox 4k. 

Please, is there a next update planed ? 

[SFPK]

+1 and shame on Google for sort of misleading users that the WiFi devices support IPv6 and sending so many people down a long search (and making no mention of this on the main/official IPv6 support pages + misleading label in the Google Home app with "Enable or disable IPv6" that only and mostly pointlessly enables it for the internal network).

PS: If you don't want to have your ISP modem do the routing, you can use a Tunnel Broker like https://route48.org/ or https://tunnelbroker.net/  on the device that needs IPv6 (note: this requires ICMP on your external IPv4.

Keywords: ISP supported IPv6 WAN DHCP not working on Google Nest WiFi

Update 20221017: Google One Support (name: Jikky) says:

1. Please explain the problem again.
2. I am looking into it.
3. My manual says: "For IPv6 to work on your network, all of these must be true: ISP should support IPv6, the device that you are using should support IPv6 and the OS\application running on that device should support IPv6."
4. Please reboot your network + more I am looking into it.
5. Your internal network is now using IPv6. [Yes, it was before I contacted you, but WAN is still not.]
6. Will escalate this to a Senior Specialist (ticket 6-28950000*****) and get back to you.

Update 20221019: Google Senior Specialists are saying "that something is wrong with your IPv6 settings on your Google Nest Wifi router. Currently, the connection is not confirmed, that is why none of your devices are getting IPv6 addresses. To fix this, they suggest that you factory reset the network and set it up again."

I've done that. LAN gets an IPv6 address and DUID via DHCPv6 from the Nest Router (and even some IPv6 DNS servers), but http://www.test-ipv6.com/ still says ZERO.

Update 20221024: sorry, your device is faulty, but is outside of warranty.

Update 20221031: I've not accepted that solution, but it remains quiet on the Google Support side.

Trust me, this is not a hardware problem, so my advice (for now) is still to: sell your Google devices (to some unexpecting person that will not need IPv6 for another 10 years) and buy Ubiquity.

PS: See also: https://Pallieter.org/www8/2023/02/06/google-drive-sqlite-reference/

[MikeDoent]

Thats weird the nest wifi add both ipv4 and ipv6 adresses to my android devices and it seems the problem came from here, for a day i was having the oqee app working on ipv6. 

For now the promblem came back still no ipv6 available (and i haven't touch anything between these days).

The nest wifi pro is for sure having the same issue better stop buying nest device i guess ...... 

Is any google tech reading us ? 

[JMi1]

Has same problem with the whole new Nest Wifi Pro...

Ipv6 enabled but doesnt work, despite dhcpv6PD on isp's router. Quite a shame !