Connect in wired Ethernet the Wan of a secondary Google WiFi with the Lan of a main Google WiFi ?

[Sylvain_Cortes]

Hello,

I have a first generation Google WiFi, the ones with a Wan and a Lan port.

I have a question and I can't find a precise answer...

Here is the diagram of my network with the 3 cases of use that I have at home: https://picallow.com/network/

The case (1) corresponds to the classic use case, i.e. the Google WiFi are only connected to each other through the WiFi Mesh network

I have Ethernet points all over my house and I would like to use the best of both worlds : the Google WiFi spreaded in my house + to be able to connect them using Ethernet when it is possible to improve the connection - this corresponds on the diagram to use cases (2) and (3)

In case (2) I have equipments connected in WiFi to a Google WiFi, but I used the Wan port of this one to connect it using Ethernet with the main Google WiFi which is used as a Router.

Case (3) is in fact a variant of case (2), the difference is that on this Google WiFi, the equipments are connected via Ethernet on the Lan port of the Google WiFi - The Wan port of the Google WiFi is connected using Ethernet to the Main Google WiFi which is used as a Router

This seems to work, but I have from time to time sudden drops in network throughput, so I wonder if this configuration is supported (using an Ethernet connection via the Wan ports of the secondary Google WiFi to connect them to the main Google WiFi which is used as a router) - Because of course, the WiFi Mesh network remains active between all the Google WiFi, so doesn't this create loops or network problems?

Thank you in advance for your help, as I can't find any specific answer to this question.

Sylvain

[olavrb · Accepted solution]

Ethernet between Nest Wifi units is known as wired backhaul, and is a supported configuration. More on that:

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

Here is a diagram I've made on it:

• https://www.googlenestcommunity.com/t5/Nest-Wifi/Ethernet-backhaul/m-p/284073/highlight/true#M31892

For reliability, it's recommended to go either all wired or all wireless on the backhaul/connection between Nest Wifi units; don't mix. This is because mesh (802.11s) does not travel over ethernet.

"Because of course, the WiFi Mesh network remains active between all the Google WiFi, so doesn't this create loops or network problems?" No, wireless mesh (802.11s) will only be active between the primary/master Nest Wifi unit, and the only wireless secondary one, in your setup.

Loops are stopped by STP (spanning tree protocol) built in to Nest Wifi. Thus it's recommended to use unmanaged switches with no loop detection/prevention features. If you happen to have managed/smart switches, make sure to disable conflicting features. More on that:

• https://www.reddit.com/r/GoogleWiFi/comments/qpurq8
• https://www.reddit.com/r/GoogleWiFi/comments/ghkqnz/comment/fq9uwnx/

[Sylvain_Cortes · Accepted solution]

Olavrb, first of all, thank you very much for your very clear answer.

I am reassured that this configuration is supported (it seemed obvious, but the articles on the subject mix several terms that are not consistent across the different articles, which makes things confusing I think...)

My switches are all NetGear GS108E v3 Manageable - I'm not sure if there is STP implemented on these switches (they are entry level switches) - but I checked, "Loop detection" is disabled. I'll monitor the performance on the network in the future to see if it works fine.

About this sentence in your answer "No, wireless mesh (802.11s) will only be active between the primary/master Nest Wifi unit, and the only wireless secondary one, in your setup." -> If I understand correctly, as soon as a Secondary One is connected to the Primary one by an Ethernet cable, it automatically does not participate in the wireless mesh anymore? Is this correct?

If i understand well, this is how it works with use case (1), (2) & (3):

Thanks again for your answer and your help to the community!

Sylvain

[olavrb · Accepted solution]

Ethernet between Nest Wifi units is known as wired backhaul, and is a supported configuration. More on that:

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

Here is a diagram I've made on it:

• https://www.googlenestcommunity.com/t5/Nest-Wifi/Ethernet-backhaul/m-p/284073/highlight/true#M31892

For reliability, it's recommended to go either all wired or all wireless on the backhaul/connection between Nest Wifi units; don't mix. This is because mesh (802.11s) does not travel over ethernet.

"Because of course, the WiFi Mesh network remains active between all the Google WiFi, so doesn't this create loops or network problems?" No, wireless mesh (802.11s) will only be active between the primary/master Nest Wifi unit, and the only wireless secondary one, in your setup.

Loops are stopped by STP (spanning tree protocol) built in to Nest Wifi. Thus it's recommended to use unmanaged switches with no loop detection/prevention features. If you happen to have managed/smart switches, make sure to disable conflicting features. More on that:

• https://www.reddit.com/r/GoogleWiFi/comments/qpurq8
• https://www.reddit.com/r/GoogleWiFi/comments/ghkqnz/comment/fq9uwnx/

[Sylvain_Cortes · Accepted solution]

Olavrb, first of all, thank you very much for your very clear answer.

I am reassured that this configuration is supported (it seemed obvious, but the articles on the subject mix several terms that are not consistent across the different articles, which makes things confusing I think...)

My switches are all NetGear GS108E v3 Manageable - I'm not sure if there is STP implemented on these switches (they are entry level switches) - but I checked, "Loop detection" is disabled. I'll monitor the performance on the network in the future to see if it works fine.

About this sentence in your answer "No, wireless mesh (802.11s) will only be active between the primary/master Nest Wifi unit, and the only wireless secondary one, in your setup." -> If I understand correctly, as soon as a Secondary One is connected to the Primary one by an Ethernet cable, it automatically does not participate in the wireless mesh anymore? Is this correct?

If i understand well, this is how it works with use case (1), (2) & (3):

Thanks again for your answer and your help to the community!

Sylvain

[olavrb · Accepted solution]

Happy to help. 🙂

"If I understand correctly, as soon as a Secondary One is connected to the Primary one by an Ethernet cable, it automatically does not participate in the wireless mesh anymore? Is this correct?"

Yep. So your new diagram looks right. I'd try to wire unit 1 and 1 (two with same number) if possible though. If straight up ethernet cables isn't an option, maybe ethernet over coax (MoCA) or power line is?

About the switch, seems it has a web gui where features can be configured.

• https://kb.netgear.com/25093/GS108Ev3-FAQs

Maybe a place to start is to make sure no features GS108 (no "E") does not have is enabled? I got GS108 myself.

[MichaelP]

Just to add on to @olavrb 's answer, which is quite good and accurate, I personally prefer variant #2 over variant #3. Both will work, but since the two Ethernet ports are bridged in software, all of the traffic between the LAN-port connected switch in #3 and the rest of the network is being copied by the #3 unit's processor, putting higher load on it than variant #3. In short, I like to build a complete wired network first, rooted in the LAN port of the primary unit, and then hang everything off of that (wired secondary units and as many client devices as possible, especially anything that streams video or is used for gaming).

[Sylvain_Cortes]

Thanks for the notes MichaelP - gotcha - yep when it is possible I will do it this way

[LovelyM]

Hi everyone,

Chiming in to check if you still need help. Don't hesitate to tell me if you have other questions or concerns. I want to ensure you're all sorted out.

Cheers, 
Lovely

[LovelyM]

Hello there, 

We haven't heard from you in a while, so we'll be locking this thread if there's still no update within 24 hours. If you have any new issues, updates or just a discussion topic, feel free to start a new thread here in the Community.

Best, 
Lovely

[edv72]

Hello, very interesting conversation. I have a similar setup with 6 points, some Google Wifi (1st gen) over Moca and some Google Nest over mesh. The Moca connected are the farthest from the router. Do you think upgrading to Nest Pro would improve reliability or does is use the same 802. 11s and won't make a difference? Thanks 

[olavrb]

No difference with Nest Wifi Pro, it too uses 802.11s.

[AbigailF]

Hey folks, 

Thanks for lending a hand, @olavrb and @MichaelP.
I wanted to follow up and see if you are still in need of any help. Please let me know if you are still having any concerns or questions from here, as I would be happy to take a closer look and assist you further.

Thanks,
Abi