From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] anybody have a nest?
Date: Thu, 11 Aug 2022 12:33:22 -0700 [thread overview]
Message-ID: <CAHb6Lvp0DXAvopt92Rh=MV63ysHTPYC2oAFYj-L9gig1rpc4sQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4FtWMT+UEt5zH2vSD6Kp9Oe2_0BdxU5ELHs8eBLk+WQw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1829 bytes --]
I have nest protects and thermostats but not "nest wifi." I used
structured wiring and WiFi APs that support the 6GHz band. I don't think
Google's APs support 6GHz but could be wrong.
I'm thinking to avoid mesh and use Corning's clear track fiber
<https://www.corning.com/fiber-to-the-premise/worldwide/en/home/products/clear-track-fiber-pathway.html>
where
possible. Then find switches that support 100Gb/s SFPs per those
SerDes/laser economics. Future proof so to speak.
Bob
On Thu, Aug 11, 2022 at 11:56 AM Dave Taht via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:
>
> https://wccftech.com/google-and-nest-wifi-are-getting-an-update-that-improves-performance-on-slower-connections/
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: Type: text/html, Size: 2658 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
prev parent reply other threads:[~2022-08-11 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 18:56 Dave Taht
2022-08-11 19:33 ` Bob McMahon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHb6Lvp0DXAvopt92Rh=MV63ysHTPYC2oAFYj-L9gig1rpc4sQ@mail.gmail.com' \
--to=bob.mcmahon@broadcom.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox