FTTP doesn't use any VLAN settings. Why are you trying to put a managed switch between the ONT and your router? Which FTTP package are you on? If you are on the top 900 package then the cpu in the Nest Wifi router is probably not fast enough to process the PPPoE packets.
This is recommended by NEST. https://support.google.com/googlenest/answer/9798157?hl=en-GB
I am only on the 150mbps but can't get higher than 20 on the Nest directly plugged into the ONT router. IPV6 doest
Tried different cables too.
BT doesn't use VLAN tagging for FTTP so the article is not relevant here. Try a factory reset on your router and try setting up again.
Yes, it was and nothing I could do about it. I replaced the Google hub with a Unifi Dream machine pro and it's all working!
Like another poster, I sporadically get IPv6 after the latest firmware update.
The connection drops 1-3 times a day though... and with it goes the IPv6 allocation.
I know this is an old post I'm bumping but it is a top result on a Google search for "next WiFi vlan tagging". It is the very top result of you add the word OpenReach.
The thread has been linked to another thread elsewhere regarding the Nest WiFi working with OpenReach FTTP.
The user is convinced the ONT doesn't add VLAN tagging because it's mentioned twice in this thread.
Nest are correct.
The OpenReach ONT absolutely does add VLAN tagging.
It works just the same as the VLAN 101 tag added by a modem on OpenReach FTTC.
ONTs won't work on OpenReach FTTP without the VLAN tagging.
They are always provided to the customer locked and preconfigured so I'm curious why the user above was so convinced there was no tagging used.
Edit: to clarify, the ONTs vlan tagging likely has nothing to do with the Nest WiFi not working.