[Cerowrt-devel] google wifi

[Cerowrt-devel] google wifi

[Matt Taggart]

Google is working with TP-LINK (and soon ASUS) on wifi (is there a
make-wifi-fast list this should have gone to?)

Google Blog: Meet OnHub: a new router for a new way to Wi-Fi
https://tinyurl.com/nloy3jm

product page
https://on.google.com/hub/

--  
Matt Taggart
matt@lackof.org

Re: [Cerowrt-devel] google wifi

[Matt Taggart]

Matt Taggart writes:
> Google is working with TP-LINK (and soon ASUS) on wifi (is there a
> make-wifi-fast list this should have gone to?)
> 
> Google Blog: Meet OnHub: a new router for a new way to Wi-Fi
> https://tinyurl.com/nloy3jm
> 
> product page
> https://on.google.com/hub/

I talked to a friend that worked on it:

<ggg> the kernel for the Onhub router is under "whirlwind" project
 name in the chromium.org source tree. The firmware is coreboot and is
 also public.
<ggg> Openwrt has all the support for the Qualcom chipset but not
 this board.
<ggg> Openwrt also require fastboot and won't work with Coreboot.
<ggg> Key bits are the Device Tree description of the HW in this directory:
<ggg> https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/arch/arm/boot/dts/
<ggg> qcom-apq8084-mtp.dts
<ggg> qcom-apq8084.dtsi
<ggg> qcom-ipq8064-ap148.dts
<ggg> qcom-ipq8064-arkham.dts
<ggg> qcom-ipq8064-storm.dts
<ggg> qcom-ipq8064-thermal.dtsi
<ggg> qcom-ipq8064-v1.0.dtsi
<ggg> qcom-ipq8064-whirlwind-sp3.dts
<ggg> qcom-ipq8064-whirlwind-sp5.dts
<ggg> qcom-ipq8064.dtsi
<ggg> whirlwind-sp5 is what shipped. (AFAIK)
<ggg> btw, all of this was reviewed on a public chromium.org gerrit
 server.
<ggg> openwrt does support AP148
<ggg> and at some point chromeos was booting on AP148 though I don't
 expect it to work "out of the box"


-- 
Matt Taggart
matt@lackof.org

Re: [Cerowrt-devel] google wifi

[David Lang]

On Tue, 18 Aug 2015, Matt Taggart wrote:

> Matt Taggart writes:
>> Google is working with TP-LINK (and soon ASUS) on wifi (is there a
>> make-wifi-fast list this should have gone to?)
>>
>> Google Blog: Meet OnHub: a new router for a new way to Wi-Fi
>> https://tinyurl.com/nloy3jm
>>
>> product page
>> https://on.google.com/hub/
>
> I talked to a friend that worked on it:
>
> <ggg> the kernel for the Onhub router is under "whirlwind" project
> name in the chromium.org source tree. The firmware is coreboot and is
> also public.
> <ggg> Openwrt has all the support for the Qualcom chipset but not
> this board.
> <ggg> Openwrt also require fastboot and won't work with Coreboot.
> <ggg> Key bits are the Device Tree description of the HW in this directory:
> <ggg> https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/arch/arm/boot/dts/
> <ggg> qcom-apq8084-mtp.dts
> <ggg> qcom-apq8084.dtsi
> <ggg> qcom-ipq8064-ap148.dts
> <ggg> qcom-ipq8064-arkham.dts
> <ggg> qcom-ipq8064-storm.dts
> <ggg> qcom-ipq8064-thermal.dtsi
> <ggg> qcom-ipq8064-v1.0.dtsi
> <ggg> qcom-ipq8064-whirlwind-sp3.dts
> <ggg> qcom-ipq8064-whirlwind-sp5.dts
> <ggg> qcom-ipq8064.dtsi
> <ggg> whirlwind-sp5 is what shipped. (AFAIK)
> <ggg> btw, all of this was reviewed on a public chromium.org gerrit
> server.
> <ggg> openwrt does support AP148
> <ggg> and at some point chromeos was booting on AP148 though I don't
> expect it to work "out of the box"

sounds promising.

how open is the wifi driver? Is it something that we can dive into and modify 
for make-wifi-fast? or is it a typical vendor blob?

David Lang

Re: [Cerowrt-devel] google wifi

[Dave Taht]

I would like very much for someone from this group to put this box
through it's paces with flent on the isp side, and to test the wifi
side with the rtt_fair tests, and publish their results.

Re: [Cerowrt-devel] google wifi

[Matt Taggart]

David Lang writes:
> how open is the wifi driver? Is it something that we can dive into and modify
> for make-wifi-fast? or is it a typical vendor blob?

more info..

ath10k
<ggg> ChromeOS uses tools to share/merge config files. The config parts
specific to OnHub are here:  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.14/chromeos/config/armel/chromiumos-ipq806x.flavour.config
<ggg> it's using a v3.18 kernel mac80211 code base.  (USE="wireless318")

-- 
Matt Taggart
matt@lackof.org

Re: [Cerowrt-devel] google wifi

[Isaac Konikoff]

Yep, planning to do just that...but already the marketing has got me 
shaking my head... "AC1900 for Wi-Fi speeds up to 1900Mbps"




On 08/18/2015 01:56 PM, Dave Taht wrote:
> I would like very much for someone from this group to put this box
> through it's paces with flent on the isp side, and to test the wifi
> side with the rtt_fair tests, and publish their results.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

Re: [Cerowrt-devel] google wifi

[Mikael Abrahamsson]

On Wed, 19 Aug 2015, Isaac Konikoff wrote:

> Yep, planning to do just that...but already the marketing has got me 
> shaking my head... "AC1900 for Wi-Fi speeds up to 1900Mbps"

"everybody does it"

http://www.cnet.com/topics/networking/best-networking-devices/802-11ac/

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

Re: [Cerowrt-devel] google wifi

[Jonathan Morton]

[-- Attachment #1: Type: text/plain, Size: 132 bytes --]

Everyone except Apple.  They're using the same "Airport Extreme Base
Station" branding as my 2007 draft-n model.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 189 bytes --]

Re: [Cerowrt-devel] google wifi

[Isaac Konikoff]

Started testing an onhub box with lanforge and flent...just wifi to lan 
side for now compared to a netgear r8000.

Configuration of the onhub is somewhat limited because you have to use 
the google-on app and many settings are not available such as picking a 
channel, setting ht/mcs rates, disabling encryption, etc... Also, it 
appears that the wan port requires a live internet connection for any 
functionality at all.

Here are some reports and data on what I've tested so far:
candelatech.com/downloads/wifi-reports/trial2

Here are some sample plots from the data:
candelatech.com/downloads/wifi-reports/trial2/rtt_fair4be-box-plot-comparison.png

candelatech.com/downloads/wifi-reports/trial2/tcp-download-box-plot-comparison.png

candelatech.com/downloads/wifi-reports/trial2/10stations-ht80-to-onhub-udp-only.png

candelatech.com/downloads/wifi-reports/trial2/63stations-ht80-to-onhub-udp+tcp.png

I'm planning to do some more comparisons with other ap's or maybe some 
additional flent tests to netperf.bufferbloat.net. I'll publish those 
results when available.

Isaac

On 08/18/2015 01:56 PM, Dave Taht wrote:
> I would like very much for someone from this group to put this box
> through it's paces with flent on the isp side, and to test the wifi
> side with the rtt_fair tests, and publish their results.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

Re: [Cerowrt-devel] google wifi

[Isaac Konikoff]

Found an interesting way to bind firefox to an interface, so I can run 
http://www.dslreports.com/speedtest from eth1, sta1, sta2, etc...to test 
the wifi to internet path of different APs even though it eventually all 
goes through our main router at the cable modem.

http://www.ryde.net/code/bind.c.txt

Anyway, here are some results:

eth0 on my desktop: http://www.dslreports.com/speedtest/1516977

eth1 through Onhub: http://www.dslreports.com/speedtest/1517395

sta1 through Onhub: http://www.dslreports.com/speedtest/1517298

sta2 through Onhub: http://www.dslreports.com/speedtest/1517364

eth1 through R8000: http://www.dslreports.com/speedtest/1517769

sta1 through R8000: http://www.dslreports.com/speedtest/1517821

sta2 through R8000: http://www.dslreports.com/speedtest/1517871




On 09/22/2015 03:08 PM, Isaac Konikoff wrote:
> Started testing an onhub box with lanforge and flent...just wifi to lan
> side for now compared to a netgear r8000.
>
> Configuration of the onhub is somewhat limited because you have to use
> the google-on app and many settings are not available such as picking a
> channel, setting ht/mcs rates, disabling encryption, etc... Also, it
> appears that the wan port requires a live internet connection for any
> functionality at all.
>
> Here are some reports and data on what I've tested so far:
> candelatech.com/downloads/wifi-reports/trial2
>
> Here are some sample plots from the data:
> candelatech.com/downloads/wifi-reports/trial2/rtt_fair4be-box-plot-comparison.png
>
>
> candelatech.com/downloads/wifi-reports/trial2/tcp-download-box-plot-comparison.png
>
>
> candelatech.com/downloads/wifi-reports/trial2/10stations-ht80-to-onhub-udp-only.png
>
>
> candelatech.com/downloads/wifi-reports/trial2/63stations-ht80-to-onhub-udp+tcp.png
>
>
> I'm planning to do some more comparisons with other ap's or maybe some
> additional flent tests to netperf.bufferbloat.net. I'll publish those
> results when available.
>
> Isaac
>
> On 08/18/2015 01:56 PM, Dave Taht wrote:
>> I would like very much for someone from this group to put this box
>> through it's paces with flent on the isp side, and to test the wifi
>> side with the rtt_fair tests, and publish their results.
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>