Configuration with Google wifi

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Configuration with Google wifi

1 | 2 | 3 | 4 | 5

ald

172 posts

Master Geek

Trusted

SimWorks

#2902299 14-Apr-2022 11:52

Hi team, I'll shortly need to move off my trusty VDSL connection at home as Chorus are decommissioning the copper in my street. I have a Nest Wifi on the latest firmware (plugged in to my current DSL router) and didn't think I would be able to connect it to fibre directly because of the VLAN tagging issue. However, this thread has been great, and it appears that giving it a go may be worth it. I'm keen to go with Contact Energy's fibre, just because I already get gas and electricity through them and they offer a really good deal to existing customers that also pick up their fibre offering. However, I can't find any reference in any post (forgive me if I've overlooked something) of anyone trying to use the Nest Wifi with Contact's fibre. Contact state specifically in their service information that support for VLAN tagging is a requirement for devices connecting to their service.

Has anyone tried connecting Nest Wifi to Contacts fibre service or does anyone with better knowledge of how things work on the other side of the ONT have any reason to believe that it would or would not be successful?

As always, thanks for your help!

Delorean

651 posts

Ultimate Geek

ID Verified

Trusted

Lifetime subscriber

#2902411 14-Apr-2022 15:14

ald:

Hi team, I'll shortly need to move off my trusty VDSL connection at home as Chorus are decommissioning the copper in my street. I have a Nest Wifi on the latest firmware (plugged in to my current DSL router) and didn't think I would be able to connect it to fibre directly because of the VLAN tagging issue. However, this thread has been great, and it appears that giving it a go may be worth it. I'm keen to go with Contact Energy's fibre, just because I already get gas and electricity through them and they offer a really good deal to existing customers that also pick up their fibre offering. However, I can't find any reference in any post (forgive me if I've overlooked something) of anyone trying to use the Nest Wifi with Contact's fibre. Contact state specifically in their service information that support for VLAN tagging is a requirement for devices connecting to their service.

Has anyone tried connecting Nest Wifi to Contacts fibre service or does anyone with better knowledge of how things work on the other side of the ONT have any reason to believe that it would or would not be successful?

As always, thanks for your help!

Who is your current ISP. Google Nest WiFi works with VLAN tagging, you need to enable it though the app.

I think the Google Product will work best with an IPoE provider, (Vocus, Vodafone, Sky etc) Whereas Contact is a PPPoE provider.

With that said, 2degress and voyager get good reviews on the forum, however it is recommended you use their router / mesh setup

Referral Link: | Quic Broadband (use R142206E0L2CR for free setup)

ald

172 posts

Master Geek

Trusted

SimWorks

#2902433 14-Apr-2022 15:50

Orcon is my current ISP, but I'm not planning on sticking with them. I don't mind using an ISP supplied router if it comes to it, but it would be tidier if I could just do away with it altogether and just use the Nest Wifi. Very interested in hearing from anyone that has attempted to use their Nest Wifi with Contact's fibre service.

danielsiva

21 posts

Geek

Trusted

#2903468 18-Apr-2022 12:28

Posting an update here for general information to others in the future:

Spark UFB (Chorus ONT) > Google Wifi (generation 1/older version device, not the new Curvy nest device) is working for me.

Running version 14150.43.80 (I believe having at least this version is important).
Factory reset the Google Wifi, plug in network cable from the ONT into the WAN port on the Google Wifi. Start the setup process & it will transparently try VLAN 10 (it does not give feedback that it is trying). It will fail & offer option to select DHCP/Static/PPPoE. Select PPPoE & input details provided by spark:

https://www.spark.co.nz/help/internet/set-up/non-spark-modem/

PPP username: user@spark.co.nz
PPP password: password

I was using an android phone with the Google Home app for this entire process.

This succeeded for me.

Model: AC-1304

porboy

5 posts

Wannabe Geek

#2903472 18-Apr-2022 13:10

My Google Wifi has updated to the same 14150.43.80 firmware and has been running reliable on Spark/Chorus for the past 10 months. It worked on earlier firmware 13728.57.15 as well. Recently we have had several planned and unplanned power outages and the connection re-established every time so I now have the confidence to on-sell the Linksys router I had originally to do the VLAN tagging. So strange that there has been no mention of this functionality being added after so much feedback being given that it was needed. No more double NAT and one less device consuming power. Happy.

ald

172 posts

Master Geek

Trusted

SimWorks

#2923222 6-Jun-2022 12:33

A quick update: Nest Wifi works fine on Contact's internet service.

Switched from Orcon VDSL to Contact fibre a couple of weeks. Initially used supplied modem just to be sure that the connection etc were fine. This weekend, with family away so no dramas if there were problems, I moved to using the Nest Wifi as the router. Much simpler than anticipated. Unplugged everything except power from the Nest. Did factory reset through the Google Home app, and waited probably around 10 mins for the slow orange flashing light to become a slowly flashing white light. Via Google Home app, I added the Nest Wifi to my account, followed the instructions, it complained that there did not appear to be an ethernet cable attached (which there wasn't, just power), so I plugged in the connection from the ONT, proceeded through the setup, no tricky questions, it just worked. Testing various devices around the home, wired and wireless, everything is just working and connection seems fine. Some needed a restart, probably just to get a new DHCP lease.

Prior to doing the setup, I did a quick check of the Google instructions for setting up the Nest Wifi, where I found a whole page specifically confirming that Nest Wifi is compatible with VLAN tagging (a link from the set up instructions, sorry, I didn't grab the link).

So it appears that you can likely just use your Nest Wifi with any NZ ISP that uses VLAN tagging (if they use one of the 3 tags that Google supports, 3, 7 and 10 I think they said on the page, with all others also supported, but just requiring an extra step or two).

I hope this is of help to anyone wanting to simplify their setup and use the Nest Wifi with NZ ISPs.

MBIL

4 posts

Wannabe Geek

#2934345 25-Jun-2022 19:45

I’ve just purchased a Google Nest Wifi (router and 2 access points) and I’m struggling to get it to connect to the internet when connected directly to the ONT.

I’ve been through the set up multiple times and tried the troubleshooting steps in the Google Home app e.g. powering off modem, router etc with no luck. It won’t connect to the internet.

If I connect the Nest router to the Vodafone Ultra Hub then it connects fine but I get double NAT and as far as I can work out you can’t put the Ultra Hub into bridge mode.

ISP: Vodafone NZ

Model: H2D
Software version: 14150.43.81

Any tips on getting the Nest router to connect to the internet directly?

Not sure if this changes anything but I bought the Nest Wifi in America as I was just there last week.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

ald

172 posts

Master Geek

Trusted

SimWorks

#2934553 26-Jun-2022 10:44

Hi MBIL, sorry to hear you've run into a few problems. This is the opposite of what you want to hear, but things went pretty smoothly for me, so there weren't really any issues I had to sort out. So there's nothing that I can specifically point to that was crucial etc. The one thing that does appear to be universal is that you need to start with a router that has either never been used or reset. In my case, I'd been using it connected to my old router, and so it had already been set up. About the trickiest thing I had to figure out, which wasn't that tricky, was how to get the thing to reset itself, forcing it to go through the whole set up process, including presumably getting itself sorted out for handling vlan tagged connections. So you'll definitely want to ensure that it has been reset between each attempt, and if it matters, with no cables other than the power cable attached.

Sorry I haven't got more to offer! Just goes to show, you really only learn stuff when things go wrong!

cyril7

9058 posts

Uber Geek

ID Verified

Trusted

Subscriber

#2934616 26-Jun-2022 14:29

Hi, I believe it was only the AU/NZ supplied models that got a firmware that supported vlan's on the WAN interface, so its possible your out of luck, other option is to purchase a cheap managed switch to drop the vlan for you.

Cyril

MBIL

4 posts

Wannabe Geek

#2934727 26-Jun-2022 21:15

Thanks for the quick replies, appreciate it.

Is there any way to confirm it is only the AU/NZ model that has the VLAN tagging? I've done some Googling but have not found anything definitive.

I'll go down the managed switch route if the US model doesn't have it.

danielsiva

21 posts

Geek

Trusted

#2934733 26-Jun-2022 21:53

Thinking out loud..

If i wanted to confirm it was trying a vlan tag, I would setup wireshark on a computer & plug in the network link from the monitored interface into the Google Nest WAN port, then watch for any vlan tagged traffic coming from it during the setup wizard process.

MBIL

4 posts

Wannabe Geek

#2947149 27-Jul-2022 23:52

I had a bit of time tonight so I had another go at setting up the Nest Wifi Router directly to the ONT after a reset.

It still didn't work so I called to Google support and they didn't really help other than saying that all the models should support VLAN tagging.

They suggested the Vodadone is blocking the router but I don't think that is true, I still think it isn't attempting the VLAN tagging based on the vLanScanAttemptCount = 0 shown below.

My ISP is Vodafone so I tried selecting DHCP in the WAN settings but that didn't seem to help either.

It's a pity they don't just allow you open the settings page directly rather than the Nest automatically trying to do the setup.

Does anyone have any ideas before I go an buy a managed switch?

Below is the status info for the router during the set up phase.

Note for others if you want to check the setting of your router below below:

In set up: http://192.168.84.1/api/v1/status

Once set up: http://192.168.86.1/api/v1/status

porboy

5 posts

Wannabe Geek

#2947325 28-Jul-2022 12:15

MBIL:

I had a bit of time tonight so I had another go at setting up the Nest Wifi Router directly to the ONT after a reset.

It still didn't work so I called to Google support and they didn't really help other than saying that all the models should support VLAN tagging.

They suggested the Vodadone is blocking the router but I don't think that is true, I still think it isn't attempting the VLAN tagging based on the vLanScanAttemptCount = 0 shown below.

My ISP is Vodafone so I tried selecting DHCP in the WAN settings but that didn't seem to help either.

It's a pity they don't just allow you open the settings page directly rather than the Nest automatically trying to do the setup.

Does anyone have any ideas before I go an buy a managed switch?

Below is the status info for the router during the set up phase.

Note for others if you want to check the setting of your router below below:

In set up: http://192.168.84.1/api/v1/status

Once set up: http://192.168.86.1/api/v1/status

Interesting, I ran http://192.168.86.1/api/v1/status on my working AC-1304 Google WiFi setup and notice that the differences are "countryCode": "au", "pppoeDetected": true, "vlanScanAttemptCount": 1, "vlanScanComplete": true } .

Mine is running the same "softwareVersion": "14150.43.81". Your post has US country code, maybe after resetting you need to connect via DHCP behind a working router first to update to au? Then dive into Advanced network and select pppoe etc. Good luck.

MBIL

4 posts

Wannabe Geek

#2953237 10-Aug-2022 23:30

I couldn't get this to work so in the end I purchased the router below and set up VLAN tagging on one of the ports.

https://www.pbtech.co.nz/product/SWHTPL1006/TP-Link-TL-SG108E-8-Port-Gigabit-Easy-Smart-Switch

My conclusion is the the US model of Nest Wifi doesn't do VLAN tagging for some unknown reason even though Google support insists it does.

I used this article to set up the router:

https://superuser.com/questions/1148268/how-to-ditch-centurylink-fiber-modem

I wanted to set the router up as follows:

Available as LAN port
Available as LAN port
Available as LAN port
Available as LAN port
Available as LAN port
In from router LAN
Out to router WAN (VLAN 10 untagged)
In from from ONT (VLAN 10 tagged)

So I followed these steps:

Plug your computer into port 5 of the switch
Go to http://192.168.86.152 in your browser
Login with admin for the username and password
Click VLAN on the left
Click 802.1Q VLAN on the left
Enable 802.1Q VLAN Configuration
Click "Apply"
Type 10 into the VLAN ID box, and name it "Fiber"
Check the "Tagged" radio button for Port 8
Check the "Untagged" radio button for port 7
Click "Add/Modify"
Click 802.1Q PVID on the left
Check Port 7 and 8
Type 10 into the PVID box
Click "Apply"
Plug the cable from the ONT into Port 8
Plug the router into Port 7
Click "Save Config" and confirm

I then set up the following for the LAN side

Click VLAN on the left
Click 802.1Q VLAN on the left
Enable 802.1Q VLAN Configuration
Click "Apply"
Type 2 into the VLAN ID box, and name it "Ethernet"
Check the "Untagged" radio button for ports 1-6
Click "Add/Modify"
Click 802.1Q PVID on the left
Check Port 1-6
Type 2 into the PVID box
Click "Apply"
Plug the cable from the Nest Wifi into port 6
Click "Save Config" and confirm

This seems to be wokring fine but I am no expert on VLAN settings so if anyone has any suggested improvements to the set up above let me know.

1 | 2 | 3 | 4 | 5