General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Török Edwin" <edwin+ml@etorok.eu>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] eero adds sqm
Date: Tue, 29 May 2018 21:37:54 +0100	[thread overview]
Message-ID: <39ddffd4-9aff-65c2-f477-8829a3958277@etorok.eu> (raw)
In-Reply-To: <CAA93jw7kzVacNRRriVdtiCwxBbf-23wjLLRfpAO1C0Og4R-Lxw@mail.gmail.com>

On 29/05/18 18:09, Dave Taht wrote:
> I am so happy to see some companies have the ability to update
> existing systems in the field to have better queue management
> software. I rather liked eeros little boxes, and they were some of the
> first folk to pay attention to the fq_codel on wifi work, and now,
> uplinks.
> 
>  https://blog.eero.com/introducing-eero-labs-building-future-home-wifi/
> 

The eero itself looks nice, however be careful of the Arris cable modem
they offer.

I don't know if all Arris modems are like this, but my current ISP uses
an Arris based cable modem containing a Puma 6 chipset, which has a very
annoying high latency bug [2] that more than a year later is still
unfixed in the production firmware [1].

At first I thought my WiFi signal was bad, but if I ping the router on
wired LAN several times a minute you get >50ms latency spikes. Using any
kind of bufferbloat management behind the router is hopeless with the
wired connection being this bad, even in modem mode.
I should probably switch to a different ISP...

[1]
https://community.virginmedia.com/t5/Gaming-Support/Hub-3-Compal-CH7465-LG-TG2492LG-and-CGNV4-Latency-Cause/td-p/3271492
[2]
https://www.theregister.co.uk/2016/12/03/intel_puma_chipset_firmware_fix/
[3] http://www.dslreports.com/tools/puma6

Best regards,
--Edwin

      reply	other threads:[~2018-05-29 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 17:09 Dave Taht
2018-05-29 20:37 ` Török Edwin [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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39ddffd4-9aff-65c2-f477-8829a3958277@etorok.eu \
    --to=edwin+ml@etorok.eu \
    --cc=bloat@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