General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht via Bloat <bloat@lists.bufferbloat.net>
Cc: Dave Taht <dave.taht@gmail.com>,
	"Luis A. Cornejo" <luis.a.cornejo@gmail.com>,
	libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [Bloat] Fwd: [New post] How Good is FWA Wireless?
Date: Wed, 8 Feb 2023 16:53:19 -0800	[thread overview]
Message-ID: <20230208165319.583064e7@hermes.local> (raw)
In-Reply-To: <CAA93jw5SN6QDNsvvrSZqL8f3uTPt7raMTDS7R9M2YcuNLC4zqQ@mail.gmail.com>

On Wed, 8 Feb 2023 16:43:59 -0800
Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:

> On Wed, Feb 8, 2023 at 2:41 PM Luis A. Cornejo <luis.a.cornejo@gmail.com> wrote:
> >
> > As a former T-mobile HSI customer, I can attest the horrible queue management. The deprioritization was so bad that it became basically unusable, even a ping or DNS lookup just lagged. I latched to a tower near the interstate about 2 miles away. I knew when there was an accident at the interstate, my online experience correlated very well.  
> 
> I ranted over here about how bad just the depriotization could become,
> and also pointed to a flaw, I believe, in how long devices hold onto
> packets in that case. I fear that when the network is getting toasty,
> and comes back online that there is a thundering herd of devices,
> enormous backlogs of stale syns, and so on that hit it, and what is in
> place is some sort of timed rate limiter to deal with it, not very
> well. It is the only explanation I have for seeing pings come back on
> 1s intervals...
> 
> https://blog.cerowrt.org/post/flaws_in_flent/
> 

I think this is leftover circuit switch telco mindset. Everyone needs/wants/will buy their own slice.
It looks like they keep trying and trying to see value added networking. But well-designed best effort
is always cheaper, more efficient and overall faster. We heard this story before with MPLS, ATM, etc.

      reply	other threads:[~2023-02-09  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49312101.15152.0@wordpress.com>
2023-02-08 16:13 ` Dave Taht
2023-02-08 17:07   ` Sebastian Moeller
2023-02-08 22:41     ` Luis A. Cornejo
2023-02-09  0:43       ` Dave Taht
2023-02-09  0:53         ` Stephen Hemminger [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=20230208165319.583064e7@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=luis.a.cornejo@gmail.com \
    /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