Google WiFi Reviewed

[bernard038]

The only way GWifi will work in bridge mode is to disconnect all mesh-connected nodes to the primary unit in the app. So mesh connectivity is null and void.

..So Google Wifi will turn into a Netgear Orbi, but without the dedicated backhaul channels... I think i will buy the giant overpriced air-refreshener instead of Google Wifi....

 

[thiggins]

To make sure i didn't misunderstood something (English is not my native language) The phrase "Does not support access point mode for mesh configurations" basically means that when Google Wifi is set in bridge mode (disabling all router functions, because you already have a decent router) the additional wifi points act as range extenders and / or as objets d'art, nice looking but having no specific function (of which we already have quite a collection at home, thanks to the misses).

What I mean is that the only way you an have a mesh network is to run the root node (the one connected to your modem) in NAT. The only bridged / AP configuration supported is a single Wifi point.

 

[thiggins]

..So Google Wifi will turn into a Netgear Orbi, but without the dedicated backhaul channels... I think i will buy the giant overpriced air-refreshener instead of Google Wifi....

No. NO OTHER Wifi points will be connected.

 

[whsbuss]

No. NO OTHER Wifi points will be connected.

Exactly. Bridge mode only works on a single unit. So you can ethernet connect each unit in bridge mode but it won't be a wireless mesh.

 

[sfx2000]

For the curious - that STMicro chip is the embedded controller that Google has added to the ARM-based chromebooks - it's there for board support -- it works hand-in-hand with the TPM module Tim mentioned in the review.

More info here

https://www.chromium.org/chromium-os/ec-development

The Chromium OS project includes open source software for embedded controllers (EC) used in recent ARM and x86 based Chromebooks. This software includes a lightweight, multitasking OS with modules for power sequencing, keyboard control, thermal control, battery charging, and verified boot. The EC software is written in C and currently supports two different ARM Cortex based controllers. Intel based designs, such as the Chromebook Pixel use the TI Stellaris LM4F (Cortex M4) while the Samsung Chromebook (XE303C12) and HP Chromebook 11 use an ST-Micro STM32F100 (Cortex M3). Some STM32L variants are also supported. Support for additional embedded controllers is ongoing.​

 

[pbarnes]

With these results and early firmware I don't see how anyone can justify +$200 for the eero.

FWIW, I bought 3 ASUS OnHubs off eBay for $99 each new. I meshed them over Ethernet and now have the best networking setup I've had in a long time.

Even a single OnHub provided similar routed Internet speeds to my iPhone 7 as my RT-AC5300. The OnHub lost slightly on the downlink but outperformed the AC5300 on uplink.

Here's my speed test standing right next to each one:

RT-AC5300

http://www.speedtest.net/my-result/i/1892868618

ASUS OnHub running latest firmware:

http://www.speedtest.net/my-result/i/1892869456

I recommend this setup to anyone looking to build a great network at very low prices.

I turned off my RT-AC5300 and I'm never looking back.

 

[Novirius]

Thanks pbarnes, I was actually thinking about meshing Onhubs instead of Google Wifis. Seems just as expensive if you buy from ebay, but you get a better product (Correct me if I'm wrong).

 

[whsbuss]

With these results and early firmware I don't see how anyone can justify +$200 for the eero.

FWIW, I bought 3 ASUS OnHubs off eBay for $99 each new. I meshed them over Ethernet and now have the best networking setup I've had in a long time.

Even a single OnHub provided similar routed Internet speeds to my iPhone 7 as my RT-AC5300. The OnHub lost slightly on the downlink but outperformed the AC5300 on uplink.

Here's my speed test standing right next to each one:

RT-AC5300

http://www.speedtest.net/my-result/i/1892868618

ASUS OnHub running latest firmware:

http://www.speedtest.net/my-result/i/1892869456

I recommend this setup to anyone looking to build a greaat network at very low prices.

I turned off my RT-AC5300 and I'm never looking back.

Wish I could get ethernet to remote spots in my home - best mesh you can build.

 

[pbarnes]

Thanks pbarnes, I was actually thinking about meshing Onhubs instead of Google Wifis. Seems just as expensive if you buy from ebay, but you get a better product (Correct me if I'm wrong).

Exactly. $299 for a Google Wifi 3 pack or $99 x 3 for 3 OnHubs.

To be honest you could get away with 2 OnHubs, but might as well go big.

Compared to the $399 I wasted on the RT-AC5300, it's a no brainer. I don't want to tweak anything. I just want to plug it in and have it work. I used to run ISP networks and don't want to do that sh*t at home.

There's a couple of things to keep in mind:

* The firmware that comes preinstalled on the OnHub is ancient and doesn't know it can be a "leaf node". So you need to connect each one directly to your upstream until it auto-updates. Takes 5 minutes per AP. Then everything works great.

* Depending on AP radio overlap, some devices will "stick" to a less optimal node for longer than you'd expect. There's a fine line here between ping pong and optimal performance. This seems to affect my Android devices more than Apple devices.

That's it for negatives. This is really, really great. As good as rolling your own Ubiquiti based network for like 20% of the price.

 

[thiggins]

I think it was a very smart move for Google to give new life to OnHubs via mesh. I'm sure TP-Link and ASUS will appreciate the goose in sales once people realize they can do this. You may see discounts go away....

 

[pete y testing]

hi tim

can you incorperate the wifi data into the mesh remash blog so we can see how google wifi compare to all the others coverage and throughput wise including the orbi

will have a deeper read of the review over the weekend but those graphs pretty much show googles own paid testing was only based on a single unit and after all what the point of a mesh system with only 2 points

pete

 

[pbarnes]

I think it was a very smart move for Google to give new life to OnHubs via mesh. I'm sure TP-Link and ASUS will appreciate the goose in sales once people realize they can do this. You may see discounts go away....

It would be pretty great if you tested all these systems with ethernet backhaul at some point.

 

[thiggins]

Sorry, Pete. I honestly don't have the time right now.
Next step, when I have time, is to get a subset of the data into the Charts as an official benchmark. I've been hoping to hold off on that until I get a chamber-based test process set up, but Octoscope isn't ready with their smaller chambers yet.

It's pretty clear Orbi blows all the three-pack mesh products away.

 

[thiggins]

It would be pretty great if you tested all these systems with ethernet backhaul at some point.

I at least test bridging for one hop, which no one else does.

While interesting, that is not the primary mode that these products are intended to be used in.

Not enough hours in the day to test all the stuff I'd (or you guys) would like to...

 

[pete y testing]

i will say no wps will have consequences as ppl return them simply because their printer wont connect etc , with more and more IoT devices using wps connection method i think this is a real deal breaker that i cant why google would not have seen , certainly a strange decision , seems google use the same though process as apple , eg we do it our way !!

 

[thiggins]

i will say no wps will have consequences as ppl return them simply because their printer wont connect etc , with more and more IoT devices using wps connection method i think this is a real deal breaker that i cant why google would not have seen , certainly a strange decision , seems google use the same though process as apple , eg we do it our way !!

Google cited security concerns as the reason why WPS is not supported. It's not supported on eero, Luma or Amplifi for the same reason. Only Orbi, which isn't true mesh, supports WPS.

 

[whsbuss]

I at least test bridging for one hop, which no one else does.

While interesting, that is not the primary mode that these products are intended to be used in.

Not enough hours in the day to test all the stuff I'd (or you guys) would like to...

Tim,

Thank you SO much for all you do. Without your expertise and determination we would be in the dark when it comes to networking.

 

[thiggins]

Thank you SO much for all you do. Without your expertise and determination we would be in the dark when it comes to networking.

Thanks. Just feeling a bit overwhelmed lately. The new test processes are taking too much time and need to be streamlined.

 

[mokodi]

Tim thanks a lot for the great review as always.

Any idea what Google Wifi uses for backhaul? 2.4 ghz? I'm really surprised to see the eero perform in the same range as the other solutions since it has a dedicated backhaul. I'd have really expected it to perform somewhere between the Orbi and the others.

I'm really puzzled as to why most of these products are only AC1200 with no dedicated backhaul. I would think being a mesh product would mean more radios rather than less.

 

[sfx2000]

I think it was a very smart move for Google to give new life to OnHubs via mesh. I'm sure TP-Link and ASUS will appreciate the goose in sales once people realize they can do this. You may see discounts go away....

Was nice to see this - the Legacy On-Hubs being able to work together with the Google WiFi devices...

Should also note that while it's not as open as many BHR's might be, Google has been pretty good about rolling updates out - a side-effect of the WiFi device basically being headless Chromebooks...

Good stuff - might not appeal to those who like getting under the hood on legacy platforms, but for many, like On-Hub, it's a nice turnkey solution...