According to google it’s not supported - https://support.google.com/googlenest/answer/9798157?hl=en-AU

geekiegeek:

 

According to google it’s not supported - https://support.google.com/googlenest/answer/9798157?hl=en-AU

 

It is supported on Google Nest Wifi - not Google Wifi.

Do you know something Google and PB don't? is there a specific firmware that supports this or any documentation to show it is supported? The reason I ask is that if I by one and then try and return it because it doesn't support tagging, PB will likely point out that it was clearly stated that it doesn't. From the link above ", VLAN tagging is not supported by Google Nest Wifi or Google Wifi and can cause your setup to fail." 

I am genuinely thinking of getting a set of these for a friend but I'm hesitant to pull the trigger when googles own support article says it's not supported. Would love it if it is.

geekiegeek:

 

Do you know something Google and PB don't? is there a specific firmware that supports this or any documentation to show it is supported? The reason I ask is that if I by one and then try and return it because it doesn't support tagging, PB will likely point out that it was clearly stated that it doesn't. From the link above ", VLAN tagging is not supported by Google Nest Wifi or Google Wifi and can cause your setup to fail." 

 

I am genuinely thinking of getting a set of these for a friend but I'm hesitant to pull the trigger when googles own support article says it's not supported. Would love it if it is.

 

I know what I said: I was in a conference call with the product owner before their release in New Zealand. I asked specifically about VLAN support and he said this was added because of AU/NZ. Also Orcon is providing the Google Nest as their default route now.  

I might just try emailing PB and explain the Orcon situation and see if they would still allow a return if it didn't work.

Interesting as PBTech call theirs a 'Google nest AC2200 wifi router'. If it doesn't have VLAN tagging would this one be for other parts of the world?

I see it has perforations on the lower section so guess this has a speaker?

Can't say it having no ethernet ports would help sell it to me (not that I am in the market!).

It has one ethernet port available - use a switch for more?

Hi, the nest "Point" has no ethernet ports, the nest "Router" has two, one wan and one lan. Just as with the original Google WiFi the router part (with two ports) can be setup as a router or a slave point, when in slave point mode the two ethernet port and the wifi are bridged so you can use the ethernet ports to provide wired backhaul and an extra lan port.

The nest "Point" device is physically similar to the router, but has no ethernet ports and can only wireless mesh for a backhaul.

The original Google WiFi and and newer Nest devices can be mixed and matched in the same network. The original Google WiFi only comes in a single hardware sku and just like the nest router can be in router or point mode. So clearly the newer nest point was a cost saving incarnation.

As for vlan support, as has been stated the original Google WiFi does not support vlan tagging on the WAN, as for the product at PBTech, I note its the same product code GA00595-AU as Harvery Norman has the exact same product code.

So my conclusion is that the PBTech site is wrong, not the first time I might add

Cyril

After reading this thread and eager to get rid of the spark modem and plug a decent WiFI router directly into the Chorus ONT, I purchased the new Google Nest WiFi router (GA00595-AU).

However, it seems that as found by the OP, the Nest WiFi does NOT support VLAN tagging, in spite of what may been mentioned in that conference call.

It even displays a very specific error message informing me of the issue. 

It could be the Google WiFi, not a Google Nest WiFi.

Hi Aploeger, I recommend you return the system and ask for money back, not only does it not support Vlan tagging a recent firmware update has rendered them totally unfit for purpose, this issue I discussed in this thread and to my knowledge it still exists today.

Cyril

Edit, by the way the issue I mentioned seems to affect all variants of Google WiFi, Nest etc.

Definitely the Nest Wifi...

Thanks. Just fired an email to a contact.