From: "jf@jonathanfoulkes.com" <jf@jonathanfoulkes.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] where home 5G can go south
Date: Fri, 28 Oct 2022 17:10:30 -0400 [thread overview]
Message-ID: <B078ECBA-9A20-49B1-854E-8A31D7174720@jonathanfoulkes.com> (raw)
In-Reply-To: <CAA93jw7wvqD7vs7tXkf_-kQ=j0q1NThTcaS6PuA3fCiQHEqZBw@mail.gmail.com>
We’ve observed growing variability on some TMHI setups from our fleet, and it seems there is a correlation to usage growth on a single tower. Seems neighbors talk to hear other after all ;-)
And yes, horrible bufferbloat on these variable capacity links.
> The author switched to verizon, but what guarantees of continued
> reliability does one have?
It seems none ATM, as it really depends on user density vs tower capacity. Woe to those that share a tower with a busy highway, ‘rush hour’ likely means low capacity and even higher latencies.
Cheers,
Jonathan Foulkes
> On Oct 27, 2022, at 11:37 PM, Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> This had some details as to the things that could go wrong from an
> initial happy install of t-mobile, to something terrible.
>
> The author switched to verizon, but what guarantees of continued
> reliability does one have?
>
> https://blog.networkprofile.org/redundant-wan-ditching-t-mobile-5g-for-verizon-5g/
>
> (both services had horrible bufferbloat)
>
>
> --
> This song goes out to all the folk that thought Stadia would work:
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2022-10-28 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 3:37 Dave Taht
2022-10-28 21:10 ` jf [this message]
2022-10-29 9:40 ` Erik Auerswald
2022-10-29 16:51 ` Sebastian Moeller
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=B078ECBA-9A20-49B1-854E-8A31D7174720@jonathanfoulkes.com \
--to=jf@jonathanfoulkes.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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